servicemove
The servicemove failover program helps transfer a failed server’s workload to a secondary server. The program is run from the secondary server.
For example, upon installation, each Workflow Manager Service (idwfm) is assigned a unique ID on each server. Each Workflow Manager Service (idwfm) handles only the IDs assigned to it. A workflow request, when created, is bound to one of these IDs. So if one of the servers goes down, servicemove can be used to transfer the down Workflow Manager Service to an active server, so that the requests bound to this Workflow Manager Service service could be processed.
Usage
servicemove.exe [options] ...
Argument | Description |
|---|---|
-force | Forces a move to occur even when the remote service appears to be running. |
-list <server ID> | Specify a server ID to list services for that server, or you can specify "all" to list services for all servers. |
-move <service name> | Moves the specified service to this server. |
-release <service name> | Releases the specified service back to its home server. |
-server <serverID> | Specifies the home server of the service. |
Examples
To list services on all servers:
servicemove.exe -list all
To make the secondary server take over running the Password Manager service (
idpm) on behalf of a failed primary server, and put all the requests in queue:servicemove.exe -server <primary server id> -move idpm
To force a secondary server to take over running the Password Manager service even though the primary server is currently running:
servicemove.exe -server <primary server id> -move idpm -force
To release the Password Manager service back to its home server:
servicemove.exe -server <primary server id> -release idpm