IBM Rational Asset Manager, version 7.5.0.2

Installation guide

Version 7.5.0.2
Note

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

First Edition (March 2011)

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

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

Contents

Guides 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.7
Registering the DB2 license key
Installing Rational License Key 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 email settings
Configuring LDAP authentication for Tomcat
Configuring the Tomcat server for Rational Asset Manager to use LDAP
Configuring Rational Team Concert on Tomcat to use LDAP
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 content indexing on Linux and AIX
Enabling database connectivity for non-root users (Linux and AIX)
Installing the X Virtual Frame Buffer on AIX or Linux
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
Backing up and restoring
Creating a backup of a Rational Asset Manager repository
Restoring from a backup
Uninstalling Rational Asset Manager
Uninstalling with the server setup application and Installation Manager
Uninstalling from WebSphere Application Server manually
Notices
Trademarks and service marks

Guides 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

The embedded WebSphere Application Server that you install with IBM Installation Manager is not intended for a large-scale deployment of Rational Asset Manager. You do not have complete access to the WebSphere administrative console and accordingly will not be able to fully manage application, security, and performance settings.

For larger deployments, consider using a dedicated WebSphere Application Server or WebSphere Application Server Network-Deployment cluster of servers.

Note: To create and use a cluster of application servers, you must have IBM WebSphere Application Server Network Deployment (ND), which is not bundled with IBM Rational Asset Manager.

Procedure

  1. Install a database application for Rational Asset Manager:

    Rational Asset Manager requires a database for storing assets and associated data. If you do not have one of the supported database applications installed, you can install IBM DB2® Enterprise Server Edition, version 9.7 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 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 content indexing to run for non-root users.
    2. Enable database connectivity for non-root users.
    3. Install the X Virtual Frame Buffer
  6. Configure the email 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:

Procedure

  1. Install a database application for Rational Asset Manager:

    Rational Asset Manager requires a database for storing assets and associated data. If you do not have one of the supported database applications installed, you can install IBM DB2 Enterprise Server Edition, version 9.7 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 content indexing to run for non-root users.
    2. Enable database connectivity for non-root users.
    3. Install the X Virtual Frame Buffer
  8. Configure the email 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.

Procedure

  1. Install a database application for Rational Asset Manager:

    Rational Asset Manager requires a database for storing assets and associated data. If you do not have one of the supported database applications installed, you can install IBM DB2 Enterprise Server Edition, version 9.7 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 a database 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 content indexing to run for non-root users.
    2. Enable database connectivity for non-root users.
    3. 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 email 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

The following topics explain how to upgrade Rational Asset Manager to the current version from any previous version.

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 must upgrade your license server and file a request for updated license keys. For more information on the required version of Rational License Server, see Installing Rational License Key Server.

You will also have to stop and restart your application server several times.

You can also configure an existing Rational Team Concert server to work with Rational Asset Manager. The server setup application will handle the configuration. You must know the username and password for the Rational Team Concert server administrator.

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.

About this task

This outline shows what you must do to upgrade to the latest version of Rational Asset Manager:

  1. Prepare to upgrade by making backups and configuring your application server: steps 1-6.
  2. If you are using a WebSphere Application Server Network Deployment cluster and you are upgrading from V7.1.1.1 or earlier, create a stand-alone application server instance on your cluster for Rational Team Concert: step 7.
  3. If you are using Oracle, copy the additional JDBC .jar files: steps 8-9.
  4. Install the required interim fix pack on your WebSphere Application Server or cluster V6.1: step 10.
  5. If you are using the embedded WebSphere Application Server, stop the server: step 11.
  6. Upgrade your license server to Rational Common Licensing V8.1.1: step 12.
  7. Retrieve the application files for the latest version of Rational Asset Manager and deploy the server setup application: steps 13-14.
  8. Use the server setup application to update the other Rational Asset Manager applications: steps 15-18.
  9. If you are upgrading from V7.1.1.1 or earlier and you need Rational Team Concert, deploy Rational Team Concert to your server and create a database: steps 20-24.
  10. Restart the application server: step 26.
  11. If you are upgrading from V7.1.1.1 or earlier, configure Rational Team Concert: step 27.
  12. Log in to the Rational Asset Manager web client and migrate the repository: steps 28-29.
  13. Reconfigure some settings for Rational Asset Manager: steps 31-32.
  14. Clear the cache for the help application: step 33.
  15. Update the Rational Asset Manager Eclipse application: step 34.

Procedure

  1. Before you upgrade, create a full backup of your repository, databases, asset files, and application server settings per the instructions in Creating a backup of a Rational Asset Manager repository.
  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 3072:
    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 3072, increase the limit with the following command: ulimit -n 3072
  3. If you have modified your theme or email messages, before you update the Rational Asset Manager server, download the current theme and mail message files (on the Administration -> Tools page) and then, after you have updated the server, reapply the theme and your messages.
  4. 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 Global security.
    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 and SIP 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.
  5. 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.
  6. Verify that all of the repository servers are set to the same current date, time, and time zone.
  7. For WebSphere:If you are upgrading from version 7.1.1.1 or earlier and use a WebSphere Application Server cluster and you need to install Rational Team Concert, 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 distributed 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.
  8. For Oracle: If you are using Oracle, copy the following additional JDBC .jar file to the WebSphere_install_directory/profiles/profile_name/config/cells/cell_name/ram_jdbc directory for your application server: You can download the appropriate .jar files from Oracle; even if you are using Oracle 10g, download a package for Oracle 11 to find the appropriate .jar file.
  9. If you are using Oracle and you are using AIX, Linux, or Linux for zSeries, set the appropriate permissions for the new JDBC .jar file as described in Enabling database connectivity for non-root users (Linux and AIX).
  10. If you are not using the embedded WebSphere Application Server and you are using WebSphere Application Server V6.1, 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.
    Note: Do not stop your server if you are using a network deployment cluster or if you installed onto an existing 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. For Windows: For Linux: For AIX: Migrate your Rational Licensing Server to Rational Common Licensing V8.1.1 or later. For more information, see Migrating from Rational Licensing Server v7.1.x or earlier to Rational Common Licensing.

    Rational License Key Server is included with the Rational Asset Manager installation media. You can also retrieve the latest version of Rational License Server through your Passport Advantage account, or through the Rational Download Center.

    This process requires that you shut down all applications that use Rational Licensing Server, uninstall your existing Rational Licensing Server, update your license files, and install Rational Common Licensing server. For Windows, see Configuring a license server for Windows; for AIX or Linux, see Configuring a license server for UNIX.

    For Linux for zSeries, continue to use Rational License Server for UNIX and Linux 7.0.0.1.
  13. Retrieve the appropriate Rational Asset Manager applications:
  14. Deploy the Rational Asset Manager server setup application to your application server:
  15. 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 context root for the server setup application is 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.
  16. In the Step 1: Locate Installation Files section, click Provide the location of the files on the server and type the directory on the file system on the server that is running the server setup application 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:

    If you deployed the server setup application to an application server that is part of a cluster and you are accessing that application server, to upload the files to the server that is running the server setup application, click Upload the files to the server; then click Browse and select each of the required files.

  17. To verify that all required application files are in the directory, or to upload them to the server, click Verify Location. If you uploaded the application files, the server setup application will save them to a temporary directory. A message will verify if all the required files are present.
  18. 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.
  19. Next:
  20. Rational Team Concert is required for the enhanced lifecycle process. Next:
  21. On the Deploy Rational Asset Manager page:
    1. 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.
  22. Create a new database for asset lifecycles for Rational Team Concert
  23. 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 22.
    2. To test the connection, click Test Connection.
    3. If the connection succeeds, click Next.
  24. 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.
  25. Continue through the server setup application to configure or adjust your database and application server settings until you get to Part 4: Configure Lifecycle management settings.
  26. On the page for Part 4: Configure Lifecycle management settings, click Restart the Server. You will have to enter the user ID and password for the application server administrator. After the server has stopped and restarted, the Configure Lifecycle management settings page opens.
  27. In the Configure Lifecycle management settings page, type the path and login information for the Rational Team Concert application:
    1. In Step 1, In the Rational Team Concert server 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 Step 2, in the Jazz Administrator ID field, type the user ID of the administrator for the Rational Team Concert server (the default is admin); then, in the Password field, type the password for that user (by default, this is admin). If you just installed the Rational Team Concert with the server setup application, type the username and password for the application server administrator.
    3. In Step 3, in the Project Area Name field, type a descriptive name for the project area that will be created for lifecycles (for example, Rational Asset Manager lifecycles). Then, in the Project Area Administrator ID field, type the user ID for the user that you want to be the project area administrator. Then, type the Password for that user. If you are using an external Rational Team Concert server, the Project Area administrator will probably be a different user from the Jazz server administrator. If you are installing a new Rational Team Concert, the server setup application will suggest using the Jazz Administrator ID as the Project Area Administrator ID.
    4. Click Configure server. This process might take a few minutes. After the configuration, the Summary page appears.
  28. On the Summary page, click Start using Rational Asset Manager. or click Finish. The web client opens.
  29. 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.
  30. After you migrate the repository, stop and then restart your application server.
  31. 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.
  32. After configuration is complete, manually remap shared library references for the previous version of Rational Asset Manager to the RAM1WebApplication (for example, for the integration with IBM Rational ClearQuest® you must run the integration steps again after upgrading to the new Rational Asset Manage server).
  33. If you open the help application and it shows an older version of the help or you see errors, clear the cache for the Rational Asset Manager help application. See the documentation for your application server for instructions on clearing the cache. On a cluster, you will have to stop every application server and clear the cache for every node and server in the cluster. For the embedded WebSphere Application Server, to clear the cache:
    1. Stop the server.
    2. Delete the following directory: Rational_Asset_Manager_install_location/ram/ewas/profiles/profile1/temp/node_name/server_name/iehs_war/.
    3. Restart the server.
  34. 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 must upgrade your license server and file a request for updated license keys. For more information on the required version of Rational License Server, see Installing Rational License Key Server.

You will also have to stop and restart your application server several times.

You can improve the performance and stability of Rational Asset Manager by installing its web applications and the application files for the included IBM Rational Team Concert on separate Tomcat servers. Throughout this document, the installation directory for the Tomcat server for Rational Asset Manager is referred to as tomcat_install_directory. The installation directory for the Tomcat server for Rational Team Concert is tomcat_for_rtc_install_directory. If you are installing all the web applications on the same Tomcat server, the directories are the same.

About this task

This outline shows what you must do to upgrade to the latest version of Rational Asset Manager:

  1. Prepare to upgrade and back up important files and databases: steps 1-4.
  2. Retrieve the application files for the latest version of Rational Asset Manager: step 5.
  3. If you are upgrading from V7.1.1.1 or earlier, create an additional database: step 6.
  4. Shut down the Tomcat server: step 7.
  5. Upgrade your license server to Rational Common Licensing 8.1.1: step 8.
  6. Copy new shared library files for Rational Asset Manager and for Rational Common Licensing 8.1.1 and modify the Tomcat server startup files accordingly: steps 9-11.
  7. Configure the Tomcat server for single sign-on: step 12.
  8. Retrieve the current application files for the included Rational Team Concert: steps 13-14.
  9. If you are upgrading from V7.1.1.1 or earlier and you need Rational Team Concert, install Rational Team Concert on your application server: steps 17-24.
  10. If you are upgrading from V7.1.1.1 or earlier, configure Rational Team Concert: steps 25-31.
  11. If you are upgrading from V7.2 or later, upgrade the included Rational Team Concert: step 33.
  12. Remove the existing application files for Rational Asset Manager and install the new versions of the applications: steps 34-39.
  13. Log in to Rational Asset Manager and migrate the repository: step 40.
  14. If you are upgrading from V7.1.1.1 or earlier, configure Rational Asset Manager to connect to Rational Team Concert: step 42.
  15. Modify your settings to connect to your new Rational Common Licensing server: step 43.
  16. Upgrade any Eclipse clients: step 44.

Procedure

  1. Before you upgrade, create a full backup of your repository, databases, asset files, and application server settings per the instructions in Creating a backup of a Rational Asset Manager repository.
  2. If you have modified your theme or email messages, before you update the Rational Asset Manager server, download the current theme and mail message files (on the Administration -> Tools page) and then, after you have updated the server, reapply the theme and your messages.
  3. Verify that all of the repository servers are set to the same current date, time, and time zone.
  4. 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.
  5. Retrieve the application files on the appropriate archive for Tomcat and for your operating system. The application files are in the archive_extract_location/apps/tomcat/ folder.
  6. If you are upgrading from V7.1.1.1 or earlier: Create the database for asset lifecycles:
  7. Stop the Tomcat server or servers. Your repository and any other applications on your server will now be offline.
  8. For Windows: For Linux: For AIX: Migrate your Rational Licensing Server to Rational Common Licensing V8.1.1 or later. For more information, see Migrating from Rational Licensing Server v7.1.x or earlier to Rational Common Licensing.

    Rational License Key Server is included with the Rational Asset Manager installation media. You can also retrieve the latest version of Rational License Server through your Passport Advantage account, or through the Rational Download Center.

    This process requires that you shut down all applications that use Rational Licensing Server, uninstall your existing Rational Licensing Server, update your license files, and install Rational Common Licensing server. For Windows, see Configuring a license server for Windows; for AIX or Linux, see Configuring a license server for UNIX.

    For Linux for zSeries, continue to use Rational License Server for UNIX and Linux 7.0.0.1.
  9. Extract the shared library files to the \shared\lib folder for your Tomcat servers:
    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.
  10. For Windows: For Linux: For AIX: Extract the library files for Rational Licensing Key Server V8.1.1 to the tomcat_install_directory\shared\lib folder:
    Important: If you are installing on Linux for zSeries, do not complete this step
    1. Find and extract the archive_extract_location\sharedLibs\rlsclients_rlsibmratl_811_4.zip file.
    2. From the extracted .zip file, find the file rlsibmratl811_4.zip for your operating system and architecture. For example, the file for 32-bit Windows is in the win32 directory.
    3. Extract the contents of the appropriate rlsibmratl811_4.zip file.
    4. Copy the entire contents of the extracted rlsibmratl811_4.zip file to the tomcat_install_directory\shared\lib directory.
  11. For Windows: For Linux: For AIX: Modify the startup script for the Tomcat server for Rational Asset Manager
    1. Find the Tomcat startup file and open it in a text editor. On Windows, this file is tomcat_install_directory\bin\startup.bat. On Linux, AIX, or Linux for zSeries, it is tomcat_install_directory/bin/startup.sh.
    2. Search for a line that includes JAVA_OPTS=.
      • If the JAVA_OPTS environmental variable is already set, add the following option and value:
        • For Windows:
          -Djava.library.path="tomcat_install_directory\shared\lib"
        • For Linux: For AIX:
          -Djava.library.path=tomcat_install_directory/shared/lib
      • If the JAVA_OPTS environmental variable is not set, type the following text:
        • For Windows:
          set JAVA_OPTS=-Djava.library.path="tomcat_install_directory\shared\lib"
        • For Linux: For AIX:
          export JAVA_OPTS="-Djava.library.path=tomcat_install_directory/shared/lib"
  12. Configure the Tomcat server for single sign-on for all applications:
    1. In a text editor, open the tomcat_install_directory\conf\server.xml file.
    2. Search for the following text:
      <!--
      <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
      -->
    3. Uncomment the <Valve> element:
      <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
  13. On the installation media, find the archive_extract_location/apps/tomcat/RTC-server.zip file.
  14. Extract RTC-server.zip to a location on your hard disk drive, which is referred to in these instructions as rtc_install_dir.
  15. Depending on your situation, either install and configure or updateRational Team Concert:
  16. Depending on your situation, either install and configure or only configure Rational Team Concert:
  17. Find the rtc_install_dir/jazz/server/jazz_war.ear file and extract it. To extract .ear files, you can use a free utility, such as 7-Zip. From the extracted jazz_war.ear package, copy the jazz.war file to the tomcat_for_rtc_install_directory/webapps/ directory.
  18. Configure a secure port on your Tomcat server for Rational Team Concert:
    1. Create a security certificate that identifies your Tomcat server for Rational Team Concert for SSL connections. You can use the Java JDK keytool command to create a self-signed certificate. Alternatively, you can request a certificate that is signed by a trusted certificate authority.

      For more information about creating self-signed certificates with the keytool command, see the Oracle Java documentation. You can create a self-signed certificate with the following example keytool command:

      keytool -genkey -alias tomcat -keystore tomcat_for_rtc_install_directory/.keystore

      When you run that command, you will be prompted for a password for the keystore file. The default password is changeit, but you should specify a different one. You will have to remember that password to input it into the server.xml file later.

      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 about using the iKeyman tool, see iKeyman User's Guide.

      We also include a simple certificate in the rtc_install_dir/jazz/server/ folder; the certificate file is ibm-team-ssl.keystore

    2. In the tomcat_for_rtc_install_directory\conf\server.xml file, find the <Connector> tag with the attribute scheme="https". The default file includes an example <Connector> tag for port 8443 that is commented out.
    3. Copy and paste the following text:
      <Connector port="8443"
           maxHttpHeaderSize="8192" 
           maxThreads="150"
           minSpareThreads="25" 
           maxSpareThreads="75"
           enableLookups="false"
           disableUploadTimeout="true"
           connectionTimeout="20000"
           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 file name of your keystore file. It can be an absolute path, or relative from the root directory of your Tomcat server (tomcat_for_rtc_install_directory). If you used the simple command above, this will be .keystore. If you use the included certificate, this will be rtc_install_dir/jazz/server/ibm-team-ssl.keystore .
      • keystore_password is the password for the keystore file. If you use the included keystore file, this is ibm-team .
      • keystore_protocol is the protocol for the keystore. Most likely it is TLS or SSL_TLS. If you use the included keystore file, this is SSL_TLS .
      • keystore_algorithm is the X509 algorithm for the keystore. Most likely it is SunX509 or IbmX509, depending on the source of the certificate. If you use the included keystore file, this is IbmX509 .
    4. You can change the port value to use a port besides 8443 for the non-SSL connector (by default, port 8080). If you change the port value, change the value of the redirectPort attribute to match your port number for the SSL connector.

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

  19. For Oracle: For Microsoft SQL Server: Copy the appropriate .jar file from your database provider:
  20. Configure the Tomcat startup property settings:
    1. Find the Tomcat startup file and open it in a text editor. On Windows, this file is tomcat_for_rtc_install_directory\bin\startup.bat. On Linux, AIX, or Linux for zSeries, the file is tomcat_for_rtc_install_directory/bin/startup.sh.
    2. In the startup file, type the following text:
      • For Windows: Replace each space character 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 -Djava.library.path="tomcat_for_rtc_install_directory\shared\lib" -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:
        ORACLE_JDBC=oracle_jar_dir
        SQLSERVER_JDBC=sqlServer_jar_dir
        JAZZ_INSTALL_DIR=rtc_install_dir
        export JAVA_OPTS="-Djava.awt.headless=true -Djava.library.path=tomcat_for_rtc_install_directory/shared/lib -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"

      Where:

      • rtc_install_dir is the extracted directory of the RTC-server.zip file. On Windows, replace each space character in rtc_install_dir with %20
      • For Oracle: oracle_jar_dir is the directory for the ojdbc14.jar file (rtc_install_dir/jazz/server/oracle)
      • For Microsoft SQL Server: sqlServer_jar_dir is the directory of the sqljdbc.jar file (rtc_install_dir/jazz/server/sqlserver)
      • tomcat_for_rtc_install_directory is the installation directory for the Tomcat server
      • For Windows: For Linux: For AIX: If you are installing Rational Asset Manager and Rational Team Concert on the same application server, use this JAVA_OPTS system variable to replace the one that you created when you configured the startup script for the Tomcat server for Rational Asset Manager; this declaration still includes the -Djava.library.path option.
  21. Find and rename the appropriate 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: teamserver.oracle.properties
      • For SQL Server: teamserver.sqlserver.properties
    3. Rename the file to teamserver.properties.
  22. In a text editor, open the teamserver.properties file and modify it as follows (for your database provider):
  23. Create the tables for Rational Team Concert:
    1. Open a command-line window and navigate to the rtc_install_dir/jazz/server/ directory.
    2. Enter 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
  24. Configure user authorization for the included Rational Team Concert.
  25. Start the Tomcat server for Rational Team Concert. To start Tomcat, run the following file:
  26. Launch the Administrative web interface of Rational Team Concert in a web browser at https://machine_name:secure_port/jazz/admin/. Note the https; the connection must be secure.
  27. Log in with the user ID and password for the administrator of Rational Team Concert. If no one has logged in to Rational Team Concert before, use the user ID and password for the administrator of the application server.
  28. If you are working with a new installation of Rational Team Concert: Configure the administrative user for Rational Team Concert:
    1. If you see an error about "fetching server status information," shut down and restart both your database server and your application server and log in again.
    2. In the Rational Team Concert Administrative web interface, click User Management. Ignore any errors about an external registry not being configured.
    3. Click Create User.
    4. Enter the following details:
      1. User Name: The user ID of the application server administrator
      2. User ID: The user ID of the application server administrator
      3. Email Address: A valid email address for the application server administrator
    5. In the Client Access License section, select Rational Team Concert - Developer to assign the developer license to that user.
    6. Click Save.
    7. Log out, and then log back in to the Administrative web interface as the administrator of the application server.
  29. Import the lifecycles process template into Rational Team Concert:
    1. In the Rational Team Concert Administrative web interface, click Process Template Management. If you cannot see the Process Template Management link, log out and then log back in to the Administrative web interface.
    2. Click Import Template and browse to the com.ibm.ram.lifecycle.zip file in the archive_extract_location/DatabaseScripts/ folder. Then click OK. The RAM Lifecycle template is displayed.
  30. Create a project area in Rational Team Concert:
    1. In the Rational Team Concert Administrative web interface, click Project Area Management. If you cannot see the Project Area Management link, log out and then log back in to the Administrative web interface.
    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.
  31. 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. Search for and select the administrator user that you created. If you are working with an existing Rational Team Concert application, you can also select a different user to be administrator for this project area.
    3. In the Members section, click Add; then search for and select the same user that you selected as the administrator for the project area.
    4. After you add the administrator, click the Process Roles icon next to the administrator's name.
    5. In the Edit Process Roles window, from the Available Roles list, select Administration and click Add.
    6. Click Finish.
    7. Click Save.
  32. If you are upgrading from V7.1.1.1 or earlier: Proceed to step 34.
  33. 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 disk 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 Rational Team Concert files.

    3. Find the Tomcat startup file and open it in a text editor. On Windows, this file is tomcat_for_rtc_install_directory\bin\startup.bat. On Linux, AIX, or Linux for zSeries, the file is tomcat_for_rtc_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 33a:
      • 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 a web browser, enter the following URL: https://host:secure_port/jazz/admin?internal, where host is your IP address or server 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, click Server reset.
    9. Click Request server reset.
    10. Stop, and then restart the Tomcat server. The included Rational Team Concert application is updated.
  34. Stop the Tomcat server for Rational Asset Manager.
  35. Remove the old Rational Asset Manager .war web application files that are installed on Tomcat:
    1. Navigate to the tomcat_install_directory/webapps/ directory.
    2. Note the folders and file names for any Rational Asset Manager web applications. In previous versions of Rational Asset Manager, the following names were suggested 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/
    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 names in the list, depending on how you installed the applications on your server.
    4. Delete the associated folders for those applications.
  36. From the archive_extract_location/apps/tomcat/ directory, copy the following files to the tomcat_install_directory/webapps/ directory:
  37. To change the context path of the applications, rename the WAR application files. Use the same context paths that you had before. The file names and context paths for new installations are as follows:
    Table 1. Context paths for Rational Asset Manager web application files
    Original file name New 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
  38. Clear the cache for the Tomcat server. Delete the tomcat_install_directory/work/ directory.
  39. Restart the Tomcat server for Rational Asset Manager.
  40. 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.
  41. After you migrate the repository, stop and then restart your application server.
  42. If you are upgrading from V7.1.1.1 or earlier: Configure the settings to connect to Rational Team Concert from Rational Asset Manager:
    1. In the Rational Asset Manager web client, click Administration.
    2. Click Configuration.
    3. In the Internal Rational Team Concert path section, type the following information:
      1. Path: The secure URL to the Rational Team Concert server that you have configured. For example, https://localhost:9443/jazz. Note the https connection, and the secure port number.
      2. User: The user name for the user in Rational Team Concert that is the administrator for the "RAM Lifecycles" project area.
      3. Password: The password for the user that is the administrator for the "RAM Lifecycles" project area.
      4. Timeout: The amount of time, in seconds, to allow Rational Asset Manager to connect to Rational Team Concert. The default is 120.
  43. 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.
  44. 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 several aspects of the installation, including which configuration to use.

Installation scenarios

You can install the product in four basic scenarios:

In each scenario, you can install the product either by using IBM Installation Manager or by manually installing the deployment .zip files. If you are using Installation Manager, you can use the GUI or run a silent installation from a command line.

Starting in version 7.2, IBM Rational Team Concert is a required component that you must install. Rational Team Concert requires at least an additional 250 MB of disk space for the server files, and its database needs at least 5 GB of free space. You cannot install Rational Asset Manager onto an existing Rational Team Concert server. You cannot update Rational Team Concert in the Rational Asset Manager 7.2 server. In a WebSphere network deployment environment, Rational Team Concert cannot be deployed onto clusters; that component must be deployed to a single 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 Eclipse client can communicate with a Rational Asset Manager server that uses the same version or the version that is one level earlier, including fix packs of each version. If possible, use the same version of both the Rational Asset Manager server and the Eclipse client. For more information, see Eclipse client communicates with servers that use either the same version or one-level earlier version.

Licensing model for 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.

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 the product through the web client, Eclipse client, and published Rational Asset Manager application programming interfaces.

The following licenses are available:

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 collaborator license.

Only administrators can assign licenses to users; licenses are not automatically assigned. Administrators can assign authorized user licenses from the web client. Floating licenses are used for a user who does not have the appropriate authorized license. Programmatic access also requires a Rational Asset Manager license based on the user ID. One user license cannot be used across multiple repositories concurrently but can be used across multiple client programs in the same repository.

Note: 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 be used only on Rational Asset Manager servers that are configured to be Standard Edition servers. Similarly, Rational Asset Manager Enterprise Edition licenses can be used only on servers that are configured to be Enterprise Edition servers.

When a user accesses the system, the user is licensed as one of the following user types:

The system checks whether a user is authorized, and either allocates the authorized user license or provides a floating license based on the user operation. License allocation follows these processes:

Examples of license allocation:

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 does 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 time out.

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 they log out or until all of the sessions expire.

If that user had an assigned collaborator license, the license would not be released because that license is assigned. Only floating licenses can be promoted. If you are assigned a collaborator license and try to complete an action that requires a publisher license, the license server will allocate a publisher floating license if one is available.

When you plan for the number of each license type for your deployment, follow these guidelines:

Disk considerations for optimizing performance

Plan to separate the database, repository index, temporary folders, and assets directory on separate hard disk drives. This separation 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, such as asset browsing.

Database

Rational Asset Manager requires a database for storing assets and associated data. 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 that server. You can use either server with any database or other platform software. However, if you integrate with other products, do not use the version of WebSphere Application Server that is embedded in 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 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 the product 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

Note: To create and use a cluster of application servers, you must have IBM WebSphere Application Server Network Deployment (ND), which is not bundled with IBM Rational Asset Manager.

When you deploy the product to a cluster environment, the components must use the same operating system and application server. If you plan to integrate with Rational ClearCase and Rational ClearQuest, the 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 tens or hundreds of thousands of assets, 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 a Redundant Array of Independent Disks (RAID) and 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 deciding 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:

Planning for hardware

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.

Application server requirements

The embedded WebSphere Application Server is a lightweight server. It supports environments that run a limited number of applications and that do not require the full administration support provided by WebSphere Application Server; you do not have complete access to the WebSphere administrative console and accordingly will not be able to fully manage application, security, and performance settings.

You can also install Rational Asset Manager on a single server that runs WebSphere Application Server and a database, and use local disks for assets and indexing; however, that configuration cannot scale well beyond 200 concurrent users.

You can install and maintain Rational Asset Manager on a single server; however, to improve performance, at a minimum, use an external database server and file server.

For the greatest flexibility in environments with many users, install Rational Asset Manager on WebSphere Application Server Network Deployment cluster environment, which will allow you to distribute the load across multiple servers and across multiple disks in a variety of ways.

Note: To create and use a cluster of application servers, you must have IBM WebSphere Application Server Network Deployment (ND), which is not bundled with IBM Rational Asset Manager.

Example deployments

The following two figures show deployment examples.

This figure shows a simple deployment that supports up to 200 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 to 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 Team Concert is a required integration

Rational Asset Manager requires Rational Team Concert. The Rational Team Concert application manages the lifecycle processes for assets in Rational Asset Manager. We include a limited version of Rational Team Concert that you can install and use, or you can extend an existing Rational Team Concert server application to work with Rational Asset Manager.

The Rational Team Concert server application cannot be deployed as part of a WebSphere Application Server cluster. However, you can create a stand-alone application server. See Creating an application server instance for Rational Team Concert on a WebSphere Application Server distributed server cluster.

Storage requirements

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.

Your needs for storage space for assets will depend on the types of artifacts (files) you will be storing on the repository; text documents and spreadsheets are relatively small, while bootable operating system images are very large.

As one example for planning how much storage space you might need, the repository for a 3-year-old enterprise deployment with 70,000 assets requires 10 GB of space for the database, and 250 GB of space for files.

Database requirements for storing metadata, metrics, and lifecycle processes

Rational Asset Manager requires two databases: one for asset and data storage and another for managing lifecycle processes (which is used by the included Rational Team Concert application). For best performance, place the database server application on a separate server and on a dedicated disk.

The size of the database for Rational Asset Manager 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 with increased repository usage.

The size of the database for Rational Team Concert depends on the amount of custom lifecycles that you add, and whether or not others are using Rational Team Concert as a project management and development tool.

File system requirements for storing asset files

In addition to the space required for the application files and the databases, you will need several folders for storing assets:

User registry considerations

To make it easier to manage users in most large deployments, you will probably want to use your existing LDAP or other custom user registry. Both WebSphere Application Server and Tomcat application servers support using an LDAP registry to manage access to the server.

Although Rational Asset Manager supports adding users from an external registry (such as LDAP or a custom registry), you do not need to use an external registry. You can use a file-based security system, or if you are using WebSphere Application Server you can use the user accounts database for your operating system.

Hardware configurations to improve performance

Place the database, repository index, temporary folders, and assets directory on separate hard disk drives. Using multiple drives prevents certain operations, such as asset retrieval and indexing, from interfering with performance, such as browsing assets.

By adjusting hardware, you can improve performance:

Configurations to improve user actions

When you plan for the initial platform size and for production environment upgrades, consider the relative system resources that are used by different types of operations. For example, operations through the Eclipse client consume more system operations than operations for the web client.

User actions (for example, searching for, downloading, viewing, or submitting assets) require much more processing and memory resources than are needed for asset storage. As more concurrent users are added, you need more and faster servers.

For more specifics on tuning your system for performance, see Tuning the performance of Rational Asset Manager.

Considerations for uploading and downloading large files

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

Considerations for help and assistance

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

In this example, your product must support 200 concurrent users and 10,000 assets.

Every asset contains one artifact; the artifacts vary in size:

Your users are doing the following activities:

For this configuration of assets and user activity, you need at least the following equipment:

In general, to support more concurrent users you will need to add more nodes and servers (which will require WebSphere Application Server Network Deployment edition), increase the memory, or use faster hard disks.

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.

Note: To create and use a cluster of application servers, you must have IBM WebSphere Application Server Network Deployment (ND), which is not bundled with IBM Rational Asset Manager.

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.

For detailed instructions on backing up and restoring your applications, see Backing up and restoring.

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:

Procedure

  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 you install the product, verify that your system meets the software requirements.

To view the requirements, from the system requirements list, select the current version of the product.

What's included with Rational Asset Manager

The installation media includes the following applications:

Application server requirements

You must have a supported application server. You will deploy the web applications for Rational Asset Manager onto an application server.

If you do not have an application server, the installation media includes a limited, embedded version of IBM WebSphere Application Server that you can install along with the Rational Asset Manager sever applications. If you have one of the supported application servers, you can install the Rational Asset Manager server applications onto it.

For WebSphere Application Server, a single application server and clustered deployments are supported.

Note: To create and use a cluster of application servers, you must have IBM WebSphere Application Server Network Deployment (ND), which is not bundled with IBM Rational Asset Manager.

Database application requirements

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

License server requirements

To distribute licenses, you must use install and use Rational License Server. You will install your licenses onto Rational License Server. After you deploy Rational Asset Manager, you must configure the Rational Asset Manager web application to communicate with Rational License Server.

Rational Team Concert is a required integration

Rational Asset Manager requires Rational Team Concert. The Rational Team Concert application manages the lifecycle processes for assets in Rational Asset Manager. We include a limited version of Rational Team Concert that you can install and use, or you can extend an existing Rational Team Concert server application to work with Rational Asset Manager.

The Rational Team Concert server application cannot be deployed as part of a WebSphere Application Server cluster. However, you can create a stand-alone application server. See Creating an application server instance for Rational Team Concert on a WebSphere Application Server distributed server cluster.

Web browser requirements

A supported web browser is required to view the Rational Asset Manager web client and 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:

Procedure

  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.

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.

Procedure

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

Procedure

  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 Manager at 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/v1r4/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/v1r4/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:

Procedure

  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:

Procedure

  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:

Procedure

  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:

Procedure

  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:

Procedure

  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:

Procedure

  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:

Procedure

  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:

Procedure

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:

Procedure

  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.7

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.7 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/v9r7/index.jsp.

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

Procedure

  1. Start the DB2 Setup Launchpad program. From the Rational Asset Manager launchpad program, click Install IBM DB2 Enterprise Server Edition, Version 9.7. 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.7 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:

Procedure

  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 Key Server

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

Procedure

  1. Install Rational License Key Server.

    For Windows, AIX, or Linux: If you use Rational License Server version 7.01 or earlier, upgrade to the Rational License Key Server v8.1.1 or later.

    For Linux for zSeries: You must install Rational License Key Server v8.1.1 or later on a supported platform.

    Rational License Key Server is included with the Rational Asset Manager installation media. You can also retrieve the latest version of Rational License Server through your Passport Advantage account, or through the Rational Download Center.

    For information about installing and configuring the license server, see the following topics in the License Management Guide:

    For an overview of Rational License Server, see the delivery and support web page for that server: http://www.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.

    If you are using redundant license servers, you must install your licenses on every server.

    If you are using multiple license servers that are distributed on different networks, you must have separate licenses on every license server.

    To upgrade, you must file a request for updated license keys.

    For more information about 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/.

    For information about updating your license files for Rational Common Licensing Server v8.1.1, see License Migration Utility or Returning or moving license keys.

  3. Start the Rational License Server. For more information, see the IBM Rational License Management Guide or the License Key Administrator Help.
  4. After you deploy the Rational Asset Manager applications to your application server, configure that server to communicate with Rational License Server.

    You can manually configure the servers to communicate or use the Rational Asset Manager server setup application to configure the servers. For instructions to use the server setup application, see Deploying and configuring application files by using the server setup application. For instructions to manually configure the servers, 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.

Procedure

  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 server or cluster, make sure the 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.

Note: To create and use a cluster of application servers, you must have IBM WebSphere Application Server Network Deployment (ND), which is not bundled with IBM Rational Asset Manager.

Procedure

  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.5.0.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\RAM75Server
      • For Linux: For AIX: For Linux for zSeries:/opt/IBM/RAM75Server
    3. To continue, click Next.
  12. On the Features page, click Next. You cannot clear any features on this page.
  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 2. 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 the Rational 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, type the location of the profile for the deployment manager.) 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 server), enter that port number in place of 9080. For a cluster, type the URL and port number for any application server that is part of the cluster.
    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. Click Get list from server.
      • For single server node installations, the name of the server is displayed in the text field (for example, server1).
      • For clusters, the name of the cluster is displayed.
    6. Click Next.
    7. On the Context Root page, in the Rational Asset Manager Setup Server field, type a context root for the Rational 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).

If you needed an application server, the embedded WebSphere Application Server is installed and started, and the server setup application has been deployed to the application server. If you installed to an existing WebSphere Application Server, the server setup application has been deployed to the application server. If you installed to a WebSphere Application Server cluster, the server setup application has been deployed to the cluster.

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 Installing silently with Installation Manager on the information center for Installation Manager

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:

The complete list of files is in Table 1, below.

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

Procedure

  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 or files 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 3. 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 the Deployment Manager server on an 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.
Both extracted_.zip_location\sharedLibs rlsclients_rlsibmratl_811_4.zip Files for the Rational Licensing Server. This .zip contains the appropriate files for all supported operating systems

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

The Rational Asset Manager server application requires a database for assets and other repository information.

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.

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.7 for Linux, AIX, or Linux for zSeries.

You will use the following scripts:

Procedure

  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.7 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:

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.7 for Linux and /opt/IBM/db2/V9.7 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:

Procedure

  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:

Creating and populating the database for assets in Oracle

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

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:

Procedure

  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 must be named RAMSCHEMA. Rational Asset Manager requires a schema named RAMSCHEMA, and in Oracle schemas are owned by a database user and share the name of that user. You cannot use a different name.
      • 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; however, you still must name the user RAMSCHEMA.
  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

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:

Procedure

  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; the Rational Asset Manager database must use a case-sensitive collation to work correctly. 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 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

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.

If you are using an existing Rational Team Concert server, you can skip this task because Rational Team Concert will already have a database.

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.

If you are using an existing Rational Team Concert server, you can skip this task because Rational Team Concert will already have a database.

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

The user performing these instructions must have system administrator authority on the DB2 database.

Tip: On Linux, AIX, or Linux for zSeries, to get system admin authority on the DB2 database, sudo to the DB2 user db2inst1 and run bash. Note that db2inst1 is the default instance user.

About this task

To set up the DB2 database:

Procedure

  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.

Note: To create and use a cluster of application servers, you must have IBM WebSphere Application Server Network Deployment (ND), which is not bundled with IBM Rational Asset Manager.

If you are installing to a WebSphere Application Server cluster and you need to install Rational Team Concert, 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. See Deploying the Rational Asset Manager server applications on Tomcat 5.5.

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

If you are using an existing Rational Team Concert server, you can skip this task because Rational Team Concert will already have a database.

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:

Procedure

  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:
      • You can use any valid username. Unlike the database for assets, a specific username is not required.
      • 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.

Note: To create and use a cluster of application servers, you must have IBM WebSphere Application Server Network Deployment (ND), which is not bundled with IBM Rational Asset Manager.

If you are installing to a WebSphere Application Server cluster and you need to install Rational Team Concert, 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. See Deploying the Rational Asset Manager server applications on Tomcat 5.5.
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

If you are using an existing Rational Team Concert server, you can skip this task because Rational Team Concert will already have a database.

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:

Procedure

  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 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.

Note: To create and use a cluster of application servers, you must have IBM WebSphere Application Server Network Deployment (ND), which is not bundled with IBM Rational Asset Manager.

If you are installing to a WebSphere Application Server cluster and you need to install Rational Team Concert, 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. See Deploying the Rational Asset Manager server applications on Tomcat 5.5.

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

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

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.

Procedure

  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 -> Application types.
  4. Click WebSphere 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 9, 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 -> Application types.
    2. Click WebSphere 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 -> Server types.
    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. Configure the application security and authentication settings:
    1. Click Security.
    2. Click Global security.
    3. In the Administrative Security section, if the Enable administrative security checkbox is selected, select the Enable application security checkbox.
    4. In the Authentication section, click Web and SIP security.
    5. Click General settings.
    6. 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.
    7. Click Apply.
    8. In the Messages window, click Save directly to the master configuration.
  15. Stop, and then restart WebSphere Application Server and Web servers.
  16. 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.)
  17. 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

You can manually deploy the IBM Rational Asset Manager server setup application to a Network Deployment cluster.

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.

Note: To create and use a cluster of application servers, you must have IBM WebSphere Application Server Network Deployment (ND), which is not bundled with IBM Rational Asset Manager.
Note:

In V7.2.0.2 or earlier, you were required to deploy the server setup application directly to the Deployment Manager server. In V7.5 or later, you should deploy the server setup application to your cluster as described in the procedure below. If you want to deploy the server setup application directly to the Deployment Manager, see Deploying the server setup application to the Deployment Manager on a WebSphere Application Server cluster.

After you have deployed and started the server setup application, you will then use it to deploy and configure the other applications.

Procedure

  1. Log in to the WebSphere Application Server administrative console.
  2. Click Applications -> New Application.
  3. Click New Enterprise Application.
  4. Select Local file system, then click Browse and select the server setup application (com.ibm.ram.repository.setup.web.ear) file on your file system.
  5. Click Next.
  6. Select Show me all installation options and parameters.
  7. Click Next until you reach Step 2: Map modules to servers section (or click that step directly).
  8. Map the module to your cluster:
    1. Select the com.ibm.ram.repository.setup.web module in the table.
    2. From the Clusters and servers list, select the cluster where you want to deploy the server setup application. (Later, you will use the server setup application to deploy all the other applications to this cluster.)
    3. Click Apply.
  9. Click Next until you reach Step 7: Map context roots for Web modules (or click that step directly).
  10. Note the Context Root value. You can change it, or accept the default of ram.setup.
  11. Click Next until you get to Step 9: Summary.
  12. Click Finish.
  13. After the application installs, click Save directly to the master configuration. While saving the configuration, synchronize the configuration with the nodes where you intend to use to run the application. To synchronize a node manually, on the System Administration -> Node Agents page, verify that the node is running; then, on the System Administration -> Nodes page, select the node and click Synchronize.
  14. Click Applications -> Application Types -> WebSphere enterprise applications.
  15. Select com.ibm.ram.repository.setup.web.ear and click Start.
  16. 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 -> Server types.
    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.
  17. Configure the application security and authentication settings:
    1. Click Security.
    2. Click Global security.
    3. In the Administrative Security section, if the Enable administrative security checkbox is selected, select the Enable application security checkbox.
    4. In the Authentication section, click Web and SIP security.
    5. Click General settings.
    6. 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.
    7. Click Apply.
    8. In the Messages window, click Save directly to the master configuration.
  18. Stop, and then restart WebSphere Application Server and Web servers.
  19. 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.)
  20. 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.
Deploying the server setup application to the Deployment Manager on a WebSphere Application Server cluster

You can manually deploy the server setup application onto the Deployment Manager by running a Jython script to place the server setup application on the Deployment Manager server for the cluster.

Before you begin

Note: To create and use a cluster of application servers, you must have IBM WebSphere Application Server Network Deployment (ND), which is not bundled with IBM Rational Asset Manager.

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 be able to deploy applications on to the Deployment Manager server for the cluster.

After you have deployed and started the server setup application, you will then use it to deploy and configure the other applications.

About this task

Prior to V7.5, you had to install the server setup application directly onto the Deployment Manager for a cluster; in V7.5 or later, we recommend installing the server setup application to the application servers in the cluster.

Procedure

  1. Locate the following scripts in the Rational_Asset_Manager_install_directory\ram\conf\bin folder:
  2. To deploy the Rational Asset Manager server setup enterprise archive to the Deployment Manager server, 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 context_root

    On AIX, Linux, or Linux for zSeries 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 context_root

    where:

    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.
  3. Launch the WebSphere Application Server Administrative Console and login as an administrator.
  4. Start the application:
    1. In the navigation pane, click Applications -> Application types.
    2. Click WebSphere 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.

What to do next

To uninstall the server setup application from the Deployment Manager server, run the following command (Windows):

wsadmin.bat -conntype NONE -lang jython -f install_dir\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 install_dir/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 distributed 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 an IBM WebSphere Application Server cluster, you can create a single application server instance on your cell for Rational Team Concert.

Before you begin

Note: To create and use a cluster of application servers, you must have IBM WebSphere Application Server Network Deployment (ND), which is not bundled with IBM Rational Asset Manager.

If you already have Rational Team Concert installed and configured, skip this task.

You must be an WebSphere administrator to create a new server instance on a cell.

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 in your cell.

Procedure

  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 -> Server types.
  3. Click WebSphere 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 different from the names of any other application servers on 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.

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 the Rational Asset Manager server applications on Tomcat 5.5

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

Before you begin

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

Before you do this task, complete the following tasks:

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

You must know the location of the following JDBC .jar files for your database server:

About this task

You can improve the performance and stability of Rational Asset Manager by installing its web applications and the application files for the included IBM Rational Team Concert on separate Tomcat servers. Throughout this document, the installation directory for the Tomcat server for Rational Asset Manager is referred to as tomcat_install_directory. The installation directory for the Tomcat server for Rational Team Concert is tomcat_for_rtc_install_directory. If you are installing all the web applications on the same Tomcat server, the directories are the same.

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 unsecured ports to avoid collisions. For more information about ports in Tomcat 5.5, see the Apache Tomcat documentation.

Procedure

  1. Verify that all of the repository servers are set to the same current date, time, and time zone.
  2. Retrieve the application files on the appropriate archive for Tomcat and for your operating system. The application files are 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.
    3. If you are installing Rational Team Concert on a different Tomcat server, copy the extracted contents of the sharedLib.zip file to the tomcat_for_rtc_install_directory\shared\lib directory for the other Tomcat server.
  4. For Windows: For Linux: For AIX: Extract the library files for Rational Licensing Key Server V8.1.1 to the tomcat_install_directory\shared\lib folder:
    Important: If you are installing on Linux for zSeries, do not complete this step
    1. Find and extract the archive_extract_location\sharedLibs\rlsclients_rlsibmratl_811_4.zip file.
    2. From the extracted .zip file, find the file rlsibmratl811_4.zip for your operating system and architecture. For example, the file for 32-bit Windows is in the win32 directory.
    3. Extract the contents of the appropriate rlsibmratl811_4.zip file.
    4. Copy the entire contents of the extracted rlsibmratl811_4.zip file to the tomcat_install_directory\shared\lib directory.
  5. For Windows: For Linux: For AIX: Modify the startup script for the Tomcat server for Rational Asset Manager:
    Important: If you are installing on Linux for zSeries, do not complete this step
    1. Find the Tomcat startup file and open it in a text editor. On Windows, this file 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:
      • For Windows:
        set JAVA_OPTS=-Djava.library.path="tomcat_install_directory\shared\lib"
      • For Linux: For AIX:
        export JAVA_OPTS="-Djava.library.path=tomcat_install_directory/shared/lib"
  6. From the archive_extract_location/apps/tomcat/ directory, copy the following files to the tomcat_install_directory/webapps/ directory:
  7. To change the context path of the applications, rename the WAR application files. Use the following names.
    Table 4. Context paths for Rational Asset Manager web application files
    Original file name New 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
  8. Configure the Tomcat server for Rational Asset Manager to access your database:
    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>, 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 full administrative access to the database. For example, the "url" attribute might look like jdbc:db2://localhost:50000/RAMDB
    Enter this text for your database server, replacing the following variables:
  9. Configure the Tomcat server for single sign-on for all applications:
    1. In a text editor, open the tomcat_install_directory\conf\server.xml file.
    2. Search for the following text:
      <!--
      <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
      -->
    3. Uncomment the <Valve> element:
      <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
  10. Copy the following JAR files to the tomcat_install_directory\common\lib folder: These files are available from your database provider, most likely in the /java/ folder of your database installation.
  11. Configure the Tomcat server for user security. If you intend to use LDAP security, first use file-based security to configure the applications, and after you configure the applications, switch to LDAP authentication. For more information, see Configuring LDAP authentication for Tomcat.
    1. In a text editor, open the tomcat_install_directory\conf\tomcat-users.xml file.
    2. Add a user named admin and assign that user the admin and manager roles. To add this user, you can copy and paste the following text between the <tomcat-users> tags:
      <user username="admin" password="" roles="admin,manager" />

      This user must be named admin.

  12. Depending on your setup, either deploy or configure Rational Team Concert.

Deploying the included Rational Team Concert server application on Tomcat

IBM Rational Asset Manager requires IBM Rational Team Concert, which controls the lifecycle functions that you can use to manage the development of assets. If you do not already have Rational Team Concert, a limited version of that product is included, which you can deploy to a Tomcat server.

Before you begin

If you already deployed and configured a Rational Team Concert server application, you can use your existing application instead of installing a new application. To configure Rational Team Concert to work with Rational Asset Manager, see Configuring a Rational Team Concert server to work with Rational Asset Manager.

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

Before you do this task, complete the following tasks:

  1. Retrieving the application files
  2. 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.

About this task

You can improve the performance and stability of Rational Asset Manager by installing its web applications and the application files for the included IBM Rational Team Concert on separate Tomcat servers. Throughout this document, the installation directory for the Tomcat server for Rational Asset Manager is referred to as tomcat_install_directory. The installation directory for the Tomcat server for Rational Team Concert is tomcat_for_rtc_install_directory. If you are installing all the web applications on the same Tomcat server, the directories are the same.

Procedure

  1. Verify that all of the repository servers are set to the same current date, time, and time zone.
  2. Retrieve the application files on the appropriate archive for Tomcat and for your operating system. The application files are in the archive_extract_location/apps/tomcat/ folder.
  3. For Windows: For Linux: For AIX: Extract the library files for Rational Licensing Key Server V8.1.1 to the tomcat_for_rtc_install_directory\shared\lib folder:
    Important: Do not complete this step on Linux for zSeries
    1. Find and extract the archive_extract_location\sharedLibs\rlsclients_rlsibmratl_811_4.zip file.
    2. From the extracted .zip file, find the file rlsibmratl811_4.zip for your operating system and architecture. For example, the file for 32-bit Windows is in the win32 directory.
    3. Extract the contents of the appropriate rlsibmratl811_4.zip file.
    4. Copy the extracted contents of the rlsibmratl811_4.zip file to the tomcat_for_rtc_install_directory\shared\lib directory.
    If you are installing Rational Asset Manager and Rational Team Concert on the same application server, you already completed this step.
  4. On the installation media, find the archive_extract_location/apps/tomcat/RTC-server.zip file.
  5. Extract RTC-server.zip to a location on your hard disk 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. To extract .ear files, you can use a free utility, such as 7-Zip. From the extracted jazz_war.ear package, copy the jazz.war file to the tomcat_for_rtc_install_directory/webapps/ directory.
  7. Configure a secure port on your Tomcat server for Rational Team Concert:
    1. Create a security certificate that identifies your Tomcat server for Rational Team Concert for SSL connections. You can use the Java JDK keytool command to create a self-signed certificate. Alternatively, you can request a certificate that is signed by a trusted certificate authority.

      For more information about creating self-signed certificates with the keytool command, see the Oracle Java documentation. You can create a self-signed certificate with the following example keytool command:

      keytool -genkey -alias tomcat -keystore tomcat_for_rtc_install_directory/.keystore

      When you run that command, you will be prompted for a password for the keystore file. The default password is changeit, but you should specify a different one. You will have to remember that password to input it into the server.xml file later.

      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 about using the iKeyman tool, see iKeyman User's Guide.

      We also include a simple certificate in the rtc_install_dir/jazz/server/ folder; the certificate file is ibm-team-ssl.keystore

    2. In the tomcat_for_rtc_install_directory\conf\server.xml file, find the <Connector> tag with the attribute scheme="https". The default file includes an example <Connector> tag for port 8443 that is commented out.
    3. Copy and paste the following text:
      <Connector port="8443"
           maxHttpHeaderSize="8192" 
           maxThreads="150"
           minSpareThreads="25" 
           maxSpareThreads="75"
           enableLookups="false"
           disableUploadTimeout="true"
           connectionTimeout="20000"
           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 file name of your keystore file. It can be an absolute path, or relative from the root directory of your Tomcat server (tomcat_for_rtc_install_directory). If you used the simple command above, this will be .keystore. If you use the included certificate, this will be rtc_install_dir/jazz/server/ibm-team-ssl.keystore .
      • keystore_password is the password for the keystore file. If you use the included keystore file, this is ibm-team .
      • keystore_protocol is the protocol for the keystore. Most likely it is TLS or SSL_TLS. If you use the included keystore file, this is SSL_TLS .
      • keystore_algorithm is the X509 algorithm for the keystore. Most likely it is SunX509 or IbmX509, depending on the source of the certificate. If you use the included keystore file, this is IbmX509 .
    4. You can change the port value to use a port besides 8443 for the non-SSL connector (by default, port 8080). If you change the port value, change the value of the redirectPort attribute to match your port number for the SSL connector.

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

  8. For Oracle: For Microsoft SQL Server: Copy the appropriate .jar file from your database provider:
  9. Configure the Tomcat startup property settings:
    1. Find the Tomcat startup file and open it in a text editor. On Windows, this file is tomcat_for_rtc_install_directory\bin\startup.bat. On Linux, AIX, or Linux for zSeries, the file is tomcat_for_rtc_install_directory/bin/startup.sh.
    2. In the startup file, type the following text:
      • For Windows: Replace each space character 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 -Djava.library.path="tomcat_for_rtc_install_directory\shared\lib" -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:
        ORACLE_JDBC=oracle_jar_dir
        SQLSERVER_JDBC=sqlServer_jar_dir
        JAZZ_INSTALL_DIR=rtc_install_dir
        export JAVA_OPTS="-Djava.awt.headless=true -Djava.library.path=tomcat_for_rtc_install_directory/shared/lib -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"

      Where:

      • rtc_install_dir is the extracted directory of the RTC-server.zip file. On Windows, replace each space character in rtc_install_dir with %20
      • For Oracle: oracle_jar_dir is the directory for the ojdbc14.jar file (rtc_install_dir/jazz/server/oracle)
      • For Microsoft SQL Server: sqlServer_jar_dir is the directory of the sqljdbc.jar file (rtc_install_dir/jazz/server/sqlserver)
      • tomcat_for_rtc_install_directory is the installation directory for the Tomcat server
      • For Windows: For Linux: For AIX: If you are installing Rational Asset Manager and Rational Team Concert on the same application server, use this JAVA_OPTS system variable to replace the one that you created when you configured the startup script for the Tomcat server for Rational Asset Manager; this declaration still includes the -Djava.library.path option.
  10. Find and rename the appropriate 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: teamserver.oracle.properties
      • For SQL Server: teamserver.sqlserver.properties
    3. Rename the file to teamserver.properties.
  11. In a text editor, open the teamserver.properties file and modify it as follows (for your database provider):
  12. Create the tables for Rational Team Concert:
    1. Open a command-line window and navigate to the rtc_install_dir/jazz/server/ directory.
    2. Enter 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
  13. Configure the Tomcat server for user security. If you intend to use LDAP security, first use file-based security to configure the applications, and after you configure the applications, switch to LDAP authentication. For more information, see Configuring LDAP authentication for Tomcat.
    1. In a text editor, open the tomcat_for_rtc_install_directory\conf\tomcat-users.xml file. Again, if you are installing the applications onto the same Tomcat server, this file is the same file where you modified the user security settings for the Rational Asset Manager applications.
    2. Between the <tomcat-users> tags, paste the following text:
      <role rolename="JazzUsers"/>
      <role rolename="JazzAdmins"/>
      <role rolename="JazzDWAdmins"/>
      <role rolename="JazzGuests"/>
    3. Add a user named admin and assign that user the admin, manager, and JazzAdmins roles. To add this user, you can copy and paste the following text between the <tomcat-users> tags:
      <user username="admin" password="" roles="admin,manager,JazzAdmins" />

      If you are installing the applications on the same Tomcat server, add the JazzAdmins role to the user that you created when you modified the user security settings for the Rational Asset Manager applications.

  14. Start the Tomcat server for Rational Team Concert. To start Tomcat, run the following file:
  15. Configure Rational Team Concert to work with Rational Asset Manager. You must configure administrative rights and create a project area in Rational Team Concert.

Configuring a Rational Team Concert server to work with Rational Asset Manager

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

Before you begin

To configure a Rational Team Concert server application to work with Rational Asset Manager, 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 procedure for you.

The Tomcat server for Rational Team Concert must be running.

Procedure

  1. Retrieve the application files on the appropriate archive for Tomcat and for your operating system. The application files are in the archive_extract_location/apps/tomcat/ folder.
  2. On the installation media, find the archive_extract_location/apps/tomcat/RTC-server.zip file.
  3. Extract RTC-server.zip to a location on your hard disk drive, which is referred to in these instructions as rtc_install_dir.
  4. Launch the Administrative web interface of Rational Team Concert in a web browser at https://machine_name:secure_port/jazz/admin/. Note the https; the connection must be secure.
  5. Log in with the user ID and password for the administrator of Rational Team Concert. If no one has logged in to Rational Team Concert before, use the user ID and password for the administrator of the application server.
  6. If you are working with a new installation of Rational Team Concert: Configure the administrative user for Rational Team Concert:
    1. If you see an error about "fetching server status information," shut down and restart both your database server and your application server and log in again.
    2. In the Rational Team Concert Administrative web interface, click User Management. Ignore any errors about an external registry not being configured.
    3. Click Create User.
    4. Enter the following details:
      1. User Name: The user ID of the application server administrator
      2. User ID: The user ID of the application server administrator
      3. Email Address: A valid email address for the application server administrator
    5. In the Client Access License section, select Rational Team Concert - Developer to assign the developer license to that user.
    6. Click Save.
    7. Log out, and then log back in to the Administrative web interface as the administrator of the application server.
  7. Import the lifecycles process template into Rational Team Concert:
    1. In the Rational Team Concert Administrative web interface, click Process Template Management. If you cannot see the Process Template Management link, log out and then log back in to the Administrative web interface.
    2. Click Import Template and browse to the com.ibm.ram.lifecycle.zip file in the archive_extract_location/DatabaseScripts/ folder. Then click OK. The RAM Lifecycle template is displayed.
  8. Create a project area in Rational Team Concert:
    1. In the Rational Team Concert Administrative web interface, click Project Area Management. If you cannot see the Project Area Management link, log out and then log back in to the Administrative web interface.
    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.
  9. 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. Search for and select the administrator user that you created. If you are working with an existing Rational Team Concert application, you can also select a different user to be administrator for this project area.
    3. In the Members section, click Add; then search for and select the same user that you selected as the administrator for the project area.
    4. After you add the administrator, click the Process Roles icon next to the administrator's name.
    5. In the Edit Process Roles window, from the Available Roles list, select Administration and click Add.
    6. Click Finish.
    7. Click Save.
  10. Stop and then restart the application server. If you are using Rational Asset Manager and Rational Team Concert on separate Tomcat servers, also start the Tomcat server for Rational Asset Manager. To start Tomcat, run the following file:
  11. Open and log in to the Rational Asset Manager web client to 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 for IBM WebSphere Application Server that 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).

Procedure

  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 3072:
    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 3072, increase the limit with the following command: ulimit -n 3072
  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 Global security.
    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 and SIP 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 are upgrading from version 7.1.1.1 or earlier and use a WebSphere Application Server cluster and you need to install Rational Team Concert, 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 distributed 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.

    If you are unable to access the machine that you deployed the server setup application to, you will be able to upload the files later.

  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 Database vendor 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. Rational Asset Manager requires Rational Team Concert. Select if you need to installRational Team Concert from the Rational Team Concert server list:
      • I need to install a new Rational Team Concert server.: Install a new, limited version of Rational Team Concert to your application server. If you are using a WebSphere Application Server cluster, you must create a single application server instance for Rational Team Concert.
      • I have a Rational Team Concert server and would like to use that.: You will configure an existing Rational Team Concert to work with Rational Asset Manager.
    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, click Provide the location of the files on the server and type the directory on the file system on the server that is running the server setup application 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:

    If you deployed the server setup application to an application server that is part of a cluster and you are accessing that application server, to upload the files to the server that is running the server setup application, click Upload the files to the server; then click Browse and select each of the required files.

  9. To verify that all required application files are in the directory, or to upload them to the server, click Verify Location. If you uploaded the application files, the server setup application will save them to a temporary directory. A message will verify if all the required files are present.
  10. If you are using a WebSphere Application Server cluster, you might see a message that says that you do not have enough Java heap memory to deploy the applications. If you see this message, the server setup application has increased the heap memory to the recommended setting. To make this change take affect, click the restart of the server link. Your server might be unavailable for several minutes while it restarts. After you deploy the applications, you can change the heap memory settings for your application servers.
  11. 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.
  12. 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 12b.
      • 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 13
    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. If you are installing a new Rational Team Concert, in the Create a database for Lifecycle Management field, type a name for the lifecycle management database (for example, RTCDB). If you are using an existing Rational Team Concert, you do not need to create a new database.
          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 populating the database for assets.
  13. 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. Your database vendor can provide these files.
      • 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 Rational_Asset_Manager_install_root\ram\ewas\universalDriver\lib on the local computer. When uploaded to the server, they will be placed in WebSphere_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 ("/").
        Note: For Oracle, you can download the appropriate .jar files from Oracle. For Microsoft SQL Server, you can download the appropriate .jar file from Microsoft.
        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. Then, type the User ID and Password for a database administrator.
    6. In the Database name for Lifecycle field, type the name of the Lifecycle management database; for example, RTCDB. Then, type the User ID and Password for a database administrator.
    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.
  14. In Section 2, part 3, 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.
  15. For DB2:In Section 2, Part 4, 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.
  16. 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.
  17. In Section 3, configure users and authentication:
  18. In Section 4, configure settings for Rational Asset Manager:
    1. Type the address for the License server with the format of port_number@host_name; for example, 27000@example.com.

      If you downloaded Rational Asset Manager from jazz.net, the field will be populated with a temporary license key. Do not modify the key while you evaluate the product.

      If you have redundant license servers, separate multiple entries with commas. (You must provide three servers.) For example, 27000@primary.example.com,27000@secondary.example.com,27777@tertiary.example.com.

      If you have multiple license servers (where the servers are on different networks and have different licenses):

      • For Windows: Separate server addresses with semicolons (;), for example, 27000@main.example.com;27000@backup.example.com.
      • For Linux: For AIX: For Linux for zSeries: Separate server addresses with colons (:), for example, 27000@main.example.com:27000@backup.example.com.

      By default, Rational License Key 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 11. 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. On a cluster, each node will have its own index folder.
        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.
  19. 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.
  20. 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.
  21. 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 Configure lifecycle management settings page opens.
  22. In the Configure Lifecycle management settings page, type the path and login information for the Rational Team Concert application:
    1. In Step 1, In the Rational Team Concert server 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 Step 2, in the Jazz Administrator ID field, type the user ID of the administrator for the Rational Team Concert server (the default is admin); then, in the Password field, type the password for that user (by default, this is admin). If you just installed the Rational Team Concert with the server setup application, type the username and password for the application server administrator.
    3. In Step 3, in the Project Area Name field, type a descriptive name for the project area that will be created for lifecycles (for example, Rational Asset Manager lifecycles). Then, in the Project Area Administrator ID field, type the user ID for the user that you want to be the project area administrator. Then, type the Password for that user. If you are using an external Rational Team Concert server, the Project Area administrator will probably be a different user from the Jazz server administrator. If you are installing a new Rational Team Concert, the server setup application will suggest using the Jazz Administrator ID as the Project Area Administrator ID.
    4. Click Configure server. This process might take a few minutes. After the configuration, the Summary page appears.
  23. On the Summary page, click Start using Rational Asset Manager. or click Finish. The web client opens.

What to do next

Next, configure the email settings for Rational Asset Manager. To do so, see Configuring email 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 or servers that host the Rational Asset Manager and Rational Team Concert server applications must be started before you can complete the following steps.

Procedure

  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. In the License and Version section, specify the license server path and select the type of license that this repository will use:
    1. In the License and Version section, in the Location of license server field, type the port number, then the full name of the lìcense server. Separated the number and name with an At sign (@). For example, 27000@license_server_path.

      If you have redundant license servers, separate multiple entries with commas. You must provide three servers. For example, 27000@primary.example.com,27000@secondary.example.com,27777@tertiary.example.com.

      If you have multiple license servers, where the servers are on different networks and have different licenses:

      • Windows: Separate server addresses with semicolons (;). For example, 27000@main.example.com;27000@backup.example.com.
      • Linux, AIX, or Linux for zSeries: Separate server addresses with colons (:). For example, 27000@main.example.com:27000@backup.example.com.
    2. To configure the type of licenses for the repository to use, under License Type, select either Standard edition or Enterprise edition.
  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 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
  8. 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 user that is the administrator for the "RAM Lifecycles" project area on Rational Team Concert. In simple installs, this will probably be the Rational Team Concert and application server administrator.
  9. In the Custom user registry section, 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. If you intend to use a custom user class, select the Use a custom user registry checkbox and type the fully qualified class path in the Class field. Otherwise, leave the default value for the Class field.
    2. In the Administrator ID field, type the login ID of a registry user that will have repository administrator permission for Rational Asset Manager. You must provide a valid repository administrator, or else you will be unable to log on to Rational Asset Manager as a repository administrator to further configure the application.
    3. Click Configure and enter the following information to configure the relationship between Rational Asset Manager and the LDAP registry. If you leave a value empty, it will revert to the default value. If you want a value to be null, enter a space (" ") character.
      Table 5. LDAP registry configuration options
      LDAP configuration field Description
      LDAP Server's URL The URL to the LDAP server; for example, ldap://hostname:389. For secure communication, use ldaps://hostname:636.
      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.
      The password for the user The password for the user above.
      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.
      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 email address). Note that the Login ID property must be the same as the administration user's login ID in step 9b.
      User's Phone Number property The (objectClass) property that represents the telephone number of the user. For example: (objectClass) person's telephonenumber property.
      User's Email property The (objectClass)'s property representing the email address of the user. For example: (objectClass) person's mail property.
      User's display name property The (objectClass) property representing the name for the user to display in the interface. For example: (objectClass) person'scn property.
      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.
      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.
      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.
      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.
      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 attempt to log in causes the server to validate the user with each IP address and thus can cause multiple failures. If you have set a maximum number of attempts to log in, one invalid attempt could lock you out of your LDAP account. To prevent this issue from occurring, follow the steps described here: http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg1PK42672

  10. (Optional) To configure Rational Asset Manager to perform some processing with a remote Java executable, which can improve performance, see Configuring remote processes. Otherwise, select Use Web Server's JRE.
  11. 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.
  12. 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
  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. If this setting is checked, when you submit an asset, preview images will be automatically created for up to 3 artifacts that contain the following extensions: .doc, .ppt, .pdf, .odt, .odp, and .otp.
    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 email notifications, see Configuring email settings.

If you are using Tomcat, you can now configure Tomcat for LDAP authentication. For more information, see Configuring LDAP authentication for Tomcat.

Configuring email settings

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

Procedure

  1. Log on to the IBM Rational Asset Manager Web client as a repository administrator.
  2. Click Administration.
  3. Click Configuration.
  4. Locate the Email 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 email text field, type the e-mail address to be used in the reply-to field of automated outgoing messages.
  7. In the Default return email name text field, type the name to be used in the name field of automated outgoing messages.
  8. Click Save.

Configuring LDAP authentication for Tomcat

You can configure IBM Rational Asset Manager, IBM Rational Team Concert, and Tomcat for LDAP authentication.

Before you begin

For IBM WebSphere Application Server, you can configure LDAP authentication for both WebSphere Application Server and Rational Asset Manager in the server setup application. For more information, see Deploying and configuring application files by using the server setup application.

Before you do the following procedure, you must deploy and configure both Rational Asset Manager and Rational Team Concert by using file-based security:

  1. Deploying the server applications on Apache Tomcat
  2. Configuring the Rational Asset Manager server application

About this task

If you installed Rational Team Concert on a separate Tomcat server, you do not need to configure LDAP authentication for Rational Team Concert; the included Rational Team Concert uses a single user, so file-based security is sufficient.

Follow the instructions in the topics below to configure both Rational Asset Manager and Rational Team Concert on Tomcat to use LDAP authentication.

Procedure

  1. Configure the Tomcat server for Rational Asset Manager to use LDAP.
  2. Configure the Tomcat server for Rational Team Concert to use LDAP

Configuring the Tomcat server for Rational Asset Manager to use LDAP

You must configure both Rational Asset Manager and the Tomcat server to use LDAP authentication.

Procedure

  1. Log in to the Rational Asset Manager Web client as the server administrator and configure Rational Asset Manager to use LDAP authentication. Be sure to specify the user ID for the repository administrator in the Administrator ID field, or else you cannot log in to Rational Asset Manager later. For more information, see step 9 in Configuring the Rational Asset Manager server application.
  2. Log out of Rational Asset Manager.
  3. Shut down the Tomcat server.
  4. Configure the Tomcat server for Rational Asset Manager to use LDAP:
    1. In a text editor, open the tomcat_install_directory/conf/server.xml file.
    2. Find the Realm tag and edit it with the appropriate values for your LDAP server:
      <Realm  className="org.apache.catalina.realm.JNDIRealm" debug="99"    			
           connnectionURL="ldap://example.com:389"
           connectionName="uid=123456,c=us,ou=exampleorganization,o=example.com"
           connectionPassword="password"
           userBase="ou=exampleorganization,o=example.com"
           userSearch="(mail={0})"
           userSubtree="true"
           roleBase="ou=memberlist,ou=groups,o=example.com"
           roleName="cn"
           roleSearch="(mail={0})"
           roleSubtree="true"
      />

      Where:

      Table 6. LDAP Properties needed for Rational Asset Manager and Rational Team Concert
      LDAP Property Definition
      connectionURL The location and port for the LDAP server
      connectionName The distinguished user name that is used to connect to the LDAP repository
      connectionPassword The password for the distinguished user
      userBase When you search for a user, this is where to start the search.
      userSearch The LDAP search filter to use to select the user entry after substituting the user name in {0}.
      userSubtree To enable LDAP searches of the entire subtree, set to this value to true.
      roleBase The base entry for the role search
      roleName An LDAP entry that contains the name of the role
      roleSearch The LDAP filter that is used for searching groups
      roleSubtree To enable LDAP searches of the entire roles subtree, set this value to true.
  5. Restart the Tomcat server.

Results

Now you can log in to Rational Asset Manager as a repository administrator by using the ID that you specified in Rational Asset Manager. Tomcat no longer uses file-based authentication. You can create communities and assign other LDAP users to be administrators.

What to do next

If the included Rational Team Concert is on the same server, or it is on a different server and you want it to use LDAP authentication, you must configure Rational Team Concert to use LDAP.

Configuring Rational Team Concert on Tomcat to use LDAP

You can configure the included IBM Rational Team Concert running on Apache Tomcat to use LDAP.

Before you begin

You must have administrative access to the Tomcat server.

Unlike Rational Asset Manager, Rational Team Concert uses LDAP groups to determine user roles. You must be able to create LDAP groups, or know the names of LDAP groups that you can remap to the appropriate roles for Rational Team Concert.

About this task

Complete the following procedure only if you meet either of these requirements:

Procedure

  1. Shut down the Tomcat server.
  2. Configure the Tomcat server for Rational Team Concert to use LDAP. If Rational Team Concert is on the same server as Rational Asset Manager, you already configured the Tomcat server in step 4 of Configuring the Tomcat server for Rational Asset Manager to use LDAP. If Rational Asset Manager and Rational Team Concert are on different servers, complete the following:
    1. In a text editor, open the tomcat_for_rtc_install_directory/conf/server.xml file.
    2. Find the Realm tag and edit it with the appropriate values for your LDAP server:
      <Realm  className="org.apache.catalina.realm.JNDIRealm" debug="99"    			
           connnectionURL="ldap://example.com:389"
           connectionName="uid=123456,c=us,ou=exampleorganization,o=example.com"
           connectionPassword="password"
           userBase="ou=exampleorganization,o=example.com"
           userSearch="(mail={0})"
           userSubtree="true"
           roleBase="ou=memberlist,ou=groups,o=example.com"
           roleName="cn"
           roleSearch="(mail={0})"
           roleSubtree="true"
      />

      Where:

      Table 7. LDAP Properties needed for Rational Asset Manager and Rational Team Concert
      LDAP Property Definition
      connectionURL The location and port for the LDAP server
      connectionName The distinguished user name that is used to connect to the LDAP repository
      connectionPassword The password for the distinguished user
      userBase When you search for a user, this is where to start the search.
      userSearch The LDAP search filter to use to select the user entry after substituting the user name in {0}.
      userSubtree To enable LDAP searches of the entire subtree, set to this value to true.
      roleBase The base entry for the role search
      roleName An LDAP entry that contains the name of the role
      roleSearch The LDAP filter that is used for searching groups
      roleSubtree To enable LDAP searches of the entire roles subtree, set this value to true.
  3. Configure four LDAP groups for Rational Team Concert.

    Create four groups:

    The user who is the Rational Team Concert server administrator must be in the JazzAdmins group. To add the user to the group, complete either of these steps:

    For more information about creating LDAP groups, see the documentation for your LDAP server.
  4. Restart the Tomcat server.
  5. Remove the developer license from the old administrative user:
    1. Launch the Admin Web UI of Rational Team Concert in a web browser at https://machine_name:secure_port/jazz/admin/. Note the https; the connection must be secure.
    2. Log in with the user ID and password for the new administrative user that is a member of the JazzAdmins LDAP group.
    3. Click User Management.
    4. Click the name of the previous administrative user.
    5. In the Client Access License section, clear the selected Rational Team Concert - Developer license.
    6. Click Save.
  6. Add the new administrative user:
    1. Click Create user.
    2. Enter the following details:
      1. User Name: The user ID (LDAP login) of the new server administrator
      2. User ID: The user ID (LDAP login) of the new Tomcat server administrator
      3. Email Address: A valid email address for the Tomcat server administrator
    3. In the Client Access License section, select Rational Team Concert - Developer to assign the developer license to that user.
    4. Click Save.
    5. Log out, and then log back in to the Admin Web UI as the new administrator of the application server.
  7. Assign the appropriate memberships and process roles for the new administrator:
    1. On the Project Area Management page, click the RAM Lifecycle project area.
    2. In the Administrators section, click Add. Search for and select the administrator user that you created. If you are working with an existing Rational Team Concert application, you can also select a different user to be administrator for this project area.
    3. In the Members section, click Add; then search for and select the same user that you selected as the administrator for the project area.
    4. After you add the administrator, click the Process Roles icon next to the administrator's name.
    5. In the Edit Process Roles window, from the Available Roles list, select Administration and click Add.
    6. Click Finish.
    7. Click Save.
  8. Stop and then restart the Tomcat server.
  9. Change the information about the administrative user for Rational Team Concert in Rational Asset Manager:
    1. In a Web browser, log in to the Rational Asset Manager as a repository administrator.
    2. Click Administration -> Configuration.
    3. In the Internal Rational Team Concert Path section, update the User and Password fields for the new Rational Team Concert administrator.
    4. 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, this is a starting point for driving high user loads on Rational Asset Manager.

Rational Asset Manager tuning

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.

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 8. 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 / Disabled

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 click Administration -> Configuration; then, in the Job Schedules section, locate the Statistics index builder schedule and click Edit.

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; then, in the Job Schedules section, locate the Process subscriptions schedule and click Edit.

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; then, in the Job Schedules section, locate the User / group information update schedule and click Edit.

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; then, in the Job Schedules section, locate the Review process notification schedule and click Edit.

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 Automatically create featured content on asset submission / 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 coversIBM WebSphere Application Server, version 7.0 settings that significantly affect performance. You can also adjust these setting in IBM WebSphere Application Server, version 6.1, but the instructions to set the parameters might be different.

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

Table 9. 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 -> Server types -> WebSphere 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 sessions in memory by 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 -> Server types -> WebSphere 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 -> Server types -> WebSphere 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://www.oracle.com/technetwork/java/gc-tuning-5-138395.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 -> Server types -> WebSphere 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 -> Server types -> WebSphere application servers -> Server name -> 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 10. 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 -> Server types -> WebSphere application servers -> Server name -> Thread pools -> WebContainer.

Minimum size: 15

Maximum size: 30

Table 11. 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 -> Server types -> WebSphere 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 12. 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 13. 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 14. 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 15. 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 16. 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 17. 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 18. 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 19. 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 20. 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

Procedure

  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:

Procedure

  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 content indexing on Linux and AIX

If you are using Apache Tomcat on Linux or AIX, you must set the appropriate exporter permission on the directory that contains the files for Stellent content indexing.

About this task

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

Procedure

  1. Log in as root.
  2. In a command line, change to the directory of the Stellent content indexing files described above.
  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:

Procedure

  1. Log in as root.
  2. In a command line, change to the WebSphere_install_directory/profiles/profile_name/config/cells/cell_name/ram_jdbc directory.
  3. Type the following command: chmod 755 database_jar_file_name.jar (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.

Procedure

  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

Results

For more information about installing and verifying XVFB on AIX, see http://publib.boulder.ibm.com/infocenter/aix/v6r1/index.jsp?topic=/com.ibm.aix.aixwnpgd/doc/aixwnpgd/xvfb.htm.

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

Rational Asset Manager has an Eclipse client which you can use to find and download assets and interact with the repository from Eclipse. You can install the IBM Rational Asset Manager Eclipse features into an existing of Eclipse IDE by using the Eclipse update manager and downloading the features from the Rational Asset Manager server, a method that insures that 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.4. The process for installing new software is slightly different in each version of Eclipse and in different applications that are built on Eclipse. For example, in Eclipse 3.5 the update manager is located in Help -> Install New Software. In general, the wizard to install new software is usually under the Help menu.

Procedure

  1. Start Eclipse.
  2. Click Help -> Software Updates.
  3. In the Software Updates and Add-Ons window, click the Available software tab.
  4. Click Add site.
  5. Provide the Update site details:
    1. Open the Rational Asset Manager Web client and click Help -> Extensions.
    2. On the Extensions page, in the Eclipse Client Plug-in section, copy the URL listed next to Update site.

      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.

    3. In Eclipse, in the Add Site window, paste the Update Site URL into the Location field.
    4. Click OK
  6. Expand the Rational Asset Manager update site that you just added and select the features to install. Typically, select all of the features, with the following exceptions:
  7. After you have selected the features to install, click Install.
  8. In the Install window, review and accept all of the license agreements and click Next.
  9. Click Finish.
  10. 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 install procedure again, starting at step 2.
  11. 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.

Procedure

  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.

Procedure

  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.

Backing up and restoring

You should plan to frequently back up your repository. With backups of certain parts of your server configuration, file storage, and databases, you can completely recover your repository.

About this task

See the topics below for information on backing up and restoring your IBM Rational Asset Manager repository.

Creating a backup of a Rational Asset Manager repository

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

Before you begin

To back up your repository, you must have these permissions:

To prevent others from modifying the repository while you create a backup, you must be able to stop all application servers.

About this task

You do not need to back up every application file. You can completely recover your repository with the appropriate configuration files, your databases, and the Persist storage folder, which holds all asset artifacts.

Procedure

To create a backup of your repository:

  1. Create a backup of your installation directory with the application files and documentation from the installation media. If you used IBM Installation Manager, this directory is the install_package_location/ram/ folder. You do not need these files for most backups; however, if the backup and restore do not go as planned and you need to completely re-install and configure the applications, you need the files.
  2. Log in to the Rational Asset Manager web client as an administrator.
  3. Click Administration -> Configuration.
  4. In the Disk Storage section, note the location of the Persist and Index folders. If you are on an IBM WebSphere Application Server cluster, there is an Index folder for every node.
  5. Stop the Rational Asset Manager application. Stopping the application helps prevent data corruption. The Rational Asset Manager application is now offline.
  6. Stop the application servers. Your other applications are now offline.
  7. On the computer where the database is located, create a backup of the database for Rational Asset Manager, which is the database for assets. For instructions, see the documentation for your database application.
  8. Create a backup of the database for IBM Rational Team Concert, which is the database for lifecycles. For instructions, see the documentation for your database application.
  9. Create a backup of the Persist folder that you noted in step 4.
  10. Create a backup of the Index folder for every node. Rational Asset Manager can completely rebuild the Index folder after you restore the repository. However, for large repositories, if you restore the Index folders, the search index rebuilds faster.
  11. Create a backup of your configuration files:

What to do next

By using the Persist folder and databases, you can recover your repository. For more information, see Restoring from a backup.

Restoring from a backup

With the databases, the persist folders, and some configuration files, you can recover your IBM Rational Asset Manager repository and server configuration.

Before you begin

Create a backup of your repository, as described in Creating a backup of a Rational Asset Manager repository.

You must have the following permissions:

Procedure

  1. From your backups, restore both the asset and lifecycle databases to your database server.
  2. From your backups, restore the Persist disk storage folder. If you cannot restore the Persist folder to the same path, you can change the location of the Persist folder.
  3. From your backups, restore the Index disk storage folder. If you are using an IBM WebSphere Application Server cluster, you must restore the Index folder for each node. If you restore the index folders, Rational Asset Manager can rebuild the search index faster.
  4. From your backups, restore the configuration for your application server:
  5. Start the application servers.
  6. If it is not already started, start the Rational Asset Manager web application.
  7. If you cannot restore the Persist and Index folders to the same location, with the same path to the directories, you can change the location of the folders.

Results

Your repository is restored from the point of your backup. Depending on the size of your repository and whether you restored the Index folders, it might take several minutes for the search index to rebuild.

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:

Procedure

  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.

Procedure

  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. Locate and delete the storage directories for Rational Asset Manager:
    1. Click Resources -> URLs.
    2. Click All scopes.
    3. You will see many variables called RAM Persist, RAM Local, and RAM Index.
    4. Click on every variable and note the values of the variables, which will be directories.
    5. Delete all files and folders in those directories. On a WebSphere Application Server ND environment, the Persist directory will be a single shared directory, and there will be an Index and Local directory for every node in the cluster.
    6. After you have deleted all of the directories, delete all the variables called RAM Persist, RAM Local, RAM Index, and RAM CQJRE
  8. Delete the datasource for Rational Asset Manager:
    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 -> Global security -> Java Authentication and Authorization Service -> J2C Authentication Data.
    5. Delete the entry whose name matches the component-managed authentication alias that you noted.
  9. If you installed Rational Team Concert onto your server or cluster, delete the datasource for Rational Team Concert:
    1. Locate and click the Datasource with the JNDI name jdbc/RTC_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 server that Rational Team Concert 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 -> Global security -> Java Authentication and Authorization Service -> J2C Authentication Data.
    5. Delete the entry whose name matches the component-managed authentication alias that you noted.
  10. Optionally, if your server is a network deployment cluster, delete the 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.
  11. If necessary, manually uninstall each enterprise or Web archive to be removed from the application server:
    1. Click Applications -> Application types.
    2. Click WebSphere 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.
  12. Delete custom properties for IBM Rational Team Concert:
    1. Click Servers -> Server types -> WebSphere 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.
  13. Stop the server. On a cluster, you only need to stop the application server that was running Rational Team Concert.
  14. Navigate to the following directory on your hard drive: WebSphere_install_directory\profiles\profile_name\temp\server_name\
  15. In the server_name directory, delete the following directories:

    For a WebSphere Application Server Cluster, delete the above directories on every physical computer in the cell.

  16. Navigate to the following directory on your hard drive: WebSphere_install_directory\profiles\profile_name\config\cells\cell_name\. On a cluster, this directory will be in a subdirectory of the profile of the machine where Deployment Manager is installed.
  17. In the cell_name directory, delete the RTC directory.

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.

Procedure

  1. Start the IBM WebSphere Application Server Administrative Console.
  2. Log in using an administrator user ID and password.
  3. Delete the datasource for Rational Asset Manager:
    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 -> Global security -> Java Authentication and Authorization Service -> J2C Authentication Data.
    5. Delete the entry whose name matches the component-managed authentication alias that you noted.
  4. If you installed Rational Team Concert onto your server or cluster, delete the datasource for Rational Team Concert:
    1. Locate and click the Datasource with the JNDI name jdbc/RTC_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 server that Rational Team Concert 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 -> Global security -> Java Authentication and Authorization Service -> J2C Authentication Data.
    5. Delete the entry whose name matches the component-managed authentication alias that you noted.
  5. Optionally, if your server is a network deployment cluster, delete the 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.
  6. Remove the applications.
    1. Click Applications -> Application types -> WebSphere 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.
  7. Locate and delete the storage directories for Rational Asset Manager:
    1. Click Resources -> URLs.
    2. Click All scopes.
    3. You will see many variables called RAM Persist, RAM Local, and RAM Index.
    4. Click on every variable and note the values of the variables, which will be directories.
    5. Delete all files and folders in those directories. On a WebSphere Application Server ND environment, the Persist directory will be a single shared directory, and there will be an Index and Local directory for every node in the cluster.
    6. After you have deleted all of the directories, delete all the variables called RAM Persist, RAM Local, RAM Index, and RAM CQJRE
  8. Delete custom properties for IBM Rational Team Concert:
    1. Click Servers -> Server types -> WebSphere 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.
  9. 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.
  10. 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.
  11. Stop the server. On a cluster, you only need to stop the application server that was running Rational Team Concert.
  12. Navigate to the following directory on your hard drive: WebSphere_install_directory\profiles\profile_name\temp\server_name\
  13. In the server_name directory, delete the following directories:

    For a WebSphere Application Server Cluster, delete the above directories on every physical computer in the cell.

  14. Navigate to the following directory on your hard drive: WebSphere_install_directory\profiles\profile_name\config\cells\cell_name\. On a cluster, this directory will be in a subdirectory of the profile of the machine where Deployment Manager is installed.
  15. In the cell_name directory, delete the RTC directory.
  16. Restart the server.

Notices

© Copyright IBM Corporation 2007, 2011. 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