This documentation supports the 9.0 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

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

The following table provides the steps for migrating from BMC Atrium Single Sign-On to BMC Remedy Single Sign-On.

StepActionAdditional information
1.

Install BMC Remedy Single Sign-On

BMC Remedy Single Sign-On installer does the following:

  1. Deploys the 'rsso' web application on the existing Apache Tomcat web server.
  2. Creates the 'rsso' database on the specified RDBMS and provisions this database with the essential data.
2.

Configuring BMC Remedy Single Sign-On

BMC Remedy Single Sign-On can be configured to process end user's authentication against AR and SAML v2 user stores.

3.Integrate BMC Remedy AR System with BMC Remedy Single Sign-On

Perform the following steps to integrate BMC Remedy AR System with BMC Remedy Single Sign-On.

  1. Unintegrate BMC Remedy AR System from BMC Atrium Single Sign-On.
    1. Stop BMC Remedy AR System.
    2. Modify and save the following files.
      Note: Take a backup prior to modifying the files.

      File

      Modifications

      ar.cfg (arsystem/conf folder)

      Remove the following entries:

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

      pluginsvr_config.xml (arsystem/pluginsvr)

      Remove the plugin entries.

      For example,

      • !-- Atrium SSO AREA Plug-in -->
      • <plugin>
      • </plugin>
    3. In the pluginsvr folder take the backup of following files and then delete them.

      Note

      The following files can be deleted only if there are no more references in pluginsvr_config.xml:

      • 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

        d.Restart the BMC Remedy AR System.

2. Integrate BMC Remedy Single Sign-On with BMC Remedy AR System.

4.Integrate BMC Remedy Mid Tier with BMC Remedy Single Sign-On

Perform the following steps to integrate BMC Remedy Mid Tier with BMC Remedy Single Sign-On.

  1. Unintegrate BMC Remedy Mid Tier from BMC Atrium Single Sign-On.
    1. Stop BMC Remedy Mid Tier.
    2. Take a backup of the “atssoAgents” folder under apache/tomcat.. and then delete it.
    3. Modify and save the following files.

Note: Take a backup prior to modifying the files.

File

Modifications

config.properties

(Midtier/WEB-INF/classes/)

Comment the line that starts with:

arsystem.authenticator

web.xml

(Midtier/WEB-INF/)

Remove the following filter definition and filter mapping definitions

  • <!--Atrium SSO webagent filter. Un-comment when needed-->
  • <!--<filter>
    • <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>-->

Note: Make sure that there are no references to ASSO in this file.

d. In the Midtier/WEB-INF/lib folder, take a backup of 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 BMC Remedy Single Sign-On.

Related topics

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Julio Goncalves

    The instructions on step 3 need to be reviewed.

    Deleting the file json.jar from the plugin directory also breaks other plugins.

    Please correct the page appropriately.

    Jul 24, 2016 10:19