Creating the EAR on WebLogic

About this task

Note: Set the number of file descriptors (ulimit -n) for the user creating the EAR to be greater than 8192.

During the ear build, when JAX-WS webservice creation occurs, Sterling Order Management System Software will look for customer extensions and use them if they exist. If they do not exist, default handler XML and handler classes will be built into the ear and used. Sterling Order Management System Software provides one single set of default handlers that will get used against all beans that are deployed and for which customers have not provided extensions. Customer extensions can be provided on a per JAX-WS bean basis.

Enterprise Archives are built using an ANT (buildEAR.xml) that accepts the following targets:

Main Target
Description
create-ear
Creates smcfs.ear - The Sterling Order Management System Software application EAR file.

Procedure

To create an application EAR file, run the following command from the <INSTALL_DIR>/bin directory:
UNIXLINUX

./buildear.sh -Dappserver=weblogic -Dwarfiles=<application wars>
 -Dearfile=smcfs.ear -Dasyncejb=true create-ear
Windows

.\buildear.cmd -Dappserver=weblogic -Dwarfiles=<application wars>
 -Dearfile=smcfs.ear -Dasyncejb=true create-ear
Note:
  • Sterling Order Management System Software supports the RPC encoded or document literal style and usage of invocation for Web services. When choosing style and usage for WebLogic, the Web service uses the document literal only.
  • If you are using Oracle JDK or Open JDK, create the file install_dir/jdk/jre/lib/stax.properties (or equivalent directory if the sandbox.cfg variable JAVA_HOME points to an external directory). Add the following line in stax.properties:
    javax.xml.stream.XMLInputFactory=com.sun.xml.internal.stream.XMLInputFactoryImpl
    Otherwise, you may see ear build failures with JAX-WS webservices.

Running this command creates the smcfs.ear file in the <INSTALL_DIR>/external_deployments/ directory. Depending on the application wars provided in the command while creating the EAR, appropriate war files are included in the smcfs.ear. Examples:

  • smcfs.war - the Sterling Order Management System Software or Sterling Configure, Price, Quote war file.
  • sma.war - the System Management Administrator application war file.
  • sbc.war - the Sterling Business Center application war file.

Notes:

You can add the following options to the end of the above buildear commands:

  • -Dnowebservice=true if you do not want to use Web services.
  • -Ddevmode=true if you want to use the HTTP API Tester in the development environment.
    Note: If the -Ddevmode is set to true while building the EAR, a few struts developer notification warnings may be logged while using the application. You can either ignore those warnings or raise the logging level to error for those packages.
  • -Dnodocear=true if you want to skip the documentation build. Use this option when building the ear for a production environment. 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.
  • -Dsupport.multi.war=true if you want to copy all the UI jars to <WAR>/WEB-INF/lib. The UI jars will be copied based on the entry in DCL.xml.
  • -Dapp.name=<application_name> if you want to override the default value of "Sterling applications" and build some other application, particularly in an auto-deploy scenario.
  • -Dasyncejb=true - Use this option only if you are implementing the Parallel Processing functionality.
Note:

Results

For more information about WebLogic, see the documentation provided by the vendor.