steps for environment director

8/13/2019 Steps for Environment Director

1/17

Welcome to the demo of the Environment Director application. We will start by logging intoEnterpriseOne Solution Explorer in the JDEPLAN environment. We are logged in with the JDE User IDand password. We will then fast path to the GH9611 menu. On this menu, there is a selection forEnvironment Copy. This is where we can access the Environment Director program (P989400).

We will select the Environment Copy selection.

This application can be used to copy data, Central Objects. Path codes, packages and ESU History from one

environment to another predefined environment. Or it can be used to create a new environment, optionallycopying those same objects from an existing environment.

Note, there are options to copy definitions from the System Data Surce to Planner.If we select this option,it will copy environment definitions from the System Data Source to the Planner database on theDeployment Server. We will select this for our environment.


2/17

We also have options for "Environment Copy" mode. We may choose to Copy an existing environment orcreate a new environment by copying an existing environment.

We will select "Create/Copy to new environment."

The Environment Director will step you through the process of defining the components of a newenvironment including environment, pathh code, enterprise servers and data sources. You may click Cancelat any time to exit the Environment Director. If you do so, it should rollback or undo your changes.


3/17

We have the option to select a new environment or copy an existing environment.We will copy an existingenvironment to create a new environment.The Environment that we will copy will be the productionenvironment. We will go to the visual assist and select "PD900" for the production environment.


4/17

Once we have done this, we click "Next".


5/17


6/17

We may now specify properties for the new environment.If an existing environment is being copied, theproperties for that environment are presented as the defaults.

The Prefix is used for creating data sources. For example, prefix "PROD" will generate "Business Data -PROD" and "Control Table-PROD".

JAS is used for a Java environment, and stands for JAVA Application Server. This affects OCM mappingsfor logic.

We will define an environment name called ST900. Our description will e "E900 Staging Environment."

Our prefix for data will be "ST", and our release is "E900". We will not select JAS/WTS Environment atthis time. The entries for this form will eventually be inserted into the table F0094. This is the Library ListMaster, sometimes called the Environment Master Table.


7/17

We now have the option to "Select Share an Existing Path Code" in order to share an existing path codewith another environment, or to "Select Copy an Existing Path Code to copy an existing path code for useby the new environment.

We will select "Copy an Existing Path Code" and will copy PD900(for prodcution).

We also have the option to select a package name to copy and the new package name to be created.

We will copy the PD900FA(or full production package) to create the ST900FA( or full staging package).

There is also an option to "Check Disk Space".


8/17

If we select this option it will take some time to check the disk space on the Deployment Server. This is anew option that did not exist in E1 8.9.

After completing this option, we will select "Next".

We may now specify the properties for the new path code. The properties for the existing path code areused as the defaults for the new path code.

Our path code will be ST900.We will change the description to "E900 Staging Path".Our release is E900.We will Cumulative Description empty. Our Check in location is DENMLSAN030, which is ourDeployment Server. Our server share path is E900. We will choose the UNC for Universal Naming

Conventions, and our Deployment Data Source is "Central Objects - ST900".

The entries on this form will be inserted into the F00942 table, the Object Path Master.


9/17

We will now select enterprise servers where the new environments will run. EnterpriseOne will use thisinformation to populate the server map data sources on these servers.

Note we may click on this link to automatically select the enterprise servers from the existing environment.

We have the option to either remove an enterprise server by clicking on the blue arrow pointing to the left,or we may select from a list of available enterprise servers and use the blue arrow pointing to the right.

Note that we have now selected an enterprise server.


10/17

We will click "Next".

We are now on the Database Script Generator form. We will select Windows, but notice we have the optionfor Unix or iSeries. We will also select Oracle but notice we have the option for UDB or SQL Server. Thereare additional options for SQL Server Properties. These include the Database Server Name and DatabaseServer Path. These are not required for the Oracle database.


11/17

We will select "Next".

We are now on the Data Load form. We will select the optins to "Load Business Data" as well as "ControlTables". We will also take the default options to load "Central Objects", the "Check Out Records","Versions", and "ESU History". Note that we will also take the default options for "Copy Path, PackageDirectory on the Deployment Server" as well as "Copy Path Code Package Directory on the EnterpriseServer". Note that we have also selected "Copy Metadata Repository" as well as "Configure PackageManifest." We will also confirm that these have been completed after Environment Director runs.


12/17

After accepting these default options we will select "Next".


13/17

We will now define our Data Sources. We will start with Business Data, and enter "Business Data - ST."This will be for our staging business data. We will use an Oracle Database on a windows platform. Ourdatabase server name will be DENMLSAN030. Although this server is also our Deployment Server, in thereal world this would typically be a different name - either the name of your enterprise server or thedatabase server.

We will select the Oracle tab. The owner ID will be STDTA. This will point to an Oracle database schema.The database name is san030orcl. This is the connect string in the tnsnames.ora file.

We will selct the advanced exit. Note the options here for Unicode.We are using a Unicode database. We areallowing decimal shifting for the data dictionary. we are using Julian dates for JD Edwards. This is not an

OCM data source. We have selected Table Owner because we are using an Oracle schema.

We will select OK, and then we will select port. The database port field is empty; however, our Oracledatabase is listening on port 1521.

After reviewing our values, we will click OK.


14/17

We will now define the "Central Objects - ST900" data source in the Oracle database on a windowsplatform.

Our database server name is the same DENMLSAN030. We will click the Oracle tab. Note the Pwner Id isST900. Again, this is for an Oracle schema and our connect string will be san030orcl.

We will click the davanced exit. Once again it's a Unicode character set in the database. We will use JDEdwards data dictionary decimal shifting and Julian dating.

The database port is once again port 1521.

We will click OK.


15/17

We will now define the "Control Objects - ST900" data source in the Oracle database on a windowsplatform.

Our database server name is the same DENMLSAN030. We will click the Oracle tab. Note the Pwner Id isST900. Again, this is for an Oracle schema and our connect string will be san030orcl.

We will click the davanced exit. Once again it's a Unicode character set in the database. We will use JDEdwards data dictionary decimal shifting and Julian dating.

The database port is once again port 1521.

We will click OK and ok.


16/17

We will now define our versions Data Source. Our Data Source name will be "Version - ST900" for anOracle database on a windows. We will select our database server.

We will select the Oracle tab. Our Owner ID will be ST900. Note that this Owner ID or Schema name isshared with "Central Objects - ST900". Our database name once again will be our connect string ofsan030orcl.

We will click the advanced exit and review our options. Again this is a Unicode database, allowing decimalshifting with Julian dates. This is not an OCM Data Source, and we are using the table owner or schema.

We will click OK, and then the port. Note here the port says 1433. This is a Microsoft SQL Server port. Wewill change this to port 1521 for Oracle, and then click OK.

We will then click OK.


17/17

This is the Environment Director Revision form. We may select records here to make changes. Forexample, we can select the ST900 path code to review, including Deployment Server Location, Share Pathand Central Objects. We will click Cancel.

We may also select other parameters such as Path Code Data to see the Data Load Form. This will tell uswhat we will load for our data sources and path code. We will click Cancel.

We may select our Enterprise server and see it's definition. We will then click Cancel.

We may also select data sources. Here is the definition for Business Data - ST. We will selct Cancel.

We also have the options selct the Back button. This takes us back to our previous selection, or we mayclick next, which returns us to the Environment Director Revision form.

steps for environment director

Documents