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

Verify that all of the repository servers are set to the same current date, time, and time zone.
Access the Rational Asset Manager server application using the appropriate URL:
- On WebSphere Application Server:
```
http://server:port_number/Rational_Asset_Manager_Context_Root/home.faces
```
  where port_number (HTTP transport port, or WC_defaulthost) is 9080 by default and Rational_Asset_Manager_Context_Root (context root for the Rational Asset Manager application) is ram by default..
  For example, type:
```
http://www.example.com:9080/ram/home.faces
```
  To confirm the WC_defaulthost value, open the WebSphere Application Server administrative console and click Servers > Server types > WebSphere application servers > server_name > Ports.
- On Apache Tomcat:
```
http://server:8080/ram/home.faces
```
  For example, type:
```
http://localhost:8080/ram/home.faces
```
Log in as an application server administrator:
- For WebSphere Application Server, the default User ID and Password are admin.
- For Apache Tomcat, the default User ID is admin and the default Password is blank.
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.
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 select Repository administrator use only for the License type, the Location of license server field is disabled.
  
  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, Enterprise edition, or Repository administrator use only. Licenses are not required for users who are repository administrators. Repository administrators have authority to perform any activity with the Rational Asset Manager web application. Do not assign repository administrator privileges to typical users. If you select Repository administrator use only, users who are not repository administrators cannot view asset details and cannot submit or update assets.
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.
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
```
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 user name 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.

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:

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

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 1. 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 9.b.
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's`cn` property.
Locale property	The (objectClass) property representing the language for the user to display the interface in. For example: `es`
User's user class property	The (objectClass) property to use when determining if a user is in a particular user class. If this field is left empty, users are not separated into classes. For example: `company`. Enter `DN` to use the distinguished name as the property for separating users into classes.
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

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.
In the Disk Storage section, configure disk storage for assets and index files:
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.
1. From the Persist type list, select how you want to store assets.
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. For Linux and UNIX systems, if the persist location is on a shared location on a remote system, the remote location must be mounted to a local directory on the Rational Asset Manager server.
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.
Specify the web server path:
1. Under Web Server Path, type:
```
http://server:port_number/Rational_Asset_Manager_Context_Root
```
  where server 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
```
Specify the documentation path:
1. In the Path to Information center field, if the 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://server.com:port/ram.help. If you use IPV6, use the IPV6 hostname; an IPV6 address will not work. If the documentation web application does not use the same protocol type, domain name, and port number as the server application, the context-sensitive help is not displayed.
  Attention: Whether you install the documentation web application on the same server or a different server, the public information center content is loaded automatically into the application. If you do not have internet access or prefer to install the help plugins, from the help server you can open the Local Help Updater with the URL http://127.0.0.1:port/help/updater/updatewar.jsp and install the plugins. To change the help preferences, open the URL http://server.com:port/ram.help/remote/remotehelp.jsp.
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://server.com:port/ram.process. If you use IPV6, use the IPV6 hostname; an IPV6 address will not work.
In the Job Schedules section, configure how frequently certain repetitive jobs will run:
- Statistics index builder schedule is the schedule for updating information provided in the Repository Statistics page, the Asset Statistics page, and the home page.
- The Process subscriptions schedule is the schedule for sending email subscriptions to subscribers. Typically, this would be scheduled to run once per day.
- The User/group information update schedule is the schedule for how often information is updated from, and written to, the user directory. Information in an LDAP registry is not updated through this process, however; any recent updates to the information in an LDAP registry is updated in the Rational Asset Manager user information.
- The Review process notifications schedule is the schedule for processing alerts to reviewers indicating that an asset requires their review. For example, if set to one hour, then the notifications for all new assets created within the hour are sent at the beginning of the next hour.
- The Artifact cache refresh schedule is the schedule for refreshing the cache of artifacts that have been downloaded.
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.
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.
At the bottom of the page, click Save.
Restart your application server.
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.)
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.

Feedback