Doorgaan naar hoofdcontent

OpenText Process Suite 10.5 platform

Introduction

With the acquisition of Cordys this year, i was curious about the integration with OpenText. At the Enterprise World 2013 some insight is already given. This will be a short recap.
You may also listen to Brian Wick here.

Process Suite 10.5 Platform

There was a tweet from @r that showed the content of the process suite platform of OpenText.


It also shows that Cordys is rebranded to "OpenText Cordys 10.5". The platform and BPM offering of OpenText can be visualized as:


The suite is composed of several components:

  • OpenText Cordys 10.5This is the core component of the suite with BPM and Case Management 
  • Unified UIThere comes a unified UI with HTML5 support that is integrated within BMPM, Case360, Process360 and Execute360
  • BPM EverywhereThis is a new social platform that lets users collaborate on cases.
  • AppWorks GatewayThis gives a set of RESTfull APIs on top of OpenText EIM produkts to integrate the data, taken from EIM, with the processes.
  • Process IntelligenceComponent for businesss intelligence and analytics
  • Process Component LibraryThis is a set of components that can be used by IT or business to assemble applications.
  • Cloud ProvisioningAll developed apps can be made available to the Cloud using the Cloud Provisioning component

There are a few ways to develop BPM apps:

  • Packaged AppsThese are apps that are fully pre-developed and only need some configurations. This way customers have a fast solution.
  • Assembled AppsWith the use of the Process Component Library customers can easy and quickly develop new apps.
  • Model Driven AppsWith the use of the BPM development environment, customers can make custom apps.
  • Coded AppsWith the use of the AppWorks gateway, customers can easily expose data with this API.

Also more information can be found on Process Suite 10.5: 

Process Suite 10.5

Reacties

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