IBM® Rational® Asset Manager is
a library management system for creating and governing software assets.
Before you begin
Add the
IBM Rational Asset Manager client
library to the
IBM UrbanCode Deploy server:
- Log on to Rational Asset Manager from
a web browser.
- Click .
- Under Client API Jars, download the ramclient.zip file.
- Extract the file on the server to the folder server_install/server/extensions/ramclient,
where server_install is the
installation location of the IBM UrbanCode Deploy server.
- Restart the IBM UrbanCode Deploy server.
About this task
To learn more about
Rational Asset Manager,
see the
Rational Asset Manager information
center.
Procedure
- In IBM UrbanCode Deploy,
click Components, and then click Create
New Component.
- In the Create New Component window,
specify a name and description for the component.
- In the Teams fields,
specify the access information for the new component.
- To use a template for the new component,
select a template from the Template list. In this case, the component inherits source configuration, properties,
and processes from the template. For information about templates,
see Component templates.
- In the Source Config Type list,
select Rational Asset Manager.
- Specify the following parameters for the component:
- Repository URL
- The location of the Rational Asset Manager repository.
This field is required. To find the repository URL, log on to Rational Asset Manager from
a web browser. Click . The repository URL is displayed in the Repository
location field, such as the following example:
http://ram.mycompany.com:9080/ram
- User
- The Rational Asset Manager user
name.
- Password
- The password that is associated with the Rational Asset Manager user
name.
- Asset ID
- The asset ID, or GUID, of the Rational Asset Manager asset
to load as a component source. This field is required. In Rational Asset Manager,
the ID of an asset is displayed in the Attributes section
of the General Details page for the asset.
- Version
- A regular expression that represents the version of the Rational Asset Manager asset
to load as a component source, for example, 6.0.0.*.
- State
- The state of the Rational Asset Manager asset
to load as a component source. This field is optional; specify a value
if you want to limit the component to only assets with the specified
state.
States are defined in lifecycles in Rational Asset Manager.
To learn more about lifecycles, see Asset development and lifecycles in the Rational Asset Manager information
center.
- Query
- The query to use when selecting an asset to load. Use this field
only if you want to specify the asset with a complex query.
- Include Dependent
- Select to load the related assets that the asset depends on.
- Latest Build Count
- The number of the search results to load. This field is required.
By default, only the most applicable result is loaded. However, to
load more than one version or state of the asset, specify the number
to load.
- Preserve Execute Permissions
- For Linux and UNIX operating systems, select this check box
to retain the execute permissions for each file.
- Import Versions Automatically
- Select this check box to check for new versions periodically and
to import new versions automatically. Also, if you select this check
box, the server synchronizes the status of the component with the
state of the asset.
If you do not import versions automatically,
you can import versions manually by clicking and then clicking Import New Versions.
- Copy to CodeStation
- This option, which is selected by default, creates a tamper-protected
copy of the artifacts and stores them in the embedded artifact management
system, CodeStation. If the check box is cleared, only metadata about
the artifacts is imported. In most cases, keep this check box selected.
- Default Version Type
- Specify how to import versions into CodeStation:
- Full
- Each version is comprehensive and contains all artifacts.
- Incremental
- Each version contains a subset of artifacts.
- Inherit Cleanup Settings
- Specify how many component versions to keep in CodeStation, and
how long to keep them. If you select this check box, the component
uses the values that are specified on the System Settings pane.
If you clear this check box, the Days to Keep Versions (initially
set to -1, keep indefinitely) and Number of Versions to
Keep (initially set to -1, keep all) fields are displayed,
and you can define custom values.
- Run process after creating a new version
- To automatically run a process after each new version is created,
select this check box and then specify an application process and
an environment for the process.
- Click Save.
Results
The new component is listed on the
Components page.
The
Versions tab shows the versions of the component
that are available. If you selected the
Import Versions
Automatically check box, versions are displayed automatically.
Otherwise, click
Import New Versions to show
the available versions. Depending on the number and size of the artifacts,
it might take time before the versions are displayed. To see the artifacts
in the component, click a component version.
What to do next
Create processes for the component. See
Configuring component processes.