Components must be archived as part of the package where they are installed. You can import two archive formats:
EAServer JAR This format, while proprietary to EAServer, supports all component types. Also, unlike the EJB-JAR format, all component property settings are preserved in the archive.
EJB JAR This format provides portability between J2EE and EJB servers from different vendors. Only EJB components are archived in this format; components of other types are ignored when you create the archive. See Chapter 2, “Deploying and Configuring EJB Components,” in the EAServer Enterprise JavaBeans User’s Guide.
You cannot deploy EJB components and components of other types (such as PowerBuilder or CORBA) in the same package.
Deploying packages between servers using an export
configuration
Start the Management Console and connect to the test server.
Create an export configuration that includes the files you want to import to your production server—see Chapter 7, “Exporting Server Modules.”
When you create the export configuration, select the following options on the Synchronization tab:
Build Before Synchronizing
Synchronize Server or Synchronize Cluster
Restart Servers After Synchronizing
By default, all the files that are required for an entity are included in the export configuration. You can include other files, such as project descriptions, client applets, and HTML pages, when you configure the export configuration.
Start the Management Console on the production server host, and connect to the production server.
If you have copied a package between host machines that have different architectures, recompile the components to run on the new architecture.
