Architect Consultant blog

Introduction I am a great fan of the service orientation principles described by Thomas Erl:  http://www.soaprinciples.com/ And also of its patterns:  http://www.soapatterns.org/ This will not be a sucking up story about Thomas, but the need for a pattern on error handling. Layering One of the patterns is that of Service Layering, in which the Services can be categorized in the following layers: The Utility Service Layer consists of Services that are of agnostic functional nature and are not functional related to a business entity or business process. The Entity Service Layer contains Services that are related to business entities and are usually also agnostic. The Task Service Layer is more related to Services that are specific to a particular task or process. Usually you also have a Orchestrated Task Service layer contains Services that orchestrates Services to fulfill a business process. My question is how to deal with errors in the separate layers? Error Types Let me fi

Taken from Cordys Wiki: Cordys has always had two types of connectors. The first group of connectors are developed and supported by the Cordys platform engineers. Examples include the E-mail and the FTP connector. The second group of the connectors are developed and supported by the former Cordys professional services group (a.k.a. COE). Examples include the JMS connector and Command Connector. Some time ago the professional services group moved to CSC, leaving the status of the professional services connectors a bit unclear. People were still maintaining professional services connectors, but it became more difficult because they needed to focus on CSC projects. Not on maintaining the connectors. Another development is the creation of alternatives for platform connectors. The development of platform alternative takes a lot of time and blocks the possibility of including the enhancements into the product since they were on a different code base. So Cordys had to revise its strategy. One

Introduction The 14th and 15th September I visited the Cordial 2010 event with 5 of my CIBER colleagues. This is a small overview of the event and my findings. Overview The subtitle of the event was Accelerate Time To Value. The whole message of the event was that the Cordys offerings will shorten your time to value, a promise of all BPM vendors, but I think Cordys can actually achieve it. The majority of the presentations were about Cloud computing, so the terms IaaS, SaaS, PaaS and  BPaaS were mentioned a lot. Cordys also has launched a new product in 2009 called Cordys Process Factory (CPF). This new product was built on top of BOP4 and will nicely integrate with BOP4. The product is meant to build dynamic MashUps in the Cloud with little effort. It abstracts the more complex features of BOP4, to make it simple to use. Cordys now can offer services on premise, in the cloud and both.   Per Jonsson was presenting on his first month as the new CEO of Cordys. Quiet, calm, s

Introduction In one of my previous Blog item about Cordys BOP4, I described how Apache WebServer and Cordys BOP must be configured for using secure two-way-SSL. I discovered some behavior of this set-up which i want to share in this blog. Behavior When you configure two-way-SSL in Apache Webserver, the client certificate is used by the Apache WebServer to check whether this client may access the WebServer. However this certificate is also used by Cordys BOP4 for the identification of the User within BOP4. For this you have to configure a User that has the client certificate attached to it. * Goto User Manager > Users Roles * Select a User, Right click Edit * Select as Authentication Type: Certificate * Click Use Certificate and import the public certificate of the client (X.501 compliant) When you sent a soap message to the platform you must NOT use wsse:Security tags in the soap header anymore    Roger Password

Introduction Cloud is one of the buzzwords today and Cordys also has a Cloud platform: The Cordys Process Factory (CPF). So what is it? It is a webbased integrated cloud environment for rapid Cloud Application Development. You can build forms, business processes, integration with other webservices and reporting. How does it work? A CPF Composer is used to design forms, business processes, business rules, using external webservices, reports and charts (PDF, HTML, MS Word, or MS Excel). SaaS There is a CPF marketplace where you can sell your cloud application as a SaaS product and where you can buy other products as well. A Simple example When you fill in you credentials the Cordys Explorer or MashupComposer is shown. * Select "Create a new application" and fill in the application information, click Save and go to Composer * The Composer is shown * Select Build Forms > New Form and fill in the following details * The Forms composer is shown. Drag

Introduction This describes a review of the book: Service-Oriented Architecture: An Integration Blueprint. The book is written by Guido Schmutz, Daniel Liebhart and Peter Welkenbach. The book is about successfully implementing your own enterprise integration architecture using the Trivadis Integration Architecture Blueprint (TIAB). The authors try to set a standard for integration problems that organisation face. Chapters The book contains 5 chapters, but unfortunately the subchapters are not numbered and sometimes it is difficult to see what belongs to what. Chapter 1: Basic Principles Chapter 2: Base Technologies Chapter 3: Integration Architecture Blueprint Chapter 4: Implementation scenarios Chapter 5: Vendor Products for Implementing the Trivadis Blueprint I will dive deeper into the chapters later on, but first some general remarks about the book. General remarks As sais before I missed the subchapter numbering. The book describes an integration blueprint, so the term