Gateway Configuration

When tree-gateway is started, it uses the file tree-gateway.json to load the initial configurations it needs to start. The most important one is the location of Redis database.

Then, knowing where the redis database is, the gateway can ask database for all other configurations, including the installed middlewares and APIs.

The redis database store configurations about:

• the gateway itself - which kind os services are enabled / monitors / protocols and ports for the listening services / loggers etc;
• the admin users - Who can access the configuration services;
• the installed middlewares - To extend gateway features / listen an handle events etc;
• and all API configurations - The main purpose of the gateway: to route, secure and manage your APIs.

So, all of those configurations are made directly into the redis database. Messages are sent to all cluster nodes when some of them is changed. We provide 3 different ways to you manage all of those configurations:

• Use the Admins REST API;
• Use the Node JS SDK;
• Use the CLI admin.

All of those tools will help you to send the configurations to the redis database.

But, before you can change any gateway configuration, you need to define one first user and password to you. With this first user created, you can use any the above methods (REST API, SDK or CLI) to manage all of your configurations, including the creation of other users to the gateway admin service.

To create this fisrt user, you must use the userAdmin tool.