Deploying the enterprise archive (EAR) on JBoss
The doc ear does not contain end-user documentation, such as context-sensitive help files. It contains only development-related documentation, including the 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
- 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.
During installation, you can use JVM-specific arguments in your Sandbox.cfg file, such as ADDITIONAL_ANT_JAVA_TASK_ARGS and ADDITIONAL_ANT_COMPILER_TASK_ARGS, to avoid out-of-memory errors.
Deploy your newly created smcfs.ear
file as described in your
application server documentation, using the deployEARJboss.xml
ant script.
- Stop the application server.
- Copy the ear file to the deployment directory on the application server (the JBoss installation directory is <servername>/deploy).
- Restart the application server.
- Log in.
To verify the Sterling Call Center
- Restart your application server.
- Start Internet Explorer.
- To access the Application Console:
- Access
http://<hostname>:<port>/smcfs/console/login.jsp
. - When prompted, enter your Login ID and Password.
- Access
- To access Sterling Business Center:
- Access the Sterling Business Center login page by setting the enterprise appropriately.
- When prompted, enter your Login ID and Password.
java.lang.NoClassDefFoundError: org/omg/CORBA
error, see
Troubleshooting:
"java.lang.NoClassDefFoundError: org/omg/CORBA" error encountered in JBoss EAP 7.2
version