You can create an EJB-JAR file that contains the Java classes and deployment descriptors for the EJB components installed in an EAServer package. The JAR file can be deployed to another EAServer installation or any EJB compatible server.
You can export EJB-JAR files in two formats:
EJB JAR Use this format for exporting EJB 2.0 or 1.1 components. Components in the package of other types are not included in the JAR file. The file can be deployed to any EJB 2.0 server.
EJB 1.0 JAR Use this format for exporting EJB 1.0 components. Components in the package of other types are not included in the JAR file. The file can be deployed to any EJB 1.0 server. Appendix A, “Using EJB 1.0 JAR Support,” describes this option.
Use synchronization for deploying beans
between servers
The EAServer synchronization feature can also be used to deploy
components from one EAServer installation to another. Synchronization
is simpler than importing and exporting JAR files, but the source
server must be able to connect to the target server. If you use
synchronization, you will avoid the need to reconfigure JNDI resource
references on the target server for EJB 2.0 or 1.1 components.
Highlight the EAServer package to export and choose File | Export, then choose EJB 1.0 JAR or EJB JAR.
Enter the path and file name for the new JAR file and click Next.
Optionally deselect the Export with EAServer XML Configuration File option if you do not want the archive to include an EAServer XML configuration file.
EAServer Manager creates the JAR file, displaying status messages in the Export wizard.
Exporting an EJB-JAR file