In my previous post I described about the basic architecture of ContolM Enterprise Server.In this post I am going to describe the architecture of ControlM Enterprise Server in further detail.Before that I am going to just review back the basics discussed in previous post.
ControlM EM server is primarily used for GUI process.It is used to display the status of information related to the processing of jobs in GUI form,also it is used for connecting two different ControlM servers which can't talk directly to each other.As far as architecture part is concerned its primarily defined into 4 parts as described in my previous post.
1)Database
2)Configuration Agent
3)ControlM Web Server
4)Naming Services (NS)
Database which is in sync with with database of controlM server holds information about jobs of one or more controlM server and is divided into two partition one having active job information and one having permanent job defintion.
Configuration Agent which is used for routing information between EM server and database and deciding the state of EM server components whether we want them to be up or down.The information between GUI server and database also goes through Configuration Agent.
ControlM Web Server is used to generate a url so that we can using that url connect to EM server and its database,no need to install large umber of clients on different machines.
Naming Services which act as a repository and resolves the name of Control M EM server for the gui client.
So this was the basic structure of Control M EM server as discussed previously by me
Now I am going to further discuss about the 7 other components of EM server which acts as add on and can be made up or off as per requirement.
The 7 other components are:
GUI Server:-This is the main server which is responsible for handling all the GUI related issues.If this server is down we wont able to handle or see information about the alerts on GUI panels.Though we will be able to login to the server if naming services are up but if GUI server is down we wont be able to see anything.
Global Alert Server(GAS):-This is responsible for shouting of alerts which gets generated when jobs overrun or gets delayed.This is the screen where monitoring team people in companies see the alerts and then generate the tickets for the corresponding teams.Now third party tools can be integrated in this component like patrol.
But this part is dependent on GUI server since we can see alerts only if GUI server is up.
Configuration Manager Server:-This part is responsible for routing the information within the components.TCP/IP is the protocol used for communication within these components.So this part need to be up for proper communication within these components.
Forecast Server:-This is more of a Data mining sort of tool which is used to predict some information about the jobs by studying about the permanent job definitions stored in the database of controlM server.We can query from the databse about the job and see when is job next time scheduled to run,what conditions does it nedded etc.Also it need GUI server for the display purpose.
Batch Impact Manager:-This is used to self troubleshoot the machine means suppose we want some component to be up then BIM will try to make that component up when it goes down and suppose we have a flow of jobs with us which needs to start at some particular time and get finish at some particular time then if by any reason jobs gets stuck in between and are not able to move further from a particular node point in path flow of jobs BIM will automatically check if that node point can be ignored and jobs can be transfered to next node point , in case its not posssible to move jobs to next node point then BIM is going to notify us how much time more its gonna take to finish up the jobs or what's the shortest path that we can follow now so as to finish the jobs on the required time.
Global Condition Server:-This is required when we have a job which needs to get executed on two or more different controlM server so the global conditions for that job are executed from this component because we need a EM server for the connectivity between two control M server.
Gateway:-as the name suggest is responsible for connecting Control M EM server with Control M server.All the traffic passes through it,however it doesn't has got any buffering capacity of its own like a Global Alerts Server so if large number of request are sent for processing more than the capacity of gateway to handle the request they often get dropped and we see gateway error.
So this completes a basic overview of the architecture of ControlM EM server.For more details refer the site of BMC.
ControlM EM server is primarily used for GUI process.It is used to display the status of information related to the processing of jobs in GUI form,also it is used for connecting two different ControlM servers which can't talk directly to each other.As far as architecture part is concerned its primarily defined into 4 parts as described in my previous post.
1)Database
2)Configuration Agent
3)ControlM Web Server
4)Naming Services (NS)
Database which is in sync with with database of controlM server holds information about jobs of one or more controlM server and is divided into two partition one having active job information and one having permanent job defintion.
Configuration Agent which is used for routing information between EM server and database and deciding the state of EM server components whether we want them to be up or down.The information between GUI server and database also goes through Configuration Agent.
ControlM Web Server is used to generate a url so that we can using that url connect to EM server and its database,no need to install large umber of clients on different machines.
Naming Services which act as a repository and resolves the name of Control M EM server for the gui client.
So this was the basic structure of Control M EM server as discussed previously by me
Now I am going to further discuss about the 7 other components of EM server which acts as add on and can be made up or off as per requirement.
The 7 other components are:
1)GUI Server also called as GSR
2)Global Alerts Server(GAS)
3)Configuration Manager Server(CMS)
4)Forecast Server(FS)
5)Batch Impact Manager(BIM)
6)Global Conditions Server(GCS)
7)Gateway
GUI Server:-This is the main server which is responsible for handling all the GUI related issues.If this server is down we wont able to handle or see information about the alerts on GUI panels.Though we will be able to login to the server if naming services are up but if GUI server is down we wont be able to see anything.
Global Alert Server(GAS):-This is responsible for shouting of alerts which gets generated when jobs overrun or gets delayed.This is the screen where monitoring team people in companies see the alerts and then generate the tickets for the corresponding teams.Now third party tools can be integrated in this component like patrol.
But this part is dependent on GUI server since we can see alerts only if GUI server is up.
Configuration Manager Server:-This part is responsible for routing the information within the components.TCP/IP is the protocol used for communication within these components.So this part need to be up for proper communication within these components.
Forecast Server:-This is more of a Data mining sort of tool which is used to predict some information about the jobs by studying about the permanent job definitions stored in the database of controlM server.We can query from the databse about the job and see when is job next time scheduled to run,what conditions does it nedded etc.Also it need GUI server for the display purpose.
Batch Impact Manager:-This is used to self troubleshoot the machine means suppose we want some component to be up then BIM will try to make that component up when it goes down and suppose we have a flow of jobs with us which needs to start at some particular time and get finish at some particular time then if by any reason jobs gets stuck in between and are not able to move further from a particular node point in path flow of jobs BIM will automatically check if that node point can be ignored and jobs can be transfered to next node point , in case its not posssible to move jobs to next node point then BIM is going to notify us how much time more its gonna take to finish up the jobs or what's the shortest path that we can follow now so as to finish the jobs on the required time.
Global Condition Server:-This is required when we have a job which needs to get executed on two or more different controlM server so the global conditions for that job are executed from this component because we need a EM server for the connectivity between two control M server.
Gateway:-as the name suggest is responsible for connecting Control M EM server with Control M server.All the traffic passes through it,however it doesn't has got any buffering capacity of its own like a Global Alerts Server so if large number of request are sent for processing more than the capacity of gateway to handle the request they often get dropped and we see gateway error.
So this completes a basic overview of the architecture of ControlM EM server.For more details refer the site of BMC.
No comments:
Post a Comment