Verj.io Applications are portable. They can be run in the Verj.io Studio and deployed to test and production environments without having to change or reconfigure the application.
To achieve this each Verj.io Runtime Environment is configured individually. Important features such as user authentication and connections to databases and email servers are configured in these environments.
This allows, for example:
- Test environments to connect to test database servers and authentication services.
- Production environments to connect to production database servers and authentication services.
The Verj.io Application doesn’t know the connection details in any given environment, it simply uses these configured connections.
The Verj.io Administration Application is used to configure a Verj.io Runtime Environment.
Verj.io Studio
The Administration Application can be opened by selecting the Embedded Server in the server selection drop down on the right-hand side of the main toolbar, clicking on the 
icon and selecting Start Server Admin App.
The Embedded Server’s Administration Application is then opened in your browser.
Note the Embedded Server must be running to open its Administration Application.
Verj.io Service Plans
The Administration Application can be opened by logging into the Verj.io Cloud Portal and clicking on the Admin Application on your Service Plan’s Settings Page.
At least one of the Service Plan’s Application Containers must be running to configure it.
Verj.io On-Premises
The Admin Application is distributed with every On-Premises environment and can be accessed in a browser using the URL: http://<hostname>:<port>/<webapp>/ebaseAdmin.eb e.g. http://myOnPremisesEnvironment/ebase/ebaseAdmin.eb.
The Adminstration Application prompts for a user name and password. These were requested during the installation of the On-Premises environment.