This documentation supports the 9.0 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.

Resolving BMC Atrium Single Sign-On installation issues

You may encounter the following errors when you integrate BMC Remedy Mid Tier with BMC Atrium Single Sign-On after installing BMC Atrium Single Sign-On.

Container validation error

Error: SEVERE,com.bmc.install.product.atriumsso.integration.ar.installer.validator.
     AtriumSsoIntegrationMtContainerTypeValidationTask;


Resolution:

  1. Open the server.xml file present in the tomcat conf directory in BMC Remedy Mid Tier.
  2. Add protocol="HTTP/1.1" to the server.xml file.
<Connector URIEncoding="UTF-8" acceptCount="250" connectionTimeout="90000"
               protocol="HTTP/1.1" 
                 disableUploadTimeout="true"
                 enableLookups="false"
                 maxHttpHeaderSize="8192"
                 maxKeepAliveRequests="-1"
                 maxThreads="300"
                 minSpareThreads="50"
                 port="8080"
                 redirectPort="443"/>

Note

Delete the assoagents directory present in the tomcat directory in BMC Remedy Mid Tier, if BMC Atrium Single Sign-On is not installed on the same server.

Mid Tier not reachable error

Error: BMC Remedy Mid Tier server is not reachable; Enter a valid URL;

Resolution:

  1. Open the arsys.xml file present in the Catalina directory.
  2. Add path="/arsys" to the arsys.xml file and restart the Tomcat.
<?xml version="1.0" encoding="ISO-8859-1"?>
<!--
    Context configuration file for the Tomcat Manager Web App

    $Id: manager.xml 303123 2004-08-26 17:03:35Z remm $

--><!-- http://tomcat.apache.org/tomcat-5.5-doc/config/context.html --><Context deployOnStartup="true" docBase="D:\BMCSoftware\ARMidtier\midtier"
         path="/arsys"
         reloadable="false"
         sessionCookiePathUsesTrailingSlash="false">
         <!-- reloadable will disable session persistance across shutdown/startup and sessionCookiePathUsesTrailingSlash is set to prevent creating of a duplicate JSESSIONID in Tomcat 7 because of enabling HTTPOnly cookie for JSessionID -->
         <Manager pathname=""/>
</Context>
Was this page helpful? Yes No Submitting... Thank you

Comments