IBM Rational Asset Manager, version 7.2.0.1

Installation guide

Version 7.2.0.1
Note

Before using this information and the product it supports, read the information in Notices.

Fourth Edition (December 2009)

This edition applies to version 7.2.0.1 of IBM Rational Asset Manager and to all subsequent releases and modifications until otherwise indicated in new editions.

Copyright International Business Machines Corporation 2007, 2009.
US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

Roadmaps for installing Rational Asset Manager
Installing Rational Asset Manager with the embedded WebSphere Application Server
Installing Rational Asset Manager to an existing WebSphere Application Server by using Installation Manager
Installing Rational Asset Manager on an Apache Tomcat server
Upgrading Rational Asset Manager
Upgrading from a previous version on WebSphere Application Server
Upgrading from a previous version on Tomcat
Planning your installation
Rational Asset Manager system and capacity planning guidelines
WebSphere Application Server clusters
Integrations with Rational Asset Manager
System maintenance
IBM Packaging Utility
Installing Packaging Utility
Installation requirements
Hardware requirements
Software requirements
User privileges requirements
Pre-installation tasks
Installing from download
Extracting the files
Installing from the launchpad program
Starting the launchpad program
Starting an installation from the launchpad program
Installing from the IBM Installation Manager
Working with IBM Installation Manager
Installing IBM DB2 Enterprise Server Edition, version 9.5
Registering the DB2 license key
Installing Rational License Server
Enabling application security on WebSphere Application Server V6.1
Installing Rational Asset Manager
Installing Rational Asset Manager server by using Installation Manager
Installing silently with Installation Manager
Manually deploying and configuring Rational Asset Manager on an existing application server
Retrieving the server application files directly from the installation media
Creating and configuring databases for Rational Asset Manager
Deploying the server applications manually on WebSphere Application Server
Deploying the server applications on Apache Tomcat
Post-installation configuration
Deploying and configuring application files by using the server setup application
Configuring the Rational Asset Manager server application
Configuring e-mail settings
Tuning the performance of Rational Asset Manager
Configuring remote processes
Configuring the embedded WebSphere Application Server as a service (Windows and Linux only)
Additional configuration requirements for Linux and AIX
Enabling artifact content indexing for Linux and AIX
Enabling content indexing (Linux and AIX)
Enabling database connectivity for non-root users (Linux and AIX)
Installing the X Virtual Frame Buffer on AIX or Linux
Creating a backup of a Rational Asset Manager repository
Installing the Rational Asset Manager Eclipse client
Installing Rational Asset Manager Eclipse client using Eclipse update manager
Installing Rational Asset Manager Eclipse client by using Installation Manager
Adding the server public certificate to the Eclipse client
Uninstalling Rational Asset Manager
Uninstalling with the server setup application and Installation Manager
Uninstalling from WebSphere Application Server manually
Notices
Trademarks and service marks

Roadmaps for installing Rational Asset Manager

Installing Rational Asset Manager with the embedded WebSphere Application Server

Follow this outline to consider installation options for IBM® Rational® Asset Manager and to install it with IBM WebSphere® Application Server, version 6.1.

About this task

To install Rational Asset Manager with the embedded WebSphere Application Server:

  1. Install a database application for Rational Asset Manager:

    Rational Asset Manager requires a database for asset and data storage. If you do not have one of the supported database applications installed, you can install IBM DB2® Enterprise Server Edition, version 9.5 from the Rational Asset Manager launchpad.

    To improve performance, the database server typically resides on a computer that is physically separate from the application server and on its own dedicated disk.

    To configure the database tables and schema, you must have database administrator privileges.

    Choose one of the following databases:

    1. DB2
    2. Oracle
    3. Microsoft® SQL Server
  2. Install Rational License Server.

    To distribute license keys to clients, Rational Asset Manager server requires the IBM Rational License Server.

  3. Install the embedded WebSphere Application Server V6.1 and the IBM Rational Asset Manager server application.

    Use IBM Installation Manager to simultaneously install an embedded version of WebSphere Application Server, Version 6.1 and the Rational Asset Manager server setup application. This is the easiest method for installing Rational Asset Manager server.

  4. Deploy the other application files and configure the Rational Asset Manager Server application using the server setup application.

    The Rational Asset Manager server setup application is browser-based application that works like a wizard to help you deploy application files, set up databases, configure users and security, and adjust repository settings.

  5. Configure the server environment settings.

    Additional configuration steps are required on Linux®, AIX®, and Linux for zSeries®:

    1. Enable artifact content indexing for Linux.
    2. Enable content indexing to run for non-root users.
    3. Enable database connectivity for non-root users.
    4. Install the X Virtual Frame Buffer
  6. Configure the e-mail settings for Rational Asset Manager.
  7. Optionally: see the Rational Asset Manager Tuning Guide and the guidelines for system and capacity planning.

    If you are an administrator, ensure the best possible performance for users, regardless of the number of concurrent users or the number of assets in the repository.

  8. Optionally: Install the Rational Asset Manager Eclipse client.

    You can install the Rational Asset Manager Eclipse client by the following methods:

Installing Rational Asset Manager to an existing WebSphere Application Server by using Installation Manager

Follow this outline to plan the installation of IBM Rational Asset Manager to an IBM WebSphere Application Server by using IBM Installation Manager.

About this task

To install Rational Asset Manager to a WebSphere Application Server:

  1. Install a database application for Rational Asset Manager:

    Rational Asset Manager requires a database for asset and data storage. If you do not have one of the supported database applications installed, you can install IBM DB2 Enterprise Server Edition, version 9.5 from the Rational Asset Manager launchpad.

    To improve performance, the database server typically resides on a computer that is physically separate from the application server and on its own dedicated disk.

    To configure the database tables and schema, you must have database administrator privileges.

    Choose one of the following databases:

    1. DB2
    2. Oracle
    3. Microsoft SQL Server
  2. Install Rational License Server.

    To distribute license keys to clients, Rational Asset Manager server requires the IBM Rational License Server.

  3. Create a backup of your server configuration by using the <WebSphere_install_location>/bin/backupConfig.bat command. For more information, see the WebSphere Application Server documentation.
  4. If you are installing to WebSphere Application Server V6.1, make sure application security is enabled.
  5. Install the Rational Asset Manager server setup application on the existing WebSphere Application Server.

    Use IBM Installation Manager to install the Rational Asset Manager server setup application on an existing WebSphere Application Server. On the Features page of the Install wizard, select WebSphere Application Server

  6. Deploy the other application files and configure the Rational Asset Manager Server application using the server setup application.

    The Rational Asset Manager server setup application is browser-based application that works like a wizard to help you deploy application files, set up databases, configure users and security, and adjust repository settings.

  7. For Linux: For AIX: For Linux for zSeries: Configure the server environment settings.

    Additional configuration steps are required on Linux, AIX, and Linux for zSeries:

    1. Enable artifact content indexing for Linux.
    2. Enable content indexing to run for non-root users.
    3. Enable database connectivity for non-root users.
    4. Install the X Virtual Frame Buffer
  8. Configure the e-mail settings for Rational Asset Manager.
  9. Optionally: see the Rational Asset Manager Tuning Guide and the guidelines for system and capacity planning.

    If you are an administrator, ensure the best possible performance for users, regardless of the number of concurrent users or the number of assets in the repository.

  10. Optionally: Install the Rational Asset Manager Eclipse client.

    You can install the Rational Asset Manager Eclipse client by the following methods:

Installing Rational Asset Manager on an Apache Tomcat server

You can install and configure IBM Rational Asset Manager manually on Tomcat. Follow this outline plan to install Rational Asset Manager and to configure it on an existing Apache Tomcat server.

  1. Install a database application for Rational Asset Manager:

    Rational Asset Manager requires a database for asset and data storage. If you do not have one of the supported database applications installed, you can install IBM DB2 Enterprise Server Edition, version 9.5 from the Rational Asset Manager launchpad.

    To improve performance, the database server typically resides on a computer that is physically separate from the application server and on its own dedicated disk.

    To configure the database tables and schema, you must have database administrator privileges.

    Choose one of the following databases:

    1. DB2
    2. Oracle
    3. Microsoft SQL Server
  2. Install Rational License Server.

    To distribute license keys to clients, Rational Asset Manager server requires the IBM Rational License Server.

  3. Retrieve the Rational Asset Manager server application files for Apache Tomcat:
    1. See Retrieving the server application files directly from the installation media. The archive files have the .war application files and database scripts that you need. Extract it to a convenient location.
  4. Create and configure the databases for Rational Asset Manager.
  5. Create a database for managing custom lifecyles.
  6. Deploy the server application files to Apache Tomcat and configure the database connection.
  7. For Linux: For AIX: For Linux for zSeries: Configure the server environment settings.

    Additional configuration steps are required on Linux, AIX, and Linux for zSeries:

    1. Enable artifact content indexing for Linux.
    2. Enable content indexing to run for non-root users.
    3. Enable database connectivity for non-root users.
    4. Install the X Virtual Frame Buffer
  8. Configure the Rational Asset Manager Server application.

    Before you can use Rational Asset Manager server, you must configure the licensing, storage, and other configuration settings.

  9. Configure the e-mail settings for Rational Asset Manager.
  10. Optionally: see the Rational Asset Manager Tuning Guide and the guidelines for system and capacity planning.

    If you are an administrator, ensure the best possible performance for users, regardless of the number of concurrent users or the number of assets in the repository.

  11. Optionally: Install the Rational Asset Manager Eclipse client.

    You can install the Rational Asset Manager Eclipse client by the following methods:

Upgrading Rational Asset Manager

Upgrading from a previous version on WebSphere Application Server

Use this guide to upgrade from an earlier version of IBM Rational Asset Manager on IBM WebSphere Application Server.

Before you begin

Important: If you are upgrading from Rational Asset Manager, Version 7.1.1.1 or earlier, you must install IBM Rational Team Concert, which requires its own application server instance - you cannot install Rational Team Concert to a cluster - and an additional database. You will also have to stop and restart your application server several times.

If you have Internet access, you can use IBM Installation Manager to locate and install the updates directly from the IBM update repository for Rational Asset Manager.

Important: When Rational Asset Manager installs, the location of its update repository is automatically embedded in Installation Manager. For Installation Manager to search the default update repository, the Search the linked repositories during installation and updates preference on the Repositories preferences page must be selected; this preference is selected by default.

To install the fix pack from a different repository location (for example, if the update is on a shared drive or HTTP or HTTPS server), add the repository location in Installation Manager. To add a repository location, see Setting installation repository preferences in Installation Manager.

To work with Installation Manager, you must use a graphical user interface (GUI). If you do not have access to a GUI, you must install silently over the command line with response files. For more information, see the IBM Installation Manager online help and Installing silently with Installation Manager.

  1. Create a backup of your Rational Asset Manager database. For more information, see the documentation for your database software.
  2. Create a backup of the Persist folders for all of your servers. To find the location of the Persist folders, log in to the Web client as a repository administrator and click Administration; then click Configuration. In the Disk Storage section, you will see the location of the Persist folder.
  3. For Linux: For AIX: For Linux for zSeries:On Linux, AIX, or Linux for zSeries, increase the number of file descriptors a process may have open at once to at least 2048:
    1. To view the current number of descriptors that can be open at once, in the command line type: ulimit -n
    2. If the limit is not at least 2048, increase the limit with the following command: ulimit -n 2048
  4. If you have modified your theme, before you update the Rational Asset Manager server, download the current theme and then, after you have updated the server, reapply the theme. You might have to update your theme after you migrate.
  5. Create a backup of your IBM WebSphere Application Server configuration by using the <WebSphere-Install-Directory>\bin\backupConfig.bat command. For more information, see the WebSphere Application Server documentation.
  6. For WebSphere:If you use a WebSphere Application Server cluster, you must create a stand-alone application server instance on your cluster for Rational Team Concert. To do so, see Creating an application server instance for Rational Team Concert on a WebSphere Application Server cluster. If you are not using a cluster, you do not have to do this; Rational Team Concert and Rational Asset Manager can be installed on the same application server.
  7. For WebSphere: Configure the application security and authentication settings for WebSphere Application Server:
    1. In a Web browser, log in to the WebSphere Application Server Administrative Console. By default, this is located at:
      • For embedded WebSphere Application Server: http://localhost:13060/ibm/console . The default username is admin and the default password is admin.
      • For WebSphere Application Server: http://localhost:9060/ibm/console
    2. Click Security.
    3. Click Secure administration, applications, and infrastructure.
    4. In the Administrative Security section, if the Enable administrative security checkbox is selected, select the Enable application security checkbox.
    5. In the Authentication section, click Web security.
    6. Click General settings.
    7. In the Web Authentication Behavior section, select the Use available authentication data when an unprotected URI is accessed checkbox if it is not already selected.
    8. Click Apply.
    9. In the Messages window, click Save directly to the master configuration.
    10. Stop, and then restart the server.
  8. If you are using Rational Asset Manager, version 7.0.0.2 or earlier, verify that the job server is enabled. To enable the job server:
    1. Log in to the Rational Asset Manager Web client as a repository administrator.
    2. Click Administration.
    3. In the Repository Administration sidebar, click Tools.
    4. In the address bar of the browser, replace tools.faces with advancedConfiguration.faces and go to that address. For example, http://example.com:9080/com.ibm.ram.repository.web/admin/repository/advancedConfiguration.faces
    5. On the Advanced Settings page, in the Job Options section, select Enable job server.
    6. Click Save.
    7. Restart the application server.
  9. Verify that all of the repository servers are set to the same current date, time, and time zone.
  10. If you are not using the embedded WebSphere Application Server, you must install the following Interim Fix to your server: http://www-01.ibm.com/support/docview.wss?uid=swg24023024. This Interim Fix prevents an issue where WebSphere Application Server is unable to release connections with Rational Team Concert.
  11. If you use the embedded WebSphere Application Server, stop the embedded WebSphere Application Server. If issuing the Rational Asset Manager Stop the server command does not stop the server, run the stopServer command from a command line in the <Install-directory>\ram\ewas\bin directory, and specify a server administrator user name and password by using the -username and -password options.
  12. Retrieve the appropriate Rational Asset Manager applications:
  13. Deploy the Rational Asset Manager server setup application to your application server:
  14. After you have deployed the most recent version of the server setup application, in a Web browser, open the server setup application by using the URL: http://<host>:<port>/<setup-server-context-root>. The default URL is: http://<host>:<port>/ram.setup/. If security is enabled on the application server, type the user ID and password for an application server administrator. For the embedded WebSphere Application Server, the default user ID and password are admin and admin.
  15. In the Step 1: Locate Installation Files section, in the Location field type the directory on the file system where the new web application files are located. If you used the Update wizard in Installation Manager, the files will be at the <package_group_location>\ram\apps\was directory. The following files must be in that directory:
  16. To verify that all required application files are in the Location directory, click Verify Location. A message will verify if all the required files are present.
  17. Click Update. The server setup application updates all other Rational Asset Manager application files to the latest versions and maintains their context roots, a process that can take several minutes.
  18. Next:
  19. Click Next. You must deploy Rational Team Concert, which is required for the enhanced asset lifecycle process:
    1. On the Deploy Rational Asset Manager page, in the Deploy Rational Team Concert section, confirm the application server in the Servers list - you cannot deploy Rational Team Concert to a cluster - and click Deploy Applications. The operation to deploy Rational Team Concert can take several minutes. The Deploy Rational Asset Manager page reopens when the process completes.
    2. When the operation completes, click Next.
  20. Create a new database for asset lifecycles for Rational Team Concert
  21. On the Configure Database page, enter and test the connection to the database for lifecycle management:
    1. In the Database name for Lifecycle field, type the name of the database that you created in step 20.
    2. To test the connection, click Test Connection.
    3. If the connection succeeds, click Next.
  22. Configure the Rational Team Concert database. Under Step 6: Configure Rational Asset Manager Lifecycle Database:
    1. Click Populate the Database.
    2. A message asks you to verify that you want to configure the lifecycle database. Click OK.
    3. After the process completes, click Next.
  23. Continue through the server setup application to configure or adjust your database and application server settings. For more details, see Deploying and configuring application files by using the server setup application.
  24. Restart the server. To restart the server in the server setup application, click Tools -> Restart the server. Next:
  25. In the Lifecycle management settings page, type the path and login information for the Rational Team Concert application:
    1. In the Rational Team Concert field, type the path to the Rational Team Concert location. You must use a secure (https://) connection. By default, this value is:
      • For the embedded WebSphere Application Server: https://localhost:13443/jazz
      • For an existing WebSphere Application Server: https://localhost:9443/jazz
    2. In the User ID field, type the username of the WebSphere Application Server repository administrator. By default, this is admin.
    3. In the Password field, type the password for the repository administrator. By default, this is admin.
    4. Click Configure server. This process may take a few minutes. After the configuration, the Summary page appears again.
  26. On the Summary page, click Start using Rational Asset Manager. The Web client opens.
  27. Migrate the Rational Asset Manager repository to the newest version:
    1. In a Web browser, open the Rational Asset Manager Web client. The first time that you open the Web client after the upgrade, a message is displayed that indicates that you must migrate the repository.
    2. If necessary, log in with a user ID that has repository administrator authority.
      Note: For SQL Server, if an existing Rational Asset Manager database does not have the collation set to a sequence that ends with _BIN2 (for example, Latin1_General_BIN2) then the Manual Configuration Required page appears with a message. You can either recreate the database and set the collation option to be case-sensitive to work correctly with Rational Asset Manager or you can accept that there may be unexpected case-sensitivity conflicts.
    3. Click Migrate. On large repositories, the migration might take several minutes; until the migration is complete, some information on the repository might not be available.
    4. After the migration process completes, click Home.
  28. To upgrade, you need to file a request for a new license key. You need to acquire a new server license and new user authorized licenses. Go to the Rational License Key Center: http://www-01.ibm.com/software/rational/support/licensing/ If you see an error about Rational License Server, adjust your license configuration:
    1. Click Administration
    2. On the Administration page, click Configuration.
    3. In the License and Version section, to select what type of server license this repository will use, select either Standard edition or Enterprise edition.
    4. At the bottom of the page, click Save.
    5. You might see the License Server error again. Click Retry connection to license server.
  29. After configuration is complete, manually remap shared library references for the previous version of Rational Asset Manager to the RAM1WebApplication (for example, integration with IBM Rational ClearQuest®).
  30. Update the Rational Asset Manager Eclipse application by using the same method that you used to install it. For more information on installing the Eclipse client, see Installing the Rational Asset Manager Eclipse client.
    Note: Before you install the latest version of the Rational Asset Manager Eclipse client, uninstall the Rational Asset Manager Eclipse client plug-in.

    If you installed the Rational Asset Manager V7.0.0.2 Eclipse client into an existing Eclipse V3.3 application by using Installation Manager, use Installation Manager to uninstall the client. You cannot use the Eclipse Configuration Manager to uninstall Rational Asset Manager from the Eclipse client.

    If you installed the Rational Asset Manager Eclipse client plug-ins by using the Eclipse update manager, before you install the latest version of Rational Asset Manager, use the Eclipse configuration manager to remove any features that are named Rational Asset Manager. To use the Eclipse configuration manager, in Eclipse, click Help -> Software Updates -> Manage Configuration.

Upgrading from a previous version on Tomcat

Use this guide to upgrade from an earlier version of IBM Rational Asset Manager on Apache Tomcat.

Before you begin

Important: If you are upgrading from Rational Asset Manager, Version 7.1.1.1 or earlier, you must install IBM Rational Team Concert, which requires an additional database and a secure certificate for your Tomcat server. You will also have to stop and restart your application server several times.

  1. Create a backup of your Rational Asset Manager database. For more information, see the documentation for your database software.
  2. Create a backup of the Persist folders for all of your servers. To find the location of the Persist folders, log in to the Web client as a repository administrator and click Administration; then click Configuration. In the Disk Storage section, you will see the location of the Persist folder.
  3. If you have modified your theme, before you update the Rational Asset Manager server, download the current theme and then, after you have updated the server, reapply the theme. You might have to update your theme after you migrate.
  4. Verify that all of the repository servers are set to the same current date, time, and time zone.
  5. Create a backup of your Tomcat server configuration by copying the <tomcat_install_directory>\conf\server.xml file.
  6. Create a backup of the Tomcat server startup file:
  7. If you are using Rational Asset Manager, version 7.0.0.2 or earlier, verify that the job server is enabled. To enable the job server:
    1. Log in to the Rational Asset Manager Web client as a repository administrator.
    2. Click Administration.
    3. In the Repository Administration sidebar, click Tools.
    4. In the address bar of the browser, replace tools.faces with advancedConfiguration.faces and go to that address. For example, http://example.com:9080/com.ibm.ram.repository.web/admin/repository/advancedConfiguration.faces
    5. On the Advanced Settings page, in the Job Options section, select Enable job server.
    6. Click Save.
    7. Restart the application server.
  8. Retrieve the Rational Asset Manager server files on the appropriate archive for Tomcat and for your operating system. The application files will be in the <archive_extract_location>/apps/tomcat/ folder.
  9. If you are upgrading from V7.1.1.1 or earlier: Create the database for asset lifecycles:
  10. Stop the Tomcat server. Your repository and any other applications on your server will now be offline.
  11. Extract the shared library files to the <tomcat_install_directory>\shared\lib folder:
    1. Find and extract the <archive_extract_location>\apps\tomcat\sharedLib.zip file.
    2. Copy the entire contents of the extracted sharedLib.zip file to the <tomcat_install_directory>\shared\lib directory.
  12. Find the <archive_extract_location>/apps/tomcat/RTC-server.zip file on the installation media.
  13. Next:
  14. Extract RTC-server.zip to a location on your hard drive, which is referred to in these instructions as <rtc_install_dir>.
  15. Find the <rtc_install_dir>/jazz/server/jazz_war.ear file and extract it. You can use the free utility 7-Zip to extract .ear files. From the extracted jazz_war.ear package, copy the jazz.war file to the <tomcat_install_directory>/webapps/ directory.
  16. Configure a secure port on your Tomcat server for Rational Team Concert:
    1. You must create a security certificate that identifies your Tomcat server for SSL connections. You can either use the Java JDK keytool function to create a self-signed certificate or you can request a certificate signed by a trusted certificate authority (CA).

      For more information on creating self-signed certificates with keytool, see the Sun Java documentation.

      If you are using an IBM JRE, many versions include the IBM tool ikeyman in the <IBM_Java_JRE_install_location>/jre/bin/ directory. You can use this tool to create and manage security certificates on the server. For more information on using the iKeyman tool, see iKeyman User's Guide.

    2. Copy the certificate keystore file to the root directory for your server, <tomcat_install_directory>.
    3. In the <tomcat_install_directory>\conf\server.xml file, locate the <Connector> tag with the attribute scheme="https". The default file includes an example <Connector> tag for port 8443 that is commented out.
    4. Copy and paste the following text:
      <Connector port="8443"
           maxHttpHeaderSize="8192" 
           maxThreads="150"
           minSpareThreads="25" 
           maxSpareThreads="75"
           enableLookups="false"
           disableUploadTimeout="true" 
           acceptCount="100"
           scheme="https"
           secure="true" 
           clientAuth="false"
           keystoreFile="<keystore_file>"
           keystorePass="<keystore_password>"
           sslProtocol="<keystore_protocol>"
           algorithm="<keystore_algorithm>"
           URIEncoding="UTF-8" />

      Where:

      • <keystore_file> is the filename of your keystore file;
      • <keystore_password> is the password for the keystore file;
      • <keystore_protocol> is the protocol for the keystore. It will most likely be SSL, TLS, or SSL_TLS;
      • <keystore_algorithm> is the X509 algorithm for the keystore. Most likely it will be SunX509 or IbmX509, depending on the source of the certificate.
    5. If you change the port value to use a port other than 8443, for the non-SSL connector (by default, port 8080), change the value of the redirectPort attribute to match your port number for the SSL connector.

    For more information on configuring SSL for Tomcat, see Apache Tomcat 5.5 SSL Configuration HOW-TO and Apache Tomcat Configuration reference.

  17. Modify the Tomcat user authorization settings for Rational Team Concert:
  18. Configure the Tomcat system property settings:
    1. Find the Tomcat startup file and open it in a text editor. On Windows this is <tomcat_install_directory>\bin\startup.bat. On Linux, AIX, or Linux for zSeries, it is <tomcat_install_directory>/bin/startup.sh.
    2. In the startup file, type the following text, where <rtc_install_dir> is the extracted directory from step 10: if you use Oracle, <oracle_jar_dir> is the location of the Oracle ojdbc14.jar file; if you use SQL Server, <sqlServer_jar_dir> is the location of the SQL Server sqljdbc.jar file:
      • For Windows:On Windows (replace space characters in the <rtc_install_dir> with %20):
        set ORACLE_JDBC=<oracle_jar_dir>
        set SQLSERVER_JDBC=<sqlServer_jar_dir>
        set JAZZ_INSTALL_DIR=<rtc_install_dir>
        
        
        set JAVA_OPTS=-Djava.awt.headless=true -DSQLSERVER_JDBC="%SQLSERVER_JDBC%" -DORACLE_JDBC="%ORACLE_JDBC%" -DDB2I_JDBC="%DB2I_JDBC%" -DDB2Z_JDBC="%DB2Z_JDBC%" -Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true -DJAZZ_HOME=file:///%JAZZ_INSTALL_DIR%\jazz\server\conf -Dcom.ibm.team.repository.tempDir=%TEMP% -Xmx700M
      • For Linux: For AIX: For Linux for zSeries:On Linux, AIX, or Linux for zSeries:
        ORACLE_JDBC=<oracle_jar_dir>
        SQLSERVER_JDBC=<sqlServer_jar_dir>
        JAZZ_INSTALL_DIR=<rtc_install_dir>
        
        
        export JAVA_OPTS="-Djava.awt.headless=true -DSQLSERVER_JDBC=$SQLSERVER_JDBC -DORACLE_JDBC=$ORACLE_JDBC -DDB2I_JDBC=$DB2I_JDBC -DDB2Z_JDBC=$DB2Z_JDBC -Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true -DJAZZ_HOME=file://"$JAZZ_INSTALL_DIR"/jazz/server/conf -Dcom.ibm.team.repository.tempDir=$TEMP_DIR -Xmx700M"
  19. Edit the Jazz™ server properties file:
    1. In the <rtc_install_dir>/jazz/server/conf/jazz/ directory, find the teamserver.properties file and rename it to teamserver.derby.properties.
    2. Find the appropriate file for your database server:
      • For DB2: For Windows:For DB2 on Windows: teamserver.db2.win32.properties
      • For DB2: For Linux: For AIX: For Linux for zSeries:For DB2 on Linux, AIX, or Linux for zSeries: teamserver.db2.linux.properties
      • For Oracle:For Oracle: teamserver.oracle.properties
      • For SQL Server:For SQL Server: teamserver.sqlserver.properties
    3. Rename the file for your database server to teamserver.properties.
    4. In the teamserver.properties file, specify the database and connection properties:
      1. In a text editor, open the teamserver.properties file.
      2. Edit the com.ibm.team.repository.db.jdbc.location and com.ibm.team.repository.db.jdbc.password properties as discussed in the following topics:
      3. Add the following properties to the teamserver.properties file, where <unsecure_port> is the unsecure port for your Tomcat server (by default, 8080), <secure_port> is the secure port number for your Tomcat server (by default, 8443), and <team_temp_dir> is an absolute path to a directory for storing temporary files:
        com.ibm.team.scm.tmpdir=<team_temp_dir>
        com.ibm.team.repository.server.repourl.port.http=<unsecure_port>
        com.ibm.team.repository.user.registry.type=UNSUPPORTED
        com.ibm.team.repository.ws.allow.admin.access=false
        com.ibm.team.repository.server.repourl.port.https=<secure_port>
  20. Create the tables for Rational Team Concert:
    1. Open a command window and navigate to the <rtc_install_dir>/jazz/server/ directory.
    2. Run the following command:
      • For Windows::
        repotools.bat -createTables teamserver.properties=conf\jazz\teamserver.properties
      • For Linux: For AIX: For Linux for zSeries::
        ./repotools.sh -createTables teamserver.properties=conf/jazz/teamserver.properties
  21. Restart the Tomcat server.
  22. If you are using LDAP to manage users: You can now map existing LDAP group names to the group names required for Rational Team Concert:
    1. Stop the Tomcat server.
    2. With a text editor, open the file <tomcat_install_directory>/webapps/jazz/WEB-INF/web.xml.
    3. Modify the web.xml file as described in TN0030: User management for Jazz servers in Tomcat. The user who is the Tomcat server administrator must either be a member of an LDAP group named JazzAdmins, or be a member of a group that is mapped to the JazzAdmins group.
    4. Restart the Tomcat server.
  23. Configure the administrative user for Rational Team Concert:
    1. Launch the Admin Web UI of Rational Team Concert in a Web browser at https://<machine_name>:<secure_port>/jazz/admin/.
    2. Log in with the User ID and Password for the administrator of the application server.
    3. Click User Management.
    4. Click Create New.
    5. Enter the following details:
      1. User Name: The user ID of the Tomcat server administrator
      2. User ID: The user ID of the Tomcat server administrator
      3. E-mail Address: A valid e-mail address for the Tomcat server administrator
    6. In the Client Access License section, select Rational Team Concert - Developer to assign the developer license to that user.
    7. Click Save.
    8. Log out, and then log back in to the Admin Web UI as the administrator of the application server.
  24. Import the lifecycles process template into Rational Team Concert:
    1. In the Rational Team Concert Admin Web UI, click Process Template Management. If you cannot see the Process Template Management link, log out and then log back in to the Admin Web UI.
    2. Click Import Template and browse to the com.ibm.ram.lifecycle.zip file in the <archive_extract_location>/DatabaseScripts/ folder. Then click OK.
  25. Create a new project area in Rational Team Concert:
    1. In the Rational Team Concert Admin Web UI, click Project Area Management. If you cannot see the Project Area Management link, log out and then log back in to the Admin Web UI.
    2. Click Create Project Area.
    3. Enter the following details about the project area:
      • Project name: RAM Lifecycle
      • Summary: Rational Asset Manager Lifecycle control project area
      • Description: This area is used to manage the lifecycles for Rational Asset Manager
    4. Click Save.
  26. Assign the appropriate memberships and process roles for the project area:
    1. On the Project Area Management page, click the RAM Lifecycle project area.
    2. In the Administrators section, click Add; then search for and select the administrator user that you created.
    3. In the Members section, click Add; then search for and select the administrator user that you created.
    4. After you add the administrator, click the Process Roles icon next to the administrator's name.
    5. In the Edit Process Roles dialog, from the Available Roles list, select Administration and click Add.
    6. Click Finish.
    7. Click Save.
  27. If you upgrading from V7.1.1.1 or earlier: Proceed to step 29.
  28. If you are upgrading from V7.2 or later, upgrade the included Rational Team Concert:
    1. From the installation media, extract the RTC-Server.zip file to a new location on your hard drive, which in these instructions is referred to as <new_rtc_install_dir>.
    2. From the older <rtc_install_dir>/jazz/server/conf/jazz/ folder, copy the file teamserver.properties to the new <new_rtc_install_dir>/jazz/server/conf/jazz/ folder.

      You can find the existing <rtc_install_dir> location in the Tomcat startup file. In the startup file, search for the line that contains JAZZ_INSTALL_DIR= ; the value of the JAZZ_INSTALL_DIR variable is the location of the current RTC files.

    3. Find the Tomcat startup file and open it in a text editor. On Windows this is <tomcat_install_directory>\bin\startup.bat. On Linux, AIX, or Linux for zSeries, it is <tomcat_install_directory>/bin/startup.sh.
    4. In the Tomcat startup file, search for the line that contains JAZZ_INSTALL_DIR=. Edit the value per the following, where <new_rtc_install_dir> is the extracted directory from step 28a:
      • For Windows: (replace space characters in <new_rtc_install_dir> with %20 ):
        set JAZZ_INSTALL_DIR=<new_rtc_install_dir>
      • For Linux: For AIX: For Linux for zSeries::
        JAZZ_INSTALL_DIR=<new_rtc_install_dir>
    5. Start the Tomcat server.
    6. In Web browser, navigate to the following URL: https://<host>:<secure_port>/jazz/admin?internal, where <host> is your IP address or machine name, and <secure_port> is the secure port for your Tomcat server.
    7. Log on as an application server administrator.
    8. In the sidebar, under Internal Tools section, click Server reset.
    9. Click Request server reset.
    10. Stop, and then restart the Tomcat server. The included Rational Team Concert application is updated.
  29. Stop the Tomcat server.
  30. Remove the old Rational Asset Manager .war Web application files that are installed on Tomcat:
    1. Navigate to the directory <tomcat_install_directory>/webapps/.
    2. Write down the folders and filenames for any Rational Asset Manager Web applications.
    3. Delete the following application files:
      • com.ibm.ram.repository.web.tomcat_runtime.war
      • com.ibm.ram.repository.web.ws.tomcat_runtime.war
      • iehs.war
      • rmcabdgovernprocess.war
      The file names might be different from the above list, depending on how you installed the applications on your server.
    4. Delete the associated folders for those applications In previous versions of Rational Asset Manager, we recommended the following names for those folders (in other words, the context paths of the applications):
      • /com.ibm.ram.repository.web.tomcat_runtime
      • /com.ibm.ram.repository.web.ws.tomcat_runtime
      • /help/
      • /abdprocess/
  31. From the directory <archive_extract_location>/apps/tomcat/, copy the following files to the <tomcat_install_directory>/webapps/ directory:
  32. To change the context path of the applications, rename the WAR application files. We recommend that you use the same context paths that you had before. Here are the recommended paths:
    Table 1. Recommended context paths for Rational Asset Manager Web application files
    Original file name Recommended file name Resulting context path What is it?
    com.ibm.ram.repository.web.tomcat_runtime.war ram.war ram Rational Asset Manager primary Web application for Tomcat
    com.ibm.ram.repository.web.ws.tomcat_runtime.war ram.ws.war ram.ws Rational Asset Manager Web services application for Tomcat
    iehs.war ram.help.war ram.help Rational Asset Manager help and user assistance application.
    rmcabdgovernprocess.war ram.process.war ram.process Documentation application for asset-based development and governance processes
  33. Restart the Tomcat server.
  34. In a Web browser, open Rational Asset Manager. If you used the recommended names for the application files, the URL will be http://localhost:8080/ram/home.faces, or through a Web server, the URL will be http://<Web_server_address>:<port>/ram/home.faces. The Rational Asset Manager Web client opens.
  35. Migrate the Rational Asset Manager repository to the newest version:
    1. In a Web browser, open the Rational Asset Manager Web client. The first time that you open the Web client after the upgrade, a message is displayed that indicates that you must migrate the repository.
    2. If necessary, log in with a user ID that has repository administrator authority.
      Note: For SQL Server, if an existing Rational Asset Manager database does not have the collation set to a sequence that ends with _BIN2 (for example, Latin1_General_BIN2) then the Manual Configuration Required page appears with a message. You can either recreate the database and set the collation option to be case-sensitive to work correctly with Rational Asset Manager or you can accept that there may be unexpected case-sensitivity conflicts.
    3. Click Migrate. On large repositories, the migration might take several minutes; until the migration is complete, some information on the repository might not be available.
    4. After the migration process completes, click Home.
  36. To upgrade, you need to file a request for a new license key. You need to acquire a new server license and new user authorized licenses. Go to the Rational License Key Center: http://www-01.ibm.com/software/rational/support/licensing/ If you see an error about Rational License Server, adjust your license configuration:
    1. Click Administration
    2. On the Administration page, click Configuration.
    3. In the License and Version section, to select what type of server license this repository will use, select either Standard edition or Enterprise edition.
    4. At the bottom of the page, click Save.
    5. You might see the License Server error again. Click Retry connection to license server.
  37. Update the Rational Asset Manager Eclipse application by using the same method that you used to install it. For more information on installing the Eclipse client, see Installing the Rational Asset Manager Eclipse client.
    Note: Before you install the latest version of the Rational Asset Manager Eclipse client, uninstall the Rational Asset Manager Eclipse client plug-in.

    If you installed the Rational Asset Manager V7.0.0.2 Eclipse client into an existing Eclipse V3.3 application by using Installation Manager, use Installation Manager to uninstall the client. You cannot use the Eclipse Configuration Manager to uninstall Rational Asset Manager from the Eclipse client.

    If you installed the Rational Asset Manager Eclipse client plug-ins by using the Eclipse update manager, before you install the latest version of Rational Asset Manager, use the Eclipse configuration manager to remove any features that are named Rational Asset Manager. To use the Eclipse configuration manager, in Eclipse, click Help -> Software Updates -> Manage Configuration.

Planning your installation

Before you install the IBM Rational Asset Manager server, consider the aspects of the installation, including which configuration you will use.

Installation scenarios

You can install Rational Asset Manager in four basic scenarios:

For each scenario, you can install Rational Asset Manager either by using IBM Installation Manager or by using the deployment .zip files and installing them manually. If you are using Installation Manager, you can use the GUI or run a silent install by using the command line.

In this release, Rational Team Concert is a required component that you must install as part of the Rational Asset Manager installation. Rational Team Concert requires an additional 250MB+ of disk space for the server files, and the Rational Team Concert database needs 5GB+ of free space. You cannot install Rational Asset Manager into an existing Rational Team Concert server, nor can you update Rational Team Concert in the Rational Asset Manager 7.2 server. In a WebSphere network deploy environment, Rational Team Concert cannot be deployed onto clusters; Rational Team Concert has to be deployed on an application server only.

In all of these scenarios, you can also install the Rational Asset Manager Eclipse client to interact with the repository.

Eclipse client and server version compatibility

The Rational Asset Manager Eclipse client communicates with Rational Asset Manager servers that use either the same version or one-level earlier version. If it is possible, use the same versions of both the Rational Asset Manager server and the Eclipse client. However, the Eclipse client can communicate with a Rational Asset Manager server of the same version or of a version that is earlier by one level. This includes fix packs of each version. For more information, see this technote: http://www-01.ibm.com/support/docview.wss?uid=swg21380362

Client access licenses

Every valid client access license includes a designated authorization for one user or one program to directly or indirectly access the Rational Asset Manager server for use of the program.

Beginning in Version 7.2, the licensing for Rational Asset Manager Enterprise edition is based on two defined types of user licenses:

Both publisher and collaborator client access licenses can access Rational Asset Manager by using the Web Client, Eclipse Client and through published Rational Asset Manager application programmer interfaces.

User licenses can be assigned or floating. An assigned, or authorized, user is a person or program that is authorized by an administrator to use the licensed product. You must maintain licenses for the equivalent number of persons and programs that use the licensed product. People or programs cannot share user IDs. A user can be assigned either a publisher or a consumer license.

The following licenses are available for Rational Asset Manager:

Rational Asset Manager uses FLEXlm license key enforcement. FLEXlm consumes a license whenever a person logs in to a Rational Asset Manager server. Rational Asset Manager Standard Edition licenses can only be used on Rational Asset Manager servers configured to be a Standard Edition Server. You can not use Rational Asset Manager Standard Edition authorized user licenses on a Rational Asset Manager Enterprise Edition Server. Administrators assign who has named authorized user licenses by using the Rational Asset Manager Web Client; users are assigned their authorized licenses by the administrator, not automatically. Floating licenses are used for any user that does not already have the appropriate authorized license assigned to them. Programmatic access also requires a Rational Asset Manager license based on the user id. A single Rational Asset Manager user id authorized user license cannot be used across multiple programs concurrently.

When an authorized user logs in, a license is allocated to the user. If a user logs in with a different session or from the Eclipse client, the user is still considered to be logged in and they do not consume additional licenses. The license is released only when the user logs out completely from all of the sessions or when all of the sessions timeout.

If a user is not an authorized user and does not have an assigned license, logging in does not consume a license. Depending on the action a user selects, a specific type of license is required. When a user requests an action, a floating license of the correct type is allocated. If no licenses are available, the action is denied. A floating license is held until the user logs out or all of the user's sessions expire.

For example, if a user chooses an action that requires a collaborator floating license and then chooses an action that requires a publisher license, a publisher floating license is allocated to the user and the collaborator floating license is released. The user then holds the publisher license until he or she logs out or all of the sessions expire. If this user had an assigned collaborator license, the license would not be released because that license is assigned. Only floating licenses can be promoted. A license server will still allocate a publisher floating if it can in the case of an assigned collaborator license.

When you plan for the number of each license type to be available for your deployment, the following guidelines might be helpful:

Disk considerations for optimizing performance

Plan to separate the database, repository index, temporary folders, and assets directory on separate hard disk drives. This prevents certain operations (for example, asset retrieval, or the indexing of assets in the repository) from interfering with the users' experience while they perform different operations (for example, asset browsing).

Database

Rational Asset Manager requires a database for asset and data storage. To improve performance, place the database server on a separate physical computer from the application server and on a dedicated disk.

To configure the database tables and schema, you must have database administrator privileges.

Application server

If you use WebSphere Application Server, you can either choose to install a new embedded WebSphere Application Server or use your existing version of WebSphere Application Server. You can use either server with any database or other platform software. However, with integrations you should not plan to use Rational Asset Manager with the embedded version of WebSphere Application Server that is included with Rational Asset Manager.

Embedded WebSphere Application Server is a lightweight version of the server. It supports environments that run a limited number of applications and do not require the full administration support provided by WebSphere Application Server. The embedded WebSphere Application Server provides a lightweight version of the WebSphere Application Server administration console with limited configuration options.

User registries

Although you can add users to Rational Asset Manager from an external registry (such as LDAP or a custom registry), you do not have to use an external registry. You can add users manually.

Security and user authentication

If you plan to manually install Rational Asset Manager onto an existing WebSphere Application Server that is configured for security (for example, using LDAP), reconfigure the application server for file-based security until the installation and configuration of Rational Asset Manager is complete.

File-based security is not intended for use in production environments.

Integrations

Optional: You can integrate Rational Asset Manager with IBM Rational ClearQuest, IBM Rational ClearCase®, and IBM WebSphere Service Registry and Repository. Client applications must be installed on the same computer as the server and Rational Asset Manager server application. To improve performance, run the servers for these applications on computers other than the application server.

When you integrate with Rational ClearCase, the WebSphere Application Server service must be started by the same user who has access to the versioned object base (VOB).

Clusters

When you deploy Rational Asset Manager to a cluster environment, the components must be homogenous with regard to operating system and application server. If you plan to integrate with Rational ClearCase and Rational ClearQuest, client applications must be installed on every component in the cluster and have the same installation path on every node in the cluster. You cannot configure individual nodes independently.

Large numbers of assets

If you expect that the repository will contain a large number of assets (for example, tens or hundreds of thousands), several asset management operations, such as indexing, might require several hours. You might improve performance if you use data management and hard-disk management techniques, such as using a Redundant Array of Independent Disks (RAID) and a technique called disk striping. Disk striping involves dividing data into blocks and storing the data blocks on multiple partitions on multiple hard disk drives. For instructions to set up disk striping for your environment, see the documentation for your operating system. As mentioned in the previous paragraph, consider placing the repository index, assets, and database each on a different hard disk.

Learn more about the component based software architecture practice: This practice focuses on identifying the major abstractions of the system and making decisions on how the system will be built to ensure resilience and maintainability. Read more about the component based software architecture practice at http://www.ibm.com/developerworks/rational/practices/compbased_sa/.

Rational Asset Manager system and capacity planning guidelines

This topic includes planning and performance guidelines for IBM Rational Asset Manager.

Consider the following areas in your system and capacity planning:

Performance factors

Many factors determine capacity requirements and performance results:

Performance and scalability depend on hardware setup and tuning, operating system tuning, software tuning, network traffic and latency, user usage models, the number of assets stored in Rational Asset Manager, and other factors.

When you plan your server hardware requirements, consider the number of concurrent users to have access and the number of assets to be stored in the repository. Response time depends on the details of your specific use cases. For example, uploading a large file takes more time than displaying a Web page.

By adjusting hardware, you can improve performance:

When you plan for the initial platform size and for production environment upgrades, consider the relative system resources that are consumed by different classes of user operations. Heavier system resources are required for Eclipse operations than for the Web interface. For example, the system requirements and steps to improve performance for the following user actions vary:

Plan to need more storage for additional assets or for assets with high artifact content. To support more users, add memory or application servers or use faster disks.

Place the database, repository index, temporary folders, and assets directory on separate hard disk drives. This prevents certain operations (such as asset retrieval and asset indexing) from interfering with user performance (for example, browsing assets).

You can install and maintain Rational Asset Manager on a single server; however, at a minimum, use an external database server and file server. You can also install Rational Asset Manager on a single computer that runs WebSphere Application Server and a database, and use local disks for assets and indexing. However, that configuration cannot scale beyond 50 to 75 concurrent users. To increase the capacity of a single application server, distribute the overall load.

The following two figures show deployment examples.

This figure shows a simple deployment that supports up to 100 users: Simple example of Rational Asset Manager deployment for up to 100 users. The image shows an Eclipse and a Web client connecting to a Web server and one application server, a database server, and a server for asset storage.

This figure shows a complex system that can support more than 100,000 users: Example of a deployment for up 150,000 users. The image shows an Eclipse and a Web client connecting to two Web servers through a load balancer and two application servers, a database server, and a server for asset storage. All of the back end servers have backup servers connected to them.

Rational Asset Manager storage is composed by two components: the database and the file system. The assets are stored in the file system and the metadata are stored in the database.

The number of assets in a repository can affect performance. The size of the assets does not affect database size, but does affect file system storage.

Three major storage points are required for Rational Asset Manager: asset files, the index, and the database. A clustered environment contains one asset storage location and one database storage location.

The indexes against which searches are performed are on each application server, not the database server. The size of the index depends on both the size of the assets and whether the content of the assets are mostly text, which can be indexed, or binary content, which cannot be indexed. If you use large amounts of text and large asset files, the index size will be large.

The amount of disk space that the index needs depends on the type of assets, number of assets, level of user activity, and length of time that the repository has existed.

The size of the database depends on the size of asset descriptions and other repository activity, such as forums, tagging, and registered users. Metrics are recorded in the database for many user activities, such as searching and downloading. Even if you do not add assets to the repository, the database grows over time as user activity metrics are recorded. The size of the database increases in a linear fashion that is based on the repository usage.

If you plan to complete large file size uploads and downloads, follow these guidelines:

When users upload a large file, they should select the advanced upload utility in the Submit wizard on the Web.

Rational Asset Manager supports HTTP range requests, which Web clients use to resume an interrupted download or to download a file in portions. When users download a large file, they can use HTTP range requests by using a Web browser such as Firefox with the extension DownThemAll! (https://addons.mozilla.org/en-US/firefox/addon/201). Users might also consider changing large files into a set of smaller files.

The Rational Asset Manager Web application accesses the help application to deliver contextual assistance for pages, tools, and forms: An example of contextual help in the Rational Asset Manager Web application. Hover your mouse cursor over a Question Mark to see more information about a page, tool, or form.

If you require users to authenticate (for example, through the application server or an external firewall) to access the Rational Asset Manager help application, you must install the Rational Asset Manager help application on the same server as the Rational Asset Manager Web application.

Capacity and system planning example

Use the following numbers of users and assets as base configuration guidelines:

The following guidelines apply to both of the base configuration examples:

The assets are composed as follows:

This example is based on a workload of these user operations:

Table 2.
User action User activity Description
Keyword Search 48% Users search keywords and occasionally use a wildcard search.
Download Assets 20% Users search, locate, and download an asset.
Faceted Search 26% Users run faceted searches that return 10, 100, and 1000 assets, regardless of the repository size.
Submit Assets 1% Users create assets and upload content.
Communities Page 5% Users select the Communities tab and view the pages of a community.

If a workload includes more of complex operations, it supports fewer users for each application server; a lighter workload supports more users.

When you monitor system performance, you can review both the processor load and the index drive capacity to learn how load affects your Rational Asset Manager server and decide to add disks or a cluster server.

WebSphere Application Server clusters

A large IBM WebSphere Application Server cluster is composed of front end HTTP servers and proxy servers with a load balancer that directs requests around the cluster.

You can scale WebSphere Application Server both vertically and horizontally. Use a dedicated database server and file server. The degree to which WebSphere Application Server can be scaled and the number of servers that you can use depend on the type and magnitude of server requests and the number of assets.

Clustering topologies

Clustering is combining a group of machines into a logical entity that can be referenced as if it were one machine. This section describes various cluster configurations and the primary advantages and disadvantages of each.

Scalability

Scalability is how easily a site can expand. The number of users, assets, and communities for a given Rational Asset Manager installation must be able to expand to support an increasing load. The increasing load can come from many sources, such as adding additional teams or departments to the set of Rational Asset Manager users or importing large sets of historical assets into Rational Asset Manager.

Scalability is an architectural consideration that drives the design of your architecture. While you might improve scalability by adding additional hardware to your system, it might not improve performance and throughput.

The choice between scaling up (vertical clustering) and scaling out (horizontal clustering) is usually a decision of preference, cost, and the nature of your environment. However, application resiliency issues can change your preferences.

Availability

Also referred to as fault-tolerance or resiliency, availability is the ability of a system to provide operational continuity in spite of failed components and systems. Architectural decisions, such as horizontal versus vertical scaling and using backup load balancers (that is, dispatchers), can impact the availability of your Rational Asset Manager application. Consider availability for all shared resources, networks, and disk storage systems that compose your Rational Asset Manager environment. In a fault-tolerant design, if an application or server fails, other members of the cluster can continue to service clients.

There are two categories of failover: server failover and session failover. When server failover occurs, sessions on the failed cluster member are lost (a user will have to log in again) but services are still available to the clients. In session failover, the existing sessions are resumed by other members of the cluster as if the cluster member had not failed (although the last transaction can have been lost). If a redundant infrastructure is configured to support server failover, Rational Asset Manager will support it.

Integrations with Rational Asset Manager

If you want to integrate a IBM Rational Asset Manager installation with other software, such as IBM Rational ClearCase, IBM Rational ClearQuest, or IBM WebSphere Service Registry and Repository (WSRR), consider a common authentication strategy, such as LDAP or Active Directory.

Also consider the connectivity to each of the constituent components. If the products cross firewall boundaries, open the appropriate ports for each of the integrated products.

System maintenance

As you monitor your system, check Web server log files for errors and server restarts.

Also review system log files, which are in the following location: <install path>\IBM\WebSphere\AppServer\profiles\AppSrv01\logs

Backing up Rational Asset Manager

To prevent data loss, back up the IBM Rational Asset Manager database, the asset storage location, and (if you used Installation Manager) the Rational Asset Manager installation location. Also consider backing up your IBM WebSphere Application Server configuration.

You do not need to back up your indexes; Rational Asset Manager creates an index for you. Do not back up any /temp data.

Before you upgrade your system, perform the necessary back ups.

Upgrades to Rational Asset Manager

When you plan to upgrade your system, consider the path that your upgrade must follow. For example, do you plan to use IBM Installation Manager to install the media on your server, or do you plan to copy the media from other sources?

Pre-upgrade considerations:

For more detailed information on upgrading see Upgrading from a previous version on WebSphere Application Server

IBM Packaging Utility

Use IBM Packaging Utility software to copy product packages to a repository that can be placed on a Web server available over HTTP or HTTPS.

Packaging Utility software is located on the Enterprise Deployment CD for each platform (Windows and Linux) that is included with IBM Rational Asset Manager. If you want to place a repository that contains a Rational Asset Manager package on a Web server that will be available over HTTP or HTTPS, you must use Packaging Utility to copy the product package of Rational Asset Manager into the repository.

Use this utility to perform the following tasks:

Refer to the online help for Packaging Utility for full instructions using the tool.

Installing Packaging Utility

Before you can use the IBM Packaging Utility to copy the Rational Asset Manager product package, you must install the Packaging Utility from the Enterprise Deployment CD.

About this task

To install IBM Packaging Utility software from the Enterprise Deployment CD:

  1. Run the Enterprise Deployment CD for the appropriate platform and extract the compressed file from the CD.
  2. In the Packaging Utility directory, extract the Packaging Utility installation package from the compressed file (pu.disk_win32.zip or pu.disk_linux.zip).
  3. Locate the Packaging Utility installer executable file.
  4. Start the installer executable file and follow the instructions in the wizard to install the Packaging Utility.
  5. If Installation Manager is not detected on your workstation, you are prompted to install it and the installation wizard starts. To install Installation Manager, follow the instructions in the wizard.
  6. After Installation Manager is installed on your computer, Installation Manager starts and automatically begins the installation wizard.
  7. To complete the installation, follow the instructions in the installation wizard.

Installation requirements

This section details hardware and software requirements for successfully installing and running your software.

Hardware requirements

Before you can install the product, verify that your system meets the minimum hardware requirements.

Select the current version of IBM Rational Asset Manager from this link: http://www-01.ibm.com/support/docview.wss?rs=3263&uid=swg27014356 and click the Hardware section on the system requirements page.

Software requirements

Before installing the product, verify that your system meets the software requirements.

Select the current version of IBM Rational Asset Manager from this link: http://www-01.ibm.com/support/docview.wss?rs=3263&uid=swg27014356 to view the requirements.

Application Server (for server)

You can install Rational Asset Manager server that includes an embedded version of IBM WebSphere Application Server or you can install Rational Asset Manager server on one of the supported application servers.

For WebSphere Application Server, both Network Deployment and clustered deployments are supported.

Database application (for server)

A database application is required for the Rational Asset Manager server. You can use any of the supported databases in conjunction with an installation of Rational Asset Manager server installed on any of the supported application servers.

Web browser

A supported Web browser is required to run the Rational Asset Manager Web client, to view the documentation, and to support the Eclipse Standard Widget Toolkit (SWT) browser widget.

Additional software requirements

User privileges requirements

You must have a user ID that meets the following requirements before you can install IBM Rational Asset Manager.

Pre-installation tasks

Before you install the product, complete these steps:

  1. Confirm that your system meets the requirements that are described in the section Installation requirements.
  2. Confirm that your user ID meets the required access privileges for installing the product. See User privileges requirements.
  3. Read the topic Planning your installation.

What to do next

You can install IBM Rational Asset Manager either by using IBM Installation Manager or by using the deployment .zip files and installing them manually. If you are using Installation Manager, you can use the GUI or install silently by using the command line.

Installing from download

After obtaining the installation files, extract the contents.

About this task

You install IBM Rational Asset Manager manually by downloading the .zip files and then extracting the contents of the compressed files to your file system.

If you download the installation files from IBM Passport Advantage®, you must extract the image from the compressed files before you can install Rational Asset Manager.

If you select the Download Director option for downloading the installation files, the Download Director applet automatically verifies the completeness of each file that it processes.

Extracting the files

About this task

Extract each compressed file to the same directory. For Linux. Do not include spaces in the directory names, or you will not be able to run the launchpad.sh command to start the launchpad from a command line.

Installing from the launchpad program

The launchpad program provides you with a single location to view release information and start the installation process.

Before you begin

About this task

Use the launchpad program to start the installation of IBM Rational Asset Manager in the following cases:

By starting the installation process from the launchpad program, IBM Installation Manager is automatically installed if it is not already on your computer, and it starts preconfigured with the location of the repository that contains the Rational Asset Manager package. If you install and start Installation Manager directly, then you must set repository preferences manually.

Starting the launchpad program

If you are installing from a CD and autorun is enabled on your workstation, then the Rational Asset Manager launchpad starts automatically when you insert the first installation disc into your CD drive. If you are installing from an electronic image, or if autorun is not configured on your workstation, then you must start the launchpad program manually.

Before you begin

Complete the preinstallation tasks described in Pre-installation tasks, if you have not done so already.

About this task

To start the launchpad program:

  1. Insert the IBM Rational Asset Manager CD into your CD drive. For Linux. Ensure that you have mounted the CD drive.
  2. If autorun is enabled on your system, the IBM Rational Asset Manager launchpad program automatically opens. If autorun is not enabled on your system:

Starting an installation from the launchpad program

  1. Start the launchpad program.
  2. If you have not done so already, read the release information by clicking Release notes.
  3. When you are ready to begin the installation, click Install IBM Rational Asset Manager.
  4. If IBM Installation Manager is not detected on your system or if an older version is already installed, then you must continue with the installation of the latest release of it.
    1. Follow the instructions in the wizard to complete the installation of Installation Manager. Refer to Installing Installation Manager on Windows for more information.
    2. When the installation of Installation Manager completes successfully, click Finish to close the wizard. After the installation is complete, Installation Manager opens automatically.
  5. If this is a new installation, click Install and follow the instructions in the wizard to complete the installation process. For complete details, see Installing Rational Asset Manager server by using Installation Manager
  6. If this is a product update, you must start Installation Manager that you already have installed and then select Update and choose the Rational Asset Manager offering to check for updates. For complete details, see Upgrading from a previous version on WebSphere Application Server.

Installing from the IBM Installation Manager

IBM Installation Manager is a program that helps you install the product packages on your computer.

Installation Manager also helps you update, modify, and uninstall any package that you install. A package can be a product, a group of components, or a single component that is designed for Installation Manager to install.

In most installation scenarios for IBM Rational Asset Manager, you use Installation Manager. Rational Asset Manager usually requires the most recent version of IBM Installation Managerat the time of release.

You can use the Installation Manager GUI to install Rational Asset Manager or you can install silently from the command line by using a response file.

For more information about IBM Installation Manager, visit the Installation Manager information center at http://publib.boulder.ibm.com/infocenter/install/v1r2/index.jsp.

Working with IBM Installation Manager

About this task

This section deals with some common tasks relating to IBM Installation Manager. For more information, see the Installation Manager online help or the Installation Manager Information Center at http://publib.boulder.ibm.com/infocenter/install/v1r2/index.jsp.

Installing Installation Manager on Windows

About this task

If you start the installation of your product from the launchpad program, then the installation of Installation Manager is started automatically if it is not already installed on your workstation. (For more information on this process, refer to Installing from the launchpad program.) In other cases, you must manually start the installation of Installation Manager.

To start the installation of Installation Manager manually:

  1. Run install.exe from the InstallerImage_win32 folder on the first installation disk.
  2. Click Next on the Install Packages page.
  3. Review the license agreement on the License Agreement page and select I accept the terms in the license agreement to accept. Click Next.
  4. Click the Browse button on the Destination Folder page to change the installation location if required. Click Next.
  5. Click Install on the Summary page. When the installation process is complete, a message confirms the success of the process.
  6. Click Finish. Installation Manager opens.

Installing Installation Manager on Linux and AIX

About this task

IBM Installation Manager is installed by the launchpad. For more information on this process, refer to Installing from the launchpad program.

To install Installation Manager manually:

  1. Open a terminal window with root user privileges.
  2. Run install.
  3. Click Next on the Install Packages screen.
  4. Review the license agreement on the License Agreement page and select I accept the terms in the license agreement to accept. Click Next.
  5. If necessary, edit the installation directory location. Click Next.
  6. Click Install on the information summary page. When the installation process is complete, a message confirms the success of the process.
  7. Click Finish. IBM Installation Manager opens.

Starting Installation Manager on Windows

About this task

Installation Manager should be started from the launchpad program. Doing so starts Installation Manager with a configured repository preference and selected Rational Asset Manager packages. If you start Installation Manager directly, then you must set a repository preference and choose product packages manually. For more information, see Planning your installation.

To start Installation Manager manually:

  1. Open the Start menu from the Taskbar.
  2. Select All Programs -> IBM Installation Manager -> IBM Installation Manager.

What to do next

Starting Installation Manager on Linux and AIX

About this task

Installation Manager should be started from the launchpad program. Doing so starts the Installation Manager with a configured repository preference and selected Rational Asset Manager packages. If you start Installation Manager directly, then you must set repository preference and choose product packages manually. For more information, see Planning your installation.

To start Installation Manager manually:

  1. Open a terminal window with root user privileges.
  2. Change directory to the installation directory for Installation Manager (by default, /opt/IBM/InstallationManager/eclipse) and run IBMIM.

Uninstalling Installation Manager on Windows

About this task

To uninstall Installation Manager:

  1. Open the Start menu from the Taskbar.
  2. Select All Programs -> IBM Installation Manager -> Uninstall IBM Installation Manager.
  3. Click Next on the Uninstall page. The IBM Installation Manager is selected for uninstallation.
  4. Click Uninstall in the Summary page.

Results

Note: You can also uninstall Installation Manager by using the Control Panel. Click Start -> Settings -> Control Panel, and then double-click Add or Remove Programs. Select the entry for IBM Installation Manager and click Remove.

Uninstalling Installation Manager on Linux and AIX

About this task

Installation Manager must be uninstalled using the package management tool that is included with your Linux or AIX version.

To uninstall Installation Manager manually on Linux or AIX:

  1. Open a terminal window with root user privileges.
  2. Change directory to the uninstallation directory of Installation Manager. By default, this is /var/ibm/InstallationManager/uninstall. If Installation Manager has been installed to a location other than the default path, locate the uninstall directory relative to where Installation Manager is installed.
  3. Run ./uninstall.

Silently installing and uninstalling Installation Manager

IBM Installation Manager can be silently installed and uninstalled.

Silently installing Installation Manager on Windows

About this task

To silently install Installation Manager onto a default install location on Windows:

  1. Change directory to InstallerImage_win32 folder on the first installation disk.
  2. Run setup.exe /S /v"/qn"

What to do next

If you want to change the install location, you can add the INSTALLDIR property inside the /v option. For example: setup.exe /S /v"/qn INSTALLDIR=\"C:\InstallationManager\""

Silently uninstalling Installation Manager from Windows

About this task

To silently uninstall Installation Manager on Windows:

Run the following command in the command prompt: msiexec /x {DBD90D51-BD46-41AF-A1F5-B74CEA24365B}

Installation repositories for Installation Manager

IBM Installation Manager retrieves product packages from specified repository locations.

If the launchpad is used to start Installation Manager, the repository information is passed to Installation Manager. If the Installation Manager is started directly, you must specify an installation repository that contains the product packages that you want to install. See Setting installation repository preferences in Installation Manager.

Some organizations bundle and host their own product packages on their intranet. For information about this type of installation scenario, see the IBM Installation Manager online help. Your system administrators will need to provide you with the correct URL.

By default, IBM Installation Manager uses an embedded URL in each Rational software development product to connect to a repository server over the Internet. Installation Manager then searches for the product packages as well as new features.

Setting installation repository preferences in Installation Manager

When you start the installation of IBM Rational Asset Manager from the launchpad program, the location of the repository that contains the product package you are installing is automatically defined in IBM Installation Manager when it starts. However, if you start Installation Manager directly (for example, installing Rational Asset Manager from a repository located on a Web server) then you must specify the repository preference (the URL for the directory that contains the product package) in Installation Manager before you can install the product package. Specify these repository locations on the Repositories page of the Preferences window. By default, Installation Manager uses an embedded URL in each Rational software development product to connect to a repository server through the Internet and search for installable packages and new features. Your organization may require you to redirect the repository to use intranet sites.

Before you begin

Note: Before starting the installation process, be sure to obtain the installation package repository URL from your administrator.

About this task

To add, edit, or remove a repository location in Installation Manager:

  1. Start Installation Manager.
  2. On the Start page of Installation Manager, click File -> Preferences, and then click Repositories. The Repositories page opens, showing any available repositories, their locations, and whether they are accessible.
  3. On the Repositories page, click Add Repository.
  4. In the Add repository window, type the URL of the repository location or browse to it and set a file path.
  5. Click OK. If you provided an HTTPS or restricted FTP repository location, then you will be prompted to enter a user ID and password. The new or changed repository location is listed. If the repository is not accessible, a red x displays in the Accessible column.
  6. Click OK to exit.

What to do next

Note: For Installation Manager to search the default repository locations for the installed packages, ensure the preference Search service repositories during installation and updates on the Repositories preference page is selected; this preference is selected by default.

Installing IBM DB2 Enterprise Server Edition, version 9.5

IBM Rational Asset Manager requires a database application. If you do not already have one of the supported database applications installed, then you can install IBM DB2 Enterprise Server Edition, version 9.5 which is included with the Rational Asset Manager installation media.

About this task

Installation instructions and release notes, as well as information about working with DB2 are available in the IBM DB2 Database for Linux, UNIX®, and Windows Information Center. See http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp.

To start an installation of DB2 Enterprise Server Edition, version 9.5:

  1. Start the DB2 Setup Launchpad program. From the Rational Asset Manager launchpad program, click Install IBM DB2 Enterprise Server Edition, Version 9.5. If you are installing from CD media, you might be prompted to insert the first DB2 installation CD. The DB2 Setup Launchpad starts.
  2. Make sure that you have read the release information that is available in the DB2 Setup Launchpad or in the information center.
  3. In the left menu, click Install a product, and then in the page that opens, under DB2 Enterprise Server Edition, click Install new. The DB2 Setup wizard opens.
  4. Follow the instructions in the wizard to complete the installation. For more information, see the installation instructions in the IBM DB2 Database for Linux, UNIX, and Windows Information Center or click Help in the DB2 Setup wizard.

What to do next

You must register your license key for DB2. To do so, see Registering the DB2 license key.

Registering the DB2 license key

The IBM DB2 Enterprise Server Edition, Version 9.5 license key must be registered using the db2licm command.

About this task

The DB2 product uses the license key information contained in the nodelock file. The nodelock file is created or updated by running the db2licm command and specifying the license file for the DB2 product. Creating or updating the nodelock file is referred to as registering the DB2 product license key.

The DB2 product uses the license key information that is contained in the nodelock file, which is created or updated by running the db2licm command and specifying the license file for the DB2 product. To register the license key, you must run the db2licm command on each computer where DB2 is installed.

To manually register your DB2 product license key using root authority:

  1. Log in as a user with root authority.
  2. Register the DB2 product license key with the appropriate command: where filename is the full pathname and filename for the license file that corresponds to the product you are bundling.

For example, on AIX, if the CD-ROM is mounted in the /cdrom directory and the name of the license file is db2ese_o.lic, the command should be: /usr/opt/db2_08_01/adm/db2licm -a /cdrom/db2/license/db2ese_o.lic

After running the db2licm command, the DB2 product license key information is contained in the nodelock file in the following directories:

To register your DB2 product license key as the instance owner:

  1. Create the instance environment and become the instance owner.
  2. Register your DB2 product license with the appropriate command: where db2instance_path is where the DB2 instance was created and filename is the full pathname and filename for the license file that corresponds to the product that you are bundling.

Installing Rational License Server

To distribute license keys to clients, IBM Rational Asset Manager server uses the IBM Rational License Server.

About this task

To install and configure Rational License Server for Rational Asset Manager:

  1. Install IBM Rational License Server.

    If you use Rational License Server version 7.0 or earlier, upgrade to the Rational License Server for Windows version 7.0.1 or the Rational License Server for UNIX and Linux version 7.0.0.1. Rational License Server 7.0.1 and 7.0.0.1 are compatible with your previously installed license keys and will continue to service your existing client computers.

    Rational License Server is included with the Rational Asset Manager installation media.

    License Management Guide for information on installing and configuring the license server:

    See the Rational License Server delivery and support Web page for an overview: http://www-01.ibm.com/support/docview.wss?uid=swg21265239

  2. Request and install your license keys.

    The number of license keys that are available determines the number of users that can be simultaneously logged in to the Web application.

    To upgrade, you need to file a request for a new license key. You need to acquire a new server license and new user authorized licenses.

    For more information on Rational licensing and to get your Rational Asset Manager license keys, see the Rational licensing support page at http://www.ibm.com/software/rational/support/licensing/.

  3. Start the Rational License Server. See the IBM Rational License Management Guide or the License Key Administrator Help.
  4. After you have deployed the Rational Asset Manager applications to your application server, configure Rational Asset Manager server to communicate with Rational License Server.

    You can configure Rational Asset Manager server to communicate with Rational License Server by either manual configuration or by using the Rational Asset Manager server setup application. For instructions to install Rational Asset Manager and use the server setup application, see Deploying and configuring application files by using the server setup application. For instructions to manually configure Rational Asset Manager server to communicate with the license server, see Configuring the Rational Asset Manager server application.

Enabling application security on WebSphere Application Server V6.1

If you are installing to an existing IBM WebSphere Application Server, version 6.1, application security must be enabled. If application security is not enabled, the IBM Rational Asset Manager server setup application will be unable to make any configuration changes for IBM WebSphere Application Server.

  1. In the WebSphere Application Server Administrative Console, click Security.
  2. Make sure Enable application security is checked.
  3. Click Apply.
  4. Click Save.

Installing Rational Asset Manager

This section discusses the steps to upgrade IBM Rational Asset Manager, to install it with embedded IBM WebSphere Application Server, version 6.1, and to install it to an existing installation of WebSphere Application Server or Apache Tomcat server.

About this task

Note: As of version 7.2, only the server setup application is installed using IBM Installation Manager. You then use the server setup application to complete the installation.

Installing Rational Asset Manager server by using Installation Manager

You can install the IBM Rational Asset Manager server setup application, which you will use to deploy all other applications, by using IBM Installation Manager. You can install the server application with an embedded version of IBM WebSphere Application Server, or on an existing version of WebSphere Application Server, Version 6.1. You can install to a single node or to a cluster.

Before you begin

If you are installing to Apache Tomcat or you do not want to use Installation Manager, see Retrieving the server application files directly from the installation media.

If you do not have access to a graphical user interface, you can use response scripts over the command line.

Before you install Rational Asset Manager, make sure that the database application (DB2,Oracle, or SQL Server) is installed and running.

For WebSphere:If you are installing to an existing WebSphere Application Server, make sure the application server or cluster is running. You must run Installation Manager on the same server as the application server, or for a network-deployed cluster, on the server that is running the deployment manager.

  1. Start the Rational Asset Manager launchpad program (see Installing from the launchpad program). To use a different language, select a language from the Select a language list.
  2. Click Install IBM Rational Asset Manager server. Installation Manager launches, and the Install wizard opens.
  3. If you are installing from the launchpad program, go to step 7.
  4. If Installation Manager is already installed on your system but you do not have the latest version, the latest version of Installation Manager appears; select it and continue through the Install wizard to update Installation Manager.
  5. To search for available updates to the Rational Asset Manager server package, click Check for Other Versions and Extensions.
    Note: To use Installation Manager to search the predefined IBM update repository locations for the installed packages, on the File -> Preferences -> Repositories preferences page, select Search service repositories during installation and updates. This preference is selected by default. To search, you must be connected to the Internet.
    Installation Manager searches for updates in the predefined service repository for the product package. It also searches any other repository locations that you have set. You can install updates at the same time that you install the base product package.
  6. If updates are found for the Rational Asset Manager server package, they are displayed after their corresponding products in the Installation Packages list on the Install Packages page. By default, only the latest updates are displayed. To see other versions of packages, select Show all versions.
  7. In the Installation Packages window, expand IBM Rational Asset Manager server and select Version 7.2. Updates that have dependencies are automatically selected and cleared together.
    Note: If you install multiple packages at the same time, all of the packages install into the same package group.
  8. Click Next.
  9. On the Licenses page, read the license agreement for the selected package. If you selected to install more than one package, there might be a license agreement for each package. To display each license agreement, select each package version. The package versions that you selected to install (for example, the base package and an update) are listed under the package name.
    1. If you agree to the terms of each license agreement, click I accept the terms of the license agreements.
    2. To continue, click Next.
  10. On the Location page, either type the path for the shared resources directory in the Shared Resources Directory field or accept the default path. The shared resources directory contains resources that package groups can share. To continue, click Next.

    Default paths:

    Important: You can specify the shared resources directory only the first time that you install a package. To ensure that adequate space is available for the shared resources of packages, use your largest disk for this directory. You cannot change the directory location unless you uninstall all packages.
  11. On the Location page, either choose an existing package group to install the Rational Asset Manager server package into or create a new one. A package group represents a directory in which packages share resources. To create a package group:
    1. Click Create a new package group.
    2. Type the path for the installation directory for the package group. The name for the package group is created automatically.

      Default paths:

      • For Windows: C:\Program Files\IBM\RAM72Server
      • For Linux: For AIX: For Linux for zSeries:/opt/IBM/RAM72Server
    3. To continue, click Next.
  12. On the Features page, select IBM Rational Asset Manager server 7.2.
  13. On the next Features page, in the Select application server list, select the application server:
  14. If you selected Packaged embedded WebSphere Application Server, indicate the server configuration to use:
    1. Specify the embedded WebSphere Application Server ports, or use the default port assignments. The Available column indicates whether the port is already in use or not.
      Table 3. Default port definitions for embedded WebSphere Application Server V6.1
      Port name Default value
      HTTP Transport Port (WC_defaulthost) 13080
      Administrative Console Port (WC_adminhost) 13060
      HTTPS Transport Port (WC_defaulthost_secure) 13443
      Administrative Console Secure Port (WC_adminhost_secure) 13043
      Bootstrap Port (BOOTSTRAP_ADDRESS) 13809
      SOAP Connector Port (SOAP_CONNECTOR_ADDRESS) 13880
    2. Click Next.
    3. On the Context Root page, in the Rational Asset Manager Setup Server field, type a context root for theRational Asset Manager server setup application. A context root identifies the location of a web application on the server. For example, if you use the default context root ram.setup on a server with a domain of www.example.com, you would access the server setup application in a web browser at the URL www.example.com/ram.setup
    4. Click Next and proceed to step 16
  15. If you selected WebSphere Application Server, indicate the server configuration:
    1. In the Application server profile location field, type the full path to the application server on the local computer, or click Browse and navigate to the application server profile location. (For a Network Deployment cluster, select the application server that the deployment manager application is running on.) For example, on a full installation of WebSphere Application Server, enter C:\Program Files\IBM\WebSphere\AppServer\profiles\<profile_name> (where profile name is the name of the profile on the server or the deployment manager for a cluster). For an installation of embedded WebSphere Application Server that is installed with Rational Asset Manager, by default this is C:\Program Files\IBM\RAM71Server\ram\ewas\profiles\profile1.
    2. In the Server root URL text field, type the root URL for the server (that is, the root URL to the server hosting the WebSphere Application Server administrative console). By default, this URL is http://localhost:9080. If you use a different port number for your WebSphere Application Server administrative console for the profile that you selected in step 14a (for example, if security is enabled, or if there are multiple profiles on the application server), enter that port number in place of 9080. For a cluster, the default port for the deployment manager is 9060.
    3. If security is enabled on your application server, type an administrator's user name and password. If security is not enabled, clear the check box.
    4. In the Type of server configuration section, indicate whether you are installing a single server or a network deployment cluster, and provide the server or cluster name. The server must be identified in the Server Configuration section and must be running.
    5. If you are installing to a single server, click the Get list from server button.
      • For single server node installations, the name of the server is displayed in the text field (for example, server1).
    6. Click Next.
    7. On the Context Root page, in the Rational Asset Manager Setup Server field, type a context root for theRational Asset Manager server setup application. A context root identifies the location of a web application on the server. For example, if you use the default context root ram.setup on a server with a domain of www.example.com, you would access the server setup application in a web browser at the URL www.example.com/ram.setup
  16. On the Summary page, review your choices. To change choices or configuration details, click Back, and make your changes.
  17. When you are satisfied with your installation choices, click Install. An indicator shows the progress of the installation and can take several minutes.
  18. When the installation process is complete, a message confirms the success of the process. To return to the Start page of Installation Manager, click Finish.

Results

Note:

If you installed the embedded WebSphere Application Server on Windows or Linux and you want to run WebSphere Application Server as a service, see Configuring the embedded WebSphere Application Server as a service (Windows and Linux only).

The Rational Asset Manager Configuration Web page opens in a browser window. Follow the instructions to start the server (or restart the server, if it was already running) and then click the link to start the Rational Asset Manager server setup application. The server setup application is a wizard that deploys the other enterprise archive and Web archive files and configures the database, the database connection, security, and repository settings. For instructions to use the server setup application, see the Deploying and configuring application files by using the server setup application section.

What to do next

For DB2: If you are using DB2

If you are using DB2, the server setup application can create and configure the databases for you. See Deploying and configuring application files by using the server setup application.

For Oracle: For SQL Server: If you are using Oracle or Microsoft SQL Server

Create the databases for assets and lifecycles. See Creating and configuring databases for Rational Asset Manager.

Installing silently with Installation Manager

You can install IBM Rational Asset Manager from the command line using response files rather than using the IBM Installation Manager graphical user interface.

You can install silently by using a response file from the command line. There are sample response files included on the installation media or installed to be used for silent installs. The sample response files are on installation media in the disk1/sample_response_files folder and they are also installed in the /sample_response_files directory. The sample files are:

Each file includes comments that help describe how you must modify it for your specific installation.

For information on using response files to silently install the product, see http://publib.boulder.ibm.com/infocenter/install/v1r2/topic/com.ibm.silentinstall12.doc/topics/c_silent_install_over_IM.html

Manually deploying and configuring Rational Asset Manager on an existing application server

If you want to use your existing IBM WebSphere Application Server or cluster environment, follow these steps to manually install and configure IBM Rational Asset Manager.

About this task

The following list is the order of the steps to deploy and configure Rational Asset Manager for use with an existing application server. In general, you will be completing the following tasks:

  1. Create a database for assets.
  2. Create a database for lifecycles.
  3. For WebSphere:On WebSphere Application Server, you will:
    1. Deploy the server setup application:
    2. Use the server setup application to deploy the other application and configure Rational Asset Manager
  4. On Tomcat you will:
    1. Deploy the applications and configure the database connections.
    2. Configure the Rational Asset Manager application.

Retrieving the server application files directly from the installation media

The installation media contain .zip files for every supported operating system that contain all of the required files for manually installing and configuring IBM Rational Asset Manager.

Before you begin

You must have downloaded the installation media for Rational Asset Manager and extracted all of the .zip files to the same directory.

About this task

The installation media contains a .zip file for every supported operating system and application server that contains the following files:

Note: The application files and scripts for Rational Asset Manager are specific for each operating system.

  1. On the installation media, or through the IBM download site, or in the download package from Passport Advantage, locate the appropriate .zip files for your operating system and application server.

    The .zip files have the following naming convention: com.ibm.ram.manual.deploy.<application_server>.<operating_system>_<version_number>.disk1.zip, where <application_server> will be either was for WebSphere Application Server, or tomcat for Apache Tomcat.

  2. Extract the appropriate .zip file for your operating system to a local disc image. Each .zip file contains all the files that are required for the appropriate operating system

Results

For a manual installation you must now:

The extracted .zip files contain the following files:

Table 4. List of installation files for Rational Asset Manager server in .zip files for deploying manually
Disc Path File names Description
.was only <extracted .zip location>\apps\was
  • com.ibm.ram.repository.setup.web.ear
  • com.ibm.ram.repository.web_runtime.ear
  • iehs_war.ear
  • rmcabdgovernprocess_war.ear
  • RTC-server.zip
Rational Asset Manager .ear application files, and the included IBM Rational Team Concert server application that is required for managing asset lifecycles
.tomcat only <extracted .zip location>\apps\tomcat
  • com.ibm.ram.repository.web.tomcat_runtime.war
  • com.ibm.ram.repository.web.ws.tomcat_runtime.war
  • iehs.war
  • rmcabdgovernprocess.war
  • RTC-Server.zip
  • sharedLib.zip
Rational Asset Manager Web Archive files and shared library files for Tomcat
.was only <extracted .zip location>\conf\bin
  • deployClusterSetup.py
  • UninstallSetup.py
Files for deploying or uninstalling the server setup application to a IBM WebSphere Application Server cluster.
.was only <extracted .zip location>\conf\cq
  • linkscript.py
A file to help you configure a connection between Rational Asset Manager and IBM Rational ClearQuest.
Both <extracted .zip location>\DatabaseScripts com.ibm.ram.lifecycle.zip A file to populate the database tables for the database for asset lifecycles that is used by the internal version of Rational Team Concert.
Both <extracted .zip location>\DatabaseScripts\DB2
  • bootStrap_DB2.sql
  • dbcreate.sql
  • dbcreate_populate.bat
  • dbcreate_populate.sh
  • dbcreate_populate_zLinux.sh
  • RAMSCHEMA_DB2.sql
Files for creating and populating a DB2 database for Rational Asset Manager.
Both <extracted .zip location>\DatabaseScripts\Oracle
  • bootStrap_Oracle.sql
  • RAMSCHEMA_Oracle.sql
Files for creating and populating an Oracle database.
Both <extracted .zip location>\DatabaseScripts\SQLServer
  • bootStrap_SQLServer.sql
  • RAMSCHEMA_SQLServer.sql
Files for creating and populating a Microsoft SQL Server database.

Creating and configuring databases for Rational Asset Manager

If your database software is installed and the database server is running, you can create and configure a database either prior to installing IBM Rational Asset Manager, or while using the Rational Asset Manager server setup application. If you are using IBM DB2, the server setup application can create the databases for you.

For WebSphere: For DB2: If you are using IBM WebSphere Application Server and DB2 and choose to create your database with the Rational Asset Manager server setup application, skip this section.

Creating and populating the database for assets

Creating and populating database tables for assets in DB2 with batch files

Use batch files and database scripts to create and populate tables in IBM DB2 for IBM Rational Asset Manager.

Before you begin

If you are using IBM WebSphere Application Server and will be using the server setup application, you can skip this task because the server setup application can create and configure the databases for you.

If you prefer to create the database and tables manually, see Creating and populating database tables for assets in DB2 manually.

You can create the database and tables automatically by running batch files. DB2 must already be installed and running. Ensure that you know the location of the SQL scripts that are included in the installation media. The location is install location\ram\DatabaseScripts\DB2 if you installed by using Installation Manager. You must also know the installation directory for DB2 (typically C:\Program Files\IBM\SQLLIB for Windows and opt/IBM/DB2/V9.5 for Linux, AIX, or Linux for zSeries.

You will use the following scripts:

  1. If you are installing from the CD, then copy the SQL scripts to your local file system.
  2. For Linux: For AIX: For Linux for zSeries: Check that you have write permission for the directory containing the SQL scripts.
  3. In a command line, change to the directory containing the SQL scripts for DB2 (path to installation media\ db_scripts\DB).
  4. Run the following batch file:
  5. When prompted, enter the name of the database or press the Enter key to accept the default database name (RAMDB).
  6. At the next prompt, enter the installation directory path for DB2, or press the Enter key to accept the default value (C:\Program Files\IBM\SQLLIB for Windows, and /opt/IBM/DB2/V9.5 for Linux, AIX, or Linux for zSeries.
  7. The batch file runs. The script performs the following actions:
    Note: When you run the batch file for the first time, you might see a number of SQL0204N error messages that name is an undefined name, and they will be similar to the following example:
    ** CLI error in executing the SQL statement:
    (-204): [IBM][CLI Driver][DB2/NT] SQL0204N  "RAMSCHEMA.FORUM" is an undefined name.  SQLSTATE=42704
    If you are running the batch file for the first time, then you can safely ignore these messages.
  8. Verify that the tables were created. For example, start the DB2 Control Center and browse for the RAMDB database. Verify that the database and tables were created.

What to do next

Next, create the database for lifecycle management. See Creating a database for asset lifecycles in DB2.

Creating and populating database tables for assets in DB2 manually

These are the instructions for manually configuring IBM DB2 and creating and populating tables for IBM Rational Asset Manager in DB2.

Before you begin

If you are using IBM WebSphere Application Server and will be using the server setup application, you can skip this task because the server setup application can create and configure the databases for you.

DB2 must already be installed and running. Also, make sure that you know the location of the SQL scripts that are included with the installation media (typically, path to installation media\ db_scripts\DB2). Finally, ensure that you also know the installation directory for DB2 (typically C:\Program Files\IBM\SQLLIB for Windows, opt/ibm/DB2/V9.5 for Linux and /opt/IBM/db2/V9.5 for AIX.

About this task

You can optionally use batch scripts to simplify this process. See Creating and populating database tables for assets in DB2 with batch files.

To configure DB2 and create the database tables:

  1. Start the DB2 Control Center.
  2. Select the instance of the database.
  3. Create and add a new database.
    1. Click Tools -> Command Editor.
    2. In the command editor, type (in uppercase):
      ATTACH TO <DATABASE_INSTANCE>
      (where <DATABASE_INSTANCE> is the name of the database instance you selected in step 2)
    3. Click Execute.
    4. Clear the previous command from the command editor and type (in uppercase):
      CREATE DATABASE <DATABASE_NAME> AUTOMATIC STORAGE YES USING CODESET UTF-8 TERRITORY US
      (where <DATABASE_NAME> may be any name you choose; for example, RAMDB)
    5. Click Execute.
    6. Click Add, select the database you just created, and click OK.
  4. Execute the dbcreate.sql script.
    1. Click Open.
    2. Navigate to the dbcreate.sql file.
    3. Click OK.
    4. Click Yes.
    5. Click Execute.
  5. Execute the RAMSCHEMA_DB2.sql script.
    1. Click Open.
    2. Navigate to the RAMSCHEMA_DB2.sql file.
    3. Click OK.
    4. Click Yes.
    5. In the Statement termination character text field, in place of the default semi-colon character ( ; ), type a caret ( ^ ).
    6. Click Execute.
  6. Execute the bootstrap_DB2.sql script.
    1. Click Open.
    2. Navigate to the bootstrap_DB2.sql file.
    3. Click OK.
    4. Click Yes.
    5. In the Statement termination character text field, in place of the caret ( ^ ), type a semi-colon ( ; ).
    6. Click Execute.
  7. Verify that the tables were created.
    1. Click Object View and open the database instance.
    2. Click Tables to verify that the tables contain data.

What to do next

Next, create the database for lifecycle management. See Creating a database for asset lifecycles in DB2.

Creating and populating the database for assets in Oracle 11g or 10.2(g)

These are the instructions for manually creating and populating tables for IBM Rational Asset Manager in Oracle 11g or 10.2(g).

Before you begin

Oracle must already be installed and running. Also, make sure that you know the location of the SQL scripts (typically, <path to installation media> \db_scripts\Oracle).

About this task

To create the database tables:

  1. Using the Oracle Database Configuration Assistant, follow the steps in the wizard to create a new database.
    1. Use global database name ramdb_<your domain>, and a system identifier (SID) ramdb.
    2. On the Custom Scripts tab, do not run the SQL scripts that are mentioned in the later steps. You must create a user account first.
    3. On the Character Sets page, select Use Unicode (AL32UTF8).
    4. Also on the Character Sets page, for National Character Set, select UTF8 - Unicode 3.0 UTF-8.
    5. Complete the other pages in the wizard, accepting the default values.
  2. Create a database user:
    1. Open Database Control.
    2. Navigate to the Users page. (In Oracle 10.2(g), click Administration, then Users; in Oracle 11(g), click Server, then in the Security section click Users.)
    3. Create a user named RAMSCHEMA that meets the following qualifications:
      • The user has the RESOURCE and CONNECT roles.
      • The user's quota setting is unlimited.
      • For tablespace, you can use any default tablespace (with the exception of Temp) that meets the access level requirements for the user that you created.
      Tip: Oracle provides a default user named "Scott" that has the appropriate permissions. You can use this default user as the basis for your new user account.
  3. Run the scripts that will populate the database. (This step is not necessary if you are using the server setup application; the server setup application will run the scripts for you.)
    1. Click SQL+ to open it.
    2. Open the RAMSCHEMA_Oracle.sql file in the sqlscripts/oracle folder. Highlight the entire contents of the file, copy them (right-click, and then Copy), and then paste them into the top of the SQL+.
    3. Click Execute. When the process finishes, delete the commands from the top window.
    4. Repeat these steps for the bootStrap_Oracle.sql file.
  4. Verify that the tables were created.

What to do next

Next, create the database for lifecycle management. To do so, see Creating a database for asset lifecycles in Oracle.

Creating and populating a database for assets in Microsoft SQL Server 2005

These are the instructions for manually creating and populating tables for IBM Rational Asset Manager in Microsoft SQL Server 2005.

Before you begin

SQL Server 2005 must already be installed and running. Also, make sure that you know the location of the SQL scripts (typically, path to installation media\db_scripts\SQLServer).

About this task

To create the database tables:

  1. Ensure that your ID has permission to execute CREATE SCHEMA statements. (Typically, the database owner has this permission.)
  2. Create a new database with database name RAMDB. The default collation option for SQL Server is case-insensitive and must be changed to case-sensitive to work correctly with Rational Asset Manager. You must select a collation sequence that ends with_BIN2 (for example, Latin1_General_BIN2).

    From the command line tool, type:

    CREATE DATABASE RAMDB COLLATE collation

    where collation is where you specify a collation sequence. For example:

    CREATE DATABASE RAMDB COLLATE SQL_Latin1_General_BIN2 
  3. Execute the scripts that will populate the database.
    1. Open a command prompt.
    2. Type sqlcmd -d RAMDB -i path to SQL scripts\RAMSCHEMA_SQLServer.sql (where RAMDB is the name of the database that you created in step 2), and press Enter.
    3. Type sqlcmd -d RAMDB -i path to SQL scripts\bootStrap_SQLServer.sql (where RAMDB is the name of the database that you created in step 2), and press Enter.
  4. Verify that the tables were created.

What to do next

Next, create the database for lifecycle management. To do so, see Creating a database for asset lifecycles in Microsoft SQL Server.

Creating a database for asset lifecycles

You must create a second database for custom asset lifecycles.

About this task

For WebSphere: For DB2: If you are using IBM WebSphere Application Server and DB2 and choose to create your database with the Rational Asset Manager server setup application, skip this section.

Creating a database for asset lifecycles in DB2

Create a database for lifecycle management in IBM DB2 for IBM Rational Asset Manager This database will be used by the included version of IBM Rational Team Concert.

Before you begin

If you are using IBM WebSphere Application Server and will be using the server setup application, you can skip this task because the server setup application can create and configure the databases for you.

Ensure that you also know the installation directory for DB2 (typically C:\Program Files\IBM\SQLLIB for Windows and opt/IBM/DB2/V9.5 for Linux, AIX, and Linux for zSeries.

About this task

To set up the DB2 database:

  1. Create the database in the DB2 Command Window. The following example commands create a new database called RTCDB. These commands run in the DB2 Command Window. The Command Window can be opened from the application Start menu under the DB2 Command Line Tools menu.
    Note: To ensure proper handling of Unicode content, the database character set must be UTF-8 encoding.
    Tip: If the database is not running, the command db2start starts DB2.
  2. For DB2 v9.1 only: You must increase the APP_CTL_HEAP_SZ setting from its default of 128 to 1024. You will have to restart your database server:
    1. In the DB2 Command Window, type the following command:
      db2 UPDATE DATABASE CONFIGURATION FOR RTCDB USING APP_CTL_HEAP_SZ 1024
    2. Stop the database server with the following command:
      db2 stop database manager force
    3. Start the database server with the following command:
      db2 start database manager

What to do next

For WebSphere: If you are using WebSphere Application Server:

If you have not deployed the server setup application, deploy it to your server or cluster. To do so, see deploying to a server or deploying to a cluster.

If you are installing to a WebSphere Application Server cluster, you will also have to create a single application server instance for Rational Team Concert.

Then, use the server setup application to configure WebSphere Application Server to connect to your database. If you have deployed the server setup application to your server or cluster, see Deploying and configuring application files by using the server setup application.

If you are using Apache Tomcat:

Configure Apache Tomcat and deploy the Rational Asset Manager application files. To do so, see Deploying Rational Asset Manager on Apache Tomcat 5.5 connected to DB2.

Creating a database for asset lifecycles in Oracle

These are the instructions for creating a database for lifecycle management in Oracle for IBM Rational Asset Manager. This database will be used by the included version of IBM Rational Team Concert.

Before you begin

Oracle must already be installed and running.

You must create the database for asset lifecycles on the same host as the database for assets.

About this task

To set up the Oracle database for asset lifecycles:

  1. Using the Oracle Database Configuration Assistant, follow the steps in the wizard to create a new database.
    1. The database must be on the same host as the database that you created for assets.
    2. Use global database name rtcdb, and a system identifier (SID) rtcdb. The global database name and the system identifier must be the same and must be 8 or fewer characters long.
    3. On the Character Sets page, select Use Unicode (AL32UTF8).
    4. Also on the Character Sets page, for National Character Set, select UTF8 - Unicode 3.0 UTF-8.
    5. Complete the other pages in the wizard, accepting the default values.
  2. Create a tablespace. The tablespace must have the following properties:

    The following command for a Windows computer shows a sample create statement:

    CREATE BIGFILE TABLESPACE jazz_tbs DATAFILE 'D:\jazz_tbs\jazz_tbs.dbf' SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE
    Note: In the above command, the directory D:\jazz_tbs\ must exist.
  3. Create a database user:
    1. Open Database Control.
    2. Navigate to the Users page. (In Oracle 10.2(g), click Administration, then Users; in Oracle 11(g), click Server, then in the Security section click Users.)
    3. Create a user named RAMSCHEMA that meets the following qualifications:
      • The user must have the same username and password as the user that you created for the asset database.
      • The user has the RESOURCE and CONNECT roles.
      • The user's quota setting is unlimited.
      • The default tablespace for the user is the tablespace that you created in step 2.
      • The user must have the following permissions:
        • ALTER ANY INDEX
        • ALTER ANY TABLE
        • CREATE ANY INDEX
        • CREATE DATABASE LINK
        • CREATE MATERIALIZED VIEW
        • CREATE PROCEDURE
        • CREATE PUBLIC SYNONYM
        • CREATE ROLE
        • CREATE SEQUENCE
        • CREATE SESSION
        • CREATE SYNONYM
        • CREATE TABLE
        • CREATE TRIGGER
        • CREATE TYPE
        • CREATE VIEW
        • DELETE ANY TABLE
        • DROP ANY INDEX
        • DROP ANY TABLE
        • INSERT ANY TABLE
        • UNLIMITED TABLESPACE
        • UPDATE ANY TABLE
      Tip: Oracle provides a default user named "Scott" that has many of the appropriate permissions. You can use this default user as the basis for your new user account.

What to do next

For WebSphere: If you are using WebSphere Application Server:

If you have not deployed the server setup application, deploy it to your server or cluster. To do so, see deploying to a server or deploying to a cluster.

If you are installing to a WebSphere Application Server cluster, you will also have to create a single application server instance for Rational Team Concert.

Then, use the server setup application to configure WebSphere Application Server to connect to your database. If you have deployed the server setup application to your server or cluster, see Deploying and configuring application files by using the server setup application.

If you are using Apache Tomcat:
Configure Apache Tomcat and deploy the Rational Asset Manager application files. To do so, see Deploying Rational Asset Manager on Apache Tomcat V5.5 connected to Oracle.
Creating a database for asset lifecycles in Microsoft SQL Server

These are the instructions for manually creating a database for lifecycle management for IBM Rational Asset Manager in Microsoft SQL Server 2005. This database will be used by the included version of IBM Rational Team Concert.

Before you begin

SQL Server 2005 must already be installed and running.

About this task

To set up an SQL Server database by using the command tool sqlcmd:

  1. Create a Jazz Team Server database. From the command line tool, type:
    CREATE DATABASE rtcdb 
    GO
  2. Change the ownership of the Jazz Team Server database to the same user that you use for the Rational Asset Manager asset management database. The following example command assigns the username ramDBuser as the owner of database rtcdb. From the command line tool, type:
    USE rtcdb;
    exec sp_changedbowner 'ramDBuser'
    GO
  3. Change the collation of the Jazz Team Server database. From the command line tool, type:
    ALTER DATABASE rtcdb COLLATE SQL_Latin1_General_CP437_CS_AS 
    GO

What to do next

For WebSphere: If you are using WebSphere Application Server:

If you have not deployed the server setup application, deploy it to your server or cluster. To do so, see deploying to a server or deploying to a cluster.

If you are installing to a WebSphere Application Server cluster, you will also have to create a single application server instance for Rational Team Concert.

Then, use the server setup application to configure WebSphere Application Server to connect to your database. If you have deployed the server setup application to your server or cluster, see Deploying and configuring application files by using the server setup application.

If you are using Apache Tomcat:
Configure Apache Tomcat and deploy the Rational Asset Manager application files. To do so, see Deploying Rational Asset Manager on Apache Tomcat V5.5 connected to SQL Server 2005.

Deploying the server applications manually on WebSphere Application Server

About this task

You can manually deploy the IBM Rational Asset Manager server setup application, which will deploy all of the other applications, on an existing IBM WebSphere Application Server.

Deploying the server setup application to WebSphere Application Server V6.1

Manually install IBM Rational Asset Manager on an existing installation of IBM WebSphere Application Server, version 6.1.

Before you begin

If you used IBM Installation Manager, Installation Manager would have deployed the server setup application to your server for you. For more information, see Installing Rational Asset Manager server by using Installation Manager.

If you install the product into a clustered environment, see Deploying the server setup application to a Websphere Application Server cluster.

  1. Locate the Rational Asset Manager server setup Enterprise Archive for WebSphere Application Server file: com.ibm.ram.repository.setup.web.ear. To locate this file, see Retrieving the server application files directly from the installation media.
  2. Launch the WebSphere Application Server Administrative Console and login as an administrator.
  3. Click Applications.
  4. Click Enterprise Applications.
  5. Click Install.
  6. Type the path and file name of the Rational Asset Manager Server setup EAR file (com.ibm.ram.repository.setup.web.ear).
  7. Click Show me all installation options and parameters.
  8. Until you reach Step 10, click Next, or click this step in the navigation pane.
  9. On the Summary page, click Finish.
  10. After the EAR file is installed, click Save to Master Configuration.
  11. Click Save.
  12. Start the application.
    1. In the navigation pane, click Applications.
    2. Click Enterprise Applications.
    3. Select the com.ibm.ram.repository.setup.web.ear application and click Start.
  13. If you access Rational Asset Manager without a Web server front end, skip this step. If you access Rational Asset Manager through the IIS or Apache server:
    1. In the navigation pane, click Servers.
    2. Click Web Servers.
    3. Select the Web server name and click Generate Plug-in. (If the Web server plug-in has not been created, seeInstalling Web server plug-ins.)
    4. Check the Web server name again and click Propagate Plug-in. This sends the plug-in to the Web server so that the Rational Asset Manager Server application can be referenced through the installed Web server.
  14. Restart WebSphere Application Server and Web servers.
  15. To access the Rational Asset Manager server setup application, use the following URLs:
    1. If you use a Web server, type http://<machine_name>/ram.setup/ . For example, http://www.example.com/ram.setup/
    2. If you do not use a Web server, type http://<machine_name>:<port>/ram.setup/. For example, http://www.example.com:13080/ram.setup/(Use the port number for the Default Host that is defined in Virtual Hosts under Environment in the navigation pane.)
  16. Use the server setup application to configure Rational Asset Manager. For more information, see Deploying and configuring application files by using the server setup application.

Deploying the server setup application to a Websphere Application Server cluster

To manually deploy the IBM Rational Asset Manager server setup application to a Network Deployment cluster, it is necessary to run a Jython script. If you used IBM Installation Manager to install Rational Asset Manager to a cluster, Installation Manager performed this step.

Before you begin

If you used IBM Installation Manager, Installation Manager would have deployed the server setup application to your server for you. For more information, see Installing Rational Asset Manager server by using Installation Manager.

You must have access to the files for manually installing and deploying Rational Asset Manager. For more information, see Retrieving the server application files directly from the installation media.

You must run this script on the machine that has the profile for Deployment Manager.

  1. Locate the following scripts in the <Rational_Asset_Manager_install_directory>\ram\conf\bin folder:
  2. To deploy Rational Asset Manager server setup enterprise archive to the cluster, run the following command (Windows):
    wsadmin.bat -lang jython -user <user_name> -password <password> -f <install_dir>\ram\conf\bin\deployClusterSetup.py <install_dir>/ram/apps/was/com.ibm.ram.repository.setup.web.ear com.ibm.ram.repository.setup.web.ear <contextRoot>
    On AIX or Linux, run the following command:
    wsadmin.sh -lang jython -user <user_name> -password <password> -f <install_dir>/ram/conf/bin/deployClusterSetup.py <install_dir>/ram/apps/was/com.ibm.ram.repository.setup.web.ear com.ibm.ram.repository.setup.web.ear <contextRoot>
    where:
  3. Launch the WebSphere Application Server Administrative Console and login as an administrator.
  4. Start the application.
    1. In the navigation pane, click Applications.
    2. Click Enterprise Applications.
    3. Select the com.ibm.ram.repository.setup.web.ear application and click Start.
  5. Now you can use the server setup application to deploy the other application files and configure your system. See Deploying and configuring application files by using the server setup application.

Example

Note: The path to the Jython script should contain backslashes on Windows and forward slashes on AIX and Linux. The path to the EAR file should contain forward slashes, regardless of platform.

What to do next

To uninstall it from the cluster, run the following command (Windows):

wsadmin.bat -conntype NONE -lang jython -f <installdir>\ram\conf\bin\UninstallSetup.py com.ibm.ram.repository.setup.web.ear

On AIX, Linux, or Linux for zSeries, run the following command:

wsadmin.sh -conntype NONE -lang jython -f <installdir>/ram/conf/bin/UninstallSetup.py com.ibm.ram.repository.setup.web.ear

Creating an application server instance for Rational Team Concert on a WebSphere Application Server cluster

Although you cannot deploy IBM Rational Team Concert, which is required for managing the lifecycles of assets in IBM Rational Asset Manager, to a IBM WebSphere Application Server cluster, you can create a single application server instance on an existing cluster for Rational Team Concert.

Before you begin

You must be an application server administrator to create a new server instance on a cluster.

About this task

Important: Only complete this task if you are using a clustered environment with WebSphere Application Server. If you are not using a cluster, you can install Rational Asset Manager and Rational Team Concert on the same application server.

Because you cannot deploy Rational Team Concert to a cluster, you must create an additional application server that is separate from your clustered servers. You can then deploy Rational Team Concert to that server.

You do not need another machine; you can create a new stand-alone application server on any individual node of your cluster.

  1. In a Web browser, log in to the WebSphere Application Server Administrative Console. By default, this is located at:
  2. In the navigation pane, click and expand Servers.
  3. Click Application Servers.
  4. Click New.
  5. Select a node for the application server.
  6. Type a name for the application server. For example, ramTeamConcertServer. This name must be within the node.
  7. Click Next.
  8. Select a server template. For this, you can use the default server template.
  9. Click Next.
  10. Select Generate unique HTTP ports to assign a unique port to the new application server.
  11. Click Next and review the settings for the new server.
  12. Click Finish.
  13. Click Review, select Synchronize changes with nodes, and then click Save.

What to do next

Your new application server is now configured. You can configure it further by clicking the name of the server on Servers -> Application servers page.

You can now use the server setup application to deploy Rational Team Concert to the new application server.

Configuring the included Rational Team Concert™ server

You can manually configure the included IBM Rational Team Concert server that is required for lifecycles in IBM Rational Asset Manager.

Before you begin

To configure the included Rational Team Concert server application, the application must be deployed to the application server and connected to the database. If you are using IBM WebSphere Application Server, the server setup application does this. If you are using Tomcat, see Deploying the server applications on Apache Tomcat.

  1. Retrieve the Rational Asset Manager server files on the appropriate archive for Tomcat and for your operating system. The application files will be in the <archive_extract_location>/apps/tomcat/ folder.
  2. Find the <archive_extract_location>/apps/tomcat/RTC-server.zip file on the installation media.
  3. Extract RTC-server.zip to a location on your hard drive, which is referred to in these instructions as <rtc_install_dir>.
  4. Configure the administrative user for Rational Team Concert:
    1. Launch the Admin Web UI of Rational Team Concert in a Web browser at https://<machine_name>:<secure_port>/jazz/admin/.
    2. Log in with the User ID and Password for the administrator of the application server.
    3. Click User Management.
    4. Click Create New.
    5. Enter the following details:
      1. User Name: The user ID of the Tomcat server administrator
      2. User ID: The user ID of the Tomcat server administrator
      3. E-mail Address: A valid e-mail address for the Tomcat server administrator
    6. In the Client Access License section, select Rational Team Concert - Developer to assign the developer license to that user.
    7. Click Save.
    8. Log out, and then log back in to the Admin Web UI as the administrator of the application server.
  5. Import the lifecycles process template into Rational Team Concert:
    1. In the Rational Team Concert Admin Web UI, click Process Template Management. If you cannot see the Process Template Management link, log out and then log back in to the Admin Web UI.
    2. Click Import Template and browse to the com.ibm.ram.lifecycle.zip file in the <archive_extract_location>/DatabaseScripts/ folder. Then click OK.
  6. Create a new project area in Rational Team Concert:
    1. In the Rational Team Concert Admin Web UI, click Project Area Management. If you cannot see the Project Area Management link, log out and then log back in to the Admin Web UI.
    2. Click Create Project Area.
    3. Enter the following details about the project area:
      • Project name: RAM Lifecycle
      • Summary: Rational Asset Manager Lifecycle control project area
      • Description: This area is used to manage the lifecycles for Rational Asset Manager
    4. Click Save.
  7. Assign the appropriate memberships and process roles for the project area:
    1. On the Project Area Management page, click the RAM Lifecycle project area.
    2. In the Administrators section, click Add; then search for and select the administrator user that you created.
    3. In the Members section, click Add; then search for and select the administrator user that you created.
    4. After you add the administrator, click the Process Roles icon next to the administrator's name.
    5. In the Edit Process Roles dialog, from the Available Roles list, select Administration and click Add.
    6. Click Finish.
    7. Click Save.

Deploying the server applications on Apache Tomcat

About this task

You can manually deploy IBM Rational Asset Manager on an existing installation of Apache Tomcat.

Deploying Rational Asset Manager on Apache Tomcat 5.5 connected to DB2

You can manually install IBM Rational Asset Manager on an existing installation of Apache Tomcat.

Before you begin

You must have administrative and file access to a Tomcat server that is installed and running.

You must have completed the following tasks:

  1. Retrieving the application files
  2. Creating the database for assets
  3. Creating the database for lifecycles

You must have a security certificate for your Tomcat server. The included version of Rational Team Concert requires a secure connection.

You need to know the location of the db2jcc_license_cu.jar and db2jcc.jar files, which allow Tomcat to communicate with an IBM DB2 database server. Your database server provider should provide you with these files.

Note: If you intend to deploy Rational Asset Manager and the included Rational Team Concert on different Tomcat server applications on the same machine, make sure that you have configured the different Tomcat servers to use different secure and unsecure ports to avoid collisions. For more information on ports in Tomcat 5.5, see the Apache Tomcat documentation.

  1. Verify that all of the repository servers are set to the same current date, time, and time zone.
  2. Retrieve the Rational Asset Manager server files on the appropriate archive for Tomcat and for your operating system. The application files will be in the <archive_extract_location>/apps/tomcat/ folder.
  3. Extract the shared library files to the <tomcat_install_directory>\shared\lib folder:
    1. Find and extract the <archive_extract_location>\apps\tomcat\sharedLib.zip file.
    2. Copy the entire contents of the extracted sharedLib.zip file to the <tomcat_install_directory>\shared\lib directory.
  4. Find the <archive_extract_location>/apps/tomcat/RTC-server.zip file on the installation media.
  5. Extract RTC-server.zip to a location on your hard drive, which is referred to in these instructions as <rtc_install_dir>.
  6. Find the <rtc_install_dir>/jazz/server/jazz_war.ear file and extract it. You can use the free utility 7-Zip to extract .ear files. From the extracted jazz_war.ear package, copy the jazz.war file to the <tomcat_install_directory>/webapps/ directory.
  7. From the directory <archive_extract_location>/apps/tomcat/, copy the following files to the <tomcat_install_directory>/webapps/ directory:
  8. To change the context path of the applications, rename the WAR application files. We recommend the following names:
    Table 5. Recommended context paths for Rational Asset Manager Web application files
    Original file name Recommended file name Resulting context path What is it?
    com.ibm.ram.repository.web.tomcat_runtime.war ram.war ram Rational Asset Manager primary Web application for Tomcat
    com.ibm.ram.repository.web.ws.tomcat_runtime.war ram.ws.war ram.ws Rational Asset Manager Web services application for Tomcat
    iehs.war ram.help.war ram.help Rational Asset Manager help and user assistance application.
    rmcabdgovernprocess.war ram.process.war ram.process Documentation application for asset-based development and governance processes
  9. Configure Tomcat to access DB2.
    1. In a text editor, open the <tomcat_install_directory>\conf\server.xml file.
    2. Find any lines in server.xml that begin with <Connector and that contain port="8080" or port="8009". Change the beginnings of these lines to <Connector URIEncoding="UTF-8".
    3. Between the opening and closing tags for Global JNDI resources <GlobalNamingResources> and </GlobalNamingResources> in server.xml, enter the following text for your version of Tomcat.
      Note: For the values your_username and your_password, use a user ID and password that have access to the database. The values shown for "maxWait", "maxActive", and "maxIdle" are sample values and can be adjusted according to your performance needs.
    Enter this text:
    <Resource name="jdbc/RAM_Con"
    type="javax.sql.DataSource"
    driverClassName="com.ibm.db2.jcc.DB2Driver"
    username="your_username"
    password="your_password"
    url=" jdbc:db2://fully_qualified_server_name:db2_port_number/database_name "
    poolPreparedStatements="true"
    maxWait="5000"
    maxActive="4"
    maxIdle="2"/>
  10. Configure a secure port on your Tomcat server for Rational Team Concert:
    1. You must create a security certificate that identifies your Tomcat server for SSL connections. You can either use the Java JDK keytool function to create a self-signed certificate or you can request a certificate signed by a trusted certificate authority (CA).

      For more information on creating self-signed certificates with keytool, see the Sun Java documentation.

      If you are using an IBM JRE, many versions include the IBM tool ikeyman in the <IBM_Java_JRE_install_location>/jre/bin/ directory. You can use this tool to create and manage security certificates on the server. For more information on using the iKeyman tool, see iKeyman User's Guide.

    2. Copy the certificate keystore file to the root directory for your server, <tomcat_install_directory>.
    3. In the <tomcat_install_directory>\conf\server.xml file, locate the <Connector> tag with the attribute scheme="https". The default file includes an example <Connector> tag for port 8443 that is commented out.
    4. Copy and paste the following text:
      <Connector port="8443"
           maxHttpHeaderSize="8192" 
           maxThreads="150"
           minSpareThreads="25" 
           maxSpareThreads="75"
           enableLookups="false"
           disableUploadTimeout="true" 
           acceptCount="100"
           scheme="https"
           secure="true" 
           clientAuth="false"
           keystoreFile="<keystore_file>"
           keystorePass="<keystore_password>"
           sslProtocol="<keystore_protocol>"
           algorithm="<keystore_algorithm>"
           URIEncoding="UTF-8" />

      Where:

      • <keystore_file> is the filename of your keystore file;
      • <keystore_password> is the password for the keystore file;
      • <keystore_protocol> is the protocol for the keystore. It will most likely be SSL, TLS, or SSL_TLS;
      • <keystore_algorithm> is the X509 algorithm for the keystore. Most likely it will be SunX509 or IbmX509, depending on the source of the certificate.
    5. If you change the port value to use a port other than 8443, for the non-SSL connector (by default, port 8080), change the value of the redirectPort attribute to match your port number for the SSL connector.

    For more information on configuring SSL for Tomcat, see Apache Tomcat 5.5 SSL Configuration HOW-TO and Apache Tomcat Configuration reference.

  11. Configure the Tomcat server for user security:
  12. Copy the following JAR files from the <DB2_installaton_location>\java folder of your DB2 installation to the <tomcat_install_directory>\common\lib folder:
  13. Configure the Tomcat system property settings:
    1. Find the Tomcat startup file and open it in a text editor. On Windows this is <tomcat_install_directory>\bin\startup.bat. On Linux, AIX, or Linux for zSeries, it is <tomcat_install_directory>/bin/startup.sh.
    2. In the startup file, type the following text, where <rtc_install_dir> is the extracted directory from step 5:
      • For Windows:On Windows (replace space characters in the <rtc_install_dir> with %20):
        set JAZZ_INSTALL_DIR=<rtc_install_dir>
        
        
        set JAVA_OPTS=-Djava.awt.headless=true -DSQLSERVER_JDBC="%SQLSERVER_JDBC%" -DORACLE_JDBC="%ORACLE_JDBC%" -DDB2I_JDBC="%DB2I_JDBC%" -DDB2Z_JDBC="%DB2Z_JDBC%" -Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true -DJAZZ_HOME=file:///%JAZZ_INSTALL_DIR%\jazz\server\conf -Dcom.ibm.team.repository.tempDir=%TEMP% -Xmx700M
      • For Linux: For AIX: For Linux for zSeries:On Linux, AIX, or Linux for zSeries:
        JAZZ_INSTALL_DIR=<rtc_install_dir>
        
        
        export JAVA_OPTS="-Djava.awt.headless=true -DSQLSERVER_JDBC=$SQLSERVER_JDBC -DORACLE_JDBC=$ORACLE_JDBC -DDB2I_JDBC=$DB2I_JDBC -DDB2Z_JDBC=$DB2Z_JDBC -Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true -DJAZZ_HOME=file://"$JAZZ_INSTALL_DIR"/jazz/server/conf -Dcom.ibm.team.repository.tempDir=$TEMP_DIR -Xmx700M"
  14. Edit the Jazz server properties file:
    1. In the <rtc_install_dir>/jazz/server/conf/jazz/ directory, find the teamserver.properties file and rename it to teamserver.derby.properties.
    2. In the <rtc_install_dir>/jazz/server/conf/jazz/ directory, find the teamserver.db2.win32.properties file (for Windows) or the teamserver.db2.linux.properties file (for Linux, AIX, or zLinux) and rename the file to teamserver.properties.
    3. In the teamserver.properties file, specify the database and connection properties:
      1. In a text editor, open the teamserver.properties file.
      2. Find the following lines:
        com.ibm.team.repository.db.vendor = DB2
        com.ibm.team.repository.db.jdbc.location=//localhost:50000/JAZZ:user=db2admin;password={password};
        com.ibm.team.repository.db.jdbc.password=db2admin
      3. Edit the value of com.ibm.team.repository.db.jdbc.location for your DB2 server location, and the name of the database for lifecycles:
        1. Replace localhost:50000 with the location and port for the DB2 database.
          Tip: In the DB2 Command Window, run the command db2 get dbm cfg, and then find the line that contains SVCENAME, which indicates the DB2 port name or number. If this command displays a number, use it as the port number (in place of 50000 in the example above). If the command returns a non-numeric name, determine what port number was assigned for this name and use that port number. On Linux, the /etc/services file contains the mapping between port names and numbers; on Windows, the C:\windows\system32\drivers\etc\services file contains the mapping. For more information, ask your database administrator or see the database documentation.
        2. Replace JAZZ with the name of the database for lifecycles.
        3. Replace db2admin with the user name for the DB2 database.
          Note: The DB2 user must have permissions to create tables, table spaces, and to modify the database configuration. DB2 users are created by the operating system.
      4. Specify the user password in the property com.ibm.team.repository.db.jdbc.password.
        Note: Do not change the password={password} text in the com.ibm.team.repository.db.jdbc.location property.
      5. Add the following properties to the teamserver.properties file, where <unsecure_port> is the unsecure port for your Tomcat server (by default, 8080), <secure_port> is the secure port number for your Tomcat server (by default, 8443), and <team_temp_dir> is an absolute path to a directory for storing temporary files:
        com.ibm.team.scm.tmpdir=<team_temp_dir>
        com.ibm.team.repository.server.repourl.port.http=<unsecure_port>
        com.ibm.team.repository.user.registry.type=UNSUPPORTED
        com.ibm.team.repository.ws.allow.admin.access=false
        com.ibm.team.repository.server.repourl.port.https=<secure_port>
  15. Create the tables for Rational Team Concert:
    1. Open a command window and navigate to the <rtc_install_dir>/jazz/server/ directory.
    2. Run the following command:
      • For Windows::
        repotools.bat -createTables teamserver.properties=conf\jazz\teamserver.properties
      • For Linux: For AIX: For Linux for zSeries::
        ./repotools.sh -createTables teamserver.properties=conf/jazz/teamserver.properties
  16. Restart the Tomcat server.
  17. If you are using LDAP to manage users: You can now map existing LDAP group names to the group names required for Rational Team Concert:
    1. Stop the Tomcat server.
    2. With a text editor, open the file <tomcat_install_directory>/webapps/jazz/WEB-INF/web.xml.
    3. Modify the web.xml file as described in TN0030: User management for Jazz servers in Tomcat. The user who is the Tomcat server administrator must either be a member of an LDAP group named JazzAdmins, or be a member of a group that is mapped to the JazzAdmins group.
    4. Restart the Tomcat server.
  18. Configure the administrative user for Rational Team Concert:
    1. Launch the Admin Web UI of Rational Team Concert in a Web browser at https://<machine_name>:<secure_port>/jazz/admin/.
    2. Log in with the User ID and Password for the administrator of the application server.
    3. Click User Management.
    4. Click Create New.
    5. Enter the following details:
      1. User Name: The user ID of the Tomcat server administrator
      2. User ID: The user ID of the Tomcat server administrator
      3. E-mail Address: A valid e-mail address for the Tomcat server administrator
    6. In the Client Access License section, select Rational Team Concert - Developer to assign the developer license to that user.
    7. Click Save.
    8. Log out, and then log back in to the Admin Web UI as the administrator of the application server.
  19. Import the lifecycles process template into Rational Team Concert:
    1. In the Rational Team Concert Admin Web UI, click Process Template Management. If you cannot see the Process Template Management link, log out and then log back in to the Admin Web UI.
    2. Click Import Template and browse to the com.ibm.ram.lifecycle.zip file in the <archive_extract_location>/DatabaseScripts/ folder. Then click OK.
  20. Create a new project area in Rational Team Concert:
    1. In the Rational Team Concert Admin Web UI, click Project Area Management. If you cannot see the Project Area Management link, log out and then log back in to the Admin Web UI.
    2. Click Create Project Area.
    3. Enter the following details about the project area:
      • Project name: RAM Lifecycle
      • Summary: Rational Asset Manager Lifecycle control project area
      • Description: This area is used to manage the lifecycles for Rational Asset Manager
    4. Click Save.
  21. Assign the appropriate memberships and process roles for the project area:
    1. On the Project Area Management page, click the RAM Lifecycle project area.
    2. In the Administrators section, click Add; then search for and select the administrator user that you created.
    3. In the Members section, click Add; then search for and select the administrator user that you created.
    4. After you add the administrator, click the Process Roles icon next to the administrator's name.
    5. In the Edit Process Roles dialog, from the Available Roles list, select Administration and click Add.
    6. Click Finish.
    7. Click Save.
  22. Stop, and then restart the Tomcat server.
  23. In a Web browser, open Rational Asset Manager. If you used the recommended names for the application files, the URL will be http://localhost:8080/ram/home.faces, or through a Web server, the URL will be http://<Web_server_address>:<port>/ram/home.faces. The Rational Asset Manager Web client opens.

What to do next

Next, configure the Rational Asset Manager Web application. For more information, see Configuring the Rational Asset Manager server application.

Deploying Rational Asset Manager on Apache Tomcat V5.5 connected to Oracle

You can install IBM Rational Asset Manager manually on an existing installation of Apache Tomcat. Follow these instructions to deploy Rational Asset Manager on Tomcat V5.5.

Before you begin

You must have administrative and file access to a Tomcat server that is installed and running.

You must have completed the following tasks:

  1. Retrieving the application files
  2. Creating the database for assets
  3. Creating the database for lifecycles

You will need the ojdbc14.jar file, which allows Tomcat to communicate with an Oracle server.Your database server provider should provide you with these files.

Note: If you intend to deploy Rational Asset Manager and the included Rational Team Concert on different Tomcat server applications on the same machine, make sure that you have configured the different Tomcat servers to use different secure and unsecure ports to avoid collisions. For more information on ports in Tomcat 5.5, see the Apache Tomcat documentation.

  1. Verify that all of the repository servers are set to the same current date, time, and time zone.
  2. Retrieve the Rational Asset Manager server files on the appropriate archive for Tomcat and for your operating system. The application files will be in the <archive_extract_location>/apps/tomcat/ folder.
  3. Extract the shared library files to the <tomcat_install_directory>\shared\lib folder:
    1. Find and extract the <archive_extract_location>\apps\tomcat\sharedLib.zip file.
    2. Copy the entire contents of the extracted sharedLib.zip file to the <tomcat_install_directory>\shared\lib directory.
  4. Find the <archive_extract_location>/apps/tomcat/RTC-server.zip file on the installation media.
  5. Extract RTC-server.zip to a location on your hard drive, which is referred to in these instructions as <rtc_install_dir>.
  6. Find the <rtc_install_dir>/jazz/server/jazz_war.ear file and extract it. You can use the free utility 7-Zip to extract .ear files. From the extracted jazz_war.ear package, copy the jazz.war file to the <tomcat_install_directory>/webapps/ directory.
  7. From the directory <archive_extract_location>/apps/tomcat/, copy the following files to the <tomcat_install_directory>/webapps/ directory:
  8. To change the context path of the applications, rename the WAR application files. We recommend the following names:
    Table 7. Recommended context paths for Rational Asset Manager Web application files
    Original file name Recommended file name Resulting context path What is it?
    com.ibm.ram.repository.web.tomcat_runtime.war ram.war ram Rational Asset Manager primary Web application for Tomcat
    com.ibm.ram.repository.web.ws.tomcat_runtime.war ram.ws.war ram.ws Rational Asset Manager Web services application for Tomcat
    iehs.war ram.help.war ram.help Rational Asset Manager help and user assistance application.
    rmcabdgovernprocess.war ram.process.war ram.process Documentation application for asset-based development and governance processes
  9. Configure the Tomcat server to access Oracle.
    1. In a text editor, open the <tomcat_install_directory>\conf\server.xml file.
    2. Find any lines in server.xml that begin with <Connector and that contain port="8080" or port="8009". Change the beginnings of these lines to <Connector URIEncoding="UTF-8".
    3. Between the opening and closing tags for Global JNDI resources <GlobalNamingResources> and </GlobalNamingResources> in server.xml, enter the following text for your version of Tomcat.
      Note: For the values your_username and your_password, use a user ID and password that have access to the database. The values shown for "maxWait", "maxActive", and "maxIdle" are sample values and can be adjusted according to your performance needs.
    Enter this text:
    <Resource name="jdbc/RAM_Con"
    type="javax.sql.DataSource"
    driverClassName="oracle.jdbc.driver.OracleDriver"
    username="<your_username>"
    password="<your_password>"
    url="jdbc:oracle:thin:@fully_qualified_machine_name:oracle_port_number:database_name"
    poolPreparedStatements="true"
    maxWait="5000"
    maxActive="4"
    maxIdle="2"/>
  10. Configure a secure port on your Tomcat server for Rational Team Concert:
    1. You must create a security certificate that identifies your Tomcat server for SSL connections. You can either use the Java JDK keytool function to create a self-signed certificate or you can request a certificate signed by a trusted certificate authority (CA).

      For more information on creating self-signed certificates with keytool, see the Sun Java documentation.

      If you are using an IBM JRE, many versions include the IBM tool ikeyman in the <IBM_Java_JRE_install_location>/jre/bin/ directory. You can use this tool to create and manage security certificates on the server. For more information on using the iKeyman tool, see iKeyman User's Guide.

    2. Copy the certificate keystore file to the root directory for your server, <tomcat_install_directory>.
    3. In the <tomcat_install_directory>\conf\server.xml file, locate the <Connector> tag with the attribute scheme="https". The default file includes an example <Connector> tag for port 8443 that is commented out.
    4. Copy and paste the following text:
      <Connector port="8443"
           maxHttpHeaderSize="8192" 
           maxThreads="150"
           minSpareThreads="25" 
           maxSpareThreads="75"
           enableLookups="false"
           disableUploadTimeout="true" 
           acceptCount="100"
           scheme="https"
           secure="true" 
           clientAuth="false"
           keystoreFile="<keystore_file>"
           keystorePass="<keystore_password>"
           sslProtocol="<keystore_protocol>"
           algorithm="<keystore_algorithm>"
           URIEncoding="UTF-8" />

      Where:

      • <keystore_file> is the filename of your keystore file;
      • <keystore_password> is the password for the keystore file;
      • <keystore_protocol> is the protocol for the keystore. It will most likely be SSL, TLS, or SSL_TLS;
      • <keystore_algorithm> is the X509 algorithm for the keystore. Most likely it will be SunX509 or IbmX509, depending on the source of the certificate.
    5. If you change the port value to use a port other than 8443, for the non-SSL connector (by default, port 8080), change the value of the redirectPort attribute to match your port number for the SSL connector.

    For more information on configuring SSL for Tomcat, see Apache Tomcat 5.5 SSL Configuration HOW-TO and Apache Tomcat Configuration reference.

  11. Configure the Tomcat server for user security:
  12. Add the following .jar file to the <tomcat_install_directory>\common\lib folder: This file is available from your database application provider.
  13. Configure the Tomcat system property settings:
    1. Find the Tomcat startup file and open it in a text editor. On Windows this is <tomcat_install_directory>\bin\startup.bat. On Linux, AIX, or Linux for zSeries, it is <tomcat_install_directory>/bin/startup.sh.
    2. In the startup file, type the following text, where <rtc_install_dir> is the extracted directory from step 3 and <oracle_jar_dir> is the location of the Oracle .jar file from step 12:
      • On Windows (replace space characters in the <rtc_install_dir> with %20):
        set JAZZ_INSTALL_DIR=<rtc_install_dir>
        set ORACLE_JDBC=<oracle_jar_dir>
        set JAVA_OPTS=-Djava.awt.headless=true -DSQLSERVER_JDBC="%SQLSERVER_JDBC%" -DORACLE_JDBC="%ORACLE_JDBC%" -DDB2I_JDBC="%DB2I_JDBC%" -DDB2Z_JDBC="%DB2Z_JDBC%" -Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true -DJAZZ_HOME=file:///%JAZZ_INSTALL_DIR%\jazz\server\conf -Dcom.ibm.team.repository.tempDir=%TEMP% -Xmx700M
      • On Linux, AIX, or Linux for zSeries:
        JAZZ_INSTALL_DIR=<rtc_install_dir>
        ORACLE_JDBC=<oracle_jar_dir>
        export JAVA_OPTS="-Djava.awt.headless=true -DSQLSERVER_JDBC=$SQLSERVER_JDBC -DORACLE_JDBC=$ORACLE_JDBC -DDB2I_JDBC=$DB2I_JDBC -DDB2Z_JDBC=$DB2Z_JDBC -Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true -DJAZZ_HOME=file://"$JAZZ_INSTALL_DIR"/jazz/server/conf -Dcom.ibm.team.repository.tempDir=$TEMP_DIR -Xmx700M"
  14. Edit the Jazz server properties file:
    1. In the <rtc_install_dir>/jazz/server/conf/jazz/ directory, find the teamserver.properties file and rename it to teamserver.derby.properties.
    2. In the <rtc_install_dir>/jazz/server/conf/jazz/ directory, find the teamserver.oracle.properties file and rename it to teamserver.properties.
    3. In the teamserver.properties file, specify the database and connection properties:
      1. In a text editor, open the teamserver.properties file.
      2. Find the following lines:
        com.ibm.team.repository.db.vendor = ORACLE
        com.ibm.team.repository.db.jdbc.location=thin:jazzDBuser/{password}@localhost:1521/ORCL
        com.ibm.team.repository.db.jdbc.password=jazzDBpswd
      3. Edit the value of com.ibm.team.repository.db.jdbc.location for your Oracle server location and the name of the database for lifecycles:
        1. Replace jazzDBUser with the user name for the Oracle database (for example, RAMSCHEMA.
        2. Replace @localhost:1521 with the location and port for the Oracle database. If the location is not localhost, you must precede the location with two forward slashes (//); for example, @//oracleserver.example.com:1521.
        3. Replace ORCL with the name of the lifecycle database; for example, rtcdb.
      4. In the com.ibm.team.repository.db.jdbc.password property, replace JazzDBpswd with the password for the Oracle that user you specified above.
        Note: Do not change the text {password} in the com.ibm.team.repository.db.jdbc.location property.
      5. Add the following properties to the teamserver.properties file, where <unsecure_port> is the unsecure port for your Tomcat server (by default, 8080), <secure_port> is the secure port number for your Tomcat server (by default, 8443), and <team_temp_dir> is an absolute path to a directory for storing temporary files:
        com.ibm.team.scm.tmpdir=<team_temp_dir>
        com.ibm.team.repository.server.repourl.port.http=<unsecure_port>
        com.ibm.team.repository.user.registry.type=UNSUPPORTED
        com.ibm.team.repository.ws.allow.admin.access=false
        com.ibm.team.repository.server.repourl.port.https=<secure_port>
  15. Create the tables for Rational Team Concert:
    1. Open a command window and navigate to the <rtc_install_dir>/jazz/server/ directory.
    2. Run the following command:
      • For Windows::
        repotools.bat -createTables teamserver.properties=conf\jazz\teamserver.properties
      • For Linux: For AIX: For Linux for zSeries::
        ./repotools.sh -createTables teamserver.properties=conf/jazz/teamserver.properties
  16. Restart the Tomcat server.
  17. If you are using LDAP to manage users: You can now map existing LDAP group names to the group names required for Rational Team Concert:
    1. Stop the Tomcat server.
    2. With a text editor, open the file <tomcat_install_directory>/webapps/jazz/WEB-INF/web.xml.
    3. Modify the web.xml file as described in TN0030: User management for Jazz servers in Tomcat. The user who is the Tomcat server administrator must either be a member of an LDAP group named JazzAdmins, or be a member of a group that is mapped to the JazzAdmins group.
    4. Restart the Tomcat server.
  18. Configure the administrative user for Rational Team Concert:
    1. Launch the Admin Web UI of Rational Team Concert in a Web browser at https://<machine_name>:<secure_port>/jazz/admin/.
    2. Log in with the User ID and Password for the administrator of the application server.
    3. Click User Management.
    4. Click Create New.
    5. Enter the following details:
      1. User Name: The user ID of the Tomcat server administrator
      2. User ID: The user ID of the Tomcat server administrator
      3. E-mail Address: A valid e-mail address for the Tomcat server administrator
    6. In the Client Access License section, select Rational Team Concert - Developer to assign the developer license to that user.
    7. Click Save.
    8. Log out, and then log back in to the Admin Web UI as the administrator of the application server.
  19. Import the lifecycles process template into Rational Team Concert:
    1. In the Rational Team Concert Admin Web UI, click Process Template Management. If you cannot see the Process Template Management link, log out and then log back in to the Admin Web UI.
    2. Click Import Template and browse to the com.ibm.ram.lifecycle.zip file in the <archive_extract_location>/DatabaseScripts/ folder. Then click OK.
  20. Create a new project area in Rational Team Concert:
    1. In the Rational Team Concert Admin Web UI, click Project Area Management. If you cannot see the Project Area Management link, log out and then log back in to the Admin Web UI.
    2. Click Create Project Area.
    3. Enter the following details about the project area:
      • Project name: RAM Lifecycle
      • Summary: Rational Asset Manager Lifecycle control project area
      • Description: This area is used to manage the lifecycles for Rational Asset Manager
    4. Click Save.
  21. Assign the appropriate memberships and process roles for the project area:
    1. On the Project Area Management page, click the RAM Lifecycle project area.
    2. In the Administrators section, click Add; then search for and select the administrator user that you created.
    3. In the Members section, click Add; then search for and select the administrator user that you created.
    4. After you add the administrator, click the Process Roles icon next to the administrator's name.
    5. In the Edit Process Roles dialog, from the Available Roles list, select Administration and click Add.
    6. Click Finish.
    7. Click Save.
  22. Stop, and then restart the Tomcat server.
  23. In a Web browser, open Rational Asset Manager. If you used the recommended names for the application files, the URL will be http://localhost:8080/ram/home.faces, or through a Web server, the URL will be http://<Web_server_address>:<port>/ram/home.faces. The Rational Asset Manager Web client opens.

What to do next

Next, configure the Rational Asset Manager Web application. For more information, see Configuring the Rational Asset Manager server application.

Deploying Rational Asset Manager on Apache Tomcat V5.5 connected to SQL Server 2005

You can install IBM Rational Asset Manager manually on an existing installation of Apache Tomcat.

Before you begin

You must have administrative and file access to a Tomcat server that is installed and running.

You must have completed the following tasks:

  1. Retrieving the application files
  2. Creating the database for assets
  3. Creating the database for lifecycles

You will need the sqljdbc.jar file, which allows Tomcat to communicate with Microsoft SQL Server. Your database server provider should provide you with these files.

Note: If you intend to deploy Rational Asset Manager and the included Rational Team Concert on different Tomcat server applications on the same machine, make sure that you have configured the different Tomcat servers to use different secure and unsecure ports to avoid collisions. For more information on ports in Tomcat 5.5, see the Apache Tomcat documentation.

  1. Verify that all of the repository servers are set to the same current date, time, and time zone.
  2. Retrieve the Rational Asset Manager server files on the appropriate archive for Tomcat and for your operating system. The application files will be in the <archive_extract_location>/apps/tomcat/ folder.
  3. Extract the shared library files to the <tomcat_install_directory>\shared\lib folder:
    1. Find and extract the <archive_extract_location>\apps\tomcat\sharedLib.zip file.
    2. Copy the entire contents of the extracted sharedLib.zip file to the <tomcat_install_directory>\shared\lib directory.
  4. Find the <archive_extract_location>/apps/tomcat/RTC-server.zip file on the installation media.
  5. Extract RTC-server.zip to a location on your hard drive, which is referred to in these instructions as <rtc_install_dir>.
  6. Find the <rtc_install_dir>/jazz/server/jazz_war.ear file and extract it. You can use the free utility 7-Zip to extract .ear files. From the extracted jazz_war.ear package, copy the jazz.war file to the <tomcat_install_directory>/webapps/ directory.
  7. From the directory <archive_extract_location>/apps/tomcat/, copy the following files to the <tomcat_install_directory>/webapps/ directory:
  8. To change the context path of the applications, rename the WAR application files. We recommend the following names:
    Table 9. Recommended context paths for Rational Asset Manager Web application files
    Original file name Recommended file name Resulting context path What is it?
    com.ibm.ram.repository.web.tomcat_runtime.war ram.war ram Rational Asset Manager primary Web application for Tomcat
    com.ibm.ram.repository.web.ws.tomcat_runtime.war ram.ws.war ram.ws Rational Asset Manager Web services application for Tomcat
    iehs.war ram.help.war ram.help Rational Asset Manager help and user assistance application.
    rmcabdgovernprocess.war ram.process.war ram.process Documentation application for asset-based development and governance processes
  9. Configure the Tomcat server to access the SQL Server.
    1. In a text editor, open the <tomcat_install_directory>\conf\server.xml file.
    2. Find any lines in server.xml that begin with <Connector and that contain port="8080" or port="8009". Change the beginnings of these lines to <Connector URIEncoding="UTF-8".
    3. Between the opening and closing tags for Global JNDI resources <GlobalNamingResources> and </GlobalNamingResources> in server.xml, enter the following text for your version of Tomcat.
      Note: For the values your_username and your_password, use a user ID and password that have access to the database. The values shown for "maxWait", "maxActive", and "maxIdle" are sample values and can be adjusted according to your performance needs.
    Enter this text:
    <Resource name="jdbc/RAM_Con"
    type="javax.sql.DataSource"
    driverClassName="com.microsoft.jdbc.sqlserver.SQLServerDriver"
    username="your_username"
    password="your_password"
    url="jdbc:microsoft:sqlserver://fully_qualified_server_name:SQLServer_port_number:db_name"
    poolPreparedStatements="true"
    maxWait="5000"
    maxActive="4"
    maxIdle="2"/>
  10. Configure a secure port on your Tomcat server for Rational Team Concert:
    1. You must create a security certificate that identifies your Tomcat server for SSL connections. You can either use the Java JDK keytool function to create a self-signed certificate or you can request a certificate signed by a trusted certificate authority (CA).

      For more information on creating self-signed certificates with keytool, see the Sun Java documentation.

      If you are using an IBM JRE, many versions include the IBM tool ikeyman in the <IBM_Java_JRE_install_location>/jre/bin/ directory. You can use this tool to create and manage security certificates on the server. For more information on using the iKeyman tool, see iKeyman User's Guide.

    2. Copy the certificate keystore file to the root directory for your server, <tomcat_install_directory>.
    3. In the <tomcat_install_directory>\conf\server.xml file, locate the <Connector> tag with the attribute scheme="https". The default file includes an example <Connector> tag for port 8443 that is commented out.
    4. Copy and paste the following text:
      <Connector port="8443"
           maxHttpHeaderSize="8192" 
           maxThreads="150"
           minSpareThreads="25" 
           maxSpareThreads="75"
           enableLookups="false"
           disableUploadTimeout="true" 
           acceptCount="100"
           scheme="https"
           secure="true" 
           clientAuth="false"
           keystoreFile="<keystore_file>"
           keystorePass="<keystore_password>"
           sslProtocol="<keystore_protocol>"
           algorithm="<keystore_algorithm>"
           URIEncoding="UTF-8" />

      Where:

      • <keystore_file> is the filename of your keystore file;
      • <keystore_password> is the password for the keystore file;
      • <keystore_protocol> is the protocol for the keystore. It will most likely be SSL, TLS, or SSL_TLS;
      • <keystore_algorithm> is the X509 algorithm for the keystore. Most likely it will be SunX509 or IbmX509, depending on the source of the certificate.
    5. If you change the port value to use a port other than 8443, for the non-SSL connector (by default, port 8080), change the value of the redirectPort attribute to match your port number for the SSL connector.

    For more information on configuring SSL for Tomcat, see Apache Tomcat 5.5 SSL Configuration HOW-TO and Apache Tomcat Configuration reference.

  11. Configure the Tomcat server for user security:
  12. Add the following JAR file to the <tomcat_install_directory>\common\lib folder: This file is available from your database application provider.
  13. Configure the Tomcat system property settings:
    1. Find the Tomcat startup file and open it in a text editor. On Windows this is <tomcat_install_directory>\bin\startup.bat. On Linux, AIX, or Linux for zSeries, it is <tomcat_install_directory>/bin/startup.sh.
    2. In the startup file, type the following text, where <rtc_install_dir> is the extracted directory from step 3 and <sqlServer_jar_dir> is the location of the SQL Server .jar file from step 12:
      • On Windows (replace space characters in the <rtc_install_dir> with %20):
        set JAZZ_INSTALL_DIR=<rtc_install_dir>
        set SQLSERVER_JDBC=<sqlServer_jar_dir>
        set JAVA_OPTS=-Djava.awt.headless=true -DSQLSERVER_JDBC="%SQLSERVER_JDBC%" -DORACLE_JDBC="%ORACLE_JDBC%" -DDB2I_JDBC="%DB2I_JDBC%" -DDB2Z_JDBC="%DB2Z_JDBC%" -Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true -DJAZZ_HOME=file:///%JAZZ_INSTALL_DIR%\jazz\server\conf -Dcom.ibm.team.repository.tempDir=%TEMP% -Xmx700M
      • On Linux, AIX, or Linux for zSeries:
        JAZZ_INSTALL_DIR=<rtc_install_dir>
        SQLSERVER_JDBC=<sqlServer_jar_dir>export JAVA_OPTS="-Djava.awt.headless=true -DSQLSERVER_JDBC=$SQLSERVER_JDBC -DORACLE_JDBC=$ORACLE_JDBC -DDB2I_JDBC=$DB2I_JDBC -DDB2Z_JDBC=$DB2Z_JDBC -Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true -DJAZZ_HOME=file://"$JAZZ_INSTALL_DIR"/jazz/server/conf -Dcom.ibm.team.repository.tempDir=$TEMP_DIR -Xmx700M"
  14. Edit the Jazz server properties file:
    1. In the <rtc_install_dir>/jazz/server/conf/jazz/ directory, find the teamserver.properties file and rename it to teamserver.derby.properties.
    2. In the <rtc_install_dir>/jazz/server/conf/jazz/ directory, find the teamserver.sqlserver.properties file and rename it to teamserver.properties.
    3. In the teamserver.properties file, specify the database and connection properties:
      1. In a text editor, open the teamserver.properties file.
      2. Find the following lines:
        com.ibm.team.repository.db.vendor = SQLSERVER
        com.ibm.team.repository.db.jdbc.location=//localhost:1433;databaseName=jazz;user=jazzDBuser;password={password}
        com.ibm.team.repository.db.jdbc.password=jazzDBpswd
      3. Edit the value of com.ibm.team.repository.db.jdbc.location for your SQL Server location and the name of the database for lifecycles:
        1. Replace @localhost:1433 with the location and port for the SQL Server database.
        2. Replace jazz with the name of the lifecycle database; for example, RTCDB.
        3. Replace jazzDBUser with the user name for the SQL Server database.
      4. In the com.ibm.team.repository.db.jdbc.password property, replace JazzDBpswd with the password for the SQL server user that you specified above.
        Note: Do not change the text {password} in the com.ibm.team.repository.db.jdbc.location property.
      5. Add the following properties to the teamserver.properties file, where <unsecure_port> is the unsecure port for your Tomcat server (by default, 8080), <secure_port> is the secure port number for your Tomcat server (by default, 8443), and <team_temp_dir> is an absolute path to a directory for storing temporary files:
        com.ibm.team.scm.tmpdir=<team_temp_dir>
        com.ibm.team.repository.server.repourl.port.http=<unsecure_port>
        com.ibm.team.repository.user.registry.type=UNSUPPORTED
        com.ibm.team.repository.ws.allow.admin.access=false
        com.ibm.team.repository.server.repourl.port.https=<secure_port>
  15. Create the tables for Rational Team Concert:
    1. Open a command window and navigate to the <rtc_install_dir>/jazz/server/ directory.
    2. Run the following command:
      • For Windows::
        repotools.bat -createTables teamserver.properties=conf\jazz\teamserver.properties
      • For Linux: For AIX: For Linux for zSeries::
        ./repotools.sh -createTables teamserver.properties=conf/jazz/teamserver.properties
  16. Restart the Tomcat server.
  17. If you are using LDAP to manage users: You can now map existing LDAP group names to the group names required for Rational Team Concert:
    1. Stop the Tomcat server.
    2. With a text editor, open the file <tomcat_install_directory>/webapps/jazz/WEB-INF/web.xml.
    3. Modify the web.xml file as described in TN0030: User management for Jazz servers in Tomcat. The user who is the Tomcat server administrator must either be a member of an LDAP group named JazzAdmins, or be a member of a group that is mapped to the JazzAdmins group.
    4. Restart the Tomcat server.
  18. Configure the administrative user for Rational Team Concert:
    1. Launch the Admin Web UI of Rational Team Concert in a Web browser at https://<machine_name>:<secure_port>/jazz/admin/.
    2. Log in with the User ID and Password for the administrator of the application server.
    3. Click User Management.
    4. Click Create New.
    5. Enter the following details:
      1. User Name: The user ID of the Tomcat server administrator
      2. User ID: The user ID of the Tomcat server administrator
      3. E-mail Address: A valid e-mail address for the Tomcat server administrator
    6. In the Client Access License section, select Rational Team Concert - Developer to assign the developer license to that user.
    7. Click Save.
    8. Log out, and then log back in to the Admin Web UI as the administrator of the application server.
  19. Import the lifecycles process template into Rational Team Concert:
    1. In the Rational Team Concert Admin Web UI, click Process Template Management. If you cannot see the Process Template Management link, log out and then log back in to the Admin Web UI.
    2. Click Import Template and browse to the com.ibm.ram.lifecycle.zip file in the <archive_extract_location>/DatabaseScripts/ folder. Then click OK.
  20. Create a new project area in Rational Team Concert:
    1. In the Rational Team Concert Admin Web UI, click Project Area Management. If you cannot see the Project Area Management link, log out and then log back in to the Admin Web UI.
    2. Click Create Project Area.
    3. Enter the following details about the project area:
      • Project name: RAM Lifecycle
      • Summary: Rational Asset Manager Lifecycle control project area
      • Description: This area is used to manage the lifecycles for Rational Asset Manager
    4. Click Save.
  21. Assign the appropriate memberships and process roles for the project area:
    1. On the Project Area Management page, click the RAM Lifecycle project area.
    2. In the Administrators section, click Add; then search for and select the administrator user that you created.
    3. In the Members section, click Add; then search for and select the administrator user that you created.
    4. After you add the administrator, click the Process Roles icon next to the administrator's name.
    5. In the Edit Process Roles dialog, from the Available Roles list, select Administration and click Add.
    6. Click Finish.
    7. Click Save.
  22. Stop, and then restart the Tomcat server.
  23. In a Web browser, open Rational Asset Manager. If you used the recommended names for the application files, the URL will be http://localhost:8080/ram/home.faces, or through a Web server, the URL will be http://<Web_server_address>:<port>/ram/home.faces. The Rational Asset Manager Web client opens.

What to do next

Next, configure the Rational Asset Manager Web application. For more information, see Configuring the Rational Asset Manager server application.

Post-installation configuration

To finalize configuration of the server application, a repository administrator must perform the steps in the topics in this section.

If you installed IBM Rational Asset Manager manually and did not configure the server using the server setup application, perform the steps in the topics in this section and then perform the steps in the topics in the section entitled "Mandatory configuration."

Deploying and configuring application files by using the server setup application

The server setup application is a browser-based Web application that opens after the installs IBM Rational Asset Manager features on a new embedded IBM WebSphere Application Server or an existing WebSphere Application Server. It helps you deploy the other Rational Asset Manager applications and configure the database, security, performance, and repository settings. You can use the server setup application to later modify these settings instead of using the Administration pages within Rational Asset Manager Web client.

Before you begin

The server setup application helps you complete the following tasks:

To configure Rational Asset Manager, the setup enterprise archive must be deployed and running, and the database server must be running:

About this task

Important: The server setup application will need to stop and restart the server - including all nodes on a cluster - to configure Rational Asset Manager. If you are running other applications on your server or cluster, make the proper preparations for your server or cluster to be stopped and restarted.

As you configure Rational Asset Manager, the server setup application creates and updates a log file that records all changes to your server environment. To view all of the current changes that you made while using the server setup application, click Tools -> View/hide log ( View/hide log icon). A list of your current changes will be displayed at the bottom of your browser view.

While the log is in view, to view a complete record of all the changes that the server setup application has made to your server environment, click View full log ( View full log icon).

To view the current details of your server environment, click Tools -> View configuration report ( View configuration report icon).

  1. Verify that all of the repository servers are set to the same current date, time, and time zone.
  2. For Linux: For AIX: For Linux for zSeries:On Linux, AIX, or Linux for zSeries, increase the number of file descriptors a process may have open at once to at least 2048:
    1. To view the current number of descriptors that can be open at once, in the command line type: ulimit -n
    2. If the limit is not at least 2048, increase the limit with the following command: ulimit -n 2048
  3. Configure the application security and authentication settings for WebSphere Application Server:
    1. In a Web browser, log in to the WebSphere Application Server Administrative Console. By default, this is located at:
      • For embedded WebSphere Application Server: http://localhost:13060/ibm/console . The default username is admin and the default password is admin.
      • For WebSphere Application Server: http://localhost:9060/ibm/console
    2. Click Security.
    3. Click Secure administration, applications, and infrastructure.
    4. In the Administrative Security section, if the Enable administrative security checkbox is selected, select the Enable application security checkbox.
    5. In the Authentication section, click Web security.
    6. Click General settings.
    7. In the Web Authentication Behavior section, select the Use available authentication data when an unprotected URI is accessed checkbox if it is not already selected.
    8. Click Apply.
    9. In the Messages window, click Save directly to the master configuration.
    10. Stop, and then restart the server.
  4. For WebSphere:If you use a WebSphere Application Server cluster, you must create a stand-alone application server instance on your cluster for Rational Team Concert. To do so, see Creating an application server instance for Rational Team Concert on a WebSphere Application Server cluster. If you are not using a cluster, you do not have to do this; Rational Team Concert and Rational Asset Manager can be installed on the same application server.
  5. If you manually deployed the server setup application (you did not use Installation Manager), on the same machine that you deployed the server setup application, create a folder that contains the following application server files:

    For more information on retrieving these files, see Retrieving the server application files directly from the installation media.

  6. Open the server setup application by navigating a Web browser to http://<machine_name>:<port_number>/<Server_Setup_Context_Root>.

    The default URL for the server setup application is:

    If security is enabled on the application server, you will be prompted for the user ID and password for an application server administrator.

  7. On the Introduction page, indicate the type of database and user authentication to use:
    1. Select the database application that you will be using from the list.
    2. Select the type of user authentication that the Rational Asset Manager Web application will use:
      • LDAP: User information is stored in a Lightweight Directory Access Protocol (LDAP) repository. To access the repository, you need administrative information.
      • File: User information is stored in a custom user registry, as defined for your application server; this might be displayed in the list as the name of the custom registry as defined for the application server. An example custom user registry is File, where user information is stored in a flat file on the server. If you are not using any of the other types of authentication, select this option.
        Note: File-based authentication is not intended for use in a production environment.
      • Federated Repository: User information is stored in multiple repositories, such as LDAP repositories. This type of authentication is managed by WebSphere Application Server.
      • Local Operating System: User information is stored in the user accounts database on the local operating system. This type of authentication is managed by WebSphere Application Server.
    3. In the Locate installation files field, type the directory on the file system where the new Web application files are located. If you used Installation Manager, the files will be at the <package_group_location>\ram\apps\was directory. The following files must be in that directory:
      • com.ibm.ram.repository.web_runtime.ear
      • RTC-Server.zip
      • iehs_war.ear
      • rmcabdgovernprocess_war.ear
    4. Confirm that the Server or Cluster listed is the one that you want to configure. If you need to create a Network Deployment cluster for Rational Asset Manager, see the WebSphere Application Server documentation.
    5. Click Next.
  8. In the Step 1: Locate Installation Files section, in the Location field type the directory on the file system where the new web application files are located. If you used Installation Manager, the files will be at the <package_group_location>\ram\apps\was directory. The following files must be in that directory:
  9. In the Step 2: Select the applications and documentation to install section, applications that are successfully deployed are indicated with the cluster or server name that they are deployed on. To deploy Rational Asset Manager Web applications:
    1. Select one or more application to deploy.
    2. From the Clusters and servers or Servers list, select the clusters or servers to deploy to. You cannot deploy Rational Team Concert to a cluster; use the single server that you created in step 4.
      Note: If you require users to authenticate (for example, through the application server or an external firewall) to access the Rational Asset Manager help application, you must deploy the Rational Asset Manager help application on the same server or cluster as the Rational Asset Manager Web application.
    3. Click Deploy Applications. The process to deploy one or more applications can take several minutes. The progress of the deployments is displayed on a separate page; the result of the process is displayed on the Deploy Rational Asset Manager page.
    4. Click Next.
    5. On the Summary page, click Next.
  10. In Section 2, Part 1, either create a new database or connect to an existing database:
    1. Select whether to create a new database or use an existing database.
      • To create and populate a new database, select You need to create both databases and then click Next. Go to step 10b.
      • To use an existing database (for example, if you are upgrading from a previous version of Rational Asset Manager), click Use Existing Database. Go to step 11
    2. Create a database.
      • For DB2, you can use a Java™ applet to create and populate the database, or you can perform these manually.
        • To use the Java applet:
          1. After the applet loads, it searches for an instance of DB2 on the local computer. The browser that you run the server setup application on must be on the computer on which DB2 is installed. If the applet finds an instance of DB2, the location of the DB2 installation and its version are displayed. If the applet does not find an instance, you are prompted to enter the location.
          2. To use a different installation of DB2, click Change install location.
          3. Type the User ID and Password for the DB2 administrator. DB2 administrators are managed by the operating system.
          4. After you select the appropriate location, in the Create a database for Asset Management field, type a name for the asset database (for example, RAMDB).
          5. In the Create a database for Lifecycle Management field, type a name for the lifecycle management database (for example, RTCDB).
          6. Click Create Database(s). This will also populate the tables for the database for assets.
        • To manually create and configure the DB2 database, click View instructions on how to manually create the DB2 DATABASE(s) and follow the displayed instructions.
      • For Oracle or SQL Server, follow the instructions to manually create and populate the database.
      The instructions displayed in the server setup application are identical to those at Creating and configuring databases for Rational Asset Manager.
  11. In Section 2, Part 2, specify the database connection properties:
    1. In the Database server text field, type the host name or IP address of the database server; for example, servername.example.com. (Do not use localhost).
    2. In the Port field, type the port number. For example, the default value for DB2 is 50000.
    3. Type the user ID and password of a user with administration authority for the database application.
    4. Select to either provide the location of the archive file or files required by the database on the server, or upload them to the server.
      • To enter the location of the archive files on the server, type the full path to the folder that contains them; for example, C:\Program Files\IBM\SQLLIB\java.
      • To upload the files to the server, select that option and browse to the file or files on the local computer. By default, these are available in <RAM V7.1 install root>\ram\ewas\universalDriver\lib on the local computer. When uploaded to the server, they will be placed in <WAS_install_directory>\profiles\<profile_name>\config\cells\<cell_name>\ram_jdbc
        Note: For Linux: For AIX: For Linux for zSeries: Replace back slashes ("\") in the directory paths with forward slashes ("/").
        Important: For Linux: For AIX: For Linux for zSeries: If you must run WebSphere Application Server or Apache Tomcat as a non-root user, then you must set the appropriate permission on the database Java archive files that you upload. Refer to the instructions in Enabling database connectivity for non-root users (Linux and AIX).
    5. In the Database name for RAM field, type the name of the main Rational Asset Manager database; for example, RAMDB.
    6. In the Database name for Lifecycle field, type the name of the Lifecycle management database; for example, RTCDB
    7. Click Test Connection. The server setup application reports whether the server could connect to the databases.
    8. If the connection test was successful, click Next.
  12. In Section 2, part 2, configure the databases and populate the tables:
    1. Under Step 5: Configure Rational Asset Manager Core Database, click Populate the database.
    2. A message will ask you to verify that you want to configure the database. Click OK. This process can take a few minutes.
    3. Under Step 6: Configure Rational Asset Manager Lifecycle Database, click Populate the Database.
    4. A message will ask you to verify that you want to configure the database. Click OK. This process can take a few minutes.
    5. After the databases are configured, click Next.
  13. For DB2:In Section 2, Part 3, if you use DB2, you can configure database settings to optimize the performance of Rational Asset Manager. If you are using Oracle or SQL, you cannot configure database settings here.
    1. If you are using DB2, configure your database settings. Suggested values and current values for the following parameters are listed. To change all parameters to the recommended values, select Use recommended values. Changes to database settings take effect when you restart the database server.
      • LOCKLIST: to specify the amount of storage that is allocated to the lock list, type a number between 4 and 60000, inclusive.
      • LOCKTIMEOUT: To specify the number of seconds that an application waits to obtain a lock, type a number between 1 and 30000. Setting this property helps avoid global deadlocks for applications. If the value is -1, lock timeout detection is turned off.
      • LOGFILSIZ: To specify the size of each primary and secondary log file, type a number. The size of these log files limits the number of log records that can be written to them before they become full and a new log file is required. If the database has a large number of update, delete, or insert transactions running, which will fill the log file quickly, increase the value of LOGFILSIZ.
        Note: Changing the LOGFILSIZ parameter from the default is necessary only when there are a large number of assets in the repository (for example, tens or hundreds of thousands).
      • MAXAPPLS: type a number that is greater than the number of expected concurrent connections.
      • MAXLOCKS: To specify the percentage of the lock list that is reached when the database manager escalates, from row to table, the locks that the application holds, type a number between 1 and 100. Although the escalation process does not take much time, locking entire tables versus individual rows decreases concurrency, and potentially decreases overall database performance for subsequent attempts to access the affected tables.
    2. Click Next.
  14. In Section 2, Summary, the server setup application will prompt you to restart the server. If you plan to continue through other sections of the server setup application, you can wait to restart the server until you have finished those sections.
  15. In Section 3, configure users and authentication:
  16. In Section 4, configure settings for Rational Asset Manager:
    1. Type the address for the License server in the <port>@<host_name> format ; for example, 27000@example.com. By default, Rational License Server uses TCP/IP port 27000.
    2. In the License type section, select the type of license that the Rational Asset Manager server will use.
    3. Configure the address of the server with the applications that were deployed in step 9. Type the protocol, fully qualified host name, and port number; for example, http://example.com:9080.
      Important: Always use a host name or IP address for these entries. Do not use localhost. If you use IPV6, use the IPV6 hostname; an IPV6 address will not work.
    4. Configure the paths for the applications. The default paths are based on the server address provided.
      • Rational Asset Manager: Type the deployment URL for the Rational Asset Manager server application; for example, http://example.com:9080/ram.
      • Web Services: Type the deployment URL for the Web services; for example, http://example.com:9080/ram.ws
      • Help and User Assistance: Type the deployment URL for the Rational Asset Manager user assistance application; for example, http://example.com:9080/ram.help.
      • Asset-Based Development Process: Type the deployment URL for the Rational Asset-based Development Process application; for example, http://example.com:9080/ram.process.
      To modify the locations or context roots (for example, if you have specified different context roots in WebSphere Application Server), click Edit.
    5. Click Next.
    6. Configure the storage folder locations. If you are installing to a cluster, the cluster name is displayed and you must select the folders for every node in the cluster; to use the settings that you entered for the first node for all nodes, click Use these settings for all nodes.
      Note: For Windows: For WebSphere: If you are using a remote file server or a WebSphere Application Server cluster, the same Windows user account (username and password) must be able to log on to every machine used by Rational Asset Manager. Otherwise, Rational Asset Manager will not be able to save files on different file servers.
      • Persist folder: Type the full path to the folder where assets and search indexes are to be stored on the file system. This can be a mapped directory. If you are installing to a cluster, this must be a location that is shared between all of the nodes of the cluster.
      • Local storage folder: Type the full path to the folder where the Rational Asset Manager Web application will store data. This must be a location on the local computer, not a mapped or shared location. If you are installing to a cluster, each node in the cluster must have its own local storage folder that is not shared with the other nodes. If you are installing multiple servers on the same physical node, the servers should all use the same physical local storage folder.
      • Index folder: Type the full path to the folder where the Rational Asset Manager Web application will store search index files.
        Tip: For best performance, all of these folders should be on different physical drives. The drives should be capable of fast reads and writes, and should not be the same drive as the operating system or application server. For cluster installations, each computer should have its own local folder on a hard disk that is local to the computer. Sharing a local folder between all application servers will degrade performance.
    7. Click Next.
    8. For cluster installations, Java Messaging Service (JMS) must be correctly configured for Rational Asset Manager to communicate between servers in the cluster. Confirm that JMS is configured correctly and click Next.
  17. Optional: In Section 4, Part 3, configure performance settings for WebSphere Application Server:
    1. Configure server settings.
      • Class garbage collection: Optional: Type the name of the garbage collection algorithm to use. The recommended value is intended to result in increased server performance:
        • -XX:+UseParallelGC
        • For Linux: For AIX: For Linux for zSeries: -Xgcpolicy:optavgpause
      • Performance monitoring: Performance monitoring should remain disabled. To turn on performance monitoring on the application server, check Enable.
      • Maximum number of sessions: Type the number of sessions that WebSphere Application Server will maintain in memory. The default value is 1000. To allow more sessions to be maintained in memory, increase this number.
      • JDBC maximum connections: Type a number that is equal to or greater than the number of users that might be logged in to Rational Asset Manager at one time. For example, 100.
      • Session timeout (minutes): Type a number for the number of minutes before a user's session times out. The default number of minutes in WebSphere Application Server is 30.
        Tip: Although reducing the Session timeout value might allow for more users, especially if many users will be making brief transactions, setting the timeout too low might interfere with a user's experience or prevent users from uploading large assets.
      • Web container minimum size: Type the minimum number of threads to allow in the Web container. The default value is 25 for Windows and 15 for Linux and AIX. If the processor for the server is underutilized, increase this number; if the processor is overutilized, decrease the number.
      • Web container maximum size: Type the maximum number of threads to allow in the Web container. The default value is 50 for Windows and 30 for Linux and AIX. If the processor for the server is underutilized, increase this number; if the processor is overutilized, decrease the number.
    2. Click Next.
    3. On the Configure Java Virtual Memory Heap Settings page, change the heap size for the server. If you are installing to a cluster, you can set the heap size per node. The default is No setting. Before you select one of the other options (Low, Medium, or High), make sure that you know how much physical memory the computer has.
    4. Click Next. The summary page is displayed again.
  18. Restart the server. To restart WebSphere Application Server, at the bottom of the page, click Restart the Server, type the User ID and Password of the server administrator, and click Restart. You cannot launch any of the Rational Asset Manager deployed applications until the server has been restarted. After the server has restarted, the Lifecycle management settings page opens. If the server takes longer than 180 seconds to restart, navigate to the start page of the server setup application (http://<machine_name>:<port_number>/<Server_Setup_Context_Root> ; for example, http://localhost:13080/ram.setup) to access the Lifecycle management settings page.
  19. If you are using the embedded WebSphere Application Server, because you have now configured security, you will have to log in with the Username and Password of a WebSphere Application Server administrator. After you log in, the Lifecycle management settings page opens.
  20. In the Lifecycle management settings page, type the path and login information for the Rational Team Concert application:
    1. In the Rational Team Concert field, type the path to the Rational Team Concert location. You must use a secure (https://) connection. By default, this value is:
      • For the embedded WebSphere Application Server: https://localhost:13443/jazz
      • For an existing WebSphere Application Server: https://localhost:9443/jazz
    2. In the User ID field, type the username of the WebSphere Application Server repository administrator. By default, this is admin.
    3. In the Password field, type the password for the repository administrator. By default, this is admin.
    4. Click Configure server. This process may take a few minutes. After the configuration, the Summary page appears again.
  21. On the Summary page, click Start using Rational Asset Manager. The Web client opens.

What to do next

Next, configure the e-mail settings for Rational Asset Manager. To do so, see Configuring e-mail settings.

For additional performance tuning information, see the Tuning the performance of Rational Asset Manager.

Configuring the Rational Asset Manager server application

To finalize configuration of the IBM Rational Asset Manager server application, perform the steps in this section.

Before you begin

If you are using IBM WebSphere Application Server and you used the server setup application, you can use the server setup application to configure the repository. For more information, see Deploying and configuring application files by using the server setup application.

Note: Sample values in the section are for a basic standalone environment. For a more complex installations, the server administrator will need to customize these settings for their environment.

The application server that hosts the Rational Asset Manager server application must be started before you can complete the following steps:

  1. Verify that all of the repository servers are set to the same current date, time, and time zone.
  2. Access the Rational Asset Manager server application using the appropriate URL:
  3. Log in as an application server administrator:
  4. The first time that you access Rational Asset Manager, you will see a Configuration Error page. Click the here link and enter the administrator user ID and password at the prompts. The Configuration page opens.
  5. Specify the license server path and select the type of license that this repository will use:
    1. Under License Server Path, type the port number, then the full name of the license server, separated by '@'. For example, 8010@license_server_path. If you have redundant license servers, separate multiple entries with commas. (You must provide three servers.) For example, 27000@license_server_path_a.example.com, 27000@license_server_path_b.example.com, 27777@license_server_path_c.example.com.
    2. For License Type, select either Standard edition or Enterprise edition to configure what type of licenses this repository will use.
  6. In the Database section, verify that the user in the User field has full access to the Rational Asset Manager and Rational Team Concert databases. Otherwise, type the User and Password for a database user with full permissions.
  7. Specify the Web server path:
    1. Under Web Server Path, type:
      http://<machine_name>:<port_number>/<Rational_Asset_Manager_Context_Root>
      where <machine_name> is the host name of the application server, and <port_number> is the HTTP transport port, and <Rational_Asset_Manager_Context_Root> is the context root of the Rational Asset Manager application.

      If you are using a load balancer, specify the name of the load balancer. If you are using a Web proxy server without a load balancer specify the name of the Web server. If you use IPV6, use the IPV6 hostname; an IPV6 address will not work.

      For example, type:

      http://www.example.com:9080/ram
  8. Specify the Web Services path:
    1. Under Web Services Path, type:
      http://<host_name>:<port_number>/<Rational_Asset_Manager_Web_Services_Context_Root>
      where <host_name> is the host name of the application server, <port_number> is the HTTP transport port , and <Rational_Asset_Manager_Web_Services_Context_Root> is the context root for the Rational Asset Manager Web Services application.

      If you are using a load balancer, specify the name of the load balancer. If you are using a Web proxy server without a load balancer specify the name of the Web server. If you use IPV6, use the IPV6 hostname; an IPV6 address will not work.

      For example, type:

      http://www.example.com:9080/ram.ws
  9. In the Internal Rational Team Concert Path section, specify the path and login information for IBM Rational Team Concert:
    1. In the Path field, enter the secure path for Rational Team Concert server. For example, https://www.example.com:9443/jazz. If you use IPV6, use the IPV6 hostname; an IPV6 address will not work.
    2. In the User and Password fields, type the username and password of the application server administrator.
  10. If you have configured your web server to use LDAP authentication, you can configure Rational Asset Manager to use the LDAP registry to perform user authentication, retrieve user information, and leverage group bindings:
    1. LDAP Server's URL: The URL to the LDAP server; for example, ldap://<url>:389. For secure communication, use ldaps://<url>:636.
    2. User's Distinguished Name: A user name to use to log in to the registry in order to gain access. Enter the distinguished name of the user, for example, uid=123456,c=us,ou=exampleorganization,o=example.com.
    3. The password for the user: The password for the user above.
    4. A unique ID property for the user: The property name of the objectClass instance for the user that represents the unique ID. For example: (objectClass) person's serialNumber property, or the (objectClass) user's sAMAccountName property.
    5. User's Login ID property: The (objectClass) property that a user uses to log in. Even though it is common for the unique ID and login ID to be the same, it is possible that the registry may be set so that a user logs in using another ID (for example, using an e-mail address). Note that the Login ID property must be the same as the user's login ID, in Step 6.
    6. User's Phone Number property: The (objectClass) property that represents the telephone number of the user. For example: (objectClass) person's telephonenumber property.
    7. User's E-mail property: The (objectClass)'s property representing the e-mail address of the user. For example: (objectClass) person's mail property.
    8. User's display name property: The (objectClass) property representing the name for the user to display in the interface. For example: (objectClass) person's cn property.
    9. LDAP User base searching: To avoid searching parts of the registry that do not contain user objects, enter the value of the path of the root from where to start the search. For example, ou=exampleorganization,o=example.com.
    10. User search filter: The template to use when searching for a user. The %v represents the search term that was entered from an input text field. The search will perform as if a wild card is appended to the search term. The default search template is constructed to find all person objectClasses where either the mail property or the name property is the same as the search term.
    11. LDAP Group base search: Similar to a base search, this is the base search for searching groups. For example, ou=memberlist,ou=groups,o=example.com.
    12. Group search filter: Similar to the user based filter, this is the filter for searching groups. The default searches any of groupOfUniqueNames (static group), groupOfNames (static LDAP group), groupOfUrls (dynamic LDAP group), group (Active Directory defined group) for the search term entered by the user.
    13. Image URL template: It is common to store images somewhere other than an LDAP registry. You can retrieve a user's image using a URL by configuring this template to retrieve the image at the same time as the user information in the registry. In the template, ${property} represents a LDAP objectClass property of the user object that is going to be replaced when the image is retrieved. For example, for a user with a uid property=123456, the default template https://<ImageServer url>/photo/${uid}.jpg results in the URL https://<ImageServer URL>/photo/123456.jpg.
    Note: If you are using LDAP authentication and a single LDAP hostname is mapped to multiple IP address in your network configuration then you must use the WebSphere Application Server administrative console to apply the appropriate configuration property to prevent possible LDAP user account lockouts if users log in to Rational Asset Manager with invalid credentials.

    An invalid login causes the server to validate the user with each IP address and thus causes multiple login failures. If you have set a maximum number of login attempts, one invalid logon could cause an LDAP account lockout. To prevent this issue from occurring, follow the steps described here: http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg1PK42672

  11. (Optional) To configure Rational Asset Manager to perform some processing with a remote Java executable, which can improve performance, see Configuring remote processes.
  12. In the Disk Storage section, configure disk storage for assets and index files:
    Note: For Windows: For WebSphere: If you are using a remote file server or a WebSphere Application Server cluster, the same Windows user account (username and password) must be able to log on to every machine used by Rational Asset Manager. Otherwise, Rational Asset Manager will not be able to save files on different file servers.
    1. From the Persist type list, select how you want to store assets from the list. If you are planning to use IBM Rational ClearCase to store assets, it must already be installed and running, and your server must be running as a user who has rights to use Rational ClearCase.
    2. If you are using the file system to store assets, type the location in the Persist folder field; for example, d:\RAMStorage. On a cluster, the persist folder must be on a shared drive that all servers on the cluster can access.
    3. In the Local folder field, type the full path to the folder where you want to store temporary data used by the Web application; for example, e:\RAMlocalfolder. It must be on a local hard drive for the server; it must not be a shared drive. If you are installing to a cluster, each node in the cluster must have its own local storage folder that is not shared with the other nodes. If you are installing multiple servers on the same physical node, the servers should all use the same physical local storage folder.
    4. In the Index folder field, type the full path to the folder where you want to store search indexes. It must be on a local hard drive for the server; it must not be a shared drive.
    To improve performance, all three folders should be on different physical drives.
  13. Specify the documentation path:
    1. In the Path to Information center field, if the help and documentation Web application is on the same server as the server application, check Use default. Otherwise, clear the Use default check box and type the URL where the help Web application is installed; for example, http://www.example.com:9080/ram.help. If you use IPV6, use the IPV6 hostname; an IPV6 address will not work.
    2. Under Path to Asset-based Development process, if the Asset-based Development and Governance Process documentation Web application is on the same server as the server application, check Use default. Otherwise, clear the Use default check box and type the URL to where the help Web application is installed; for example, http://www.example.com:9080/ram.process. If you use IPV6, use the IPV6 hostname; an IPV6 address will not work.
  14. In the Job Schedules section, configure how frequently certain repetitive jobs will run:
  15. For each job in the Job Schedules section, edit the frequency for the jobs. Click Edit, and then select from the following options:
    1. To run the job at a certain interval of hours or minutes, select Schedule job to run at interval, type a number, and then select Minutes or Hours from the drop-down list.
    2. To run the job once per day or once per week, select Schedule job to run at a set time, select Every day or a specific day of the week, and then select a time from the drop-down list.
  16. Configure performance options:
    1. In the Performance Options section, if you do not want Rational Asset Manager to automatically generate thumbnails of artifacts that you attach to assets, clear the Automatically create featured content on asset submission checkbox. This can improve performance when submitting assets to the repository.
    2. If you do not want the search engine to consider the popularity of assets, clear the Enable popularity indexing checkbox. Clearing the checkbox can improve the performance for large repositories; however, the search engine will not use factors such as downloads and page views to deliver more relevant results.
    3. In the Maximum number of sessions per user field, type the maximum number of sessions a single user can open.
    This can affect performance of your server. For more information, see the performance tuning guide.
  17. At the bottom of the page, click Save.
  18. Restart your application server.
  19. Click on the Help link. (If the help system does not open, check that you included the documentation when you installed Rational Asset Manager server.)
  20. In the navigation pane of the Help, navigate to Configuring -> Configuring Rational Asset Manager -> Optional configuration. Depending on your configuration, you might have to configure other aspects of Rational Asset Manager.

What to do next

If you want Rational Asset Manager to send out e-mail notifications, see Configuring e-mail settings.

Configuring e-mail settings

Set up the location of the SMTP server and information to use for sending e-mail messages to users. This information is used to send e-mail messages for user subscriptions and other notifications.

  1. Log on to the IBM Rational Asset Manager Web client as a repository administrator.
  2. Click Administration.
  3. Click Configuration.
  4. Locate the E-mail section of the Configuration page.
  5. In the SMTP server text field, type the location of the Simple Mail Transfer Protocol server; for example, smtp.example.com.
  6. In the Default return e-mail text field, type the e-mail address to be used in the reply-to field of automated outgoing messages.
  7. In the Default return e-mail name text field, type the name to be used in the name field of automated outgoing messages.
  8. Click Save.

Tuning the performance of Rational Asset Manager

The performance of IBM Rational Asset Manager heavily depends on how you tune your application server, database, Web server, caching proxy, load balancer, and operating system. This section provides guidelines for how to tune these systems and Rational Asset Manager. Although it is not possible to cover every setting, the information provided here is a good starting point for driving high user loads on Rational Asset Manager. This section does not cover hardware setups or the expected user loads that can be supported in various setups. Refer to the Rational Asset Manager Capacity Planning Guide for this information.

Rational Asset Manager tuning

The Rational Asset Manager configuration page has settings that you can adjust to achieve optimal performance. This page can be accessed by any repository administrator.

Table 11. Cross-Platform Rational Asset Manager Tuning Parameters
Problem Parameter / Setting Additional Details
Slow responses when searching for assets Local and index folders / Do not use a remote or shared folder

For best performance, each application server should have its own local and index folders on a hard disk local to the computer. This should not be the same hard disk on which the application server or operating system is installed.

To set the parameter, log in to Rational Asset Manager as an administrator and navigate to Administration -> Configuration; in the Disk Storage section, set the Local folder and Index folder parameters.

Slow responses when searching for assets Popularity indexing / Disable popularity indexing for search results

The search engine can consider the popularity (for example, views and downloads) of assets to deliver more relevant search results; however, this can affect the performance of large repositories.

To disable popularity indexing, log in to Rational Asset Manager as an administrator and navigate to Administration -> Configuration; in the Performance Options section, clear the Enable popularity indexing checkbox.

Slow responses when searching for assets. Index folder / Use a fast dedicated drive for the index folder

It is important that the index folder resides on a dedicated drive that is not used for other purposes. Separating the local folder and index folder helps to ensure quick response times when searching for assets.

To set the parameter, log in to Rational Asset Manager as an administrator and navigate to Administration -> Configuration; in the Disk Storage section, set the Index folder parameter.

General performance issues at regular intervals Statistics index builder schedule / 10 minutes

Frequently running the statistics index builder leads to poor performance. A default setting of 10 minutes is adequate for most environments.

To set the parameter, log in to Rational Asset Manager as an administrator and navigate to Administration -> Configuration -> Statistics index builder schedule.

General performance issues at regular intervals Process subscriptions schedule / Set time for low workload periods

Subscriptions can be processed at custom intervals. For better performance, set this interval to a time when Rational Asset Manager experiences a relatively low workload.

To set the parameter, log in to Rational Asset Manager as an administrator and navigate to Administration -> Configuration -> Process subscriptions schedule.

General performance issues at regular intervals User and group information update schedule / Set time for low workload periods

User and group information can be processed at custom intervals. For better performance, set this interval to a time when Rational Asset Manager experiences a relatively low workload.

To set the parameter, log in to Rational Asset Manager as an administrator and navigate to Administration -> Configuration -> User / group information update schedule.

General performance issues at regular intervals Review process notifications schedule / Set time for low workload periods

Review process notifications can be processed at custom intervals. For better performance, set this interval to a time when Rational Asset Manager experiences a relatively low workload.

To set the parameter, log in to Rational Asset Manager as an administrator and navigate to Administration -> Configuration -> Review process notification schedule.

Out of memory errors in logs - session issues Maximum number of sessions per user / 10

It's possible for a single user to exhaust all available sessions on a server. This might be the result of a poorly written script or a denial of service attack. To prevent against this possibility the default maximum sessions per user is set to 10. After a user reaches this limit they will not be able to create new sessions on the server.

To set the parameter, log in to Rational Asset Manager as an administrator and navigate to Administration -> Configuration; in the Performance Options section, set the Maximum number of sessions per user parameter.

Submitting an asset is slow Automatic creation of featured content on Submit / Disabled

When you submit an asset, Rational Asset Manager creates thumbnail images of artifacts that are attached to the asset. If the asset has many artifacts, submitting an asset can take a long time.

To disable the automatic creation of those thumbnails, log in to Rational Asset Manager as a repository administrator and navigate to Administration -> Configuration; in the Performance Options section, clear the Automatically create featured content on asset submission checkbox.

In addition to the above parameters, administrators can access the Job Status page in Rational Asset Manager by navigating to Administration -> Configuration -> View Job Status. This page will display currently running or previously run jobs that might impact performance in Rational Asset Manager. Error messages might also display on the Job Status page.

Application server tuning

Rational Asset Manager works closely with your application server; therefore, optimizing your application server settings will improve the performance of Rational Asset Manager.

This section specifically covers IBM WebSphere Application Server, version 6.1 settings that significantly affect performance. You can also adjust these setting in IBM WebSphere Application Server, version 6.0, but the instructions to set the parameters might be different.

Important: Back up your WebSphere Application Server profile before changing any parameters.

Table 12. Cross-Platform WebSphere Application Server V6.1 Tuning Parameters
Problem Parameter / Setting Additional Details
Out of memory errors in logs Java Virtual Machine heap size / Between 1300 and 2000

On a server with 4GB of memory is installed, you can specify two instances with a heap size of 1300MB, or one instance with a heap size of 2000MB. You must watch the system paging to make sure that there is enough memory available. If your server has 8GB of memory, then specify 2 instances with a heap size of 2000MB for each instance.

To set the parameter, log in to WebSphere Administrative Console and navigate to Servers -> Application servers -> Java and process management -> Process definition -> Java virtual machine -> Initial heap size and Maximum heap size.

Note that this setting should be applied to the Rational Asset Manager servers and the IBM Rational Team Concert server. In a cluster, the RTC server may be installed on its own node if needed.

Database connection errors JDBC Maximum Connections / 100

Make sure that there are enough JDBC connections available to support all users that are logged into Rational Asset Manager.

To set the parameter, log into the WebSphere Application Server Administrative Console and navigate to Resources -> JDBC -> Data sources -> <Rational Asset Manager data source> -> Connection pool properties -> Maximum connections.

Refer also to topic "MAXAPPLS and MAXAGENTS parameters" under DB2 tuning.

Refer also to topic "Maximum number of processes for AIX and Linux" under operating system tuning.

Out of memory errors in logs - session issues Maximum In-Memory Session Count / 200

By default, IBM WebSphere Application Server, version 6.1 maintains up to 1000 sessions in memory. However, the Allow Overflow option is also selected, which indicates that additional sessions will be stored in a secondary session table. These default settings can allow for potential out of memory conditions. It is best to limit the maximum number of in memory disabling the Allow Overflow option and setting the maximum in memory session count to a value that is appropriate for the server memory.

To set the parameter, log in to the WebSphere Application Server Administrative Console and navigate to Servers -> Application Servers -> <Server name> -> Session management -> Maximum in-memory session count.

Out of memory errors in logs - session issues Session Timeout / Default (30 minutes)

The default value for a session timeout in IBM WebSphere Application Server, version 6.1 is 30 minutes. Setting this value to a shorter time allows for more users, especially if you have many users making quick transactions. Setting this value too low might not allow users to upload very large assets. Remember that most users do not explicitly log out when they are done with a transaction: most sessions will exist until they timeout.

To set the parameter, log in to the WebSphere Application Server Administrative Console and navigate to Servers -> Application servers -> <Server name> -> Session management -> Set timeout.

Downloads for large assets are failing, possibly with Async or IO errors HTTP inbound channel (HTTP 2) Write timout / 300 seconds

The default value for a write timeout from the server to a client in IBM WebSphere Application Server, version 6.1 is 60 seconds. Setting this value to a longer time may prevent failures when download files, especially if the client that is downloading the files has a slow connection or is making many requests.

To change the parameter, log in to the WebSphere Application Server Administrative Console and navigate to Servers -> Application servers -> <Server name> -> Ports -> View associated transports (for the port that you are using for Rational Asset Manager; for example, 9080) -> WCInboundDefault -> HTTP inbound channel (HTTP 2) -> Write timeout.

High CPU usage observed Performance monitor infrastructure / disabled

By default, IBM WebSphere Application Server, version 6.1 enables basic performance monitor infrastructure (PMI). Although PMI is a good tool for tuning an application server, for maximum performance, disable this feature after the server has been properly tuned. You must disable it for all instances and node agents.

To set the parameter, log in to the WebSphere Application Server Administrative Console and navigate to Monitoring and Tuning -> Performance Monitoring Infrastructure (PMI) -> <Server name> -> Enable Performance Monitoring Infrastructure (PMI).

General performance issues Prepared Statement Cache / 100

WebSphere Application Server provides the ability cache commonly used prepared statements. If cached statements are being discarded, turn on PMI in WebSphere Application Server and increase the value.

To set the parameter, log in to the WebSphere Application Server Administrative Console and navigate to Resources -> JDBC -> Data sources -> <Rational Asset Manager data source> -> WebSphere Application Server data source properties -> Statement cache size.

Refer also to topic "Further Information for Tuning WebSphere Application Server."

Session timeout issues Maximum In-Memory Session Count / Default

By default, Websphere Application Server 6.1 will maintain up to 1000 sessions in memory. However, the Allow Overflow option is also selected, which indicates that additional sessions will be stored in a secondary session table. If you expect to have more than 1000 in memory sessions, you must increase the number for the secondary session table.

To set the parameter, log in to the WebSphere Application Server Administrative Console and navigate to Servers -> Application Servers -> <Server name> -> Session Management -> Maximum in-memory session count.

Periodic slowness; observed performance spikes due to garbage collections Class Garbage Collection / Xgcpolicy:optavgpause (for WebSphere Application Server Fix Pack 16 and below) or -Xgcpolicy:gencon (for WebSphere Application Server Fix Pack 17 and above)

Your specific server environment or workload might benefit from one of the other garbage collection settings. See http://java.sun.com/docs/hotspot/gc5.0/gc_tuning_5.html for more information on garbage collection settings.

To set the parameter, log in to the WebSphere Application Server Administrative Console and navigate to Servers -> Application servers -> <Server name> -> Java and process management -> Process definition -> Java virtual machine -> Generic JVM arguments.

Server fails during transfer of large files; possibly with out of memory or malloc errors in logs Web container custom property channelwritetype / synchronous data transfer (sync) The use of asynchronous data transfer might require an excessive number of buffers to send data over a TCP/IP connection.

1. In the WebSphere Application Server Administrative Console, navigate to Servers -> Application Servers -> serverName -> Web Container Settings -> Web Container -> Custom Properties.

2. Click New.

3. Add the following pair:

  • Name: com.ibm.ws.webcontainer.channelwritetype
  • Value: sync

Click OK and then save the configuration. Restart the application server to pick up the property.

For a deployment manager:

1. Start an interactive wsadmin session:

<dmgr-profile-root>\bin>wsadmin -lang jacl

2. Copy the following block of lines, then paste them all at once at the wsadmin> prompt:

set dmgr [$AdminConfig getid /Server:dmgr/]
set webcontainer [$AdminConfig list WebContainer $dmgr]
$AdminConfig create Property $webcontainer {{name com.ibm.ws.webcontainer.channelwritetype} {value sync}} properties
$AdminConfig show $webcontainer
$AdminConfig save

3. Restart the deployment manager to pick up the property.

For more information, refer to http://www.ibm.com/support/docview.wss?uid=swg21317658.

Table 13. AIX / Linux WebSphere Application Server V6.1 Tuning Parameters
Problem Parameter / Setting Additional Details
CPU is being overused or underused WebContainer Pools / 30

Web container threads are used by the application server to handle requests. If you notice that the CPU of the server is underused, try increasing this number. If it is overused, try reducing this number. Do not set the Web container threads above 50.

To set the parameter, log in to the WebSphere Application Server Administrative Console and navigate to Servers -> Application servers -> <Server name> -> Thread pools -> WebContainer.

Minimum size: 15

Maximum size: 30

Table 14. Windows WebSphere Application Server V6.1 Tuning Parameters
Problem Parameter / Setting Additional Details
CPU is being overused or underused WebContainer Pools / 50

Web container threads are used by the application server to handle requests. If you notice that the CPU of the server is underused, try increasing this number. If it is overused, try reducing this number. Do not set the Web container threads above 50.

To set the parameter, log in to the WebSphere Application Server Administrative Console and navigate to Servers -> Application servers -> <Server name> -> Thread pools -> WebContainer.

Minimum size: 25

Maximum size: 50

In addition to these parameters, you can tune WebSphere Application Server under a specific workload by turning on Performance Monitor Infrastructure (PMI). This will provide detailed graphs showing performance data. Although you should have PMI turned on under a normal workload to capture data, this will decrease performance and it should be turned off after data capture is complete.

To enable PMI, log in to the WebSphere Application Server Administrative Console and navigate to Monitoring and Tuning -> Performance Monitoring Infrastructure (PMI) -> <Server name> -> Enable Performance Monitoring Infrastructure (PMI).

Additional resources:

Database server tuning

To improve the performance of Rational Asset Manager, you should tune your database using the parameters and values below as a guide.

Note: This section is specific to DB2 version 9.5, but many of the parameters here are available in other versions of DB2. There might be similar parameters in Oracle and SQL Server.
Table 15. Cross-Platform DB2, version 9.5 Tuning Parameters
Problem Parameter / Setting Additional Details
No connections available MAXAPPLS / AUTOMATIC (WebSphere Application Server maximum JDBC connections * the number of instances)

Make sure that MAXAPPLS is set high enough to handle the number of JDBC Connection Pools that are specified in your application server. The MAXAPPLS setting must be greater than or equal to the JDBC Maximum Connections setting.

Setting location: Database parameters

Also refer to topic "JDBC Maximum Connections" under Application Server Tuning

No connections available MAXAGENTS / AUTOMATIC (WebSphere Application Server maximum JDBC connections * the number of instances)

Make sure that MAXAGENTS is set high enough to handle the number of JDBC Connection Pools that are specified in your application server. The MAXAGENTS setting must be greater than or equal to the JDBC Maximum Connections setting.

Setting location: Instance parameters

Also refer to topic "JDBC Maximum Connections" under Application Server Tuning

Deadlocks MAXLOCKS / AUTOMACTIC (80)

The MAXLOCKS parameter indicates the maximum percentage of available locks within DB2 that an application can hold before escalating row locks to table locks. These table locks can result in deadlocks.

Setting location: Database parameters

Deadlocks LOCKLIST / AUTOMATIC (20000)

The LOCKLIST parameter represents the available memory for locks in DB2. You can use the following formula to set this parameter in a specific environment:

LOCKLIST = [(512 * 64 * MAXAPPLS) / 4096]*2

Do not set this higher than the memory heap that is available to DB2. Setting location: Database parameters

Deadlocks LOCKTIMEOUT / 60

If a single lock is stopping other transactions, this can result in a deadlock. To make sure this does not happen, set the lock time out to 60 seconds.

Setting Location: Database parameters

General performance issues Statistics / Schedule regular runs Running statistics against the tables will help the optimizer determine the best path for accessing data. Statistics should be run on a regular basis or scheduled automatically.
Errors during database migrations LOG_FIL_SIZ / 10000 The migration function in Rational Asset Manager might not work on databases with thousands of assets of the LOG_FIL_SIZ is set too low.
Table 16. AIX / Linux DB2, version 9.5 Tuning Parameters
Problem Parameter / Setting Additional Details
Unable to access DB2 server *See Topic: Maximum number of processes for AIX and Linux under operating system tuning. If you cannot access the DB2 server, it might be possible that the db2agents have used the maximum number of processes.

Other parameters to check in your specific environment can include, but is not limited to:

Setting parameters to AUTOMATIC within DB2 will allow DB2 to tune the parameters based on the current workload. At first, this can result in a negative performance impact and some potential errors if certain values are not tuned quickly enough, but it is a good way to determine what parameters might need to be tuned to achieve maximum performance.

If you set a parameter too high and cannot start the DB2 control center, the parameter can be changed on the DB2 command line by using the statement db2 update db cfg for db_name using parameter_name value.

Additional Resources:

Web server tuning

This section provides tuning information for IBM HTTP Web Server, which is included in the supplements for Websphere Application Server.

The parameters that are described in this section can be modified in the httpd.conf file.

Table 17. Cross-Platform Web Server Tuning Parameters
Problem Parameter / Setting Additional Details
Connection closed errors MaxKeepAliveRequests / 0 This directive signifies the maximum number of requests that a single client can make before the connection is closed. Generally, this value is set to 0.
General performance issues LoadModule / ibm_afpa_module modules/mod_afpa_cache.so

To cache static content such as images, uncomment the following line:

LoadModule ibm_afpa_module modules/mod_afpa_cache.so

This will activate the Fast Response Cache Accelerator (FRCA).

General Performance Issues Afpa Logging / off

If you do not need FRCA logging turned on, you can turn it off by placing the comment character (‘#') before the AfpaLogFile directive. Doing this will also boost server performance.

#AfpaLogFile "_path_to_server_/logs/afpalog" V-ECLF
Table 18. AIX / Linux Web Server Tuning Parameters
Problem Parameter / Setting Additional Details
Out of threads errors in Web server logs ThreadLimit / 25 Depending on how many users access Rational Asset Manager at a given time, it might be necessary to increase the thread limit. To see if you need to increase the limit, check the Web server logs for out of threads errors or warnings.
Out of threads errors in Web server logs ThreadsPerChild / 25 Depending on how many users access Rational Asset Manager at a given time, it might be necessary to increase the thread limit. To see if you need to increase the limit, check the Web server logs for out of threads errors or warnings.
Table 19. Windows Web Server Tuning Parameters
Problem Parameter / Setting Additional Details
Out of threads errors in Web server logs ThreadLimit / 4000 Depending on how many users access Rational Asset Manager at a given time, it might be necessary to increase the thread limit. To see if you need to increase the limit, check the Web server logs for out of threads errors or warnings.
Out of threads errors in Web server logs ThreadsPerChild / 3000 Depending on how many users access Rational Asset Manager at a given time, it might be necessary to increase the thread limit. To see if you need to increase the limit, check the Web server logs for out of threads errors or warnings.

Additional Resources:

Caching proxy server tuning

This section specifically covers IBM Edge Caching Proxy. For information on DMZ caching proxy server configuration, see the DMZ caching proxy server configuration section.

You can modify the parameters that are described in this document in the ibmproxy.conf file.

Table 20. IBM Edge Server Tuning Parameters
Problem Parameter / Setting Additional Details
Unable to upload assets with large file sizes LimitRequestBody / 2G By default, this parameter is set to 10 M. Change this to a larger value so that users can upload large files.
Unable to upload assets with large file sizes due to timeouts InputTimeOut / 60 Minutes

Changing this parameter to 60 minutes will give users sufficient time to upload large assets.

Refer also to topic "Session Timeout" under Application Server Tuning

Unable to upload assets with large file sizes due to timeouts ReadTimeout / 60 Minutes

Changing this parameter to 60 minutes will give users sufficient time to upload large assets.

Refer also to topic "Session Timeout" under Application Server Tuning

Unable to upload assets with large file sizes due to timeouts ScriptTimeout / 60 Minutes

Changing this parameter to 60 minutes will give users sufficient time to upload large assets.

Refer also to topic "Session Timeout" under Application Server Tuning

Table 21. Additional Settings
Parameter Setting
SendRevProxyName yes
PurgeAge 3
DirShowCase off
MaxActiveThreads 110
ConnThreads 15
MaxPersistRequest 15
ServerConnPool on
CacheMemory 1200 M (max)
CacheAlgorithm responsetime
numclient 100
flexibleSocks off
listenBacklog 256

DMZ caching proxy server configuration

Follow these caching proxy server guidelines for better performance:

Operating System tuning

Cross-Platform:

Windows:

Table 22. Windows Operating System Settings
Problem Parameter / Setting Additional Details
"Address already in use" errors seen when testing with Rational Performance Tester. registry item MaxUserPort / 65534
  1. In the registry editor, navigate to My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters.
  2. Right-click Parameters, click New -> DWORD Value.
  3. Type MaxUserPort for the name of the DWORD value.
  4. Right-click the value and click Modify.
  5. Set the value to 65534.
  6. Under base, select Decimal.
  7. Reboot the computer.
To avoid session availability bottleneck (seen with 900 users on 6-instance cluster) registry item TcpTimedWaitDelay / 30
  1. In the registry editor, navigate to My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters.
  2. Right-click Parameters, click New -> DWORD Value.
  3. Type TcpTimedWaitDelay for the name of the DWORD value.
  4. Right-click the value and click Modify.
  5. Set the value to 30.
  6. Under Base, select Decimal.
  7. Reboot the computer.

Additional Resources:

AIX/Linux

The following instructions are specific to AIX.

Maximum number of processes

The maximum number of processes that a user can run must be set to a high enough level. This is especially true of the database server, which can have many database agents.

To view the set maximum number of processes, use the following command:

lsattr -E -l sys0 -a maxuproc

To set the maximum number of processes, use the following command:

chdev -l sys0 -a maxuproc=2000

This will result in a limit of 2000.

File descriptors

In the /etc/security/limits file, change all settings to unlimited.

Soft FILE Size      -1
Soft CPU Time       -1
Soft STACK Size     -1
Soft CORE File Size -1
Hard FILE Size      -1
Hard CPU Time       -1
Hard STACK Size     -1
Hard CORE File Size -1

This can also be accomplished by using the ulimit command.

Table 23. AIX/Linux Operating System Settings
Problem Parameter / Setting Additional Details
Going to external DNS /etc/netsvc.conf Add this line to the netsvc.conf file:
hosts=local,bind4
Ethernet adapter is doing Segmentation Offload
no -o tcp_recvspace=65536
no -o tcp_sendspace=65536
no -o udp_sendspace=65536
no -o udp_recvspace=65536
no -o tcp_finwait2=60
no -o tcp_timewait=1
no -o tcp_keepidle=600
no -o tcp_keepintvl=10
no -o tcp_keepinit=40
The impact of these commands is affected by how big the TCP/IP packets are that your application creates, sends, or receives. The "no -a" commands are in effect until the system is rebooted. To make them permanent, add them to the /etc/tunables/nextboot file. These can also be set on a per-tcpip-interface basis. Check the "lsattr -E -l en0" and if they are not set there, then AIX uses the "no -a" values.
AIX sees a number of virtual processors that is greater than the number of physical processors. smtctl -m off The AIX smtctl command shows how many virtual processors that AIX sees. Turn SMT off with the command:
smtctl -m off
The two threads on each physical processor share a Level1 cache. If the threads are unrelated, they corrupt the other cache data, which can end up slowing down the overall throughput as the system waits for more memory fetches to refresh the cache. Consider making a couple of test runs with this on and off to see what setting is best for your workload.
NIS is running. Disable NIS. If the /etc/hosts and /etc/passwd files contain lines with '+', then the system is running 'NIS', also called YellowPages. This can also be seen by
ps -ef | grep yp
NIS is not normally enabled on AIX-out-of-the-box. If you do not need this for the application server, consider a test run with NIS disabled.
Many sockets in FIN_WAIT_2 state no -o tcp_finwait2=60

If the "netstat -an" shows many sockets in FIN_WAIT_2 state, this means "high connection rates occur" and will correspond to the "Address already in use" message that is in server logs.

This can be controlled by a "no" command. First look at the current setting,

"no -a | grep fin"

and see the default of 1200 half-seconds (i.e., 10 minutes). Try a test run with the following setting:

no -o tcp_finwait2=60

The "no" command is good until reset or until a reboot. To make it permanent, define it in /etc/tunables/nextboot.

The processor is capable of using large pages, but is not doing so. Add parameter to JVM: -Xlp/-Xlp64 Enables 64 KB pages.

Additional Resources:

Configuring remote processes

To improve the performance of the Web application, you can configure IBM Rational Asset Manager to perform some of its processing using a Java executable other than the one in the Web container. You must be an administrator to configure remote processing.

About this task

  1. In the Web client, click Administration.
  2. Click Configuration.
  3. In the Remote Processes section, select the Java runtime environment that you want to use for Rational Asset Manager processes that could be handled outside the Web container:
  4. Click Save.

Configuring the embedded WebSphere Application Server as a service (Windows and Linux only)

If you installed the embedded IBM WebSphere Application Server, it is not automatically configured as a service for your operating system; you must start and stop the server manually. You can create a service to start the server automatically for you.

About this task

Note: These commands will not work on AIX or Linux for zSeries

To create a service for the embedded WebSphere Application Server:

  1. See the WebSphere Application Server documentation on using the WASService command.
  2. Use these example WASService commands to help you set up the service:

What to do next

If you change the administrative security for the embedded WebSphere Application Server, you must update the service commands with the updated username and password.

Additional configuration requirements for Linux and AIX

If you are running IBM Rational Asset Manager on Linux or AIX, perform the tasks in this section as needed to complete your configuration.

Enabling artifact content indexing for Linux and AIX

To enable artifact content indexing on Linux and AIX, you must add the Stellent files to your library path environment variable LD_LIBRARY_PATH (for Linux) or LIBPATH (for AIX).

Before you begin

The Stellent files are located in the following directories, depending on which application you used for installing IBM Rational Asset Manager server:

About this task

If you do not modify your library path variable to enable content indexing, you typically see an error on the Rational Asset Manager status page indicating that artifact indexing has been turned off.

To add update your library variable:

  1. Consult your shell's man page for specific details on how to set environment variables. For example, in the Bash shell, enter the command LD_LIBRARY_PATH=$LD_LIBRARY_PATH:path for WebSphere Application Server or Tomcat path shown above.
  2. After you update the environment variable, restart the Rational Asset Manager server.

Enabling content indexing (Linux and AIX)

To run IBM WebSphere Application Server or Apache Tomcat, you must set the appropriate exporter permission on the directory that contains the files for Stellent content indexing.

About this task

To set exporter permission:

  1. Log in as root.
  2. In a command line, change to the directory of the Stellent content indexing files described in Enabling artifact content indexing for Linux and AIX.
  3. Type the following command: chmod 755 exporter.

Enabling database connectivity for non-root users (Linux and AIX)

If you must run IBM WebSphere Application Server or Apache Tomcat as a non-root user, then you must set the appropriate permission on the database Java archive files that you upload.

About this task

To set permission:

  1. Log in as root.
  2. In a command line, change to the <WAS_install_directory>/profiles/<profile_name>/config/cells/<cell_name>/ram_jdbc directory.
  3. Type the following command: chmod 755 database jar file name (for example, chmod 755 db2jcc.jar).
  4. Repeat step 3 for each database Java archive file that you uploaded.

Installing the X Virtual Frame Buffer on AIX or Linux

On Linux, Linux for zSeries, or AIX operating systems, if you want to create thumbnails of the files that you attach to assets, you must install the X Virtual Frame Buffer (XVFB).

Before you begin

You must have administrative access to your operating system. The following instructions are for AIX and Linux, however this process is similar for other Linux distributions.

  1. Install the XVFB file sets. For AIX, the file sets are on the product CDs. Install the following file sets:
  2. Start XVFB:
  3. (Optional) For AIX: Verify that XVFB is running:
    1. Run the following command, where sysname is the system name, and n is the display number that you are checking:
      /usr/lpp/X11/Xamples/bin/xprop -display sysname:n -root | grep VFB 
    2. If XVFB is running, you will see the following string: XVFB_SCREEN(STRING) = "TRUE".
  4. For Linux: For AIX: Export the display:
    1. Run the following command, where n is the display number of XVFB:
      export DISPLAY=:n
  5. For Linux: Export the gdfontpath:
    1. Run the following command, where font_path is the full path to a folder that contains .ttf system fonts (for example, <WebSphere_Application_Server_install_location>/java/jre/lib/fonts):
      export GDFONTPATH=font_path
      Tip: Use the following command to find folders that contain .ttf fonts:
      find / -name *.ttf
  6. If you have not set the LD_LIBRARY_PATH (for Linux) or LIBPATH (for AIX) variable, export the variable. For more information, see Enabling artifact content indexing for Linux and AIX

Results

For more information about installing and verifying XVFB on AIX, see the AIX Programming Guide.

Creating a backup of a Rational Asset Manager repository

You can create a backup copy of your IBM Rational Asset Manager repository, which you can restore later.

Before you begin

To create a backup repository, you must have administrator access to Rational Asset Manager, full administrative access to the database server, and access to the Persist storage folder for each application server.

About this task

To create a backup repository:

  1. Log in to the Rational Asset Manager Web client as an administrator.
  2. Go to Administration -> Configuration.
  3. Note the location of the persist folder.
  4. Stop the server.
  5. On the computer where the database is located, create a backup of the Rational Asset Manager database. For instructions, see the documentation for your database application.
  6. In the operating system, create a backup copy of the persist folder.
  7. Create a backup of your Rational Asset Manager database. For more information, see the documentation for your database software.

What to do next

With the persist folder and databases, you can recover your repository.

Installing the Rational Asset Manager Eclipse client

This section contains the instructions to install the IBM Rational Asset Manager Eclipse client.

About this task

You can install the Rational Asset Manager Eclipse client by either of two methods:

Installing Rational Asset Manager Eclipse client using Eclipse update manager

You can install the IBM Rational Asset Manager Eclipse client into an existing version of Eclipse by using the Eclipse update manager. This method insures that your the versions of Rational Asset Manager on your Eclipse client and on the server are compatible.

Before you begin

You can use the Rational Asset Manager Eclipse client with a Rational Asset Manager server of the same release version and one release version prior to that. Release versions include the original release and its fix packs. For example, you can use a Rational Asset Manager Eclipse client of version 7.1.1 with a Rational Asset Manager server of versions 7.1.1, 7.1.0, and 7.1.0.1.

Your Eclipse IDE must meet the software requirements before you can install the Rational Asset Manager Eclipse client into it. See Software requirements for detailed requirements. You must also know the URL for accessing the Rational Asset Manager server using the Web client.

Note: These instructions are for Eclipse 3.3. The process for installing new software is slightly different in each version of Eclipse. For example, in Eclipse 3.5 the update manager is located in Help -> Install New Software

  1. Start Eclipse.
  2. Click Help -> Software Updates -> Find and Install.
  3. In the Install/Update pane, select Search for new features to install.
  4. Click New Remote Site
  5. Provide the Update site details:
    1. Type a name for the new entry; for example, type Rational Asset Manager.
    2. Open the Rational Asset Manager Web client and click Help -> Extensions.
    3. On the Extensions page, in the Eclipse Client Plug-in section copy the URL listed next to Update site and paste it into the URL field.

      If the Rational Asset Manager server is only available on an https protocol, the Eclipse client will not be able to use the update site. To resolve this, refer to the topic Adding the server public certificate to the Eclipse client.

  6. Click OK.
  7. Select the new Rational Asset Manager site and click Finish. The Update wizard opens.
  8. Expand and select the plug-ins to install and click Next.

    If the Eclipse client you are using does not have IBM Rational Team Concert installed, do not select Rational Asset Manager Eclipse Client Integration -> Rational Asset Manager Eclipse RTC Client integration.

    The two "IBM Rational common user assistance" plug-ins have similar names, but they have different content and are both required for the help system.

    Note: If you are installing the Rational Asset Manager Eclipse client into IBM Rational Team Concert, you can clear these features, which should already be installed:
    • IBM Rational common user assistance
    • IBM Rational common user assistance resources
  9. Accept the license agreement and click Next.
  10. Click Finish.
  11. If you see an error that says An error occurred while collecting items to be installed - Unpack facility not configured, you must restart Eclipse with a command to use a Java JRE that can unpack the files at the update site:
    1. Locate a Java JRE on your file system. For example, C:\Program Files\IBM\Java\jre\bin or C:\Program Files\Java\jre\bin.
    2. Launch Eclipse with the -vm argument that points to the location of the JRE. For example, eclipse.exe -vm C:\Program Files\IBM\Java\jre\bin.
    3. Try the procedure starting at step 2.
  12. When the installation finishes, restart Eclipse.

Results

To verify that the installation was successful, open the Asset Management perspective; click Window -> Open Perspective -> Other and then select Asset Management from the list. Click OK.

Installing Rational Asset Manager Eclipse client by using Installation Manager

Install the IBM Rational Asset Manager Eclipse client package by using the IBM Installation Manager GUI.

Before you begin

If you do not have access to a graphical user interface, you can use response scripts over the command line.

  1. Start the Rational Asset Manager launchpad program (see Installing from the launchpad program) and select IBM Rational Asset Manager. If Installation Manager is not installed, install it by following the steps in the installation wizard. The installation wizard opens.
  2. The Installation page of the installation wizard lists all the packages that Installation Manager found in the repositories.
  3. To search for updates to the Rational Asset Manager package, click Check for updates.
  4. Select the Rational Asset Manager client and any updates to the package to install. Updates that have dependencies are automatically selected and cleared together. To continue, click Next.
    Note: If you install packages at the same time, all of the packages install into the same package group.
  5. On the Licenses page, read the license agreement for the selected package. If you selected more than one package to install, there might be a license agreement for each package. To display the license agreement for a package, on the left side of the License page, click each package version. The package versions that you selected to install are listed under the package name.
    1. If you agree to the terms of all of the license agreements, click I accept the terms of the license agreements.
    2. To continue, click Next.
  6. If you install the first package on this computer, then on the Location page, either type the path for the shared resources directory in the Shared Resources Directory field or accept the default path. The shared resources directory contains resources that package groups can share. To continue, click Next.

    Default paths:

    Important: You can specify the shared resources directory only the first time that you install a package. To ensure adequate space for the shared resources of future packages, use your largest disk for this directory. You cannot change the directory location unless you uninstall all of the packages.
  7. On the Location page, either choose an existing package group to install the Rational Asset Manager Eclipse client package into, or create a new one. A package group represents a directory in which packages share resources. To create a package group:
    1. Click Create a new package group.
    2. Type the path for the installation directory for the package group. The name for the package group is created automatically.

      Default paths:

      • For Windows. C:\Program Files\IBM\SDP70
      • For Linux. /opt/IBM/SDP70
    3. To continue, Click Next.
  8. If an Eclipse IDE is installed on your system, you can extend its functionality to the packages that you are installing.
  9. On the Features page under Languages, select the languages for the package group. The corresponding national language translations for the user interface and documentation for the Rational Asset Manager package are installed. Your choices apply to all of the packages that are installed under this package group.
  10. On the next Features page, click Next. You cannot clear the IBM Rational Asset Manager client feature.
  11. Before you install the Rational Asset Manager package, review your choices on the Summary page. To change your choices, click Back and make your changes. When you are satisfied with your installation choices, click Install to install the package. An indicator shows the progress of the installation.
  12. When the installation process is complete, a message confirms the success of the process.
    1. Click Finish. The installation wizard closes and you are returned to the Start page of Installation Manager.

Adding the server public certificate to the Eclipse client

If the IBM Rational Asset Manager server is only available on an https protocol, the Eclipse client cannot use the update site. To resolve this, you must add the public certificate of the server to the Eclipse client.

About this task

These instructions are for a Windows computer with a Firefox browser. Instructions for Linux are similar.

  1. Save the certificate.
    1. Access the Rational Asset Manager Web client using a browser.
    2. Double-click the security icon in the status bar. The Security window opens.
    3. Click View Certificate.
    4. In the Certificate Viewer, click the Details tab.
    5. On the Details page, click Export.
    6. In the Save Certificate to File window, select X.509 Certificate (DER) in the Save as Type list.
    7. Click Save.
  2. (Optional) Create the keystore. You can use an existing keystore or create a new one. To create a new keystore, run the following command from a command prompt:
    keytool.exe -genkey -keystore ram.keystore -storepass ibmram
    The keystore will contain the keys for the Eclipse client.
  3. Import the certificate to the keystore.
    1. From a command prompt, run the following command to import the certificate:
      keytool.exe  -import -alias [server] -file [server].der -keystore ram.keystore -storepass ibmram
      Where server is the name of the server with Rational Asset Manager server.
    2. Type yes to accept the certificate and press Enter.
    3. Verify that the certificate was added to the keystore.
  4. Launch the Eclipse client from a command prompt using the following command:
    eclipse -vmargs -Djavax.net.ssl.trustStore="drive:\path\to\certificate\ram.keystore" -Djavax.net.ssl.trustStorePassword=ibmram
    Where drive:\path\to\certificate\ram.keystore is the full path to the ram.keystore file. Eclipse will start and will trust the connection with the server.

Uninstalling Rational Asset Manager

You can use the Uninstall option in the IBM Installation Manager to uninstall packages from a single installation location. You can also uninstall all the installed packages from every installation location.

Before you begin

Beginning in IBM Rational Asset Manager version 7.2, the default installation process was changed so that Installation Manager installs the Rational Asset Manager server setup application only and the server setup application deploys the Rational Asset Manager application .ear files. Therefore, to uninstall Rational Asset Manager from your server, you must remove the Rational Asset Manager application .ear files using the server setup application and then use the Installation Manger to remove the Rational Asset Manager server setup application from the IBM WebSphere Application Server application and delete Rational Asset Manager folders.

To uninstall the packages, you must log in to the system using the same user account that you used to install the product packages.

Note: If you are uninstalling Rational Asset Manager server, Installation Manager will only remove the files that it installed. If you installed the Rational Asset Manager server manually on an application server, then you must uninstall it manually.
Note: If you deployed enterprise or Web archive files using the Rational Asset Manager server setup application, you must uninstall them manually or through the server setup application. Installation Manager can only uninstall applications that it has installed.

About this task

To uninstall the packages:

  1. Close the programs that you installed using Installation Manager.
  2. If you are uninstalling Rational Asset Manager server on embedded WebSphere Application Server, then stop the server. For example, run the stopServer.bat server1 from a command prompt in the WAS_PROFILE/bin folder.
  3. On the Start page click Uninstall.
  4. In the Uninstall Packages page, select the Rational Asset Manager product package that you want to uninstall. Click Next.
  5. In the Summary page, review the list of packages that will be uninstalled and then click Uninstall. The Complete page is displayed after the packages are removed.
  6. Click Finish to exit the wizard.

Uninstalling with the server setup application and Installation Manager

If you used the IBM Rational Asset Manager server setup application to deploy Rational Asset Manager applications, you can use the Server Setup application and the Uninstall wizard in IBM Installation Manager to remove some of the applications, but you must manually remove some settings and configurations.

  1. In a Web browser, open the Rational Asset Manager server setup application and log in as an administrator. Because the server is configured, the summary page will open.
  2. Click the Deployment step.
  3. Click Next.
  4. For every application that you want to remove, click Uninstall.
  5. If you used Installation Manager to deploy the server setup application, you can use the Uninstall wizard in Installation Manager to remove it. Next:
  6. Open the IBM WebSphere Application Server Administrative Console.
  7. Delete the datasource.
    1. Locate and click the Datasource with the JNDI name jdbc/RAM_Con
      • If you are using a standalone server, you may find it under the Server scope.
      • If you are using a network server, you may find it under the cluster that Rational Asset Manager was installed on.
    2. Note the name of the component-managed authentication alias that the datasource uses.
    3. Delete the datasource.
    4. Navigate to Security -> Secure administration, applications & Infrastructure -> Java Authentication and Authorization Service -> J2C Authentication Data.
    5. Delete the entry whose name matches the component-managed authentication alias that you noted.
  8. If necessary, manually uninstall each enterprise or Web archive to be removed from the application server:
    1. Click Applications.
    2. Click Enterprise Applications.
    3. Select each of the following applications that remain:
      1. RAM1WebApplication
      2. com.ibm.ram.repository.setup.web.ear (Installation Manager might have removed this application for you)
      3. iehs_war
      4. jazz_war
      5. rmcabdgovernprocess_war
    4. Click Uninstall.
  9. Delete custom properties for IBM Rational Team Concert:
    1. Click Application servers.
    2. Click the name of the server where you deployed Rational Team Concert.
    3. Click Java and Process Management.
    4. Click Process Definition.
    5. Click Java Virtual Machine.
    6. Click Custom Properties.
    7. Select the following properties:
      1. JAZZ_HOME (the value of this variable will be a folder on your hard drive that you will have to delete)
      2. java.awt.headless
      3. org.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin
      4. (if you used an Oracle database) ORACLE_JDBC
      5. (if you used a Microsoft SQL Server database) SQLSERVER_JDBC
    8. Click Delete.
  10. Stop the server. On a cluster, you only need to stop the application server that was running Rational Team Concert.
  11. Navigate to the following directory on your hard drive: <WebSphere_install_directory>\profiles\<profile_name>\logs\temp\<server_name>\ On a cluster, this directory will be on the machine with the application server that was running Rational Team Concert.
  12. Delete the jazz_war folder.
  13. Navigate to the following directory on your hard drive (the value of the JAZZ_HOME property, above): <WebSphere_install_directory>\profiles\<profile_name>\config\cells\<cell_name>\nodes\<node_name>\servers\<server_name>\. On a cluster, this directory will be on the machine where Deployment Manager is installed.
  14. Delete the RTC folder.

Uninstalling from WebSphere Application Server manually

To uninstall IBM Rational Asset Manager manually, use the following instructions to uninstall the enterprise and Web archives from the application server and remove any other settings and configurations.

Before you begin

If you used the server setup application or Installation Manager to help you deploy the application files, you can use them to help you remove files. For more information, see Uninstalling with the server setup application and Installation Manager.

  1. Start the IBM WebSphere Application Server Administrative Console.
  2. Log in using an administrator user ID and password.
  3. Delete the datasource.
    1. Locate and click the Datasource with the JNDI name jdbc/RAM_Con
      • If you are using a standalone server, you may find it under the Server scope.
      • If you are using a network server, you may find it under the cluster that Rational Asset Manager was installed on.
    2. Note the name of the component-managed authentication alias that the datasource uses.
    3. Delete the datasource.
    4. Navigate to Security -> Secure administration, applications & Infrastructure -> Java Authentication and Authorization Service -> J2C Authentication Data.
    5. Delete the entry whose name matches the component-managed authentication alias that you noted.
  4. Optionally, if your server is a network deployment, delete system integration bus.
    1. Navigate to Service Integration -> Buses.
    2. Delete the bus named RAMBus.
    3. Navigate to Resources -> JMS -> Connection Factories.
    4. Delete the factory named RAM Factory. It might be under the scope of the cluster that Rational Asset Manager was installed on.
    5. Navigate to Resources -> JMS -> Topics.
    6. Delete the topic named RAM Cache. It might be located under the scope of the cluster that Rational Asset Manager was installed on.
  5. Remove the applications.
    1. Click Applications -> Enterprise Applications in the navigation pane.
    2. Check any of the applications that are installed:
      • RAM1WebApplication
      • com.ibm.ram.repository.setup.web.ear
      • iehs_war
      • rmcabdgovernprocess_war
      • jazz_war
    3. Click Uninstall.
    4. Click Save to apply the changes to the master configuration.
  6. Delete custom properties for IBM Rational Team Concert:
    1. Click Application servers.
    2. Click the name of the server where you deployed Rational Team Concert.
    3. Click Java and Process Management.
    4. Click Process Definition.
    5. Click Java Virtual Machine.
    6. Click Custom Properties.
    7. Select the following properties:
      1. JAZZ_HOME (the value of this variable will be a folder on your hard drive that you will have to delete)
      2. java.awt.headless
      3. org.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin
      4. (if you used an Oracle database) ORACLE_JDBC
      5. (if you used a Microsoft SQL Server database) SQLSERVER_JDBC
    8. Click Delete.
  7. Optionally, if Rational Asset Manager was the only application on the server, remove any environment variables.
    1. Click Environment -> WebSphere Variables in the navigation pane.
    2. Click the name of any environment variables that were set up for Rational Asset Manager (for example, Oracle_JDBC_DRIVER_PATH).
    3. Click Delete.
    4. Click Save to apply the changes to the master configuration.
  8. Optionally, re-configure authentication and security settings. If you configured security specifically for Rational Asset Manager, then revert any settings to the previous configuration. If the security settings apply to other applications, do not modify them.
  9. Stop the server. On a cluster, you only need to stop the application server that was running Rational Team Concert.
  10. Navigate to the following directory on your hard drive: <WebSphere_install_directory>\profiles\<profile_name>\logs\temp\<server_name>\ On a cluster, this directory will be on the machine with the application server that was running Rational Team Concert.
  11. Delete the jazz_war folder.
  12. Navigate to the following directory on your hard drive (the value of the JAZZ_HOME property, above): <WebSphere_install_directory>\profiles\<profile_name>\config\cells\<cell_name>\nodes\<node_name>\servers\<server_name>\. On a cluster, this directory will be on the machine where Deployment Manager is installed.
  13. Delete the RTC folder.
  14. Restart the server.

Notices

© Copyright IBM Corporation 2007, 2009. All rights reserved.

Note to U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

Intellectual Property Dept. for Rational Software
IBM Corporation
20 Maguire Road
Lexington, Massachusetts 02421-3112
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this Documentation and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

Trademarks and service marks

IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at www.ibm.com/legal/copytrade.html.

Adobe is a registered trademark of Adobe Systems Incorporated in the United States, and/or other countries.

Intel® and Pentium® are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product or service names, may be trademarks or service marks of others.


Feedback