Running the BMC Atrium Single Sign-On Installer on BMC Remedy Mid Tier

To integrate BMC Remedy Mid Tier with the BMC Atrium Single Sign-On, you must run the BMC Atrium Single Sign-On installer on the computer on which the BMC Remedy Mid Tier is installed.

Important

The BMC Atrium Single Sign-On version 9.0 installer can only be used for integration with BMC Remedy Mid Tier installed on Microsoft Windows and RedHat Linux platforms. Use the SSOMidTierIntegration utility for integrating with BMC Remedy Mid Tier server installed on other platforms. For more information, see Running the SSOMidTierIntegration utility on the AR System server.

Before you begin

Before you integrate BMC Atrium Single Sign-On with BMC Remedy Mid Tier, ensure that the following conditions are met:

  • The BMC Atrium Single Sign-On server and BMC Remedy AR System server are running.
  • The BMC Remedy AR System server is integrated with the BMC Atrium Single Sign-On server.
  • You are running the BMC Atrium Single Sign-On installer on the same computer on which the BMC Remedy Mid Tier is installed.
  • If you want the common installer to start and stop the Tomcat server with the tomcat scripts, it should not be registered as a Windows service. When Apache Tomcat server is registered as a Microsoft Windows service, the installer will use the Windows service to control the Tomcat server in preference to the start/stop scripts.

Note

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 BMC Atrium Single Sign-On Installer on BMC Remedy Mid Tier

  1. Unzip the BMC Atrium Single Sign-On files.
  2. Run the installation program.
    The setup executable is located in the Disk1 directory of the extracted files:
    • (Microsoft Windows) Run setup.exe.
    • (UNIX) Run setup.sh (which automatically detects the appropriate subscript to execute).
  3. In the lower-right corner of the Welcome panel, click Next.
  4. Review the license agreement, click I agree to the terms of the license agreement, and then click Next.

    BMC Atrium Single Sign-On installer

  5. Select the Integrate with BMC Remedy Mid Tier check box.
  6. Accept the default destination directory or browse to select a different directory, and then click Next.
  7. Enter BMC Remedy AR System integration parameters such as the AR System server name, user, password, and port number.
  8. Verify that the server name is the fully qualified domain name (FQDN) and that the user name is valid, and then click Next.
  9. Enter the path to the mid tier container directory. For example, SP engine home.

    Note

    Ensure that you have either Apache Tomcat 6 or 7 installed. For this release, the other servers are not supported.

  10. Click Next.
  11. Enter the mid tier or load balancer FQDN, and click Next.

    Note

    If you have entered the load balancer FQDN, you must select the Is BMC Remedy Mid Tier behind load balancer check box.




  12. (Optional) Enter the truststore file path and password, and click Next.
  13. Enter the path of the mid tier installation directory, and click Next.
  14. Select the appropriate BMC agent (realm) name to integrate with the mid tier, and click Next.
  15. In the Installation Preview screen, click Install to perform integration with the mid tier.
  16. After the integration is complete, restart the mid tier.

Note

Run the installer on all the mid tier servers, if you have deployed BMC Remedy Mid Tier in HA load balancing environment.

Adjusting the timeout values

After the integration of BMC Atrium Single Sign-On with BMC Remedy Mid Tier is completed, BMC recommends that you adjust the timeout values of the BMC Atrium Single Sign-On sessions to work with the settings of the BMC Remedy Mid Tier. For more information on timeout values, see Server Configuration Parameters.

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

Comments

  1. Matthew Brown

    I am integrating Atrium SSO 9.0 with Midtier 8.1.02. Step 9 never occurs during my installation and I am not allowed to enter Atrium SSO credentials or location. Does anyone have an idea why this might be happening? It skips the step entirely and then errors out of the installation with "The credentials provided for BMC Atrium SSO are not valid."

    Sep 23, 2014 12:50
    1. Abhay Chokshi

      Thank you for your comment, Matthew.

      The step was outdated and I have removed it from the process. However, the verification for the BMC Atrium Single Sign-On password happen based on the value that you have entered while integrating BMC Remedy AR System. 

      You might be facing this error due to the change in amadmin user's password from BMC Atrium SSO Admin Console after integration with BMC Remedy AR System.

      Please try reintegration of BMC Atrium Single Sign-On with BMC Remedy AR System as mentioned in Running the BMC Atrium Single Sign-On Installer on AR System server.

       Thanks!

      -Abhay

      Sep 24, 2014 08:34
    1. Abhay Chokshi

      Hi Matthew,

      Alternatively, you can also change the password from the Atrium SSO Integration tab in Mid Tier. For more information, see https://docs.bmc.com/docs/display/public/ars81/Configuring+the+connection+to+the+BMC+Atrium+SSO+integration.

      Thanks!

      -Abhay

       

      Sep 25, 2014 02:13
      1. Matthew Brown

        Hello, thank you for the responses. I attempted to rerun the integration executable on the AR System and suprisingly, it also said the credentials were not valid. (This installer ran without errors the first time and completed integration) I then managed the SSO tab as you suggested in the 2nd comment. I verified the URL and password, then reran the integration tool (on both servers, AR system first). It still complains that the credentials are incorrect.

        Sep 25, 2014 07:05
        1. Abhay Chokshi

          Thank you for your update, Matthew.

          The concerned SME is looking into this issue and I will get back to you as soon as possible. Meanwhile, if you want to contact Customer Support to log a formal ticket on this issue, click here.

          Thanks!

          -Abhay

          Sep 26, 2014 03:48
  2. Marcel Martins

    Is there any walkthrough to install on Websphere?

     

     

    Sep 24, 2014 03:30
    1. Abhay Chokshi

      Hi Marcel,

      Please find the topic for reviewing the integration steps required on Websphere server. For information, see  Mid Tier integration when deployed on Websphere.

      Thanks!

      -Abhay

      Sep 26, 2014 03:33
  3. Martin Penev

    Hello,

    If I have two (or more) mid-tiers behind a load balancer, should I run the SSO installer on every mid-tier or it is enough to run it on only one of them?

    Thanks,

    Martin

    Oct 10, 2014 02:47
    1. Abhay Chokshi

      Hi Martin,

      Thank you for your comment. I have updated the documentation with a note stating that you must run the installer on each mid tier, if you have deployed mid tier in HA cluster.

      For information about end-to-end installation and integration steps in HA environment, refer to the following topic: End-to-end integration steps in HA environment.

      Thanks!

      -Abhay

      Oct 10, 2014 03:49
      1. Martin Penev

        Abhay,

        Thanks for your quick reply!

        Regards,

        Martin

        Oct 10, 2014 07:39
  4. Martin Penev

    Hello,

    When I enter the Host FQDN in step 11 and I click the "Next" button, I get the following error message: "BMC Remedy Mid Tier server is not reachable. Enter a valid URL. Server should be up and running."

    Why is the error message asking me to enter a valid URL when the previous step of the installer instructed me to enter a Host FQDN?

    Thanks,

    Martin

    Oct 13, 2014 02:00
    1. Abhay Chokshi

      Hi Martin,

      This is an open issue and has a workaround for completing the integration. Please check the defect, SW00473767 on the Known and Corrected Issues page.

      We will try to resolve this issue soon.

      Thank you for providing this information!

      -Abhay

      Oct 14, 2014 07:56
      1. Martin Penev

        Hi Abhay,

        Thanks for the suggested workaround but for me it was easier to run the integration utility manually.

        Regards,

        Martin

        Oct 14, 2014 09:00
  5. John Grunder

    Step 9 is very unclear to me.  What is SP Engine home?  Can you add examples, especially given the qualification then provided that only Tomcat 6 and 7 are supported?

    Mar 04, 2015 07:38
    1. Martin Penev

      Hi John,

       

      In step 9 you should enter the path to the Tomcat installation directory. For example:

      C:\Program Files\Apache Software Foundation\Tomcat7.0

       

      If you use other types of web server, please see the page below. These are the steps that you need to perform in order to deploy the agent manually:

      https://docs.bmc.com/docs/display/public/sso90/Running+the+SSOMidtierIntegration+utility+on+the+Mid+Tier

       

      Best Regards,

      Martin

      Mar 05, 2015 12:30
      1. Kamalakannan Srinivasan

        Hi Martin,

        Thanks.

        Regards,

        Kamal

         

        Mar 06, 2015 07:31
  6. Sameer Al omari

    hello team

    i have 2 concerns i really hope to clarify  

    1- step # 11 , if i have 2 mid tiers behind loade balancer and i provide the host name rather than LB name without check " Is BMC Remedy Mid Tier behind load balancer" check box is this OK? because if i provide the LB URL on first integration it will notify me in the second installation that this LB is already integrated! and suppose that i provide the host name rather than LB name( if  this alllicable) , the installer will ask for LB information later during the installation ??


    2 - if i changed the LB name of the midtiers after the integration with Mid tiers , how can i  reflect the changes on SSO side , shall i run the installer on MT again ?

    thank you 

    Oct 15, 2015 08:56
    1. Kamalakannan Srinivasan

      Hi Sameer,

      Thank you for your comment. I will discuss with the technical team and then keep you informed.

      Regards,

      Kamal

       

      Oct 15, 2015 11:41
      1. Sameer Al omari

        Hi Kamal

        did you get a chance to help on this please ?

        thank you

        Oct 21, 2015 06:00
        1. Kamalakannan Srinivasan

          Hi Sameer,

          I will keep you informed as soon as possible.

          Regards,

          Kamal

          Oct 23, 2015 12:36
    1. Kamalakannan Srinivasan

      Hi Sameer,

      Thank you for your comment. Please find below the responses.

      1. In this case, specify the actual node name as the name of the BMC Mid Tier load balancer name. Later after the completion of the integration, manually change the <webapp> value to the BMC Mid Tier load balancer value in the agent’s config file. The agent's config file is available at <MT Tomcat>\atssoAgents\atsso.cfg.xml.

        You may want to refer the Agent manager topic for further information.

      2. You may have to repeat the same process as specified for the first item. But if the load balancer is completely changed, i.e. not just its name, then BMC Atrium Single Sign-On needs to be re-integrated with BMC Remedy Mid Tier. You also have to reset the certificates. Please refer

        https://docs.bmc.com/docs/display/public/sso90/Manually+configuring+mid+tier+for+BMC+Atrium+Single+Sign-On+user+authentication

      Regards,

      Kamal

       

      Oct 26, 2015 12:18
  7. Mahendra Mahalkar

    Hi,

    The document and replies to the comment are very nice. I have a query. I am having a MT LB with actual host name as "srvmtp.dubairealestate.gov" and an alias for it as "sanad.wasl.ae". I tried to integrate with LB URL with alias https://sanad.wasl.ae/arsys (Before SSO integration with midtier this LB alias url is accessible).  I provide the host name of MT1 / MT2 with checking " Is BMC Remedy Mid Tier behind load balancer" check box and later in LB URL i entered alias URL https://sanad.wasl.ae/arsys. The installer goes find but user could not login later. Can I integrate LB with an alias rather than its hostname? Please suggest. I expect end result as https://sanad.wasl.ae/arsys/forms/...

    Aug 12, 2016 02:40
    1. Kamalakannan Srinivasan

      Hi Mahendra,

      Thank you for your comment. I discussed your query with the technical team. They suggest that you raise a help ticket with BMC Support.

      Regards,
      Kamal

      Jun 12, 2017 11:54