Hi,
I work for a company that has a large SAP installation (16 separate clusters - Development, Assurance, and Production). We are in the process of upgrading to Control-M 6.x (yet to be determined). My questions are as follows:
1. Do you have a central scheduling group that handles all Control-M scheduling needs?
2. Do you let certain end users schedule their own jobs?
a. Approximately what percentage of your user population has this ability?
b. What are the issues you are having with this approach?
3. Is your run/re-run ability centrally controlled?
4. Do you let let certain end users run / re-run their own jobs?
a. Approximately what percentage of your user population has this ability?
b. What are the issues you are having with this approach?
Thanks in advance for your input
MarkT
Who schedules / runs jobs at your installation?
Who schedules / runs jobs at your installation?
Hi MarkT
On all other server you will need to install a Control-M Agent communicating with your Control-M Server.
Control-M/EM is abble to communicate with all Control-M Server declared on your architecture. All conditions created by one of them could be sent to all others through Global Condition Server.
With the last version of Control-M/EM 6.3.01, it's posible to interface Control-M/EM with Active Directory.
If you considerate that a Control-M Server is full with most of 10 000 Jobs, and if you are able to determinate how many jobs you will define, it will be easy to know how many Control-M Server you need.1. Do you have a central scheduling group that handles all Control-M scheduling needs?
On all other server you will need to install a Control-M Agent communicating with your Control-M Server.
Control-M/EM is abble to communicate with all Control-M Server declared on your architecture. All conditions created by one of them could be sent to all others through Global Condition Server.
Concerning right access on the Control-M/EM Gui, you could able to create some different groups with restricted right about Jobs edition, Resources, Condition, Re-run, etc...2. Do you let certain end users ......
With the last version of Control-M/EM 6.3.01, it's posible to interface Control-M/EM with Active Directory.
fyot,
Thank you for your reply.
What I am asking is if you have a small group of users - a scheduling team - that is responsible for setting up and scheduling batch jobs or do you let end users set up their own jobs. If you let the end users set up their own jobs, what are some issues you've seen and how did you handle them.
MarkT
Thank you for your reply.
What I am asking is if you have a small group of users - a scheduling team - that is responsible for setting up and scheduling batch jobs or do you let end users set up their own jobs. If you let the end users set up their own jobs, what are some issues you've seen and how did you handle them.
MarkT
MarkT,
There are some different view about how to organize users and developpers using Control-M.
One of them, and may be the most secure to a Production, is to have:
- one team to administrate all Control-M components with all rights
- one team to devellop, maintain and modify all jobs with special right,
without all rights used to administrate Control-M components.
To all others it's possible to create a very small rights only to be able to view the plan, jobs results, sysout and logs, but with no right to modify anythings.
As Control-M administrator I purposed to create a Windows Terminal Server or a Citrix server to share Control-M Console with to all including the same parameters and access right.
Users just need to have Citrix client to access on it.
An access have been given to all other users having no special needs to use Control-M tools, but needs some results informations, creating a web access to extract some information from Control-M and to give to all those information whitout any risk.
In a same way, it is possible to create some different external tools, using XML for example, to create some template giving to user right to create their control-m jobs.
I know some administrator that created some tools using visual basic or different other language to create a small interface to define jobs following special standards.
The most important will be to define standards to normalize how to write jobs definition.
There are some different view about how to organize users and developpers using Control-M.
One of them, and may be the most secure to a Production, is to have:
- one team to administrate all Control-M components with all rights
- one team to devellop, maintain and modify all jobs with special right,
without all rights used to administrate Control-M components.
To all others it's possible to create a very small rights only to be able to view the plan, jobs results, sysout and logs, but with no right to modify anythings.
As Control-M administrator I purposed to create a Windows Terminal Server or a Citrix server to share Control-M Console with to all including the same parameters and access right.
Users just need to have Citrix client to access on it.
An access have been given to all other users having no special needs to use Control-M tools, but needs some results informations, creating a web access to extract some information from Control-M and to give to all those information whitout any risk.
In a same way, it is possible to create some different external tools, using XML for example, to create some template giving to user right to create their control-m jobs.
I know some administrator that created some tools using visual basic or different other language to create a small interface to define jobs following special standards.
The most important will be to define standards to normalize how to write jobs definition.
Always in all environment there are two o three kind of flows scheduled in control-M:
- day jobs always scheduled
- job that are scheduled only if there is a need: request scheduled
- job that are scheduled by some event or conditions in the flow
All kind of flows must be designed by a group of person, the schedulers that knows well the control-m and the environment.
When design the flows that are request flows and can run by users, the progect must consider this action conseguence in all the environment.
If all the processes are controlled by control-m you have the integration with different applicazion and flows that optimize all the environment in all ways. How define users and action depend fronm flow and organization but the schedulers administrators are a skills that must be present.
- day jobs always scheduled
- job that are scheduled only if there is a need: request scheduled
- job that are scheduled by some event or conditions in the flow
All kind of flows must be designed by a group of person, the schedulers that knows well the control-m and the environment.
When design the flows that are request flows and can run by users, the progect must consider this action conseguence in all the environment.
If all the processes are controlled by control-m you have the integration with different applicazion and flows that optimize all the environment in all ways. How define users and action depend fronm flow and organization but the schedulers administrators are a skills that must be present.