BTB-2890: Understanding the IBM

BPM Process Federation Server

Eric Herness
Chris Richardson
 Please Note:
• IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole
discretion.

• Information regarding potential future products is intended to outline our general product direction and it should not be relied on in
making a purchasing decision.

• The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any
material, code or functionality. Information about potential future products may not be incorporated into any contract.

• The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

• Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual
throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the
amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed.
Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

1
Agenda
 Introduction & Motivation
 Architecture Details
 Install & Configuration
 HA, DR & Scalability
 Future Vision

2
 Process Federation Server
 Process Federation Server enables task and knowledge workers to access all their work
from a single Process Portal.

 Tasks can be federated across

– Multiple BPM cells
– Multiple BPM releases BPM
– BPMN and BPEL tasks V8.0.1.3

BPM
V8.5.0.1

Responsive BPM Responsive Process Federation

Portal Portal Server BPM
(browser) (browser) (Liberty) V8.5.5

Single BPM environment BPM

V8.5.6
Federated environment

BPM
vNext

3
 Process Federation Server – Why Federate?
 Unified view across various task types
 BPMN, BPEL, and others in the future

 Support process isolation

 Isolate important process applications into their own cells
 Avoid resource contention

 Simplify migration via draindown approach

 Finish existing work on old environment
 Start new work on new environment

 Massively scale BPM infrastructure across cells

 Third scaling dimension (in addition to horizontal and vertical)
 Scale beyond a single cell-scoped database

 Isolate client applications from BPM engine evolution

 Ensure portability across topology and software changes
 Continuous availability during topology and software changes

 Future: Hybrid cloud - federation across BPM on-prem and Cloud

 On ramp to cloud-based deployment options
 Flexibility for customers who have some services on-prem and some on a cloud
4
Process Federation Server – Unified task list
Responsive Process Portal

BPM 8.0.1.3

BPM 8.5.6

5
Quick Sketch: Using PFS to Isolate Users from Complexity

 Let’s flip through a series of pictures to illustrate the idea…..

6
 BPM Vision: Moving Toward Continuous Availability
Stage 0:
Single BPM system executing
both BPEL & BPMN processes

Users see separate task lists

for BPEL & BPMN BPM v8.013

BPE DB
Portal Client
IHS
(Browser) Process
Portal App

BPMN BPEL BPM DB

Process A Process 1

LDAP
 BPM Vision: Moving Toward Continuous Availability
Stage 0b:
Or, maybe you only run BPMN, BPM v8.013
but on 2 cells – to support
different BPM versions or for BPE DB
isolation
IHS
Process
Portal App

BPMN BPMN BPM DB

Process A Process B
Users see separate task lists
for each of the cells

LDAP
Portal Client
(Browser)
BPM v8.5.5

BPE DB

IHS
Process
Portal App

BPMN BPMN BPM DB

Process 1 Process 2
 BPM Vision: Moving Toward Continuous Availability
Stage 1:
Add Process Federation Server BPM 8.013
• Isolate Users from Topology BPE DB
• Present Unified Task List
IHS

BPMN BPEL
PFS API allows unified Process A Process 1
task list containing BPEL BPM DB
& BPMN tasks

PFS 8.5.7

Portal Client
IHS Federated Search Index LDAP
(Browser)

IHS Client uses WLE API to

Independent Process Portal deployment
work on BPMN tasks &
isolates it from future BPM changes:
WPS API for BPEL tasks
• BPM Responsive Federated Portal
Process
Process or Custom App
Portal
PortalApp
App
 BPM Vision: Moving Toward Continuous Availability
Stage 2:
Rewrite client to use BPM BPM 8.013

Common BPM API

Common API to communicate BPE DB
with all BPM & PFS servers.
IHS
Investment applied here to
BPMN BPEL
write apps to the BPM Process A Process 1
Common API, but now they BPM DB
are not sensitive to task type

PFS 8.5.7

Common BPM API

Portal Client
IHS Federated Search Index LDAP
(Browser)

IHS
Import a new library - required
to expose BPM Common API in
Process
Process BPM & PFS servers
Portal
PortalApp
App
 BPM Vision: Moving Toward Continuous Availability
Stage 3:
Can also ‘federate in’ another BPM 8.013

Common BPM API

BPM System with new BPE DB
Processes – without changes to
the front end IHS

Users continue to see a BPMN BPEL

Process A Process 1
single task list containing their BPM DB
work across all processes.

PFS 8.5.7

Common BPM API

Portal Client
IHS Federated Search Index LDAP
(Browser)

IHS BPM 8.5.x

Common BPM API

BPE DB

Process IHS
Process
Portal
PortalApp
App Process Process Process
10 11 12
New processes in another BPM DB
BPM version with full cell &
infrastructure isolation.
 BPM Vision: Moving Toward Continuous Availability
Stage 4:
Now we ‘migrate’ the apps on BPM 8.013

Common BPM API

our 8.013 cell up to a future BPE DB
BPM version without clients
seeing a disruption of service IHS
BPMN BPEL
Users continue to see a Process A Process 1
single task list containing their BPM DB
work across all processes.

PFS 8.5.7 BPM 8.5.future

Common BPM API

Common BPM API
BPE DB
Portal Client
IHS Federated Search Index IHS
(Browser)
BPMN BPEL
Process A Process 1
BPM DB

IHS BPM 8.5.x

Common BPM API

BPE DB

Process New BPM version to replace IHS

Process
Portal
PortalApp
App our old 8.013 system using Process Process Process
artifact-only migration 10 11 12
BPM DB
 BPM Vision: Moving Toward Continuous Availability
Stage 5: Drain down and
Our 8.013 cell can now be decommission BPM
safely removed. 8.013 system.

Users continue to see a

single task list containing their
work across all processes.

PFS 8.5.7 BPM 8.5.future

Common BPM API

Common BPM API
BPE DB
Portal Client
IHS Federated Search Index IHS
(Browser)
BPMN BPEL
Process A Process 1
BPM DB

IHS BPM 8.5.x

Common BPM API

BPE DB

Process IHS
Process
Portal
PortalApp
App Process Process Process
10 11 12
BPM DB
Process Federation Server: Security
BPM 8.013

Common BPM API

3 Each of the arrows in this BPE DB
diagram denotes an SSL
connection IHS

1 Since Portal Client makes cross-origin requests BPMN

Process A
BPEL
Process 1
(calls to servers other than Portal app server),
define which servers are trusted via Cross BPM DB
Origin Resource Sharing (CORS)
4 PFS & BPM servers must
PFS 8.5.7 share the same LTPA keys

Common BPM API

and configure SSO within
the entire domain.
Portal Client
IHS Federated Search Index LDAP
(Browser)

IHS BPM 8.5.x

Common BPM API

BPE DB
2Clients must be configured to
Process IHS
Process trust the Process Federation
Portal
PortalApp
App Server and federated BPM
2 PFS must contain a truststore Process Process Process
systems’ signer certificate. 12
10 11
Use CA-signed certs to get BPM DB
this for free. containing each federated BPM
systems’ signer certificate. Use CA-
signed certs to simplify this.
Additional Details & References

• Where can I get the BPM Common API asset?

– It’s available in the BPM Developer Center (developer.ibm.com/bpm), called bpm-api
– Which links to the same place as this: bit.ly/24l0XEm

• Where can I get the PFS Docker image?

– Look for it to arrive soon on the ibmcom namespace in docker hub: https://hub.docker.com/u/ibmcom/

• Do I have to move my existing BPM systems up to v8.5.7 to start using PFS?

– No. PFS v 8.5.7 can federate in back-level systems
– An APAR may be required for those older BPM versions:
http://www-01.ibm.com/support/docview.wss?uid=swg21699090

15
Agenda
 Introduction & Motivation
 Architecture Details
 Install & Configuration
 HA, DR & Scalability
 Future Vision

16
 Process Federation Server – Architecture
 Federation service is quickly deployed in a lightweight WebSphere Liberty server
 Provides access to resources spanning federated environments (task list, launch list)
 Minimizes configuration and performance impact to existing BPM environments

 PFS includes federated search index powered by Elasticsearch

 Distributed task index for fast end user task queries
 Relieves query pressure from BPM transactional servers and databases
 Easy to scale horizontally by adding Liberty servers
 Traditional ‘structured’ task list queries, as well as full-text search

17
 Process Federation Server
- Federated task list data flow
1. Task data from BPM environments is indexed to Process Federation Server
2. User logs into client web application
3. Task list requests get routed to Process Federation Server, resulting task list spans all BPM environments.
4. Task claim and completion requests (and other interactions with an individual task/instance), get routed to back-end BPM
environment that hosts the task, transparent to end user

Servers need to be configured for

BPM
• Single-sign on (SSO)
V8.0.1.3
• Cross –origin resource sharing (CORS)

BPM
V8.5.0.1
Client
application / Process Federation
Responsive Server Indexer 1) Task data is indexed to Process Federation Server
3) Task list
Portal request
(Liberty)
(browser)
BPM
V8.5.5
Server hosting
client application /
Responsive Portal BPM
V8.5.6

Note:
• 8.5.6: Support for default task list query “IBM.DEFAULTALLTASKSLIST_75” and search filters. Business data can be added to the
‘selectedAttributes’ list, e.g. selectedAttributes=bd.hiringManager.string
• 8.5.7: Full support for custom ‘Saved Search’ and ad hoc queries (define custom fields, sorting, condition filters) 18
 Process Federation Server
- Federated launch list data flow
1. Launch list request gets routed to Process Federation Server
2. Process Federation Server propagates request to BPM environments and returns aggregate response
3. User’s launch request for a specific process or human service gets routed to the back-end BPM environment that hosts the
resource, transparent to end user

Servers need to be configured for

BPM
• Single-sign on (SSO)
V8.0.1.3
• Cross –origin resource sharing (CORS)

BPM
V8.5.0.1
Client
application / Process Federation
2) Propagate request to BPM envs
Responsive Server
1) Launch list
Portal request
(Liberty)
(browser)
BPM
V8.5.5
Server hosting
client application /
Responsive Portal BPM
V8.5.6

Note: When the same process application is deployed on two or more federated systems, two modes are possible:
• Failover – Send new work to preferred BPM system, use others if the preferred BPM system is not available
• Load balanced – Load balance new work across the BPM systems
19
 New for PFS 8.5.7 – Saved Search feature
 Federated Saved Search is defined once in PFS, single query spans all federated systems
 Ad hoc task queries and Saved Searches
 Define desired fields, filter conditions, sort order.
 Structured queries AND full text search supported
 Default task fields AND business data fields supported
 Saved Search works in a consistent way when using a single BPM cell or a federation of cells
 Federated Saved Searches are stored in a new PFS database

Hiring Process
Single BPM environment Federated environment
Process Federation Server BPM1
(Liberty) (any supported
Responsive REST ES engine/version)
BPM Responsive
Portal (traditional WAS) query elasticsearch
Portal
(browser) (browser) BPM1 BPM2
REST DB BPM2
index index (any supported
query
engine/version)

Account Open Process

BPMDB
(Repos & Data)
LSW_SAVED_SEARCHES PFSDB
(Repos)
PFS_SAVED_SEARCHES
20
 PFS Capabilities by Version
BPM 8.5.6 BPM 8.5.7 Future?

Task Instances List Yes Yes

Launch List (Processes to Start) Yes Yes

Saved Search No Yes

BPEL Task Completion No Yes, using external

PFS Core Capabilities
activities
Process Instances List No No Perhaps

Process Performance Dashboards No No Perhaps

Social Features (Following and Mentions) No No Perhaps

Responsive Federated Portal Application Tech Demo Yes

PFS Supporting &
Related Code Common API No Via BPM Developer Perhaps
Center
21
Swagger metadata for the BPM Common API

22
 A couple of Common API Examples
 Query all process apps: GET /bpm/process-apps
 Query all toolkits: GET /bpm/toolkits
 Get details of the Hiring Sample process app: GET /bpm/process-apps/Hiring+Sample
 Deploying a process app introduces new values of path params
 Note no UUIDs – nice human-readable URIs
 Still supports use of UUIDs as well, for backward compatibility
 Query all process types: GET /bpm/process-models
 Equivalent to the “exposed” processes API today
 Query details for HR Open New Position process: GET /bpm/process-models/HR+Open+New+Position
 Query all process instances: GET /bpm/processes
 Start an instance of HR Open New Position process: POST /bpm/processes?model=HR+Open+New+Position
 Query all task instances: GET /bpm/user-tasks
 Has an optional “search” query param (just like /bpm/processes)
 Defaults to “IBM.DEFAULTALLTASKSLIST_75” if not specified

23
Agenda
 Introduction & Motivation
 Architecture Details
 Install & Configuration
 HA, DR & Scalability
 Future Vision

24
 Installing Process Federation Server
 Download Process Federation Server package from the IBM BPM
 Run installPFS.bat to silently launch IBM Install Manager

 IM will install the following Liberty binaries

 Lear more about Liberty!

 IBM WebSphere Liberty Repository: https://developer.ibm.com/wasdev/downloads/
 Installing Process Federation Server
 OR, get started even quicker by Downloading the PFS 8.5.7 Docker Image:
https://hub.docker.com/u/ibmcom/
 Configure BPM & Process Federation Server (PFS)
1 Configure BPM Server 2 Configure Process Federation Server server.xml
 Apply IFIX on 8.0.1.3, 8.5.0.1, 8.5.5 template for your environment
 Database  Configure server.xml stanzas to point to your federated systems
 Create PFS tables in BPMDB  dataSource, federatedSystem, bpdIndexer, bpdRetriever
 Single Sign On (SSO)
 Export LTPA key for PFS  Configure federated security
 Event point enablement  Configure common user registry - One LDAP, multiple
 100 Custom.xml – LDAPs, or Custom User Registry supported in Liberty
 <federated-index-enabled merge="replace"> (instead of using VMM)
 true
 </federated-index-enabled>
 Configure LTPA-based SSO (WebSphere or WebSEAL)
 Configure SSL certificates

 Configure IBM HTTP Server (or another reverse proxy server)

for availability and load balancing

Install and configure one ‘master’ server, then create clones as needed.

Note: Liberty configuration in server.xml is simple enough to do with a basic text editor. The template server.xml has all the elements required. Update the values for your environment,
and then clone a configuration by simply copying the server.xml file.
More details:
https://www-01.ibm.com/support/knowledgecenter/SSD28V_8.5.5/com.ibm.websphere.wlp.nd.doc/ae/cwlp_config.html?lang=en

27
Quick Start and Production topologies
Quick Start Production

Roadmap for each with step-by-step instructions in documentation:

http://www-01.ibm.com/support/knowledgecenter/SSFPJS_8.5.6/com.ibm.wbpm.main.doc/topics/cfg_fps_roadmap.html

28
Agenda
 Introduction & Motivation
 Architecture Details
 Install & Configuration
 HA, DR & Scalability
 Future Vision

29
 Process Federation Server - HA
PFS is made Highly Available through normal WebSphere Liberty mechanism
 Configure N Liberty servers and load balance HTTP requests with a load balancer such as IBM HTTP Server
 No concept of a WebSphere-defined ‘cluster’. The cluster is implicit based on number of servers configured.

PFS Elasticsearch service manages distributed index automatically via ‘shards’ and ‘replicas’
 Example for illustration purposes: 12 shards and 1 replica
 BPM 8.5.7 default is 3 shards & 1 replica
 shards get dynamically allocated across servers

Example with three PFS servers (‘nodes’ in Elasticsearch terminology)

Ensure integrity of distributed Elasticsearch index by defining a quorum of servers that are required for the service to be available:
discovery.zen.minimum_master_nodes="2“
30
 Process Federation Server - HA
The distributed Elasticsearch index requires a quorum to ensure data integrity
 So, we must consider the number of nodes that the system can lose and continue to function properly
Recommendations:
 Start with 3 servers and one index replica
 Ensures any one server can be lost without impacting the distributed index availability
 Add additional servers and configure additional index replicas to tolerate loss of more servers

Servers 3 4 5 6 7 8 9 10 11 12

discovery.zen.minimum_master_nodes 2 3 3 4 4 5 5 6 6 7

(number of servers required for a ‘quorum’

to ensure distributed index availability)

index.number_of_replicas 1 1 1 to 2 1 to 2 1 to 3 1 to 3 1 to 4 1 to 4 1 to 5 1 to 5

(number of servers that can be lost

without impacting distributed index
availability

31
 Disaster Recovery Notes
 Our DR testing now includes cross-site failover scenarios with federated environments
 Internal testing has gone well. Very few surprises.

 Replication and recovery for the member cells proceeds just as usual
 All of the traditional concepts like Stray Nodes and Cloned Cells still apply to the member cells

 Replication for the Federation Server components must be added:

 Copy the configuration information across the site boundary
 Copy the data associated with the PFS datasource across the site boundary
 8.5.6 Only: reconfigure the datasource definition to point to the replica database
 In our testing, we do not replicate the elasticsearch index, but rebuild as part of recovery
 Rebuild time depends on index size and the hardware involved
 We have rebuilt a 15000 entry index in 80s

32
Disaster Recovery for the Entire Federation
DataCenter A DataCenter B

Federation Server Replication:

Copy Config Data (or simply reinstall)

Cross-Site BPM cell replication as usual

via Stray Nodes or Cloned Cell
Agenda
 Introduction & Motivation
 Architecture Details
 Install & Configuration
 HA, DR & Scalability
 Future Vision

34
 Future Vision: Increased flexibility & isolation
Stage 0:
This is our base topology BPM 8.013

Common BPM API

BPE DB

IHS

Process Process Process

A B C
BPM DB

Process Federation Server

Common BPM API

Portal Client
IHS Federated Search Index LDAP
(Browser)

IHS BPM 8.5.x

Common BPM API

BPE DB

Process IHS
Process
Portal
PortalApp
App Process Process Process
10 11 12
BPM DB
 Future Vision: API Proxy Service
Step 1:
API Proxy service allowing BPM 8.5.x

Common BPM API

Browser to communicate with a BPE DB
single endpoint
IHS

Process Process Process

A B C
BPM DB

Process Federation Server

Common BPM API

Portal Client Federated Search Index
IHS LDAP
(Browser)
API Proxy Service

IHS BPM 8.5.y

Common BPM API

BPE DB

Process IHS
Process
Portal
PortalApp
App Process Process Process
10 11 12
BPM DB
 Future Vision: Collocate the Process Portal App
Step 2:
Deploy Portal App to our UI BPM 8.5.x

Common BPM API

Tier BPE DB

IHS

Process Process Process

A B C
BPM DB

Process Federation Server

Common BPM API

Federated Search Index
Portal Client
IHS LDAP
(Browser) API Proxy Service

Process Portal App

BPM 8.5.y

Common BPM API

BPE DB

IHS

Process Process Process

10 11 12
BPM DB
 Future Vision: UI Tier
Step 3:
Separate process app UI from BPM 8.5.x

Common BPM API

Business Logic BPE DB

IHS

Process Process Process

A Flow B Flow C Flow
BPM DB
Process Federation Server
Federated Search Index

Common BPM API

Portal Client API Proxy Service
IHS LDAP
(Browser)
Process Portal App

Process AProcess B
Process C
UI UI UI

BPM 8.5.y

Common BPM API

BPE DB

IHS

Process Process Process

10 11 12
BPM DB
 Future Vision: Isolate PFS
Topology Alternative A:
Deploy UI Tier & PFS server BPM 8.5.x

Common BPM API

separately. BPE DB

IHS

Process Process Process

Process Federation Server A Flow B Flow C Flow
BPM DB

Common BPM API

IHS Federated Search Index

LDAP

BPM 8.5.y

Common BPM API

UI Tier Server BPE DB
Common BPM API

API Proxy Service

Portal Client IHS
IHS Process Portal App
(Browser)
Process Process Process
Process AProcess B
Process C 10 11 12
UI UI UI
BPM DB
 Future Vision: Additional deployment ideas
Step 3:
Deploy PFS using BPM PFS BPM 8.5.x

Common BPM API

Docker Image BPE DB

IHS

Process Process Process

A Flow B Flow C Flow
BPM DB
Process Federation Server
Federated Search Index

Common BPM API

Portal Client API Proxy Service
IHS LDAP
(Browser)
Process Portal App

Process AProcess B
Process C
UI UI UI

BPM 8.5.y

Common BPM API

BPE DB

IHS

Process Process Process

10 11 12
BPM DB
 BPM Vision: Hybrid Cloud BPM Federation
IBM BPM on Premise
https://hub.jazz.net/project/jalcorn/bpm- BPM 8.013

Common BPM API

BPE DB
Users see a single task list api/overview New - Available
2/19/2016 - IHS
containing their work across
Cloud based Service
all processes. https://bit.ly/24l0X BPMN BPEL
Em Process A Process 1
BPM DB

PFS 8.5.Future BPM 8.5.future

Common BPM API

Portal Client PFS 8.5.7
Federated Search Index BPE DB

Common BPM API

Common BPM API
(Browser)
API Proxy Service IHS
IHS Federated Search Index
BPMN BPEL
Process Portal App Process A Process 1
Custom client BPM DB
Process AProcess B
Process C
programs in UI UI UI

node.js, java, .. BPM 8.5.x

Common BPM API

BPE DB

Configure what you need IHS

for hybrid cloud Process Process Process
10 11 12
scenarios in this service BPM DB
IBM BPM on Cloud
BWL App Builder …
 Notices and Disclaimers
Copyright © 2016 by International Business Machines Corporation (IBM). No part of this document may be reproduced or transmitted in any form without written permission
from IBM.

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM.

Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of
initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. THIS DOCUMENT IS
DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL IBM BE LIABLE FOR ANY DAMAGE ARISING FROM THE
USE OF THIS INFORMATION, INCLUDING BUT NOT LIMITED TO, LOSS OF DATA, BUSINESS INTERRUPTION, LOSS OF PROFIT OR LOSS OF OPPORTUNITY.
IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided.

Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice.

Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers
have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary.

References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in
which IBM operates or does business.

Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials
and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or
their specific situation.

It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and
interpretation of any relevant laws and regulatory requirements that may affect the customer’s business and any actions the customer may need to take to comply with such
laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law

42
 Notices and Disclaimers Con’t.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not
tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. IBM does not warrant the quality of any third-party products, or the
ability of any such third-party products to interoperate with IBM’s products. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

The provision of the information contained h erein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual
property right.

IBM, the IBM logo, ibm.com, Aspera®, Bluemix, Blueworks Live, CICS, Clearcase, Cognos®, DOORS®, Emptoris®, Enterprise Document Management System™, FASP®,
FileNet®, Global Business Services ®, Global Technology Services ®, IBM ExperienceOne™, IBM SmartCloud®, IBM Social Business®, Information on Demand, ILOG,
Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®, PureData®,
PureExperience®, PureFlex®, pureQuery®, pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, Smarter Commerce®, SoDA, SPSS, Sterling Commerce®,
StoredIQ, Tealeaf®, Tivoli®, Trusteer®, Unica®, urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and System z® Z/OS, are trademarks of International Business
Machines Corporation, registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM
trademarks is available on the Web at "Copyright and trademark information" at: www.ibm.com/legal/copytrade.shtml.

43
 Thank You
Your Feedback is Important!

Access the InterConnect 2016 Conference Attendee

Portal to complete your session surveys from your
smartphone,
laptop or conference kiosk.