Postinstallation tasks for OSLC integrations
OSLC-based integrations share common postinstallation tasks that must be performed to establish communication between integrated applications.
Server cross-communication
Secure communication among servers for integrated applications must be established. For IBM Engineering Lifecycle Management products, this communication is through server friending. A server friend is one that allows communication with other friend servers in a secure way. You must establish server communication from each application of your integrations. For example, when you use the Rational Adapter for HP ALM to work with IBM Engineering Workflow Management and IBM Engineering Requirements Management DOORS Next, you create server requests for each application. You must approve each request from the target server as well.
Depending on your security scheme, you might be required to create OAuth consumer keys as well.
Project associations
After cross-server communication is established by requesting and approving secure access to application data stores, you can create project associations. This association of project areas enables users to create links from artifacts, such as test cases, requirements, and work items, in one project area to artifacts in another project area.
When projects are associated, they can use services such as requirements, change requests,
defects, or quality tasks for the IBM Engineering Lifecycle Management project that are being linked
to. These services are described by the link types you choose when you are configuring projects.
Information for supported link types is available in the Extending product function
topics in
your IBM Engineering Lifecycle Management product help.