The EAR package is necessary for deployment. You will configure
the EAR to deploy Sterling Warehouse Management System using the smcfs.ear file.
Note: Sterling Warehouse Management System supports overriding the context root during EAR
deployment.
When deploying Sterling Warehouse Management System on WebLogic, use the smcfs.ear file,
which may contain:
- smcfs.war -
Web module that contains all of the Sterling Warehouse Management System JSPs and other Web application components.
- sma.war -
Web module that contains the System Management Administrator application
components.
- sbc.war -
Web module that contains all of the Sterling Warehouse Management System Web application components.
- yantrawebservices.war -
Web module that contains all of the Sterling Warehouse Management System Web services interface classes.
- smcfsejb.jar -
The EJB module that contains all the Sterling Warehouse Management System EJBs. You can pass an alternate earfile name
by using the –Dearfile option to the buildear.sh script.
Doing this will result in a name change for the ejb jar file. For
example, if you specify an EAR file as xyz.ear, the
ejb jar becomes xyzejb.jar.
- smcfswsbe.jar - The
backend Web services jar file. You get this file if you expose Web
services. You can pass an alternate earfile name to the ear build
script. Doing this will result in a name change for the Web services
backend jar file. For example, if you specify an EAR file as xyz.ear,
the Web service backend jar becomes xyzwsbe.jar.
- Jars that contain backend business logic.
- Jars that contain third-party libraries accessed
by backend logic.
Each of the third-party JAR files are left as is
and in the manifest of the application each file is indicated as a
dependency. For example, log4j files are represented separately as log4j-1.2.15.jar with
a dependency in the application.