Deploying the enterprise archive (EAR) using the WebSphere Admin Console
About this task
The doc ear does not contain end-user documentation, such as context-sensitive help files. It contains only development-related documentation, including API Javadoc, ERDs, and XSDs and should not be deployed to a production server. Deploy the doc ear with the application ear on test or development environments. Do not deploy the doc ear on a production environment.
Sterling Call Center provides support for deploying Multiple EARs (Enterprise Archives) on a single application server. On the same application server, you can:
- Deploy different customizations of the same or different versions of the application, or
- Deploy different versions of the same application
Multiple EARs or context roots require additional memory for the application server JVM. Testing has shown that the deployment of a second IBM® EAR file requires 2.5 - 3.5 times the memory of a single EAR. Supporting two deployments may require up to 2.5 GB of heap space and 1.2 GB of permanent space.
<WAS_HOME>/deploytool/itp/ejbdeploy.shto avoid out-of-memory issues while deploying:
To deploy the EAR on WebSphere:
- From the WebSphere Administrative Console menu in the left pane, select Applications > Application Types > WebSphere enterprise applications.
- The right pane is populated with a list of applications that are deployed. Click the Install button.
- Choose Local File System or Remote File System.
Click the corresponding Browse button and browse to the Enterprise
Archive such as
smcfs.earyou want to deploy. Click Next.
- Choose Fast Path option. Click Next.
- Check Deploy enterprise beans, and change
the application name as follows:
- Ensure that there are no spaces in the application name; otherwise, the WebSphere-provided jsp compiler script will fail.
- Ensure that the application name is different from
that of the documentation EAR; otherwise, accepting the default makes
both names the same.
If you are using Web services, check Deploy WebServices.Note: If you want to precompile the JSP files during deployment, check Precompile JavaServer Pages files.
- The Map Modules to Servers screen displays.
Select the checkbox next to each desired module (at least two entries,
smcfs.war, should be present). Click the Cluster/Server in the Cluster and Server pane. Click Apply. The screen refreshes and the server field is updated with the chosen value. Click Next.
- Accept the default JNDI names for the EJB modules on the Provide JNDI Names for Beans screen. Click Next.
- On the Map Virtual Hosts for Web Modules screen, select your web module and its correct virtual host. Choose Next.
- The Ensure all Unprotected 2.x Methods screen displays. Click Next.
- The Provide Options to perform the WebServices Deployment screen displays. Leave them as is and click Next.
- On the summary page, choose Finish.
- If you are deploying the Sterling Field Sales application,
make the following additional changes in the WebSphere Administration Console:
- For each one of the application servers where you deploy the Sterling Call Center application, verify that the ClassLoader Policy is set to Multiple.
- Navigate to Enterprise Applications > Application Name > Class Loader. Set the Class Loader Order to "Classes loaded with local class loader first (parent last)."
- Navigate to Enterprise Applications > Application Name > Class Loader. Set the WAR Class Loader Policy to "Class Loader for each WAR file in application."