@Docs

Electronic document management

system based on FileNet P8 platform

ECM solution in BPS-Sberbank

(Belarus)

• Yuri Veremeichik, Minsk, Belarus

• V1.0

• 22.03.2016, IBA Confidential

Introduction

• Business needs: custom solution based on ECM IBM FileNet

platform and its place in enterprise application landscape vs

"another one application" - ECM IBM FileNet

• Solution baseline, development of custom solution based on

ECM IBM FileNet P8 and IBM Integration bus (IIB)

• Integration aspects. SOA approach for integration of ECM with

banking applications Oracle CRM Siebel and BPM PEGA

• Steps for development of custom solution based on FileNet

platform and state-of-the-art open-source frameworks

• Operational stuff. Basic software products

• Delivery to the customer

• Showcase: Demo screens for usage of ECM client from CRM

and from PEGA PRPC

Component model

Definitions, Acronyms and

Abbreviations• IIB - IBM Integration Bus (formerly known as WebSphere

Message Broker) is IBM's integration broker from the

WebSphere product family

• ECM - Enterprise Content Management system,

• for instance IBM FileNet platform

• BPM PEGA - Business process management (BPM) is a

methodology to manage processes and workflows in an

organization. BPM PEGA - the software of Pegasystems

• CRM, Oracle Siebel CRM - Customer Relationship

Management (CRM) Applications

• ABBYY FineReader software products - competitor or

IBM DataCap software

Functional scope

• ECM solution based on FileNet P8 platform

• Prevent switching between CRM and ECM, BPM and

ECM, implement all-in-one software

• Integrate ECM solution with CRM Oracle Siebel

• Integrate ECM solution with BPM PEGA

• Integrate ECM solution with legacy applications

• Integrate ECM with the software for capturing and

recognition of documents.

• Implement the components for online usage of crypto-

provider and digital signature

Functional scope

• Introduce the categories and types of electronic documents

• Introduce the templates for several types of dossier

• Enable synchronization of ECM master data with other systems

in the enterprise application landscape

• Migrate existing documents from legacy apps

• Generate reports about status of migration and enable them for

web-access and export into PDF, Excel and Word format

• Enable FileNet-audit feature for all types of documents

• Implement reports based on data collected by FileNet-audit

and enable reports for web-access and export

• Implement SSO (Single-Sign-On) in accordance to the usage

scenarios defined by the customer

Non functional requirements

• 1500 users, 200 concurrent users

• Minimal number - 100000 customers

• 1500 documents/per customer

Client software requirements

• Internet Explorer version 8 (old IE version also supported)

• Internet Explorer versions 9, 10, 11

• Google Chrome version < 41 (only versions with enabled

support of ActiveX and Java)

• Java JRE 1.6 on client computer (also requirement of

CRM Siebel)

Architectural templates

• J2EE platform compliance

• SOA enabled application (services)

• Thin-Client application - Rich Internet Application (RIA)

• Usage of base products from IBM

• Usage of open source frameworks approved by the customer

• Design application in order to minimize efforts for migration to new versions of base software products

• Simplicity

• Maintainability

• Transparent build and deployment procedure

• Continuous integration

Solution baseline

• After analysis Pros & Cons, solution evaluation and

implementation of PoC the decision is made :

• implement SOA enabled applications (services and web-

apps) based on FileNet Content Management platform,

use FileNet P8 platform API

• Use software products supplied by IBM (WebSphere

Application Server ND, IBM FileNet P8 platform)

Base software products

• IBM WebSphere Application Server Network Deployment v8.5

• IBM FileNet Content Platform Engine, v5.2

• IBM Content Navigator, v2.0x (ECM client, supplied with IBM FileNet)

• IBM WebSphere MQ v.8

• IBM Integration Bus 10.0.0.3 (IBM Message Broker)

• IBM ISAM for Web 7.0 (previously named Web-seal, SSO support)

• Other software:• Oracle Database 11G (Database server for FileNet)

• SMTP servers

• LDAP (MS Active Directory)

Open source frameworks

• Main factor - Customer preferences and compliance

• Open source frameworks agreed with the customer

• Open source frameworks compliant to base products

listed on the previous slide and especially to

specifications implemented by IBM WebSphere

Application Server

Open source frameworks

• For instance, open source frameworks for UI implementation:

• JSF2 PrimeFaces, version 4.03, compliant to MyFaces 2.01 engine supplied by WebSphere Application Server v8.5

• jQuery - version of javascript toolkit compliant to PrimeFacesand supported versions of internet browsers

• Preferred are APIs, implemented in J2EE-platform and supplied with WebSphere Application Server:

• JSF2 (UI)

• JAX-RS (RESTful services), JAX-WS 2.1 (SOAP web-services)

• EJB 3.1 (MDB – Message Driven Beans, TimerService, Async-Beans)

SOA enabled solution – services

• Supported types of services

XML (JMS/MQ transport) services

SOAP/HTTP web-services

RESTFul services

XML messages transferred via MQ

• Transport - MQ/JMS, asynchronous

• Message payload for messages – XML,

generated in accordance to XSD schema

• Security mechanisms: supplied by MQ (SSL for

MQ)

• Usage scenario:

• Migration of data from legacy applications

• loading of documents produced by ABBYY

FineReader products

XML messages transferred via MQ

• Format of XML request:

XML messages transferred via MQ

Example of XML request:

<?xml version="1.0" encoding="UTF-8"?>

<xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchemaxmlns:ns2="http://bank.by/fn/type/document"

xmlns:tns=http://bank.by/fn/as/FNFindFolderRq

targetNamespace=http://bank.by/fn/as/FNFindFolderRq

elementFormDefault="qualified" attributeFormDefault="unqualified">

<xs:annotation>

<xs:documentation>(SVC-ECM-AS-05) </xs:documentation>

</xs:annotation>

<xs:include schemaLocation="../common/FnRequestType.xsd" />

<xs:import namespace="http://bank.by/fn/type/document"schemaLocation="../../types/document/filterFolder.xsd" />

<xs:element name="FNFindFolderRq" type="tns:FnRequestType" /><xs:element name="filterFolder" type="ns2:filterFolder"substitutionGroup="tns:AnyMessagePayload" />

</xs:schema>

SOAP/HTTP web-services

• Transport - SOAP/HTTP, synchronous

• Message payload for messages – XML,

generated in accordance to XSD schema

• Security mechanisms: message level security,

• SOAP WS-security: Username Token authentication

• Typical usage scenario:

• Work with the documents from PEGA PRPC or from CRM

Siebel

SOAP/HTTP web-servicesExample of SOAP request:

<soapenv:Envelope xmlns:ecm="http://bveb.by/fn/EcmService" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

<soapenv:Header>

<wsse:Security soapenv

…

<ecm:createFolder>

<folderRef>

<folderDetails>

<folderId>{F3355E12-53B4-4F56-9F8E-7D77A7EA0ECD}</folderId>

<clientId>1-4QB77</clientId>

<productId>1-2648</productId>

<title>Вопросник</title>

<path>/Документы клиентов/2. Клиенты физ.лица/Иванов Иван Иванович 14.04.1986/Общие</path>

<folderId>{F3355E12-53B4-4F56-9F8E-7D77A7EA0ECD}</folderId>

<dateCreated>2015-12-22</dateCreated>

<hasDocs>true</hasDocs>

<comment>Вопросник</comment>

</folderDetails>

<listOfFolderRefs>

<folderRef>

<folderDetails>

RESTFul services

Transport: RESTFul

• Message payload for messages – XML, generated in

accordance to XSD schema

• Security mechanisms: HTTP BASIC

• Typical usage scenario:

• Work with the documents from PEGA PRPC or from CRM

Siebel

Services format validation

Format of message payload is the same for all

types of services:

XML messages (MQ/JMS transport)

SOAP/HTTP web-services

RESTful services

• Validate XML messages against XSD:

• In Java Enterprise application (ECM client application)

• In the application deployed on IBM Integration Bus

Development tasks

• FileNet logical model

• FileNet-audit configuration

• Services for migration of documents from legacy systems

• SOAP and RESTful services

• SOA enabled application (services)

• Reports for migration and audit of documents

• Integration and wiring of services for usage from BPM PEGA or from CRM

• Testing of services

• ThinClient apps - RIA (Rich Internet Application)

Operational tasks

• ECM FileNet platform products installation and

configuration

• IIB (IBM Integration Bus) installation and configuration

• Results:

• BPM, ECM and ESB (оperational model, physical level

diagram)

• CRM, ECM and ESB (оperational model, physical level

diagram)

BPM, ECM and ESB (оperationalmodel, physical level diagram)

CRM, ECM and ESB (оperationalmodel, physical level diagram)

Single-sign-on (SSO)

implementation• Solutions for SSO implementation

• Programmatically create user credentials given for user

principal name

• Use IBM Security Access Manager for Web (ISAM for

Web or IBM WebSeal reverse proxy)

What is delivered to the customer

• Installed and configured infrastructure for FileNet products

• Installed and configured infrastructure for IBM Integration

Bus (IIB)

• Operational documents

• Deployment packages for custom app. ECM client

EAR including:

• Application with all kinds of services (SOAP, RESTFul,

MQ/JMS)

• ThinClient applications for usage with Oracle Siebel CRM

• ThinClient applications for usage with BPM PEGA

• SSO for CRM and BPM usage scenarios

Usage scenario 1: Integration of

ECM with CRM Siebel

Usage Scenario 2: Integration of ECM

with CRM Siebel

Usage Scenario 2: Integration of

ECM with BPM PEGA

Usage Scenario 2: Integration of ECM with BPM PEGA

Usage Scenario 2: Integration of ECM with BPM PEGA• Showcase: custom web application in PEGA PRPC

Usage Scenario 2: Integration of ECM with BPM PEGA

Usage scenario 3: IBM Content Navigator web-app also supported• Showcase: IBM Content Navigator