IBM Business Automation Workflow on Containers Technical Introduction - PDF Free Download (2022)

Transcription

1 IBM Business Automation Workflow on Containers Technical Introduction Technical Overview Version Paul Pacholski SWAT Digital Business Automation Brian M. Petrini Technical Offering Manager Business Automation Workflow Latest version: IBM Corporation

2 Agenda Introduction Licensing and Support BAW on Containers Runtime BAW on Containers Development 2

3 Cloud Paks Enterprise-ready containerized software A faster, more secure way to move your core business applications to any cloud through enterprise-ready containerized software solutions IBM containerized software Packaged with Open Source components, pre-integrated with the common operational services, and secure by design Container platform and operational services Logging, monitoring, security, identity access management Complete yet simple Application, data and AI services that are modular, term licensed, and easy to consume IBM certified Full software stack support, and ongoing security, compliance and version compatibility Run anywhere On-premises, on private and public clouds, and in pre-integrated systems 3

4 Cloud Paks Pre-integrated for cloud use cases Today, IBM offers clients the first six Cloud Paks Cloud Pak for Applications Cloud Pak for Data Cloud Pak for Integration Cloud Pak for Automation Cloud Pak for Multicloud Management Cloud Pak for Security Developer & DevOps Tools Modernization Toolkit Organize Analyze API Lifecycle Messaging and Events Content Operational Intelligence Multicluster App and Infrastructure Federated Search and Investigation Incident Response Frameworks and Runtimes Collect App and Data Integration Workflow and Decisions Security and Compliance Management Security Orchestration and Automation Container platform and operational services Container platform and operational services Container platform and operational services Container platform and operational services Container platform and operational services Container platform and operational services IBM Cloud AWS MS Azure Google Cloud Edge Private Systems 4

5 Multiple ways to deploy the automation platform On-Premises On-Premises Any Cloud SaaS Individual Modules Cloud Pak for Automation DBA on Cloud License individual modules separately Traditional on-prem install One license gives entitlement to both certified containers and traditional on-prem install Fully supported on Red Hat OpenShift Container Platform OpenShift Container Platform included Move to containers at your own pace Fully Managed Software-as-a Service Runs on IBM Cloud 5

6 Three ways to run Cloud Pak for Automation Embraces next-generation hybrid multicloud Cloud Pak platform Your own environment * Your own environment on Cloud Pak System OpenShift Managed Service on IBM Public Cloud Install and run on your own Red Hat OpenShift Container Platform Cloud Pak System includes hardware preintegrated with VMware and IBM Cloud Pak for Automation (Includes licenses for Cloud Pak for Automation) Fully managed OpenShift containers running on highly scalable and reliable IBM Cloud platform (Client provides licenses for Cloud Pak for Automation) 6 * Install and run on your own Red Hat OpenShift Container Platform or any CNCF certified K8s Platform

7 CP4A components and deployment options New Business Automation Workflow FileNet Content Manager Operational Decision Manager Datacap Enterprise Records Content Collector Business Automation Content Analyzer Business Automation Insights Automation Workstream Services Business Automation Studio Business Automation Application Designer Automation Digital Worker Deprecated Legend Traditional On-premises Cloud Native Containerized Traditional & Containerized Versions 7 7

8 IT Value of Workflow Containers Cloud Pak for Automation Unified platform experience Better component reuse New capabilities: Studio, App Builder, Workstream Services, etc. IBM Cloud Pak for Automation Red Hat OpenShift Application Lifecycle Services based on Operators: Installation services, packaging, servicing and updates Common diagnostic services: Logging, monitoring, and metering Kubernetes Commodity infrastructure skills Standardized load balancing More scalable: policy-based auto-scaling Innate High Availability Continuous Availability: no down-time for upgrades for minor updates Better application isolation: Faster and cheaper to create an additional application domain Improved application portability Topology Best Practice out-ofthe-box (Operators) Docker - Standardized provisioning (installation) - Much faster environment creation - Reduced support costs - Docker containers are provided by IBM and considered "read only" black boxes - Simpler updates - Applying a cumulative fix or just an ifix is a new Docker image. - More flexible architectures - A mix of different runtimes such as Jakarta (Liberty), JavaScript (Node.JS), or even C/C++ (MQ). - Faster delivery of product capabilities - a benefit of microservices WebSphere Liberty Smaller package: 800 MB for Liberty container vs. multiple GB for traditional Faster start up time: 10s of seconds vs. several minutes Simpler configuration: 100s down to dozens of configuration parameters IBM Automation / 2020 IBM Corporation 8

9 Container Federation by Default All tiers are for all application domains - Task federation (PFS) - Single UI tier (Navigator) - Common content services (CPE) - Global Teams (UMS) -Aggregated monitoring/kpis (BAI) - Federated BPM Portal - All application tier federated by default (BAW) Each tier is independently scalable using auto-scaling to optimize resources Greatly reduces cost of application isolation only need to have another application tier (BAW) - Avoid resource contention Simplify migration from BAW traditional - Start new work on the container environment, finish existing work on traditional environment Federated environment 9

10 Workflow for Multicloud Strategy Business Automation Workflow Automation Workstream Services Developer Developer IT Developer Developer Developer Business Developer Case Builder Web Process Designer Integration Designer Case Builder Web Process Designer Workplace Case Process (BPMN) Process (BPEL/SCA) Process Portal & Case Client Process Portal & Case Client Case Process (BPMN) Workplace 10 WAS-ND (traditional) & VM (VMWare, AWS, Azure) OpenShift, CNCF

11 What is Workflow Server on Containers? Runtime Environment Development Environment Workflow Server Packaged as Docker Containers Most containers based on WebSphere Liberty Deployed as Pods Managed by K8S runtimes i.e. OpenShift Supported Solutions must be Case Solutions Process App Workflow Server management Deploy Configure Console support Tools run on Traditional WAS not in Containers Process Designer Helps to convert from to Flags all the artifacts that need to be converted including toolkits Once a target environment is selected provides authoring artifact that match the project type Workflow Center Provides support for tagging Solutions Enables to create install package for remote deploy to Workflow Server on Containers BAW supports two Target Environments: 11 Traditional Only Traditional or Container

12 Workflow Server on Containers What s supported? 12 High Availability and Disaster Recovery Load balancing, clustering, high-availability, and disaster recovery will rely on Kubernetes not on WAS ND Infrastructure ops, including admin APIs and tuning Will not be able to rely on WAS ND features (wsadmin and WAS Admin Console) The functionality and features will remain the same but relay on REST APIs and Kubernetes The following BAW capabilities are supported in the container environment: Process apps, case solutions, and toolkits that are built with the web-based IBM Process Designer that do not use deprecated APIs or deprecated features. See Artifact support in traditional and container runtime environments. Online and offline deployment from IBM Workflow Center REST Operations APIs and REST Runtime APIs IBM Business Automation Insights event emission Process Admin Console (only UMS based users are supported) Process Portal Playback server in the Workflow Center Connected and disconnected snapshot install

13 Workflow Server on Containers What s not supported? 13 Deprecated features are not supported Processes See Deprecated and removed features of IBM Business Automation Workflow Deprecated artifacts that are created in the desktop Process Designer are not supported in containers. Exception: Heritage Human Services Although heritage human services are supported, heritage coaches that are included in heritage human services are not supported. See Artifact support in traditional and container runtime environments. LiveConnect API To invoke Java from JavaScript in applications that are running in a container environment Cases Case forms WAS ND dependent capabilities are not supported (due to architectural differences in Liberty) Advanced capabilities Applications created with Integration Designer: BPEL processes, Mediation flows, SCA applications Advanced Integration Services Dashboards that do not support Federated API The Process Performance dashboard, and the Team Performance dashboard in IBM Process Portal Monitoring capabilities Performance Data Warehouse Monitor models for IBM Business Monitor in process apps and toolkits Dynamic Event Framework (DEF) XML event emission Web Services Policy Sets Playback in the container runtime environment Integrations based on the integration.jar: SQL integrations, IBM MQ and JMS integrations, XML validation and transformation

14 Agenda Introduction Licensing and Support BAW on Containers Runtime BAW on Containers Development 14

15 Licensing/Entitlement Licensing BAW on containers are licensed per VPC (charge for engine containers only: BAW/CPE) Entitlement All BAW customers and CP4Auto customers with current entitlements have access to the containers on June 26, 2020 BAW IBM Cloud Pak for Automation Since BAW itself is part of the CP4A bundle, BAW containers will also be available for all CP4A customers with current entitlements. 15

16 BAI is packaged as a supporting program BAW includes BAI (officially CP4A, but only the BAI capability) as a supporting program with the following restrictions: The license will limit its usage to only collecting events from BAW (Case, BPMN, and BPEL) and it will be capped at a specific number of VPCs for the Flink job. The number of VPCs we are working out, but it is probably around 6. So if a customer wants to collect events from other sources than BAW, they would need to trade up to CP4A. If they exceed their capacity for event processing they would need to trade up. This includes the BAI Single Server and BAI Containers/K8s with the following supported scenarios: 1. BAI Container/K8s and BAW traditional - this we've supported since BAW BAI Single Server and BAW traditional - expected usage and supported 3. BAI Container/K8s and BAW on containers - expected usage and supported 4. BAI Single Server and BAW on containers - non standard configuration and not supported. Learn more about IBM BAI Knowledge Center: Presentations: 16

17 Supported Environments and Support Policy Support Policy The IBM Business Automation Continuous Delivery Support Lifecycle Policy: Based on the IBM continuous delivery support model: Supported Environments BAW containers will support certified Kubernetes (CNCF), including OpenShift. BAW will only provide the containers and the operators. CP4Auto includes OpenShift licenses. BAW V2.0. Announcement Letter 17

18 BAW on Containers Runtime Kubernetes Introduction Docker Images and Pods Server Management and Administration Install Process Federation Server Process Portal 18

19 WebSphere Cell versus Kubernetes Cluster WebSphere Cell Kubernetes Cluster admin end users admin end users Dmgr Master node Node 1 Node 2 IBM HTTP Server Worker Node 1 Worker Node 2 Infra Node 19 Exposes master node

20 WebSphere Cell versus Kubernetes Cluster Datasource WAS Cell JNDI props Persistent volume K8s Cluster Config map Master node Connection factory KeyStore HTTP transport Auth alias Ingress Role Binding Role Secret Worker Node 1 Worker Node 2 Worker Node N.ear application.ear application Pod Pod Pod 1 Pod 1 Pod 1 Pod 2 Pod 2 Pod 3 Pod replicated across all Nodes Pod replicated across 2 Nodes 20 Pod singleton (i.e. resource registry)

21 Operators Workflow Server on Container installation, config changes and upgrade is based on Operators An Operator is a method of packaging, deploying and managing a Kubernetes-native application Based on Ansible to support full pod lifecycle (from install to scaling) Operator is running in a Pod on the cluster Interacts with the Kubernetes API server. Introduces new object types through Custom Resource (CR) Watches CRs and is notified about their presence or modification. Ensures the Pods defined in CRs are actually available and configured in the way the user expressed in the object s specification More about operators: 21

22 BAW on Containers Runtime Kubernetes Introduction Docker Images and Pods Server Management and Administration Install Process Federation Server Process Portal 22

(Video) IBM Business Automation Content Analyzer

23 BAW on Containers (Pods) Runtime (Workflow Server) Workflow Workflow Server Liberty DBA Navigator Navigator Liberty BAW DB Test / UAT/ Production Workflow Server User Management Workflow Messaging (JMS) Content Platform Engine CPE Liberty LDAP Business Automation Insights (BAI) Process Federation CMIS Resource Registry (etcd) OpenShift & CNCF Kafka ELK including Elasticsearch Not required for minimum configuration BAW on Container means: Workflow Server on Containers only BAI requires Pods not built by IBM ELK and Kafka If ELK is not supplied, then PFS and BAI both use their own Elasticsearch installed by the operator (BAI & PFS installs its own Elasticsearch) Db2 and LDAP Is supplied in the demo install package as Docker Containers Enterprise install enables to connect to exiting Db2 and LDAP instances BAW DB: used by BAW, UMS, Navigator LDAP: used by CMIS, Navigator, CPE, UMS 23

24 What s in the Workflow Server Pods? CMIS Liberty CMIS Case Client Case Admin BAI Emitter Process Admin Case Client Case Admin Workplace Liberty Process API Process Runtime Case API Case BAI Emitter ETCD Resource Registry DBA Navigator Case Runtime Liberty Repository Federated Process Portal Liberty Case Runtime JMS Liberty User Management Liberty Federation Server Liberty CPE Workflow Server Workflow Messaging User Management Process Federation CPEDB CPE tables BPMDB ProcServer Messaging ME tables LDAP Elasticsearch 24 Loaded / deployed see next chart

25 Workflow Server Pods - Key Component Dependencies Case Client Case Admin Workplace Workflow Server uses External Navigator Workflow Server does not use embedded Navigator and CPE. Process Portal Liberty Loads Plugins Case Client Process Admin DBA Navigator Case Admin Process API Workplace App Node.js Application Engine Case Runtime Liberty CPE Required by Automation Workstream Services (optimal) Deploys Case Solution Artefacts Case API Federated Process Portal Case Runtime BAI Emitter Liberty Workflow Server Process Engine Repository Case BAI Emitter 25 CPEDB CPE tables Case SOR External Content Platform Engine (CPE) used by Workflow Server BPMDB ProcServer Object Store dedicated to process instance document attachments is now configured in external CPE

26 BAW on Containers Runtime Kubernetes Introduction Docker Images and Pods Server Management and Administration Install Process Federation Server Process Portal 26

27 BAW on Containers Runtime BAW Admin On-prem customers moving to containers are accustomed to on-prem admin experience Container based BAW supports: 1. Process Admin Console for Workflow Server process administration 2. ACCE for content administration BPM Process Admin Console DBA Navigator Workflow Workflow Server Liberty Content Platform Engine (CPE) Test / UAT/ Production Workflow Server User Management Workflow Messaging (JMS) CMIS Process Federation Elasticsearch Resource Registry (etcd) 3. Case Manager Admin Client for Cases administration 4. PFS Admin REST API and ES Head ACCE & Case Admin BAW DBs LDAP PFS Admin OpenShift & CNCF 27

28 BAW on Containers Runtime Admin - Workflow BAW on Containers BAW Traditional Not available in BAW on Containers BAW on Containers does not support VMM. Users and Groups are managed using UMS Team UI Users are sourced from an external LDAP federated via UMS Team Server 28

29 BAW on Containers Runtime Admin CPE (ACEE) BAW ECM Server definition for the former BPM Document Store now directly points to this CPE. Object Store dedicated to process instance document attachments is now configured in external CPE 29

30 BAW on Containers Runtime Server Management On prem customers to perform WAS admin tasks and BAW configuration tasks used wsadmin commands WAS Admin Console In Docker version there is no WAS Admin Console or WAS wsadmin commands In Workflow Server on Containers most of the configuration tasks are available as REST API More recently added ops commands have been introduced as REST Ops APIs only with no wsadmin equivalents App Server Management API DBA Navigator Workflow Workflow Server Liberty Content Platform Engine (CPE) BAW DBs Test / UAT/ Production Workflow Server User Management Workflow Messaging (JMS) CMIS LDAP OpenShift & CNCF Process Federation Elasticsearch Resource Registry (etcd) 30

31 REST Operations API were expanded REST API version of most of the wsadmin commands is already available in Workflow Server on twas New REST API were added to ensure all admin functions provided by wsadmin commands are available See er/en/ss8jb4/com.ibm.wbpm.ref.doc/bawapidoc/bpm-swagger-ops-standardpublished.json 31

32 Example: Exposed Process Value, Process, Branch New New New 32

33 Example: Container New New New New 33

34 BAW on Containers Runtime App Configuration On prem customers used Test / UAT/ Production Workflow Server WAS Admin console i.e. Next Task mashup config 100custom.xml i.e. Transaction timeouts Custom Resurce Workflow Workflow Server Liberty User Management Workflow Messaging (JMS) Process Federation In Docker version there is no WAS Admin Console In Docker version 100custom.xml files are in PVs To accomplish both tasks in Docker version we recommend using Custom Resource DBA Navigator Content Platform Engine (CPE) BAW DBs CMIS LDAP OpenShift & CNCF Elasticsearch Resource Registry (etcd) 34

35 Using Custom Resources 1. Create a Secret 3. Add secret to Custom Resource 2. Edit Secret to add required configurations 35

36 Create and Edit Secret Use the same XML settings as documented in 100custom.xml. This setting enables CSHS coach debug in a web browser. 36

37 Add Secret to CR 1 1. Secret content gets saved to 199Custom.xml 2. Pods are incrementally restarted to get reconfigures with the new config data. Restart is staged so that at least one Pod is always up to ensure HA

38 BAW Configuration - Best Practice CHALLENGE In BAW on WAS, to configure BAW runtime, we often updated 100custom.xml file directly In BAW on Containers this can be done using CRs and Secrets What is the commanded method and why? SUGGESTED BEST PRACTICE Always use CRs and Secrets! Here are the key advantages: CR and Secrets once configured can be saved and reused to configure other clusters Secrets are a form or record that shows what configurations were performed When restarting containers the state of PV is unpredictable in fact some setting may be lost During a lifecycle of pods, when the are destroyed and recreated the Operator will start applying the configuration from CR and Secret 38

39 BAW on Containers Runtime Kubernetes Introduction Docker Images and Pods Server Management and Administration Install Process Federation Server Process Portal 39

40 Install Options 40 Select install method Enterprise Fully configurable and upgradable Evaluation (a.k.a. Demo Pattern) Simple install steps Because there are no configuration option installer takes care of dependencies and prerequisites The only preparation step is to secure storage class Restrictions Cannot be updated Cannot be upgraded to Enterprise deployment Select what to install Business Automation Workflow and Workstream Services Business Automation Workflow Workstream Services

41 BAW on Containers System Prerequisites System Kubernetes 1.16 with Kubernetes command line interface OpenShift with OpenShift Container Platform CLI Full spec Dynamic storage created and ready Configured NFS server and client for the OCP nodes A non-administrator user that can be used to run the deployment script H/W requirements Component CPU Memory Storage IBM BAW Server on Containers 1 master node with 4 CPUs 1 infrastructure node with 4 CPUs 3 worker nodes with 6 CPUs 16G on the master and infrastructure nodes 24G on the worker nodes 231 GB IBM BAW Server on Containers with IBM Business Automation Insights 1 master node with 4 CPUs 1 infrastructure node with 4 CPUs 3 worker nodes with 10 CPUs 16 Gi on the master and infrastructure nodes 24 Gi on the worker nodes 761 GB 41

42 Evaluation Installation Steps Prepare storage To run stateful applications, developers need to store the persistent data in a managed storage that is backed by some physical storage. Run cp4a-clusteradmin-setup.sh Sets up security for selected cluster user and returns host name and storage class to be used in the next script Download install images From PPA or IBM Entitled Registry to local Docker registry Run cp4a-deployment.sh User is prompted for: storage class, host name of the infrastructure node, docker registry url Uses customized ibm_baw_cr.yaml (resource file) to deploy and configure Workflow Server on Container pods Get BAW console urls and credentials oc get route oc get secret 42

43 BAW on Containers How many Pods? Minimum configuration 1. 2 Maximum configuration 8 pods 49 pods See next chart! Workflow Server Pods Db2 and LDAP are external No PFS (not supported) Simply remove this sections PFS BAI Db2 LDAP Additional unrelated pods Workplace Workstreams (runs on BAW pods) App Engine (no App Designer) 43

44 Minimum Configuration Workflow Server Docker Containers Worker 0 Worker 1 Worker BAW DBs CMIS Workflow Workflow Server Liberty DBA Navigator Navigator Liberty Resource Registry (etcd) User Management Workflow Messaging (JMS) Content Platform Engine CPE Liberty Above docker containers have 1:1 correspondence with Pods 7 LDAP

45 OS Resource Monitoring Workflow Server Pod Workflow Workflow Server Liberty 45

(Video) IBM Business Process Manager (BPM) 8.5.7: Building a Business Process

46 BAW on Containers Runtime Kubernetes Introduction Docker Images and Pods Server Management and Administration Install Process Federation Server Process Portal 46

47 Process Federation Server on Containers Process Portal Workstream Services Workflow Server Process Federation Server Workflow Server X Workflow Server X Workflow Server It is possible to federate an on-prem BAW with Process Federation Server running in ICP4A 47 Process Federation Server enables task workers to access all their work from a single Workflow Portal Tasks that can be federated BPMN tasks and instances of BAW on premises version and later, and BAW Container systems Workstream tasks of IAWS (under the cover, those are BPMN tasks) It will be non-optional component in BAW on Containers Easier to configure and manage than on prem

48 Process Federation Server Architecture Configuration Runtime Operations BAW Server register itself to DBA registry PFS discovers BAW Server from DBA registry One of BAW system is chosen to host Federated Portal PFS returns tasks and process instances to Federate Portal BAW Server Event Listener dates BPMDB Change Log Indexer queries Change Log Indexer updates Elastic Search indices BAW Server 1 PFS PFS BAW Server 1 - N Federated Portal Get Tasks Federated REST API Indexer BPMDB Workflow Engine Change log Event listener Registers BAW Server N DBA Registry (etcd) Discovers 48 Elastic Search Elastic Search

49 BAW on Containers Runtime Kubernetes Introduction Docker Images and Pods Server Management and Administration Install Process Federation Server Process Portal 49

50 Process Portal in Workflow Server Container Workflow Server on Containers Workflow Server - Traditional Only Work Dashboard will be available in Work out of the box Workflow on Container Next Task configurable These Dashboards are not available in Workflow on Container version Task Prioritization feature is not available in Workflow on Container version 50 Other features not available in Process Portal on Containers: Audit History Process Diagram

51 What is Next Task Dashboard? NEXT TASAK Dashboard can be configured to replace the default WORK Dashboard. Task Worker can only see one task at a time In configuration it is possible to specify what team can see WORK versus NEXT TASK dashboard in the IBM Process Portal. 51

52 Agenda Introduction Licensing and Support BAW on Containers Runtime BAW on Containers Development 52

53 BAW on Containers Development Playback and Deployment Target Environment Examples of Unsupported Features Migrating Solutions to BAW on Containers Process Migrating Solutions to BAW on Containers - Case 53

54 BAW on Containers Playback Authoring Environment Web Designer Workflow Center Workflow Center Case Builder Playback and Debug for Traditional and Container projects. Not available in release. Targeted for a future release. Playback and Debug for Traditional and Traditional or Container projects. Workflow Workflow Server Liberty DBA Navigator Workflow Server on Containers User Management Workflow Messaging (JMS) Content Platform Engine (CPE) Resource Registry (etcd) Elasticsearch Workflow Server WebSphere CMIS Process Federation BAW DBs VM or On Prem BAW DBs LDAP OpenShift & CNCF Traditional Only projects 54 Traditional or Container projects

55 Playback for Traditional and Container Processes Traditional and Container projects will not run on playback Workflow Center Server if conversion errors exist 55

56 BAW on Containers Deployment Authoring Environment Workflow Server on Containers Web Designer Workflow Center Workflow Center Workflow Server Case Builder Online Deploy for Traditional and Containers Workflow Server Workflow Workflow Server Liberty DBA Navigator User Management Workflow Messaging (JMS) Content Platform Engine (CPE) Resource Registry (etcd) Elasticsearch CMIS Process Federation WebSphere BAW DBs BAW DBs LDAP 56 VM or On Prem Traditional Only projects Traditional or Container projects Offline Deploy for Traditional and Container and projects. Provides updated REST API. OpenShift & CNCF

57 Deploying on Workflow Server on Containers Off Line Deploy Workflow Server on Containers Hands-on lab 57

58 Create an Online Workflow Server on Containers Online Deploy When creating Workflow Server select Container By default the Connection status shows Offline. See next chart for configuration details. 58

59 Configuration to enable online deploy 1) A tls secret needs to be created within the operator code using the rootca cert of the WC so that it can be recognized as a trusted server. Steps are: * kubectl create secret generic baw-tls-secret --from-file=tls.crt=/root/wc.cert * add this secret in the trust list of baw_configuration.tls.tls_trust_list of workflow deployed CR file like below: baw_configuration: - name: instance1 tls: tls_trust_list: [baw-tls-secret] You can get the WC.cert by pasting the first cert you see when you execute - $keytool -printcert -sslserver example.fyre.ibm.com:9443 rfc 2) A WC credentials secret needs to created in "adminsecrets4operator-ctnrs.yaml". Something along the lines of: apiversion: v1 kind: Secret metadata: name: ibm-baw-wc-secret type: Opaque stringdata: username: deadmin password: deadmin with the stringdata having the "username" and "password" of the WC. Then apply this secret $oc apply -f./baw_ctnrs/adminsecrets4operator-ctnrs.yaml 3) You should see new config parameters in your BAW Custom Resource for the WC. An example of the values are: workflow_center: url: " secret_name: "ibm-baw-wc-secret" heartbeat_interval: 30 You might need to redeploy or get the updated CR recognized at this point. After the above three steps completed the BAW on Container should show up in the WC. You can check the servers page of the WC to test see if it shows up. 4) Use Workflow Center WebSphere Admin Console to add Workflow Server on Conatiner certificate. Go to Security > SSL certificate and key management > Key stores and certificates > CellDefaultTrustStore > Signer certificates > Retrieve from port. Enter the BAW PS router hostname and port and save. 59

60 Enable Online Workflow on Container Server Online Deploy Workflow Server on Containers Workflow Pod Workflow Server Liberty See the instructions below in Speaker Notes to enable communications between Workflow Center on Workflow Server on Containers Heartbeat Once communication is established (Workflow Center Server detects a heartbeat) the Connection status will change to Online Workflow Center Workflow Center Web Designer Case Builder Workflow Server 60 WebSphere

61 Deploy to Online Workflow on Container Server Online Deploy Once communication is established (Workflow Center Server detects a heart beet) the Connection status will change to Online Workflow Server on Containers Workflow Workflow Server Liberty 61

62 BAW on Containers Development Playback and Deployment Target Environment Examples of Unsupported Features Migrating Solutions to BAW on Containers Process Migrating Solutions to BAW on Containers - Case 62

63 Target Environment New Authoring Option New capability to specify the target runtime environment for Process Apps and Case Solutions. Triggers project features validation to ensure that they are supported in the selected environment. Traditional Projects are targeted to the Workflow Server in the traditional WebSphere environment. The project features are automatically validated to ensure that they are supported in this environment. Traditional or Container Projects are targeted to the Workflow Server in either the traditional WebSphere environment or the container environment. The project features are automatically validated to ensure that they are supported in both environments. 63

64 Why do we need Target Environment? 1. To ensure only those artifacts are shown/offered that are supported in the target environment i.e. emitting events to IBM Business Monitor is not supported on Containers 2. Enable conversion of artefacts that are supported only in Traditional environment to artifacts supported in Traditional and Container environment i.e. AIS Services must be removed and converted to use supported bindings such as Web Services 64

65 Target Environment in Process Designer Target Environment Conversion Available in Process App Settings > Overview Tab 65

66 Target Environment in Process DesignerTarget Environment Conversion Unsupported / removed features shown in Target Environment Conversion Tab Action will need to be taken to perform conversions and deletions 1. BPD, UI, Service conversion This happens if the a ProcessApp or Toolkit was originally authored in desktop PD 2. Automatic conversion 3. Artefact deletions 4. Manual conversions 5. Toolkits that require conversions Conversion issues are also listed in Validation Errors and Warnings View System Data Toolkit conversion to Traditional and Container (_TC version)

67 Target Environment in Workflow Center New Target Option in Workflow Center New feature to set Target Environment when creating a new Process App or a Case Solution 67

68 Target Environment in Workflow Center Target Environment Tagging Tiles are marked with icons indicate the target environment Snapshots are labelled to clarify to what server type a snapshot should be deployed to Traditional Traditional or Container 68

(Video) Webinar: CP4A Part 1 - Overview

69 Target Environment in Workflow Center Validation Errors New type of validation errors that prevent snapshot to be installed on selected Target Server 69 Oonly Install actions is removed

70 BAW on Containers Development Playback and Deployment Target Environment Examples of Unsupported Features Migrating Solutions to BAW on Containers - Process Migrating Solutions to BAW on Containers - Case 70

71 System Data Toolkit Conversion System Data ( ) Includes unsupported Services: SQL, JMS, MQ integrations and XML validation and transformation System Data ( _TC) Unsupported Services are removed 71

72 System Data Toolkit Conversion System Data ( ) Includes Integration.jar used to create Java Service from Server File, which includes JMS/SQL/XML integration Java classes System Data ( _TC) JMS/SQL/XML integration Java classes not available 72

73 Outbound Web Services - Policy Sets and Policy Binding Traditional Policy Sets are supported by WAS ND runtime Traditional & Container Policy Sets cannot be specified. They are flagged as critical errors (cannot deploy) Must be converted (Convert button removes Policy Sets) 73

74 Outbound Web Services Other Differences Removed compatibility flags Removed WSDL cache flags Flag use-breadth-first-search-wsserver use-protect-wsdl-auth-inwebservice use-advanced-response-typemapping serializer-exclude-incompleteelement preserve-pre85-default-nillablevalue use-jaxws dateandtime-include-milliseconds Behavior in BAW on Containers False False True True False True True The WSDL is not required at run time in BAW on Containers and therefore the WSDL cache with its configurations is obsolete in BAW on Containers. Message Level Encryption Not available More details 74

75 Inbound Web Services are not avilable Traditional Inbound Web Service. Could be used with UCA and Service Flow to expose a Process Traditional & Container Cannot be created It is a critical error category and must be deleted before Process App can be deployed 75

76 Advanced Integration Services Integration Designer will not be supported including BPEL, MFC, SCA, etc. BAW on Containers does not include BPM Adv runtime If you are using AIS you will see errors that look similar to this Changing Target environment to TC automatically disassociates Process App from Advanced Content in Integration Designer There are three patterns conversion patterns - see Conversion to BAW on Containers - Best Practice 1. Calling Advanced Integration Services from Processes 2. Calling a Process from BPM Adv 3. Inbound SCA 76

77 BAW on Containers Development Playback and Deployment Target Environment Examples of Unsupported Features Migrating Solutions to BAW on Containers Process Migrating Solutions to BAW on Containers - Case 77

78 Environment Migration Traditional to Containers BAW X BAW 18.0.X BAW BPM General migration approach of migration of Use side by side artifact migration Similar in effort to BPM 8.0 to BPM 8.5 migration. No runtime migration (running instances or tasks) Can use PFS (Federation) to make it seamless to the business users allowing the drain method of completing tasks on the traditional instance of BAW and starting new instance on BAW on container. Can use dual license entitlement to run both for the period of migration (up to 18 months) 78

79 Conversion to BAW on Containers - Best Practice CHALLENGE I have several large Apps Based on BPDs (in eclipse PD) Based on Processes (in Web PD) What is the best way convert a Process App to run on Workflow Server on Containers? What do I need to do first? What is the conversion process? Is the conversion automated? How can I plan my work? Can I do the work in parallel deploying multiple developers? SUGGESTED BEST PRACTICE This Best Practice describes the steps to convert Process Applications It all starts with selection of the Target Environment in Web PD 79

80 Conversion to BAW on Containers - Best Practice Determine dependent Toolkits for your Process App Perform eclipse to Web PD conversions of your Process App Set Target Environment to TC in your Process App Select the next Toolkit and convert the artifacts Convert artifacts in your Process App 80 Steps 1. Use Workflow Center to find out what are the toolkit dependencies to help you plan your work 2. If coming from eclipse PD, convert artefacts supported only in eclipse PD artefact to Web PD artefacts 3. Set the Target Environment to Traditional and Container 4. Pick the next leaf toolkit and convert all artefact in the toolkit Update System Data Toolkit to Examine: target Server Conversion Tab and Validation and Warnings Perform the conversions; Manual Conversion, Automated Conversion, Deletions Examine and fix Validation and Warnings after conversions 5. Go to 4 6. After all toolkits are converted convert the Process App Notes Take a snapshot at every conversion milestone Perform individual unit tests as you converting Assign work to multiple developers Convert Toolkits first Process App last step done when all toolkits are converted

81 Conversion to BAW on Containers - Steps Determine dependent Toolkits for your Process App Perform eclipse to Web PD conversions of your Process App Set Target Environment to TC in your Process App Select the next Toolkit and convert the artifacts Convert artifacts in your Process App 81

82 Find out what are the toolkit dependencies This toolkit in Process Designer has a lot toolkit dependencies (as shown in Workflow Center view on the right) Using the recommended approach, we need to convert all the dependent toolkits first need to start with the leaf toolkit labelled

83 Conversion to BAW on Containers - Steps Determine dependent Toolkits for your Process App Perform eclipse to Web PD conversions of your Process App Set Target Environment to TC in your Process App Select the next Toolkit and convert the artifacts Convert artifacts in your Process App If required 83

84 Eclipse PD to Web PD Artefact Conversion If required If needed (coming from eclipse PD), convert eclipse PD only supported artefact to Web PD artefacts 84

85 Conversion to BAW on Containers - Steps Determine dependent Toolkits for your Process App Perform eclipse to Web PD conversions of your Process App Set Target Environment to TC in your Process App Select the next Toolkit and convert the artifacts Convert artifacts in your Process App 85

86 Set the Target Environment to Traditional and Container 86

87 Conversion to BAW on Containers - Steps Determine dependent Toolkits for your Process App Perform eclipse to Web PD conversions of your Process App Set Target Environment to TC in your Process App Select the next Toolkit and convert the artifacts Convert artifacts in your Process App More information about conversion of deprecated artefacts 87

88 Use References View to Select Next Toolkit to Migrate Using the toolkit Snapshots References view, convert dependent toolkits recursively starting from leaves and progressing up the toolkit dependency tree following the order: 1, 2, 3, 4, 5 88

89 Examine what needs to be converted Only when this list is empty you should start converting The artefacts shown in this view! Perform conversions of artefacts shown here in this order: 1. Delete 2. Convert 3. Manual Fixes Required You should not see any artifact here at this point. Eclipse PD to Web PD artefact conversion should be done first

90 Manage Directly Referenced Toolkits Use Toolkit Dependencies view to manage dependent toolkits that are not compatible with Traditional or Container target. Do not start any conversion tasks if you see any dependent toolkits in this converting The artefacts shown in this view! 90

91 Convert Manual Fixes Required Points to an exiting are tact that includes unsupported feature. Click the link to open the artefact and convert to a supported implementation. As prescribed in the hover-over help, use External Service > External Implementation 91

(Video) Demo Overview of IBM Robotic Process Automation (RPA)

92 Convert Deletions Required Most Deletion Required artefacts are visible only in desktop PD. 92

93 Convert Automated Conversion Automated action to trigger conversion of 8.5 Case Type to Process. 93

94 Examine and fix Validation and Warnings New Critical label means you will not be able to install on target platform Click on the error to open the artifact in Editor. 94

95 Converting Advanced Integration Services 1. Calling Advanced Integration Services from Processes Advanced Content is automatically disassociated from Process App in Integration Designer Expose the SCA Components formerly marked As Advanced Integration Services as Web Services Refactor Service Flows that call AISes to call Web Services More information on using AISes 95

96 Converting Advanced Integration Services 2. Calling BPMN Processes from BPEL Processes Advanced Content is automatically disassociated from Process App in Integration Designer Expose Process as a Web Service in Process Designer Use the Web Service Import in Integration Designer Be aware that there are two invocation patterns One Way (i.e. to start a BPMN Process) Use Web Service call Request Response (i.e. to start BPM process for human task implementation) Requires a callback from the Process back to the invoking BPEL process 96

97 Converting Advanced Integration Services 3. Inbound SCA What is it? Allows to use SCA Service as triggering mechanism to start Message Events This triggering mechanism makes it possible to use instance-based correlation that always delivers the message to exactly one event of one instance. Steps to convert Disassociate Process App from Advanced Content in Integration Designer Associate the UCA triggers with new inbound Web Service Change the SCA Components to invoke the exposed inbound Web Services 97

98 Conversion to BAW on Containers - Steps Determine dependent Toolkits for your Process App Perform eclipse to Web PD conversions of your Process App Set Target Environment to TC in your Process App Select the next Toolkit and convert the artifacts Convert artifacts in your Process App 98

99 Convert App Level Artifacts this is the final step! Only when this list is empty you should start converting The artefacts shown in this view! You should not see any artifact here at this point. Eclipse PD to Web PD artefact conversion should be done first 99

100 BAW on Containers Development Playback and Deployment Target Environment Examples of Unsupported Features Migrating Solutions to BAW on Containers Process Migrating Solutions to BAW on Containers - Case 100

101 Migrating Case Solution to Containers Process App First migrate the Process App associated with a Case Solution Case Use Process Designer to change Target Environment (in Workflow Center) to Traditional and Containers Use Case Designer to remove Case Forms ACCE Console Ensure that all custom Content Platform Engine (CPE) event handlers will work in Content Platform Engine in a container environment Navigator Use Process Designer to change Target Environment in Process App associate with Case Solution Ensure that all custom Content Navigator plug-ins work in IBM Content Navigator in a container environment 101

102 Supported Project Types Case Solutions (Process Apps, Templates, Toolkits) Process Apps (Toolkits) Legacy Cases (created in Case tooling prior to BAW 18.x) must be first converted to Case Solutions BAW Solution created in Case Builder (in BAW 18.x or higher) must be Promoted using the Promote to workflow project option 1 Case project built in a pre-baw Case Builder must be fist upgraded using the Promote button which will upgrade the project to a BAW 18.x project

103 103

104 Playback Options in Web Process Designer Workflow Server on Workflow Center (see note 1) Workflow Server Traditional Playback runs on Workflow Server on Workflow Center Traditional or Container Optionally, Playback runs on external Workflow Server on Container which must be dedicated to this function and installed/configured separately (see note 1) When you click Debug or Run button Current Unnamed snapshot (since you did a save) will be packaged and installed on the external PS on Container Optionally Playback runs on external Workflow Server on Workflow Center Ability to debug a process instance on a connected Test/AQ/Prod Workflow Server on 104 Feature formerly available only on eclipse Process Designer Workflow Server (Playback) Ability to select either Workflow Center Playback server or a connected Workflow Server Playback on Container (see note 1) Note 1: Not available in release. Targeted for a future release.

105 Debug/Run Instance of Remote Process Server This feature is one of few available only in desktop PD There are plans to make offer this feature in web PD Not available in release Targeted for a future release 4. Select instance to start debug, inspect process variable, etc 1. Select Connected Workflow Server 2. Select Process 3. Select Snapshot 105

106 Pods by Name 106

107 Pods by Worker Nodes 107

108 Pods by Function 108

109 Pods listed using command line db2u-release-db2u-0 db2u-release-db2u-ldap-6cb9cdfdbd-zhwrm db2u-release-db2u-tools-5865c8f997-k7gwr db2u-release-etcd-0 db2u-release-etcd-1 db2u-release-etcd-2 ibm-cp4a-operator-9d869f854-vpksp icp4adeploy-cmis-deploy-b5fcd558b-qj5q5 icp4adeploy-cpe-deploy-84c855596d-hbs6b icp4adeploy-navigator-deploy-757bc n76f icp4adeploy-openldap-deploy-84dfd7b569-jlx26 icp4adeploy-phpldapadmin-c8ff5c465-9wlkp icp4adeploy-pfs-0 icp4adeploy-pfs-dbareg-5b9d655d49-764jw icp4adeploy-elasticsearch-statefulset-0 icp4adeploy-ums-deployment-7f86f4bd95-fv9rw icp4adeploy-ums-deployment-7f86f4bd95-j2b2g icp4adeploy-dba-rr-1aac272c45 icp4adeploy-dba-rr-cd3bade8fa icp4adeploy-dba-rr-f880d66f24 icp4adeploy-instance1-workflow-server-0 icp4adeploy-instance1-workflow-server-jms-0 109

110 What is Next Task Dashboard? Task Workers can only see the (single) next task to work on When enabled, replaces Works dashboard Displays only one task The task selection/ordering criteria can be customized using a dedicated Saved Search (by default its is the same for the Work dashboard) New Task dashboard enablement and configuration in WAS Admin Console Configure what teams can see New Task dashboard Select either Work or Task dashboards (they are mutually exclusive) Configure if claimed but not completed tasks are returned back to the queue Configure Saved Search used for task selection/ordering criteria 110

111 Why do we need Target Environment? Workflow Server Binaries UNSUPPORTED Features not supported on Liberty DEPRECATED Features marked as deprecated Workflow Server Binaries WebSphere Liberty Operating System or VM Workflow Server Container When you select Target Environment in Web Process Designer unsupported / removed features shown Target Environment Conversion Tab Action will need to be taken to BPD, UI, Service conversion 111 This is if the a PorcessApp/Toolkit is converted from desktop to web PD Automatic conversion Artefact deletions Manual conversions Conversion issues are also listed in Validation Errors and Warnings View

112 Validation Errors 112

113 Validation Errors 113

114 Configuring Next Task Capability in Process Portal Example of the use of WAS Admin Console mashup setting not available in BAW on Containers 2 com.ibm.bpm.portal.defaultnexttasksavedsearch Identify the saved search that is used to determine which tasks the Next Task dashboard shows to all the users who are allowed to see this dashboard. If the property is not set, the built-in default saved search is used 3 com.ibm.bpm.portal.returntasktoteamonlogout 1 Determine what happens when users who work with the Next Task dashboard logs out. The property can be set to all or a set of teams. On this case if the user log outs without finishing the task, the task is assigned back to the user team. If the property is not set the user who has just logged out remains the task owner. Use WAS Admin Console to enable and configure Next Task dashboard 114 Add new custom property Specify teams to use the Next Task Dashboard. all means all the teams/users

(Video) Automate your business with IBM Cloud Pak for Automation

Videos

1. AWS Certified Cloud Practitioner Certification Course (CLF-C01) - Pass the Exam!
(freeCodeCamp.org)
2. IBM RPA Client Presentation 2022
(IBM Process Mining & RPA EMEA)
3. Webinar: Automating Your Business Process
(airSlate)
4. WordPress Accessibility Day - Sessions 7-12
(WordPress Accessibility Team)
5. Jfrog | Jfrog Artifactory | Jfrog Artifactory Tutorial | Artifactory Tutorial | Intellipaat
(Intellipaat)
6. IBM BPM Training Day3
(swazir2000)

Top Articles

Latest Posts

Article information

Author: Tuan Roob DDS

Last Updated: 11/06/2022

Views: 5643

Rating: 4.1 / 5 (62 voted)

Reviews: 93% of readers found this page helpful

Author information

Name: Tuan Roob DDS

Birthday: 1999-11-20

Address: Suite 592 642 Pfannerstill Island, South Keila, LA 74970-3076

Phone: +9617721773649

Job: Marketing Producer

Hobby: Skydiving, Flag Football, Knitting, Running, Lego building, Hunting, Juggling

Introduction: My name is Tuan Roob DDS, I am a friendly, good, energetic, faithful, fantastic, gentle, enchanting person who loves writing and wants to share my knowledge and understanding with you.