For me there are not similar. I've no info about integrated solution between Control-M and BladeLogic, but it could make sense
Recently BMC has organised 1 webinar named "BMC Control-M for BMC Bladelogic customers".
There must be something which could be similar in both the tools.
What do you mean "something which could be similar in both the tools" - do you mean an integration between control-m and bladelogic or do you mean overlapping functionality between the two tools?
i mean to say funcationality as both the tools are job schedulers.There must some advantages or disadvantages of one on other.
I advantage of BladeLoic i know is ""it can perform OS installtion on servers which control-m cant do.
BL is far more than a job scheduler. Job scheduling is just one component of what it does.
The 'jobs' in bladelogic are unique to bladelogic (eg, compliance, audit, provisioning, deployments) while control-m is a more generic scheduling tool.
BladeLogic is used to deploy applications, patches or OS when the Control-M is a scheduler.
BladeLogic can not schedule the job but just plan the jobs.
With Control-L, you can link jobs between them.
I do not see how plannifier 10,000 jobs with BladeLogic
What kind of jobs are you talking about?
When we are talking about BladeLogic Jobs, those are objects that are native to the BladeLogic tool and perform functions specific to BladeLogic.
In control-m, jobs may also be useful unique, but completely different from BladeLogic.
To me this is not the type of job that can run that one must make the difference in control-m and BladeLogic but the conditions for carrying out these jobs.
With BladeLogic you can run jobs in a unified way, whereas with control-m you can specify the conditions for its execution (eg need to wait for another job, the machine she used at 100%, the job can s Execute only if another job is not running at the same time).
Bill is right to say that jobs are in BladeLogic specific reports by those of control-m.
I would say that the great difference between the two is that BladeLogic is used to deploy objects while control-m is used to schedule executions.
PS : Excuse me for my English, I'm French
thanks for the valuable contribution to the discussion.
I just wanted to know the views of various people about both these tools
Basically i am a control-m engineer but wanted to learn something about bladelogic so i did this.
Control-M is a scheduler and not Bladelogic even if BL could schedule jobs. BL could only schedule jobs with very basic sequential logic out of the boxe.
I've some customer using external scheduler like Control-M to schedule "complexe" conditional sequences of BL jobs.
For me the main question is more: what could differentiate when it's better to use Control-M or BAO?
Could you tell me how do u bring BL jobs in Control-m environment?
is there any way to see bladelogic jobs in CTM environment?
Use the 'blcli' - bladelogic's commandline api.
You call BL jobs thru blcli