This chapter contains the following topics:
Oracle's JD Edwards EnterpriseOne can be configured in many ways. Examples and recommendations for the setup follow.
You should follow JD Edwards 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 JD Edwards 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
You should understand the basic environments of a JD Edwards 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 JD Edwards EnterpriseOne share common data sources. For example, for JD Edwards EnterpriseOne 8.11, these data sources are common to all environments:
System - 900
Object Librarian - 900
Data Dictionary - 900
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.
This table explains the data sources for the production environment.
| Data Source | Environment |
|---|---|
| Path Code | PD900 |
| Central Objects data source | Central Objects - PD900 |
| Versions Tables data source | Versions - PD900 |
| Business Data data source | Business Data - PROD |
| Next Numbers data source | Control Tables - Prod |
| Tasks/UDCs data source | Control Tables - Prod |
This table defines the data sources for the prototype environment.
| Data Source | Environment |
|---|---|
| Path Code | PY900 |
| Central Objects data source | Central Objects - PY900 |
| Versions Tables data source | Versions - PY900 |
| Business Data data source | Business Data - CRP |
| Next Numbers data source | Control Tables - CRP |
| Tasks/UDCs data source | Control Tables - CRP |
This table defines the data sources for the development environment.
| Data Source | Environment |
|---|---|
| Path Code | DV900 |
| Central Objects data source | Central Objects - DV900 |
| Versions Tables data source | Versions - DV900 |
| Business Data data source | Business Data - TEST |
| Next Numbers data source | Control Tables - Test |
| Tasks/UDCs data source | Control Tables - Test |
This table defines the data sources for the pristine environment.
| Data Source | Environment |
|---|---|
| Path Code | PS900 |
| Central Objects data source | Central Objects - PS900 |
| Versions Tables data source | Versions - PS900 |
| Business Data data source | Business Data - PS900 |
| Next Numbers data source | Business Data - PS900 |
| Tasks/UDCs data source | System Local - PS900 |
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 - 900 |
| 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 |
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 |
Remote environment names are preceded by a 3-character location code followed by a J for Java application server.
For example:
xxxJPD900 indicates a Java application server for the PD900 environment at location xxx.
The path codes and data sources for remote environments are identical to the base environments.
This table defines the data sources for a remote production environment.
| Data Source | Environment |
|---|---|
| Path Code | PD900 |
| Purpose | PD900 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. |
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 - PD900 | Maps to the central object tables, including F98950 - User Overrides. |
| Control Tables - Prod | Maps to the next number tables. |
| Data Dictionary - 900 | 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 - 900 | Maps to the object librarian tables and the object librarian media object text in these data structures:
|
| Local - PD900 | Maps to the user defined code tables. |
| System - 900 | Maps to the system tables. |
| Versions - PD900 | Maps to the version tables, including:
|
This table defines the data sources for a remote prototype environment.
| Data Source | Environment |
|---|---|
| Path Code | PY900 |
| Purpose | PY900, 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 PD900, which represents the production data. |
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 - PY900 | Maps to the central object tables, including F98950 - User Overrides. |
| Control Tables - CRP | Maps to the next number tables. |
| Data Dictionary - 900 | 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 - 900 | Maps to the object librarian tables and the object librarian media object text in these data structures:
|
| Local - PY900 | Maps to the user defined code tables. |
| System - 900 | Maps to the system tables. |
| Versions - PY900 | Maps to the version tables including:
|
This table defines the data sources for a remote development environment.
| Data Source | Environment |
|---|---|
| Path Code | DV900 |
| Purpose | DV900, the development environment, is the testing environment for development objects. This environment shares the test data that TS900 uses. Developers log in to this environment to modify objects and test them before transferring the changed objects to the PD900 path code.
Once you have transferred objects into PD900, 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. |
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 - DV900 | Maps to the central object tables, including the F98950 - User Overrides table. |
| Control Tables - Production | Maps to the next number tables. |
| Data Dictionary - 900 | 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 - 900 | Maps to the object librarian tables and to the object librarian media object text in these data structures:
|
| Local - DV900 | Maps to the user defined code tables. |
| System - 900 | Maps to the system tables. |
| Versions - DV900 | Maps to the version tables, including;
|
This table illustrates the data sources for a remote test environment.
| Data Source | Environment |
|---|---|
| Path Code | PS900 |
| Purpose | Use the PS900 environment to test pristine (unaltered) objects with JD Edwards 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 JD Edwards 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 JD Edwards EnterpriseOne demonstration data shipped with the software. |
This table illustrates the object mappings for a test environment.
| Mapping | Explanation |
|---|---|
| Business Data - PS900 | 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 - 900 | 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 - 900 | Maps to the object librarian tables and to the object librarian media object text in these data structures:
|
| Local - PS900 | Maps to the user defined code tables. |
| System - 900 | Maps to the system tables. |
| Versions - PS900 | Maps to the version tables, including:
|
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.
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 - PS900 | The owner is PS900DTA.
The library is PS900DTA. 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-JD Edwards EnterpriseOne systems. |
| Central Objects - PY900 | The owner is PY900.
The library is COPY900. The central objects data source associated with the PY900 path code. After you create and test the modifications in this path code, transfer them to the PD900 path code. |
| Central Objects - DV900 | The owner is DV900.
The library is CODV900. The central objects data source associated with the DV900 path code. After you create and test the modifications in this path code, transfer them to the PD900 path code. |
| Central Objects - PS900 | The owner is PS900.
The library is COPS900. The central objects data source associated with the PS900 path code. |
| Central Objects - PD900 | The owner is PD900.
The library is COPD900. The central objects data source associated with the PD900 path code. Transfer objects into this data source after you have tested them in path code DV900. |
| 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 - PS900 | The owner is PS900CTL.
The library is PS900CTL. The control tables used in the PS900 path code. |
| Control Tables - Test | The owner is TESTCTL.
The library is TESTCTL. The control tables used in the test environment. |
| Data Dictionary - 900 | The owner is DD900.
The library is DD900. The single data dictionary that all environments use. |
| LOCAL | No owner exists.
The data source that defines the local machine to JD Edwards EnterpriseOne. Use it to override reports to the workstation. |
| machine name | No owner exists.
A value that defines the logic host to JD Edwards EnterpriseOne. |
| Machine Name - Server Map | The owner is SVM900.
The server map for the logic server. |
| Object Librarian - 900 | The owner is OL900.
The Object Librarian, which is release specific. |
| Control Tables Local | No owner exists.
The data found in the PSCTL900 MSDE. This data is used only in the planner. |
| System Local | No owner exists.
The data found in the PSSY900 MSDE. This data is used only in the planner. |
| Data Dictionary Local | No owner exists.
The data found in the PSDD900 MSDE. This data is used only in the planner. |
| Object Librarian Local | No owner exists.
The data found in the PSOL900 MSDE. This data is used only in the planner. |
| Versions Local | No owner exists.
The data found in the PSVL900 MSDE. This data is used only in the planner. |
| Local - PY900 | No owner exists.
The source that contains the User Defined Codes (UDCs): Control Tables - CRP. |
| Local - DV900 | No owner exists.
The source that contains the User Defined Codes (UDCs): Control Tables - Test. |
| Local - PS900 | No owner exists.
The source that contains the User Defined Codes (UDCs): Business Data - PS900. |
| Local - PD900 | No owner exists.
The source that contains User Defined Codes (UDCs): Control Tables - Production. |
| System - 900 | The owner is SY900.
The library is SY900. The single set of system tables that all environments use. |
| Versions - PY900 | The owner is PY900.
The library is COPY900. The source that contains the versions list and processing option text tables for the PY900 environment. |
| Versions - DV900 | The owner is DV900.
The library is CODV900. The source that contains the versions list and processing option text tables for the DV900 environment. |
| Versions - PS900 | The owner is PS900.
The library is PS900. The source that contains the versions list and processing option text tables for the PS900 environment. |
| Versions - PD900 | The owner is PD900.
The owner is COPD900. The source that contains the versions list and processing option text tables for the PD900 environment. |
This table summarizes the data, environments, central objects (path codes), and packages needed:
| Requirement | Explanation |
|---|---|
| Data | You might have these sets of data:
|
| Central Objects (Path Codes) | You should have these sets of central objects or path codes, which are release-specific:
|
| Environment | The installation process defines the environments, which are as follows:
PY900 CRP objects (possibly testing a package you have not released to production users), with data mapped to CRP. The path code is PY900 with table objects mapped to CRP data. DV900 Development objects with test data. The path code is DV900, with table objects mapped to test data. PS900 Pristine objects with JD Edwards EnterpriseOne pristine demo data. The path code is PS900, with objects mapped to JD Edwards EnterpriseOne pristine data PD900 Production objects with production data. The path code is PD900, with table objects mapped to production data. TS900 CRP objects with test data. The path code is PY900, with table objects mapped to test data |
| If you are not planning any development projects, you need only two path codes: PY900 and PD900. 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): PY900 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. |
|
| DV900
Use this path code for normal development. Upon successful testing, transfer the objects to the PY900 path code, using Object Transfer, and distribute to the users through a package build and a workstation installation. PS900 This is the set of pristine objects shipped from JD Edwards EnterpriseOne. You should not make changes to this path code other than paper fixes from JD Edwards EnterpriseOne. This path code is used to compare JD Edwards 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. PD900 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 PY900, transfer them to PD900 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 JD Edwards 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:
|