Clusters
A client's environment is located on a cluster together with other clients (except clients with a dedicated cluster). After logging in, add ‘__serverinfo__' to the URL behind '/axxerion/’ and hit enter to see on what cluster the environment is located.
Example: https://fmg.axxerion.com/axxerion/ui/ → https://fmg.axxerion.com/axxerion/__serverinfo__
To access the backup or test server of a client, you will need to know the cluster. More on the backup and test servers, see the next chapter.
Servers
On a cluster, the clients environment can be accessed via several servers.
The Backup and Test environments of a client use the same login name and password as the Production environment, but are accessed via a seperate URL.
Environment name | Description | URL |
|---|---|---|
Production | Production environment | https://{clientreference}.axxerion.com/axxerion/signin example: https://fmg.axxerion.com/axxerion/signin/ |
Backup | Short-term testing environment. Data gets refreshed every night. Changes in backup do not affect the production environment. | axbk{cluster}.axxerion.com/axxerion/signin example: |
Test | Long-term testing environment. Data is refreshed every 6-8 weeks (every release cycle). Changes in test do not affect the production environment. | axts{cluster}.axxerion.com/axxerion/signin example: |
Staging | The staging server is not used in every cluster. Data and configuration can be pushed from the staging server to the production environment. Staging is a separate paid service. Using staging requires having your own baseline. There are very few clients that make use of this functionality and it is only relevant in case of a lot of customizations happening. | axsg{cluster}.axxerion.com/axxerion/signin example: |
Replica | Standby- and replica server: This stores real-time backups of all data. The replica server is not directly accessible. | - |
Keep in mind when testing in either the backup or testing environment, all changes that are made should be manually copied to production. Since production gets copied to the backup every night, long-term testing is performed on the test environment to prevent your changes from getting overwritten.
The test environment gets overwritten with the production data about one to two weeks before the next release (to be able to test with up-to-date production data). Keep this in mind when planning or doing longer-term work on the test environment. There are also no guarantees on how often the test environment gets overwritten with the most recent production data.