Oracle Applications Release 11 i Release 11.5.9 WorkFlow

1. Oracle Applications Release 11iRelease 11.5.9 WorkFlow Business Events – The Setups You May Be Missing Karen Brownfield Kbrownfield@solutionbeacon.com Release 11i Workshops Dallas, TX • Cincinnati, OH • Phoenix, AZ • Los Angeles, CA Denver, CO • Washington, DC • Atlanta, GA • Portland, OR www.solutionbeacon.com

2. About the Trainer • 25+ yrs experience in IT Industry • 12+ yrs experience Oracle Applications • 5 yrs experience Workflow • OAUG Board of Directors 11 years, Former President • Presenter of Training/Presentations multiple clients, conferences • Solution Beaconis a leading provider of expert-level resources to Government Agencies and Fortune 1000 companies specializing in the Oracle Applications marketplace, providing leading expertise in the following areas:  • Release 11i Upgrades/Implementations • Oracle Apps Database Administration • Oracle Systems Architecture • Oracle Performance Tuning • Oracle Workflow

3. Steps to Set up Business Event System • Optional – Establish database links to external systems • Optional – Enable Oracle Message Broker queues • Optional – Set up custom queues • Required – Check Business Event setup parameters

4. Steps to Set up Business Event System • Required – Schedule listeners for local inbound agents • Required – Schedule propagation for local outbound agents • Required – Synchronize event and subscription license statuses with product license statuses • Required – Ensure WF_CONTROL queue is periodically cleaned up • Optional – change Global Preference

5. Setting up Queues • Each agent must have a queue • Standard queues created by upgrade/install

6. Standard Queues/Listeners

7. Standard Queues/Listeners

8. Standard Queues

9. Standard Queues • Default retention for consumed messages – 7 days • To change, DBMS_AQADM.Alter_Queue procedure • DO NOT change any other parameters for these queues

10. Enabling OMB queues • Only Required for Oracle8i database • Set up WF_OMB_IN and WF_OMB_OUT queues • Translates between standard workflow event msg structure, WF_EVENT_T, and structure required by OMB, OMBAQ_TEXT_MSG. • Assign WF_EVENT_OMB_QH as propagation protocol

11. Enabling OMB queues • Run wfquhndos.sql to create PL/SQL spec • Run wfquhndob.sql to create PL/SQL body • Both located in $APPL_TOP/wf/sql

12. Check Business Event Setup Parameters • Admin responsibility • Workflow | Check Event Manager Setup

13. Check Business Event System Parameters • Verify Database Init.ora Parameters are equal or greater than recommended levels • Aq_tm_processes – monitors delay events such as Wait activity • Job_Queue_Processes – handles propagation of Business Event System event messages • Job_Queue_Interval (8i only) – how frequently job_Queue_process wakes up • Change values through init.ora file or ALTER SYSTEM statement (9i)

14. Check Business Event System Parameters • Verify queues are created for standard queues (Queue Name and Queue Created columns in Local Agents section) • Do not use Create Link to Schedule In-bound Listeners • If Link says Edit, press Edit, click Delete

15. Check Business Event System Parameters • Start outbound propagations • Admin responsibility • Workflow | Check Event Manager Setup • Click Create for all queues used

16. Check Business Event System Parameters • Start Outbound (cont) • Click Create • Enter Duration • Enter reschedule interval • Enter latency (how long to wait after all messages queued before checking again) • Must be > or = job_queue_interval

17. Schedule In-Bound Listeners • Verify Listeners for local inbound agents are scheduled • Do not utilize Create link in Check Event Manager Setup • ECX_INBOUND and ECX_TRANSACTION are only required if using EDI Gateway

18. Schedule In-Bound Listeners -Start Containers • Requires GSM to be configured • Profile option ‘Concurrent:GSM Enables’ should be set to ‘Y’ • Done through OAM • Start Workflow Agent Listener (required)

19. Start Containers • Navigate to Workflow Manager • Click on Service Components

20. Start Containers

21. Start Containers • Verify Deferred, Deferred Notification Agent, Error, and Inbound status is ‘Running’ • If not, click the Workflow Agent Listener Service Container

22. Start Containers • If status is Deactivated, click radio button next to Service, ensure Start is displayed action, click Go • Starts agent listener service components for WF_DEFERRED, WF_ERROR, WF_NOTIFICATION_IN, WF_IN

23. Start Containers • If status “sticks” on Activating (doesn’t change to Running), then something is wrong with GSM link to concurrent managers • Until link is fixed…..

24. Schedule In-Bound Listeners – GSM Not Configured • Concurrent program – Workflow Agent Listener • If doesn’t show in Run Requests window, check program definition, may not be enabled • Run a program for each queue • Schedule to rerun periodically

25. Schedule In-Bound Listeners • Minimum listeners that must be scheduled • WF_IN • WF_DEFERRED • WF_NOTIFICATION_IN • WF_ERROR • Can create Program Set • WF_REPLAY_IN was accidentally required with initial 11.5.9

26. Synchronize License Statuses • Concurrent program: Synchronize Product License and Workflow BES License • Will have to be added to Request Group

27. Verify Queue Cleanup Scheduled • From Concurrent Manager, verify ‘Workflow Control Cleanup’ is scheduled • Oracle recommends every 12 hours

28. Revisit System Status • Global Preferences page • Enabled – Internal / External Events • Local Only– Internal Only • External Only – do not use this value • Disabled – do not use this value

29. Verify Event System Works • Workflow Agent Ping/Acknowledge • Sends ping event message to each inbound agent on local system • Waits to receive acknowledgement event message from each agent • If this workflow completes successfully, Business Event System setup is valid

30. Verify Event System Works • Event Queue Summary • Note Current Count for Inbound queues

31. Verify Event System Works • Launch Process • Click on Workflow Agent Ping/Acknowledge

32. Verify Event System Works • Make up a Item Key (must be unique) • Select Master Ping Process in Process Name • Click OK

33. Verify Event System Works • Starts One Master and 3 Details • Detail for each IN queue except ERROR

34. Verify Event System Works • Return to Event Queue Summary • Click on Flashlight beside any queue where count is higher (except Out) • Click Go

35. Verify Event System Works • There should be one message in IN, one in Deferred • Check if count increased for Replay, if so, use concurrent manager program to start it • Messages will stay in queue until next time concurrent process runs for that queue, then message will go to Replay queue and stay there until Replay concurrent process runs

36. Verify Event System Works • As each message is either “consumed” (or transferred to Replay queue), detail process for that queue completes • If Replay queue is being used, master process won’t complete until all messages have made it through the replay queue

37. Questions and Answers KISS Keep It Simple and Supportablesm Thank You! Karen Brownfield kbrownfield@solutionbeacon.com www.solutionbeacon.com