Flow Designer Action in SSH step. How to communicate between MID Servers

[Sato3]

Should I follow such a Flow Step to communicate between MID Servers using the Flow Designer Action in SSH step?

What I want to achieve is when MID Server A is in the Up state and MID Server B is in the Down state, MID Server A passes an SSH command (./start.sh) to MID Server B to restart it.

Best regards

[Hitoshi Ozawa]

Hi Sato-san

Why not just setup a Fail-over MID server cluster?

https://docs.servicenow.com/bundle/quebec-servicenow-platform/page/product/mid-server/task/t_Configu...

Setup a MID server cluster and select cluster type to "Failover".

https://docs.servicenow.com/en-US/bundle/sandiego-servicenow-platform/page/product/mid-server/task/t...

[Sato3]

Hi, @Hitoshi Ozawa san

>>>Why not just setup a Fail-over MID server cluster?

The reason for not using a cluster is that there is an administrative audit of who restarted the MID Server.

Therefore, it is desirable to use Flow Designer with Service Catalog.

What steps do you need to take in SSH-savvy Flow Designer to interact with MID Servers?

Best regards

[Hitoshi Ozawa]

MID Server is used to connect ServiceNow network with user's internal network. If the MID server is down, ServiceNow would not be able to access user's internal network. So if the MID Server is down and ServiceNow is not able to connect with company's internal network, how will the MID server be started?

[Sato3]

Hi, @Hitoshi Ozawa 

As you say, if the MID Server is down, I don't think the access itself can be started.

As a start method, it is an image to pass the command to the target MID Server by SSH as if you type ./start/.sh directly at the command prompt.
MID Server should start this way.

But I don't know how to pass SSH from MID Server via MID Server.