Configuring multiple BMC Network Automation application servers

This topic provides special instructions applicable when you are deploying multiple BMC Network Automation application servers in your Continuous Compliance for Network Automation environment.

Configuring BMC Remedy ITSM to interact with the artifacts

BMC Remedy ITSM interacts with the artifacts that were installed by the BMC Atrium Orchestrator Content installer.

The system installs a single registry by default, assuming that you have only a single application server. When multiple application servers are deployed, you must create a CAI Application Registry for each server.

Set the Application Name in each registry to BMC Network Automation. The Registry Name should be able to easily identify a specific application server (for example, bna-ITOPS-01).

See Configuring BMC Remedy ITSM to interact with the artifacts.

Enforcing continuous compliance to change management process for BMC Remedy Service Desk initiated changes

When a BMC Remedy ITSM user enters data in the Task Summary, instructing network engineering to provision a server onto the network and the Network Task is saved, an application server is assigned.

If the system only has a single application server registered, the assignment is made automatically. When multiple application servers are registered, a list is displayed to allow the BMC Remedy ITSM user to select the application server for which to implement the change request.

See Facilitating and documenting BMC Remedy Service Desk-initiated changes.

BMC Remedy Server integration artifacts

This section documents the BMC Remedy artifacts that are specifically applicable when deploying multiple application servers in your environment. For more information, see BMC Remedy server integration artifacts.

BMC Remedy Administrator workflow objects

• INT:BCAN:TMS:MultiSiteUpdate
• INT:BCAN:CHG:ApprovalNotification
• NT:BCAN:TMS:UpdateServerFromCAI

Federated links

Federated links are supported only when a single application server is deployed. If you have multiple servers, delete the BMC.CORE.CONFIG.BMC_Federated… objects to avoid launching Federated links to the wrong server.