1. System Administration Guide
  2. Required Data Source Types

Required Data Source Types

You must set up a minimum number of data sources for EnterpriseOne to run. Two of the required data sources define machines that process logic in the enterprise. The other data sources define various databases used in the enterprise.

The installation software provides samples of these required data sources to build your system configuration:

Object Librarian

This data source points to the Object Librarian tables you use for custom development. You should have only one set of Object Librarian tables for each software release, regardless of how many path codes (sets of central objects) you maintain. This data source can reside on any supported platform. The Object Librarian data source is named by base release number; for example, Object Librarian - 910.

System

This data source consists of the technical tables you use to run all EnterpriseOne applications. You must set up one system data source per release.

All workstations use a central set of system tables usually stored on the enterprise server but not on the deployment server. Each logic server requires its own subset of system tables. These server system tables are stored in the server map data source.

When running applications, the system tables provide:

  • Object mappings (location of tables, batch processes, and business functions)

  • Data source definitions

  • EnterpriseOne security

  • Next IDs (used for development only)

Data Dictionary by Release

This data source enables you to store data dictionary master tables in a central location to enable easier administration of changes. Group these master tables together to form a data dictionary database. You should share one data dictionary between the production (such as PD910) and development (such as DV910) path codes. The software allows one data dictionary per path code, but multiple data dictionaries are not recommended or supported. The Data Dictionary data source is named by base release number-for example, Data Dictionary - 910, Data Dictionary - B7334, or Data Dictionary - B732.

Local

This data source defines the EnterpriseOne workstation. Use this data source to override the process location of a batch application that you mapped in the Object Configuration Manager to run on the server.

Business Data

This data source is used when you divide the business data into multiple owners or libraries, which can reside on the same enterprise server or on different ones. Each group of data requires a separate data source. The installation software provides demonstration data that you can copy to supported host databases. The data source name is Business Data - PS910.

Some examples of business data include:

  • Production data (non technical data, such as financial and manufacturing data)

  • Test data

  • Demo data (demonstration or training data)

  • Conference Room Pilot (CRP) data

Distributed Processing

This data source definition contains information that the software uses to identify the logic machine in the network. You need to define each logic machine as a data source.

Server Map

This data source enables you to create for each logic server its own subset of system tables, which are called server map tables. Server map tables are required for each logic server. You must maintain these tables to ensure integrity with the workstation's system tables.

Use Server Map data sources to establish unique object mappings for logic servers. When batch jobs and business functions running on the server request data, they look to the Object Configuration Master and the Data Source Master tables in the server map data source; this is necessary because the mappings are different.

For example, suppose a user logs on to an environment that maps static local data on the workstation, dynamic transaction data to the server, and the master business functions and batch processes to the server. The user enters a sales order and clicks OK to enter the order, which runs the Sales Order Entry master business function on the server. It does not make sense for the master business function to go back to the workstation to retrieve user defined codes and tax information; therefore, the server map Object Configuration Manager table maps all data to the appropriate server data source.

These tables in the Server Map database are unique to a server's perspective of processing:

  • Object Configuration Master (F986101): Provides logic objects processing on a server request data and perhaps other logic objects. When these requests are made to EnterpriseOne running on a server, Object Configuration Master must be accessed to find the correct mappings for the data and logic objects. Servers might have different mapping requirements than workstations.

    For example, you should map all user defined codes locally to the workstation for performance during interactive processing. Server processing would require you to map these files locally to a server database to enhance server processing performance.

  • Job Control Status Master (F986110): Records information about batch jobs launched on a server.

  • Job Number Master File (F986111): Records next numbers for batch jobs launched on a server.

Central Objects

This data source points to the source objects (central objects specifications), as well as the User Overrides table (F98950). Central Objects data sources are databases.

If you have multiple path codes, each must have a separate Central Objects data source. Developers check objects out of a Central Objects data source for modification. When the developer checks in the objects, the system copies the objects from the developer's workstation to the relational database tables in the Central Objects data source. You must set up one Central Objects data source for every path code needed in the configuration, for example, Central Objects - PD910 or Central Objects - DV910.

You must have a Central Objects data source for:

  • Pristine objects

  • Production objects

  • Development objects

You connect each Central Objects data source to a path code used by the environments that you created for the configuration.

Control Table

This data source consists of user defined codes, menus, and next numbers.

Versions

This data source corresponds to the path code, as in Versions - PD910. It stores versions and processing option information. It includes these tables:

  • Versions List (F983051)

  • Processing Option Text (F98306)

Alternate Data Source (Release 9.2.1.2)

EnterpriseOne Search execution can be performed on an alternate data source. An alternate data source is a source other than the primary data source that is used for EnterpriseOne operations. If you have a data source with a similar data schema, you can define the search execution to access it instead.

The alternate data source must contain the same data structure, including column names and data types, as the primary data source. On the search result window, the system displays the data retrieved directly from alternate data sources.

See Defining an Alternate Data Source for EnterpriseOne Search (Release 9.2.1.2) for more information.