IBM BPM, V8.0.1, All platforms > Installing, deploying, and undeploying applications in the runtime environment > Deploying service modules
Export modules for deployment or development
In IBM Integration Designer, you can export modules as EAR files for server deployment or as serviceDeploy files for command-line server deployment. You can also export modules as project interchange files so that you can share projects for development purposes. If you are exporting modules for adapter deployment, you might need to configure dependency libraries for the adapter on the server.
The following topics explain how to export modules for deployment or development and how to configure dependency libraries for adapters that have been deployed on a server.
If you want to author artifacts in IBM Integration Designer and deploy them to an IBM BPM runtime environment, the major versions of the two products must match.
- Export modules as EAR files
In IBM Integration Designer, you can export modules and libraries as EAR files and then deploy them on Process Server or WebSphere Enterprise Service Bus (mediation modules only) using the administrative console or command-line tools.- Export modules and libraries as serviceDeploy files
In IBM Integration Designer, you can export modules and libraries as compressed files and then use the serviceDeploy command of Process Server or WebSphere Enterprise Service Bus (mediation modules only) to build and deploy them as EAR files.- Export modules and libraries as project interchange files
In IBM Integration Designer, you can export modules and libraries as project interchange files. This enables you to share modules and their projects for development work.- Configure dependency libraries for adapters
The deployed adapter running in the server requires the same dependency libraries as it does in IBM Integration Designer to process requests. The method for adding these library files depends on the mode of the adapter deployment: deployed as a stand-alone adapter; or embedded in the EAR file.