Starting Webservices agent through the process tab

[Anon Anon]

Hi,

The Automic Web service agent is automatically going down due to some reasons

I am trying to start the web-services agent in UC4 service manager through the process tab of the job

When I am using TERMINATE parameter its stopping the agent in UC4 service manager, but while using the STARTUP parameter its not working

:set &agent_name# = '***_WEBSERVICES'

:IF SYS_HOST_ALIVE(&agent_name#) = "N"
:   PRINT "Agent is not alive...Starting Agent"
:   set &ACT1# = modify_system("STARTUP", &agent_name#)
:ENDIF

Thanks and Regards,

Avinash

[Luu_Le_185]

Hi Avinash,

Some thing to consider, for the "STARTUP" action to work, 1) The ServicesManager need to be available 2) The Agent/ServiceManager need to have been configured.  For example, in the Agent Attributes tabs, it should have the services manager record configured and linked.

Also, If you are putting that script within a process tab of a WebServices job that is supposed to be using the agent   ***_WEBSERVICES (that is down) then it won't be able to start up, as when that job run it will be stuck in "Waiting for host"

[Anon Anon]

Hi Luu,

Thanks for the input.

What I am trying to achieve is that the webservices agent goes down, so before starting of the workflow, I am putting a check to verify if the agent is down, if yes, then start it.

So basically start the Web-service Agent from the UC4 Service manager on the Automic Server

Thanks and Regards,

Avinash

[Luu_Le_185]

Hi Avinash,

Before doing this, I would say try this first:
-Shut down your WS agent, then create a script object and put that script you have in it and execute it.  (It should work if its been configure with the services manager).  If it does not, we can at least take a look at that first, that way we can make sure the configuration is properly set.

What I did, was I took your script there (and just replace that Agent name with a WS agent on my system).  There is a few way to do this:

This is what I had tried;
-I had put that script into the process tab of the workflow level - What this does is when the workflow launches, it will execute the script that is in the workflow process tab (since the Workflow is a container and does not require an Agent), and bring the agent up.  Afterward it start executing all the jobs that within the Workflow.

-The other method is to use the EXECUTE_ON_END, what this does is that whenever the Agent goes down, it will then execute the specified object name (in this case, the script you had provided there).

What I did was to create a UC_HOSTCHAR_MYWEBSERVICE  then in the UC_EX_HOSTCHAR set the Webservice agent to use the newly created UC_HOSTCHAR_MYWEBSERVICE.

After that I created a Script object and put your script you provided there (and changed the name of the agent to match the one in my system).

Next within my newly created UC_HOSTCHAR_MYWEBSERVICE, I set the "EXECUTE_ON_END" where the "Value" is, I put in the name of my script object.  (Notes - The Agent need to be restarted once, for this to start working

Some reference:  on the UC_HOSTCHAR and EXECUTE_ON_END
Some reference:  on the UC_EX_HOSTCHAR

[Anon Anon]

Hi,

Thanks for the input. Would try your suggestion

- Avinash

[Luu_Le_185]

Hi Avinash,

Did either of those worked for you?

Also if you are continuing to have issue with that Webservices disconnecting randomly, I would recommend opening a ticket with Support as they can assist in trying to find out root cause.