2 Understanding Typical Customer Configurations

This chapter contains the following topics:

2.1 Recommended Configurations

EnterpriseOne can be configured in many ways. Examples and recommendations for the setup follow.

You should follow EnterpriseOne-recommended setup and naming standards wherever possible, unless a strong business case exists to support the need to change. Following the typical setup and naming standards enhances the likelihood of success and minimizes confusion when communicating with individuals outside the core project team who are not aware of your specific configuration.

If you want to customize your configuration, you should change only the descriptions with the typical setup, not the names. Upgrades will be easier with fewer manual steps if you use the EnterpriseOne-recommended naming standards.

An environment description is important because the description appears on the environment list of the login screen where the user selects the environment. The environment description should define:

  • Path code

  • Data type (such as production, test, or prototype)

  • Data location

  • Location that batch applications will execute

2.1.1 Basic Environments

You should understand the basic environments of a EnterpriseOne configuration. For each environment, this chapter describes:

  • The path code

  • The purpose

  • The object mappings

For a given release, all environments you receive from EnterpriseOne share common data sources. For example, for EnterpriseOne 8.11, these data sources are common to all environments:

  • System - 910

  • Object Librarian - 910

  • Data Dictionary - 910

2.1.2 Environment-Specific Data Sources for UNIX and Windows

These data sources are specific to a particular UNIX and Windows environment. For each environment, a separate data source must exist.

  • Central objects

  • Versions tables

  • Business data

  • Control tables

  • Local - xxxx

    Where xxxx is the path code for the environment.

2.1.2.1 Production Environment (PD910)

This table explains the data sources for the production environment.

Data Source Environment
Path Code PD910
Central Objects data source Central Objects - PD910
Versions Tables data source Versions - PD910
Business Data data source Business Data - PROD
Next Numbers data source Control Tables - Prod
Tasks/UDCs data source Control Tables - Prod

2.1.2.2 Prototype Environment (PY910)

This table defines the data sources for the prototype environment.

Data Source Environment
Path Code PY910
Central Objects data source Central Objects - PY910
Versions Tables data source Versions - PY910
Business Data data source Business Data - CRP
Next Numbers data source Control Tables - CRP
Tasks/UDCs data source Control Tables - CRP

2.1.2.3 Development Environment (DV910)

This table defines the data sources for the development environment.

Data Source Environment
Path Code DV910
Central Objects data source Central Objects - DV910
Versions Tables data source Versions - DV910
Business Data data source Business Data - TEST
Next Numbers data source Control Tables - Test
Tasks/UDCs data source Control Tables - Test

2.1.2.4 Pristine Environment (PS910)

This table defines the data sources for the pristine environment.

Data Source Environment
Path Code PS910
Central Objects data source Central Objects - PS910
Versions Tables data source Versions - PS910
Business Data data source Business Data - PS910
Next Numbers data source Business Data - PS910
Tasks/UDCs data source System Local - PS910

2.1.2.5 Planner Environment (PSFTPLAN)

This table defines the data sources for the deployment environment.

Data Source Environment
Path Code PLANNER
Central Objects data source Not applicable
Planner Tables data source Planner - 910
Versions Tables data source Versions Local
Business Data data source Business Data Local
Next Numbers data source Control Tables Local
Tasks/UDCs data source Control Tables Local

2.1.2.6 Deployment Environment (DEP910)

This table defines the data sources for the deployment environment.

Data Source Environment
Path Code PLANNER
Central Objects data source Not applicable
Versions Tables data source Versions Local
Business Data data source Business Data Local
Next Numbers data source Control Tables Local
Tasks/UDCs data source Control Tables Local

2.1.3 Remote Environments

Remote environment names are preceded by a 3-character location code followed by a J for Java application server.

For example:

xxxJPD910 indicates a Java application server for the PD910 environment at location xxx.

The path codes and data sources for remote environments are identical to the base environments.

2.1.3.1 PD910 Environment

This table defines the data sources for a remote production environment.

Data Source Environment
Path Code PD910
Purpose PD910 is the live production environment for the end users who will have a tested and released package on their machine. Batch applications run on the server. Eventually, more than one production environment might be established for different types of distributed data, logic, and modes of processing.

2.1.3.2 PD910 Object Mappings

This table explains the object mappings for a production environment.

Mapping Explanation
Business Data - PROD The default object mapping. Tables that are not specifically mapped by other data sources use this data source as their default mapping. This mapping includes the F00165 - Media Objects Storage table.
Central Objects - PD910 Maps to the central object tables, including F98950 - User Overrides.
Control Tables - Prod Maps to the next number tables.
Data Dictionary - 910 Maps to the data dictionary tables and the data dictionary media object text in the GT92002 - Data Dictionary - Glossary Information data structure.
Logic Data Source Maps to the machine on which batch applications are run.
Object Librarian - 910 Maps to the object librarian tables and the object librarian media object text in these data structures:
  • GT9860A - Object Librarian Generic Text Structure

  • GT9862A - Business Function Notes

  • GT98DSA - Data Structure Notes - Structure and Item

  • GT98DSB - Data Structure Notes - Structure and Item

  • GT98TMPL - Media Object Templates

Local - PD910 Maps to the user defined code tables.
System - 910 Maps to the system tables.
Versions - PD910 Maps to the version tables, including:
  • F983051 - Versions List

  • F98306 - Processing Option Text


2.1.3.3 PY910 Environment

This table defines the data sources for a remote prototype environment.

Data Source Environment
Path Code PY910
Purpose PY910, the prototype environment, is the staging environment for production. Constants tables and master tables (such as company constants, fiscal date patterns, and item master) are populated with customer data during the prototype process.

Copy the tables to the production environment before you go live. After you run the Installation Workbench, no business data exists until you enter it. When appropriate, you should refresh the test data from PD910, which represents the production data.


2.1.3.4 PY910 Object Mappings

This table explains the object mappings for a prototype environment.

Mapping Explanation
Business Data - CRP The default object mapping. Tables that are not specifically mapped by other data sources will use this data source as their default mapping. This mapping includes the F00165 - Media Objects Storage table
Central Objects - PY910 Maps to the central object tables, including F98950 - User Overrides.
Control Tables - CRP Maps to the next number tables.
Data Dictionary - 910 Maps to the data dictionary tables and the data dictionary media object text in the GT92002 - Data Dictionary - Glossary Information data structure.
Logic Data Source Maps to the machine on which batch applications are run.
Object Librarian - 910 Maps to the object librarian tables and the object librarian media object text in these data structures:
  • GT9860A - Object Librarian Generic Text Structure

  • GT9862A - Business Function Notes

  • GT98DSA - Data Structure Notes - Structure and Item

  • GT98DSB - Data Structure Notes - Structure and Item

  • GT98TMPL - Media Object Templates

Local - PY910 Maps to the user defined code tables.
System - 910 Maps to the system tables.
Versions - PY910 Maps to the version tables including:
  • F983051 - Versions List

  • F98306 - Processing Option Text


2.1.3.5 DV910 Environment

This table defines the data sources for a remote development environment.

Data Source Environment
Path Code DV910
Purpose DV910, the development environment, is the testing environment for development objects. This environment shares the test data that TS910 uses. Developers log in to this environment to modify objects and test them before transferring the changed objects to the PD910 path code.

Once you have transferred objects into PD910, a user can install a recent PRD package that has not been released to end users and log in to either CRP or TST for additional testing.


2.1.3.6 DV910 Object Mappings

This table defines the object mappings for a development environment.

Mapping Explanation
Business Data - PROD The default object mapping. Tables that are not specifically mapped by other data sources use this data source as their default mapping. This mapping includes the F00165 - Media Objects Storage table
Central Objects - DV910 Maps to the central object tables, including the F98950 - User Overrides table.
Control Tables - Production Maps to the next number tables.
Data Dictionary - 910 Maps to the data dictionary tables and to the data dictionary media object text in the GT92002 - Data Dictionary - Glossary Information data structures.
Logic Data Source Maps to the machine on which batch applications are run.
Object Librarian - 910 Maps to the object librarian tables and to the object librarian media object text in these data structures:
  • GT9860A - Object Librarian Generic Text Structure

  • GT9862A - Business Function Notes

  • GT98DSA - Data Structure Notes - Structure and Item

  • GT98DSB - Data Structure Notes - Structure and Item

  • GT98TMPL - Media Object Templates

Local - DV910 Maps to the user defined code tables.
System - 910 Maps to the system tables.
Versions - DV910 Maps to the version tables, including;
  • F983051 - Versions List

  • F98306 - Processing Option Text


2.1.3.7 PS910 Environment

This table illustrates the data sources for a remote test environment.

Data Source Environment
Path Code PS910
Purpose Use the PS910 environment to test pristine (unaltered) objects with EnterpriseOne demonstration data. Also use this environment for training classes. You must have this environment to compare modified objects to pristine objects.

When you encounter a software problem that EnterpriseOne Worldwide Customer Support cannot duplicate, they will ask you to log in to the pristine environment to duplicate the problem. Routinely (such as monthly or quarterly), you should refresh the data that this environment uses with the EnterpriseOne demonstration data shipped with the software.


2.1.3.8 PS910 Object Mappings

This table illustrates the object mappings for a test environment.

Mapping Explanation
Business Data - PS910 The default object mapping. Tables that are not specifically mapped by other data sources use this data source as their default mapping. This mapping includes the F00165 - Media Objects Storage table.
Data Dictionary - 910 Maps to the data dictionary tables and to the data dictionary media object text in the GT92002 - Data Dictionary - Glossary Information data structure.
Logic Data Source Maps to the machine on which batch applications are run.
Object Librarian - 910 Maps to the object librarian tables and to the object librarian media object text in these data structures:
  • GT9860A - Object Librarian Generic Text Structure

  • GT9862A - Business Function Notes

  • GT98DSA - Data Structure Notes - Structure and Item

  • GT98DSB - Data Structure Notes - Structure and Item

  • GT98TMPL - Media Object Templates

Local - PS910 Maps to the user defined code tables.
System - 910 Maps to the system tables.
Versions - PS910 Maps to the version tables, including:
  • F983051 - Versions List

  • F98306 - Processing Option Text


2.1.4 Data Sources

If the enterprise server has Oracle Server or Microsoft SQL Server and is a more powerful machine than the deployment server, for performance reasons we recommend that you put all data sources (except the local data sources) on the enterprise server instead of the deployment server.

2.1.4.1 Data Sources

This table illustrates the data sources and their purpose.

Data Source Name Owner and Purpose
Business Data - CRP The owner is CRPDTA.

The library is CRPDTA.

The CRP business data. Before going live, you should copy much of this data to Business Data - PROD.

Business Data - PS910 The owner is PS910DTA.

The library is PS910DTA.

The pristine data shipped with the software.

Business Data - PROD The owner is PRODDTA.

The library is PRODDTA.

The production business data.

Business Data - TEST The owner is TESTDTA.

The library is TESTDTA.

The test data entered during CRP or converted from non-EnterpriseOne systems.

Central Objects - PY910 The owner is PY910.

The library is COPY910.

The central objects data source associated with the PY910 path code. After you create and test the modifications in this path code, transfer them to the PD910 path code.

Central Objects - DV910 The owner is DV910.

The library is CODV910.

The central objects data source associated with the DV910 path code. After you create and test the modifications in this path code, transfer them to the PD910 path code.

Central Objects - PS910 The owner is PS910.

The library is COPS910.

The central objects data source associated with the PS910 path code.

Central Objects - PD910 The owner is PD910.

The library is COPD910.

The central objects data source associated with the PD910 path code. Transfer objects into this data source after you have tested them in path code DV910.

Control Tables - CRP The owner is CRPCTL.

The library is CRPCTL.

The control tables used in the CRP environment.

Control Tables - Prod The owner is PRODCTL.

The library is PRODCTL.

The control tables used in the production environment.

Control Tables - PS910 The owner is PS910CTL.

The library is PS910CTL.

The control tables used in the PS910 path code.

Control Tables - Test The owner is TESTCTL.

The library is TESTCTL.

The control tables used in the test environment.

Data Dictionary - 910 The owner is DD910.

The library is DD910.

The single data dictionary that all environments use.

LOCAL No owner exists.

The data source that defines the local machine to EnterpriseOne. Use it to override reports to the workstation.

machine name No owner exists.

A value that defines the logic host to EnterpriseOne.

Machine Name - Server Map The owner is SVM910.

The server map for the logic server.

Object Librarian - 910 The owner is OL910.

The Object Librarian, which is release specific.

Control Tables Local No owner exists.

The data found in the PSCTL910 MSDE. This data is used only in the planner.

System Local No owner exists.

The data found in the PSSY910 MSDE. This data is used only in the planner.

Data Dictionary Local No owner exists.

The data found in the PSDD910 MSDE. This data is used only in the planner.

Object Librarian Local No owner exists.

The data found in the PSOL910 MSDE. This data is used only in the planner.

Versions Local No owner exists.

The data found in the PSVL910 MSDE. This data is used only in the planner.

Local - PY910 No owner exists.

The source that contains the User Defined Codes (UDCs): Control Tables - CRP.

Local - DV910 No owner exists.

The source that contains the User Defined Codes (UDCs): Control Tables - Test.

Local - PS910 No owner exists.

The source that contains the User Defined Codes (UDCs): Business Data - PS910.

Local - PD910 No owner exists.

The source that contains User Defined Codes (UDCs): Control Tables - Production.

System - 910 The owner is SY910.

The library is SY910.

The single set of system tables that all environments use.

Versions - PY910 The owner is PY910.

The library is COPY910.

The source that contains the versions list and processing option text tables for the PY910 environment.

Versions - DV910 The owner is DV910.

The library is CODV910.

The source that contains the versions list and processing option text tables for the DV910 environment.

Versions - PS910 The owner is PS910.

The library is PS910.

The source that contains the versions list and processing option text tables for the PS910 environment.

Versions - PD910 The owner is PD910.

The owner is COPD910.

The source that contains the versions list and processing option text tables for the PD910 environment.


2.2 Configuration Data

This table summarizes the data, environments, central objects (path codes), and packages needed:

Requirement Explanation
Data You might have these sets of data:
  • Conference Room Pilot (CRP) business data

  • Conference Room Pilot (CRP) control tables

  • Data Dictionary (all environments share)

  • EnterpriseOne pristine data

  • Production business data

  • Production control tables (used by the PD910 environment)

  • Object Librarian (all environments share)

  • System (technical data all environments share)

  • Test business data

  • Test control tables (used by TS910 and DV910 environments)

  • Versions

Central Objects (Path Codes) You should have these sets of central objects or path codes, which are release-specific:
  • PY910 central objects

  • DV910 central objects

  • PS910 central objects

  • PD910 central objects

Environment The installation process defines the environments, which are as follows:

PY910

CRP objects (possibly testing a package you have not released to production users), with data mapped to CRP. The path code is PY910 with table objects mapped to CRP data.

DV910

Development objects with test data. The path code is DV910, with table objects mapped to test data.

PS910

Pristine objects with EnterpriseOne pristine demo data. The path code is PS910, with objects mapped to EnterpriseOne pristine data.

PD910

Production objects with production data. The path code is PD910, with table objects mapped to production data.

TS910

CRP objects with test data. The path code is PY910, with table objects mapped to test data.

  If you are not planning any development projects, you need only two path codes: PY910 and PD910. You should create a development path code if you plan to do extensive software modification.

The fewer path codes you use, the better. With each additional path code comes version control maintenance that is time consuming unless a good reason exists for the additional path code. Even when making extensive software modifications, you should have only these four path codes (sets of central objects):

PY910

This path code contains a practice set of objects that are tested during conference room pilot before transferring objects to production. It is for deploying quick fixes or making minor modifications that you will quickly transfer to production. It can also be used as a place to test modifications that were done in the development path code before taking the risk of transferring them to the production path code.

  DV910

Use this path code for normal development. Upon successful testing, transfer the objects to the PY910 path code, using Object Transfer, and distribute to the users through a package build and a workstation installation.

PS910

This is the set of pristine objects shipped from EnterpriseOne. You should not make changes to this path code other than paper fixes from EnterpriseOne. This path code is used to compare EnterpriseOne standard software to any custom solutions you have implemented in other path codes. You should keep a copy of this path code so that you have a clean copy of the software in case you need to refresh anything.

PD910

This is the production path code. Just-in-time installations come directly from this location, and production server objects are also deployed from here. After testing software changes in PY910, transfer them to PD910 and then deploy the changes to the enterprise servers and workstations.

Packages All path codes share the same Object Librarian tables, the same system data source, and, normally, the same data dictionary. The only distinct tables across path codes are central objects/specifications (F987*), Versions List (F983051), and Processing Option Text (F98306).

At EnterpriseOne. we have determined that each package should have an A and B version, and that you alternate between these versions when you build packages.

If you are using both full and partial packages, you would have four packages for each path code. This setup gives you two full packages (A and B) for production and two partial packages (A and B) for production. For example:

  • PD910FA (Standard Production Full A)

  • PD910FB (Standard Production Full B)

  • PD910PA (Standard Production Partial A)

  • PD910PB (Standard Production Partial B)