Package J2EE assets for an entire module

When you package J2EE assets for an entire module, the steps are different, depending on whether or not your module will be deployed to a target WebSphere Commerce Server that uses the same, or different, type of database as your 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 your development environment, follow the instructions contained in Packaging your 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 your development environment, follow the instructions contained in Packaging your module with EJB backend conversion.

Web modules

If you are deploying customizations to the Management Center, package your changes as a Web module by following the instructions contained in Package Management Center files for deployment.

Related tasks

Deploy J2EE assets for an entire module
Package custom J2EE assets