End-to-end integration steps in HA environment
This topic provides a high-level overview for installing and configuring BMC Remedy AR System, BMC Remedy Mid Tier in a High Availability (HA) load-balancing, server-group environment with BMC Atrium Single Sign-On.
The following topics are provided:
ITSM integration architecture in an HA load-balancing environment (when integrated with BMC Atrium SSO)
Installing and configuring BMC Remedy AR System
Follow the steps for installing and configuring BMC Remedy Action Request (AR) System and BMC Remedy Mid Tier on multiple servers in an HA environment.
Before you begin
- Create a list of all load balancers, AR System servers, mid-tier servers, and BMC Atrium Single Sign-On servers and their IP addresses, along with the accepted fully qualified domain names (FQDNs), in a text file. You can refer to the ITSM architecture provided in this topic.
- Create a comprehensive list of all of the following items in a text file:
- Load balancers
- AR System servers
- BMC Remedy Mid Tier servers
- BMC Atrium Single Sign-On servers and their IP addresses along with their accepted FQDNs
You can refer to the ITSM architecture provided in this topic. For more information, see Planning-where-software-is-installed-in-server-groups.
Setting up your load balancer
A load balancer is a valuable component in building a scalable, highly available BMC Remedy AR System infrastructure. Scalability is achieved through the ability to add BMC Remedy AR System servers as demand and workload increase. For more information about setting up a load balancer, see Configuring-a-hardware-load-balancer-with-BMC-Remedy-AR-System.
To set up your load balancer
- Configure the AR System server load balancer with all of the servers in the server group. For more information, see Load-balancer-configuration-examples.
- Configure the BMC Remedy Mid Tier load balancer.
- Configure the SSO server load balancer. For more information, see Installing-BMC-Atrium-Single-Sign-On-as-a-High-Availability-cluster.
Installing the server group
The following list describes the list of tasks required to install a server group for BMC Remedy AR System, BMC Atrium Core, and other BMC products. For more information, see Installing-a-server-group.
- Installing-the-first-AR-System-server.
- Installing the first mid tier server.
- Obtaining BMC Remedy license keys.
- (Optional) Testing-the-mid-tier-in-your-server-group.
This step is used for testing the installation of the first AR System server. - Configuring-the-first-server-to-be-a-server-group-member.
- Testing the first server to confirm that it is working properly.
- Installing-the-next-AR-System-server-in-the-server-group.
- Configuring-the-next-server-for-the-server-group.
- Configuring the mid tier to include all AR System servers that you have installed.
- Testing the current server to confirm that it is working properly.
Use the AR System Server Group Operation Ranking form to distribute the load between the AR System servers and the load balancer.
- Configuring the mid tier to use the AR System server load balancer.
Remove the first AR System from the mid tier and add the name of the virtual host of the AR System server load balancer (for example, remedyssoservergroup). - Logging on to the BMC Remedy Mid Tier
Make sure that the mid tier resolves to the AR System server load balancer.
For example, you should be able to access the BMC Remedy AR System Administration Console. - Installing the remaining BMC Remedy Mid Tier servers for your environment.
- Configuring the Mid Tier load balancer with all of the Mid Tiers in the server group.
When you log on to the Mid Tier load balancer, it should resolve to the AR System server load balancer URL.
Installing and configuring BMC Atrium Single Sign-On
BMC Atrium Single Sign-On is the first authentication step for BMC Remedy AR System.
- Running-the-BMC-Atrium-Single-Sign-On-Installer-on-AR-System-server — Perform the BMC Atrium Single Sign-On integration with the AR System servers for each server in a cluster.
- Reviewing-AR-System-server-external-authentication-settings-and-configuring-group-mapping — Before you configure BMC Atrium Single Sign-On, you must configure group mapping for external authentication in each BMC Remedy AR System server in a cluster.
- Running-the-BMC-Atrium-Single-Sign-On-Installer-on-BMC-Remedy-Mid-Tier — After you integrate BMC Atrium Single Sign-On with the computers on which the AR System server is installed, you must integrate BMC Atrium Single Sign-On with each server where mid tier is installed. Configure the SSO AREA plug-in with a Java plug-in entry, along with other external authentication parameters.
- (Optional) Enabling multi-tenancy support — Set the value of the allow.tenant.admin and allow.multiple.realms parameters to true in the web.xml file.
- (Optional) Adding a tenant realm on the Realms panel — Add a new realm in BMC Atrium SSO so that single sign-on is seamlessly available for the new tenant. To add realms to a BMC Atrium SSO server, use the Realms panel in the BMC Atrium SSO Admin Console.
- Editing the realm — Set the Realm Authentication, Federation, or User Stores configuration values by using the tabs on the Realm Editor form. The new realm does not contain these values, which are necessary for authentication.
Mapping-realm-URLs-to-an-agent-for-multiple-realms — You must map the realm URLs on the Agent Editor console for successful authentication with BMC Atrium SSO. This mapping helps the BMC Atrium SSO server to identify requests coming from different realms and tenants.
- Configuring BMC Atrium Single Sign-On settings for AR System — Perform this step in conjunction with the AR Data Store to retrieve group information and other user attributes from the AR System server for each realm.
- (Optional) Running-a-health-check-on-the-BMC-Atrium-Single-Sign-On-installation — After you complete all of the steps, run a health check on your integration of BMC Atrium Single Sign-On with each mid tier.