Doorgaan naar hoofdcontent

Posts

Posts uit mei, 2010 tonen

Cordys - Exposing business process as webservice

In our project we have to trigger a business process within Cordys. In Cordys it is possible to expose the process as a webservice. This blog item describes a simple example how to do this. 1) First we create a simple business process. 2) We expose the process as a webservice. Select the process in the Cordys WorkSpace (CSP) and select Business Process Execution > Generate Web Service 3) Fill in the next window and click Finish 3) Now you have to add the Web Service to a service group, so go to the System Resource Manager and select the Cordys Services Service Add Web Service Interfaces Select Organization1 and select the ExampleProcess interface. Click Save. 4) Now you are able to call the Webservice. You can test the webservice. Select starProcess > Test Web Service Operation > Invoke 5) But how do you call this webservice from outside the Cordys environment to start a Business Process ? You can view the WSDL of this interface by startProcess > Show W...

Cordys: The ESB

I sometimes hear that Cordys is only a BPM tool. This blog item describes the ESB of the Cordys platform, also known as the SOA Grid. Introduction The BPM layer of Cordys is built and runs on the SOA grid of the BOP4 platform. This SOA Grid is the integration ESB of Cordys. It also has, like other ESBs, adapters to files, webservices, databases etc. It has transformation logic. It is all on board but maybe somewhat hidden because it is integrated within the platform. All components are services and run on the SOA Grid. It also uses maybe somewhat other terms you are already familiar with, like Service Groups, Service Containers, Application Connectors. Service Messages SOAP Messages over http are used to transfer service messages. Calling a service is done by sending a soap request. The soap messages arrives at the webserver (Apache or IIS) and there the user is authenticated. The message is sent to the Cordys Web Gateway. There the message is transferred to a Service Contai...

SOA Service Design Principles by example

First some context I a project i had to couple a PeopleSoft system with Planon. PeopleSoft is a HRM system used to store information about employees (in this case) and Planon is a facility management tool so that employees can order facilities. When a employee is employed within the company, this employee has to added to the HRM system and this employee has to be authorised within the Planon system. In the past this synchronization was done (as you see often) through a CSV file. In the new architecture this kind of synchronization has to be done through a ESB (Enterprise Service Bus). In this case the Oracle Service Bus. Service Naming I wanted to add a new Service for this, so the first thing you do it to come up with a Service Name. A couple of mistakes you often see is: * The name is the same as the project name. This is of course not done, because in a couple of months this name is forgotten and has nothing to with the functionality of the service at all (most of the time)....