Out of support This documentation supports the 8.1 version of BMC Atrium Single Sign-On, which is in "End of Version Support." However, the documentation is available for your convenience. You will not be able to leave comments.Click here to view the documentation for a supported version of Remedy Single Sign-On.

Running the SSOARIntegration utility on the AR System server

Performing the Single Sign-On integration with the BMC Remedy AR System server and the BMC Remedy Mid Tier is a two-step sequence:

  1. Run the SSOARIntegration utility on the computer where the AR System server is installed (this procedure).
  2. Run the SSOMidtierIntegration utility on the computer where the Mid Tier is installed.

Before you begin

  • Make sure that Oracle JRE 1.6.0_23 or higher is installed on the AR System server.
  • If you have enabled FIPS-140 mode in BMC Atrium Single Sign-On, you must install the FIPS encryption on AR System server before running the SSOARIntegration utility. For more information, see Configuring-FIPS-140-mode
  • If you are running the AR System web services with a proxy server, you must configure your AR System server for a proxy server. For more information, see Configuring-AR-System-server-for-a-proxy-server.

To run the SSOARIntegration utility to integrate Single Sign-On and the AR System server

  1. On the computer where the AR System server is installed, navigate to the <ARSystemServerInstall>\artools\AtriumSSOIntegrationUtility directory.
     For example, navigate to C:\Program Files\BMC Software\ARSystem\artools\AtriumSSOIntegrationUtility.

  2. Open the arintegration.txt file and update the parameters for your environment.
    For example, you can enter the supported container types such as Tomcat 6, JBOSS v4, and so on.

    Tip

    When you are using a BMC Atrium SSO load balancer, you must add the load balancer URL in the --atrium-sso-url parameter instead of adding the server URL.

    #AR Server Name, Provide the AR server name.
    --ar-server-name=arsystemserver.bmc.com


    #AR Server User, Provide the AR server user.
    --ar-server-user=Demo

    #AR Server Password, Provide the AR server password.
    --ar-server-password=Demo

    #AR Server Port, Provide the AR server port.
    --ar-server-port=0

    #Atrium SSO URL, Provide the Atrium SSO URL
    #and and make sure the server name is
    #provided with fully qualified domain name
    #and port is also provided in the URL.
    --atrium-sso-url=https://ssoserver.bmc.com:8443/atriumsso

    #Atrium SSO Admin Name
    --admin-name=amadmin

    #Atrium SSO Password
    --admin-pwd=ssoadminpassword

    #TrustStore Path, Path to the truststore directory.
    #This is an optional parameter.
    #Remove # to uncomment and use the below property.
    #--truststore=truststorepath | Optional parameter.

    #TrustStore Password. This is an optional parameter.
    #Remove # to uncomment and use the below property.
    #--truststore-password=truststorepassword | Optional parameter.
            
    #force option, It accepts values as "Yes" or "No" where default is "No".
    #If "Yes" is provided then utility will not wait
    #for user to shutdown the webserver, if not shutdown already.  
    #This is true in case, where webserver is other then tomcat or jboss.
    #Remove # to uncomment and use the below property.
    #--force=<Yes or No>

    Note

    • Blank passwords are not supported. Your AR System server user must have a password before you run this utility.
    • Fully-qualified domain names for the AR System server and Atrium SSO URL parameters are required.
    • The --truststore=truststorepath and --truststore-password=truststorepassword parameters are optional when integrating Single Sign-On and the AR System server. The #TrustStore Path is the local java truststore path and the value is used for providing the path of the certificate. This value is added automatically by the SSOARIntegration utility using the local java truststore.
    • The --force=Yes or No parameter is optional. If you pass this input, you are not prompted for any manual inputs to restart the AR System server and the server is started automatically. Otherwise, you are prompted to restart the AR System server.
    • Review the optional inputs carefully for your environment.
  3. Open a command window and navigate to the <ARSystemServerInstall>\artools\AtriumSSOIntegrationUtility directory.

  4. Enter the following command:

    java -jar SSOARIntegration.jar --inputfile arintegration.txt

    Note

    If you have enabled FIPS-140 mode in BMC Atrium SSO and BMC Remedy AR System, you must run the following integration command using -Datsso.sdk.in.fips140.mode=true parameter.
    For more information about enabling FIPS-140 mode, see Configuring-FIPS-140-mode

    java -jar SSOARIntegration.jar -Datsso.sdk.in.fips140.mode=true --inputfile arintegration.txt

  5. When prompted by the utility, restart the AR System server.

  7. When execution is successfully completed, run the SSOMidtierIntegration utility on the Mid Tier.

     

    Info

    To troubleshoot installation failures, or for information about log files or configurations performed by the SSOMidtierIntegration utility, see Troubleshooting AR System server and Mid Tier integrations.

Where to go from here

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*