Creating components from Rational Asset Manager
IBM® Rational® Asset Manager is a library management system for creating and governing software assets.
To learn more about Rational Asset Manager, see Rational Asset Manager .
- In IBM UrbanCode® Deploy, click Components, and then click Create Component.
- In the Create 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 Configuration Type list, select Rational Asset Manager.
- Specify the following parameters for the component:
- Repository URL
- The location of the Rational Asset Manager repository.
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:
- The Rational Asset Manager user name.
- The password that is associated with the Rational Asset Manager user name.
- Unique ID
- The ID, or GUID, of the Rational Asset Manager asset to load as a component source. In Rational Asset Manager, the ID of an asset is displayed in the Attributes section of the General Details page for the asset.
- Version Pattern
- A regular expression that represents the version of the Rational Asset Manager asset
to load as a component source. For example, (1\.[0-9]+).* matches
versions such as
22.214.171.124A. If the expression matches more than one version, all versions are imported, up to the number in the Latest Build Count field.
- The state of the Rational Asset Manager asset
to load as a component source. Specify a value 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 documentation.
- The query to use to select an asset to load. Use this field only if you want to specify the asset with a complex query.
- Latest Build Count
- The number of the search results to load. 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.
- Extensions of files to Convert
- If text-type files must be converted into another character set, type the list of file
extensions to be converted. Matching file types are converted into the default or system character
set of the system where the agent is located. Separate list items with commas, for
- If file types are listed in the Extensions of files to Convert field, specify the character set to use. Otherwise, the file types are converted into the default or system character set of the system where the agent is located.
- Include Dependent
- Select to load the related assets that the asset depends on.
- Preserve Execute Permissions
- For Linux™ and UNIX™ operating systems, select this check box to retain the execute permissions for each file.
- 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 Import New Versions.and then clicking
- Copy to CodeStation
- This option, which is selected by default, creates tamper-protected copies 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. The default for this setting is in the system setting Components copy to CodeStation by default. For more information, see Server settings.
- Default Version Type
- Specify how to import versions into CodeStation:
- Each version is comprehensive and contains all artifacts.
- Each version contains a subset of artifacts.
- Use the system's default version import agent/tag
- If this parameter is selected, the agent or tag that you specified on the System Settings page is used to import component artifacts. Agents must have access to the system where the artifacts are located. For more information, see Server settings.
- Import new component versions using a single agent
- If this parameter is selected, use the Agent for Version Imports field to identify the agent that is used to import artifacts into the component. The agent must have access to the system where the artifacts are located. To import artifacts from where the server is located, install an agent in the same location and specify that agent.
- Import new component versions using any agent with the specified tag
- If this parameter is selected, use the Agent Tag for Version Imports field to identify the tag that is used to select agents to import artifacts into the component. All tagged agents must have access to the system where the artifacts are located.
- Use Default Artifact Cleanup Settings
- To apply the component version cleanup settings that are specified on the System Settings page, select the Use Default Artifact Cleanup Settings check box. If this check box is cleared, you must specify how long to keep component versions. For more information about cleaning up component versions, see Cleaning up component versions.
- Run Process after a Version is Created
- To automatically run a process after versions are
imported, select this check box, and then specify an application process and an environment for the
process. The process runs only when the version is imported automatically, not when you import
versions manually. Similarly, the process does not run when you create versions with the REST API or
udclientcommand. If the automatic version import finds multiple versions, the process runs only once.
- Click Save.