Multitiered configuration file locations
All of the configuration files that are provided for building the multitiered architecture are located in the $NCHOME/omnibus/extensions/multitier directory.
The gateway subdirectory holds the following
customized map definition files (.map), properties
files (.props), and table replication definition
files (.tblrep.def), which can be used to configure
the ObjectServer Gateways in the collection, aggregation, and display
layers:
- A_TO_D_GATE.map
- A_TO_D_GATE.tblrep.def
- A_TO_D_GATE_1.props
- A_TO_D_GATE_2.props
- AGG_GATE.map
- AGG_GATE.props
- AGG_GATE.tblrep.def
- C_TO_A_GATE.map
- C_TO_A_GATE_B_1.props
- C_TO_A_GATE_B_1.tblrep.def
- C_TO_A_GATE_P_1.props
- C_TO_A_GATE_P_1.tblrep.def
These gateway files are preconfigured with the required settings, and should be used as provided. The gateway files also require compliance with the naming conventions for ObjectServers and ObjectServer Gateways in the multitiered architecture.
The objectserver subdirectory holds the following
customized SQL import files (.sql), which you
can apply to the ObjectServers in the collection, aggregation, and
display layers, in order to update the database schema with the required
multitiered configuration:
- aggregation.sql
- aggregation_rollback.sql
- collection.sql
- collection_rollback.sql
- display.sql
- display_rollback.sql
The SQL files provide automations that require compliance with
the naming conventions, and typically:
- Add relevant columns to the database tables.
- Create the automations that control the behavior of the ObjectServers, ObjectServer Gateways, and clients, and the flow of events across these components.
- Enable and disable triggers, as appropriate for the ObjectServers.
- Assign permissions to the triggers.
- Create conversions.
- Roll back the applied schema changes, if required.
All of the files are provided in read-only format. When setting up your multitiered environment, you are required to run commands that reference some of the files, or to make copies of some files for editing.
Use these files as directed in the relevant procedures.