Wednesday, July 16, 2008

Project Interchange

Project Interchange File How to

Websphere Integration Developer v612

Contact us...

Table of Contents

How to export a project using Project Interchange
How to import a project using Project Interchange

How to export a project using Project Interchange

Related links Exporting modules as project interchange files

Select the Project

In the Business integration view, right-click the project/s you want to export and select Export...

Select an export destination

Select Other/Project Interchange as the export destination and click Next.

Select project/s

Select the project/s you want to export.

Click Browse to specify a location.

Note:

Notice that you are only exporting the source file (i.e OrderProcessing). The ...App and ...EJB will be re-generated when you import the project. This will help prevent version incompatibilities.

Export to Zip file

Enter a name for the exported project in the File name box.

Click Save.

Export the project/s

Click Finish to export the project/s.

How to import a project using Project Interchange

Related links

Importing projects from WebSphere Business Modeler

Import a project/s

Right-click inside the Business Integration view and select Import...

Select an import source

Select Project Interchange and click Next >

Find the zip file

Click Browse to find the Project Interchange file or enter the location of the file.

Select the file

Select the Project Interchange file (i.e p5 orderprocessingcompleteprocess.zip) you want to import and click Open.

Select project/s

Select one or more projects you want to import (i.e OrderProcessing). You can also select them all (Select All) if there is more than one project.

Click Finish to complete the import.

Project imported

The Project Interchange file (p5 orderprocessingcompletedprocess) is imported into the project.

Note:

There are errors!!

This could be due to the fact that the file we imported was created from an earlier version of Websphere Integration Developer (i.e 6.0). We are currently using version 6.1.2.

See Migration How to on how to fix this problem.

No comments: