Job run on sever with certain alias

[andreasd]

Dear all,

I am using Control-M 7.
I would like to define a job that runs on the server with a certain alias or FQDN. The IP address of the alias can change between two servers.
Jobs should always run on the first server. If the first server is down the IP address of the alias will be configured on the second server.

I have my alias written in the job node id / group. The result is that Control-M says: "no agent nodes available for job's node-group".

In the file CONFIG.dat I have configured the parameter LOGICAL_AGENT_NAME to the hostname. Is that the reason for the error message.
Would it be possible to add a second value for the parameter LOGICAL_AGENT_NAME?

We also have AFT Jobs that should not be affected in the first step.

Does anybody know how to solve my problem?

[andreasd]

Hello,

I found the solution.

I have created a nodegroup and I have only the active server in the nodegroup.

ctmnodegrp -EDIT -NODEGRP

[mauriziog]

From the version 7.0 you can manage the nodegroup from the Configuration Manager (CCM).
But the manner you have described I dont understard in witch manner if the first host is not available you automatically switch the executions on the second node.
Seems a configuration like cluster in active-passive mode.

I think you can:
- install the agent in the cluster mode, so you point only to the logical name.
- configure the load balancing in controlM

Regards

[Juressen]

We had a requirement to duplicate the batch flows, without using an additional machine. By defining an alias, and installing a separate Control-M agent with the alias name characteristics we were able to do so.

[Michaeljohn]

and I have only the active server in the nodegroup.


_______________________________________________
WOW Gold|GW2 Gold|Aion Kinah|Diablo 3 Gold Kaufen