|< Day Day Up >|
One of the biggest decisions, after you have been working at administering the application for some time, is the number of Concurrent Managers to run. Until you have some basic feeling for the workload on the system and for the periods of time when you are experiencing high workloads, you should probably leave the existing configuration in place.
When the time comes to add new managers and new work shifts, you need to have a direction and a plan. Examine the Concurrent Managers that you currently have and see what the target and actual values are for the processes
One of the primary considerations in whether to add managers and how many to add is the constraints of the resource pool. Having too few managers means that concurrent jobs will likely have to wait at certain periods of higher activity. Too many managers could mean that online transactions will suffer due to the additional load of the extra managers on the system running batch at the expense of other transactions. An unexpected side effect of too many managers can also mean that the overall throughput of concurrent batch jobs slows down due to the load on the system. Further, too many concurrent jobs may add a significantly heavier load to the number of processes occurring at the OS level. This could have a detrimental effect on the overall performance of the hardware.
One manager you might consider adding,
Another consideration is to create additional Concurrent Managers to handle an increased load for off hours processing and adding an additional manager or two to the off hours to
Once you have made the decision to create a new manager, you should take into account the following
You will need to assign the new Concurrent Manager to a predefined immediate library. A Program Library contains the immediate Concurrent Programs that can be called by your new manager. An immediate program is a program that has been registered with the program library. Typically, as the FNDLIBR library contains the Apps Concurrent programs, it will be the library to which you will assign your new manager.
Next, you will have to assign a work shift to the new manager. Assigning a shift to the manager determines when your new manager will be active and available to do work.
For every shift, you will have to define the maximum number of OS processes that the manager is allowed to run concurrently to start
Specialize your new manager and allow it to read only certain kinds of requests.
To walk through creating a new Concurrent Manager graphically, after logging in as a
Figure 12.3: New Manager Definition Screen
Here you will name your manager, provide it a short name and choose, from an existing list of options, the application that you want to associate it with. You can provide a verbose description of the manager, define the type of manager that you want to create, assign it to a relevant consumer
You can, by clicking the Specialization Rules button set the rules that you want your manager to follow. In this case (see Figure 12.4), I want the manager to only be able to run analyze and gather statistics, so I create the list of what I want it to be able to do.
Figure 12.4: Specialization Rules for New Manager
Finally, by clicking the Work Shifts button, you can define when you want your manager to be able to work. Figure 12.5 shows that I allow this manager to run any time. It would probably be better if it were only allowed to run on the off shifts, but I want to be able to call it any time that a user complains about poor performance.
Figure 12.5: New Manager's Work Shift
To assign a new manager to a work shift, you have to have an available work shift that they want to use. If there is not an existing work shift that applies to your new manager, you need to define a new work shift through the Work Shifts form.
You can name the new Work Shift anything that intuitively describes the work shift and makes it obvious that it is your custom work shift. My Company Weeknights, My Company Weekends, or My Company End Of Year are descriptive, allows
Programs running assigned to a work shift run on a priority of most narrow scope to least narrow scope for those overlapping shifts. Therefore, a program assigned to a work shift that is scheduled to run at 00:05 on New Year's Day if New Year's Day is on Wednesday will take priority over a weeknights manager and a weeknights manager will take priority over the Standard Manager.
Walking through the screen to create the new work shift, you would navigate to Concurrent:Manager:WorkShifts (see Figure 12.6) and be presented with the Work Shifts window (see Figure 12.7) in which you can name your new shift, provide the from and to times, and the from and to dates as well as providing a specific date if you wanted to create one that only runs on New Year's Eve (for example). In this definition, I created a shift that runs from 5 P.M. to midnight that will be responsible for just gathering statistics, should I choose to redefine the manager I created earlier to only run during these times.
Figure 12.6: Concurrent Manager Main Screen
Figure 12.7: Work Shift Definition Screen
|< Day Day Up >|