...
Difficulty: starter
Content
| Table of Contents | ||||
|---|---|---|---|---|
|
Learning Objectives
After reading this article you will be able to:
Recognize the different server clusters
Know how to reach servers within your server cluster
On what
...
cluster is your environment?
A
...
client's environment is located on a
...
cluster together with other clients (except clients with a dedicated cluster). To find out what cluster your
...
environment is on you
...
add '__serverinfo__' to the URL after you are logged in directly after the /axxerion/ part in the URL and hit enter
example: https://fmg.axxerion.com/axxerion/ui/ → https://fmg.axxerion.com/axxerion/__serverinfo__
...
What is a server
...
Within these clusters, a client
...
environment can be accessed via several servers.
...
| Info |
|---|
...
The backup and test environments of a client use the same login name and password as the Production environment |
...
but are accessible through different URLs |
Environment name | Description | URL |
|---|---|---|
Production |
...
Production environment |
...
{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: example: axbk17.axxerion.com/axxerion/signin | |
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: http://axts17.axxerion.com/axxerion/signin | |
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 al lot of customizations happening | axsg{cluster}.axxerion. |
...
com/axxerion/signin example: http://axsg17.axxerion.com/axxerion/signin | ||
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 Testing environment to prevent your changes from getting overwritten.
...
Report servers and Converter engines
The Report servers and Converter engines have a ton of computing power and are in charge of executing the report calls that are made in Workplace. There are subtle differences between a Report server and Converter engine which decides in what situation which one is used.
The Report servers and Converter engines are for shared use for all Workplace servers. Whenever a Workplace server wants to convert a file/a call is send out, a request is sent to the available Report server/Converter engine, which handles the request and then returns it to the Workplace server.
Document servers
Workplace can be used as a Document Management System (DMS). The documents that are uploaded on here are not actually stored on the cluster but on the document server. The Document server, or File server, is just a big hard drive.
Summary
| Rw ui textbox macro |
|---|
|
Search
...
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.