5 Understanding and Setting Up Environments

This chapter contains the following topics:

5.1 Understanding Environments

This section provides an overview of environments and discusses:

  • Environment definitions

  • Environment table relationships

    See Chapter 4 "Using Environment Director to Copy an Environment to a New Environment" for a more automated approach to setting up environments.

5.1.1 Understanding Environments

EnterpriseOne environments, which you define, are collections of pointers indicating the location of data and objects. An environment definition contains a path code and a set of Object Configuration Manager (OCM) mappings.

EnterpriseOne has these types of environments:

  • Distributed data and distributed logic environments.

    Distributed data and logic environments determine where data resides and where application processing occurs.

  • Group of object environments.

    Group of object environments control which set of objects is used, such as production, development, or pristine.

5.1.2 Understanding Environment Definitions

Environment definitions are stored in these five tables:

Library List Control Table (F0093)

The Library List Control table (F0093) contains valid environments for each user. You must assign to each user at least one valid environment for logging on to EnterpriseOne. The environments you assign to each user in the Library List Control table are validated at startup against the EnterpriseOne directories on the workstation. Only those environments for which a user is authorized and that are installed on the machine they log on to are listed as available environments.

The Environment Revisions form of the User Profile application enables you to specify which users are authorized for specific environments.

Library List Master File Table (F0094)

The Library List Master File table (F0094) contains the name of the environment and the description.

Environment Detail Table (F00941)

This table contains the environment name and the associated path code from the Object Path Master File table (F00942).

Every environment must have an associated path code, but environments can share the same path code. For example, two environments can use production objects and have different data location mappings, such as in the case of a group of users processing against data on a corporate server and a group of users processing against data on a departmental server.

Object Configuration Master Table (F986101)

The Object Configuration Master table (F986101) has data and logic object mappings for every environment. Every environment must have entries in the Object Configuration Master table, even if the mappings for the environments are identical. Two environments might have different path codes but have the same mappings for data and logic. For example, developers and testers could have different sets of objects, but their data is in the same database and their logic processes locally.

Object Path Master File Table (F00942)

This table stores the location of the path code's central objects, the release associated with this path code, and other details.

5.1.3 Understanding Environment Table Relationships

The Library List Control table and the Environment Master table have a direct correlation. For each environment listed as a valid user environment in the F0093, there is one F0094 record that provides the name and description of that environment. The F986101 and F00941 and F00942 provide additional information for each of the environments defined in the Environment Master table (F0094).

This diagram illustrates environment table relationships:

Figure 5-1 Environment Table Relationships

Description of Figure 5-1 follows
Description of ''Figure 5-1 Environment Table Relationships''

5.2 Setting Up Environments

This section provides and overview of setting up environments and discusses how to set up processing options using Environment Master (P0094).

5.2.1 Understanding Setting Up Environments

You can create a new environment either by adding a new environment or by copying an existing environment. The custom environments functionality in Installation Planner and Environment Director applications simplify this process.

Because the Object Configuration Manager (OCM) mappings are an important element of the environment, determining these mappings is the first step in deciding whether to create a new environment or copy an existing environment.

When you copy an environment, the OCM mappings for that environment are copied along with the environment. It is sensible to create a new environment by copying an existing environment when the OCM mappings for the environment you want to create closely match the mappings of an existing environment. For example, if a development environment and a test environment contain similar mappings, it might be easier to copy an environment and change the mappings that are different.

You should add a new environment rather than copying an existing environment when you do not want to use another environment's object mappings.

Note:

Remember that when you add an environment without copying an existing one, you must create the OCM mappings manually. For this reason, it is typically easier to create a new environment by copying an existing one and adjusting the OCM mappings instead of creating all of them manually.

5.2.2 Form Used to Work with Environments

Form Name FormID Navigation Usage
Work With Environments W0094E In Solution Explorer, navigate to System Administration Tools, System Administration Tools, Environment Management, Environment Master(P0094). Used to work with environments.

5.2.3 Setting Processing Options for Environment Master

Processing options enable you to specify the default processing for programs and reports.

5.2.3.1 Process

These processing options give you greater flexibility when copying or deleting by enabling you to specify whether users have the ability to copy or delete OCM mappings for this environment in other data sources.

Regardless of what you enter for these processing options, the software automatically copies or deletes OCM mappings for the environment you are using. The processing option values you enter determine whether you can copy or delete mappings in other data sources.

1. Delete OCM Mappings

Indicate whether users can delete Object Configuration Manager mappings for this environment from other data sources. Values are:

Blank: Users cannot delete OCM mappings.

1: Users can delete OCM mappings.

2. Copy OCM Mappings

Indicate whether users can copy Object Configuration Manager records for this environment into other server map data sources. Values are:

Blank: Users can copy OCM mappings.

1: Users cannot copy OCM mappings.

5.3 Adding an Environment

This section discusses how to add an environment.

5.3.1 Forms Used to Add an Environment

Form Name FormID Navigation Usage
Environment Revisions W0094A In Solution Explorer, navigate to System Administration Tools, System Administration Tools, Environment Management, Environment Master(P0094).

In the Work With Environments form, click Add.

Used to add an environment.
Data Source Selection W0094F From the Environment Revisions form, the system will display the Data Source Selection form if the path code you entered does not exist in the Library Master File table (F0094). Used to select a data source.

5.3.2 Adding an Environment

You should add a new environment rather than copying an existing environment when you do not want to use the OCM mappings of another environment.

Access the Environment Revisions form.

Figure 5-2 Environment Revisions form

Description of Figure 5-2 follows
Description of ''Figure 5-2 Environment Revisions form''

Environment Name

Specify the name associated with a specific list of libraries. The J98INITA initial program uses these library list names to control environments that a user can sign on to. These configurations of library lists are maintained in the Library List Master File table (F0094).

This field represents a valid environment that can be used to run in EnterpriseOne. The environment encompasses both a path code (objects) and a data source (data). When put together, users have a valid workplace within the system.

Description

Add a user defined name or remark.

Path Code

Specify a pointer to a set of EnterpriseOne objects which will be used to keep track of sets of objects and their locations within EnterpriseOne.

Release

Specify the release number as defined in the Release Master.

Just In Time Installation

Use this field to turn ON/OFF just-in-time installation for anyone signed onto this environment. Consider turning just-in-time installation OFF before you transfer modified applications into the production path code. Once you have fully tested the applications and are ready for production users to receive the changes, you can turn just-in-time installation back ON.

Developer (Y/N)

Future Use.

A one field for the Install group.

WAN Configured Environment

Specify the code to be used

1 - WAN Configured Environment

Blank - Not Configured for WAN

Mobile Environment

Specify the code the that allows the user to indicate that this environment is a mobile environment.

Figure 5-3 Data Source Selection form

Description of Figure 5-3 follows
Description of ''Figure 5-3 Data Source Selection form''

OL Data Source

Identify the data source.

5.4 Setting Up Color Coded Environments (Release 9.2.4)

You can set up environments to be color coded for when you need a clear visual distinction as to which environment you are logged into. This enables you to quickly identify non-production environments by color.

The UDC 98/CO allows you to list environments and identify the color scheme for that environment. If no environment is listed the default color scheme is retained.

Note:

Color coded environments is not compatible with Internet Explorer 11.

5.4.1 Setting Up Color Coded Environments

To Set up color coded environments:

  1. Log into JD Edwards EnterpriseOne.

  2. Enter UDC in the Fast Path.

  3. Enter 98 in the Product Code field.

  4. Enter CO in the User Defined Codes field.

  5. Click find to verify the table exist.

  6. Click the Add button.

  7. Enter the environment you want a different color scheme for in the Codes column.

  8. Enter the hex code for the color in the description 1* field.

  9. Enter the next environment and color.

  10. Click the OK button

  11. Close User Defined Codes application.

  12. Log out of JD Edwards EnterpriseOne.

  13. Log into an environment with an associated color scheme.

Note:

If the colors do not appear, clear the server cache with Cache Management in Server Manager.

5.5 Copying an Environment

This section discusses how to copy an environment.

5.5.1 Form Used to Copy an Environment

Form Name FormID Navigation Usage
Copy an Environment W0094B In Solution Explorer, navigate to System Administration Tools, System Administration Tools, Environment Management, Environment Master(P0094).

In the Work With Environments form, click Find.

Highlight the row you want and click Select.

In the Row menu, click Copy Environment.

Used to copy and environment.

5.5.2 Copying an Environment

When you create a new environment by copying an existing environment, the software also copies the Object Configuration Manager mappings associated with the existing environment. You can set up a processing option if you want to specify additional Object Configuration Manager mappings to copy at the time that you copy the environment.

You can copy environments from your own existing environments, or you can use the Installation Planner, which provides sample production environments you can use as templates. These templates contain suggested mappings for all EnterpriseOne tables.

Access the Work With Environments form.

Figure 5-4 Copy an Environment form

Description of Figure 5-4 follows
Description of ''Figure 5-4 Copy an Environment form''

Existing Environment

Note:

This field will be unavailable for input.

The name associated with a specific list of libraries. The J98INITA initial program uses these library list names to control environments that a user can sign on to. These configurations of library lists are maintained in the Library List Master File table (F0094).

This field represents a valid environment that can be used to run in EnterpriseOne. The environment encompasses both a path code (objects) and a data source (data). When put together, users have a valid workplace within the system.

New Environment

Specify the name associated with a specific list of libraries. The J98INITA initial program uses these library list names to control environments that a user can sign on to. These configurations of library lists are maintained in the Library List Master File table (F0094).

This field represents a valid environment that can be used to run in EnterpriseOne. The environment encompasses both a path code (objects) and a data source (data). When put together, users have a valid workplace within the system.

Copy *PUBLIC Records Only

When copying an environment, the OCM records are also copied.

Check this box to copy only the *PUBLIC OCM records to the new environment.

5.6 Copying a New Environment to a New Path Code

This section discusses how to copy a new environment to a new path code.

5.6.1 Forms Used to Copy New Environment to a New Path Code

Form Name FormID Navigation Usage
Work With Environments W0094E In Solution Explorer, navigate to System Administration Tools, System Administration Tools, Environment Management, Environment Master(P0094).

In the Work With Environments form, click Find.

Used to copy a new environment to a new path code.
Copy Environment W0094B In the Work With Environments form, highlight the row you want and click Copy Environment. Used to copy and environment.
Path Code Revisions W980042D In Solution Explorer, navigate to System Administration Tools, System Administration Tools, Environment Management, Environment Master(P0094).

In the Work With Environments form, click Find.

Highlight the new environment and click Path Code from the Row menu.

Used to copy a new environment to a new path code.

5.6.2 Copying a New Environment to a New Path Code

Copying a new environment to a new path code requires that you know how to use the copy feature to create a new test environment with demo data loading in a new path code.

Access the Path Code Revisions form.

Figure 5-5 Path Code Revisions form

Description of Figure 5-5 follows
Description of ''Figure 5-5 Path Code Revisions form''

Path Code

Specify a pointer to a set of EnterpriseOne objects which will be used to keep track of sets of objects and their locations within EnterpriseOne.

Description

Specify a user defined name or remark.

Location

Indicate the name of the machine on the network (server or workstation).

Server Share Path

Indicate the shared directory for the path code. The objects that are stored on a file server will be found in this path.

Status Code

Determine the status of the software in the development cycle.

Merge Option

Denote whether a customer's object will be merged with the EnterpriseOne object This option can be set at the path code level so that all objects checked into that path will carry the same merge option as the path code.

Release Number

Specify the release number as defined by the release master.

Deployment Data Source

Specify the data source if the primary data source or if the data item in the primary data source cannot be located.

UNC Flag

Determine how to create the serve path. Valid options are:

1 or Y Creates the paths using relative paths. Enter a double slash (||) rather than a specific drive followed by a single slash (\).

0 or N Creates the path using the actual drive letter.

Cumulative Description

The description that appears in the Z record of a SAR when OMW enters information into that record.

5.7 Creating Test Batch Files

This section discusses how to create test batch files.

5.7.1 Creating Test Batch Files

To create test batch files:

  1. Using a text editor such as Notepad, remark out all lines in the LOADALL and JDESET files and format a test set in the same format as the production set.

  2. Copy the LOADPROD to a LOADTEST.BAT file, and change the appropriate parameters to the ones you created in the JDESET.BAT file.

  3. Run the LOADALL.BAT batch application.

  4. Add the data sources you need in the current plan's planner environment.

    • For logical data sources, you will probably want Business Data Test, Central Objects Test, EnterpriseOne Local Test, and Control Tables Test.

    • Make sure the deployment server source matches the Central Objects Data source and the LOADALL specifications that you entered.

5.8 Updating Server Map Tables with the New Environment

This section discusses how to update server map tables with the new environment

5.8.1 Form Used to Update Server Map Tables

Form Name FormID Navigation Usage
Work With Installation Plans W98240B In Solution Explorer, navigate to System Administration Tools, System Installation Tools, Custom Installation Plan (P98240).

In the Work With Installation Plans form, select your plan and expand it.

Select the environment and click Select.

In the Row menu, click Copy Environment.

Save the environment you added.

Used to update the server map tables with the new environment.
Work with Locations and Machines W9654AA In Solution Explorer, navigate to System Administration Tools, System Administration Tools, Advanced Operations. In the Work with Locations and Machines form, select your location and expand EnterpriseOne Servers. Select the server you want to reuse. Select Generate Server Mapfrom form menu.

Select Generate Svr. Map from the Form menu

Used to revise server map tables.

5.8.2 Adding a New Path Code on the Enterprise Server

To add a new path code on the EnterpriseOne Server:

  1. Sign on to the EnterpriseOne server with an account that has authority to the existing path codes.

  2. Navigate to an existing path code.

  3. Copy that directory to the new path code name.

5.8.2.1 Windows Path Example

This is an example of a Windows path:

D:\JDEdwards\E910\ddp\PS910 (copy PS910 to TS910)

5.8.2.2 Unix Path Example

This is an example of a Unix path:

/u01/jdedwards/E910/PS910 (copy PS910 to TS910)

5.8.2.3 IBM i Path Example

You can also map a network drive to the root directory and do the first step from the deployment server.

  1. MKDIR TS910 CPY OBJ('/PS910/*') SUBTREE(*ALL) OWNER(*KEEP)

  2. Then copy the path code library: ADDLIBLE E910SYS CPYLIB FROMLIB(PS910) TOLIB(TS910) CRTLIB(*YES)

5.9 Deleting an Environment

This section discusses how to delete an environment.

5.9.1 Form Used to Delete an Environment

Form Name FormID Navigation Usage
Work With Environments W0094E System Administration Tools, System Administration Tools, Environment Management, Environment Master (P0094).

In the Work With Environments form, click Find.

Highlight the row you want and click Select.

Under File, click Delete.

In the Confirm Delete message, click OK.

Used to delete an environment.

5.9.2 Deleting an Environment

When you delete an environment, the environment definition is removed and the Object Configuration Manager records associated with the environment are deleted. You can set a processing option if you want to specify additional Object Configuration Manager mappings to delete when you delete the environment.

Access the Work With Environments form.

Figure 5-6 Work With Environments form

Description of Figure 5-6 follows
Description of ''Figure 5-6 Work With Environments form''

Environment Name

Specifies the name to be associated with a specific list of libraries. The J98INITA initial program uses these library list names to control environments that a user can sign on to. These configurations of library lists are maintained in the Library List Master File table (F0094).

This field represents a valid environment that can be used to run in EnterpriseOne. The environment encompasses both a path code (objects) and a data source (data). When put together, users have a valid workplace within the system.

Description

Specifies a user defined name or remark.

Path Code

Specifies the path code as a pointer to a set of EnterpriseOne objects, and is used to keep track of sets of objects and their locations within EnterpriseOne.

Release

Specifies the release number as defined in the Release Master.

Just In Time Installation

Used to turn ON/OFF just-in-time installation for anyone signed onto this environment. Consider turning just-in-time installation OFF before you transfer modified applications into the production path code. Once you have fully tested the applications and are ready for production users to receive the changes, you can turn just-in-time installation back ON.

Developer (Y/N)

Future Use.

A one byte field for the Install group.

WAN Configured Environment

Indicates that this environment is an environment that is configured for the WAN.

1 - WAN Configured Environment

Blank - Not Configured for WAN

Mobile Environment

Indicates that this environment is a mobile environment.

5.10 Understanding Copying an Environment to a New Environment

The Environment Director application (P989400) brings all of the steps necessary to create an environment together in one place. It enables the user to copy an existing environment, share or copy an existing path code, set up data sources, create client and server map Object Configuration Manager (OCM) mappings, and copy data from an existing environment. This application works in the same manner as a wizard. You fill in the necessary data and then click Next.

When you want to create a new environment based on an existing environment, you can copy the control tables, business data, central objects, tested full package, and related records from the existing environment to the new environment using Environment Director. The copy environment process is run on the Deployment Server.

Note:

This process cannot be run for a target environment if the target environment and its path code are already defined in F00941 / F00942 on the Deployment Server. If you want to copy to a pre-defined environment, you must follow the procedure in the Install Guide for DB2 UDB on Microsoft Windows, Chapter 13: Copying an Environment to Another Environment.

See JD Edwards EnterpriseOne Tools Release 9.0 Installation Guide.

5.11 Understanding Creating OCM Mappings

You can create OCM mappings (TBLE, GT, BSFN, UBE) for new or copied environments. OCM mappings for a new or copied environment are created by setting up mappings for tables and GTs, and then configuring BSFN and UBE mappings.

TBLE, GT When Creating New Environments

The software finds the data class for each table or GT object in the Object Librarian Master table (F9860). Based on the environment and data class for the object, the data source name is fetched from the data sources by the Environment table (F98511). If a record is not found, the software looks for a record for the data classes where environment name is DEFAULT (a shared data source). If that data source is the default mapping, a mapping with object name DEFAULT is created; otherwise, the actual object name is used. Mappings are not created for tables in the Planner and Internal data classes.

TBLE, GT When Copying Environments

The software looks at each *PUBLIC OCM record for TBLE and GT objects for the environment being copied. It then fetches the data class for the object from Object Librarian. It then looks in F98511 for the data source in the new environment for that data class. If the data source is different from that in OCM, it changes the OCM mapping to point to the new data source.

BSFN, UBE OCM Mappings

The OCM generation algorithm for UBEs and BSFNs is identical, but the output depends on whether the default mapping is LOCAL or an enterprise server.

5.11.1 Default Mapping to LOCAL

LOCAL mappings are created for any object whose Location (labeled Business Function Location for BSFNs and Process Location for UBEs) in OMW is Client Only (F9860.SIBFLOCN = 1).

5.11.2 Default Mapping to Server

Server mappings are created for any object whose Location (labeled Business Function Location for BSFNs and Process Location for UBEs) in OMW is Server Only (F9860.SIBFLOCN = 3).

This table provides the default mappings:

Type Base Environment(DV910, PS910, PD910, PY910) HTML server/WTS Environment(JDV910, JPS910, JPD910, JPY910)
UBE Enterprise Server Enterprise Server
BSFN LOCAL Enterprise Server

This table defines the object name and data class.

Object Name Data Class
F0094 S
F9860 O
F9200 D
F0101 B
F01012 B
F0004 T
F98710 C
F983051 V
GT92002 D
GT9860A O
GT3711 B
GT4801 B

This table lists the environment, object name, user role and data source.

Environment Object Name User/Role Data Source
ENV1 DEFAULT *PUBLIC Business Data - ENV1
ENV1 F0094 *PUBLIC System - 910
ENV1 F9860 *PUBLIC Object Librarian - 910
ENV1 F9200 *PUBLIC Data Dictionary - 910
ENV1 F0004 *PUBLIC Control Tables - ENV1
ENV1 F983051 *PUBLIC Versions - PY910
ENV1 GT92002 *PUBLIC Data Dictionary - 910
ENV1 GT9860A *PUBLIC Object Librarian - 910
ENV2 DEFAULT *PUBLIC Business Data - ENV2
ENV2 F0094 *PUBLIC System - 910
ENV2 F9860 *PUBLIC Object Librarian - 910
ENV2 F9200 *PUBLIC Data Dictionary - 910
ENV2 F0004 *PUBLIC Control Tables - ENV2
ENV2 F983051 *PUBLIC Versions - DV910
ENV2 GT92002 *PUBLIC Data Dictionary - 910
ENV2 GT9860A *PUBLIC Object Librarian - 910

5.12 Understanding UBE Copy Programs

UBE Copy Programs are used to copy a source package to a target package. Once you have copied the source package to the target package, you must deploy it on the server in order to use it.

Source UBE Copy Program
Business Data R98403 XJDE0021
Control Tables R98403 XJDE0022
Central Objects and Versions R98403 XJDE0019
Deployment Server Directory R9800942 (This UBE also copies the Package Header / Detail records)
Checkout Records R989861 XJDE0001
ESU History R9672 XJDE0001
Path Code Directory on Enterprise Server Submits R9894003 XJDE0001 to the server
Copy Metadata Repository Runs R9894005 XJDE0001 to copy the metadata repository within Central Objects. It is dependent on the existence of the package header record for the target package. R9800942 copies the package records for you.
Configure Manifest Runs R9894005 XJDE0002 to rename the local metadata repository within the target path / package directory on the Deployment Server. This UBE also configures the manifest in Central Objects and in the target package on the Deployment Server. It also configures the spec.ini in the target package on the Deployment Server. . It is dependent on the existence of the package header record for the target package. R9800942 copies the package records for you.

5.13 Setting Up Database Components

This section provides an overview for setting up database components and discusses how to setup database components for the following platforms:

  • Unix

  • Microsoft Windows

  • IBM i

5.13.1 Understanding Setting Up Database Components

Before running the Environment Copy application (P989400), you must set up the database components for the target environment on your enterprise server.

5.13.2 Setting up Database Components for Unix Platform

To set up database components for Unix:

  1. Sign on to the enterprise server as an administrative user, for example; root.

  2. Change directories: cd to the EnterpriseOne install location, for example; /u01/JDEdwards/e910.

5.13.3 Setting up Database Components for Microsoft Windows Platform

To set up database components for Microsoft Windows sign on to the enterprise server as an administrative user.

5.13.4 Setting up Database Components for IBM i Platform

To set up database components for IBM i:

  1. Sign onto the enterprise server as a user with authority to create libraries.

  2. Create these libraries:

    • XXXDTA (substitute your business data library)

    • XXXCTL (substitute your control tables library)

    • XX910 (substitute your path code)

    • XX910FA (substitute your target package name)

    • COXX910 (substitute your Central Objects)

5.14 Configuring Setup Files

This section provides an overview of configuring setup files and discusses how to:

  • Configure Oracle database setup files.

  • Configure UDB database setup files.

  • Configure SQL database setup files.

5.14.1 Understanding Setup Files Configuration

Before running the Environment Copy application, you must setup the configuration files for the target platform on your enterprise server.

5.14.2 Configuring Oracle Database Setup Files

An Oracle database platform includes:

  • Microsoft Windows Platform

  • Linux / Unix Platform

5.14.2.1 Microsoft Windows Platform

To configure the setup file for Microsoft Windows:

  1. Navigate to the ORCL folder under the install path.

  2. Find the ce_ORCL_SET.bat file and change the variable values:

    • @set NEWENV=YES

    • @set NEWPATHCODE=YES

    • @set UPATHCODE= xx910 (substitute your path code name)

    • @set UENV= xxx (substitute your environment prefix)

  3. Start the cmd window, and then navigate to the ORCL folder within the install location (for example, z:\JDEdwards\E910\ORCL).

  4. Run ce_InstallOracleDatabase.BAT.

  5. Check the logs in the logs directory.

5.14.2.2 Linux/Unix Platform

To configure the setup file for Linux/Unix:

  1. Navigate to the ORCL folder under the install path (for example, /u01/JDEdwards/ORCL).

  2. Find the ce_ORCL_SET.sh file and change the variable values:

    • export NEWENV=YES

    • export NEWPATHCODE=YES

    • export LPATHCODE=xx910 (substitute your path code name)

    • export LENV=xxx (substitute your environment prefix)

  3. Verify the settings in the ce_CallInstall.sh file: export DATABASE_INSTALL_PATH=/u01/jdedwards/e910/ORCL

  4. Run ce_CallInstall.sh.

  5. Check the logs in the logs directory.

5.14.3 Configuring UDB Database Setup Files

UDB database platforms include:

  • Microsoft Windows Platform

  • Linux / Unix Platform

5.14.3.1 Microsoft Windows Platform

To configure the setup file for Windows with UDB:

  1. Navigate to the UDB folder under the install path.

  2. Find the ce_UDB_SET.bat file and change the variable values:

    • @set NEWENV=YES

    • @set NEWPATHCODE=YES

    • @set UPATHCODE=XX910 (substitute your path code name - uppercase)

    • @set LPATHCODE=xx910 (substitute your path code name - lowercase)

    • @set LENV=xxx (substitute your environment prefix - lowercase)

    • @set UENV=XXX (substitute your environment prefix - uppercase)

  3. Start the db2cmd window, and then navigate to the UDB folder within the install location (for example, z:\JDEdwards\E910\UDB).

  4. Run ce_InstallUDBDatabase.BAT.

  5. Check the logs in the logs directory.

5.14.3.2 Linux/Unix Platform

To configure the setup file for Linux/Unix:

  1. Navigate to the UDB folder under the install path.

  2. Find the ce_UDB_SET.sh file and change the variable values:

    • export NEWENV=YES

    • export NEWPATHCODE=YES

    • export LPATHCODE= xx910 (substitute your path code name - lowercase)

    • export UPATHCODE=XX910 (substitute your path code name - uppercase)

    • export LENV= xxx (substitute your environment prefix - lowercase)

    • export UENV=XXX (substitute your environment prefix - uppercase)

  3. Run ce_RunInstallUDBDatabase.sh passing in the current directory as an argument, for example: . ./ce_RunInstallUDBDatabase.sh '/u01/JDEdwards/e910/UDB'.

  4. Check the logs in the logs directory.

5.14.4 Configuring SQL Database Setup Files

Use these steps to configure the setup files for a SQL database.

  1. Navigate to the SQL scripts directory within the EnterpriseOne install location, for example, z:\JDEdwards\E910\MSSQL\scripts.

  2. Edit the ce_JDESET.BAT file:

    • rem SQL_PATH - directory where you want your database files

    • @set SQL_PATH= z:\JDEdwards\MSSQL

    • rem Version 8 is SQL Server 2000. version 9 is SQL Svr 2005

    • @SET SQL_VERSION=9

    • @set NEWENV=YES

    • @set NEWPATHCODE=YES

    • @set UPATHCODE= xx910 (substitute your path code name)

    • @set UENV= xxx (substitute your environment prefix)

    • rem JDE_SRV=MYMACHINE or JDE_SRV=MYMACHINE\MYINSTANCE

    • @set JDE_SRV=MACHINENAME\INSTANCE (substitute your machine name and instance)

  3. Start the cmd window and navigate to the SQL scripts directory.

  4. Run ce_InstallSQLDatabase.bat, passing in your sa user and password; for example, ce_InstallSQLDatabase.bat sa MySAPwd

  5. Check the logs in the scripts directory.

5.15 Setting Up Security Overrides

This section provides an overview of security overrides and discusses these tasks:

  • Adding a System User for the Central Objects Data Source Owner.

  • Adding an Override for an EnterpriseOne User Running Copy Environment.

5.15.1 Understanding Security Overrides

If you are running with security server turned on, you must add a security override so that the Copy Environment process can create the metadata repository tables in Central Objects. Adding a security override must be done by a security administrator. To add a security override, you must first add a system user for the Central Objects data source owner, and then add an override for the EnterpriseOne user who will run Copy Environment.

5.15.2 Adding a System User for the Central Objects Data Source Owner

To add a system user for the Central Objects data source owner:

  1. In P98OWSEC, select the form exit Add System User.

  2. On Work with System Users, enter the appropriate data source owner (for example, DV910, PY910 or PD910) in the System User field and select Find.

  3. If no values are returned, add the data source owner as a system user by selecting Add and completing the fields on the System User Revisions form:

    • System User

    • Data Source

    • Password

    • Password Verify

  4. Click OK and then Cancel and Close to return to the Work with User Security form.

5.15.3 Adding an Override for an EnterpriseOne User Running Copy Environment

To add an override for an EnterpriseOne user who is going to run Copy Environment:

  1. On Work with User Security, enter the user who is going to run Copy Environment, and select Find.

  2. Select the Form exit, Add Data Source.

  3. On Add Data source, complete the User ID, Data Source, and System User fields.

5.16 Using Environment Director to Copy an Environment to a New Environment

This section provides an overview of copying an environment to a new environment using Environment Director and discusses how to create a new environment using the Director mode.

5.16.1 Understanding Copying an Environment to a New Environment

The Environment Copy (P989400) application provides a director that steps you through the process of copying an environment to a new environment.

5.16.2 Prerequisites

Oracle recommends that you use the Environment Director and not the Installation Planner (P9840) and Installation Workbench (P9841) to create custom environments. Environment Director, Installation Planner, and Installation Workbench share common functionality for configuring custom environments.

If the target path code directory already exists on the deployment server or enterprise server (for example, from a previous attempt to copy to that path code), please remove it before you start the copy process. The Copy process breaks if another process has a lock on anything within that directory.

You can use the Windows command:

rmdir /S /Q d:\JDEdwards\e910\XX910(substitute your target path code directory)

You can use the Unix command:

rm -Rf /u01/jdedwards/e910/XX910

On IBM i, if the target path code and package libraries already exist from a previous attempt, please delete them before starting the copy process.

5.16.3 Forms Used By Environment Director in Director Mode

Form Name FormID Navigation Usage
Copy Environment / Package W989400V From menu GH9611, run the application Environment Copy(P989400).

Select Create/copy to New Environment. ClickNext.

Used to copy an existing environment to a new environment.
Environment Director W989400A Click Next from the Copy Environment / Package form. Defines the components of a new environment including environment, path code, enterprise servers, and data sources.
Environment W989400B Click Next from the Environment Director form. Used to select the mode to be used for setup of the new environment. For Copy Environment, fill in the source environment information.
Environment Properties W989400C Click Next from the Environment form. Used to specify the properties for the new or copied environment.

Note: If an environment is being copied, the properties are presented as defaults on this form.

Path Code W989400D Click Next from the Environment Properties form. Used to specify the Path Code that will be associated with the new environment.
Path Code Properties W989400E Click Next from the Path Code form. Used to specify the properties for the new path code. The properties for the existing path code are used as defaults for the new path code.
Data Source Revisions W986115O Click Next from the Path Code Properties form. Used to select the data source type and to provide specific database information. After filling in the appropriate information, click OK.
Machines W989400J Click OK on the Data Source Revisions form, and then click Next from the Path Code Properties form. Used to select the enterprise servers where the new environment will run. EnterpriseOne will use this information to populate the server map data sources on these servers. Highlight the machine(s) and click the large right arrow.
Database Script Generator W989400T Choose your platform and database type and pressNext. Used to prompt you for the platform and database type.
Data Load W989400H Complete the fields and click Next. Used to select the data loads the system should perform.
Environment Director Revisions W989400L Verify the fields and click End. Used to complete the environment creation actions.
Table Conversion Merge/Log W984052A Filter on conversion type 95. The application writes history records into F984052. You can see the history by running Table Conversion / Merge Log (application P984052) on menu GH9611. Filter on conversion type 95.

5.16.4 Creating a New Environment Using the Director Mode

Using the Environment Director program (P989400) in Director Mode simplifies creating a new system environment by copying an existing system environment.

5.16.4.1 Environment Copy

The Copy Environment / Packages form can be used to copy data, central objects, path code, and ESU history from one environment to another predefined (standard) environment, or it can be used to create a new environment, optionally copying those same objects from an existing environment.

Access the Copy Environment / Packages form.

Figure 5-7 Copy Environment form

Description of Figure 5-7 follows
Description of ''Figure 5-7 Copy Environment form''

5.16.4.2 Environment Director

The Environment Director steps you through the process of defining the components of a new environment including environment, path code, enterprise servers, and data sources.

Access the Environment Director form.

Figure 5-8 Environment Director form

Description of Figure 5-8 follows
Description of ''Figure 5-8 Environment Director form''

New Environment

Use this option to create a new environment with no default settings.

Copy Environment

Use this option to use settings from an existing environment as the default settings for the new environment. You can modify these settings if needed.

Note:

If you selected Copy Environment, click the search button in the Existing Environment field to select an environment from which you want to copy. The existing environment must be at the current release level as the new environment

5.16.4.3 Environment

The Environment form is used to select the mode to be used for setup of the new environment.

Access the Environment form and select Director. Press Next to access the Environment Properties form.

Director

The Director mode enables you to copy your Central Objects and Business Data from one path code to another, and your Control Tables and Path Code from one environment to another. It also sets up the environment and path code definitions (EnterpriseOne architecture data). The Director mode consists of forms for environment, path code, enterprise servers, data sources, and data load. The Environment Director Revisions form is displayed at the end of the director.

Express

The Express mode sets up the EnterpriseOne architecture definition (OCM, Path Code Master and so on) for the new environment, but does not copy any data. The Express mode requires that you only enter Environment Name, Path Code Name, Enterprise Server and Port Number, and Default Data Source Type. The environment is generated and you skip to the Environment Director Revisions.

5.16.4.4 Environment Properties

The Environment Properties form is used to specify the properties for the new environment.

Note:

When you copy an environment, the properties of that environment are presented as defaults on this form.

Access the Environment Properties form.

Figure 5-10 Environment Properties form

Description of Figure 5-10 follows
Description of ''Figure 5-10 Environment Properties form''

Name

A name for the environment that encompasses both a path code (objects) and a data source (data). When put together, users have a valid workplace.

Description

A user defined name or remark.

Code

A value that the system will substitute for a token when the system creates a new environment from a template.

Release

The release number as defined in the Release Master. The default is the current release.

Just In Time Installation

This option enables just-in-time installation for anyone signed onto this environment. Consider turning just-in-time installation off before you transfer modified applications into the production path code. After you have fully tested the application and are ready for production users to receive the changes, you can turn just-in-time installation back on.

HTML Server/WTS Environment

This option is for a Java or Windows Terminal Server environment. Enabling this option affects how the system creates business function mappings for the environment and which environments are displayed at sign-in.

5.16.4.5 Path Code

The Path Code form is used to specify the path code that will be associated with the new environment.

To copy the path code, click on Copy an Existing Path Code. To copy a package from that path code, you must choose a full package. The name you choose for your new package must not already exist as a package for any path code. The application fills in the information based on the source path code.

Access the Path Code form.

Share an Existing Path Code

The path code is a pointer to a set of EnterpriseOne objects and is used to keep track of sets of objects and their locations within EnterpriseOne.

Copy an Existing Path Code

The path code is a pointer to a set of EnterpriseOne objects and is used to keep track of sets of objects and their locations within EnterpriseOne.

Existing Package Name

The existing package name is the source package in your source path code.

New Package Name

The new package name is the target package in the target path code that you are creating.

5.16.4.6 Path Code Properties

The Path Code Properties form is used to specify the properties for the new path code. The properties for the existing path code are used as defaults for the new path code.

Access the Path Code Properties form.

Figure 5-12 Path Code Properties form

Description of Figure 5-12 follows
Description of ''Figure 5-12 Path Code Properties form''

Path Code

Enter the path code, which is a pointer to a set of system objects and is used to keep track of sets of objects and their locations.

Description

Enter a user defined name or remark.

Release

Enter the release number as defined in the Release Master. It must match the environment's release.

Cumulative Description

Use to further identify the release level of the path code; it is only used by OMW for SAR integration

Location

Enter the location or machine key of the machine (server or workstation) on the network.

Server Share Path

Use this field to indicate the shared directory for this path code. The objects that are stored on a file server will be found in this path.

UNC Flag

Determines how to create the server path. Valid options are:

Checked

Creates the path using relative paths. Enter a double slash (\\), rather than the specific followed by a single slash (\).

Unchecked

Creates the path using the actual drive letter.

Deployment Data Source

Enter the location (data source) of the Central Object Specifications data source that corresponds to the path code. For example, if the environment has a PDxxxx path code, where xxxx is the current system release level, a valid data source for that path code would be Central Objects - PDxxxx, where xxxx is the current release level.

Status Code

Enter a code to determine the status of the software in the development cycle.

Merge Option

Select this option to determine whether a customer's object will be merged in with the EnterpriseOne object. The merge option can be set at the path code level so that all objects checked into that path will carry the same merge option as the path code.

5.16.4.7 Data Source Revisions

Access the Data Source Revisions form.

Figure 5-13 Data Source Revisions form

Description of Figure 5-13 follows
Description of ''Figure 5-13 Data Source Revisions form''

Data Source Name

Specify the name that identifies the data source.

Data Source Use

Indicate how the data source is to be configured, Servers (SVR) to run UBEs and Business Functions or a Database to access table data.

Data Source Type

Specify the type of database.

Data Class

Future Use

Platform

Specify the type of physical hardware the database resides on.

Database Server Name

Specify the name of the computer that receives documents form clients.

5.16.4.8 Machines

The Machines form is used to select the enterprise servers where the copied environment will run. EnterpriseOne will use this information to populate the server map data sources on these servers.

Select which enterprise servers you want to copy the package / path codes on. The existing (source) path code and package must exist on any server you select. If you wish to copy path and package directories form one server to another, you must do the copy yourself using operating system utilities.

For example:

  • IBM i - use SAV and RST to get the IFS directories over.

  • Windows - map a network drive and copy the directories.

  • Unix - use tar, zcat and ftp to get the paths across machine.

You are responsible for ensuring that the binaries are compatible between the source and target machines.

Access the Machines form.

Machine Key

Indicate the name of the machine on the network (server or workstation).

Port Number

Identify the port for a given instance of EnterpriseOne. Because the JDE.ini file controls the port to which a workstation will connect, for workstations this port number is for reference only.

Note:

You must select at least one enterprise servers before clicking Next. To do so, click the enterprise server located in the left field below Port Number, and then click the Right arrow.

5.16.4.9 Data Script Generator

The Data Script Generator form is used to choose your platform and database type.

Access the Data Script Generator form.

Figure 5-15 Data Script Generator form

Description of Figure 5-15 follows
Description of ''Figure 5-15 Data Script Generator form''

Operating System

Select the operating system.

Database Type

Select the database type.

SQL Server Properties

Select the SQL server properties.

The Database Server Name and Database Server Path fields were used when selecting Windows and SQL. These fields can now be left blank and will have no affect on the environment copy process.

5.16.4.10 Data Load

The Data Load form is used to select the data loads the system should perform.

You can override the defaults for copying data. The options for Metadata repository will allow you to copy the source package to the target Central Objects. The process will then configure it as the target package name (rename the repository tables).

Access the Data Load form.

Load Business Data (R98403 XJDE0021)

When selected, a form prompts for the source environment.

Load Control Tables (R98403 XJDE0022)

When selected, a form prompts for the source environment.

Central Objects and Versions (R98403 XJDE0019)

This UBE copies central objects and versions from the source environment to the target environment. All UBEs must run locally except for the server path code copy.

Check Out Records (R989861 XJDE0001)

This checks out the records for the package.

ESU History (R9672 XJDE0001)

This copies the ESU history for the package. The system automatically performs this function.

Copy Path Code, Pkg Dir on Deployment Server (R9800942 XJDE0001)

This copies either the path code on the local file system or the path code on the deployment server. If run from the deployment server, these are the same. This also copies the package definition records and package ini files.

Copy Path Code, Pkg Dir on Enterprise Server (R9894003 XJDE0001)

This copies the path code and the package directories on the enterprise server. This UBE is submitted to the enterprise server.

Copy Metadata Repository (R9894005 XJDE0001)

This copies the Metadata Repository (the package specifications) from the source package to the target package. It will copy the repositories both locally and on the enterprise database.

Rename Metadata Reposity (R9894005 XJDE0001)

This renames the tables in the target metadata repository. Click this option if you have copied the metadata repository on the server using the database commands.

Configure Package Manifest (R9894005 XJDE0002)

This configures the BLOB in the manifest table (F98770) in the target package repository. It will perform the configurations both locally and on the database server.

5.16.4.11 Environment Director Revisions

The Environment Director Revisions form is used to complete the environment creation actions.

At any point in the process you can press the Back button to go back and change an option, but if you click on the cancel button you will lose any answers you have given so far.

The final screen shows you what options were chosen. When you click on End it will start doing the copies. All UBEs are run locally except for the Enterprise Server Path Code copy, which is submitted to the enterprise server.

Access the Environment Director Revisions form.

Figure 5-17 Environment Director Revisions form

Description of Figure 5-17 follows
Description of ''Figure 5-17 Environment Director Revisions form''

Path Code

The path code is a pointer to a set of EnterpriseOne objects and is used to keep track of sets of objects and their locations within EnterpriseOne.

Enterprise Servers

The names of the computers that receive data from the clients.

Data Sources

The names that identifies the data source.

5.16.4.12 Table Conversion/Merge Log

The application writes history records into F984052. You can see the history by running Table Conversion / Merge Log (application P984052) on menu GH9611. Filter on conversion type 95.

Figure 5-18 Table Conversion/Merge Log

Description of Figure 5-18 follows
Description of ''Figure 5-18 Table Conversion/Merge Log''

5.17 Using Environment Director in the Express Mode

This section provides an overview of Environment Director in Express Mode and discusses how to create a new environment using the Express Mode.

5.17.1 Understanding Environment Director in Express Mode

You can use the Express mode to create a new environment by using new settings or settings copied from an existing environment. It is recommended that you use director mode rather than express mode to allow for greater control of new environment settings.

The Environment Director Express mode is designed to simplify the process of creating system environments. However, it is recommended that you use director mode rather than express mode to allow for greater control of new environment settings.

5.17.1.1 Actions Performed

After you enter all the settings for the new environment in Environment Director and click OK, the system performs these actions:

  • Creates OCM if it does not already exist.

  • Writes F98403 record for the new environment.

    Note:

    This enables Installation Planner (P9840) to display the environment.
  • Loads business data.

  • Loads control tables.

  • Configures enterprise servers.

  • Creates server map OCM.

  • Creates server map F98611 records.

  • Writes F9651 records for enterprise servers.

  • Configures BSFN and UBE mappings.

5.17.2 Prerequisites

While Environment Director is a useful tool for creating environments, we recommended using Installation Planner (P9840) and Installation Workbench (P9841) to create custom environments. Environment Director, Installation Planner and Installation Workbench share common functionality for configuring custom environments.

5.17.3 Forms Used with Environment Director in Express Mode

Form Name FormID Navigation Usage
Environment Director W989400A In Solution Explorer, navigate to System Installation Tools, Advanced Operations, Environment Director (P989400).

Click Next to begin.

Used to step you through the process of defining the components of a new environment including environment, path code, enterprise servers, and data sources.
Environment W989400B Complete the fields and click Next. Used to select the mode to be used for setup of the new environment.
Machines W989400J Complete the fields and click Next. Used to select the enterprise servers where the new environment will run. EnterpriseOne will use this information to populate the server map data sources on these servers.
Environment Director Revisions W989400L Verify the fields and click Next. Used to complete the environment creation actions.

5.17.4 Creating a New Environment in Express Mode

Access the Environment Director form.

5.17.4.1 Environment Director

The Environment Director steps you through the process of defining the components of a new environment including environment, path code, enterprise servers, and data sources.

Access the Environment Director form.

Figure 5-19 Environment Director form

Description of Figure 5-19 follows
Description of ''Figure 5-19 Environment Director form''

New Environment

Use this option to create a new environment with no default settings.

Copy Environment

Use this option to use settings from an existing environment as the default settings for the new environment. You can modify these settings if needed.

Note:

If you selected Copy Environment, click the search button in the Existing Environment field to select an environment from which you want to copy. The existing environment must be at the current release level as the new environment

5.17.4.2 Environment

The Environment form is used to select the mode to be used for setup of the new environment.

Access the Environment form.

Director

The director mode consists of screens for Environment, path Code, Enterprise Servers, Data Sources, and Data Load. The Environment Director Revisions form will be displayed at the end of the director.

Express

The express mode only enter Environment Name, Path Code Name, Enterprise Server and Port Number, and Default Data Source Type. The environment will be generated and you will skip to the Environment Director Revisions.

  • New Environment

    • Environment Name

      Enter a valid environment that encompasses both a path code (objects) and a data source (data).

    • Description

      Enter a user defined name or remark.

  • Share Existing Path Code

    Enter the name of the existing path code.

5.17.4.3 Machines

The Machines form is used to select the enterprise servers where the new environment will run. EnterpriseOne will use this information to populate the server map data sources on these servers.

Access the Machines form.

Machine Key

Indicate the name of the machine on the network (server or workstation).

Port Number

Identify the port for a given instance of EnterpriseOne. Because the JDE.ini file controls the port to which a workstation will connect, for workstations this port number is for reference only.

5.17.4.4 Environment Director Revisions

The Environment Director Revisions form is used to complete the environment creation actions.

Access the Environment Director Revisions form.

Figure 5-22 Environment Director Revisions

Description of Figure 5-22 follows
Description of ''Figure 5-22 Environment Director Revisions''

Path Code

The path code is a pointer to a set of EnterpriseOne objects and is used to keep track of sets of objects and their locations within EnterpriseOne.

Enterprise Servers

The names of the computers that receive data from the clients.

Data Sources

The names that identifies the data source.

5.17.4.5 Environment Director Completion

The Finish Environment Creation message is displayed to let you know that the environment is now ready to be configured. Use Back at any time to verify that the environment properties have been configured correctly before continuing.

Figure 5-23 Finish Environment Creation message

Description of Figure 5-23 follows
Description of ''Figure 5-23 Finish Environment Creation message''

The Environment Director Completion message is displayed when Environment Director has finished creating the new environment.

Figure 5-24 Environment Director Completion message

Description of Figure 5-24 follows
Description of ''Figure 5-24 Environment Director Completion message''

After you enter all the settings for the new environment in Environment Director and click OK, the system will create the new environment.

See the Actions Performed within the Understanding Environment Director in Express Mode section previously in this chapter.

5.18 Running Environment Director from Different Environments

This section provides an overview of Running Environment Director from different environments and discusses how to:

  • Use Object Management Workbench (P98220) to modify table data classes.

  • Use On Track Planning Setup (P98503) to modify table data classes.

5.18.1 Understanding How to Run Environment Director from Different Environments

It is recommended that you create custom environments from the JDEPLAN environment on the deployment server using Environment Director. Doing so creates the environment in the planner databases and deploys it to the system data source. The environment must exist in the planner databases to apply software updates to the environment.

You cannot run Environment Director from the deployment environment. The deployment environment exists only on the deployment server. It uses the bootstrap tables (F98611 and F986101) from the Planner; the remainder of the system tables are in the system data source. This split will cause inconsistencies between the planner and system definitions.

If you run Environment Director as a standalone, you should run it from a Windows client. The environment will be created in the system data source and needs to be copied to the planner environment before software updates can be applied to the environment. The Copy System to Planner program (R9698611) automates the process of copying the environment definition from system to planner.

5.18.1.1 Shared Versus Environment Data Source

Environment Director does not prompt for shared data sources. These data sources are shared by all environments and have already been configured and do not need to be reconfigured. By default, these are the System, Object Librarian, and Data Dictionary data sources. Only the environment data sources are configured. By default, these are the Business Data, Control Tables, Central Objects, and Versions data sources.

5.18.1.2 Database Configuration and Permissions

New databases, table spaces, and libraries must be created before Environment Director can load data into the new environment.

Typically, System, Object Librarian, and Data Dictionary data sources are shared with existing environments and do not need new databases. Business Data and Control Tables data sources, as well as any custom data sources, need new databases if these data sources are not being shared with another environment. Central Objects and Versions need new databases if the new environment will be using a new path code.

See Installing the System Databases in the JD Edwards EnterpriseOne Applications Release 9.0 Installation Guide (for your platform and database).

5.18.2 Understanding Data Source Configuration

This section provides descriptions of various data classes and source templates by environment.

5.18.2.1 Data Class

The data class is at the center of automatic OCM generation. It categorizes the type of data stored in data sources and tables. For example, Business Data is data class 'B' and System is data class 'S'. If you want to split business data into multiple data sources, you need to create a new data class, modify the data source template (so Environment Director or Installation Planner prompts for a data source) and assign tables and GT objects to that data class. OCM will be created based on the information provided previously.

5.18.2.2 Create a New Data Class

You can create a new data class by adding a value to the H96/DU UDC for data sources and H96/CL UDC for table and GT objects.

5.18.2.3 Data Source Templates by Environment

A data source template defines the set of data sources that will be used by new environments, and the default values for data source properties. The values are stored in the Data Sources by Environment table (F98511).

F98511 also stores the set of data sources for an environment after they have been generated from the template.

The Installation Planner and Environment Director programs use F98511 when prompting for data sources and when creating OCM mappings. When prompting for a data source, the programs will first check the Data Source Master table (F98611) to see whether it has already been defined. If so, Installation Planner and Environment Director will ignore the default settings in F98511 and prompt based on the existing data source definition.

You can edit the information in F98511 using the Data Source Templates By Environment program (P98503). This program enables you to implement custom environment naming standards and ease the creation of environments.

When creating a new environment, the system copies template records to create data sources for the environment and replaces tokens in the properties with values for the environment. Records with an environment value of *SHARED are used as a template for shared data sources. This is used once to set up the shared data sources, whereas new records with environment DEFAULT are created. Environment Director does not prompt for shared data sources; they must be set up from Installation Planner. The default set of shared data sources is system, object librarian, and data dictionary.

Records with an environment *ENV are used for new environment data sources. Whenever a new environment is created, the *ENV records are copied. The environment name replaces *ENV and tokens are replaced in order to receive the actual data source name and default properties. The default set of environment data sources is business data, control tables, central objects, and version. (The central objects data source is also specified on Path Code Master.)

Records with an environment *LOGIC are used for logic and server map data sources. These are set up when selecting an enterprise server.

5.18.2.4 Table Data Classes

The system uses a field in the Object Librarian Master table (F9860) to associate a table with a data class. You can modify table data classes using either of these programs:

  • Object Management Workbench (P98220)

  • On Track Planning Setup (P98503)

    Use this program to modify the data class for several tables at once.

Note:

Modifying the data class does not affect existing OCM mappings; the data class is only used when creating mappings for a new environment.

5.18.2.5 Data Load

Environment Director can automate data load for an environment using UBEs. Cases might exist, however, when you want to use third-party tools to load the data (that is, DTS, BCP, Import/Export, CPYLIB). In these cases, the default data load can be de-selected in the director.

5.19 Using Object Management Workbench to Modify Table Data Classes

This section discusses how to use Object Management Workbench (P98220) to modify table data classes.

5.19.1 Forms Used to Modify Table Data Classes

Form Name FormID Navigation Usage
Object Management Workbench W98220A Application Development, Object Management, Object Management Workbench(P98220). Used to modify table data classes.
Data Structure Design W9860AL In the Object Management Workbench form, click Find, then select an object from the tree in the left pane and click the Design. Used to modify table data structure.

5.19.2 Using OMW to Modify Table Data Classes

Access the Data Structure Design form.

Figure 5-25 Data Structure Design form

Description of Figure 5-25 follows
Description of ''Figure 5-25 Data Structure Design form''

Optional File

Specify the name of the optional file. Values are:

Y - Designates a file as an Optional Data File if there are some situations where the file may not be needed at a client installation. The explanation of these situations can be found in the Generic Rate/Message information for that file for Generic Rate/message Type 96/OF. All of these files that exist in a specified library can be listed in the Optional File Report on menu A9645.

O - Designates that the file is designated for omission. Examples are compile files or special files like JDE User Profiles file.

N - Not an Optional File.

Data Class

Select a code that classifies the type of data that is stored in an EnterpriseOne table. The standard classes are System, data Dictionary, Object Librarian, Business data, Control Tables, Central Objects, and Versions. When you create or modify OCM mappings for an environment, this value is used to associate this table to an EnterpriseOne data source (DATUSE).

Values are:

B - Business Data

C - Central Objects

D - Data Dictionary

I - Internal

O - Object Librarian

P - Installation Planner

S - System

T - Control Tables

V - Versions

Copy Data (Y/N)

Indicate if a file and its data are copied into production. A value of N moves the file without data during a file copy. When creating a production data library from JDFDATA, this field designates whether the data is included in the copy.

Global Build Option

Future Use.

EnterpriseOne Text

Future Use.

5.20 Using On Track Planning Setup to Modify Table Data Classes

This section discusses how to use On Track Planning Setup (P985033) to modify table data classes.

5.20.1 Form Used to Modify Table Data Classes

Form Name FormID Navigation Usage
Work With On Track Planning Setup W98503A In Solution Explorer, navigate to System Administration Tools, System Installation Tools, Advanced Operations, On Track Planning Setup(P98503). Used to modify table data classes.

5.20.2 Using On Track Planning Setup to Modify Table Data Classes

Access Work With On Track Planning Setup form.

Figure 5-26 Work With On Track Planning Setup form

Description of Figure 5-26 follows
Description of ''Figure 5-26 Work With On Track Planning Setup form''

Seq.

Future use.

Environment

Specify the name associated with a specific list of libraries. The J98INITA initial program uses these library names to control environments that the user can sign on to. These configurations of libraries lists are maintained in the Library List master File table (F0094).

This field represents a valid environment that can be used to run in EnterpriseOne. The environment encompasses both a path code (objects) and a data source (data). When put together, users have a valid workplace within the system.

Environment Description

Specify a user defined name or remark.

Load Data

Denote the type of data that is loaded for an environment.

Values are:

0 - No Data is loaded.

1 - Production data is loaded. Tables that are marked in the Object Librarian to copy data, such as constants tables, will load data in the table: the other data/transaction tables are created empty.

2 - Demonstration data is loaded. All tables are copied in.

Description

Specify a user defined name or remark.

Tble Conv

Denote whether the table conversions are performed for this environment.

Cont Tble

Denote whether the table merges are performed for this environment.

Spec Mrge

Denote whether the specification merges are performed for this environment.

Previous Environment

Specify the previous Environment is the existing environment that will be used as a base to create the new environment.