What is created during import

When you import an EAServer JAR, the Deploy wizard creates an application identical to the original.

When you import an EAR, the Deploy wizard creates:

An application with the same name as the display name in the EAR file’s XML descriptor. If there is no display name, the new application has the same name as the EAR file.

For each EJB-JAR file in the EAR, a package with the same name as the EJB-JAR display name, or the name of the EJB-JAR file if there is no display name.

For each bean in an EJB-JAR file, an EJB component with the same name as the ejb-name element in the EJB-JAR deployment descriptor.

Home names for imported EJB components When importing from EAR or EJB-JAR files, EAServer sets an imported bean’s home name to the EAServer default, package/component, where package is the EAServer Manager package name, and component is the EAServer Manager component name.

For each WAR file in the EAR, a Web application with the same name as the display name in the WAR file’s XML descriptor. If there is no display name, the new Web application has the same name as the WAR file.

For each servlet defined in a WAR file, a Web application component with the same name as the servlet-name element in the Web application deployment descriptor.

If the EAR file did not contain EAServer XML configuration files, you may need to configure the following settings in the Component or Web Application Properties dialog boxes before running EJBs, servlets, or JSPs:

Role mappings
Resource references
EJB references (to components that are not installed with the EAR file)
Environment properties
Resource environment references

Other settings have been configured by the Deploy wizard.

Use the status dialog as a to-do list In the deployment status dialog box, EAServer Manager displays warnings for each setting that requires further attention before you run the application. You can copy and paste this text to a text editor to use as a to-do list.