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 SSOMidtierIntegration utility on the Mid Tier

After you ran SSOARIntegration utility on the computer where the AR System server is installed, you must now run the SSOMidtierIntegration utility on the computer where the Mid Tier is installed.

Note

When BMC Remedy Mid Tier is deployed in cluster environment, you must run the SSOMidtierIntegration utility on the all the computers where the Mid Tier is installed.

This topic contains the following information:

Before you begin

  • Make sure that Oracle JRE 1.6.0_23 or higher is installed.

  • Before you begin, perform the BMC Atrium Single Sign-On and AR System server integration.

  • If the Mid Tier web server is not Tomcat or JBoss, verify the Mid Tier URL before passing it as an input; you cannot verify it later when the web server is shut down.

  • If you have enabled FIPS-140 mode in BMC Atrium Single Sign-On, you must install the FIPS encryption on mid tier server before running the SSOARIntegration utility.

Important

If you have installed BMC Remedy Mid Tier on a Websphere server, you must run the deployer command manually on that server for integration. For more information, see Integrating BMC Atrium Single Sign-On with Mid Tier deployed on Websphere,

To run the SSOMidtierIntegration utility to integrate Single Sign-On and the Mid Tier

  1. On the computer where the Mid Tier is installed, navigate to the <MidTierInstall>\AtriumSSOIntegrationUtility directory.
    For example, navigate to C:\Program Files\BMC Software\ARSystem\midtier\AtriumSSOIntegrationUtility.
  2. Open the midtierintegration.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

    • If BMC Remedy Mid Tier is deployed with a mid tier load balancer, you must add the --web-app-url and --notify-url URLs in the following text file. In this case, add the mid tier load balancer URL in the --web-app-url parameter and add the mid tier URL in the --notify-url parameter.
    • When you have a single mid tier, do not use the --notify-url parameter. Add the mid tier URL in the --web-app-url.
    # Install mode, it accepts values as "Install" or "Uninstall" and it is case insensitive.
    # Provide "Install", if you want to install the agent. Provide "Uninstall", if you want to Uninstall the Agent.
    --install-mode=Install
    
    #AR Server Name, Provide the AR server name.
    --ar-server-name=ARServerName
    
    #AR Server User, Provide the AR server user.
    --ar-server-user=ARServerUser
    
    #AR Server Password, Provide the AR server password.
    --ar-server-password=ARServerPassword
    
    #AR Server Port, Provide the AR server port.
    --ar-server-port=ARServerPort
    
    # Container Type, Type of webserver being used to host midtier
    --container-type=TOMCATV6
    # Supported contain types include JBOSSV4, JBOSSV5, SERVLETEXECV5, SERVLETEXECV6,
    # TOMCATV5, TOMCATV6, TOMCATV7, WEBSPHEREV6, WEBSPHEREV7, WEBSPHEREV8, WEBLOGICV10, WEBLOGICV11
    
    #Web App URL, Provide the midtier URL in case load balancer is not there otherwise provide the load balancer url, 
    #and make sure the server name is provided with fully qualified domain name and port is also provided in the URL.
    #--web-app-url=MidtierURL or LoadBalancerURL
    --web-app-url=http://midtier-or-loadbalancer.bmc.com:8080/arsys
    
    #Container Base Directory, Provide the webserver home directory.
    --container-base-dir=C:\Program Files\Apache Software Foundation\Tomcat6.0
    
    #JRE Path, Provide the path to the JRE home and make sure that you haven't provided till "bin".
    --jre-path=C:\Program Files\Java\jre7
    
    #Midtier Home, Midtier Home Directory
    --midtier-home=C:\Program Files\BMC Software\ARSystem\midtier
    
    #Midtier URL, Provide the midtier URL here in case mid tier load balancer is being used.
    #Remove # to uncomment and use the below property.
    #--notify-url=http://midtier.bmc.com:8080/arsys
    
    #The Atrium SSO realm that this agent will use for user authentication. Default is /BmcRealm.
    #Remove # to uncomment and use the below property.
    #--agent-realm=/BmcRealm
    
    #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 done already in case, webserver is other then tomcat or jboss.
    #Remove # to uncomment and use the below property.
    #--force=<Yes or No>
    
    #Server Instance Name, Provide the name of Websphere instance name being used. It is required only in case Websphere being used to host the midtier.
    #Remove # to uncomment and use the below property.
    #--server-instance-name=WebSphere server instance name
    
    #Server Instance Name, Provide the path to the Websphere instance configuration directory. It is required only in case Websphere being used to host the midtier.
    #Remove # to uncomment and use the below property.
    #--instance-config-directory=WebSphere server instance configuration directory
    
    #Weblogic Domain Name, Provide the Weblogic domain name. It is required only in case WebLogic being used to host the midtier.
    #Remove # to uncomment and use the below property.
    #--weblogic-domain-home=Domain Name

    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 BMC Atrium SSO URL parameters are required.
    • If necessary, you can run the SSOMidtierIntegration utility multiple times, for example, to install or uninstall the integration (depending on the install-mode setting in the midtierintegration.txt file). The utility checks if an agent exists from a previous installation. If an agent exists, the utility uninstalls it and then re-installs a new agent.
    • Review the optional inputs carefully for your environment.
  3. Save your changes to midtierintegration.txt.
  4. At the command prompt or shell window, navigate to the <MidTierInstall>\AtriumSSOIntegrationUtility directory.
  5. Enter the following jar command at the command prompt:

    java -jar SSOMidtierIntegration.jar --inputfile midtierintegration.txt
  6. Manually shut down the web server if you are prompted by the utility.

    Note

    The utility automatically shuts down Tomcat and JBoss. 

  7. When execution is successfully completed, open the BMC Atrium SSO Admin console.
    The URL to open the BMC Atrium SSO Admin console is:
    https://<ssoServer>.<domain>:<port>/atriumsso
    For example:
    https://ssoServer.bmc.com:8443/atriumsso/atsso

    Note

    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.

  8. When you are prompted that you are connecting to an insecure or untrusted connection, add the exception and then continue.
  9. Under Agents List, verify that the agent was created.
    For example, /arsys@MidTier.labs.bmc.com:8080 should be present.

Reverse proxy URLs

Important

  • Before you pass the reverse proxy URL as input in the utility command, make sure that you can log on to the application using the reverse proxy URL from the Mid-Tier computer where the command is run.
  • If the reverse proxy server and the Mid Tier are installed on the same computer, stop the reverse proxy server before you run the SSOMidtierIntegration utility with the Mid Tier. When the utility completes its operation, restart the reverse proxy server.

If you must use reverse proxy URLs to run the Mid-Tier integration with the SSOMidtierIntegration utility, the utility works with or without ports in the --web-app-url parameter.

Where to go from here

  1. Configure BMC Atrium Single Sign-On for AR authentication and set up users and groups.

    Note

    If you do not plan to use BMC Atrium Single Sign-On AR authentication and plan to use different authentication methods, see Configuring after installation.

  2. Run a health check on the BMC Atrium Single Sign-On installation.
Was this page helpful? Yes No Submitting... Thank you

Comments