Mass replacement of agents

[Peter Wong]

We have over 4000+ objects using an agent which is about to be decommissioned.

 

As such we would like to replace the agents with a new one that we have installed.

 

I understand that there are 2 approaches:

 

1. export to XML/change attributes in XML/import

 

2. replace agents

 

With approach 2 - the AWI hangs when it tries to search for the objects using the agent

 

 

 

 

What is the best approach to perform a task like this?

[Arun Choudhari]

Best way is to use HOST.GROUP in job instead of Agent, that way we don't have to change it in every job, just add new agent in HOST.GROUP and remove old one.

[Aravindan Thambiraj]

Hi Peter Wong,

Hope you are doing good!

The best approach to perform a task like this is to use the transport case, Export the object.

Then you can use the change utility to replace the agent with the new one & import it back to the system.

Thanks & Regards,

Aravindan Thambiraj

[Juergen Lechner]

The second best way would be to keep the agent in a VARA object and have some include in the PreProcess with a GET_VAR and a PUT_ATT to add the agents name to the attribute everytime you start the job. This would mean that a simple attribute change in the VARA would redirect to the new agent.
But I personally prefer the host group approach.

Edit: Naming an explicit agent also destroys compliance. You will need to change the atrribute when you are bringing the job via prelife into production. A host group can be named identically in all environments but contain a different agent. And you can answer to needs like more processing capacity by adding more than one agent into this group. 

Edit 2: Stating the obvious... You will need to use the change utility to peform the attribute change. Do NOT think about doing this directly in the database!! But also do NOT enter the new agent's name. Take a host group.

[Christine Bauder]

Before decommissioning the original agent, from the Administration Tab/Agent, do a right click and select 'Replace':

It should bring up a list of all jobs using that agent, then just click 'Replace':

Your new agent must be installed and your old agent still needs to be available. Note that it will replace the host in the attributes, but if you have that agent name hardcoded somewhere in a script, it will not replace it there. The screenshot above shows that it will not replace it in a script. If you have things like that, just note them and change them manually....or don't hardcode an agent in a script....lol

This is the way we have always done it as we always ran into issues using the transport case....

[Christine Bauder]

well...nevermind...I reread your question and that looks like what you have been doing...but it hangs on the search....

[Peter Wong]

Thanks all for your responses.

Doing well, Aravind. Can trust you to provide a solution!

Using unload, change and load to mass update the agents.