A working simulation with sample objects and workflows
The MarcomCentral Connect feature includes a complete simulation that demonstrates how to exchange information using calls to MarcomCentral web services. The web services connect RICOH ProcessDirector objects and workflows to a sample store at the MarcomCentral web site. The sample store serves as a test environment for the RICOH ProcessDirector web services interface to MarcomCentral.
The simulation has these objects and workflows:
The MarcomReceiveOrders sample SOAP web service input device simulates a call to the MarcomCentral web service that returns orders by date. The input device retrieves sample orders, turns them into jobs, and assigns them to the MarcomProcessOrders workflow.
The MarcomProcessOrders sample workflow processes MarcomCentral orders. It converts MarcomCentral order information into RICOH ProcessDirector job properties. The workflow retrieves the job ticket for each item in the order and creates a child job for each job ticket. The workflow submits the child jobs to the MarcomProcessJobTicket workflow.
The MarcomProcessJobTicket sample workflow processes MarcomCentral job tickets. It converts job ticket information into RICOH ProcessDirector job properties. The workflow uses MarcomCentral stock-keeping unit (SKU) IDs to get information about how to process the items in each order. The workflow sends each printable item through a branch that downloads a file and prints it. The workflow sends each non-printable item through a branch that holds the job until the warehouse confirms that the item has been added to the order.
When all items in the order have completed processing, the MarcomCloseoutOrders sample SOAP web service notification simulates a call to the web service that closes the order. If the notification actually called the web service, the web service would close the order in the sample store. The status of each item in the order in the sample store would change to Shipped.
This illustration shows how the RICOH ProcessDirector input device, workflows, and notification call MarcomCentral web services to exchange information with a MarcomCentral store.
The following illustration highlights three steps in the MarcomProcessOrders workflow:
This step converts information in MarcomCentral format to RICOH ProcessDirector job properties.
This step calls the MarcomCentral Job Tickets web service and retrieves the job tickets for each order.
This step uses the information returned by the MarcomCentral web service to create a job for each job ticket. The step submits the jobs to the MarcomProcessJobTicket workflow.
The third illustration highlights six steps (one step is actually a set of steps) in the MarcomProcessJobTicket workflow. The workflow includes two ApplyXSLTransform steps, a CallSOAPService step, and a DownloadFile step. The step DownloadFile uses a URL provided with the job ticket information to download a print file. The workflow also includes a set of steps for printing files and a step for processing non-print items.
After you run the simulation and examine how it works, you can modify the samples and connect them to your store at the MarcomCentral web site. For example, you can add steps to access an external data source with the information required to process items ordered at your store. You can replace the printing steps in the MarcomProcessJobTicket workflow with the steps in your production workflow or send child jobs to multiple production workflows. You can add notifications to send additional information to MarcomCentral. For more information, see the related tasks.
Job properties and sample files for converting information
The MarcomCentral Connect feature includes job properties and sample XSLT style sheets:
The MarcomCentral order ID, MarcomCentral order number, MarcomCentral job ticket ID, and MarcomCentral product type job properties receive values converted from XML elements in MarcomCentral orders and job tickets.
Five XSLT style sheets show you how to convert XML elements into job properties for the order job and for each ticket job.
The MarcomCentral Connect feature requires the Web Services Enablement feature.