Sterling Order Management Software requires a tiered
environment, using a combination of application server, Web server, and database server software.
After the environment is set up, you install the base software, which is Sterling Order Management Software, as a required
first step. Depending on the licensing agreement, you may also install other applications on top of
the base layer.
Typically, each implementation requires customization. The base software layer provides
access to the backend database tables, transactions, and APIs that you can customize. You
can also customize the applications running on top of the base layer. A customization
project requires installing the product and working in three environments:
- Individual development environment, a working environment in which developers create
- Staging environment, a testing environment that integrates all changes and that
usually mirrors the production environment
- Production environment, where final, tested changes are deployed
After all the components you need are installed in an installation directory, you
build an EAR file and deploy this to your development environment. You create your
customizations in the development environment. When development work is ready, you build
an EAR file and deploy this to your staging environment. When testing is complete, you
build an EAR file and deploy this to your production environment.
Whether you install your development, test, or production environment,
you follow the same high-level process:
- Verify stack requirements.
- Install and configure a database, either Db2® or Oracle.
- Install and configure one of the following application servers: IBM® WebSphere®, JBoss, or Oracle WebLogic.
- Install the base software and other components supported by the
- From the installation directory, build an EAR file. Then deploy
the EAR file to the appropriate environment, whether development,
staging, or production.
Before you get started with the installation steps ensure to verify stack requirements. The
stack requirements can be verified by generating the system requirements report by using the Software Product Compatibility Reports
tool. For more information about
generating the software product compatibility reports, see System requirements