The following information pertains to additional configuration
steps that you can use to customize your installation beyond what is necessary
to run Rational® Asset
Manager.
Configuring a user registry
By default, IBM® Rational Asset Manager uses
file-based authentication to store user information in a flat file.
Instead, you can use other user registries, such as Lightweight Directory
Access Protocol (LDAP) or a database for storing user information.
A generic class is provided for accessing LDAP registries, but you
can also specify a custom class to access other types of registries.
Creating and installing custom extensions
You can create custom review processes and custom policies.
Repository administrators can then install them onto the IBM Rational Asset Manager server
application.
Setting up single sign-on with LTPA between two servers
You can set up a single sign-on environment between two
computers that run IBM WebSphere® Application Server.
Then, users can log on to an application on WebSphere Application Server on one computer
and access an application on WebSphere Application
Server on a second computer without logging on to the second computer.
Modifying job schedules
Configure how frequently certain server jobs run. The amount
of time necessary to complete a given job depends on the number of
assets in the repository or the number of users and groups in the
registry.
Exporting repository models
A model represents a repository and its asset structure,
including asset types, categories, attributes, relationships, and
configuration information. Model information is stored in the database.
Server machines that use the same database use the same model. To
facilitate reuse across repositories, or to use model information
that is produced by another application, you can import and export
models as XML metadata interchange (XMI) files.
Configuring NFS support
You can configure IBM Rational Asset Manager to
work with a bundled Network File System (NFS) server so that assets
on the Rational Asset Manager server
are available to an NFS client. In this scenario, assets stored in Rational Asset Manager can
be mounted as files on another computer. For example, you could mount
a .ear file stored in Rational Asset Manager to
install it on another computer. In this scenario, there is no need
to download the .ear file and then delete it
after installation. Also, less disk space is required on the client
computer. Disk space can be a concern when using virtual images in
the cloud.
Configuring help content
You can choose how to set up the Rational Asset Manager help
and how to receive content updates after installing the product.