Migration of OSLC integrations

You can migrate an OSLC provider definition and its related interactions from one instance of your product to another. For example, you might set up an OSLC integration in a development or test environment. After you establish that the integration is working properly, you can migrate it to a production environment.

Migration of OSLC integrations takes advantage of existing Migration Manager application features and is largely done in the Migration Manager application. The OSLC Providers application has an action to generate the package that is to be migrated.

Before you run the Migrate OSLC Provider action, you do preparatory work in the Migration Manager application. An OSLCPROVIDER package definition is provided in the Migration Manager application. For the OSLCPROVIDER package definition, you specify a target database or file destination for the package that you generate in the OSLC Providers application.

You use the Migrate OSLC Provider action in the OSLC Providers application to generate the package that you then manage in the Migration Manager application. The package contains the OSLC provider record, the associated interactions, and the associated user interface changes in the integrated consumer application or applications.

After you run the Migrate OSLC Provider action, a system message is displayed. The final line of the log message shows the name of the package. The package is listed on the Package tab of the OSLCPROVIDER package definition in the Migration Manager application in the source environment.

In the target environment, you use the Migration Manager application to import and deploy the package.

If you use a custom Java™ mapping file in your OSLC integration, the custom Java mapping file does not get included in the package. You must manually move the custom mapping file and the corresponding class file to the target environment, or manually add them to the package.

The Migrate OSLC Provider action generates a package for the current OSLC provider record only. If you have multiple OSLC provider records, you must migrate each one individually.

The Migration Manager does not support the migration of interaction groups. To migrate the objects in an interaction group, you can build a new object structure that uses the following objects:

OSLCINTGROUP
	OSLCGRPAPPS
		OSLCGRPAPPMENU
	OSLCGRPMEMBERS	

You must include the new object structure in the OSLCPROVIDER migration package.