Oracle® Retail POS Suite Implementation Guide, Volume 2 – Extension Solutions Release 14.1 E54476-02 |
|
![]() Previous |
![]() Next |
Much of this guide deals with the structure and function of Oracle Retail Back Office code, and how you can modify and extend it to serve the needs of your organization.
The source code is downloadable in a zip file.
This zip file contain the following:
File Name | Comments |
---|---|
cmnotes.txt | Configuration Management notes. Describe how to set up and build the source. |
<application>-<release_number>_source.zip | The application source, where <application> is:
|
ORSSS-<release_number>_data_model.zip | Data Model (database schema) documentation. |
README.html | Release Notes. |
Using pkzip, WinZip or similar utilities, you can extract <application>-<release_number> onto your local hard disk. Choose the option to preserve the directory structure when you extract. All the source files are placed into the following directory:
<Path to disk root>/<application>-<release_number>_source
From this point on, this directory is referred to as:
<BO_SRC_ROOT>
for Back Office.
<CO_SRC_ROOT>
for Central Office.
<POS_SRC_ROOT>
for Point-of-Service.
<RM_SRC_ROOT>
for Returns Management.
The following is the first-level directory structure under the directory:
Directory | Comments |
---|---|
applications | Contains application-specific code for applications. |
build | Files used to compile, assemble and run functional tests. |
clientinterfaces | Interface definitions, between different code modules. |
commerceservices | Commerce Services code. |
DIMP | Includes XSD and XML files used to map data import. |
installer | Files used by the installer. |
modules | A collection of various code modules some of which are the foundation for Commerce Services. The utility module contains SQL files used for database creation and pre-loading. |
thirdparty | Executable (mostly .jar files) from third-party providers. |
webapp | Web-based user interface code. Also contains the Application Managers. |
In subsequent chapters, all path names of a code file are made relative to one of these directories. You must add the directory name (for example, <source_directory>) to the file path to get its actual location on disk.