At a recent Impact event, IBM announced a next step towards highly integrated, easily scalable business process management environment, IBM Business Process Manager V8.0.

IBM BPM 8 includes tooling and runtime for process design, execution, monitoring and optimization and is focused on continuous and simplified process improvement, adopted for process owners and business users.

(more…)

BPM, IBM, IMPACT, v8.0 Hide

Recently, while I was trying to fit standard fault handling mechanisms to all of the invoke activities within a business process, using IBM WebSphere Integration Developer and Process Server 7.0, I have come across a very unpleasant problem:

CWWBF0135E: Starting the business process application ‘PRIO_SklepanjePoD_1.0.0App’ failed due to pending business process template updates. (more…)

BPEL, business process, fault link, IBM, IBM Software, IBM WebSphere Integration Developer 7.0, pending business template, Service Oriented Architecture (SOA), SOA, Tips 'n' tricks, WebSphere, WebSphere Application Server, WebSphere Integration Developer, WebSphere Process Server, WebSphere Process Server 7.0, wid 7.0, WPS 7.0 Hide

In April, 2012, IBM Cloud Academy Conference will take place in RTP North Carolina, U.S.

Matjaz B. Juric is Program Committee member.

More information: http://www.ibm.com/solutions/education/cloudacademy/us/en/cloud_academy_conference.html

No tags Hide

Lately, when I have been trying to install a new version (7.5.1.0) of IBM BPM environment, I have encountered an unexpected problem. I have installed Integration Designer along with Process Server and BPM Process Center (PC) on the same virtual machine. After installation, I have first created a Process Server Profile and after and then a PC profile.
Creation of both profiles went smoothly and both profiles started normally. Then, I opened Process Center Console on the second profile and downloaded Process Designer (PD) installation files. I installed PD and tried to open it. And there was a surprise. Although I have just downloaded files from process center, which was therefore obviously running, PD has displayed the following error: “Attempt to connect to the Process Center failed. Verify that the server is running.”. (more…)

Attempt to connect to the Process Center failed, changing process center url, Connection, Failed, IBM, ibm bpm, Problem Connecting, Process Center, Process Designer, updating connection url Hide

In the first post of this series we have described capabilities of IBM’s BPM platform and today we will take a closer look at Process Designer component, capable of designing and executing BPMN business processes. IBM Process Designer (PD) is a heritage of WebSphere Lombardi Edition and according to IBM enables you to model and implement your business processes and easily demonstrate process design and functionality during development efforts. In this post I will show you how to create and execute a simple process using PD.

(more…)

BPEL, BPM, BPMN, business process, IBM Integration Designer, Process Center, Process Designer, SOA, WebSphere Hide

This post is a follow up on the post where we described how to propagate a transaction from WebLogic 11g (WLS) to WebSphere 8 (WAS). Post is located here: http://www.soa.si/2011/12/20/how-to-propagate-a-global-transaction-between-oracle-weblogic-11g-and-ibm-websphere-8-0-using-ws-at/. It is describing transaction propagation in the opposite direction from WLS to WAS using WS-Atomic Transactions.

In this follow up I will describe transaction propagation from WAS to WLS using WS-AT.  I am using the same two JAX-WS Web Services as are used in the previous post. One is deployed on WAS and one on WLS. They both contain operation insert() which we use for inserting a record in a database table. For this each environment uses a separate database and has configured a corresponding XA Data Source. We implemented additional JAX-WS Web Service facade. Its role is to start a global transaction and invoke other two services inside this transaction.

Main steps:

• From the previous post we use XA-enabled data source and both web services that participate in a global transaction.
• Next step is to configure WAS transaction service for interoperability and proper WS-AT version (we used WS-AT version 1.2) using WAS administrative console.
• We can also configure WAS to use Secure Socked Layer connection for WS-AT coordination or disabling it in case we do not want to use it.
• Implement the facade Web Service. There we are calling both web services in one global transaction which is controlled using Java Transaction API (JTA). Both service clients must have attached proper WS-AT policy. We also recommended using WS-Addressing.

No tags Hide