Rational Connector for SAP Solution Manager 4.0.0.1

Product Release / Trial | May 14, 2013
This is not the most recent version. We recommend Rational Connector for SAP Solution Manager 4.0.0.8 . This is made available for archival purposes and may contain bugs and/or security vulnerabilities. If you do download this version, it is being provided AS IS, without warranties of any kind, including the implied warranties of merchantability and fitness for a particular purpose. We strongly advise you review the support pages for this version and update the product or take actions recommended therein. Security bulletins contain instructions for the security vulnerability addressed therein, and may require upgrading to a newer version. Link to security vulnerability blog: IBM PSIRT blog.

The downloads for this milestone are no longer available.

Upgrading to Rational Connector for SAP Solution Manager 4.0.0.1

You can upgrade the Rational Connector for SAP Solution Manager on a Tomcat Application Server or a WebSphere Application Server.

Upgrading from version 4.0.0.0 on a Tomcat Application Server

Installing the upgrade software
  1. Extract the contents of the 4.0.0.1 download package to a temporary directory and run the launchpad.exe file.
  2. On the start page of Installation Manager, select IBM Rational Connector for SAP Solution Manager 4.0.0.1 and click Next.
  3. Accept the License Agreement and click Next.
  4. Accept the default location to install the package and click Next.
  5. Accept the default language and click Next.
  6. No need to change selected features. Click Next.
  7. Keep the Tomcat Application Server check box selected and click Next.
  8. On the installation summary page, click Install.
  9. When the installation is completed, click Finish.
Completing the upgrade installation
  1. If you are using Derby, move the Derby database from 4.0.0.0 to 4.0.0.1

    cp -R 4.0.0.0_install_dir/server/conf/sapc/Derby/SAPConnectorDB 4.0.0.1_install_dir/server/conf/sapc/Derby

  2. If you are using DB2, Oracle, or the SQL Server, backup the database.
  3. Preserve your 4.0.0.0 user registry files.
    1. If you are using the Tomcat user registry, preserve your 4.0.0.0 tomcat-users.xml and server.xml files

      cp 4.0.0.0_install_dir/server/tomcat/conf/tomcat-users.xml 4.0.0.1_install_dir/server/tomcat/conf/tomcat-users.xml

      cp 4.0.0.0_install_dir/server/tomcat/conf/server.xml 4.0.0.1_install_dir/server/tomcat/conf/server.xml

    2. If you are using an LDAP user registry or disabled HTTPS or FORM authentication, preserve your 4.0.0.0 server.xml and web.xml files on the appropriate application servers

      cp 4.0.0.0_install_dir/server/tomcat/conf/server.xml 4.0.0.1_install_dir/server/tomcat/conf/server.xml

      cp 4.0.0.0_install_dir/server/tomcat/webapps/SAPConnector/WEB-INF/web.xml 4.0.0.1_install_dir/server/tomcat/webapps/SAPConnector/WEB-INF/web.xml

  4. Copy your application configuration file from 4.0.0.0 to 4.0.0.1

    cp 4.0.0.0_install_dir/server/conf/sapc/sapconnector.properties 4.0.0.1_install_dir/server/conf/sapc

  5. Start the servers.

Upgrading from version 4.0.0.0 on a WebSphere Application Server

Installing the upgrade software
  1. Extract the contents of the 4.0.0.1 download package to a temporary directory and run the launchpad.exe file.
  2. On the start page of Installation Manager, select IBM Rational Connector for SAP Solution Manager 4.0.0.1 and click Next.
  3. Accept the License Agreement and click Next.
  4. Accept the default location to install the package and click Next.
  5. Accept the default language and click Next.
  6. No need to change selected features. Click Next.
  7. Clear the Tomcat Application Server check box selected and click Next.
  8. On the installation summary page, click Install.
  9. When the installation is completed, click Finish.
Completing the upgrade installation
  1. Back up the WebSphere Application Server profile.
    1. Open a command prompt and change to the WAS_Install/bin directory.

      For example, /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin

    2. Run the following command:

      ./backupConfig path to a new compressed file to create back up of profile

      For example, ./backupConfig /root/was_backups/clm_301_profile.zip

      Note: The backed up profile can be restored if needed by running the ./restoreConfig command.

      For example, ./restoreConfig /root/was_backups/clm_301_profile.zip

  2. Uninstall the 4.0.0.0 application from the WebSphere Application Server.
    1. Log on to the WebSphere Application Server Integrated Solutions Console at https://hostname:9043/ibm/console/logon.jsp
    2. Click Applications > Applications Types > WebSphere enterprise applications.
    3. Write down the security role mapping for the SAPConnectorAdmin role for the SAPConnector 4.0.0.0 application. You will use this information when you deploy the 4.0.0.1 application.
    4. Stop and uninstall the following 4.0.0.0 application: SAPConnector.
    5. Save the changes to the master configuration when prompted.
  3. Update the Java Virtual Machine custom property named SAPC_HOME
    1. From the console, click Servers > Server Types > WebSphere application servers.
    2. Click the server name to open it. The default server name is server1.
    3. Under the Server Infrastructure section click Java and Process Management > Process definition.
    4. Under Additional Properties click Java Virtual Machine.
    5. Under Additional Properties click Custom properties.
    6. Click SAPC_HOME and update its value to 4.0.0.1_install_dir/server/conf

      For example, /opt/IBM/JazzTeamServer_4.0.0.1/server/conf

    7. If you are connecting to an Oracle or SQL Server database, ensure that ORACLE_JDBC_DRIVER_FILE or SQLSERVER_JDBC_DRIVER_FILE is pointing to the correct JDBC driver.
    8. Save the changes to the master configuration when prompted.

      Note: For detailed information, see Setting up a WebSphere Application Server.

  4. Stop the WebSphere Application Server.
  5. Remove the connector related contents from the wstemp and temp directories in the profile. The following directory is present under profile and can be removed: SAPConnector.

    profile directory/wstemp

    For example, /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/wstemp

    profile directory/temp

    For example, /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/temp

  6. Remove the connector related logs form the logs directory in the profile.

    profile directory/logs

    For example, /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs

  7. Prepare the databases for the CLM 4.0.0.1 applications.
    1. If you are using Derby, move the Derby database from 4.0.0.0 to 4.0.0.1

      Note: The commands below assume that you are using the Derby database provided with the packaged product. If you have changed your Derby database location, then the commands should be updated to use the new database location.

      cp -R 4.0.0.0_install_dir/server/conf/sapc/Derby/SAPConnectorDB 4.0.0.1_install_dir/server/conf/sapc/Derby

    2. If you are using DB2, Oracle, or the SQL Server, backup the database.
  8. Copy your application configuration file from 4.0.0.0 to 4.0.0.1.

    cp 4.0.0.0_install_dir/server/conf/sapc/sapconnector.properties 4.0.0.1_install_dir/server/conf/sapc

  9. Start the WebSphere Application Server.
  10. Deploy the 4.0.0.1 ear file in the WebSphere Application Server.
    1. From the console, click Applications > Applications Types > WebSphere enterprise applications.
    2. Install the SAPConnector.ear file.
    3. Map the security role SAPConnectorAdmin for the application SAPConnector.
  11. While in the Enterprise Applications page, start the application: SAPConnector.