2 Tasks

This chapter contains the following topics:

2.1 Required Sequence of Tasks

The following list presents the mandatory sequence of tasks necessary to upgrade to JD Edwards EnterpriseOne Tools Release 9.2.x:

  1. Disabling and Enabling Security

  2. Backing Up JD Edwards EnterpriseOne Directories and Tables

  3. Upgrading or Updating the Server Manager Management Console and Agents

    Important:

    As of JD Edwards EnterpriseOne Tools Release 9.2.x, you must install a Server Manager Agent on the Deployment Server.
  4. Installing Change Assistant

  5. Associating Environments with the Enterprise Server

  6. Backing Up the Oracle Universal Installer (OUI) Files

    Note:

    Upgrading the OUI is only required for JD Edwards EnterpriseOne Tools Release 9.2.2.x and later.
  7. Upgrading JD Edwards EnterpriseOne Tools Release 9.2.x

    Important:

    As of JD Edwards EnterpriseOne Tools Release 9.2.x, you install the EnterpriseOne Tools Release through Server Manager.
  8. Converting the Local Database Encryption with ReconfigureDB.exe

  9. Installing the Microsoft Visual Studio C++ 2010 Runtime X86 Redistributables

    For the Tools Release 9.2.3, you must install Microsoft Visual Studio C++ 2017 Redistributables and Visual Studio C++ 2010 Redistributables are not required.

  10. Installing and Applying the Planner Electronic Software Update (ESU) and Performing Special Instructions

  11. Applying the Current EnterpriseOne Tools Application Enhancement ASU and ESUs

  12. Deploying the ASI Using Change Assistant

  13. Building and Deploying the Full Package

  14. Implementing Post Installation Tasks

Important:

Following the above sequence is mandatory to upgrade to JD Edwards EnterpriseOne Tools Release 9.2.x.

2.2 Disabling Security History

You must disable the security history in the jde.ini file on the Security Server before you execute the ASI. Once the ASI has executed successfully you can enable the security history. The [SECURITY] section in the jde.ini file on the Security Server must include the History=0 prior to the initial execution of the ASI.

2.3 Backing Up JD Edwards EnterpriseOne Directories and Tables

The EnterpriseOne Tools Release download replaces the System directory and its subdirectories on the Deployment Server. Therefore, before you begin you should make a backup of the existing directory structure.

On the Deployment Server, make a copy of these directories:

  • /System

  • /Systemcomp

  • /OneWorld Client Install

It is also recommend to back up the JD Edwards EntertpriseOne tables. Follow the JD Edwards EnterpriseOne backup procedures.

See "Backing Up JD Edwards EnterpriseOne Tables" in the JD Edwards EnterpriseOne Administration Guide.

Note:

The ASI process now backs up the critical tables F952400, F952420, F00950W as xml files in the path code\package folder. You can restore these files through an uninstall path in the ASI.

2.4 Upgrading or Updating the Server Manager Management Console and Agents

You run the Server Manager Management Console installer in Upgrade mode if upgrading from one major Tools Release level to another, for example 8.98.x to 9.1.x. The installer detects if an existing installation exists and provides the option to upgrade that installation to the latest version that is compatible with the current EnterpriseOne Tools Release. If upgrading to revisions within a major release you can update the Console, for example upgrading from 9.1.2 to 9.1.2.4.

When upgrading to Tools Release 9.2.3x and later you must install Visual Studio 2017 redistributables before upgrading or updating the console and agents. The recommendation is to install both the 32-bit and 64-bit.

To upgrade or update Server Manager Console:

  1. Obtain the latest EnterpriseOne Tools 9.2.x version of the Server Manager Management Console or update from the Oracle Software Delivery Cloud.

  2. Verify the Management Console is stopped.

  3. Upgrade or update the Server Manager Console.

  4. Install an Agent on the Deployment Server, if not already installed.

  5. Use the standard functionality to obtain and run the updates for the Server Manager Agents on the target machines.

See "Working with the Server Manager Management Console" in the JD Edwards EnterpriseOne Tools Server Manager Guide.

2.4.1 Configuring Server Manager with Java 8 Update 201 and Later (Release 9.2.3.4)

If you are using Server Manager with Java 8 Update 201 and later (and equivalent Java 7 releases), you must perform the manual steps as described in "Configuring Server Manager Console with Java 8 Update 201 (and later) (Release 9.2.3.4)" in the JD Edwards EnterpriseOne Tools Server Manager Guide.

If you performed the configuration changes specified in the My Oracle Support document: Console Not Communicating With Agent And/Or Runtime Metrics Not Displaying After AS400 / iSeries / IBM Java Update Disables 3DES_EDE_CBC Algorithm (Doc ID 2256869.1), you must revert the modifications prior to performing the new manual steps.

2.5 Installing Change Assistant

The JD Edwards EnterpriseOne and World Change Assistant is a standalone Java application that helps you manage, download, and deploy JD Edwards EnterpriseOne packages. Change Assistant provides a single point of entry to facilitate administration of software updates and fixes.

You must install Visual Studio 2017 redistributables. The recommendation is to install both the 32-bit and 64-bit.

To install Change Assistant:

  1. Obtain Change Assistant from the Oracle JD Edwards EnterpriseOne Update Center.

    You can access the Update Center by using the following navigation from My Oracle Support:

    My Oracle Support | Patches & Updates tab | JD Edwards

  2. Select Electronic Software Updates from the News and Links pane on the left.

  3. Click the Download the Change Assistant Application link on the Update Center, Electronic Software Updates web page.

  4. The JD Edwards EnterpriseOne and World Change Assistant page opens providing information about Change Assistant features.

  5. Execute the steps in the Installing Change Assistant section.

See "Using Change Assistant" in the JD Edwards EnterpriseOne Tools Software Updates Guide.

Note:

JD Edwards EnterpriseOne Tools Release 9.2.2.x requires Change Assistant version 4.0.0.4 or above.

2.6 Associating Environments with the Enterprise Server

You associate environments with the Enterprise Server to automate the server map Object Configuration Manager (OCM) generation during the upgrade process.

  1. Log in to the JDEPLAN environment on the Deployment Server.

  2. Run the Work with Locations and Machines (P9654A) application.

    Description of imagec.png follows
    Description of the illustration ''imagec.png''

  3. Expand the Enterprise Server node and select your Enterprise Server.

    Description of imaged.png follows
    Description of the illustration ''imaged.png''

  4. Click Environments on the Form menu.

    Description of imagee.png follows
    Description of the illustration ''imagee.png''

  5. Add all environments associated with the path code you are upgrading on the Enterprise Server.

  6. Click OK and restart JD Edwards EnterpriseOne.

2.7 Backing Up the Oracle Universal Installer (OUI) Files

The installation of the Development Client and Webdevfeatures (WLSH4A and WASH4A) is accomplished using OUI 12.2.0.2.2.

Note:

This is required for JD Edwards EnterpriseOne Tools Release 9.2.2.x and later and must be performed before upgrading the Tools Release on the Deployment Server.

To back up the OUI files:

  1. Navigate to : <E1_dep_svr_install_directory>

  2. Rename the install and stage subdirectories under these three locations:

    • ..\OneWorld Client Install

    • ..\OneWorld Client Install\ThirdParty\WebDevFeature\WLSH4A

    • ..\OneWorld Client Install\ThirdParty\WebDevFeature\WASH4A

  3. Rename the backup special files from <E1_dep_svr_install_directory>

    Description of imagef.png follows
    Description of the illustration ''imagef.png''

2.8 Upgrading JD Edwards EnterpriseOne Tools Release 9.2.x

You locate information on fixes and enhancements in JD Edwards EnterpriseOne Tools Release 9.2.x through the Oracle Product Features, which you can access from www.LearnJDE.com.

Note:

When you upgrade a JD Edwards EnterpriseOneTools Release, ensure that the requisite JDK on the Enterprise Server and the Deployment Server meets the version requirements as specified in Oracle Certifications. If you need to upgrade the JDK, you should do so before you use Server Manager to deploy the new JD Edwards EnterpriseOne Tools Release. If an upgraded JDK version is applied on the target machine, it must be manually copied to the ..\system\jre folder on the Enterprise Server and Deployment Server for use by the Tools Release for JD Edwards EnterpriseOne.

To upgrade the latest EnterpriseOne Tools Release:

  1. Obtain the latest JD Edwards EnterpriseOne Tools Release from the Oracle JD Edwards EnterpriseOne Update Center.

  2. Download the latest JD Edwards EnterpriseOne Tools Release .par files for the appropriate server:

    • Deployment Server

    • Enterprise Server

    • HTML Server

    • AIS Server

  3. Using Server Manager Console upload the par files and distribute.

  4. Using Server Manager Console change the software component version for the server instance.

See "Installing an EnterpriseOne Tools Release on the Deployment Server" in the JD Edwards EnterpriseOne Deployment Server Reference Guide for your platform.

See Also:

JD Edwards EnterpriseOne Tools Server Manager Guide and JD Edwards EnterpriseOne HTML Server Reference Guide for your platform.

2.9 Converting the Local Database Encryption with ReconfigureDB.exe

ReconfigureDB.exe will encrypt the EnterpriseOne local database.

Note:

Do not run ReconfigureDB.exe on a local SQL Server Express database.
  1. Run ReconfigureDB.Exe

    Description of imageg.png follows
    Description of the illustration ''imageg.png''

  2. In the Change from password... area, select Legacy Encryption.

  3. In the To password area, select Enhanced Encryption.

  4. Click OK and then click Cancel to exit.

2.10 Installing the Microsoft Visual Studio Redistributables

All JD Edwards EnterpriseOne Windows machines receiving application foundation packages built with Microsoft Visual C++ 2010 or higher require the runtime libraries to be installed. For example, the Microsoft Visual C++ 2010 Redistributable Package (vcredist_x86.exe) installs runtime components of Visual C++ required to run applications developed with Visual C++ on a computer that does not have Visual C++ 2010 compiler installed.

You must download and install the Microsoft Visual Studio C++ 2010 Redistributable Package (x86) from:

http://www.microsoft.com/en-us/download/details.aspx?id=5555

For the Tools Release 9.2.3, you must download and install the Microsoft Visual Studio C++ 2017 redistributable package from:

https://visualstudio.microsoft.com/downloads/

All downloads > Other Tools and Frameworks > Microsoft Visual C++ Redistributable for Visual Studio 2017.

2.11 Installing and Applying the Planner Electronic Software Update (ESU) and Performing Special Instructions

Note:

You can view the required components on My Oracle Support - Required Components for JD Edwards EnterpriseOne Release 9.2 (Doc ID 2054020.1).

The Planner ESU contains special features that update the specifications and Dynamic Link Libraries (DLL) in the Planner path code. The Planner ESU distributes enhancements and fixes to the software programs. Planner ESUs have a .htm file that contains the Special Instructions for the software update. You will find the .htm file in the extracted directory for the Planner ESU.

To install Planner ESU:

  1. Obtain the Planner ESU from the Oracle JD Edwards EnterpriseOne Update Center.

  2. Click on Electronic Software Updates link in the News and Links section on the left-hand side of the screen.

  3. On the Electronic Software Updates main page, you will see a section marked Planner ESUs. Under the documentation links for Planner ESUs are links to the Planner ESUs, listed by EnterpriseOne application Release.

  4. Click the Get It Now link for the appropriate JD Edwards EnterpriseOne Application Release to be taken directly to the download for the Planner ESU.

    • 21358599 - JD Edwards Application Release 9.2

    • 19870568 - JD Edwards Application Release 9.1

    • 19889513 - JD Edwards Application Release 9.0

  5. Download to the Deployment Server.

  6. Run the self-extracting executable and follow the on-screen instructions to install the Planner ESU on the Deployment Server.

  7. Follow the steps in the Special Instructions, which are contained within an HTML file in the extracted Planner ESU directory.

    Note:

    It is recommended to apply the planner ESU to the path code that the ASI will be deployed to.

See "Running Software Updates" in the JD Edwards EnterpriseOne Tools Software Updates Guide.

2.12 Applying the Current EnterpriseOne Tools Application Enhancement ASU and ESUs

Note:

You can view the required components on My Oracle Support - Required Components for JD Edwards EnterpriseOne Release 9.2 (Doc ID 2054020.1).

To install the current Application Enhancement ASU:

Note:

This applies to JD Edwards EnterpriseOne Application Release 9.0 only.

Note:

The 9.2.x EnterpriseOne Tools Application Enhancement for Application Release 9.0 is an ASU for the Initial Release. ASUs cannot be deployed using Change Assistant.
  1. Obtain the current Application Enhancement ASU from the Oracle JD Edwards EnterpriseOne Update Center.

  2. Search and download the latest ASU, using JD Edwards EnterpriseOne for the search Type.

    • UDOE90* - Management of User Defined Objects ASU for E1 EnterpriseOne Tools 9.2

  3. Deploy using JD Edwards EnterpriseOne Work with Software Updates (P96470).

    1. Verify all JD Edwards EnterpriseOne processes are exited.

    2. Copy the ASU to the Deployment Server.

    3. Run the executable as Administrator.

      This will uncompress the contents of the ASU and prepare them for deployment through the JD Edwards EnterpriseOne Work with Software Updates.

    4. Open JD Edwards EnterpriseOne and launch JD Edwards EnterpriseOne Work with Software Updates (P96470), which you can access through menu GH9612- Run Application Software Updates.

    5. Select the latest UDOE90* grid row by double-clicking the row header.

    6. Click the Next button and follow the prompts to complete deployment.

To install the EnterpriseOne Tools ESUs:

Note:

This applies to JD Edwards EnterpriseOne Application Release 9.2 only.

Search, download, and deploy the ESU (and any dependencies) associated with the following bug:

  • 24710277

JD Edwards EnterpriseOne Application Release 9.1

Note:

This applies to JD Edwards EnterpriseOne Application Release 9.1 only.

Search, download, and deploy the ESU (and any dependencies) associated with the following bug:

  • 25980269

Note:

This applies to JD Edwards EntrpriseOne Application Release 9.0 only.

Search, download, and deploy the ESU (and any dependencies) associated with the following bug:

  • 21902097

2.13 Deploying the ASI Using Change Assistant

Important:

Before you execute the ASI on an AIX system with EnterpriseOne Tools Release 9.1.5 and earlier, you must perform the following steps:
  1. Log into JDEPLAN environment.

  2. Execute Object Configuration Manager (OCM).

  3. Select Planner-9xx OCM data source.

  4. Search on the following criteria to locate the default business function mapping:

    1. Environment = JXX9X0

    2. Type = BSFN

    3. Object = DEFAULT

  5. Select to deactivate the mapping.

  6. Log off all EnterpriseOne processes.

  7. Execute the ASI.

ASIs are special instructions for software updates executed automatically. They are downloaded separately from the software update you are installing, either using Update Center or Change Assistant. The JD Edwards EnterpriseOne Tools Release 9.2 ASI is a .par file and can be found using TL92* as a search criteria for the Update Name within the Update Center or Change Assistant. If you run the ASI then subsequently apply a new tools Release, you will need to re-run the ASI.

See: Appendix C: ASI Validations

See "Deploying Automated Special Instructions" on JD Edwards EnterpriseOne documentation on My Oracle Support (Doc ID 1486063.1).

To deploy ASI:

  1. Obtain the latest TL92* ASI for from the Oracle JD Edwards EnterpriseOne Update Center.

  2. Download and access with Change Assistant.

  3. On Change Assistant, expand the Work with Packages node.

  4. Navigate to the ASI package that you downloaded.

  5. Select the ASI package by checking the box next to the package.

  6. Click Deploy on the Work with Packages toolbar to start the ASI.

    Description of image_a.png follows
    Description of the illustration ''image_a.png''

    See: Appendix D: Errors and Warnings

  7. Click OK to continue.

    Description of imageaa.png follows
    Description of the illustration ''imageaa.png''

    Note:

    If you have changed the passwords for any table owners created during the Platform Pack installation, they must be defined in the jde.ini file. The ASI assumes that the table owner's password is the same as the table owner, unless it finds overrides in the jde.ini file on the Deployment Server.
  8. Verify the data source owner and password information

  9. Click Next to continue deploying new tasks.

    Description of imageab.png follows
    Description of the illustration ''imageab.png''

    The Select Deployment Type dialog box opens and presents the following options:

    • Install the ASI to the selected environment.

    • Uninstall the ASI from the selected environment.

    Note:

    The uninstall process only reverses the changes to the UDO tables. It does not uninstall any UDCs or the Rollup ESU.
  10. Select Install the ASI to the selected environment (Applications Release 9.0 9.1 only).

    Description of imageac.png follows
    Description of the illustration ''imageac.png''

  11. Click Next.

    Note:

    To access additional information on each step, click the Help button.
    Description of imagead.png follows
    Description of the illustration ''imagead.png''

  12. Click the Help button for details regarding this dialog box.

    Description of imageae.png follows
    Description of the illustration ''imageae.png''

  13. Click the X to close out of the Help dialog box.

  14. Select the target environment and click Next.

    Description of imageaf.png follows
    Description of the illustration ''imageaf.png''

  15. Click, Yes on Warning - Unknown Release.

    Description of imageag.png follows
    Description of the illustration ''imageag.png''

  16. Click, Yes on Warning - Transaction Data

    Description of imageah.png follows
    Description of the illustration ''imageah.png''

  17. For Applications Release 9.0 and 9.1 only, select, Include the upgrade tasks to run the UDO table conversions again. Otherwise click Next to execute new tools upgrades tasks.

    Release 9.2.0.5

    Description of imageai.png follows
    Description of the illustration ''imageai.png''

  18. Click Next to continue.

    Description of image_b.png follows
    Description of the illustration ''image_b.png''

  19. Click Next to continue.

    Description of imageba.png follows
    Description of the illustration ''imageba.png''

  20. At User Defined Object Naming Information, click Next to define a suffix to new UDOs.

    Description of imagebb.png follows
    Description of the illustration ''imagebb.png''

  21. On the Work with Web Object Names select a new UDO type.

  22. Update the Suffix and click OK.

    Note:

    The suffix should not be path code specific. UDOs retain the same names as they are promoted from path code to path code.

    Note:

    If you are on EnterpriseOne 9.2 (E920), you will skip to step 36.

    Release 9.2

    Description of imagebc.png follows
    Description of the illustration ''imagebc.png''

  23. Click Next.

    Description of imagebd.png follows
    Description of the illustration ''imagebd.png''

  24. Click Next.

    Description of imagebe.png follows
    Description of the illustration ''imagebe.png''

  25. Click Next.

    Description of imagebf.png follows
    Description of the illustration ''imagebf.png''

  26. Click Next.

    If F95240, F592420, F00950W, and F9000 tables have been backed up from a previous deployment, you can select to overwrite them or click Next to continue.

    Description of imagebg.png follows
    Description of the illustration ''imagebg.png''

    The ASI verifies the critical tables are in original format and skips the backup.

  27. Click Next.

    Description of imagebh.png follows
    Description of the illustration ''imagebh.png''

  28. Select the "Check to load OMW UDO Data" check box and click Next.

    Note:

    Check to load OMW UDO Data adds records in F98223 - Allowed Actions (Delete is being delivered for all UDOs) and F98225 - OMW Transfer Activity Rules for E900 and E910.
    Description of imagebi.png follows
    Description of the illustration ''imagebi.png''

  29. Enter a 1-6 character suffix to be used during the table conversion processes.

    WARNING:

    Invalid characters: !"#$%&'()*+-./:;<=>?@[\]^_`{|}~,

  30. Click the Help button to view suffix details.

    Description of image_c.png follows
    Description of the illustration ''image_c.png''

  31. Click the X to close.

    Description of imageca.png follows
    Description of the illustration ''imageca.png''

    Important:

    Read the Table Conversion Workbench instructions carefully. The instructions describe how to proceed with the dialog boxes to follow.
  32. Click the Help button to view Table Conversion Workbench details.

    Description of imagecb.png follows
    Description of the illustration ''imagecb.png''

  33. Click the X to close.

    Description of imagecc.png follows
    Description of the illustration ''imagecc.png''

  34. Click the Form menu, and then click Convert All.

    Note:

    Clicking Convert All starts the table conversions. When the table conversions are complete, a report will display the results.
    Description of imagecd.png follows
    Description of the illustration ''imagecd.png''

  35. Click Close on the Table Conversion Workbench.

    Note:

    Follow the recommended course of action displayed on the dialog box for any failed table conversion.
    Description of imagece.png follows
    Description of the illustration ''imagece.png''

  36. Execute table conversions manually.

    The ASI will only prompt you to run the table conversions if it has detected data in F980052 in the System - xxx data source and no data in F980052 in the associated Control Tables data source.

    Surrounding text describes tc.png.

    You will see the above dialog appears only if F980051, F980052, and F980053 tables in the wrong format and have records in the F980052 table.

    Note:

    The following information assumes the ASI has been applied to target environment DV9X,X which has an associated WAN environment of JDV9XX. The associated WAN environment is to be used as the source environment for the table conversions.

    Verify whether there are any records in your version of these three tables in System - xxx. You won't be able to use Universal Table Browser, you will need to use sqlplus / strsql or other database tool. If there are no records, no action needs to be taken. The ASI will have generated the tables for you into the Control Tables - xxx data source for your target environment.

    The ASI will have applied the correct .par file to your Deployment Server.

    The ASI will have reset the OCM for these 3 tables to point to Control Tables - xxx for the environment you applied the ASI to, plus any other environments that share the same path code.

    Your source and target environment for the table conversion must be different. The ASI has set the OCM for these three tables to System - xxx for the WAN environment (JDV9XX) associated with the environment you ran the ASI against.

    Run the table conversions one at a time signed into JDEPLAN and submit from Batch Versions. Click on Properties and change the source environment to JDV9XX and the target environment to DV9XX.

    Once the TCs have run, reset the OCM in JDEPLAN for the source environment to point to the Control Tables - xxx again.

    If you have multiple environments with different Control Tables associated with this path code, copy the output table from the table conversion to each of the environments' Control Tables. For example:

    • You have DV920 JDV920 DV920XX DV920YY and DV920XX and YY have their own unique Control Tables.

    • Run the table conversion against JDV920 DV920, and then copy the F980051, 52, 53 from Control Tables - Test to the Control Tables for DV920XX and DV920YY.

  37. Click Finish.

Release 9.2.4

You may need to run the following table conversion programs after the ASI completes.

To determine if the following table conversions are necessary, run R9696713 selecting F980051 and F980052 in the Control Table data source.

If you have multiple environments in each path code, run the following for each Control Table data source associated with the target path code:

  • R89980051A|XJDE0001 - Change Primary Key for F980051

  • R89980052A|XJDE0001 - Change Primary Key for F980052

Verifying ASI Table Conversions

It is recommend to verify the success of the ASI table conversions by verifying:

  • Tables

  • Security

  • Runtime

Tables

Release 9.2.3.1

Use the following grid to verify the UDO tables:

UDO Table Verification
One View Reports and EnterpriseOne Page F952400 Has the WOBNM column.
EnterpriseOne Watchlist F952420 Has the WOBNM column.
Queries F952430 Has the same record count as F98950.
Grid Formats F952440 Has the same record count as F98950.
CAFE1 F952450 Has the same record count as F98950.

Security

You use (P00950) to verify that the UDOs have the same level of security as before the EnterpriseOne Tools Release upgrade.

Runtime

After the ASI runs, you should verify access to UDO is the same as before the EnterpriseOne Tools Release upgrade.

If the ASI halts or table conversions do not successfully run, it is recommended to fix the error and run the ASI uninstall program. The ASI uninstall program performs several clean-up operations, table clean-up, and restoring. This action will allow you to run the ASI as if it is the first time.

Note:

Verify the F00165 table in Business Data has the F00165_5. If this does not exist, run the R9698713 UBE which will generate missing indexes.

2.14 Building and Deploying the Full Package

Note:

Prior to building a full package you will have to increase the Central Object database by two gigabytes.

EnterpriseOne Tools Release 9.2.1.x and above, contains enhancements to the package build process. All Object Librarian type records are inserted into a database repository. The object types inserted are:

  • Business Functions (BSFN and NER)

  • Table (TBLE)

  • Applications (APP)

  • Reports (UBE)

  • Data Structure (DSTR)

  • Business Views (BSVW)

  • Media Objects (GT)

  • Business Services(SBF)

Every object will have a record with a .par file in the Repository table (F98780R) and the History table (F98780H). Both tables are located in the Central Objects data source.

For more information see "Building Packages" in the JD Edwards EnterpriseOne Tools Package Management Guide.

2.15 Implementing Post Installation Tasks

2.15.1 Uploading Existing Media Objects to the Database

Starting with EnterpriseOne Tools Release 9.2.1 it was mandatory to store media objects to the database. In EnterpriseOne Tools Release 9.2.1.4 and beyond, you have the option to store media objects to the file system.

To insert existing media objects to the database:

  1. Run R98MODAT UBE to insert existing media objects to the database (personal and shared).

    Note:

    By default, JD Edwards EnterpriseOne will store media objects to the database.

    See "Uploading Media Object Files to Database" in JD Edwards EnterpriseOne Tools Runtime Administration Guide and Oracle Support document #2295043.1.

2.15.2 Generate Index (Release 9.2.3.2)

A new index is added to F00165 to support new functionality. Run R9698713 to create the F00165_5 index in F00165.

To generate the index on F00165:

  1. Log into JDEPLAN on the Deployment Server.

  2. Execute Batch Versions and search for R9698713.

  3. Change the Data Selection to F00165.

  4. Change the Processing Options to:

    Surrounding text describes index.png.
  5. Click OK.

Run this against the Business Data for each of your environments that are on Tools Release 9.2.3.2 and above.

2.15.3 Associating Converted UDOs with Default Projects.

To associate converted UDOs to default projects:

See "Building Packages" in the JD Edwards EnterpriseOne Tools Package Management Guide.

Note:

In order for the UBE to run properly, you must set the external role for users outside OMW to 02-Developer. You do this by clicking on the Constants icon in the P98230 application.
  1. Run UBE R98222UDO/XJDE0001 from a web client to add converted objects to default projects.

    R98222UDO performs the necessary steps to create the default project for the personal objects and corresponding records so that the end user can make modifications to their personal objects.

    The UBE runs over the F9861W table and checks if the object exists in any current project. If the object exists, that information is written to the report and nothing is done with the object.

    If the object does not yet exist in a project, the UBE will:

    Check if the default project for the user who created the object exists.

    If it does not exist:

    Create the default project; add the user as a developer and originator.

    If it does exist:

    Check if the user has the role of developer or originator and add accordingly.

    Add the object to the default project.

    Update the Object Management Workbench (OMW) object record to indicate that this object is checked out to the default project.

  2. In order for end users to be able to view, create, and modify UDOs, you must confirm setup of Allowed actions. The security works tightly with OMW allowed actions, which you must set up prior to creating security records. The OMW allowed actions are:

    1. Copy (06)

    2. Reserve (03) - checkout

    3. Delete (04)

    4. Add (05)

    5. Remove from Project (12)

    6. Add Object to Project (16)

    7. Remove Reservation (30) - erase checkout

      See JD Edwards EnterpriseOne Tools Object Management Workbench Guide and JD Edwards EnterpriseOne Tools Security Administration Guide.

    8. In order to transfer a UDO from one path code to another, you must confirm the transfer activity rules in Object Management Configuration (OMC). You setup these transfer activity rules as you would for a regular Object Librarian object (i.e. APPL) with the source and target path codes.

2.15.4 Updating the Oraparam.ini files

Note:

When updating to a Tools Release prior to 9.2.1.x, no steps other than applying the Tools Release via Server Manager are required.

The Tools upgrade process does not update the oraparam.ini files for the Development Client installer, WebLogic H4A (WLSH4A) installer, and WebSphere H4A (WASH4A) installer. You must perform the steps below to update the oraparam.ini files. Different steps are required if you are updating to Tools Release 9.2.1.x or 9.2.2.x.

Tools Release 9.2.1.x

In Tools Release 9.2.1.x, the version of the JDK that is shipped with the Oracle Universal Installer (OUI)-based installers (i.e., Development Client, WLSH4A, and WASH4A) was changed from version 1.6.0.21.51 to 1.7.0.121.0.

Update the oraparam.ini for the Development Client installer:

  1. Navigate to: <E1_dep_svr_install_directory>\OneWorld Client Install\install and copy the oraparam.ini file with a new name of oraparam - copy.ini.

  2. Locate the BOOTSTRAP_COMPS= line in the oraparam.ini file.

  3. Update the JDK value to: 1.7.0.121.0

    • From:

      BOOTSTRAP_COMPS="oracle.swd.oui:11.2.0.2.0,oracle.swd.oui.core:11.2.0.2.0,oracle.jdk:1.6.0.21.51"

    • To:

      BOOTSTRAP_COMPS="oracle.swd.oui:11.2.0.2.0,oracle.swd.oui.core:11.2.0.2.0,oracle.jdk:1.7.0.121.0"

Update the oraparam.ini for the WLSH4A installer (If you are implementing WebLogic H4A (WLSH4A).

  1. Navigate to <E1_dep_svr_install_directory>\OneWorld Client Install\ThirdParty\WebDevFeature\WLSH4A\install and copy the oraparam.ini file with a new name of oraparam - copy.ini.

  2. Locate the BOOTSTRAP_COMPS= line in the oraparam.ini file.

  3. Update the JDK: value to 1.7.0.121.0

    • From:

      BOOTSTRAP_COMPS="oracle.swd.oui:11.2.0.2.0,oracle.swd.oui.core:11.2.0.2.0,oracle.jdk:1.6.0.21.51"

    • To:

      BOOTSTRAP_COMPS="oracle.swd.oui:11.2.0.2.0,oracle.swd.oui.core:11.2.0.2.0,oracle.jdk:1.7.0.121.0"

Update the oraparam.ini for the WASH4A installer (If you are implementing WebSphere H4A (WASH4A).

  1. Navigate to <E1_dep_svr_install_directory>\OneWorld Client Install\ThirdParty\WebDevFeature\WASH4A\install and copy the oraparam.ini file with a new name of oraparam - copy.ini.

  2. Locate the BOOTSTRAP_COMPS= line in the oraparam.ini file.

  3. Update the JDK: value to 1.7.0.121.0:

    • From:

      BOOTSTRAP_COMPS="oracle.swd.oui:11.2.0.2.0,oracle.swd.oui.core:11.2.0.2.0,oracle.jdk:1.6.0.21.51"

    • To:

      BOOTSTRAP_COMPS="oracle.swd.oui:11.2.0.2.0,oracle.swd.oui.core:11.2.0.2.0,oracle.jdk:1.7.0.121.0"

Note:

The installer in the folder <E1_dep_svr_install_directory>\OneWorld Client Install\ThirdParty\WebDevFeature\H4A85 is obsolete. You can delete this folder; however, it does not hurt to keep it.

Tools Release 9.2.2.x

The OUI in Tools Release 9.2.2.x includes:

  • An OUI version upgrade from 11.2.0.2.0 to 12.2.0.2.2.

  • The oracle.swd.oui.core.min component.

  • A JRE instead of a JDK.

Update the oraparam.ini for the Development Client installer:

  1. Navigate to: <E1_dep_svr_install_directory>\OneWorld Client Install\install and copy the oraparam.ini file with a new name of oraparam - copy.ini.

  2. Locate the BOOTSTRAP_COMPS= line in the oraparam.ini file.

  3. Comment out the existing line by adding # at the start of the line, for example:

    #BOOTSTRAP_COMPS="oracle.swd.oui:11.2.0.2.0,oracle.swd.oui.core:11.2.0.2.0,oracle.jdk:1.x.x.xx.xx"

  4. Add the following new line immediately after the existing line:

    BOOTSTRAP_COMPS="oracle.swd.oui:12.2.0.2.2,oracle.swd.oui.core:12.2.0.2.2,oracle.swd.oui.core.min:1 2.2.0.2.2,oracle.swd.jre:1.8.0.45.0"

  5. Find the line that starts with OUI_VERSION=

  6. Comment out the existing line by adding '#' at the start of the line, for example:

    #OUI_VERSION=11.2.0.2.0

  7. Add the following new line immediately after the existing line

    OUI_VERSION=12.2.0.2.2

Update the oraparam.ini for the WLSH4A installer (If you are implementing WebLogic H4A (WLSH4A).

  1. Navigate to <E1_dep_svr_install_directory>\OneWorld Client Install\ThirdParty\WebDevFeature\WLSH4A\install and copy the oraparam.ini file with a new name of oraparam - copy.ini.

  2. Locate the BOOTSTRAP_COMPS= line in the oraparam.ini file.

  3. Comment out the existing line by adding '#' at the start of the line, for example:

    BOOTSTRAP_COMPS="oracle.swd.oui:11.2.0.2.0,oracle.swd.oui.core:11.2.0.2.0,oracle.jdk:1.x.x.xx.xx"

  4. Add the following new line immediately after the existing line

    BOOTSTRAP_COMPS="oracle.swd.oui:12.2.0.2.2,oracle.swd.oui.core:12.2.0.2.2,oracle.swd.oui.core.min:12. 2.0.2.2,oracle.swd.jre:1.8.0.45.0"

  5. Locate the line that starts with OUI_VERSION=

  6. Comment out the existing line by adding # at the start of the line, for example:

    #OUI_VERSION=11.2.0.2.0

  7. Add the following new line immediately after the existing line

    OUI_VERSION=12.2.0.2.2

Update the oraparam.ini for the WASH4A installer (If you are implementing WebSphere H4A (WASH4A).

  1. Navigate to <E1_dep_svr_install_directory>\OneWorld Client Install\ThirdParty\WebDevFeature\WASH4A\install and copy the oraparam.ini file with a new name of oraparam - copy.ini.

  2. Locate the BOOTSTRAP_COMPS= line in the oraparam.ini file.

  3. Comment out the existing line by adding '#' at the start of the line, for example:

    #BOOTSTRAP_COMPS="oracle.swd.oui:11.2.0.2.0,oracle.swd.oui.core:11.2.0.2.0,oracle.jdk:1.x.x.xx.xx"

  4. Add the following new line immediately after the existing line

    BOOTSTRAP_COMPS="oracle.swd.oui:12.2.0.2.2,oracle.swd.oui.core:12.2.0.2.2,oracle.swd.oui.core.min:12. 2.0.2.2,oracle.swd.jre:1.8.0.45.0"

  5. Find the line that starts with OUI_VERSION=

  6. Comment out the existing line by adding # at the start of the line, for example: #OUI_VERSION=11.2.0.2.0

  7. Add the following new line immediately after the existing line

    OUI_VERSION=12.2.0.2.2

Note:

The installer in the folder <E1_dep_svr_install_directory>\OneWorld Client Install\ThirdParty\WebDevFeature\H4A85 is obsolete. You can delete this folder; however, it does not hurt to keep it.

2.15.5 Update JDBC Drivers

Ensure the H4A installer (WLSH4A or WASH4A) has the latest JDBC driver files for the currently supported database versions. These files should be in the subdirectory called JDBC under the WLSH4A and WASH4A directories. The drivers are copied to the Development Clients during the H4A installations and are used by the H4A web clients to connect to various databases. This JDBC subdirectory must contain only the latest drivers and no obsolete drivers.

Important:

You must delete any obsolete driver files. Check Oracle Certifications for the latest drivers.

2.15.6 Development Client Installation Consideration for Tools Release 9.2.2.x and Greater

Running a version 12.2 installer to install a package on an existing Development Client that used version 11.2 OUI could cause issues. Although not required, Oracle highly recommends that the previous Development Client installation be saved via Snapshot or uninstalled before running a new installer.

2.15.7 Development Client Installation Consideration for Tools Release 9.2.3.x and Greater

You must install Visual Studio 2017 redistributables before installing the client and web dev feature. The recommendation is to install both the 32-bit and 64-bit.

2.15.8 Uninstalling ASI

To uninstall the ASI:

Note:

This is for Applications Release 9.0 and 9.1 only. The uninstall process reverses the table conversions that were performed during the install, uninstall will not remove new UDC values or OCM mappings.
  1. Deploy the ASI through Change Assistant.

  2. On Select Deployment Option, select Uninstall the ASI from the selected environment.

  3. Click Next.

    Description of imagecf.png follows
    Description of the illustration ''imagecf.png''

    Note:

    The JD Edwards EnterpriseOne 9.2 Tools Release, EnterpriseOne Tools Application Enhancement ESU, and Planner ESU will not be uninstalled.
  4. Click Next.

    Description of imagecg.png follows
    Description of the illustration ''imagecg.png''

  5. Click Next.

    Post Install UBE R98222UDO warning.

    Description of imagech.png follows
    Description of the illustration ''imagech.png''

  6. Click Next.

    Description of imageci.png follows
    Description of the illustration ''imageci.png''

  7. Select Exit the uninstall process....and click Save and Exit to complete the uninstall process.

    Select Re-run the install process.....and click Next to start the ASI installation.

    Description of image_d.png follows
    Description of the illustration ''image_d.png''

  8. Click Finish.