Architect Consultant blog

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

With the support of SCA within the Oracle SOA Suite 11g you get basically two busses: The Mediator (the "old" OESB) and (as a separate product) the OSB 11g. The Mediator is positioned as wiring intra Composite and the OSB to wire enterprise Services. A question that puzzles me is if it is wise to (always) expose all Services via the OSB? In that case the OSB is your abstraction Service entry layer and all Services are reachable and configurable through the bus. This way you use the loose coupling strategy of Proxy- and Business Services within the OSB. What is your experience or opinion on this?

De volgende tabel geeft een mooi overzicht van WS-* standaarden die gevolgd kunnen worden voor Web Services. Standaard Advies Alternatieven Orchestration BPEL WS-Choreography, WS-CDL Management WS-DistributedManagement, WS-Provisioning, WS-Management Security WS-Security WS-Trust, WS-Federation, WS-SecureConversation, WS-SecurityPolicy Transaction WS-Transaction, WS-Coordination WS-CompositeApplicationFramework (WS-CAF), WS-Context (WS-Ctx), WS-CoordinationFramework (WS-CF) Reliability WS-ReliableMessaging WS-Reliability Description WSDL, UDDI WS-Inspection, Disco, WS-Discovery, WS-PolicyFramework, WS-MetaDataExchange Messaging XML, SOAP WS-Addressing, WS-Notification, WS-ResourceFramework, WS-Eventing, WS-Policy, SOAP with Attachment Transport HTTP, JMS, RMI-IIOP TCP, UDP, Jabber, SMTP Interoperability WS-I Basic Profile Mochten er toevoegingen zijn, dan voel je vrij om een Comment te plaatsen.

When I wanted to test a WSDL I looked accross the internet for a free test tool and found a great tool: soapUI . With this tool you are able to: Test operations Set assertions on it Create test suites Create mocks Test REST, SOAP and HTTP interfaces Load testing

Just like Design Patterns, Enterprise Integration Patterns and Architecture Patterns, Thomas Erl comes with a SOA Design Pattern book. InfoQ has an interview with him: read interview He states that a SOA patterns is something different than a webservice patterns. SOA is about services and a webservice is a technology specific realization of a service. He also states that in fact EAI frameworks and middleware, enterprise service bus platforms, grid computing, transaction management systems, messaging queues, event-driven messaging frameworks, broker and mediation technologies were used as inspiration for the SOA patterns. He also explains his difference between service orientation and a SOA: "Service-orientation is a distinct paradigm that you apply to achieve a specific target state and a technology architecture is considered service-oriented if it has the characteristics necessary to support the application of this paradigm." Nice and clear right? I have not read the book (y...