BPM, Workflow, and Case

 View Only

The configuration topology for BAW Case feature

By Terence Li posted Tue October 18, 2022 05:14 AM

  

Since Business Automation Workflow V18.0.0.1, IBM® Business Process Manager and IBM Case Manager are combined in a single product and a single installation. IBM Content Navigator (ICN) and the Content Platform Engine (CPE) are included in the product installation. We received several PMRs about the configuration topology for case feature recently, here the possible supported topology are summarized.

1. The embedded CPE and ICN.

By default, after the BAW deployment environment (DE) is created, the embedded CPE and ICN are available, so this topology is easy for you to configure the Case feature, it is mainly for the test/dev purpose, but it is not recommended as the product environment if you want to use the case feature.

2. The external CPE and external ICN.

The CPE and ICN can either be installed on traditional Websphere Application Server (tWAS) v8.5.5.x or v9.x. Only standard and cluster CPE environments are supported, single server or multiple server (noncluster) network deployment CPE environments are not supported.

The customer installs the independent CPE and ICN,  then run the setBPMExternalECM and setExternalNavigator command to switch to external CPE and ICN.

2.1 The external CPE and external ICN are installed separately.


2.1.1 Clustered environment for BAW, CPE and ICN.

BAW, CPE and ICN are all clustered environment. Here are 3 different tWAS installation for BAW, CPE and ICN.

2.1.2 Standalone environment for CPE and ICN.


BAW is always clustered environment, but CPE and ICN can be standalone server. Here are 3 different tWAS installation for BAW, CPE and ICN.

2.2 The external CPE and external ICN are installed together.

BAW is always the clustered environment, CPE and ICN can be installed in single tWAS cell. Here are 2 different tWAS installation for BAW and CPE + ICN, CPE and ICN shares the same Dmgr.

2.3 BAW, external CPE and external ICN are installed together.

BAW, CPE and ICN shares the same BAW Dmgr, BAW must be installed on each node, otherwise the node agent will complain missing jars. Although we don't find problem for this topology, but we can not guarantee if there is possible configuration conflict between BAW and CPE in future release, so it is not recommended.

2 comments
97 views

Permalink

Comments

Wed February 15, 2023 01:08 AM

It is not supported, because BAW is based on tWAS v8.5.5, and the FN+ICN are on tWAS v9.x in your scenario, they can not share the same dmgr.

Tue January 10, 2023 04:47 AM

Is it possible to share one DMGR for BAW and FN+ICN in configuration in chapter 2.2 - if FN+ICN are on tWAS v9 and BAW is on tWAS v8.5.5?