Administer > Deploy > Deploying customized assets > Customized WebSphere Commerce Enterprise Application (EAR) assets > Package custom Java EE assets
Package J2EE assets for an entire module
When you package J2EE assets for an entire module, the steps are different, depending on whether the module will be deployed to a target WebSphere Commerce Server that uses the same, or different, type of database as the development environment.
There are different types of modules in J2EE:
- EJB beans
- If you are creating an EJB JAR file that is being deployed to a target WebSphere Commerce Server that uses the same type of database as the development environment, follow the instructions contained in Package the module without EJB backend conversion.
- If you are creating an EJB JAR file that is being deployed to target WebSphere Commerce Server that uses a different type of database from the development environment, follow the instructions contained in Package the module with EJB backend conversion.
- Web modules
- If you are deploying customizations to the Management Center, package the changes as a Web module by following the instructions contained in Package Management Center files for deployment.
- Package the module without EJB backend conversion
This task is applicable if you created an EJB JAR file that is being deployed to a target WebSphere Commerce Server that uses the same type of database as the development environment.
- Package the module with EJB backend conversion
This task is applicable if you created an EJB JAR file that is being deployed to target WebSphere Commerce Server that uses a different type of database from the development environment.
Related tasks
Deploy J2EE assets for an entire module