The UDM:Config regular form contains connection details for the Atrium Integrator repository and Atrium Integrator engine. The repository is created when the AR System server is installed, and the parameters are configured with default settings from the AR System server. The settings are stored in the UDM:Config form fields and can be modified by users with AR System administrator level access.
You need to update the UDM:Config form if you are performing one of the actions listed below:
|Configure UDM in a server group|
A server group environment consists of two or more servers that share the same database and are designated as part of a server group.
|Configure UDM in a non-server group environment|
In a non-server group environment, a single server exists. In case of server failure, jobs stop running.
Note: You need not rank the single server by using the AR System Server Group Operation Ranking form.
|Restore the database|
When you perform database restore, the data might contain references to the production server which may not be applicable
Note: Update the Atrium Integrator Server Name field in the UDM:Config form when you restore the database.
After updating the UDM:Config form, You must restart the AR System server for the changes to take effect.
Updating the UDM:Config form
The UDM:Config form includes the following sections:
|Repository Connection Details|
|Atrium Integrator Engine Connection Details|
Update the fields in this section if you are configuring UDM in a server group or a non-server environment.
Updating the Atrium Integrator Engine Connection Details
|Field||Description||Server group environment||Non-server environment|
|Atrium Integrator Server Name|
The name of the server hosting the Atrium Integrator. By default this is the AR System server name.
Note: BMC recommends you not to use server alias name, host name, and IP addresses.
Even when you select a server in the Atrium Integrator Engine Server Name which is not ranked 1 in the AR System Server Group Operation Ranking form, the system runs the jobs on the server which is ranked 1.
The server name mentioned in the Atrium Integrator Engine Server Name must match with the value specified in the Server-Connect-Name parameter in the ar.cfg form.
As a single server exists in a non-server environment, the Atrium Integrator jobs run on the single server.
The server name mentioned in the Atrium Integrator Engine Server Name must match with the value specified in the Server-Name parameter in the ar.cfg form.
The host name assigned to the server hosting the Atrium Integrator server. By default, this is the AR System server host name.
The Host name mentioned in the UDM:Config form must match with the diserver or carte server host name mentioned in the armonitor.cfg form.
As an example, you can see the AR server name mentioned in the armonitor.cfg file below.
The recommendation is same for server group and non-server environment .
|Failover Server Name||The failover server is the server which is ranked as 2 in the AR System Server Group Operation Ranking form. The failover server substitutes the primary server in case of an outage or a failure and the system runs the jobs on the failover server.||There is no failover server in the non-server environment. In case of server failure, jobs stop running.|
This field indicates if the server name specified in the Atrium Integrator Server Name field is the default server.
The field value set to Yes by default.
|Port||The server port assigned to the Atrium Integrator server.||The default port value must be 20000.||The default port value must be 20000.|
Example: Configuring UDM in a server group environment
The below graphics display the settings in the UDM:Config form for the 3 AR servers existing in your server group environments:
|Server 1||Server 2||Server 3|
- In the above example, jobs always run on the primary server NEWSC-PD-AR-01. Even if you trigger the jobs from the secondary or a third server, the jobs always run on the primary server.
- In the above example, the diserver or carte plugin is enabled for all the 3 servers.