Starting Suspended Process Instances

To start a suspended process instance, perform the following tasks:

1. Include project files.

2. Create a ProcessManager Client API object.

3. Suspend the process instance.

Start a suspended process instance by using the ProcessManager API (Java):

1. Include project files

   Include client JAR files, such as adobe-workflow-client-sdk.jar, in your Java project’s class path.

2. Create a ProcessManager Client API object

   • Create a ServiceClientFactory object that contains connection properties.

   • Create a ProcessManager object by using its constructor and passing a ServiceClientFactory object.

3. Start the suspended process instance

   Start a suspended process instance by invoking the ProcessManager object’s unSuspendProcess method and passing a string value that specifies the process invocation identifier value. This value can be obtained when invoking a process by using the Invocation API.

Start a suspended process instance by using the ProcessManager API (web service):

1. Include project files

   • Create a Microsoft .NET client assembly that consumes the ProcessManager service WSDL. To create a proxy object that lets you invoke its operations by using Base64 encoding, specify this WSDL definition:

     http://localhost:8080/soap/services/ProcessManager?WSDL

   • Reference the Microsoft .NET client assembly.

2. Create a ProcessManager Client API object

   • Using the Microsoft .NET client assembly, create a ProcessManagerService object by invoking its default constructor.

   • Set the ProcessManagerService object’s Credentials data member with a System.Net.NetworkCredential value.

3. Start the suspended process instance

   Start a suspended process instance by invoking the ProcessManager object’s unSuspendProcess method and passing a string value that specifies the process invocation identifier value. This value can be obtained when invoking a process by using the Invocation API.