Configuration form

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:

Action	Details
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. Server groups are designed to provide failover operations for crucial operations. They can also provide scalability and load balancing. Note: Before configuring the UDM:Config form for a server group environment, you must rank the Atrium Integrator servers by using the AR System Server Group Operation Ranking form. If you assign ranking 1 to a server, that server becomes primary server and runs the jobs. If the primary server fails, the secondary server (failover server) runs the jobs. Failover server is the server to which you assigned ranking 2. If you do not assign ranking to the servers in a server group environment, jobs run on the server which receives the request first. For details, see Setting-failover-rankings-for-servers-and-operations. Success Best practice We recommend that you select a non-user facing server (admin server) as a primary server.
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 in the new upgrade environment. In this case, you have to update the server name references. For details, see Updating the destination server names after data migration Note: Update the Atrium Integrator Server Name field ien the UDM:Config form when you restore the database.

Note

After updating the UDM:Config form, You must restart the AR System server for the changes to take effect.

UDM:Config form

Updating the UDM:Config form

The UDM:Config form includes the following sections:

Section	Fields
Repository Connection Details	Private RPC Program Number — A private RPC queue for all operations (such as, load and save) on the repository. The default value is 0 for no private RPC queue. API Timeout Normal (seconds) — The API time for all operations (such as, load and save) on the repository. The default value is 7200 seconds.
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. For details, see

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. Success Best practice We recommend that you not 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.
Host	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.	You need not select or enter the server name in this field. Even if you select or enter a failover server name in the UDM:Config form, the system overwrites this name and considers the server ranked as 2 on the AR System Server Group Operation Ranking form. Success Best practice We recommend that you enable the diserver or carte plugin in the armonitor.cfg file for all the servers existing in your server group environment. When a primary server fails, the jobs can run on the secondary server if the diserver or carte plugin is enabled for the secondary server.	There is no failover server in the non-server environment. In case of server failure, jobs stop running.
Is Default	This field indicates if the server name specified in the Atrium Integrator Server Name field is the default server.	After ranking the servers in the server group, the Is Default check box in the UDM:Config form is automatically selected for the server which is ranked as 1 in the AR System Server Group Operation Ranking form. If the primary server fails, the failover server starts running the jobs. In such instances, the system automatically updates the Is Default value for the failover server. When the primary is up, the system updates the Is Default field value for the primary 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.

Configuration form

Updating the UDM:Config form

Updating the Atrium Integrator Engine Connection Details

Example: Configuring UDM in a server group environment

Related topics

Remedy Action Request System 20.02

On this page