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 Selling and Fulfillment Suite 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:
./buildear.sh -Dappserver=websphere -Dwarfiles=<application wars> -Dearfile=smcfs.ear -Dasyncejb=true create-ear
.\buildear.cmd -Dappserver=websphere -Dwarfiles=<application wars> -Dearfile=smcfs.ear -Dasyncejb=true create-ear
-D websphere-java2wsdl-style=<rpc|document>
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 wars are included in the smcfs.ear. Examples:
Notes:
You can add the following options to the end of the above buildear commands:
For more information about WebSphere, see the IBM WebSphere information center.
If using WebSphere 8: When building EJB-based web services, if WebSphere 8 and Sterling Warehouse Management System were installed with different users, you may see file permissions errors when running the ear build script. To avoid this, grant permissions to read and write in the Sterling Warehouse Management System directory to the WebSphere 8 installation user.
The build ear process will leave files owned by the other user and you may need to set permissions back.