Deploying and configuring application files by using the server setup application

On Linux, AIX®, or Linux for zSeries®, increase the number of file descriptors a process might have open at once to at least 65535:

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 65535, increase the limit with the following command: ulimit -n 65535

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 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 check box is selected, select the Enable application security check box.
5. Click Apply.
6. In the Messages window, click Save directly to the master configuration.
7. Stop, and then restart the server.

• com.ibm.ram.repository.web_runtime.ear
• RTC-Server_401.zip
• RTC-Server_3013.zip
• ramhelp_war.ear
• rmcabdgovernprocess_war.ear

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

1. Select the database application that you will be using from the Database vendor list.
2. Select the type of user authentication for the Rational Asset Manager web application to 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 information 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.
     Tip: File-based authentication is not intended for use in a production environment. An LDAP or custom user registry supports common security practices such as rules for password patterns, password expiration, and account lockouts to prevent enumeration attacks. File-based authentication does not support these features.
   • 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 must 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 must create a Network Deployment cluster for Rational Asset Manager, see the WebSphere Application Server documentation.
5. Click Next.

• com.ibm.ram.repository.web_runtime.ear
• RTC-Server_401.zip
• RTC-Server_3013.zip
• ramhelp_war.ear
• rmcabdgovernprocess_war.ear

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.

1. Select one or more applications 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. A separate page opens to show the progress. The process to deploy one or more applications can take several minutes.
4. Click Next to review the results.
5. On the Summary page, click Next.

1. Select whether to create new databases or use existing databases.
   • To create new Assets and Lifecycles databases, select You need to Create all three databases and then click Next. Go to step 12.b.
   • To create new Lifecycle databases and use an existing Assets database, select You need to Create both RTC's CCM and JTS databases and then click Next. Go to step 12.b.v.
   • To use an existing Assets and Lifecycles databases (for example, if you are upgrading from a previous version of Rational Asset Manager), select You have already created all three databases and want to modify the settings and then click Next. Go to step 13.
2. Create a database.
   • For DB2 on a supported operating system other than z/OS®, you can use a Java™ applet to create 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 Assets 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 RTC's CCM field, type a name for the Change and Configuration Management (CCM) lifecycle management database (for example, CCMDB). In the Create a database for RTC's JTS field, type a name for the Jazz Team Server (JTS) lifecycle management database (for example, JTSDB). 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 create the database.
   The instructions displayed in the server setup application are identical to those at Creating the database for assets.

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\was\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: Replace back slashes ("\") in the directory paths with forward slashes ("/").
     Note: For Oracle, you can download the appropriate .jar file, ojdbc6.jar, from Oracle. For Microsoft SQL Server, you can download the appropriate .jar file, sqljdbc4.jar, from Microsoft.
     Important: 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 RTC's CCM field, type the name of the CCM Lifecycle management database; for example, CCMDB. Then, type the User ID and Password for a database administrator.
7. In the Database name for RTC's JTS field, type the name of the JTS Lifecycle management database; for example, JTSDB. Then, type the User ID and Password for a database administrator.
8. Click Test Connection. The server setup application reports whether the server could connect to the databases.
9. If the connection test was successful, click Next.

1. For Step 5: Populate Rational Asset Manager Core Database, click Populate the database if the database configured with errors.
2. Click OK to continue configuring the database. This process can take a few minutes.
3. For Step 6: Populate Rational Asset Manager Lifecycle Databases, click Populate the databases if the databases configured with errors.
4. Click OK to continue configuring the databases. This process can take a few minutes.
5. After the databases are configured, click Next.

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.

• If you are finished specifying your configuration settings (for example, if you are using the server setup application to make changes to an existing setup), restart the server now. To restart the server, click Tools > Restart the server.
• To continue without restarting the server, click Next.

• If you chose LDAP authentication in step 7.b, configure the connection to the LDAP on the Configure LDAP Authentication page. LDAP must be running and the LDAP server must be accessible from this computer.
  1. Configure the LDAP repository connection. On this page, you define the information that Rational Asset Manager server uses to contact the LDAP server: the address of the LDAP server, the communications port, and if necessary, a user ID and password that Rational Asset Manager will use to query the registry.
     • LDAP Vendor: Select your LDAP software. When you select a vendor, the suggested value column shows example values for some of the properties that the LDAP server requires.
     • Server: Type the name of the server on which LDAP is installed; for example, ldap.example.com. If security is enabled on the LDAP server, check SSL enabled.
     • Port: type the port number of the LDAP server.
     • Connect Anonymously: If your LDAP repository does not require a user ID and password for access, select this check box. If your LDAP repository requires a user ID and password, clear this box and complete the Bind User DN and Bind Password text fields.
     • Bind User DN: Type the distinguished name (DN) of a user that has access to query the LDAP database. Rational Asset Manager uses this user name to access LDAP. For example, uid=123456,c=us,ou=exampleorganization,o=example.com.
     • Bind password: if you typed a user DN, type the password for the user name.
     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 and click Security > Global security > Standalone LDAP registry > Configure to apply the appropriate configuration property to prevent possible LDAP user account lockouts if users log in to Rational Asset Manager with invalid credentials.

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

  2. Click Test connection. If the server setup application connects to LDAP, continue. You cannot proceed with LDAP Authentication until a connection is configured.
  3. Identify a user in the LDAP registry to be the Rational Asset Manager repository administrator.
     • Administrator ID: Type the unique ID of the user who will be the repository administrator for Rational Asset Manager. The repository administrator is responsible for configuring Rational Asset Manager server. For example (if your LDAP uses email address as the unique identifier) Administrator@example.com.
     • Password: type the password for the administrator ID.
     • User search filter: Type the syntax that LDAP will use to query for a user. The %v represents the search term that was entered from an input text field. The search will run as if a wildcard is part of 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.
     • User search base: type the path of the root from where to start searching the LDAP registry for users; for example, ou=exampleorganization,o=example.com.
  4. Click Verify the User.
  5. If the server setup application found the user in the LDAP registry, click Next. Do not continue configuring LDAP authentication until a user has been identified as the repository administrator.
  6. On the next page, map user properties in Rational Asset Manager to the corresponding user properties in your LDAP registry. Rational Asset Manager requires this information for user authentication, for user data retrieval and display, and to communicate with users by email.
     • Unique identifier: Type the property name of the user's objectClass instance that represents the unique user's ID. For example: (objectClass) person's serialNumber property, or the (objectClass) user's sAMAccountName property. The default value is uid.
     • Login identifier: Type the (objectClass) property that users use as their login ID. Even though it is common for the Unique ID and login ID to be the same, you can set the registry so that a user logs in using another ID (for example, an email address). For example, userPrincipleName.
     • LDAP user name query: Type the LDAP search query that maps the short name of a user to an LDAP entry; for example, *:userPrincipleName or *:uid.
     • Email: Type the property name that contains a user's email address; for example, mail.
     • Phone number: Type property name that contains a user's phone number; for example, telephonenumber.
     • Locale: Type the property name of the user’s email language setting; for example, zh-TW, or leave the field blank for the default value and for users to manage their email language setting. If the value is a language that is supported in Rational Asset Manager, such as de, ko, ja, zh_TW, zh_CN, es, pt_BR, en, fr, and ru), the user profiles are set with that language preference. It the value is not valid or does not exist in LDAP, en (English) is used by default.
     • Image URL Template: You can store images somewhere other than an LDAP registry. If you can retrieve a user's image by using a URL, configure this template to retrieve the image at the same time as the user information in the registry. In the template, ${value} represents a LDAP user property of the user object that will be replaced when the image is retrieved. For example, for a user with a uid property=123456, the default template https://image_server_url/photo/${uid}.jpg results in the URL https://image_server_url/photo/123456.jpg.
  7. Click Test the Mapping. If all mappings are correct, the administrator's user ID, name, email, phone number, and photo are displayed with a success message.
  8. Specify user group properties in LDAP. User group information in LDAP can be retrieved and reused by Rational Asset Manager communities. In Rational Asset Manager, communities are the primary organizational grouping within a repository: they are collections of users with a common interest in a set of assets, and each community can define its members, member roles, permissions, processes, and assets.
     • User group search 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.
     • User group search base: type the base search for searching groups; for example, ou=memberlist,ou=groups,o=example.com.
     • Group ID Map: type the LDAP search query that maps the short name of a group to an LDAP entry; for example, *:cn.
     • Group Member ID Map: type the LDAP search query that identifies user-to-group relationships; for example, memberof:member.
  9. Click Next. The Users and Authentication Configuration summary page opens.
  10. To complete the configuration, restart the application server. You can also wait to restart the server until you complete the other steps in the server setup application.
  11. Click Next.
  Note:

  This configures LDAP authentication for only the Rational Asset Manager application.

• If you chose File-based authentication in step 7.b, add or delete users from the list on the Configure File-based Authentication page. File-based authentication means that user information is stored in a text file on the server. By default there are six users ("admin" and "user1" through "user5").
  Note: The passwords for the six default users are the same as their user IDs.
  1. Add, edit, or delete users:
     • To filter the list of users, type a search string in the Search text field and click Search. You can use wildcards (*). To see the entire list, type * in the Search text field.
     • To add a user, click Add User and type the user's ID and password.
     • To delete a user, next to that user's name, click Delete.
  2. When you are finished, click Next. The Users and Authentication Configuration summary page opens.
  3. To complete the configuration, restart the application server. You can also wait to restart the server until you complete the other steps in the server setup application.
  4. Click Next.
  5. Go to step 11.
• If you chose to use a federated repository, the local operating system, or a custom user registry (other than file-based) in step 7.b, you will be prompted to confirm that the user ID of the administrator for the user registry will be the repository administrator. There are no other configuration options for this type of authentication.

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

   • Separate server addresses with semicolons (;), for example, 27000@main.example.com;27000@backup.example.com.
   • 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: 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.

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

1. In Step 1, In the Rational Team Concert server field, type the path to the Rational Team Concert location. In the Jazz Team Server field, type the path to the Jazz Team Server location.You must use a secure (https://) connection. By default, these values are:
   • For an existing WebSphere Application Server: https://server_host:9443/ramccm and https://server_host:9443/ramjts for the Jazz Team Server.
   • For an external Rational Team Concert server: https://url:port/ccm and https://url:port/jts for the Jazz Team Server.
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.