In WebSphere® Integration
Developer, you can export modules as zip files and then use the serviceDeploy
command of WebSphere Process
Server or WebSphere Enterprise Service Bus (mediation modules only) to build
and deploy them as EAR files.
Before you export any modules as zip files for deployment using the
serviceDeploy command, you should ensure that you have reviewed the information
about dependencies and packaging in the topic "Deployment."
To export modules as serviceDeploy files:
- From the File menu, select Export.
The Select page of the Export wizard opens.
- In the Select page, select Integration module,
as shown in the figure below:

- Click Next. The Integration Module Export
page opens.
- In the Select modules to export list box,
select the check box beside the name of each module that you want to export.
- Select the Command line service deployment radio
button, as shown in the following figure:

- Click Next. The Export for Command Line
Deployment page opens, as shown in the following figure:

- In the Target file field, type the path
and name of the zip file. Alternatively, you can click Browse to
navigate the file system and select the file.
- If you have changed any of your generated J2EE projects, select
the Include generated J2EE projects from workspace check
box. The names of the J2EE projects will be displayed in the Additional
projects list box. (By default, all dependencies are automatically
included in the serviceDeploy zip file. These dependencies are required to
successfully build an EAR file from the zip file and deploy it using the serviceDeploy
command-line tool.)
- Click Finish to export the selected modules
in a zip file for command-line service deployment.