Installing and deploying with Sterling Store Engagement (Legacy) optional component
This process presents a suggested order for installing Sterling Order Management System Software with the Sterling Store Engagement (Legacy) optional component.
You may want to bookmark this page so that you can return to it for reference.
- Planning
Planning includes understanding the installation and deployment process, evaluating system requirements, and anticipating security and performance needs.
Planning for installation - Obtaining software and installing prerequisites
Obtain IBM® Installation Manager and Sterling Order Management System Software software. Then set up the application server tier and the database tier.
Obtaining the software and installation prerequisites - Sterling Order Management System Software
You must Install the Sterling Order Management System Software software first, followed by the Sterling Store Engagement (Legacy) software. During this process, you decide which language packs to install, whether to create database tables, and whether to load factory setups.- What is factory setup data and do I have to load it?
- English is installed by default. You can select additional languages now or install them later.
Before you can build the EAR file and deploy it on the server, database tables must exist and must be populated with data.- If you are running an upgrade or have existing database tables that can be used, do not select the options to create tables and to load Sterling Order Management System Software factory setups.
- If you are running a new installation, choose the options to create database tables and to load
Sterling Order Management System Software factory setups.
Alternatively, the DBA at your organization can create database tables and load Sterling Order Management System Software factory setups manually, as long
as this process is completed before proceeding to Step 4.
Creating database tables manually
Manually loading Sterling Order Management System Software database factory setups
Installing Sterling Order Management System Software Professional Edition and Enterprise Edition, and Installing Sterling Store Engagement (Legacy) software
- Post-installation Phases 1 and 2
- Choice A. If you installed factory setups and you are distributing your solution in
English, you must load factory setups for Sterling Store Engagement (Legacy)
Loading the Sterling Store Engagement (Legacy) Factory Setup Data - Choice B. If you installed factory setups and you are distributing your solution in
different languages, you must install the Sterling Order Management System Software language pack, the Sterling Store Engagement (Legacy) language pack, and the localized
factory setups for Sterling Store Engagement (Legacy).
Loading the Sterling Order Management System Software Language Pack
Loading the Sterling Store Engagement (Legacy) Language Pack
Loading the Localized Sterling Store Engagement (Legacy) Factory Setup Data
- Choice A. If you installed factory setups and you are distributing your solution in
English, you must load factory setups for Sterling Store Engagement (Legacy)
- Post-installation Phases 3 and 4
Be sure to complete post-installation tasks in order, configuring installation utilities before run-time utilities.
Using the installation utilities
Configuring the run-time utilities - Post-installation: Building and deploying Sterling Order Management System Software
Before you build and deploy an EAR file on your application server, you can create yourresource.jarfile so that any property file changes are reflected in your system. After this, you can build and deploy the EAR for Sterling Order Management System Software with all the applications you installed on your server.
Creating the resource.jar file
Building and deploying the EAR on the server - Building and deploying Sterling Store Engagement (Legacy)
Building and deploying the Sterling Store Engagement (Legacy)Note: Use Google Chrome for optimal performance of the Sterling Store Engagement (Legacy) application. If you use any other browser, you might not get the maximum benefit of cached retrieval of pre-initialized screen components.