Doorgaan naar hoofdcontent

Cordys: Contract First design

Introduction

One of the principles of Service Design is Contract First. With this principle you first design the service contract of the service and then implement it. This blog item will show a small example within Cordys BOP4.

Contract First

First I will create a simple HRM Employee service first. The WSDL can be found here



Before you can use this WSDL you have to import the WSDL.
  1. Create a Project with com/examples Folders

  1. Create new Web Service document in com/examples Folder

  1. Select Import WSDL and name the service, click Next

  1. Now you have to fill in the URL of the WSDL. I have installed Cordys on my Windows machine and put my EmployeeService within the <CordysInstallDir>/Web directory. This way the WSDL is accessable through a URL. Select Show Services to view the service defined within the WSDL. Check Interface WSDL, because it is just the interface and not the implementation we are importing.
  1. Now you are able to use this as a basis to define a Contract Based Business Process Model. Create a new Business Process Model within the same Folder with the following Properties. You must check Contract and select the Interface just imported in the previous step.

  1. When you press OK, a skeleton Process is generated for you with Process messages.



Regards, Roger

Reacties

  1. Hi Roger,

    The WSDL is not correct and can't be imported. Namespace s: should be XSD, the INPUT tag at line 28 is not closed and the SOAP namespace is defined in lower case. But the principle of CFD is made very clear.

    BeantwoordenVerwijderen
  2. Hello Jan,

    Thank you for the remarks. It seems always difficult to import the WSDL into Blogger, so I have used a link now.

    BeantwoordenVerwijderen

Een reactie posten

Populaire posts van deze blog

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 .

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...

Cloud to Cloud Application Integration

A lot of applications have integration possibilities, so do cloud applications. The question I got from a customer is whether to have a point-to-point integration with Cloud applications or to go through their ESB solution. This blog describes some considerations. Context The customer has a HRM application in which job vacancies are managed. Furthermore that system also handles the full applicant process flow. They also have another cloud application that handles the job vacancies. This application posts the jobs to social sites and other channels to promote the vacancies. Furthermore this application has some intelligence for job seekers to advice some new vacancies based on previous visits or profiles. The job vacancies need to be sent to the Vacancies application and applicant information needs to be sent to the HRM application, when a job seeker actually applies for a job. Furthermore status information about the job application is als...