Administering Concurrent Managers/Programs 1. A Concurrent Program is an executable file that runs simultaneously with other concurrent programs. 2. A request to run a concurrent program is called a concurrent request. 3. When the User submits a Report – the command to run the report is the concurrent request. The Program that generates the report is the Concurrent Program. The concurrent Program is started by the concurrent manager. 4. The user submits a report, system maintains list of requests to start concurrent programs and the concurrent manager reads the request table and starts the relevant concurrent program. 5. The two predefined concurrent managers in oracle are a) Internal Concurrent Manager and b) Standard concurrent manager. You cannot alter the definition of a) . There is no restriction on the number of concurrent managers you can define. 6. When you define a concurrent manager you define the number of target processes or the number of Operating system processes it can devote to run requests. 7. GSM(Generic Service Manager) provides the framework to manage processes on multiple host machines. The Internal Concurrent Manager manages the various services across hosts. 8. When you define a concurrent Manager you define the Specialization Rules, Work Shifts, Program Libraries and Target processes. 9. A work shift can be hours in a day, days in a week or specific days in a year. 10. Specialization Rules identify the kind of requests that the concurrent manager will read to start only specific programs. 11. Assigning work shifts to the concurrent manager determine at what times the concurrent manager works. This is done to balance the load and number of concurrent programs that run simultaneously. 12. Work shift Hierarchy is a) Specific date and specific time then b)Specific date but no specific time c)Range of days and range of times d)Range of days but no range of time e) Range of time but no date or range of days and lastly f) Standard work shift no date, days or time specified. 13. Overlapping work shifts a) The work shift with more specific time period takes effect b) work shift with the larger number of target processes takes effect when two in the same hierarchy level overlap. 14. You can disable a work shift a) By not assigning it to a manager b) assign number of target process for the work shift to 0 and c) delete the assignment. 15. Program libraries consist of immediate concurrent programs that can be called by the concurrent manager. 16. Specialization Rules Action Types a) Combined Rule b) Oracle ID c) Program d) Request Type and e) User 17. Request types are defined to streamline processing of requests. A) Define a request type B) Assign the request type to appropriate concurrent program C) Use the Request type in a specialization rule. 18. Conflict Domains: Resolves conflicts and imposes constraints within a domain and not across. It identifies data that creates incompatibility . 19. The data groupings for Conflict Domains: a) SOB b)MSOB (multiple Installations) c)Multiple operating Units(MO_Operating_Unit) d) Multiple Orgs (Inventory_Organization_ID) e) Business Group (HR) and f) FA Books 20. No limits on the number of conflict domains you can define. But the more you define the performance will decline. 21. Concurrent Manager assigns conflict domain based on the hierarchy a) Program Parameter b) Profile option Concurrent: Conflicts Domain and c) Standard default domain. 22. Control features of Concurrent Managers : you can activate all or deactivate all or individual managers. 23. Internal Manager Control Functions : Verify Concurrent Manager Status, deactivate internal concurrent manager and all other managers, terminate all running requests and deactivate all managers. 24. When you deactivate a concurrent manager the running requests are allowed to complete before the manager shuts down. 25. Internal Monitor provides fault tolerance for Internal Concurrent Manager and its sole job is to monitor ICM and restart it if it fails across nodes. 26. Transaction Managers handle synchronous request processing and are associated with specific data groups. 27. Concurrent Programs can be grouped in two ways a) Request Set is defined to run several concurrent programs together in the set and b)Request Group is defined to control access to concurrent programs via responsibilities to which they are attached. 28. You can limit the number of active requests for each user by setting the profile Concurrent: Active Request Limit 29. A request group assigned to a responsibility is called Request security group. It is a collection of reports and programs to which the user of that responsibility has access to. 30. Control over users viewing requests in R12 is designed using RBAC. In 11i a Profile Report access Level was used. 31. Request set is a collection/grouping of reports and programs and can be run from both Form based and HTML based applications. Used to run multiple reports with predefined print options and parameters efficiently. 32. The Order in which each report is submitted in the set is determined by the order of stages in which the reports are grouped in the set. 33. Multi-lingual reports cannot be run as request sets. 34. System administrators can define request sets to include programs and reports outside the users request security group. They can also prevent users from modifying default parameters. 35. To run different requests in parallel include them in one stage. And to run them in sequence put them in different stages and link the stages in the order you want to run them. 36. A stage is not complete until all the reports in that stage are completed. 37. Stage has 3 statuses- Success, Warning or Error. 38. A stage can be linked more than once to any other stage or to itself. 39. Each report in a Request set can be sent to a different printer. 40. A request set can be modified only by its owner or System administrator. 41. If you want to ensure the completion status of the request set is equal to that of any particular stage then check the box ‘’Return value of this stage affects the set outcome’’ and if you check this for more than one stage then the status of the last of the stages in the set is considered. 42. In the request parameters window uncheck the modify box to prevent users from changing parameters during run time. 43. Enter in the shared parameter field for a common parameter to default in all reports in the set. 44. If you subsequently modify a shared parameter, this change will not be propagated automatically to all occurrences in the request set. 45. While an end user is the owner of the request set he defines, he can only select reports and programs in his request security group. Whereas a system admin can define requests set and include programs and reports outside the request security group. 46. The end user owner can only edit request sets they own. Any requests sets the end user defines will be available from any of his responsibilities. 47. A system administrator can define a request set and assign it to any user who becomes the user. If a request set is not assigned to any user then its parameters and print options cannot be modified. 48. An end user cannot edit a request set outside his request security group. He can only run the set, not any individual report in it , he can add any requests in his request security group to this set, he can edit print options or parameters of any reports in the set belonging to his request security group, he can also delete any request in the set regardless of whether it is in his report security group or not. 49. Request groups can be used at Responsibility Level and Form Level. 50. Run the Request Group Responsibilities Report to find out the responsibilities which have access to the request set. 51. Conflict Resolution Manager enforces incompatible and run alone program definitions. 52. The Concurrent Program details report should be used when you plan to modify a concurrent program. Everything related to the concurrent program are listed in this report. 53. The Concurrent Programs report shows he list of concurrent programs enabled and disabled.