Doorgaan naar hoofdcontent

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 WSDL
What I noticed was the strange looking endpoint:
<wsdl:service xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" name="ExampleProcessService" >
   <wsdl:port xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" name="ExampleProcessPort" binding="tns:ExampleProcess" >
<soap:address xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" location="com.eibus.web.soap.Gateway.wcp" />
</wsdl:port>
</wsdl:service>
I used the Fiddler tool and the Test Web Service tool (described in step 4) to see what the endpoint must be:
In the VM image of this Cordys installation this is http://192.168.154.128/cordys/com.eibus.web.soap.Gateway.wcp
In fact this is the Gateway endpoint of Cordys.
So now you can use the WSDL and this endpoint to test it within soapUI.

Reacties

  1. just linked this article on my facebook account. it’s a very interesting article for all.
    Agile Process

    BeantwoordenVerwijderen
  2. Hello Charles,

    Thanks for the link on Facebook !

    Regards,
    Roger

    BeantwoordenVerwijderen
  3. Deze reactie is verwijderd door een blogbeheerder.

    BeantwoordenVerwijderen

Een reactie posten

Populaire posts van deze blog

OSB 10gR3 and SWA and MTOM

This blog is about using soap with attachments and the use of MTOM within the OSB (10gR3). A service is created that accepts a soap with attachment (DocumentService) and translates it to a service that accepts a binary element. MTOM is used for performance reasons for the second. Some notes: * For the use of attachments you need RPC-style document instead of the usual document-style. This due to the fact that the document-style limits a message to a single . * A service can not have both SWA and MTOM within OSB. First a WSDL is setup for the DocumentService: The $attachments variable holds the attachments and the body holds the attachment data. Also other data is stored within the attachment element (see h

Microservices mindmap

"The tree" - See also   my photo page When you are fairly new within the Microservices land, there are a lot of terms fired at you. So also for my own understanding i have made a mindmap. I think it has a good status now, so that i can share it with you. As always feedback is very welcome ! You can download the mindmap here .

Book review: Data Management at Scale (Piethein Strengholt)

 This blog is a review of the book "Data Management at Scale (See also at bol.com ) Data Management is a hot topic nowadays and this book does a fantastic job at adding value to this topic. It is a must read and one of the few technical books I finished reading in a weekend. The book gives a fantastic overview on how to implement a Data Mesh data architecture. The Data Mesh concept is explained by Martin Fowler here . The book is a good mix between conceptual and implementation architecture level. It gives a lot of examples of how this architecture at scale can work, for both small and big companies. It is practical and I used it to implement it at one of my customers. The book describes an architecture in which the focus is on the DIAL (Data- and Integration Access Layer).  On a high level the book covers the following topics: The key principles for data management at scale - Domain-Driven Design  - Domain Data Stores - Meta data management Ready Data Store The concept of servin