Exporting from WebSphere Integration Developer

If you want to export an integration module (module or mediation module) from WebSphere Integration Developer for use elsewhere you have a number of options available which can be accessed by right clicking on the integration module and selecting Export>Integration Module. The option you should choose depends on what you are trying to do. To find out more about which is the best option for you, read on.

Direct installation onto WebSphere Process Server/WebSphere ESB – Select EAR files for server deployment

i.e. The integration module you have been developing in WebSphere Integration Developer is complete and you now need to export it as a unit (in this case an EAR file as the implementation of an integration module is a J2EE application) that can be installed directly to your WebSphere Process Server/WebSphere ESB environment.

Analagous to: Exporting a Java class file – the EAR contains the built code and deployment descriptors necessary for the application to run – but no source will be included.
Building and installation onto WebSphere Process Server/WebSphere ESB – Select Command line service deployment

i.e. The integration module you have been developing in WebSphere Integration Developer is complete and you now want to export the “source” so that the module can be built (and installed) as part of a scripted build process.

This will produce a ZIP file which the serviceDeploy command can then be run on to turn this into a deployable unit.

Analagous to: Exporting a Java source file that can be built as part of the build process.

Sharing with other developers – Select Project Interchange for sharing modules between workspace

i.e. You are developing an integration module inside WebSphere Integration Developer and want to share your work so far with another developer who is going to do some work on the integration module.

Analagous to: Exporting a Java file complete with all your dependent projects, classpath settings, etc.

Important Note: If you want to export your module as a project interchange file there are a couple of points to consider:

– If you have not modified the generated code for your integration module (the majority of cases) you should use the Project Interchange option above as this only exports the integration module “source” project and dependent projects (such as libraries). The integration module implementation projects will be built when this is imported into WebSphere Integration Developer.

– If you have modified the generated code for your integration module (you may have done this to tweak deployment descriptors if you are doing something complex with WS-Security for example) then you should right click on the integration module and choose Export>Project Interchange as this will give you the option to export the integration module implementation projects.

Advertisements

One Response to Exporting from WebSphere Integration Developer

  1. Amir Bahmanyari says:

    WID allows you to export an ear file one at a time.
    Is there any way to export ALL ears from WID (6.1.2) to a specific local directory?
    Thanks
    Amir-

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: