Creating the EAR on WebLogic

Create the EAR file for deployment of Sterling Warehouse Management System 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. If you are deploying on HP set ulimit unlimited for the user creating the EAR.

During the ear build, when JAX-WS webservice creation occurs, Sterling Warehouse Management System 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 Warehouse Management System 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 Selling and Fulfillment Foundation application EAR file.

Procedure

To create an application EAR file, run the following command from the <INSTALL_DIR>/bin directory:
./buildear.sh -Dappserver=weblogic -Dwarfiles=<application wars>
 -Dearfile=smcfs.ear -Dasyncejb=true create-ear
.\buildear.cmd -Dappserver=weblogic -Dwarfiles=<application wars>
 -Dearfile=smcfs.ear -Dasyncejb=true create-ear
Note: Sterling Warehouse Management System 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.

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:

Notes:

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

Note: If exceptions are thrown regarding application server startup or EAR deployment, this may indicate failure and require fixing and redeployment. Consult the Troubleshooting and Support topics.

Results

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