Oracle by Example brandingMigrating JD Edwards EnterpriseOne to Oracle Cloud for Linux

section 0Before You Begin

This tutorial provides instructions for migrating your JD Edwards EnterpriseOne data from an on-premises system with Oracle database on Linux to Oracle Cloud.

Time to Complete

1-2 Hours

Note that this estimate completion time is not the elapsed time. That is, it does not account for machine runtime functions.

Background

Currently, the Oracle Cloud Migration Utility only supports the migration of a single pathcode from your on-premise environment to the Compute Service instance environment. You can only run this process a single time from end to end.   However, you do have the option to import from one on-premise pathcode to a different pathcode on the Compute Service instance.  For example:  you can export your on-premise PD920 environment and import to DV920 on the Compute Service instance.  The utility has scripts packaged within the database migration that will synchronize the database records accordingly. 

Before starting the Migration process, make sure all traditional objects are checked in for the pathcode you plan to migrate.  Project information will not be migrated to the Compute Service instance. User Defined Objects (UDOs) that are reserved to a real project, will be moved to the users default project at the end of the migration process.

The Oracle Cloud Migration Utility can be used only if the on-premises environment is running at least Tools release 9.2.x with Applications 9.1 and later. After the migration is complete, your cloud compute instance will be running the same applications release as your on-premises environment.

Supported on-premises environment:

  • Enterprise One Applications release 9.1 and later
  • Enterprise One Tools 9.2
  • Oracle database on Linux

Note: It is recommended that you load the media objects to the database by setting up and running R98MODAT prior to running the migration export for tools releases 9.2.1 and higher. For tools releases prior to 9.2.1, you need to downgrade the Oracle Cloud environment to the same release as the on-premise tools release and reset F00942T for the applicable path codes prior to running the import part of the migration. See Uploading Media Object Files to Database in the JD Edwards EnterpriseOne Tools Runtime Administration Guide.

  • Oracle database on Linux

The Deployment Server migration will be performed by the Oracle Cloud Migration Utility and database scripts. The Oracle Cloud Migration Utility is deployed using Change Assistant. The migration has the following two parts:

  1. Export – execution on the on-premise Deployment Server and Database Server.
  2. Import – execution on the Deployment Server and Database Server on the Compute Service instance.

The Oracle Cloud Migration Utility export process exports system table data and pathcode folders (Solution Explorer, media objects, source, include, res, java). While the database scripts export Business Data and Shared Data (for example: Object Librarian and Data Dictionary).

The import process imports the system table data as Append Only and F9860W, F9861W data as Replace Table along with Business Data and pathcode folder structures on the Deployment Server.

The current deliverable is called JDE_9.2_Migration_Utility_3.1_for_Linux (JDE_OPC_Migration_3.0.par) and can be downloaded from the Oracle JD Edwards EnterpriseOne Update Center. To locate this deliverable in the Update Center, select JD Edwards EnterpriseOne from the Type field in the Search tab, and then enter the name of the migration utility in the Search for Name field.

In this tutorial you will:

  • Execute Oracle Cloud Migration Utility on on-premise Deployment Server.
  • Run export script on the on-premise Database Server.
  • Execute Oracle Cloud Migration Utility on the Deployment Server on the Compute Service instance.
  • Run import script on the Database Server on the Compute Service instance.

What Do You Need?

To perform the steps in this tutorial, you must have:

  • A subscription to Oracle Cloud. You must be a user with the Compute Operations role. For more information, see How to Begin with Oracle Compute Cloud Service Subscriptions in Using Oracle Compute Cloud Service.
  • Verified the database size on the Compute Service instance is large enough for the import and that database configuration / parameters are validated or tuned for your business needs (for example: max extend and extend size parameters).
  • Installed the latest Change Assistant on the on-premise Deployment Server and the Deployment Server on the Compute Service instance.
  • Downloaded the JDE_OPC_Migration_3.0.par from the Oracle JD Edwards EnterpriseOne Update Center.

    The JDE_9.2_Migration_Utility_3.1_for_Linux (JDE_OPC_Migration_3.0.par) contains:

    • TLOPCV3_20_99.par (Move this file to the on-premise Deployment Server.)
    • Export folder with export scripts (Move this folder to the on-premise Database Server.)
    • Import folder with import scripts (Move this folder to the Database Server on the Compute Service instance.)
  • Verified you can execute the following command on the source and destination machines;<dbuser>/<dbpass>@<netname> .

Note: The Oracle Cloud Migration Utility assumes that the on-premise Deployment Server and the Deployment Server on the Compute Service instance are identical. This includes the date format of the operating system. To avoid errors, verify the date formats on both servers are identical prior to executing the Oracle Cloud Migration Utility.

section 1Execute Oracle Cloud Migration Utility on On-Premise Deployment Server

The Deployment Server migration migrates pathcode files (source, include, res, java, Solution Explorer,and media objects) from the on-premise Deployment Server to the Deployment Server on the Compute Service instance.

  1. Start Change Assistant on the on-premise Deployment Server.
  2. Expand the Work with Packages tree node and select Downloads.
  3. Select Cloud Migration Utility (TLOPCV3_20_99.par) from within Change Assistant.
  4. Select New Batch Deploy.
  5. Verify the Batch Information dialog box and click OK.
  6. Sign in to the JDEPLAN environment.

After initialization, Cloud Migration Utility – Export displays, indicating what actions are performed.

  1. After reviewing the actions, click Next.

    2. Deployment Server Export
    Deployment Server Export

  1. On Object Path Search & Select, select a pathcode to export.
  2. On Deployment Synchronization Warning, select Synchronize CNC Data Now (R9840C/XJDE0002).

Only select Work with Environment Data Sources? (GH9611/P98503)?* if you have custom environments and then click Next.

    Deployment Server Export
    Deployment Synchronization Warning

  1. Verify the Copy System/Plan Information Report (R9840C/XJDE0002) has Completed Normally in the Result column.
    2. Deployment Server Export
    Copy System/Plan Information Report
  1. On Work With Environment Data Sources, select the environment to copy from and click Add.
  2. Select Include Pathcode Files and Include System Data, and then click Next.
    3. Deployment Server Export
    Export Options
  1. Review the reports generated during the export of the system tables and ensure they were successful.
  1. The Save & Exit, Export dialog box signals the end of the export process for the On-premise Deployment Server. Review the listed tasks and click Save and Exit.
    2. Save & Exit, Export
    Save & Exit, Export
  1. On the Confirm dialog box, click Yes.

Note: At this point a batch has been created in Change Assistant.

  1. Return to Change Assistant, select the Work with Batches tree node.
  2. Select your batch and click Export to jar.
  3. Indicate a name and location to save the .jar file, and click Save.
  4. On the Select Deployment Location dialog box, click Cancel.
  5. Transfer the .jar file to the Deployment Server on the Compute Service instance.
  6. Exit Change Assistant.

section 2Run Export Script on On-Premise Database Server

The export.sh script exports data from the on-premise database into dump files, which can be moved to the Database Server on the Compute Service instance.

  1. Navigate to where you downloaded the export files on the on-premise Database Server (for example: /u01/scripts).
  2. Edit the exp_set file with your information.
    3. This image shows the exp_set file.
    The exp_set file.

    Field
    		 Description
    PATHCODE_PREFIX The pathcode to export. Valid values are:PY, PD, DV, and PS.
    PATHCODE_RELEASE The patchode to export. Valid values are: 920 and above.
    SHARED Export data dictionary and object librarian schemas. YES, must be used for migration.
    DUMP_DEST The full path where you want the database dump files created.
    *Ensure the directory exists*
    DBUSER The database user with privileges to the tablespaces being exported (for example: system).
    DBPASS The password for the DBUSER.
    Note: If your database password contains any allowable special character like $ you must put single quotes around the database password in both the exp_set and the imp_set files. For example, if your database password includes a $ symbol, you would specify this value like this:
    DBPASS='Hello$123'
    NETNAME The TNS name for the database (for example: orcl).
  1. Save and close exp_set.:
  2. Run export.sh.
  3. Verify “successfully completed” is found in all generated log files and .dmp files were successfully created in the specified location.
  4. Transfer the .dmp files to a folder on the Database Server on the Compute Service instance for importing in a later step.

section 3Execute Oracle Cloud Migration Utility on Deployment Server in Oracle Compute Cloud Instances

Import the .jar file with Change Assistant on the Deployment Server on the Compute Service instance.

Note: Verify that the ActivConsole is not running.

  1. Create a new folder on the Deployment Server on the Compute Service instance (for example: /Change Assistant/downloads/ new folder)
  2. Access Change Assistant from the Deployment Server on the Compute Service instance.
  3. In Change Assistant, select the Work with Batches tree node.
  4. On the tool bar click the Import from jar button.
  5. In the Import Batch From dialog box, navigate to your jar file and then click Open.
  6. On the Import Batch To dialog box, navigate to the Change Assistant downloads directory on the Deployment Server on the Compute Service instance, and then click Open.
  7. Verify the Batch Information dialog box and click OK.
  8. Sign in to the JDEPLAN environment.
  9. On the Save & Exit, Export dialog box, click Next.
  10. On Deployment Server Import, read the tasks that will be performed by the import and then click Next.
    11. Deployment Server Import
    Deployment Server Import
  1. On Object Path Search & Select, select the pathcode to import to. If the release of the selected pathcode does not match the release of the on-premise instance, you will get the following error:
    2. Pathcode Error
    Pathcode Error
  1. On Deployment Synchronization Warning, de-select Synchronize CNC Data Now (R9840C/XJDE0002) and Work with Environment Data Sources? (GH9611/P98503)?* then click Next.
    2. Deployment Server Export
    Deployment Synchronization Warning
  1. On Backup Options select Include Pathcode files and Include System Data, and then click Next.
  1. Review the backup reports for success.
  1. On Import Options select to Include Pathcode files and Include System Data, and then click Next.
  2. Review the import reports for success.

Note: If you are importing to a 9.2.0.x tools release, there may be "Open XML failed" messages in the reports for tables F00942T and F98MODAT, as they do not exist prior to the 9.2.1.x tools release.

  1. Review the Cloud Server Tasks, and then click Next.
    2. Run Import Script
    Run Import Script
  1. On Deployment Succeeded click Finish.

section 4Run Import Script on Oracle Cloud Database Server

The import.sh script imports data from the dump files generated by the export script into the Database Server on the Compute Cloud service.

  1. Navigate to where you uploaded the import scripts on the Database Server on the Compute Cloud service (for example: /u01/scripts).
  2. Edit the imp_set file with your information.
    3. The imp_set file
    The imp_set file

    Field
    		 Description
    FROM_PATHCODE_PREFIX The pathcode to import from. Valid values are: PY, PD, DV, and PS.
    TO_PATHCODE_PREFIX The pathcode to import to. Valid values are: PY, PD, DV, and PS. If this is left blank, it is the same as FROM_PATHCODE_PREFIX.
    PATHCODE_RELEASE The pathcode to import from. Valid values are: 920 and above.
    SHARED Import data dictionary and object librarian schemas. YES, must be used for migration.
    DUMP_DEST Location where the dump files are located.
    DBUSER The database user with privileges to the tablespaces being imported (for example:system).
    DBPASS The password for the DBUSER.
    Note: If your database password contains any allowable special character like $ you must put single quotes around the database password in both the exp_set and the imp_set files. For example, if your database password includes a $ symbol, you would specify this value like this:
    DBPASS='Hello$123'
    NETNAME The TNS name for the database (for example: orcl).
    DEP_SVR_NAM The name of the Deployment Server on the Compute Service instance.
    This value is case-sensitive and should be uppercase.
    PRE_DEP_SVR The name of the on-premise Deployment Server.
    This value is case-sensitive and should be uppercase.
    SYSTEM Update system tables. YES, must be used for migration.
    ENT_SVR_NAM The name of the Enterprise Server on the Compute Service instance.
    This value is case-sensitive and should be lowercase.
    PRE_ENT_SVR The name of the on-premise Enterprise Server.
    This value is case-sensitive and should be lowercase.
  1. If you have not done so, transfer the exported *.dmp files from the your On-premise Database Server to the DUMP_DEST folder on the Database Server on the Compute Cloud service.

Note: Verify the DUMP_DEST already exists and the Oracle user has write privileges.

  1. Save and close imp_set.
  2. Run ./import.sh as the Oracle user.
  3. Examine all of the created log files and ensure they were successful.

section 5Post Tasks

  1. Run R98403A on the Deployment Server on the Compute Cloud service to copy ESU tables (F9670, F9671, and F9672) with the following values:
    • Processing Options:
      • Processing Options Value
      Source Environment Blank
      Source Data Source System - 920
      Target Environment Blank
      Target Data Source System Local
      Copy Table 1
      Replace Duplicate Records Y
      Clear Target Table Blank

  1. Apply the latest planner ESU on the Deployment Server on the Compute Cloud service.
    2. IMPORTANT: Before applying the latest planner ESU verify the “InstallPath” in the registry is the location where your Deployment Server is installed.
     
    Registry location:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\JDEdwards\OneWorldWindowsInstaller\install.ini]
    "InstallPath"="C:\\JDEdwards\\E920" (or above)
  1. Build and deploy a new full package to your target environment.
  2. Run Work with User Defined Objects (P98220U) to re-share One View Reports (OVR), if you have an OVR server configured on the Oracle Cloud.
    1. Select Shared for User Defined Object Status.
    2. Select One View Reports for User Defined Object Type.
    3. Click Find.
    4. Select the applicable objects and click Approve / Share on the Row menu.
      When the process completes the selected objects will be available on the BI Publisher Server.

      Note: Only shared OVRs are migrated, if you need personal OVRs migrated please reference the My Oracle Support Document ID: 2158173.1

  3. Run R98222UDO on the html Server to add User Defined Objects (UDO) to default projects.


    Note:     After the Oracle Cloud Migration Utility and Database Import, Personal and Reserved UDOs need to be placed on the user's default project. Since the OMW project data was not migrated, the default projects do not exist. R98222UDO creates the default project and adds the user's Personal or Reserved UDOs.

more informationWant to Learn More?