Doorgaan naar hoofdcontent

Cordys bought by OpenText. And now?

OpenText has bought Cordys.
Some links:

http://www.cordys.com/opentext

http://www.opentext.com/2/global/company/news/press-releases/press-release-details.htm?id=66B58B6F88534A9CA41B4E14A6018C6A

http://www.cmswire.com/cms/information-management/opentext-buys-cordys-offers-integrated-bpm-information-management-022146.php

From these articles we can conclude for now that:

  • OpenText wants to expand on BPM and Case Management
  • OpenText want to become leader within Cloud and PaaS marketplace
  • Cordys will be referred as OpenText Cordys 

As a certified Cordys Solution Architect I wonder:

  • What will remain of the Cordys produkts?
  • How will current clients be supported by OpenText?
  • What will be used of the strong Cordys Cloud proposition with its multi-tenant concept?
  • Will the user interfaces of Cordys be adapted, so a uniform interface will be used on multiple process engines?
  • How will Cordys be integrated within the current BPM offerings of OpenText
  • Will Cordys get a greater customer base?

We will find out the next months ...
Labels:

Reacties

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
12 reacties
Meer lezen

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 .
48 reacties
Meer lezen

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
5 reacties
Meer lezen