ROB-EX and Proficy Workflow can be easily integrated by using the Service Provider implementation implemented in the Robex.Workflow.dll.
For documentation on the available services, see the .NET client documentation, since the services available in the Proficy Workflow client are exactly the same the the .NET client services.
The requirements for using the Proficy Workflow Client are listed below.
- The same requirements as the REST Server (See the REST Server requirements)
- The RestSharp.dll, Robex.Scheduler.dll and Robex.Workflow.dll. All of these dll’s are located in the “/plugins/rest/dotnet/bin” directory
- A working installation of Proficy Workflow.
Run the “/plugins/rest/dotnet/bin/SchedulerWorkflowServiceInstall.bat” command script file(this needs to be done with administrator privileges, otherwise the files will not be copied). This will automatically package and install the service provider under the Proficy Workflow installation. After the install script has finished locate and run the ConfigureSite.exe from within the Proficy Workflow ‘Program’ folder. There should be a disabled service called SchedulerWorkflowService, enable this.
Create a file called “SchedulerService.dll.config” in the Program folder of the Proficy Workflow installation folder. This should contain the connection info (see .NET documentation regarding Setting up a connection to learn the content of the file).
The Word document
<sch_dir>\docs\tech\workflow\Scheduler 5.2 with SOA to OE and PA App Note v1.docx
describes how to create orders in Scheduler based on data read from Open Enterprise. Also it shows how to update order and operation status in Scheduler based on partial completions made in Plant Applications.
The Proficy Scheduler Integration.mp4 Video
shows the end result of the configuration described in the Word document
The “PS MasterRoute Technical.mp4” Video (included in download link above) is a technical deep dive into the workflows and highlights how data is passed between Proficy modules.
FAQ / Troubleshooting
The proficy client did not start with Proficy Workflow
Consult the Proficy Workflow log (ProficyClient.log) to get an indication of the problem.