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 EAR file.
For each EJB-JAR file in the EAR, an entity called “ejbjar-” followed by the JAR name; for example, if the application contains an EJB-JAR called “helloworld.jar,” the entity name is “ejbjar-helloworld.”
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.
For each WAR file in the EAR, a Web application named “webapp-” followed by the WAR name; for example, if the EAR contains a WAR called “samplewebapp.war,” the Web application name is “webapp-samplewebapp.”
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 an EAR file does not contain EAServer XML configuration files, you may need to configure the following component or Web application properties 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 are configured by the Deploy wizard.
