Quantcast
Channel: orabot » Enterprise Scheduler
Viewing all articles
Browse latest Browse all 2

Creating and Securing ESS Jobs in Fusion Applications using APM – Part 2

0
0

Step 1. Login to Fusion Applications using an account with both “Application Implementation Manager” and “Application Implementation Consultant” external roles assigned. You need the Application Implementation Manager role assigned to define the ESS Job and the Application Implementation Consultant in order to access FSM.

Step 2. Use the Fusion Navigator to launch FSM, open your implementation project and search for a task containing “Enterprise”. Then proceed by launching the “Manage Custom Enterprise Scheduler Jobs for Ledger and Related Applications”.

Note: The task will differ depending on what product you are implementing. The example above is the relevant task for General Ledger and Financial Accounting Hub.

This task can only be completed once you have created the oracle.apps.ess.custom.* resource in APM (Step 2. in Part 1)

Step 3. Click on the Create new ESS Job Definition icon

Step 4. Define your new ESS Job Definition, for all custom ESS Job definitions /oracle/apps/ess/custom will always be prefixed to the path you enter.

The full path is what will be used to tie back this ESS job definition to the APM resources defined in Part 1 and ultimately secure this ESS job so that only the relevant users have access to execute it.

In Part 1 I mentioned that the resource is a hierarchical identifier and that I was applying the naming convention oracle.apps.ess.custom.<product>.<entity>.<entity_type>

In Step 2. of Part 1 we defined two resources oracle.apps.ess.custom.* and oracle.apps.ess.custom.subledgerAccounting.interface.programs.* The purpose of the second resource was to allow all operations staff with access to the “Interface Controllers” external role access to run any Custom ESS job defined lower down the hierarchy.

This is why it is extremely important then when we define our Custom ESS job that we adhere to the resource name defined in APM, in this example we have to enter the path as subledgerAccounting/interface/programs.

The full path for this job definition will then end up being /oracle/apps/ess/custom/subledgerAccounting/interface/programs/XXFAHCEFCS and because we have defined the resource as oracle.apps.ess.custom.subledgerAccounting.interface.programs.* any user with access to the “Interface Controller” external role will now be permitted to execute the Job XXFAHCEFCS.

Note: In R12 security was an afterthought, after defining a concurrent request we would then assign it to the relevant request group. In Fusion the path specified when defining an ESS job is critical to securing the ESS job and this path is not updatable, therefore it means that in future we will have to start by identifying the consumers of a particular ESS job and what access they will have prior to defining it. This will also play an important factor in coming up with a naming convention adequate for this fine grained access control.



Viewing all articles
Browse latest Browse all 2

Latest Images

Trending Articles





Latest Images