Gateway Configuration

When tree-gateway starts, it uses the file tree-gateway.json to load the initial configuration needed. The most important one is the Redis database location. After this first step, the gateway can ask the database for all the other configurations, such as:

• 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 and 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 inserted directly into the Redis database. If you change a configuration (regardless of which is), messages are sent to all cluster nodes to inform the new values. This happens without any need for a gateway restart (we can call it a hot-configuration-deploy). 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.

In order to interact with the Gateway you must also create a first user/password. This will allow you to 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.