7/18/2019 Planner Update Special Instructions

Planner Update Special Instructions

Release: 9.1

Last Updated: January 10, 2019

Document Links
Introduction
Special Instructions for All
Special Instructions for Upgrades
Special Instructions for Tools 9.2 Client Install
Special Instructions for MSSQL on Windows Platform Pack
Special Instructions for Oracle on Windows Platform Pack
Special Instructions for DB2 UDB for LUW

Introduction

This ESU was created with special features that update the Planner path code on the Deployment Server. It includes all fixes for the release 9.1 installation
and upgrade process.

Note: When you deploy the Planner Update, that process does not do these Special Instructions, you must still do these Special Instructions.

Special Instructions for All

q Run SpecialInstrs.bat
q Copy ESU records to JDEPLAN environment
q Modify jde.ini for Package Build
q Add OCM for R9622C R9621S to all environments
q Update Visual Studio 2008 signature
q Refresh CNC data in JDEPLAN
q Apply this Update to your path codes
q For Tools 9.2.1 and above, add OCM for F00942T
q Add OCM for F958973 F958974 to JDEPLAN environment
q Copy F98613 to DEP910 environment

Run SpecialInstrs.bat

On the Deployment Server, start a cmd session with Run As Administrator, and navigate to the JDEdwards\E910\Planner\package\JM22365\scripts directory
(JM22365 being this ESU’s name). Run the SpecialInstrs.bat. It will update some records in your planner databases.

Copy ESU control records to JDEPLAN environment

This must be done on E910 Deployment Server or Deployment Client. You must run UBE R98403XB to copy any new Object Librarian, Data Dictionary, UDC
and other control table records to your JDEPLAN environment (before the upgrade process).

On the Deployment Server or Deployment Client, sign into JDEPLAN. In Batch Versions, find R98403XB XJDE0002 and run it. Click on the Record Selection
check box.

Data Selection:

The default data selection is:

F0004 F0005 F9000 F9001 F9843 F9843T F9603 F9860 F9862 F983051 F9200 F9202 F9203 F9207 F9210

Add F986101 to this list.

(Note: You should only copy F986101 once. If you already copied the OCM mapping records for F98700D, F98700H, and F98700R, you should not copy this
table F986101 again.)

Processing Options:

1. The path to the XML data for this ESU on your deployment server:

(For example, d:\JDEdwards\E910\planner\data\JM22365. Do not point the process to the location where your ESU was expanded; point to the location
within planner\data.)

file:///C:/Users/Jani/Desktop/UC/JM22365/E910SpecialInstructions.htm 1/6
7/18/2019 Planner Update Special Instructions
2. Environment: JDEPLAN

3. Target Data Source: Blank

4. Proof Mode: 1

5. Replace Duplicate Records: Y

6. Clear Target Table: N

If you see messages in the report that some tables were not opened in XML, check in the planner\data\JM22365 location. If those files do not exist in there,
it means there are no changes of that kind in this ESU. This is normal.

Verify OCM mapping for F98700D, F98700H, and F98700R

1. Run OCM in Fast Path

2. Highlight ‘Planner – 910’ and click ‘Select’

3. Put ‘JDEPLAN’ in Environment and ‘F98700*’ in Object Name grid field and click ‘Find’

4. Verify these 3 tables (F98700D, F98700H and F98700R) were mapped to ‘Versions Local’ for *PUBLIC (System Role) and Object Status was ‘AV’. If the
Object Status was ‘NA’, highlight the grid row, and click ‘Change Status’ from Row Menu to set Object Status to ‘AV’. Make sure sign off EOne after
changing the OCM Mapping Object Status.

Modify jde.ini for Package Build

The Administrator needs to update both the jde.ini on the deployment server (c:\Windows\jde.ini) and the client jde.ini template under <deployment server>\
<release>\OneWorld Client Install\misc. Without this change, Package Build will not work.

Add the “allowedFileExtensions” to the JDENET section of the jde.ini.

[JDENET]
allowedFileExtensions=.c;.h;.hxx;.ddb;.xdb;.cab;.Z;.log;.imp;.txt;.spc;.gif;.bmp;.jpg;.avi;.ico;.h_old;.c_old;.inf;.sts;.err;.tpl;.db;.cur;.rgs;.avi;.tdl;.rc2;.rc;.rh;.i

Through Server Manager, edit the jde.ini on all Enterprise Servers and make sure that all file types are listed in the entry as above. If you change the jde.ini,
stop and start services on that server.

Add OCM for R9622C R9621S for all environments

This must be done on the E910 Deployment Server or Deployment Client after applying this ESU to an environment, and before running the Package Build.

1. Run the OCM application, selecting System – 910.

2. Filter on an installed environment, for example DV910 R9621 (which should be mapped to LOCAL).

3. Copy and create a new entry for DV910 R9622C mapped to LOCAL.

4. Repeat for R9621S.

5. Activate new OCM mappings.

6. Repeat for all other installed environments, for example JDV910 PY910 JPY910 and so on.

Update Visual Studio 2008 signature

Microsoft regularly issues security updates which change the signature of some of the Visual Studio 2008 files. If your Deployment Server does not have the
relevant Microsoft fixes, you will get an error at run time saying the CINSTALL.dll cannot be loaded.

You can avoid the error by updating the VS/2008 runtime modules on the Deployment Server. (This does not affect signatures in packages you build on the
Deployment Server.)

The current CINSTALL.DLL manifest Version level is 9.0.21022.8

If the Deployment server has Visual Studio Installed, download the VS2008 patch from microsoft.com and install it on your Deployment Server (copy this link
and paste in your browser):

http://www.microsoft.com/download/en/details.aspx?id=26360

If the deployment server does not have the VS2008 installed then download the exe and run:

http://www.microsoft.com/download/en/details.aspx?id=26368

If you wish to distribute this to your Administrative / Development clients then download the exe:

http://www.microsoft.com/download/en/details.aspx?id=26368

1. Copy the vcredist_x86.exe file to the Deployment Server \\<Deployment_Server>\E910\OneWorld Client Install\ThirdParty\VSRunTime (overlaying the
older version that was shipped with 9.1 GA)

file:///C:/Users/Jani/Desktop/UC/JM22365/E910SpecialInstructions.htm 2/6
7/18/2019 Planner Update Special Instructions
2. After the deployment server install, run the vcredist_x86.exe file on the Deployment Server or Deployment Client from \\
<Deployment_Server>\E910\OneWorld Client Install\ThirdParty\VSRunTime

3. Include the VSRunTime feature in your package build.

Refresh CNC Data in JDEPLAN

The ESU process has changed to include automatic generation of OCM mappings and tables for tables that are not in Business Data. In order for this process
to work correctly, you must update the CNC information in JDEPLAN before applying any Tools related ESUs. Customers who have created custom
environments will have problems with OCM and table creation for any new Tools tables shipped with an ESU.

1. Signed into JDEPLAN, run R9840C and copy from System – 910 to Planner – 910. Choose Copy All Plan Components

2. Run the Data Source Templates By Environment application on menu GH9611. Copy records from an existing environment to add records for Control
Tables, Versions, Central Objects and Business Data for your custom environments. These Template records are used to generate OCM for your
custom environments. (The Template records for standard environments are shipped with the product.)

Apply this Update to your path codes

Note: If doing an Upgrade, apply this Update to your Pristine path code and build and deploy an update package, before running the upgrade for your DV / PY
/ PD environment. This Update contains fixes for the Table Conversion process, and the fixes are needed on the Enterprise Server.

This Planner Update contains changes to administrative applications that you likely will want to run on additional client machines, not just the Deployment
Server. Once you have completed your Install or Upgrade, apply this ESU to your installed path codes and include it in your next package build (server and
client package).

For Tools 9.2.1 and above, add OCM for F00942T

This only needs to be done once. This can only be done after the Tools Rollup ESU (containing F00942T) has been applied to at least one environment. You
only need to do this if you have not applied the Tools Rollup ESU to your default environment. (The ESU process generates OCM for tables in the ESU).

1. On the enterprise server, look at the jde.ini and find the [DB SYSTEM SETTINGS] section. Look at the Default Env setting.

2. Sign into JDEPLAN on the Deployment Server. Run the OCM application, selecting the System – 910 data source.

3. Find the OCM mapping for F00942T.

4. Copy it for the default environment.

5. Activate this mapping.

6. Repeat, selecting the Server Map data source.

Add OCM for F958973 F958974 to JDEPLAN environment

This must be done on E910 Deployment Server or Deployment Client signed into JDEPLAN before running the Installation Workbench.

1. Run the OCM application, selecting Planner - 910

2. Filter on JDEPLAN F96400 (which should be mapped to System Local)

3. Copy and create a new entry for JDEPLAN F958973 System Local

4. Repeat for F958974

5. Activate new OCM mappings.

Copy F98613 records to DEP910 environment

Note: You should do this step only if you already installed and applied the ESU JM12715 or a subsequent ESU containing F41001T1 to your current
environments. If you subsequently apply an ESU containing F41001T1, you should do this step at that time.

This must be done on E910 Deployment Server or Deployment Client. You must run UBE R98403XB to copy F98613 records to your DEP910 environment
(After the upgrade process).

On the Deployment Server or Deployment Client, sign into JDEPLAN. In Batch Versions, find R98403XB Add a new version F98613

Data Selection:

Set data selection to: BC Object Name is equal to “F98613”

Processing Options:

1. The path to the XML data for this ESU on your deployment server:

(For example, d:\JDEdwards\E910\planner\data\JM22365. Do not point the process to the location where your ESU was expanded; point to the location
within planner\data.)

file:///C:/Users/Jani/Desktop/UC/JM22365/E910SpecialInstructions.htm 3/6
7/18/2019 Planner Update Special Instructions
2. Environment: DEP910

3. Target Data Source: Blank

4. Proof Mode: 1

5. Replace Duplicate Records: N

6. Clear Target Table: Y

Special Instructions for Upgrades

q Update Upgrade Plan

Update Upgrade Plan

If you already created an Upgrade plan before installing this Planner Update, you will need to Finalize the plan again in order to get the updates to the Table
Conversion Schedule, the Control Table Merges and the Initial Tasks that were delivered with this Planner Update. (These updates were delivered through the
SpecialInstrs.bat and through the table copies in R98403XB.) To update your plan:

1. Highlight your plan and click on Finalize. Conversions that have already been run will be set to status 70.

Special Instructions for Tools 9.2 and Client Install

q Compress Data during first Package Build after deploying Tools 9.2

Compress Data during first Package Build after deploying Tools 9.2

After applying Tools 9.2, the Data.CAB needs to be compressed by the first full package for any path code where you are building a client package with Tools
9.2. Failure to do this will result in errors during the Client Install, as it will not be able to decompress the Data.CAB.

In Package Assembly when defining the full package, under the Compression tab, for Compression Options, select "Compress Data".

If you did not take the Tools Release through Server Manager, select "Compress Foundation" also. Otherwise the Client Install will not be able to decompress
system.CAB

This only needs to be done for the first package built for each pathcode.

Special Instructions for MSSQL on Windows Platform Pack

q Copy script for DV Central Objects attach

q Copy scripts for Custom Environment creation

Copy script for DV Central Objects attach

The script for attaching DV910 Central Objects – attach_CRP_CO.bat – refers to two non-existent files. This generates error messages in the logs. Please
copy the new version of attach_CRP_CO.bat from this ESU’s scripts directory into your install image before running the Platform Pack - for example,
x:\PPack910\mssql\scripts.

Note: This generates error messages but does not prevent the script from running successfully.

Copy scripts for Custom Environment creation

The script for creating custom environment Business Data and Central Objects databases is incorrect. Please copy the new version of
ce_InstallSQLDatabase.BAT and ce_JDESET.BAT from this ESU’s scripts directory into your install image before running them - for example,
x:\JDEdwards\mssql\scripts.

Special Instructions for Oracle on Windows Platform Pack

q Copy script for Central Objects load

file:///C:/Users/Jani/Desktop/UC/JM22365/E910SpecialInstructions.htm 4/6
7/18/2019 Planner Update Special Instructions
The script for loading Central Objects – LOAD_CO.BAT – does not load the package repository for PD910. Please copy the new version of LOAD_CO.BAT from
this ESU’s scripts directory into the x:\JDEdwardsPPack\E910\ORCL directory.

If you have already run the Platform Pack for the PD database component, once you have copied the new version of LOAD_CO.BAT, you can reload by doing
the following:

1. Connect to the oracle instance using sqlplus and delete the existing PD910 tables:

· DROP USER PD910 CASCADE;

2. Copy the ORCL_set.BAT to ORCL_set.BAT.sav. Edit the ORCL_set.BAT file and set PRECREATE_TBSP to YES and RUN_MODE to UPGRADE. Set all
environment choices except PD to NO for example,

· @set PROD=YES

· @set PRIST=NO

· @set CRP=NO

· @set DEV=NO

· @set SHARED=NO

· @set RUN_MODE=UPGRADE

· @set PRECREATE_TBSP=YES

3. Start a cmd Window with Run as Administrator and run InstallOracleDatabase.BAT

These steps will reload the Central Objects for PD910, and also correctly load the Package Repository for PD910FA.

Special Instructions for DB2 UDB for LUW

q Copy F986116 new records

q Configure F986116 new records

q JDBC driver for Deployment Server and Client

q ODBC data sources on Deployment Server

Copy F986116 new records

1. On the Deployment Server or Deployment Client, sign into JDEPLAN. In Batch Versions, find R98403XB XJDE0002 and run it. Click on the Record
Selection check box.

Data Selection:

Change the data selection to:

F986116

Processing Options:

1. The path to the XML data for this ESU on your deployment server:

(For example, d:\JDEdwards\E910\planner\data\JM22365. Do not point the process to the location where your ESU was expanded; point to the
location within planner\data.)

2. Environment: JDEPLAN

3. Target Data Source: Blank

4. Proof Mode: 1

5. Replace Duplicate Records: N

6. Clear Target Table: N

Repeat, copying to System - 910 (Target Data Source)

Configure F986116 new records

This step is not necessary if you have not yet created your Installation Plan. The Installation Planner will configure the records for you.

file:///C:/Users/Jani/Desktop/UC/JM22365/E910SpecialInstructions.htm 5/6
7/18/2019 Planner Update Special Instructions
1. On the Deployment Server or Deployment Client, sign into JDEPLAN:
2. Run application P986115 (Database Data Sources) on menu GH9611
3. Find Central Objects – DV910 and click on the row exit Database Sizing
4. In the Sizing application click on each record in turn and ensure that the correct operation system is in the Target Operating System column –
a. U for AIX
b. W for Windows
5. Save and repeat for each Central Objects data source in turn, then for System – 910.
6. Sign on to the DEP910 environment or to an Admin Client and repeat these steps for System – 910.

JDBC driver for Deployment Server and Client

In order to apply ESUs, you need to put the older JDBC driver (db2java.zip) on the Deployment Server in the x:\JDEdwards\E910\misc folder. The JDBC
driver for the Development or Admin client should be the new JDBC driver, db2jcc.jar and db2jcc_license_cu.jar1. Place these jar files in the
x:\JDEdwards\E910\OneWorld Client Install\ThirdParty\WebDevFeature\OH4A\JDBC or ..\H4A7\JDBC folder.

ODBC data sources on Deployment Server and Client

Verify that the ODBC data sources for the DB UDB databases have been created correctly on your Deployment Server and any Development or Admin client.
Run the executable c:\SysWOW64\odbcad32.exe and add the ODBC data sources if necessary for JDE910, JDE_P910, JDE_PROD, JDE_DEV, JDE_CRP.

file:///C:/Users/Jani/Desktop/UC/JM22365/E910SpecialInstructions.htm 6/6