Migrating from BMC Atrium Single Sign-On to Remedy Single Sign-On

Task 1: Install Remedy SSO

Install Remedy SSO.

The Remedy SSO installer performs the following activities:

• Deploys the Remedy SSO web application on the existing Apache Tomcat web server.
• Creates the Remedy SSO database on the specified RDBMS and provisions this database with the essential data.

 For information about how to install Remedy SSO, see Install Remedy SSO.

Task 2: Integrate Remedy AR System with Remedy SSO

Perform the following steps to integrate Remedy AR System with Remedy SSO:

1. Unintegrate Remedy AR System from Atrium Single Sign-On.
   1. Stop Remedy AR System.
   2. Create a system backup. 

   3. In arsystem/conf/ar.cfg, remove the following entries:

      Atrium-SSO-Location
      Atrium-SSO-Admin-User
      Atrium-SSO-Admin-Password

   4. In arsystem/pluginsvr/pluginsvr_config.xml, remove the plugin entries.

      Example

      !-- Atrium SSO AREA Plug-in -->
      <plugin>
      
      </plugin>
   5. From the pluginsvr directory, back up the following files.
      • bcprov-jdk15-145.jar
      • json.jar
      • simple-xml-2.5.3.jar
      • stax-1.2.0.jar
      • stax-api-1.0.1.jar
      • atsso-sdk.jar
      • atsso-common.jar
      • bcprov-jdk15-145.jar
      • json.jar
      • simple-xml-2.5.3.jar
      • stax-1.2.0.jar
      • stax-api-1.0.1.jar
        
   6. Make sure that the pluginsvr_config.xml file does not contain any references of the files that you backed up.
   7. Delete the files that you backed up.
   8. Restart the Remedy AR System.
2. Integrate Remedy SSO with BMC Remedy AR System.

Task 3: Integrate Remedy Mid Tier with Remedy SSO

Perform the following steps to integrate Remedy Mid Tier with Remedy SSO:

1. Unintegrate Remedy Mid Tier from Atrium Single Sign-On.
   1. Stop Remedy Mid Tier.
   2. Take a backup of the atssoAgents folder under Apache Tomcat, and then delete the original atssoAgents folder.
   3. In the Midtier/WEB-INF/classes/config.properties, comment out the line that starts with arsystem.authenticator.

   4. In the Midtier/WEB-INF/web.xml, make sure there are no references to Atrium SSO, and remove the following filter definition and filter mapping definitions:
      
      

      <!--Atrium SSO webagent filter. Un-comment when needed→
      <!–
      <filter-name>Agent</filter-name>
      <filter-class>com.bmc.atrium.sso.agents.web.SSOFilter</filter-class>
      </filter>→
      <!--Atrium SSO webagent filter. Un-comment when needed-->
      <!--<filter-mapping>
      <filter-name>Agent</filter-name>
      <url-pattern>/*</url-pattern>
      <dispatcher>REQUEST</dispatcher>
      <dispatcher>INCLUDE</dispatcher>
      <dispatcher>FORWARD</dispatcher>
      <dispatcher>ERROR</dispatcher>
      </filter-mapping>-->
   5. In the Midtier/WEB-INF/lib folder, take a backup of the following files and then delete them:
      
      • atsso-common.jar
      • atsso-sdk.jar
      • bcprov-jdk15-145.jar
      • json.jar
      • simple-xml-*.jar
      • stax-1.2.0.jar
      • stax-api-1.0.1.jar
      • webagent.jar
2. Integrate BMC Remedy Mid Tier with Remedy SSO.

Task 4: Configure Remedy SSO for authentication

For information about how to configure Remedy SSO for authentication, see Configure Remedy SSO for authentication.