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.
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.
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..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.
http://server:8080/ram/home.faces
http://localhost:8080/ram/home.faces
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.
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.
http://www.example.com:9080/ram.ws
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'scn 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. |
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
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.
http://www.example.com:9080/ram
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.