Use the following checklist while installing and configuring BMC Atrium Single Sign-On. If needed, you may also print the form.
Tick when done
|Installation (including deployment of the agent) was successful.|
|BMC Remedy Mid Tier/BMC Remedy AR System functions without BMC Atrium Single Sign-On.|
|The latest patch has been applied for BMC Atrium Single Sign-On/BMC Remedy Mid Tier.|
|(High-availability environment) There are no firewalls between the different nodes.|
(High-availability environment) Hostname-to-IP-address-to-hostname is in synch. To test, use the nslookup host name and nslookup IP address from the different nodes.
|You can access the BMC Atrium Single Sign-On Admin Console.|
|BMC Remedy Mid Tier/BMC Atrium Single Sign-On/BMC Remedy AR System is configured properly.|
|Area plug-ins are configured properly.|
|All servers share the same cookie domain and are configured using fully qualified domain names (FQDNs).|
You have logged on to the BMC Atrium Single Sign-On Admin Console and confirmed that the cookie names are stored in both of the following places, and that the cookie names are the same in both places:
There are three FQDN mappings (one for localhost, one for 127.0.0.1, and one for the short name of the host) at the following location:
Access Control > Top Level Realm > Agents > J2ee. Click the agent, and then click Fully Qualified Domain.
|You have checked the ARSystem\Arserver\Db\arjavaplugin.log file in BMC Atrium Single Sign-On for initialization errors and fixed any errors you encountered. (To locate errors, search the log file for ATRIUMSSO.)|
You have defined a data store in BMC Atrium Single Sign-On to check whether LDAP/AD/AR authentication is working. After defining the data store, you have viewed the users defined in the system in the BMC Atrium Single Sign-On Admin console. This will help you debug the connection information.