Also consider the connectivity to each of the constituent components. If the products cross firewall boundaries, open the appropriate ports for each of the integrated products.
Client applications must be installed on the same computer as the server and Rational Asset Manager server application. To improve performance, run the servers for these applications on computers other than the application server.
When you deploy the product to a cluster environment, the components must use the same operating system and application server. If you plan to integrate with Rational ClearCase, the client applications must be installed on every component in the cluster and have the same installation path on every node in the cluster. You cannot configure individual nodes independently.
You can create links between artifacts on Jazz™ servers and assets in Rational Asset Manager. For example, you could create a defect in IBM Rational Team Concert about an asset, and then create a link between the asset and the work item. For more information about integrating with Jazz servers, see Integrating with IBM Jazz Servers.
Rational Team Concert is a team collaboration tool that is built on a scalable, extensible platform that integrates tasks across the software lifecycle. You can create or link to work items on the Rational Team Concert server. You can also link asset files with Rational Team Concert source control, so that when users download files from Rational Asset Manager into their Eclipse clients, they are prompted to download the most recent version from the source control system. For more information about Rational Team Concert, see Integrating with Rational Team Concert.
You can add Rational Asset Manager to an Eclipse integrated development environment so that you can search for assets, download artifacts into your workspace, create new assets from your files in your workspace, and collaborate on assets. For information about installing the Rational Asset Manager into an Eclipse client, see Installing the Rational Asset Manager Eclipse client.For more information about what you can do with the Eclipse client, see Integrating with Eclipse.
You can view IBM Connections business cards in the Rational Asset Manager applications. Also, in IBM Connections you can view a list of the assets in Rational Asset Manager that you have to approve. For more information about IBM Connections, see Integrating with IBM Connections.
Rational Asset Manager complements existing build applications systems such as Build Forge®. You can use Rational Build Forge to create a build based on assets in Rational Asset Manager, and you can also use the integration to publish the build results as new assets in Rational Asset Manager. A set of supplied scripts enables you to download assets, check dependencies, compile, build, and deliver results as new assets. For more information about Rational Build Forge, see Integrating with Rational Build Forge.
You can easily post models and topologies from your modeling application to Rational Asset Manager, where others can review and approve your work. For more information about modeling tools, see Integrating with Rational modeling tools.
As part of the Rational Asset Manager and WSRR integration, you can publish Rational Asset Manager assets into WSRR. When you plan to integrate the registries for the two applications, consider the usage of the registries. For example, if Rational Asset Manager is the development time registry that contains assets that development teams use and WSRR is a runtime registry that is used for documents and for the logical services that are derived from the documents, then some assets that are developed might be deployed and a portion of the artifacts of the asset might be published in WSRR.
After the artifacts of a Rational Asset Manager asset pass onto WSRR, they are owned and managed as runtime documents. They can change and be governed as needed by the runtime organization. However, it is useful for both development and the runtime organization to preserve links between the development assets and their runtime counterpart documents so that users can understand the links between developed assets and the deployed documents. For more information about WSRR, see Integrating with WebSphere Service Registry and Repository.
To support the integration scenarios, Rational Asset Manager uses the Reusable Asset Specification (RAS) from the Object Management Group (OMG) as the core structure for asset metadata. To integrate with tools and other repositories, such as IBM Tivoli® CCMDB, additional metadata is required. RAS provides a structure for unique asset identification and metadata extension; this combination provides the basis to manage references between Rational Asset Manager and Tivoli CCMDB.
By using RAS in Rational Asset Manager, the enterprise can configure multiple asset types to meet their particular needs. Regardless of the asset type configuration in Rational Asset Manager, the synchronization works with Tivoli CCMDB. In addition to the asset metadata (such as ID, which creates a reference between Rational Asset Manager and Tivoli CCMDB) other metadata elements (such as classification) are synchronized between Rational Asset Manager and Tivoli CCMDB. Synchronizing asset classification and metadata can reduce administrative tasks and simplify developer use. Even so, when you select a subset of Rational Asset Manager assets and a subset of configured items in the CCMDB repository, you create a many-to-many connection point, which makes tracing relationships and finding necessary information more complicated.
The volatility of the references in each of the repositories can impact several levels of integration for these references, and thus impact the performance of Rational Asset Manager. Determine what to connect across the repositories. Do not connect all Rational Asset Manager assets for all asset types to all possible configured items in CCMDB. Instead, identify the scenarios that are relevant to your enterprise and then identify the asset and configured item relationships that you need to support those scenarios, selecting a subset of the asset and configuration item relationships to manage. For more information about using Tivoli Change and Configuration Management Database, see Integrating with Tivoli Change and Configuration Management Database.
Rational ClearCase provides version control, automated workspace management, parallel development support, baseline management, and build and release management, which can improve productivity and operational efficiency. To meet internal and external compliance requirements, Rational ClearCase contains extended security features, such as user authentication and audit support. You can use UCM capabilities to add project and workflow management to Rational ClearCase.
For more information about Rational ClearCase see Integrating with Rational ClearCase.
IBM Workload Deployer is a hardware appliance that provides access to software virtual images and patterns that can be securely deployed, managed, and maintained in a private cloud. For more information about IBM Workload Deployer, see Integrating with IBM Workload Deployer.