Required additional steps

Restarting the Server Object Manager

As part of the Server Object Manager (SOM) Component feature installation, additional elements are added to the SOM configuration. An update was made to the ServerTypes.dat file to include the definition of the Workflow Manager Server Object, and the Workflow Manager Web services WSDL definition file was added to the XmlSchema directory.

The Update to the ServerTypes.dat file requires an SOM restart so that any Workflow Manager server objects are recognized by your ArcGIS Server.

For the WSDL to be recognized by the Web services, it may also be necessary to restart the server manager host. For Server .NET, restart IIS. For Server Java, restart the ArcGIS Server Manager service.

Creating Workflow Manager Server Objects

To take advantage of the Workflow Manager Web services, you must create a Workflow Manager Server Object. There are two methods to complete this process:

• Using ArcCatalog
• Manual Deployment

Manually deploying a Workflow Manager Server Object

You can deploy the Workflow Manager Server Object on a machine that does not have ArcGIS Desktop installed by following these steps:

Steps:

1. Copy a .jtc file to a location your ArcGIS Server Container account has read access to.
2. Copy the service configuration file Example.WMServer.cfg from <Workflow Manager Server Install location>\cfg to <ArcGIS Install Location>\Server\user\cfg.
3. In <ArcGIS Install Location>\Server\user\cfg, rename the <Example> part of Example.WMServer.cfg to something more meaningful, for examples, WMX or <.jtc file name>.
4. Edit your xxx.WMServer.cfg file.
5. Enter the path to your .jtc file where it says <! --Enter the path to the .jtc file here-->.
6. Choose whether to manually manage the transactions or not.

   The Manual Transactions option allows you to choose whether the database transactions are managed by the server object itself or by the client consuming the server object. If the option is set to FALSE, the server object will manage all transactions for the client, so there can be no wrapping of the calls in additional transactions. In the case where the client needs to manage transactions itself (that is, wrap multiple calls in one transaction), this option should be set to TRUE, and no transactions will be created within the server object calls.

7. Optionally, update any of the other standard ArcGIS Server service properties.

   For guidance on how these properties are used, please see the ArcGIS Server help.

8. Save changes and stop editing the file.
9. Restart the ArcGIS Server Object Manager service.

Workflow Manager Server Objects in the ArcGIS Server Manager

At this time, it is not possible to create a Workflow Manager Service through the ArcGIS Server Manager. However, once the server object has been created, you can view, start, and stop the service from the Server Manager.

It is also possible to export the Workflow Manager Web services from the server manager.

Reasons why the Workflow Manager Server Object won't start

• The ArcGIS Server Object Container account doesn't have access to the location where the .jtc file is stored.
• The database the .jtc file is pointing to doesn't exist, or a connection cannot be made.
• The database the .jtc file is pointing to has a schema that doesn't match the current version.

If all these things pass the test, review the ArcGIS Server logs for error messages written during the starting process.