The server setup application is a browser-based web application
for IBM® WebSphere® Application Server that
helps you deploy the other IBM 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:
- Deploy the Rational Asset Manager server
applications and the included IBM Rational Team Concert™
- Create and configure databases for assets and lifecycles
- Configure security for the application server
To configure Rational Asset Manager,
the setup enterprise archive must be deployed and running, and the
database server must be running:
- Deploy the com.ibm.ram.repository.setup.web enterprise
archive on a running application server. You can do this by using IBM Installation Manager to
install the Rational Asset Manager feature
on an existing WebSphere Application Server.
For more information about these options in Installation
Manager,
see Installing Rational Asset Manager server by using Installation Manager.
- Install a database application, either locally or remotely, that
the Rational Asset Manager server
can access. If you plan to use the server setup application to configure IBM DB2®,
the browser that you run the server setup application in must be on
the computer on which DB2 is
installed.
Important: - You must have database administrative (DBA) privileges for the
database server. The database user ID must also adhere to all the
requirements that are indicated in the database vendor specific topics.
You can find these topics in the items under Creating and configuring
databases for Rational Asset Manager.
- You must start Rational Asset Manager setup
by using the application server administrator ID that created the
server.
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 . 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 .
To view the current details of your server
environment, click .
Procedure
- Verify that all of the repository
servers are set to the same current date, time, and time zone.
- On Linux, AIX®, or Linux for zSeries, increase the number of file descriptors
a process might have open at once to at least 65535:
- To view the current number of descriptors that can be
open at once, in the command line type: ulimit -n
- 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:
- 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
- Click Security.
- Click Global security.
- In the Administrative Security section, if the Enable
administrative security check box is selected, select
the Enable application security check box.
- Click Apply.
- In the Messages window, click Save directly
to the master configuration.
- Stop, and then restart the server.
- If you 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.
- 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:
- 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.
- 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.
- On the Introduction page, indicate the type of database
and user authentication to use:
- Select the database application that you will be using
from the Database vendor list.
- 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.
- 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.
- 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.
- Click Next.
- In the Step 1: Locate Installation
Files section, click Provide the directory which contains
the following files on the server and
then 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:
- 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.
- To verify that all required application
files are in the directory, or to upload them to the server, click Verify
Installation files. If you uploaded the application
files, the server setup application saves them to a temporary directory.
A message verifies if all the required files are present.
- 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.
- 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:
- Select one or more applications to deploy.
- 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.
- Click Deploy Applications. A separate page opens to show the progress. The process
to deploy one or more applications can take several minutes.
- Click Next to review the results.
- On the Summary page, click Next.
- In Section 2, Part 1, either create new databases or connect
to existing databases:
- 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.
- 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:
- 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.
- To use a different installation of DB2,
click Change install location.
- Type the User ID and Password for
the DB2 administrator. DB2 administrators
are managed by the operating system.
- After you select the appropriate location, in the Create
a database for Assets field, type a name for the asset
database (for example, RAMDB).
- 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.
- 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.
- In Section 2, Part 2, specify the database connection
properties:
- 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).
- In the Port field, type the port
number. For example, the default value for DB2 is 50000.
- Type the user ID and password of a user with administration
authority for the database application.
- 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: 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.
- 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.
- 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.
- 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.
- Click Test Connection. The server
setup application reports whether the server could connect to the
databases.
- If the connection test was successful, click Next.
- In Section 2, part 3, populate the databases :
- For Step 5: Populate Rational Asset Manager Core
Database, click Populate the database if the
database configured with errors.
- Click OK to continue configuring
the database. This process can take a few minutes.
- For Step 6: Populate Rational Asset Manager Lifecycle
Databases, click Populate the databases if
the databases configured with errors.
- Click OK to continue configuring
the databases. This process can take a few minutes.
- 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.
- 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.
- Click Next.
- 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.
- 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 .
- To continue without restarting the server, click Next.
- In Section 3, configure users and authentication:
- In Section 4, configure settings for Rational Asset Manager:
- 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.
By default, Rational License
Key Server uses TCP/IP port 27000.
- In the License type section, select the type of license
that the Rational Asset Manager server
will use.
- 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.
- 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.
- Click Next.
- 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.
- Click Next.
- 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.
- Optional: In Section 4, Part 3, configure performance
settings for WebSphere Application Server:
- Configure server settings.
- Click Next.
- 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.
- Click Next. The summary
page is displayed again.
- 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.
- In the Configure Lifecycle management
settings page, type the path and login information for the Rational Team Concert application:
- 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.
- 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.
- 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.
- Click Configure server. This
process might take a few minutes. After the configuration,
the Summary page appears.
- 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.