Understanding Object Configuration Manager

The Object Configuration Manager (OCM) program (P986110) has the ability to distribute logic and data provides for flexibility in determining your own partitioning schemes. It also provides independence in using only the data and logic objects that you need and allows for growth within your enterprise systems. You can later add more databases to store data or machines to process logic. You would need to define the data sources for each and create appropriate OCM mappings.

The OCM stores information in tables that tell the software where data resides and where processing occurs. At runtime, the software looks to the OCM to determine these data and processing locations.

OCM configures distributed processing and data dynamically without any programming. Depending on the environment and the user, the OCM points to the correct location for:

• Data

• Batch processes

• Business functions

• Events

In EnterpriseOne, business data objects (tables) map to database data sources. Batch processes and business functions map to machine data sources. Events map to datasources.

You always need at least two OCM tables:

One table for all workstations.

Store this table in a centralized system data source. Normally, a central data server stores the system data source. If the central server is unavailable, EnterpriseOne looks to the workstation's jde.ini file for a secondary location.

One table for each logic server.

Servers process differently than workstations; for example, the server map data source for each logic server stores separate OCM tables for server processing.