A Offline Mediation Controller Directory Structure and Contents
Learn about the Oracle Communications Offline Mediation Controller directory structure and contents.
Topics in this document:
Directory Structure and Contents
The main install directory for the system contains several sub-directories. Each contains specific types of files for various purposes. The following lists all if the directories used by the system:
-
3rdparty_jars: Contains all custom JAR files.
-
bin: Contains script files used to run Offline Mediation Controller.
- cartridges: Contains all cartridge pack JAR files.
-
config: Contains the nodes' configuration data. This data is input through the configuration GUI.
-
customization: Contains the customized classes, rules files, and templates.
-
datadict: Holds the dictionary of attributes for the entire system. This dictionary is not referenced in real-time by the system. It is a static reference.
-
datafiles
-
input: Contains the input directories for all nodes. Collection cartridges may not make use of these input directories.
-
jre:
-
licenses
-
log
-
output: Contains the output directories for all nodes. Distribution cartridges may not make use of these output directories.
-
rules: Contains the NPL files, which are also referred to as rule files. The sub-directories are organized by node type. For example, CC, DC, and Processor nodes are referred to as the major node types. Further sub-directories are organized by the minor node types. For example “FlatFileOI".
-
scratch: Contains the scratch area for all nodes. The scratch is used as a temporary area for all nodes prior to the data being passed to its output.
-
web: Contains compiled NPL files, or class files. The sub-directories here are also organized by node types similar to the rules directories.
-
xslt