WebSphere Business Process Management V7WebSphere Integration Developer - Feature Pack 2 Overview
WebSphere Business Process Management V7 WebSphere Integration Developer - Feature Pack 2 Overview
This presentation covers the WebSphere Integration Developer feature pack 2 overview.
Agenda
Agenda Feature Pack 2 installation Platform currency What is the difference between Business Process Management and Case Management What is being delivered in Feature Pack 2? Life cycle summary – how does it work? Resources Summary
You will start with learning about how to install the Feature Pack 2. Then you will see how component levels have been changed for platform currency from version 7 to Feature Pack 2. In order to set the stage appropriately for what this feature pack brings, it is important to start with what is the difference between Business Process Management and Case Management. Once that is understood, you will move onto a summary of what is being delivered in Feature Pack 2. The overview will then set the stage for the main part of the presentation; a step-by-step view the life cycle and how does the enhancement work. You will finish up with a look at documentation resources with direct link for this enhancement and a summary.
Feature Pack 2 Installation
Feature Pack 2 Installation IBM Installation Manager 1.4.1 needed to install Must install, not an update Only for WID, no runtime counterpart for FEP 2
First of all, you must install the feature pack two using IBM Installation Manager version 1.4.1. Here is a reminder that you must click the install button and not the update button in IBM Installation Manager. A big point for feature pack two is that it is only for WebSphere Integration Developer and WebSphere Adapters. There is no runtime counterpart for feature pack two.
V7 Platform Currency
4 V7 Platform Currency Updated foundation for improved functionality Changes in V7 to V7.0.2.0 (Feature Pack 2) in blue WID V7 Eclipse v3.4.2 Rational Application Developer V7.5.4 WTE: WAS ND 7.0.0.7 -wps0946.04 WPS/WESB 7.0.0.0 -of0948.05 SCA FP 1.0.1.0 -z0945.03 i11a XML FP 1.0.0.0 -g0945.03 i11a IBM Installation Manager 1.3.3 Optional install packages: WebSphere Adapters (v7) Lotus Forms (v3.5.1) WID V7.0.2.0 (Feature Pack 2) Build ID - 7.0.0.3-20100825_1011 Eclipse v3.4.2 Rational Application Developer V7.5.5.1 WTE (FEP1): WAS ND 7.0.0.11 -wps0946.04 WPS/WESB 7.0.0.3 -of1034.05 WBIFEP 1.0.0.0 -of1019.04 SCA FP 1.0.1.7 -cf071033.04 XML FP 1.0.0.7 -cf071033.05 IBM Installation Manager 1.4.1 Optional install packages: WebSphere Adapters FEP 2 (v7) Lotus Forms (v3.5.1) WebSphere Integration Developer - Feature Pack 2 Overview
This chart shows how the various components of WebSphere Integration Developer have been updated from version 7 to version 7 feature pack 2. Notice the WebSphere Test Environment is grayed-out for feature pack two since there is not a runtime counterpart for feature pack 2, only WebSphere Integration Developer and WebSphere Adapters.
Overview
5 TB Overview
You will start by learning a little more about what is Case Management, what is WebSphere Business Process Management, and then what is new for the integration story.
IBM Case Management versus Business Process Management (1 of 2)
IBM Case Management versus Business Process Management (1 of 2) Process focused Pre-defined process Data feeds the process Repeatable/predictable Business Process Management (BPM)
First you will cover Business Process Management, or BPM. Generally, BPM focuses on processes as the core driver, and data interacts with the process. BPM does an excellent job with pre-defined processes; ones that are repeatable, but also ones that can be dynamic.
IBM Case Management versus Business Process Management (2 of 2)
IBM Case Management versus Business Process Management (2 of 2) Data focused – case focused Ad-hoc, knowledge worker driven process Contextual by nature Unpredictable/unrepeatable Think in terms of a case (data) Create a case file and follow a process; lead with case first Case data used by case managers/team who collaborate to resolve and close a case; typically long lived processes After a case is closed, information is retained 360 degree view of the case throughout a process Ex: view of customer from different roles IBM Case Management
For IBM Case Management the core focus is on the data. The process interacts with the data and is contextual by nature. Case Management does an excellent job with ad-hoc type processes like ones that are knowledge worker driven process or ones that are unrepeatable. Data is thought in terms of a case and a case needs to be created before a process can be defined. Case data can be used by a case management team who collaborate to resolve and close a case. Typically, these processes are long lived and case data is retained after the case has been closed. The true value of Case Management is the 360 degree view of the case throughout a process. For example, this means a knowledge worker can have a complete view of customer and has a different context view of the case given different roles.
Enriching Advanced Case Management Scenarios with WebSphere BPM
Enriching Advanced Case Management Scenarios with WebSphere BPM Delivered in WebSphere Integration Developer V7.0 Feature Pack 2 Enable invocation of a WebSphere BPM process from an IBM Case Management task WebSphere Integration Developer to enable generation of appropriate source artifacts and invocation scripting Provide documentation to facilitate use of WebSphere BPM with IBM Case Manager Case Management support delivered in P8 Process Engine 5.0 For existing WBPM customers Simplified access to case structure during process design Easier re-use of existing WebSphere BPM processes in a case management context For existing Filenet customers Better integration into a full SOA BPM infrastructure, Business Process Management IT Developer
What is being delivered in WebSphere Integration Developer V7.0 Feature Pack 2 is the ability to connect IBM Case Management with Business Process Management. That is, you can enable invocation of a WebSphere BPM process from an IBM Case Management task. In addition, WebSphere Integration Developer generates the appropriate source artifacts and invocation scripting needed, plus provides documentation to facilitate use of WebSphere BPM with IBM Case Manager. The Case Management part is delivered in P8 Process Engine version 5.0. What this means for existing WBPM Customers is a simplified access to case structure during process design and easier re-use of existing WebSphere BPM processes in a case management context. What this means for existing FileNet customers is a better integration into a full SOA BPM infrastructure like Business Process Management.
Life cycle – Business Analyst starts life cycle
Life cycle – Business Analyst starts life cycle IT Developer Business Analyst FileNet Case Manager & P8 Runtime WebSphere Integration Developer & WPS Runtime A Business Analyst Creates a case management solution Defines an unimplemented task that will connect to and run a BPM process Works with IT Developer to communicate details (inputs, outputs, case tasks to be implemented, security, and so on.) 1
In order to explain how this enhancement will work, you will use this diagram to step through which role does an action in a certain number of steps. The first step is for the business analyst on the FileNet Case Management side to create a case management solution. This means the business analyst defines an unimplemented task that will connect to and run a BPM process. Afterwards, the business analyst works with an IT developer using business process management to communicate details like inputs, outputs, case tasks to be implemented, security, and so on.
Life cycle – In Case Manager Builder
Life cycle – In Case Manager Builder Business Analyst - Create case tasks for case types - Unique identifier will show in WID - Preconditions (events) determine when a given task is available to the case worker
Here is an example of step one where the business analyst has defined the case management solution, tasks, and case types in the IBM Case Manager Builder. The information that is entered here is important because it will help uniquely identify the task when the IT developer using WebSphere Integration Developer, or WID, will implement a coordinating business process. The preconditions, which you can think of as events, can determine when a given task is available to a case worker.
Life cycle – IT Developer implements task
Life cycle – IT Developer implements task IT Developer Business Analyst FileNet Case Manager & P8 Runtime WebSphere Integration Developer & WPS Runtime An IT Developer Implements the Case Manager task as a business process Uses External Service Wizard to discover case definitions WebSphere Integration Developer introspects Case definition for tasks (via Filenet P8 API) WID prompts developer which tasks to implement … 2
Once the business analyst has finished building and testing the case management solution, the business analyst communicates with the IT developer using WebSphere Business Process Management software to implement the case manager task as a business process. That is, the IT developer uses the external service wizard in WebSphere Integration Developer to discover case definitions. WebSphere Integration Developer will introspect the case definition for tasks using a Filenet P8 API and prompts you which task or tasks to implement.
Life cycle – IT Developer implements task
Life cycle – IT Developer implements task IT Developer Business Analyst FileNet Case Manager & P8 Runtime WebSphere Integration Developer & WPS Runtime Continued… WebSphere Integration Developer prompts developer which case properties are needed (inputs, outputs) on the business interface WID generates appropriate modules, WSDL, web service export, web service import for callback, BPEL, and Business Objects WID saves FileNet connection information in generated module … 2
In addition to prompting which tasks to implement, WebSphere Integration Developer prompts the IT developer which case properties are needed (inputs, outputs) on the business interface and generates appropriate modules, WSDL, a web service export, a web service import for callback, BPEL, and business objects. WID saves the FileNet connection information in the generated module to be reused if you need to run through the wizard again.
Life cycle – External Service Discovery
Life cycle – External Service Discovery IT Developer
Here is an example of how this action is done inside WebSphere Integration Developer. Select file, new, external service and open the plus sign for Case Management to find the option to implement as a web service.
Life cycle – External Service Discovery
IT Developer IT Developer fills out FileNet connection information Life cycle – External Service Discovery
The wizard will then step you though connecting to the FileNet system. You will need this information from the business analyst.
Life cycle – External Service Discovery
IT Developer Visual marker shows if task has already been implemented Shows tasks built by Business Analyst in Case Manager Builder Life cycle – External Service Discovery
On this page of the wizard, you will select with tasks you want to implement. Notice icons or visual markers have been built in to the tools to help identify if a task has already been implemented and only allows you to implement unimplemented tasks.
Life cycle – External Service Discovery
IT Developer Life cycle – External Service Discovery Select input and output properties
Once tasks are identified, select the inputs and outputs you are planning to use in the business process. More than likely, this has been agreed to between the business analyst and the IT developer.
Life cycle – External Service Discovery
Life cycle – External Service Discovery IT Developer - Microflow default due to immediate response - Both short and long running options creates BPEL - 3rd option for non-BPEL (ex: Java)
Now that you have identified the details of the case management task, chose how you will implement the case management task. You will have three options; a microflow, a long-running business process, or to not create a business process. Microflow is the default given the majority of cases for a case management task are to provide a more immediate response. However, both short and long running options creates BPEL code for you to work with. The last option assumes you will use a non-BPEL implementation like Java.
Life cycle – External Service Discovery
Life cycle – External Service Discovery IT Developer
The last page of the wizard allows you to specify what level of server the application is deployed to and if you need to use web service security. Note; adding security to web service affects the service. For example, moving a web service to a test environment to a production environment will change the web service details. Therefore, perform same security setup on the new server that you did with previous. When selecting “Use security to access the web service” check box, the secure port on the server will be used. Security is provided at the transport layer with WS-Security token over HTTPS layer. A default policy set, “BPM FileNet web Services”, is applied to web service export. “Use a secure socket layer (SSL) connection” check box selected by default. If security is not selected, user credentials are not encrypted. For long running business processes, encryption of the response flow from process back to the FileNet system is governed by SSL configuration of the P8 Component Manager. Ensure P8 Component Manager is configured to use a secure socket connection in order for the response data to be encrypted as well.
Life cycle – IT Developer implements task
Life cycle – IT Developer implements task IT Developer Business Analyst FileNet Case Manager & P8 Runtime WebSphere Integration Developer & WPS Runtime Continued… WID pushes content into Filenet repository (via Filenet P8 API) Implements business process based on WSDL/XSD contract 2
WID will then push the content into the Filenet repository using the Filenet P8 API and implements the business process based on WSDL/XSD contract.
Life cycle – What is generated?
Life cycle – What is generated?
Once content has been generated, you can open up the business process editor, interface editor, business object editor, or the assembly editor like on the next page.
Life cycle – What is generated?
Life cycle – What is generated? Set default policy set and provider binding Set default policy set and client binding SOAP 1.1, doc-lit, JAX-WS only
A default policy will need to be set in the export and import. Another item to make sure of is exports are generated as SOAP 1.1, doc-lit, or JAX-WS style only.
Validation
Validation Validation of service Right click Case Management web service export select “Validate” option or
Not only can WID push content to FileNet, but it can also validate the service. Right click Case Management web service export and select the Validate option.
Life cycle – Deploy applications and run
Life cycle – Deploy applications and run IT Developer Business Analyst FileNet Case Manager & P8 Runtime WebSphere Integration Developer & WPS Runtime Deploys business process Uses web service to communicate with FileNet Business process performs the work that drives outcome of the task 3 Deploys case management solution Uses web service to communicate with WPS Business users invoke tasks which invoke WPS web service 3 4 4
In the third and fourth step of the life cycle, both sides deploy their applications to their respective servers to test full communication using web services. Business users invoke tasks which invoke WebSphere Business Process Management web service and the business process performs the work that drives the outcome of the task.
Life cycle – Post deployment management
Life cycle – Post deployment management IT Developer Business Analyst FileNet Case Manager & P8 Runtime WebSphere Integration Developer & WPS Runtime 5 Test/Dev Environment Edit details input and output properties, web service endpoint, and security settings Validate with case task Clean Up Service Test/Dev Environment Edit details Update endpoint address in FileNet repository with P8 Deployment Tool 5 6 Production Environment Production Environment 6
Once the process is verified successful, that is when the applications are moved to their appropriate test or QA servers. This change involves an update to the endpoint addresses and a revalidation. Once final testing is done, the changes are done once more to move the applications to their production environments.
Resources
Resources Information Center http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=/com.ibm.websphere.wbpm.fep.doc/welcome.html
For more information on this enhancement, be sure to find the information center documentation on the feature pack two content at the link on this slide
Summary
Summary Feature Pack 2 Installation Needs IBM Installation Manager 1.4.1 Must install, not an update Only for WebSphere Integration Developer and Adapters, no runtime counterpart Provided Overview of IBM Case Management and it’s integration with WebSphere BPM WebSphere BPM/IBM Case Manager integration provides the ability to exploit the robust WebSphere BPM tools and runtime within case management solutions Provided link to more information
In summary, feature pack two installs with IBM Installation Manager 1.4.1 and is only for WebSphere Integration Developer and WebSphere Adapters. There is no runtime counterpart. This presentation provided an overview of Case Management integration to help understand the background for IBM Case Management and what this feature pack provides in terms of integrating with WebSphere BPM. Specifically, this integration provides the ability to exploit the robust WebSphere BPM tools and runtime within case management solutions. To finish up, you were provided a link to the Information Center for more details.
Feedback
Feedback Your feedback is valuable You can help improve the quality of IBM Education Assistant content to better meet your needs by providing feedback. Did you find this module useful? Did it help you solve a problem or answer a question? Do you have suggestions for improvements? Click to send email feedback: mailto:iea@us.ibm.com?subject=Feedback_about_WBPMv7_WID_FEP2.ppt This module is also available in PDF format at: ../WBPMv7_WID_FEP2.pdf
You can help improve the quality of IBM Education Assistant content by providing feedback.
Trademarks