Configuring repositories 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

Procedure

  1. 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:For Linux: If you are using a remote file server or a WebSphere Application Server cluster, the same Windows user account (user name and password) must be able to log on to every computer 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.
  2. 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.
  3. 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.
  4. 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 an existing WebSphere Application Server: https://localhost:9443/ramjazz
      • For an external Rational Team Concert server: https://url:port/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 user name 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.
  5. On the Summary page, click Start using Rational Asset Manager. or click Finish. The web client opens.

What to do next

Feedback