Scheduling a Custom Patch Deployment Using Packager

Learn how to schedule a custom patch (CEMLI Patch or ACE Data Fix) deployment using Packager. The ACE Data Fix option can be used to promote data fixes that do not require manual intervention or input parameters during execution.

You must use MOS, rather than Packager, to modify the RFC in the following situations:

• the Packager scheduling operation failed for some reason - for example, a Web service failure or application integration issue. This results in the creation, but not scheduling, of the RFC.

• Oracle Automated CEMLI Execution is down.

To schedule a custom patch deployment using Packager:

1. On the CEMLI home page, verify that your customer details are displayed.

2. Click Packager.

   The Upload Customized Files tab is displayed by default.

3. Click Create/Monitor RFCs.

4. From the Target list, select the environment where the patch will be deployed. This list is populated with all the environments associated with the support identifier (SI).

   To deploy the patch using an existing RFC, continue to step 5. To create a new RFC, continue to step 21.

5. (Production RFCs only) Click Search RFCs.

   The Search and Select Existing RFC dialog box opens, allowing you to select the number of an RFC that was already successfully deployed on a non-production instance.

   If you do not provide this information and want to directly deploy a change to a production environment, the Risk Statement dialog box opens asking you to acknowledge that you accept that you are deploying untested code directly to a production instance.

6. From the Target list, select the target the patch needs to be deployed to.

7. Click Search.

   All non-production RFCs are listed in descending order of the run completion date.

8. Click the RFC number, then click Select.

   The Create/Monitor RFCs page refreshes.

9. Click Select Patch(es).

   The Existing Cemli Patches page opens, showing all patches created in Oracle Automated CEMLI Execution, in descending order of the date created.

10. Press the Ctrl key, and select all patches that you want to include in the RFC, in the order in which they should be applied, then click Select. You can select up to 10 patches.

    The Patch Number field is automatically populated with the numbers of the selected patches, while the Summary field is automatically populated with the number of patches to be applied.

11. To deselect the selected patches, click Unselect All.
12. To include patches one-by-one (with out pressing Ctrl key), select or search the patch, and then click Add to PatchList. Repeat the step for multiple patches.

13. Select any of values in the Estimated Time to Apply Change field, ranging from 1 hour to 10 hours.

    Note:

    CEMLI patches are applied in hotpatch mode by default, which means that Oracle E-Business Suite services are not stopped and restarted.

14. Select the Accept Risk check box to acknowledge your acceptance of the risk of applying CEMLIs and read the risk statement before the RFC can be created.

    Select the Auto Skip checkbox to complete the RFC despite any custom code failure during patch application by automatically skipping the failed adworker.

    Select the Auto Stop checkbox to stop RFC execution in case of any custom code failures during patch application, and terminate the execution.

    Note
    
    

    It is important to select one of the above options, while creating an ACE RFC. Rest of the RFC creation and scheduling process remains the same. By default, the Auto Skip checkbox is auto-selected. If RFC is auto-skipped or auto-stopped, then MOS RFC Status would be Awaiting Customer.

    To select the services that need to be restarted after the patch is applied, continue to step 15. Otherwise, continue to step 21.

15. (Optional) If any service needs to be restarted after the patch is applied, click Select Options.

    The Select Bounce Options dialog box opens, displaying the list of available hosts and services.

16. Select the check box corresponding to the services that need to be restarted.

17. (Optional) If you want to delete the data in the Apache cache module, leave the Clear Apache Cache check box selected (default). Also for EBS 12.2 and above, if you want to bounce Managed Server, leave the Managed Server check box selected (default for EBS 12.2 and above).

18. Click Select.

    The Bounce field is automatically filled in with data on the host and service that need to be restarted.

    Note
    
    

    If any service needs to be restarted after the patch is applied, the estimated time listed in the Estimated Time to Apply Change field is automatically increased by one hour.

19. Click Customer Note to add an action plan or any other relevant information you want included in the RFC.

20. Select the Hot Backup check box to enable/disable the Hot backup for Non Prod instances. For Production instances, this check box is automatically selected and cannot be deselected.

    This Provision of Hot backup selection is only available for the ACE Data Fix option. Users who selected CEMLI Patching option will not see this feature.

21. Click Create RFC.

    Note
    
    

    To schedule RFCs in Packager, you must have the MOS Authorized Approver privilege for the Oracle E-Business Suite environment where the CEMLI patch will be deployed. Otherwise, request that a MOS authorized approver for your organization schedules the RFC through Oracle Automated CEMLI Execution.

22. If you have MOS Schedule RFC privileges, the Auto RFC dialog box opens.

    To schedule the RFC for execution in 30 minutes, continue to step 23.

    To select another execution date and time, continue to step 25.

23. Click Yes to schedule the RFC for execution in 15 minutes.

    Note:

    If another RFC is already scheduled for execution at the same time, for the same instance, the Schedule RFC dialog box opens, allowing you to choose another time slot for your RFC. Please continue to step 25.

24. Click OK.

25. Click No in the Auto RFC dialog box to select a future execution date and time.

    The Schedule RFC dialog box opens.

26. Click the calendar icon to select a date.

27. Select the appropriate time from the menu, then click Check.

28. If the time slot availability is confirmed, click Approve.

    The RFC is displayed in the RFC List table, with the Open - Ready for Execution status. For more information on the details and actions available in the RFC List table, see Monitoring RFCs.