Oracle by Example brandingAutomating Package Build Using the Automated Package Build Orchestration

section 0Before You Begin

This 30-minute tutorial shows you how to automatically build an update package using the JDE_ORCH_PackageBuild_AutomatedPackageBuild orchestration.

The JDE_ORCH_PackageBuild_AutomatedPackageBuild orchestration contains:

  • Form requests created using the Process Recorder to assemble and build a full or update package.
  • A Health Check orchestration to trigger a health check on the Server Manager instances before the builds are submitted.
    Note: Using this orchestration, you can only assemble and build a package. You must deploy the package manually. See Deploying Packages.

What Do You Need?

To perform the steps in this tutorial you must have:

  • Downloaded the TSPKGBLD02 file from Oracle Update Center.
  • Imported the TSPKGBLD02_60_99.par file to your environment using Change Assistant. See Change Assistant Home Page and Using Change Assistant.
  • Checked out the JDE_ORCH_PackageBuild_AutomatedPackageBuild orchestration, JDE_ORCH_PackageBuild_SMInstanceHealthCheck orchestration, and Health Check service request in the Project Objects tab of the Object Management Workbench - Web page application.
  • Subscribed to the Packages ready for deploy (JDE_NOTIFY_PackageBuild_PackagesReadyToDeploy) notification. For more information, see the JD Edwards EnterpriseOne Notifications Guide.

section 1 Running the Automated Package Build Orchestration


You want to define and build a weekly update package containing all the objects from a specific OMW project.

Note: This task relies on EnterpriseOne demo data. You can use other data available in your system to perform this task.
If you want to edit any task in the JDE_ORCH_PackageBuild_AutomatedPackageBuild orchestration, then you must reserve the task in Orchestrator Studio.

  1. Log in to Orchestrator Studio.
  2. Click the Orchestrations icon.
  3. Click the JDE_ORCH_PackageBuild_AutomatedPackageBuild orchestration.

  4. Automated Package Build orchestration
    JDE_ORCH_PackageBuild_AutomatedPackageBuild Orchestration
  5. Double-click the JDE_ORCH_PackageBuild_SMInstanceHealthCheck orchestration to verify that the orchestration is working as expected.
  6. In the JDE_ORCH_PackageBuild_SMInstanceHealthCheck orchestration, click the Health Check connector. If the system returns an Internal Server Error, then follow the instructions in Creating an Orchestration to Check the Health Status of a Server Instance and create the connection again.
  7. Click the Close button to close the JDE_ORCH_PackageBuild_SMInstanceHealthCheck orchestration.
  8. Click the Start icon.
  9. Click the Run Orchestrations icon.
  10. In the Run Orchestrations window, complete the following fields as described in this table to perform an update package build:

    Note: You can also define default values for these inputs in the Inputs and Values window of the orchestration. Click the Start icon, select the Input and Values icon, enter the default values in the input fields, and then save the orchestration.
    Package_Name Enter the name of the package you want to build. For example, enter WKLYUPD.
    Path_Code Enter the path code. For example, enter DV920.
    Package_Description Enter the description for the package. For example, enter DV925FA.
    Based_On_Package_Name Enter the parent package name of the update package.
    Package_Type Enter the package type as:
    •  41 - For update package

    • Note: To perform a full package update, enter the value as 40.
      If you are performing a full package update then you must enter values in these input fields: Package_Name, Path_Code, Package_Description, Package_Type, Language_Code, Feature_List, Server_Name, InstanceName, toEmail, and Primary_Server. If the value for the Foundation_Name field is left blank, the system will use DEFAULT as the value.
      Language_Code and Feature_list are optional fields when you are performing a full package update.

    Object_List[0].Object_Name Enter the value to specify the individual objects you want to add in the package definition.
    OMW_Project_List[0].OMW_Project_Name Enter the name of the OMW project.
    OMW_Project_Status_List[0].Project_Status Enter the status of the project.
    Foundation_Name Enter the JD Edwards EnterpriseOne foundation name.
    Build_BSSV Enter these values as required:
    • blank/no :  BSSVs will not be included in the build.
    • yes : BSSVs will be included in the build.
    Language_List[0].Language_Code This value is an array name.  You can enter the list of language codes.
    Feature_List[0].Feature This value is an array name. Enter the list of features.
    Additional_Server_List[0].Server_Name This value is an array name. Enter the name of the additional servers.
    Instance_list[0].InstanceName Enter the name of the Enterprise Server instance in the Server Manager.

    Note: If you leave this field blank, the health check task will not be performed when you run the orchestration. Also, the package build will be defined but will not be submitted.
    toEmail Enter the recipient's email address.
    Primary_Server Enter the name of the primary server.
  11. Click the Run button.
  12. Verify that the orchestration is successful.
  13. Run Orchestrations window
    Run Orchestrations Window

When the Packages are ready to Deploy notification is triggered, the system sends an email with a link to the Package Build application. You can also access JD Edwards EnterpriseOne and click the Notifications icon to view the Packages are ready to Deploy notification. This notification is scheduled to run every Monday at 7 am by default. You can modify the schedule (JDE_SCHED_PackageBuild_WeeklyUpdatePackageCheck) of this notification as per your requirements.

Run Orchestrations window
Packages are ready to Deploy Notification

section 2Verifying the Package Build Status

In this task, you will verify the package build status using the Package and Deployment Tools menu.

  1. Access the JD Edwards EnterpriseOne application.
  2. Click the Navigator menu, enter GH9083 in the Fast Path field, and then press Enter to access the Package and Deployment Tools menu.
  3. Click the Package and Deployment Tools menu and then click Package Assembly.
  4. Package Assembly application
    Package Assembly Application
  5. In the Package Assembly - Work With Packages application, enter your package name in the Package Name field of the QBE row and click the Search button.
  6. Select your package name and click the Individual Objects tab.
    Verify that the orchestration has added all the objects that are included in the project definition. For example, if 21 objects are included in the External Forms projects, you should see 21 objects in the Individual Objects tab.
  7. Package Assembly application
    Package Assembly Application - Work With Packages
  8. Access the Package and Deployment Tools menu again and click Package Build.
  9. In the Package Build application, enter your package name in the QBE row and click the Search button.
  10. Select your package name.
  11. Verify the status of your package build in the Package Build Detail grid.
  12. Package Build Detail
    Package Build Detail
  13. Click the Navigator menu, enter wsj in the Fast Path field, and then press Enter to access the Work With Submitted Jobs application.
  14. In the Submitted Reports application, verify that the status for the client package build and the server package build is displayed as Done.
  15. Package Build Detail
    Submitted Reports Window
  16. Deploy the package manually. For more information, see Deploying Packages.

section 3Want to Learn More?

Refer to these resources: