Websphere Business Services Fabric Tutorials

Building an end-to-end business solution

2020-07-18T08:22:00.000-07:00

Websphere Business Services Fabric v7.0
Contact us...

Building an E2E business solution

Related links

Building an E2E business solution

Websphere Integration Developer

Assemble in Websphere Integration Developer
Configure and Test Dynamic Assembly
Change Policies with the Business Process Agility Space
Move the Solution to a new environment

Installing Lombardi 7.1

2010-10-18T17:43:00.003-07:00

Websphere Lombardi Edition v7.1
Contact us...

Table of Contents

Express Installation and Configuration Guide

Performing an installation using Lombardi Installer Simple option
Verifying installation

Related links

Express Installation and Configuration Guide

Once you have met the hardware and software requirements for installation, you are ready to install Lombardi Process Center using the Simple installation option, which requires just a few clicks to get started with Lombardi.

Lombardi Installer's Simple option automatically performs the following:

Installs and configures WebSphere Application Server.
Installs and starts Windows services needed to run Lombardi.
Installs DB2 Express Edition.
Creates and initializes DB2 Express Edition databases for Lombardi Process Center Server and Performance Data Warehouse.
Starts the Lombardi servers.
Imports system data and samples.
Launches Lombardi Authoring Environment.
Creates Lombardi program shortcuts, enabling easy access to Lombardi components.

Lombardi Installer's Simple option creates an account (Windows account) with the following credentials for accessing DB2 Express Edition:

User name: WSLE
Password: Lombardi

Performing an installation using Lombardi Installer Simple option

Start Lombardi Installer ()
The Lombardi Installer starts ()
Review Install wizard guide and click Next ()
Accept the License agreement and click Next.
Click Simple type ()
Choose install folder and click Next ()
Choose where to create product icons and click Install ()
The installation starts ()
Installation is complete. Click Done ()

Verifying installation

After installing Lombardi, logout from windows and login again using the windows account created by Lombardi installation (WSLE/Lombardi, UID/password).
Start Servers ()
The Server is starting ()
Run Lombardi Authoring Environment when the Server startup is complete ()
Enter User Name\Password (tw_admin\tw_admin or tw_author\tw_author ()
The User Name\Password is being authenticated ()
The Lombardi window shows up indicating successful installation ()

Installing Lombardi 7.1

2010-10-18T17:43:00.001-07:00

Websphere Lombardi Edition v7.1
Contact us...

Table of Contents

Express Installation and Configuration Guide

Performing an installation using Lombardi Installer Simple option
Verifying installation

Related links

Express Installation and Configuration Guide

Lombardi Installer's Simple option automatically performs the following:

Installs and configures WebSphere Application Server.
Installs and starts Windows services needed to run Lombardi.
Installs DB2 Express Edition.
Creates and initializes DB2 Express Edition databases for Lombardi Process Center Server and Performance Data Warehouse.
Starts the Lombardi servers.
Imports system data and samples.
Launches Lombardi Authoring Environment.
Creates Lombardi program shortcuts, enabling easy access to Lombardi components.

Lombardi Installer's Simple option creates an account (Windows account) with the following credentials for accessing DB2 Express Edition:

User name: WSLE
Password: Lombardi

Performing an installation using Lombardi Installer Simple option

Start Lombardi Installer ()
The Lombardi Installer starts ()
Review Install wizard guide and click Next ()
Accept the License agreement and click Next.
Click Simple type ()
Choose install folder and click Next ()
Choose where to create product icons and click Install ()
The installation starts ()
Installation is complete. Click Done ()

Verifying installation

After installing Lombardi, logout from windows and login again using the windows account created by Lombardi installation (WSLE/Lombardi, UID/password).
Start Servers ()
The Server is starting ()
Run Lombardi Authoring Environment when the Server startup is complete ()
Enter User Name\Password (tw_admin\tw_admin or tw_author\tw_author ()
The User Name\Password is being authenticated ()
The Lombardi window shows up indicating successful installation ()

Working with the WebSphere Insurance Content Pack

2010-09-28T16:21:00.001-07:00

Websphere Industry Content Packs
Contact us...

Table of Contents

Working with the WebSphere Insurance Content Pack

Insurance Capability Models
Insurance Process Models
Insurance Service Models
Insurance Common Components
Insurance Business Vocabulary
Insurance Business Object Model
Insurance Solution Scenarios

Related Links

Working with the WebSphere Insurance Content Pack

Insurance Capability Models

Using the Insurance Capability Models

Identifying the required processes for a capability

Using the drill down approach to identify the processes
Using the search feature to identify the processes

Modeling the processes in WebSphere Business Modeler

Insurance Process Models

Process Models listing for the WebSphere Insurance Content Pack
Viewing artifacts related to the Insurance Process Models

Viewing Modeler libraries required for process
Viewing the business measures for a process

Using the Insurance Process Models

Creating an executable process
Creating an monitor model for monitoring business measures for the process
Using the Insurance Process Models related libraries

Extending the Insurance Process Models

Modifying the Insurance Process Models
Adding Services to the Insurance Process Models
Adding roles to the Insurance Process Model

Verifying the Insurance Process Models

Exporting the Insurance Process Models
Verifying the Insurance Process Models for Enterprise Archive file creation

Insurance Service Models

Insurance service interfaces

Using the Insurance service interfaces

Identifying an SCA Library
Identifying a service interface
Using a service interface from an existing SCA Library

Extending the Insurance service interfaces
Testing the Insurance service interfaces

Insurance Common Components

Insurance common services

Insurance common services listing

Prerequisite tasks for working with the Common Components
Insurance Rules Engine service
Image Transformation service
Error Identification service
ACORD Bulk service
ACORD Debulk service
ACORD File Extraction service
ACORD Reject Repair service
ACORD Signon service
ACORD Validation service
ACORD to HRXML Credit Transformation service
ACORD to HRXML Crime Transformation service
ACORD Channel service
IRI Bulking Service
IRI Debulking Service
IRI Reject Repair Service
IRI SignOn Service
IRI FileExtraction Service
IRI Validation Service

Testing the Insurance common services

Testing common services in WebSphere Integration Developer (unit test environment)

Deprecated Insurance common services

Insurance Business Vocabulary

Using the Insurance Business Vocabulary

Importing the Insurance Business Vocabulary
Creating a business policy

Extending the Insurance Business Vocabulary

Creating roles
Creating channels
Creating concepts

Insurance Business Object Model

Using Insurance Business Object Model
Extending the Insurance Business Object Model
Creating a new Business Object Model
Importing Business Object Model into Rational Software Architect
Removing Industry specific stereotypes
Verifying the Business Object Model

Insurance Solution Scenarios

Prerequisite software for executing the Solution Scenario

Prerequisite tasks for installing the Solution Scenarios

Solution Scenario 1: Claim Status

Introduction

Business Process
Scope
Business measures and KPI
Asset listing

Viewing the Claim Status Solution Scenario artifacts

Viewing Capability Models and processes in the WebSphere Business Compass business design features

Using the drill-down approach to identify the processes
Using the search feature to identify the processes

Viewing the Process Model in the WebSphere Business Modeler
Viewing Lotus Forms in WebSphere Integration Developer
Viewing processes in WebSphere Integration Developer
Viewing the business measures modeled in WebSphere Business Monitor Toolkit
Viewing Common Components in WebSphere Integration Developer
Viewing the Solution Scenario metadata in WebSphere Business Services Fabric
Viewing the Business Vocabulary in Business Space

Executing the Claim Status Solution Scenario
Executing the Claim Status Solution Scenario using Business Space
Step 1: Updating the claims.csv file
Step 2: Accessing the Claims Summary Business Space
Step 3: Accepting claim inquiry details
Step 4: Transferring the claim to a claim specialist
Step 5: Closing the claim inquiry
Step 6: Viewing reports
Step 7: Viewing the Claim Status process flow

Extending the Solution Scenario
Testing the Solution Scenario

Developing the Claim Status BPM solution

2010-09-24T21:52:00.001-07:00

Websphere Industry Content Packs
Contact us...

Table of Contents

Understanding the Claim Status problem scenario
Model phase
Assemble phase
Deploy phase
Manage phase
Related links

Understanding the Claim Status problem scenario

Description
Business process
Key Pain Points
Key Performance Indicators and Business Measures required
Roles for the BPM solution

Model phase

Performing gap analysis for identifying assets
Searching for assets using the Asset Navigator
Completing Process Decomposition

Extending Insurance Process Models
Modifying the Insurance Process Models
Adding service tasks to the Insurance Process Models
Modifying the mappings in the extended process
Adding roles to the Insurance Process Model
Adding or modifying Insurance KPIs and business measures
Extending KPI and Business Measures

Services Identification

Extending Insurance Services Models
Extending Insurance Common Components

Creating implementation process models

Importing Insurance process models from WebSphere Business Modeler to WebSphere Integration Developer
Unit testing the Insurance Process implementation using WebSphere Integration Developer

Creating the user interface

Creating the user interface using Lotus Forms
Associating a human task in WebSphere Integration Developer

Model phase summary

Assemble phase

Implementing services

Implementing a service integration logic using Dynamic Assembler
Importing an SCA module to create a composite service definition
Unit testing services

Implementing monitor models using KPI and Business Measures

Modifying and exporting KPI and business measures in Monitor Models into WebSphere Business Monitor Toolkit
Configuring the Process Flow to emit events
Generating a monitor model
Updating the generated monitor model

Defining user-defined functions
Defining Metrics
Defining Key Performance Indicators
Defining Dimensional Mode
Defining the visual model

Testing the monitor model Project Interchange file

Implementing technical policies

Creating WebSphere Business Services Fabric project and importing namespaces
Implementing policies using Business Services Composition Studio
Simulating and testing policies

Assemble phase summary

Deploy phase

Configuring the BPM solution manually

Configuring the user registry in WebSphere Process Server
Configuring user access in WebSphere Process Server for viewing the WebSphere Business Monitor widget
Configuring dashboard alerts
Configuring the Business Space dashboard
Configuring Business Space themes

Testing the BPM solution

Verifying the widget
Testing the process executions and viewing instances
Verifying dashboards for KPI and metrics updates
Executing the Claim Status BPM solution

Updating the claims.csv file
Accessing the Claim Status Business Space
Accepting claim inquiry details
Transferring the claim to a claim specialist
Closing the claim inquiry

Viewing reports

Claim Status Dashboard
Analysis
Performance
Report

Viewing the Claim Status process flow

Claim Status Process
Claim Status Process Check

Deploy phase summary

Manage phase

WebSphere Insurance Content Pack

2010-09-24T21:14:00.001-07:00

Websphere Industry Content Packs
Contact us...

WebSphere Insurance Content Pack

Using the Insurance Capability Models

Identifying the required processes for a capability

Import Insurance Capability Models
Using the drill-down approach to identify the processes
Using the search feature to identify the processes

WebSphere Insurance Content Pack

Type of Assets	Artifact Type	Tools
Capability Models	Business Document file	WebSphere Industry Content Packs WebSphere Business Compass
Process Models	Modeler Archive Files (.mar)	WebSphere Industry Content Packs WebSphere Business Modeler
Service Models	SCA Libraries, WebSphere Business Services Fabric Projects	WebSphere Industry Content Packs WebSphere Integration Developer
Common Components	SCA Libraries, SCA Modules	WebSphere Industry Content Packs WebSphere Integration Developer WebSphere Process Server
Business Vocabulary	Fabric Content Archive (.jar) file	WebSphere Industry Content Packs WebSphere Business Services Fabric
Business Object Model	UML Models	WebSphere Industry Content Packs Rational® Software Architect - Design time (Recommended tool) Rational Data Architect
Solution Scenarios	SCA Modules SCA Libraries Modeler Archive Files Monitor Models WebSphere Business Services Fabric Projects Lotus® Forms Enterprise Archive files	WebSphere Industry Content Packs WebSphere Process Server WebSphere Business Monitor WebSphere Business Modeler WebSphere Integration Developer WebSphere Business Services Fabric WebSphere Business Monitor Toolkit WebSphere Dynamic Process Edition WebSphere Business Compass IBM® DB2® Enterprise Edition Lotus Forms Viewer Scalable Vector Graphics (SVG) viewer

Using the Insurance Capability Models

The Capability Models available with the WebSphere® Insurance Content Pack are packaged as a Business Document (.bda) file. This file can be imported into Business Space using the Business Design Space.

The Insurance Capability Models can be used to identify the process required for a capability. They can also be used to model the processes available in the Capability Models using WebSphere Business Modeler.

Identifying the required processes for a capability

Identifying the required processes for a capability involves using either the drill down approach to search the process or using the search feature to identify the process.

Import Insurance Capability Models

Ensure that you import the Business Document file that includes all the capabilities and processes related to the WebSphere Insurance Content Pack before searching for processes.

Importing the Business Document file involves the following steps:

Start the Business Compass Server ()
Log on to Business Space ()
Click Actions\Create Space ()
Provide the space name and space description, select Business Design Space from the Create a new space using a template list, and then click Save ()
In the newly created space, click the Design tab and then click Upload a local file to repository ().
Click Browse button, select the required Business Document file to upload, and click OK ()
Note: Ensure that you select all the check boxes for the capabilities and sub capabilities for the WebSphere Insurance Content Pack and click OK ()
The Insurance Capability Models are imported ()

Using the drill-down approach to identify the processes

In the Documents tab\Insurance Capability Model CC, click Insurance Capability Model V7.0 Edit or View button ()
In the Outline view, click the main capability to view the capability map.
Click View sub capability in the capability to view the sub capabilities.
Note: The View sub capability option is visible if the capability includes sub capabilities.
Click the sub capability for which you want to view the related processes.
Click Details\Supporting Processes to view the processes.

Using the search feature to identify the processes

In the space where you have imported the Business Document file, clickSearch ().
Set the search type to My Documents.
Enter the name of the process you want to search for and click Search.
Click the required process to view the process details.

Moving the Solution to a new environment

2010-09-11T10:10:00.001-07:00

Websphere Business Services Fabric v7.0
Contact us...

Moving the Solution to a new environment
Re-creating Business Space

Re-create Fabric Administration Space
Re-create Fabric Authoring Space

Related links

Moving the Solution to a new environment

This topic describes how to move the content authored in Business Space and Composition Studio from one environment to another.

When moving a solution from one environment to another, it is important to remember that the content authored in business space and Composition Studio lives in a repository used by the server. It is necessary to export the content from one server and import it into another.

Each application and business service will have an associated Fabric project that can be exported as a special zip file (Fabric Content Archive) using the Fabric Admin Console. Vocabularies each have a dedicated namespace within the Fabric Business Glossary project.

Log into the Fabric Administration Console ().

Using the menu on the left, go to Governance Manager-> Import/Export
Select the Export by Project tab.
Content Type: Select Full content
Project Selection: Select the required Fabric project (i.e Business Glossary)
Namespace Selection: Select the required namespace (i.e Loans Origination Vocabulary).
Click Export to File to save a zip file containing the contents to disk

Export the Fabric project for each of the business services and applications in the solution.
Use the import tab to import Fabric archives in the correct order ()

Using the menu on the left, go to Governance Manager-> Import/Export
Select the Import tab.
Fabric Content Archive Selection: Select Browse to find the required FCA file.
While the export can be performed in any order, the same is not true for import. The system will fail to import an archive that has unsatisfied dependencies on content in other fabric projects. For the Loan Origination solution, we have the following dependency graph (). On a new system, it is necessary to import the vocabulary first, followed by the business service, followed by the application itself. Because of this, it is helpful to name exported projects so that someone else knows in what order to import them ()

Re-creating Business Space

The export of FCAs does not carry configuration of Business Spaces from one environment to another. It may very well be the case that business spaces would be configured differently on a test machine versus a production environment. It will be necessary to create new spaces using the Fabric templates on the new environment. After this is done, the Fabric Administration space will be the only space that shows the imported business space content. Just as we did in the last section, use the Add Space button to define what spaces can use which object.

Re-create Fabric Administration Space

Create a Fabric Administration space after importing the FCA's.

After this is done, the Fabric Administration space will be the only space that shows the imported business space content ().

Re-create Fabric Authoring Space

Create a Fabric Authoring space after importing the FCA's.

After this is done, the Fabric authoring space will be initially empty. To populate the Fabric Authoring space with the business space content, you have to authorize the Fabric Authoring space to edit objects that are in the Fabric Administrative space. Do this as follows:

In the Fabric Administrative space\Business Service Lifecycle Management tab\Name column, click on the icon (not the link) of the element you wish to provide authorization for click Add Space ().
Associate Space with Element ()

Select the space you want to authorize (i.e CC LoanOrigination Authoring) from the list of Available Spaces
Click Add
Click OK.

Repeat the above steps for each element you want to provide authorization for.
The Fabric Authoring space will look like this after space authorization ()

Changing Policies with the Business Process Agility Space

2010-09-05T22:04:00.001-07:00

Websphere Business Services Fabric v7.0
Contact us...

Changing Policies with the Business Process Agility Space

Editing Policies in the Agility Space

Related links

Changing Policies with the Business Process Agility Space

The business wants to enable business users to periodically change policy settings without exposing all of the powering of the authoring space. In chapter 2, Andy the administrator created the Loans Origination Policy Management space and made it accessible to Joe, a business user.

When the Loan Origination application was created, it was automatically associated with the Loan Origination Authoring space it was created in. If Joe accessed the agility space, he would find it empty because the loan origination application needs to manually exposed for use in that space.

Andy the IT Administrator goes to the Fabric Administration space and opens the Business Service Lifecycle Management page.

This page shows all Applications, Business services, and Vocabularies that exist in the system and allows and administrator to control what spaces are allowed to see these objects.
Click the Add Space button. Add the Loans Origination Policy Management space and click OK.

Editing Policies in the Agility Space

The Business Policy Configuration page allows a user to view and edit existing application-level policies. The application flow is used as a visualization and navigational aid to find policies relevant to a given business service. Edits to policies are restricted to editing existing values in policy conditions or results. Policies authored at the level of a business service are not accessible through this space. All changes go into a change set and are not available in the runtime until the change set is approved and published. Once the changes are published, the new invocation of a dynamic assembler will take advantage of the changes. Our business user wants to change the loan amount threshold used to determine whether manual or automated underwriting is performed during the Final Review business service.

In the business policies area, select the Final Review business service.
Select the Final Review Automatic Override policy and click Edit. Create a new change set with an explanation of the changes.
Select the condition about loan amounts, an click the pencil button on the right.
Change the value from 25,000 to 30,000. Click OK to dismiss the dialog and Save to leave edit mode.
The change set shows up in the governance tab. Several policies could be edited with the same change set. Click submit change set and provide a comment for the reviewer.

The changes must be approved and published before they take effect at runtime. After the change, a loan amount of $26,000 will use the automatic variation for Final Review.

Configuring Technical Policies

2010-09-05T20:49:00.001-07:00

Websphere Business Services Fabric v7.0
Contact us...

Configuring Technical Policies

Related links

Configuring Technical Policies

Within the Automated Credit Check process variation we have placed a dynamic assembly component (ChooseCreditCheck) responsible for selecting which credit service to use. To configure this endpoint selection, we will create some policies. Policies created in Composition Studio are not visible to business users using the Fabric authoring space, but the business has specified the following two concerns that are controlled with business policies:

Credit Check Type = whether to use an internal credit check system or to get a fresh report from a third-party credit reporting agency.
Premium Credit Service = whether to require the use of a credit service that offers better data, though probably at a higher cost.

A policy can be thought of as a statement with the following form:

FOR <Policy Target>

From <effective date>
To <expiration date>

When <conditions>

Then <assertions>

Policies do not directly specify a desired outcome, such as the selection of a particular endpoint. Instead, a policy provides 1 or more assertions that establish what must be considered when the policy is enforced. The dynamic assembler, as a policy enforcement point, filters out endpoints that are not consistent with a policy established for the invocation.

Set-In-Context Assertion

A Set-In-Context Assertion specifies a value for a business concept that should be set in the context. When the dynamic assembler sees this assertion in a composite policy, it will establish the specified content dimension with the specified value in the business context before invoking the selected endpoint.

In our example, we have a business –authored policy that sets a value for Credit Check Type (either Internal or Third-Party) in the context before invoking the Automated Credit Check Process Variation.

Notes:

Using Set-In-Context does not allow for forward-chaining in the evaluation of policies for a single dynamic assembly decision. In other words, the assertion impacts the context available for the endpoint that is invoked. It does not cause the system to reevaluate the policies for the current assembly step.
A Set-In-Context Assertion is ignored for the purposes of selecting an endpoint. In fact, this assertion may only be added to policies. The required setting, since it only applies to matching assertions may be ignored.

Using fill from context for a set-in-context assertion would be nonsense since that would direct the system to establish a value in the context that already exists.

Matching Endpoints with Vocabulary-Based Assertions

A Vocabulary Constraint Assertion, or constraint, is used to define an expression that serves as a constraint for endpoint selection. For example, a statement like “the value of Credit Check Type must be equal to INTERNAL” would be expressed with this type of assertion.

A Vocabulary Assertion, or fact, is used to define facts that are considered when evaluating constraints specified with Vocabulary Constraint Assertions. For example, the statement “Credit Check Type is set to INTERNAL” would be represented as a fact.

During the Find Candidates stage of processing, the system first narrows the set of endpoints by eliminating endpoints that do not meet the requirements of the selection policy. Constraints in the policy are compared to facts about the same concept declared via Vocabulary Assertions on the endpoint. If the facts don't satisfy the constraints, the endpoint is rejected.

After filtering the endpoints by selection policy, the system considers constraints on the endpoint against facts declared in the selection policy and eliminates endpoints whose constraints are not satisfied.

Use the required option for constraints. If the assertion is not marked as required on the policy side, the system may arrive at a slightly worse score for an endpoint instead of filtering it out-right. On the endpoint side, a missing required flag will cause the constraint to have no effect on selection. Since facts are not actively involved in filtering, the required flag has no effect.

The Fill from Context option is only available for assertions in policies. When this option is used, it means that the value field for the assertion should use the value for the selected concept as established in the context. In our example, business policies use the set-in-context capability to establish values in the context. We'll be using the fill-from-context option to pick up these business settings endpoint matching purposes.

Next, we'll create our first technical policy. Extending the pseudo-grammar introduced earlier, we want our policy to express:

FOR <ChooseCreditCheck>

WHEN always

THEN Assert the FACT (Credit Check Type is <fill-from-context>)

This policy will cause the business policies that set values for Credit Check Type to play a role in how the endpoint selection decision is made.

The completed vocabulary-based assertion should look like this when you have completed the steps below ()

In the Business Application Explorer view, right-click the Composite Service\CheckCredit\ChooseCreditCheck DA Component and select New\ Policy from the context menu ()
When creating a policy, the system will use the selected element as the policy target, if possible. You can also select the target explicitly in the create wizard.
Name = Match on Credit Check. Click Finish ()
Select the Policy Expression tab of the policy editor and click the Add button to add a new assertion ()
We'll be configuring a fact, so choose Vocabulary Assertion ()
Assertion Options

Required = check
Fill from Context = check

Assertion Property Values

Business Concept = Credit Check Type
Concept Value = Internal (See notes below)
Sometimes, a validation error will occur if the Concept Value field is not filled. If you see this error, it can be resolved by picking any value for the concept. If fill from context is enabled, the system will always replace any value you select with the active value in the context. However, if no value is supplied in the context, the system will use the value you specified. If a value from context must always be used, set the vocabulary dimension as required in the context specification and the system will never allow the value entered here to be used. On the other hand, if the value will not always be available in the context, make the dimension optional and the value supplied here will be used as a default.

Click OK ()

Creating a Policy to Enable the DA (Dynamic Assembler) to Enforce Business Decisions

Next, we'll create a second policy that will allow the dynamic assembler to enforce the business decision about when to use a Premium Credit service. In pseudo-grammar:

FOR <ChooseCreditCheck>

WHEN Premium Credit Check = True AND New Customer = True

THEN Assert Constraint (Premium Credit Check must equal True)

After you complete the steps below, the resulting policy should look like this ()

Create a second policy (as done above) targeted at ChooseCreditCheck with the name: Premium Credit Checks for New Customers When Needed
Create a policy expression that looks like the following ():
AND
Premium Credit Check = True
New Customer = True

Right-click inside the Expression canvas and select Add\Operator\AND from the context menu ()
Right-click the AND operator that you previously created and select Add\Condition\Business Concept from the context menu ()

Business Concept = Premium Credit Check
Comparator = equals sign
Concept Value = check the box
Click OK ()

Right-click the AND operator again to add a second business concept expression. Fill it in to express New Customer = True

Business Concept = New Customer
Comparator = equals sign
Concept Value = check the box
Click OK ()

Add a policy assertion that looks like the following ()

Click the Add button to add a new assertion to the policy then select Vocabulary Constraint Assertion and click OK ()
Use the dialog to express the constraint Premium Credit Check = True ()

Create a new context specification as shown earlier and call it Choose Credit Check CTX. Add the following vocabulary dimensions:

Credit Check Type, required
Premium Credit Service, optional
New Customer, required

Open the editor for the ChooseCreditCheck Dynamic Aassembly Component and associate the new context specification.

Configuring the Business Application Module

2010-09-05T18:51:00.001-07:00

Websphere Business Services Fabric v7.0
Contact us...

Configuring the Business Application Module

Map Business Services and Channels
Associate Endpoints with Process Variations
Define Context Specifications

Related links

Configuring the Business Application Module

When our business analyst authored the application and its business service, she had no exposure to the notion of a dynamic assembly implementation component. And up to this point, nothing was done to associate the SCA modules to the content authored in business space.

Map Business Services and Channels

In this section, we will perform some mappings that configure the dynamic assembly components to execute policies authored in Business Space.

In the Business Application Explorer, double-click the composite service named LoanOrigination to open it. In the Composite Service editor that appears, do the following: ()

Click the Business Application tab
Check the box Maps to a Business Application Module to enable the rest of this page
Click the Browse button

In the Application Selection window, select Loan Origination and click OK ()
The Business Service Mapping and Channel Mapping choices appears ()
Business Service Mapping
For each Dynamic Assembly Component, choose the business service task that it represents

Click the Browse button of the desired Dynamic Assembly Component
Select the desired Business Service ()
Repeat steps 1 to 2 as required

Channel Mapping
For each export in the module, select the Business channel that will be invoking it

Click the Browse button of the desired Channel Mapping
Select the desired Channel ()
Repeat steps 1 to 2 as required

After these mappings, the tab should look like this ()

At runtime, these mappings allow the system to use the active export, module, and DA component to find:

The business channel associated to the export
The application associated with the module
The business service and optional role associated with each DA Component.

These business dimensions are then made available in the context for invoking business and technical policies.

Important: Policies authored in the business tooling will only be considered by dynamic assembly components that have been configured, in this way, as part of a business application module.

Associate Endpoints with Process Variations

A dynamic assembly component uses policies to determine the most appropriate endpoint at runtime. When a business policy establishes that a given process variation of a business service should be selected, the system looks for an endpoint that declares that it supports this process variation (review Getting Started with IBM WebSphere Business Services Fabric V6.1 for further details).

In general, there may be several endpoints capable of supporting a given process variation and technical policies may enforce additional constraints on the selection. But for now, we have one endpoint for each variation. Let's configure them.

In the Business Application Explorer, double-click Endpoint\processes/Automatedcreditcheck/AutomatedCreditCheck, switch to the Assertions tab and click the Add button ()
In the Select Assertion Type window (), select Process Variation Assertion and click OK ().
Set the following as follows:

Required Box = Check
Business Services = Check Credit
Variations = Automated Credit Check
Click OK ()

Setting required on an endpoint assertion means that the endpoint will only be considered if the selection policy contains a matching assertion. It's a good practice to set Required when adding Process Variation assertions.

Set up all process variation assertions as follows using the same steps as above:

Endpoint	Business Service	Process Variation Assertion
AutomatedCreditCheck	Check Credit	Automated Credit Check
AutomatedUnderwriting	Final Review	Automated Underwriting
HumanUnderwriting	Final Review	Human Underwriting
AutomaticNotification	Notify Customer	Automatic Notification
HumanNotification	Notify Customer	Human Notification
HumanCollateralReview	Review Collateral	Human Collateral Review
NoCollateralReview	Review Collateral	No Collateral Review

Define Context Specifications

The next step is to identify the context elements necessary for a dynamic assembly component to apply the policies that have been implemented by the business user.

A context specification specifies the context that is needed at runtime to make a dynamic assembly decision. There are several advantages to using a context specification.

Context is central to the operation of the Dynamic Assembler.

The Dynamic Assembler uses context to make decisions on which endpoint should receive a request. The Dynamic Assembler performs a policy match on the context to determine which policies should be used in making the endpoint routing decision.

Since the context at runtime determines how policies are applied, it is important that all needed context is provided with each invocation. A context specification that indicates a particular dimension is required will ensure that the dimension has filled in the context at runtime. A context specification clearly indicates which items in the context are relevant for a particular decision point, and provides a prebuilt set of entry fields for new simulations of a dynamic assembly decision.

A context specification is used to ensure that all dimensions declared as required are made available at runtime. At design time a context specification also determines what context dimensions will be available for test simulations of dynamic assembly.

A new context specification automatically includes certain well-known context dimensions that will be provided automatically, such as the Service Interface and Business Service dimension. Generally, it is necessary to determine what additional business concepts are used in policy conditions and include these in a context specification as well.

Let's configure a context specification for Check Credit, the first business service in our flow. From looking at the business policies, we can tell that the policies need to know whether the customer applying for the loan is a new or existing customer. Also, we can tell that the amount of the loan is needed for processing.

Business Service	Business Service process variations	Business Service policies	Input/Output
Check Credit	Automated Credit Check (Since there is only 1 process variation, it will be selected all the time)	Credit Check default Internal Credit Check by Default Premium Credit Check Requirement	Input/Output Name: loanApplication Business Concept: Loan Application

Policy Name	Description	FOR (business Service or Application)	WHEN (No conditions, click to add)	THEN (No results, click to add)
Credit Check default ()	N/A	Check Credit	None	Select Automated Credit Check in Check Credit
Internal Credit Check by Default ()	Policy sets the internal credit check service as the default. Applications can override this to go to a third-party service	Check Credit	None	Set Credit Check Type to Internal
Premium Credit Check Requirement ()	N/A	Check Credit	Field Name: Amount of Loan Comparator: is greater than Value: 25,000	Set Premium Credit Check to True

Create a Context Specification

In the Business Application Explorer, right-click Loans Origination App Project and select New\Context Specification ()
Provide a name CheckCredit CTX, and click Finish. The newly created specification will open as an editor ()
Switch to the Dimensions tab of the editor (). Under Vocabulary Dimensions, click the Add button.
Select Amount of Loan, and click OK ()
Follow the same steps to add New Customer as second Vocabulary dimension. The resulting specification looks like this ()

The Required option is selected by default for newly added dimensions. It is a good idea to mark a context dimension as required if it should always have a value. If a dimension is only sometimes available in the context, deselect required. The system will not signal any error if an optional dimension is not provided.

A default value can be specified for a vocabulary dimension. Setting a default value has the same meaning as using a context extractor (next chapter) to specify a hard-coded value, but with the advantage that these values can be modified without changing or redeploying code. Use a default value if the value for a given decision is fixed. In our examples, we derive all values from business objects and other policies, so there is no need to set default values.

Associate a dynamic assembly component to a context specification

Double-click Composite Service\LoanOrigination\CreditCheck dynamic assembly component to open it. Select the Overview tab and click Browse button ()
Select Check Credit CTX and click OK ()
Note that a validation warning appears for any dynamic assembly components that do not have context specifications associated with them. Check for these validation warnings to make sure that this configuration step is not forgotten.

Define additional Context Specifications

Use this table to define context specifications for the remaining DA (Dynamic Assembly) components ():

Dynamic Assembly Component	Context Specification	Additional Context Requirements
CreditCheck	CreditCheck CTX	New Customer, Amount of Loan
CollateralReview	CollateralReview CTX	Line of Business
FinalReview	FinalReview CTX	Amount of Loan, Loan Status
NotifyCustomer	NotifyCustomer CTX	Loan Status

Importing SCA Modules to Create Composite Service Definitions

2010-09-05T12:53:00.001-07:00

Websphere Business Services Fabric v7.0
Contact us...

Importing SCA Modules to Create Composite Service Definitions

A composite service is a service whose implementation calls other services.

A composite service in Composition Studio refers to a System Component Architecture (SCA) module. A composite service may be as simple as an SCA module that implements and exposes a web service or it may include complex Business Process Execution Language (BPEL) programs and have bindings to other services exposed by other modules.

When you import a composite service, the metadata captured tells you about the following items:

Services exposed by an SCA module
Services consumed by the SCA module
Dynamic Assembly decisions performed by the composite service

When you import a composite service, endpoints are created for export bindings that have a binding type of SCA or Web Service Bindings set to use the SOAP/HTTP protocol.

When you edit your selected context specification, the results will modify any open simulations that are currently pointing to the current Dynamic Assembly Component. You must ensure that you do not change the dimensions. It is also desirable that you update your simulation when you update your context specification.

It is necessary to create composite service definitions to feed the dynamic assembler information about the interfaces, modules, and dynamic assembly components that will be deployed. This is done by importing SCA modules that exist in the workspace into Composition Studio.

In the the Business Application Explorer, right-click Loans Origination App Project and select New\Composite Service ()
Select the SCA Project to be imported (i.e LoanOrigination) and click Finish (). The following are created:

The import operation creates a Composite Service object that will show up in the Business Application explorer ().
It will also create Service Interface definitions for interfaces used by the module.
Endpoints are created for SOAP/HTTP or SCA Exports in the modules. Even though multiple modules may use a given service interface, the system does not create duplicates. Instead, it provides warning messages like the following ()

Once a composite service is created, changes in the original SCA module can be performed by carrying out the import again. It is important to import a module again if there are changes to its imports, exports or DA Components.

For each of the remaining modules listed below, carry out the same import steps 1 to 2 above ()

Project	Name Space	SCA Project (module)	Description
Loans Origination App Project	Loan Origination (Technical)	LoanOrigination	Module contains BPEL that captures the main process flow modeled in Business Space. Has several DA (Dynamic Assembler) Components, with one for each business service used in the flow.
Loans Origination App Project	Loan Origination (Technical)	CheckCredit	Uses another dynamic assembler to select among three backend credit services.
Loans Origination App Project	Loan Origination (Technical)	ReviewCollateral	Provides implementation of pass-through and human collateral review process variations.
Loans Origination App Project	Loan Origination (Technical)	FinalReview	Provides implementations for automated and human underwriting.
Loans Origination App Project	Loan Origination (Technical)	NotifyCustomer	Provides implementations for automated and human implementations.

Creating Endpoints for a Credit Check Service

2010-09-05T12:52:00.007-07:00

Websphere Business Services Fabric v7.0
Contact us...

Creating Endpoints for a Credit Check Service

Our ChooseCreditCheck dynamic assembly component needs to have some endpoints to consider. Earlier, we created endpoints for our process variations by importing some SCA modules. Here we'll create some endpoints for existing credit check services.

From the Business Application Explorer, right-click Loans Origination App Project and select New\Endpoint ()
This endpoint will represent our internal credit service. Enter name as Internal Credit Service and click Next ()
There are several available address types for endpoints, but you only need to use the SCA address type.
Using the server and port where the credit services are deployed enter a URL (i.e http://localhost:9080/BetterFinancialsBackendWeb/sca/InternalCreditCheck) ().

Click Finish.
Select the Interfaces tab of the Endpoint editor and click the Add Existing button ()
Select the getCreditReport Interface and click OK ()
The interface is added ()
Select the Assertions tab and click the Add button to add an new assertion ()
select Vocabulary Constraint Assertion and click OK ()
Enter the following information in the Vocabulary Contraint Assertion window ()

Required = check the box
Business Concept = Credit Check Type
Comparator = equal sign
Concept Value = Internal

The resulting assertions should appear as follows ()

Follow the same steps to create an endpoint for the Experian credit service. Use the following settings:

Name	Experian Credit Service
Interfaces	getCreditReport
Address	http://localhost:9080/BetterFinancialsBackendWeb/sca/ExperianCreditCheck
Assertions	Vocabulary Constraint Assertion: Credit Check Type = Third-Party, Required Vocabulary Assertion: Premium Credit Check = True

The resulting assertions should appear as follows ()

Follow the same steps to create an endpoint for the TransUnion credit service. Use the following settings:

Name	TransUnion Credit Service
Interfaces	getCreditReport
Address	http://localhost:9080/BetterFinancialsBackendWeb/sca/TransUnionCreditCheck
Assertions	Vocabulary Constraint Assertion: Credit Check Type = Third-Party, Required Vocabulary Assertion: Premium Credit Check = False

The resulting assertions should appear as follows ()

The TransUnion service is only available on weekdays. We'll use a Hours of Operation assertion to describe when this endpoint will be considered as available.

Add an Hours of Operation Assertion (). Hint: Enter a search keyword, i.e Hours, to easily find the assertion type.
Set the start time to 12AM, Duration to 24 hours, and select Mon – Friday ()

Establish a cost-based priority on the endpoints
The Experian Credit service is a premium service, but it also costs more to use this service than it does to invoke the TransUnion service. Let's use the cost field to establish a cost-based priority on the endpoints.

Open the Experian Credit Service endpoint. Select the Overview tab. Set the cost field to 2 and the cost modifier to “Transaction” ()
Edit the TransUnion endpoint to set a cost of 1 per transaction.

Simulate (Test) Business Service Decisions

2010-09-05T12:52:00.005-07:00

Websphere Business Services Fabric v7.0
Contact us...

Simulate (Test) Business Service Decisions

Related links

Simulate (Test) Business Service Decisions

A simulation in Composition Studio is a test that represents how the dynamic assembler behaves in a given business situation. It is a good idea to define a set of scenarios that represent the various inputs and expected outcomes for a given decision. For example, we have policies that determine whether we should review collateral based on line of business. To test this, we should have at least one case where the line of business causes a collateral review and one where it does not.

Let's create our first test for the CreditCheck dynamic assembly component.

From the Business Application Explorer, right-click Loans Origination App Project and select New\Simulation ()
Enter the following information into the Dynamic Assembly Simulation window and click Finish ()

Name	DA Component	Description
Automated Credit Check for Existing Customers	CreditCheck	New Customer = False Amount = 20,000 ---------------------------- Select Automated Variation & Establish Credit Check Type = INTERNAL

This is the new simulation ()

Since you may have several simulations for each Dynamic Assembler, it's a good idea to name your simulations to identify the test scenario. The description field is a good place to summarize the inputs and expected outcome of the simulation.

Note that the Business Service and Application dimensions are automatically provided under “Simulation Context”. The simulator is using the Business Application mappings that we established earlier to provide these fields. If you do not see these fields provided automatically, it is a good indication that the mapping was not performed and that the dynamic assembler will not consider policies authored in business space.

Fill out the context elements in the simulation editor. Click Edit… for Amount of Loan. Enter 20000. Click OK ()
This simulation is for an existing customer, so set New Customer = False, i.e make sure the box is NOT checked ()
Click Run ()

The results of running a simulation display the results for three phases of dynamic assembly. A green check mark shows up for each phase that successfully executed, or a red X will display on the first step that fails to execute. Keep in mind that an “all green” simulation may still be reflecting incorrect results. It is good idea to inspect the result of each phase.

During the build selection policy phase, the system finds all policies that apply given the simulation input settings. It then merges these policies into a Composite Policy. During the merge, priority rules may cause a setting of one policy to override another. Inspecting the composite policy shows which settings made it into the resulting composite policy and indicates which policy won out in contributing each setting. It is a good idea to check these results to make sure that policies are being applied in the way you expect.

During the find candidates phase, the system finds all endpoints that support the given interface and matches these endpoints against the composite policy. If an endpoint's assertions don't match required assertions in the composite policy, the output will indicate that the endpoint was filtered using the selection policy. An endpoint will also be rejected at this phase if a required assertion on the endpoint is not satisfied by the selection policy. Remaining endpoints are according to increasing cost and a suitability score based on the closeness of the match for non-required policy assertions. This rank is referred to as a tier.

During the select endpoint phase, the system selects an endpoint with the lowest tier value from the remaining candidates. If an endpoint is not available at the given time due to endpoint status, hours of operations, or other temporal concerns, that endpoint is rejected and the next best endpoint is considered.

Note that the simulation had no failures and that an endpoint supporting the automated credit check was successfully chosen.
Click the “Details” link for the Build selection policy phase. Verify that the policy sets the Credit Check Type to Internal ()
Create simulations for the other business service decisions as indicated by the table below.

Name	DA Component	Settings/Expected Results
Premium Credit Check for New Customers	ChooseCreditCheck	Business Service = Check Credit Application = Loan Origination Interface = getCreditReport Credit Check Type = Third-Party New Customer = True Amount = 30,000 ------------------------------------------- Select Automated Credit Check Premium Credit Service = True
Standard Credit Check for New Customer	ChooseCreditCheck	New Customer = True Amount = 20,000 ------------------------------------------- Select Automated Credit Check Credit Check Type = Third-Party
No Collateral Review for Auto Loans	CollateralReview	Line of Business = Auto -------------------------------------------- Select No Collateral Variation
Human Collateral Review for RV Loans	CollateralReview	Line of Business = RV -------------------------------------------- Select Human Collateral Review
Automated Underwriting for Small Loans	FinalReview	Loan Amount = 10,000 Loan Status = In Progress -------------------------------------------- Select Automated Underwriting
Human Underwriting for Large Loans	FinalReview	Loan Amount = 30,000 Loan Status = In Progress -------------------------------------------- Select Human Underwriting
Automatic Underwriting Pass Through for Rejected Loans	FinalReview	Loan Amount = 50,000 Loan Status = Rejected -------------------------------------------- Select Automatic Underwriting
Automated Notification for Approved Status	NotifyCustomer	Loan Status = Approved -------------------------------------------- Select Automated Notification
Human Notification When More Info Needed	NotifyCustomer	Loan Status = More Info -------------------------------------------- Select Human Notification

Testing the Choose Credit Check Decision

We'll need to create a few more simulations to test our policies and other configuration for the ChooseCreditCheck decision. Create the following simulations for the ChooseCreditCheck dynamic assembly component.

Name	DA Component	Settings/Expected Results
Select Internal Credit	ChooseCreditCheck	Credit Check Type = Internal New Customer = False -------------------------------------------- Select Internal Endpoint
Select Premium, Third-Party Credit	ChooseCreditCheck	Credit Check Type = Third-Party Premium Service = True New Customer = True -------------------------------------------- Select Experian
Select Normal Credit Service (Weekdays)	ChooseCreditCheck	Day of Week = Mon-Friday Credit Check Type = Third-Party Premium Credit Service = (not supplied) New Customer = True -------------------------------------------- Select TransUnion
Select Normal Credit Service (Weekend)	ChooseCreditCheck	Day of Week = Saturday or Sunday Credit Check Type = Third Party Premium Credit Service = (not supplied) New Customer = True -------------------------------------------- Select Experian

By default, a new simulation will fill in the time and date fields with the current date and time. In situation, where it is important to test hours of operation or other temporal concerns such as the effective date range for policies, use the date and time controls to specify exactly what time/date is being simulated.

For example, we can test a weekend request by picking any Saturday on the calendar:

Submitting Changes for Approval

We're done configuring the necessary metadata and testing of endpoint selection. Now we need to submit our changes to the Fabric Server so that this configuration is available on the server at runtime.

A Fabric Tool Pack install configures a Fabric Server Unit Test Environment to automatically approve and publish changes submitted from Composition Studio. For the purpose of this guide, we'll show the full process.

Right click on the Fabric Project (i.e Loans Origination App Project) in the Repository Changes View (Select Window\Show View) and select Submit Change Set. Select the project, and click Next.
Click the Add All button to select all changes. Provide a short description of the changes for the reviewer. Click Finish.
Click Yes if you are asked Are you sure you want to submit your changes?
A dialog notifies the successful submission of the change set and provides a numeric ID for the change set.

After submitting the changes, all objects in the change set become read-only until an update tells the system that the change set has been published or that the changes were rejected.
If auto-publish is turned on, the submitted changes will be automatically approved and published to the repository. Auto-Publish is turned on by default on a profile created by a Fabric installer (development/standalone profiles).

For more details on turning on/off auto-publish please see the Manage Changes section under Fabric for Administrators.

Note: The following Steps 4 to 7 are not required if your system is configured to auto-publish change sets.
Our Administrator, Andy, logs into Business Space and opens the governance tab of the Fabric Administration space. The change set submitted from Studio should appear as an active change set with a status of Pending.
Open the change set and review the details.
Click the Approve Change set button and provide a comment.
Click the publish button.
Back in WID, click the Update Project button
Select the project to be updated, click Finish.
The system will first replicate any changes from the server. These changes may include our own change submission, or changes made by other users.

The system tells us what version of the repository the project is now synchronized with and provides the current status of any outstanding change sets. After performing the update, the pending change set disappears since the project has now been updated to incorporate changes that took place on the server. Objects that were read-only while pending are unlocked so that further edits can take place.

Next, we'll need to switch to the Business Integration perspective to finish the assembly of our modules and perform some testing.

Implementing Context Extractors

2010-09-05T12:52:00.001-07:00

Websphere Business Services Fabric v7.0
Contact us...

Implementing Context Extractors

Implementing an Initial Context Extractor

Related links

Implementing Context Extractors

A Context Extractor is a Mediation Primitive located inside of a Mediation Flow Component. The Loan Origination Assembly contains three such components: one wired in front of the BPEL, and one each between the final two dynamic assemblers that are invoked in the process ()

Implementing an Initial Context Extractor

A Fabric Context can be established by using a Context Extractor. Dynamic Assembly components that occur later in the process will create sub-contexts from this initial Context. This pattern is useful if you need to establish some contextual data that will be used by all subsequent Dynamic Assemblers.

Do the following to an initial Context Extractor for the Loan Origination Assembly:

Switch to the Business Integration perspective by selecting Window\Open Perspective\Other.... Select Business Integration (default).
Open the Loan Origination\Assembly Diagram by double-clicking it.
Add a Mediation Flow
Rigth-click inside the Assembly Diagram (empty space) and select Add\Mediation Flow. Rename it to ContextExtractorMedFlow. The LoanOrigination Export should be wired to its left side, and the LoanOrigination Process should be wired to its right side. The editor will automatically add the appropriate interface to the Mediation Flow. The interface for the Export, the Mediation Flow, and the Process are all the same ().
Double-click the ContextExtractorMedFlow to implement it. Click the Yes button when the dialog box appears (The selected component is not yet implemented ...etc...).

The editor will ask you to select a location to store the generated implementation. Select LoanOrigination\extractors\main or create a new folder. Click OK button.
The main implementation editor for this Mediation Flow will now appear (). The left side (LoanOrigination) shows the interface and operation with which the flow is invoked. The right side (LoanOriginationPartner) shows the Reference Partner process, which happens to have the same interface and operation.
By clicking on the Criterion_loanApplication link on the left side interface, you will be presented with a mini wizard that will allow you to create an implementation. For this exercise, choose Blank Mediation Flow.
The Blank Mediation Flow appears. The first thing we need to do is to add a Context Extractor Mediation Primitive to the diagram. The existing primitive on the canvas represents the incoming request from the exposed interface.

Expand the Fabric folder in the Palette. This reveals the Context Extractor. Drag the Context Extractor and drop it on the canvas. Wire the existing primitive to the Context Extractor, and rename the Context Extractor to CommonContextExtractor()
Under the Service Invocation folder, on the Palette, click the Callout primitive and drop it on the canvas. You will be asked to select the Reference and the Operation. Since the Mediation Primitive is only wired to one Reference Partner, there is only one option for each. Click OK ().
After you click OK, the callout to the Reference Partner will appear on the canvas ().

Since the incoming request and the callout invocation use the same interface, there is no transformation of the message required in the Mediation Primitive.

Wire the context extractor to the callout.
Mapping Context Keys

Now let's specify the details of the Context Extractor itself. Click the Context Extractor Mediation Primitive. Once it is active, click the Properties editor in the lower panel, and then the Details tab on the left. This will bring up an editor capable of mapping Context Keys (Business Vocabularies) to Context Value Paths (runtime data from the request).

There are three main sections in the editor. The Context Operation specifies how the Context is to be altered. In this case, the default is fine: It will update the current Fabric Context if available, otherwise it will create a new one. The Context Mappings section is where extractions to be added to the Context are specified. The bottom section, Context Keys to Delete, allows you to specify items in the Context that should be removed by the primitive.

Click the Add button in the Context Mappings section. This will open a dialog box allowing you to specify the Context Key and the Context Value Path.

Click the Select button for the Context Key. Typically, this will pull up a listing of Vocabulary Terms from which you can select. (See Step ??.) However, if Business Space is not running or your project is not configured properly, you may see the following empty list of Vocabularies ().
In the above case, it may be necessary to configure the Context Extractor primitive. Click on the “Window” menu and choose “Preferences”. In the Filter of the Preferences editor, type “context” ().
Note: Ensure that the certificate of the runtime server has been imported into WID before updating this window. To import a certificate into WID please follow the steps in the topic: Connecting to the run-time server
Select the Context Extractor item under Business Integration / Medation Flow Editor. Ensure that all of the settings are correct. The Context Root should be left as “rest”, however, the protocol will likely need to be changed to “https” (Note: http works in my case). The Host, Port, User Name, and Password fields should also all be verified.
After the information has been verified, click the Update Vocabulary button. The editor will inform you if the update was successful or not (). In the case of it being successful, go to the next step. If the update fails, you may need to add the Context Keys manually. Instructions on how to do this start on Step ??.
After successfully completing step 10 above (configure the Context Extractor primitive), click the Select button for the Context Key again (step 9 above). The available Vocabulary Terms will appear, grouped by project. Expand Loans Origination Vocabulary and select Amount of Loan. Click OK ().
Next, click the Edit… button for the Context Value Path (). This will allow you to specify the XPath expression identifying the data in the request that should be associated with the Context Key. And XPath expression builder will appear.
In the simple expression builder, navigate the hierarchy by expanding the sections. Select the amountOfLoan:double under the LoanInfo object. Click OK (). In the Add/Edit Properties window that appears, click Finish (). The Context Key (Amount of Loan) is added ().

Follow the same procedure (Mapping Context Keys) for the Line of Business and New Customer Vocabularies. The values from the request should be lineOfBusiness from LoanInfo and newCustomer from CustomerInfo, respectively. You will end up with a Context Mapping that looks like the following ().
Two more Context Extractor Mediation Flows () need to be created for the assembly, one between the LoanOrigination Process and the FinalReview Dynamic Assembler, and one between the LoanOrigination Process and the NotifyCustomer Dynamic Assembler () . Follow the same procedure as above to create the Mediation Flows. Each extractor requires just one Context Mapping. The Context Key should be the Loan Status, and the Context Value Path should specify the loanStatus value in the LoanInfo object.
In the case that Business Space is unavailable, the Context Keys can be specified manually using the appropriate URIs. Navigate to the Business Service perspective in WID, and open the Assertion Explorer view. Expand the Business Vocabulary folder, and then expand the Loans Origination Vocabulary.

Double-clicking the desired Vocabulary will open that Vocabulary's editor. Its URI can be copied to the clipboard using the “Copy URI” button to the right of the ID field ().

Note: The following applies when vocabulary is not available/configured correctly. See above
Once this is complete for each Vocabulary, the Context Mapping section will resemble the following diagram:

Note that the URI of the Vocabulary is shown instead of its name. When Business Space is running again and/or your configuration is specified appropriately, these URIs will appear as names instead of URIs. The Context Extractor will continue to function in either case.

Deploying Modules to the Server

2010-09-05T12:51:00.003-07:00

Websphere Business Services Fabric v7.0
Contact us...

Deploying Modules to the Server

You must also deploy your modules to the server.

Go to the Servers View in the Business Integration perspective. Right-click on the Fabric Server and select Add or Remove projects.
Click the Add All button to deploy all of the projects. Click Finish to deploy these applications on the server.

Testing Round Trips

Do the following to test your process flow.

Right-click on the LoanOrigination export in the LoanOrigination assembly diagram. Select Test Component.
Click Continue icon ().
Choose the Websphere Dynamic Process Edition Server v7.0 at localhost as the deployment location. Click Finish ().
If prompted with a user login, provide username (admin) and password (admin) and click OK.
A trace of the interaction unfolds in the events section (). By clicking on request or responses it is possible to inspect the request and response messages sent or returned from various processing steps. The server console will display the message from the automated customer notification which indicates that Reba was approved for her loan.
Next, let's try a round trip that uses the variations with human tasks.
Create and run new invocation with the following settings in the loan application: With a web browser log into the business process choreographer at: http:localhost:9080/bpc ().
A human task for a collateral review is waiting. Select the task and click the Work on button ().
Enter the value APPROVED for the loanStatus in the Task Output Message. Click Complete ().
For the final review a new human task is created. If necessary, click Refresh for it to appear. Select this task and click the Work on button.
Enter MOREINFO in the loanStatus and click complete.
Finally, because more information is needed to process the loan, the human variant of Notify Customer is selected. Work on the task. Note that notify customer is modeled as a one-way operation. Clicking complete tells the system that the customer has been notified.

Creating a Fabric Project

2010-09-04T09:51:00.001-07:00

Websphere Business Services Fabric v7.0
Contact us...

Creating a Fabric Project

(Review Creating a project in the Fabric administrative console and Creating a Fabric project in the Business Services Perspective for more details).

This Fabric project that you will be creating in Composition Studio is a local replica of the one that already exists in Fabric. It was automatically created in Fabric while you were working on Fabric authoring in Business Space.

The Fabric authoring performed earlier using Business Space caused Fabric projects to be created. A Fabric project created for an application automatically imports each of the business services used by that application. We'll be connecting to the Loans Origination fabric project.

Note:

The first time a user creates a Fabric project, it is necessary to log in to the Fabric web console at http//<server>:<port>/fabric to establish a Fabric user account (The port (9080) is setup when you installed Webpshere Business Services Fabric. It is in the file called AboutThisProfile.txt (D:\wdpeV7\DynPrcEd7_WTE\runtimes\bi_v7\profiles\qwdpe\logs). If this step is not performed, the create project wizard will show an empty list of available projects

Start the Fabric Server (required!!). You have to connect to the Server during the process of creating a Fabric project.
In the Business Integration perspective, select File\New\Project … Select Business Services Fabric\Fabric Project, click Next ()
Provide a name for the project (i.e Loans Origination App) and click Next ()
Click the Configure button to provide server connection details ()

Protocol (http)
Hostname (localhost)
Port (9080)
Username (admin)
Password (admin)
Click OK ()

Wait. After several moments a progress bar will indicate the progress of replication. This operation may take a long time to complete ()
Click Next when replication is complete ()
In the Select a Fabric Project window, click on the drop-down listbox and choose Loan Origination from the list of available Fabric projects. Click Finish ()
A dialog appears asking if you want to "Open Associated Perspective". Click Yes ()
By default, the Business Service Perspective has a few views that are only useful if you are working with projects from WBSF 6.1.2 or earlier releases. Go ahead and close these views if empty:

Close the Subscriber Explorer view
Close the Business Services Explorer view

Expand the Business Application Explorer. Note that the application, business services, and policies authored in business space show up here with a lock icon indicating that they are read only. These objects can only be modified using the business space ()

Working with WebSphere Business Modeler

2010-08-12T15:03:00.001-07:00

Websphere Business Services Fabric v7.0

Working with WebSphere Business Modeler

Integrate Modeler with Fabric
Importing a Fabric application into the Modeler

Working with the Main Process Flow

Loan Origination application process flow
Setup Processes for each Process Variation
Export the project interchange file for WID
Import the project interchange file into WID
Modify the project in WID

Related links

Working with WebSphere Business Modeler

The process flow modeling capability available in the Fabric Authoring widgets is restricted to defining simple sequences of tasks and is not designed to be a replacement for Modeler. Instead, the application flow represents a simplified, high-level outline of the process which provides visual context for a business user to understand where policies are used in a solution.

There are two basic approaches for working with Modeler and the Fabric Authoring capability.

The first, and most general, approach involves disconnected use Modeler and Fabric authoring during the Model phase of development. Modeler is used to develop and simulate business processes while the authoring capability in business space is used to define business vocabulary and policies that determine the dynamic behavior of selected process steps.

The second approach, covered in this section, involves importing content authored in business space to establish a collection of Modeler projects with skeletal process flows. Once established, the modeler projects may be updated to pick up certain changes introduced in business space, but there is currently no reverse capability to import or update the content in business space with changes introduced in Modeler. Also, it is important to consider certain limitations that come along with using this approach.

Integrate Modeler with Fabric

You can skip this section if you installed Modeler and Fabric as part of Websphere Dynamic Process Edition 7.0 Tool and Testing Pack installation. However, if you installed Modeler and Fabric independently of each other, then you have to go through this process.

Note: Websphere Dynamic Process Edition 7.0.1 Tool and Testing Pack no longer includes Websphere Business Services Fabric. To use the Composition Studio (available in Fabric), you have to install Fabric and go through this same Modeler and Fabric integration process.

Stop WID if it is currently running (Websphere Integration Developer).
Start Business Modeler and select the same workspace you previously used for WID (which should not be running).
The first time you start up Business Modeler using a workspace you previously used for WID you may see a Workspace Migration requirement ()

Follow the migration instructions (, , ,) until completion ().
Define () and configure a Server ()
Use the following UID/Password, i.e admin/admin () and Server Settings ()
Review your Server settings if you see the following errors (, ).

Importing a Fabric application into the Modeler

Modeler features that support Fabric integration are only enabled in the Fabric mode. This mode includes all of the capabilities of the WebSphere Process Server mode and adds the ability to import from Fabric and the ability to set a technical attribute that indicates a task should be implemented with a dynamic assembler component.

Stop WID if it is currently running (Websphere Integration Developer).
Start Business Modeler and select the same workspace () you previously used for WID (which should not be running).
Start the server ()
This is a required step. Business modeler needs to connect to the server to be able to import the Fabric application which are stored on the Server.
Switch to Websphere Business Services Fabric mode by clicking Modeling\Mode\Websphere Business Services Fabric ()
From the main menu, select File\Import… Select WebSphere Business Modeler\WebSphere Business Modeler Import and click Next ()
Select Websphere Business Service Fabric Repository elements and click Next ()
Click the Add Repository button ()
Define connection details for the Fabric server to import from:

Location = http://localhost:9080
Note: The port (9080) is setup when you installed Webpshere Business Services Fabric. It is in the file called AboutThisProfile.txt (.._WTE\runtimes\bi_v7\profiles\qwdpe\logs). If you supply an incorrect port number, you will get an error message.
Name = Loan Origination
User Name = admin
password = admin
Click Finish ()
The Repository Contents section shows the applications, business services, and vocabularies grouped by the business space(s) they are associated with. You will only see the content in those fabric authoring spaces that you are authorized to see in the Business Space.

Specify the repository elements that you want to import and click Finish ()
Click OK when you see the message Import finished successfully confirmation window ()
This is the imported Fabric application ()

The import operation creates several Modeler projects. Each imported vocabulary becomes a project that contains business items derived from the object concepts that were defined in the authoring space.

Each business service becomes a modeler project with an empty process flow created for each process variation that was defined. A service is defined for the business service itself with technical attributes automatically set to indicate implementation with a dynamic assembly component.

Finally, an application becomes a modeler project with a process flow that captures the process modeled in the application flow. Each task in the flow uses an abstract service defined in a business service project.

Vocabularies and business services are designed to be reused in solutions that have been developed. Multiple modeler projects are created for the same reason. Instead of duplicating business items or business service logic each time it is needed, this content is grouped into different modeler projects that could be reused.

Working with the Main Process Flow

Loan Origination application process flow

Starting at the top, let's look at the process flow created for the Loan Origination application.

Open the Loan Origination process () in the Loan Origination project and open the Window\Properties view ()

In the Fabric authoring space, we defined two channels that could invoke the process including “Customer Care Call Center” and “Better Financials Online”. Since there is no concept of a channel in Business Modeler, this information does not appear in the process flow.

When defining the business services in the authoring space, we were careful to specify the loan application as the input and output of every business service. When the process is imported, the orchestration from one task to the next is only preserved when the output of one business service is the same as the input to the next.

For the purposes of authoring policies in a Fabric authoring space, it is sufficient to add inputs to a business service to represent the business concepts that need to be available to evaluate policies for that step at runtime. When the modeler import is brought into the picture, business service inputs and outputs need to be modeled more completely and with greater restrictions since these are used to define the business items and flow from one task to the next.

The output of the final step in our Loan Origination process is wired to the process terminal. If we want our process to yield an output we'll need to configure and output on the process.
Add an output node (Loan Application)

In the Loan Origination process, click anywhere on an empty space on the canvas, select the Properties tab, click Outputs and click the Add button ()
Change the default Associated data type (from Text to Loan Application) to make it compatible with the output of Notify Customer task. Click the browse button to display available data type ()
Select Loans Origination Vocabulary\Business items\Loan Application as the data type and click OK ()
The Loan Origination process output node is created ()

Reconnect to the process output

Delete the Terminal node ()
Re-connect Notify Customer to Output Node ()
Hover the mouse over Notify Customer and drag/drop the connection to the Output node.
New connection ()

Setup Processes for each Process Variation

Each process variation is created as an empty process flow with the inputs and outputs derived from the definition of the Business Service in the authoring space. Open each process and model the process for each step. Since the purpose of this guide is to illustrate how to build applications with the Fabric, we will keep these processes streamline with simple task implementations.

Open the Automated Underwriting Process (). Add a task named “Automatic Underwriting” and wire it to the input and output. Using the technical attributes view, set the implementation type for this task to Java. When exporting to WID, this will cause the task to be implemented with a java component.

Fill in the remaining process variations:

Process	Process Variation\Type\Implementation Type
Check Credit	Automated Credit Check Local Task Java
Final Review	Automated Underwriting Local Task Java Human Underwriting Local Human Task
Notify Customer	Automatic Notification Local Task Java Human Notification Local Human Task
Review Collateral	Human Collateral Review Local Human Task No Collateral Review Local Task Java

Export the project interchange file for WID

When modeling is complete we can export the project interchange file with SCA modules and libraries for further assembly in WID.

Select File\Export
Select WebSphere Business Modeler\Websphere Business Modeler Export and click Next ()
Select Webpshere Integration Developer and click Next ()
Provide a location for the export (Browse button), select Export entire project... , check all elements you want to export and click Next ()
Select the export option (Module + Library, check all the square buttons, enter Project Interchange Name (Loan Origination Application) and click Finish ()
You can ignore the warning message and click OK ().

TEN20010W: The element "Review Collateral" uses the Dynamic Assembler implementation type, which is supported only in WebSphere Business Services Fabric.
TEN20010W: The element "Notify Customer" uses the Dynamic Assembler implementation type, which is supported only in WebSphere Business Services Fabric.
TEN20010W: The element "Final Review" uses the Dynamic Assembler implementation type, which is supported only in WebSphere Business Services Fabric.
TEN20010W: The element "Check Credit" uses the Dynamic Assembler implementation type, which is supported only in WebSphere Business Services Fabric.

Import the project interchange file into WID

After exporting the elements from Websphere Business Modeler, you can then import it into WID.

In the Business Integration perspective in WID, Select File\Import. Select Other\Project Interchange option, and click Next ()
Provide the location of the zip file. Select all projects, and click Finish ()

Modify the project in WID

Here are the before () and after () modifications. To perform the modifications, proceed as follows:

Open the assembly diagram for the Loan Origination module ()

Typically, a dynamic assembly component is used in place of an import. When modeler generates the implementation for the process variations, it also puts the dynamic assembler component in that module. Imports wired off the process are linked to the export of the dynamic assembly component.

The next few steps cover how to remove this extra layer of indirection.

Delete the Check Credit import (right-click the import and select Delete)
Right-click on the Canvas and select Add\Dynamic Assembler component
Drag/drop the new component in the place where the import used to be and name it CheckCreditDA.
Re-draw the old wire from the old reference to the new CheckCreditDA Dynamic Assembler component.
The Add Wire window appears asking if you want to continue. Click OK.
Double-Click the dynamic assembler component that you just created to implement it. Click Yes when the Open window appears asking if you like to implement the component.
A "Generate Implementation" window appears asking you to select a folder. Select loanorigination and click OK.
A Dynamic Assembly Configuration Editor window appears. Select Event with full business payload as the event style, check Enable Result Caching and close the editor. Click Yes on the Save Resource pop-up window.
Open the assembly diagram for the Check Credit module and delete the dynamic assembly component and the export associated with it ()
Perform the same steps for the other three imports. This Loan Origination assembly diagram should then look something like this ()

TXSeries Installation

2010-05-29T12:16:00.001-07:00

IBM TXSeries 7.1

Install TXSeries

Installation considerations
Installing TXSeries
Creation of CICS users and groups
Environment variables created during installation

Create CICS Region

Setting up IBM TXSeries Administration Console for administrative tasks on Windows
Install Microsoft Loopback adapter
Disable Symantec Client Firewall
Create a CICS Region

Configure a CICS local terminal

Edit the CICS local terminal initialization file
Configure a Listener
Testing the setup

Install TXSeries

Installation considerations

The following topics provide you an introduction on the prerequisites, disk space requirements, directory structure, and so on, which are required for installing TXSeries for Multiplatforms.

Installing TXSeries

Select Install optional software and click TXSeries for Multiplatforms v7.1 ()
Click Browse... to locate TXSeries installation files and then click OK ()
TXSeries is being prepared for installation ()
In the TXSeries window, select English and click OK.
Review installation guide and click Next ()
Accept the terms in the license agreement and click Next.
Specify the installation directory and click Next.
Note: To avoid potential problems, install in the specified default directory (i.e C:\opt\cics)
Review Pre-Installation Summary and click Next or make changes (click Previous).
TXSeries is being installed. This may take some time ()
When Install is complete, you can check/uncheck to view/not view Readme and/or logfile. Click Next.
Click Done to quit the installer

Creation of CICS users and groups

During installation of CICS®, the following required user and groups are automatically created:

An operating system group named cics.
An operating system group named cicsterm.
An operating system group named cicssm (on AIX® only).
An operating system user named cics.
An operating system user named cicssm (on AIX only).

Many CICS procedures are accessible only when you are logged in as root. Other CICS procedures require that you are logged in as a user with root privileges. CICS also requires that the root and cics users be members of the cics and cicsterm groups.

Environment variables created during installation

During installation, the CICS® Product Setup program creates or updates these environment variables:

Create CICS Region

Before creating a CICS Region, you should set up the "IBM TXSeries Administration Console for administrative tasks on Windows" and "Install Microsoft Loopback adapter". You also have to disable Symantec client firewall if you are using it.

Setting up IBM TXSeries Administration Console for administrative tasks on Windows

On Windows, the TXSeries® light-weight infrastructure service runs as a local system account by default. If you attempt to perform tasks such as creating or destroying CICS® regions or other servers (for example, SFS servers) as a local system account, the create or destroy operation will fail.

To perform these tasks, you must first run the TXSeries light-weight infrastructure service as an administrator by completing the following steps:

In your deskstop, right-click the My Computer icon and select Manage ()
In the Computer Management window, select Services and Applications\Services, go to Standard tab, right-click TXSeried LWI... service and select Properties ()
In the TXSeries LWI... window, select the Log On tab, select This account, enter an administrator user name (i.e charles, or any other user who belongs to the Administrator group), enter Password, Confirm password, and click OK ()

Restart the TXSeries light-weight infrastructure service by right-clicking it and selecting Restart.

Install Microsoft Loopback adapter

The Microsoft Loopback adapter is a testing tool for a virtual network environment where network access is not available. Also, you must use the Loopback adapter if there are conflicts with a network adapter or with a network adapter driver. You can bind network clients, protocols, and other network configuration items to the Loopback adapter, and you can install the network adapter driver or network adapter later while retaining the network configuration information. You can also install the Loopback adapter during the unattended installation process.

To manually install the Microsoft Loopback adapter in Windows XP, follow these steps:

Click Start, and then click Control Panel.
If you are in Classic view, click Switch to Category View under Control Panel in the left pane.
Double-click Printers and Other Hardware
Under See Also in the left pane, click Add Hardware,and then click Next.
Click Yes, I have already connected the hardware, and then click Next.
At the bottom of the list, click Add a new hardware device, and then click Next.
Click Install the hardware that I manually select from a list, and then click Next.
Click Network adapters, and then click Next.
In the Manufacturer box, click Microsoft.
In the Network Adapter box, click Microsoft Loopback Adapter, and then click Next.
Click Finish.

After the adapter is installed successfully, you can manually configure its options, as with any other adapter. If the TCP/IP properties are configured to use DHCP, the adapter will eventually use an autonet address (169.254.x.x/16) because the adapter is not actually connected to any physical media.

Note By default, TCP/IP properties are configured to use DHCP.

Disable Symantec Client Firewall

If you are using Symantec Client Firewall, disable it temporarily.

Create a CICS Region

Start TXSeries Administration Console
You can start the ad console in two ways:

Enter http://localhost/txseries/admin in your web browser or
Click Start\All Programs\...\IBM TXSeries Administration tool ()

In the Login window, enter User Name and Password with Administrator privileges. click Login ()
In the TXSeries Administration Console, expand Regions, click All Regions, and click Create ()
Enter new CICS region name (i.e TestR), leave Group ID blank, select Use SFS (File Management) and click Submit ()
The CICS region and default SFS server is created ()
The CICS region and default SFS server is started ()

After creating a CICS region, edit the region environment file (c:\var\cics_regions\CICSRegion\environment) and add line: PATH=d:\systemZ\bin;%PATH%. This command tells the CICSRegion where to pick up the correct COBOL runtime environment.

Configure a CICS local terminal

Edit the CICS local terminal initialization file

cicslcli.ini (C:\opt\cics\bin ) is the CICS local terminal initialization file.

cicslcli.ini file excerpt

cicslcli.ini file excerpt
;Server = CICS01 ; Arbitrary, unique name for the server
Server = TestR ; Arbitrary, unique name for the server
Description = Named Pipe Support for local client ;
Protocol = LOCALCLI ; Matches with a Driver section below
NetName = 00.00.00.00 ; Dummy
NamedPipeName = CICSCC ; Must match servers named pipe

Change Server from CICS01 to TestR.
Remember CICSCC (NamedPipeName). You will be using this name to configure the Listerner
Close and save cicslcli.ini file

Configure a Listener

Open the TXSeries Web administration console
Expand Regions, expand the CICS region that you defined, i.e TestR, click Listener, and click Add ()
Set the Listerner Definition window as shown and click Submit ()

Listener Name = TestL
Activate resource at cold start? = Yes
Resource description = Listener Definition
Protocol Type = Named Pipe
Number of TCPIP listener processes to use = 1
local Named Pipe name = CICSCC
Click Submit

The Listener Definition is completed successfully ()
You have to re-start the CICS region to apply the changes.

Testing the setup

Make sure that you re-start the CICS region before testing the setup you did above.

From the Windows® Start menu, select All Programs > IBM > TXSeries for Multiplatforms V7.1 > Start Local Terminal. The CICSTERM - CICS server selection window opens ()
Select the correct CICS server for your CICS region and click OK ()
When the CICS terminal starts, type: CEMT and press Ctrl, which is the 3270 terminal Return key
If the transaction runs properly, the CICS terminal screen will show something like the following ()

Install

2010-05-28T15:14:00.001-07:00

Rational Developer for System z

Install Rational Developer for System z
Install TXSeries

Installation considerations
Installing TXSeries
Creation of CICS users and groups
Setting up IBM TXSeries Administration Console for administrative tasks on Windows
Environment variables created during installation
Create CICS Region
Install Microsoft Loopback adapter

Install Rational Developer for System z

In the RDzJava_Setup folder, run launchpad.exe ()
Select a language (i.e English) and click "Install Rational Developer for System Z" ()
Select Custom Installation ()
For an installation of Developer for System z, choose your user role to launch the installation with the recommended set of Developer for System z
features and bundled offerings for your role. Alternatively, you may choose to launch a custom installation with all Developer for System z features and
bundled offerings by clicking the corresponding link on the launchpad.

System z Traditional Developer Role
Developers wishing to develop or maintain on CICS or IMS applications, DB2 Stored Procedures, Batch applications, or green-screen interfaces. The developers can also gain access to IBM problem determination tools, CICS explorer interfaces, and Source Code Management systems.
Service Developer Role
Developers wanting to develop or maintain traditional workload and to expose System z applications and programs out as Web Services or Service Flows. This also includes the capabilities found in the System z Traditional Developer.
J2EE/WAS Developer Role
System z developers creating applications and Web interfaces using Java Enterprise Edition that connect to CICS, IMS, DB2, or Batch applications. This also includes the capabilities found in the Service Developer.

Select the packages you want to install and click Next ()
Accept the terms in the license agreements and click Next.
Create a new package group, set the Installation Directory and click Next ()
Leave the Extend an existing Eclipse box un-check and click Next.
Make sure the English checkbox (translation) is selected and click Next.
Select the features to install and click Next ()
For the Help System, select Access help from the Web. For WAS configuration, check Create a profile and check Enable administrative security on the profile. Use admin/admin as the User ID and Password. Click Next ()
Review the summary information. Click Back to make changes or click Install.
Installation completed successfully ()

Install TXSeries

Installation considerations

The following topics provide you an introduction on the prerequisites, disk space requirements, directory structure, and so on, which are required for installing TXSeries for Multiplatforms.

Installing TXSeries

Select Install optional software and click TXSeries for Multiplatforms v7.1 ()
Click Browse... to locate TXSeries installation files and then click OK ()
TXSeries is being prepared for installation ()
In the TXSeries window, select English and click OK.
Review installation guide and click Next ()
Accept the terms in the license agreement and click Next.
Specify the installation directory and click Next.
Note: To avoid potential problems, install in the specified default directory (i.e C:\opt\cics)
Review Pre-Installation Summary and click Next or make changes (click Previous).
TXSeries is being installed. This may take some time ()
When Install is complete, you can check/uncheck to view/not view Readme and/or logfile. Click Next.
Click Done to quit the installer

Creation of CICS users and groups

During installation of CICS®, the following required user and groups are automatically created:

An operating system group named cics.
An operating system group named cicsterm.
An operating system group named cicssm (on AIX® only).
An operating system user named cics.
An operating system user named cicssm (on AIX only).

Setting up IBM TXSeries Administration Console for administrative tasks on Windows

To perform these tasks, you must first run the TXSeries light-weight infrastructure service as an administrator by completing the following steps:

In your deskstop, right-click the My Computer icon and select Manage ()
In the Computer Management window, select Services and Applications\Services, go to Standard tab, right-click TXSeried LWI... service and select Properties ()
In the TXSeries LWI... window, select the Log On tab, select This account, enter an administrator user name (i.e charles, or any other user who belongs to the Administrator group), enter Password, Confirm password, and click OK ()

Restart the TXSeries light-weight infrastructure service by right-clicking it and selecting Restart.

Environment variables created during installation

During installation, the CICS® Product Setup program creates or updates these environment variables:

Create CICS Region

Before creating a CICS Region, you should set up the "IBM TXSeries Administration Console for administrative tasks on Windows" and install the "Microsoft Loopback Adapter"

Start Administrative Console
You can start the ad console in two ways:
Enter http://localhost/txseries/admin in your web browser or
Click Start\All Programs\...\IBM TXSeries Administration tool ()
In the Login window, enter User Name and Password. click Login ()
In the TXSeries Administration Console, expand Regions, click All Regions, and click Create ()
Enter Name and click Submit (
)

Install Microsoft Loopback adapter

To manually install the Microsoft Loopback adapter in Windows XP, follow these steps:

Click Start, and then click Control Panel.
If you are in Classic view, click Switch to Category View under Control Panel in the left pane.
Double-click Printers and Other Hardware, and then click Next.
Under See Also in the left pane, click Add Hardware,and then click Next.
Click Yes, I have already connected the hardware, and then click Next.
At the bottom of the list, click Add a new hardware device, and then click Next.
Click Install the hardware that I manually select from a list, and then click Next.
Click Network adapters, and then click Next.
In the Manufacturer box, click Microsoft.
In the Network Adapter box, click Microsoft Loopback Adapter, and then click Next.
Click Finish.

Note By default, TCP/IP properties are configured to use DHCP.

Configuring and Testing Dynamic Assembly

2010-05-16T20:09:00.001-07:00

Websphere Business Services Fabric v7.0
Contact us...

Configuring and Testing Dynamic Assembly

ProKennex

2010-05-12T17:12:00.001-07:00

ProKennex

Black Ace 98 (86 square inches headsize)

ProKennex

Black Ace 98 (86 square inches headsize)

Tennis Racquets for Sale

2010-05-12T13:56:00.001-07:00

Used tennis rackets for sale or trade

Power Or Game Improvement Racquets
Tweener Racquets
Control Or Player’s Racquets

Used tennis rackets for sale or trade

(Contact me if interested)

Power Or Game Improvement Racquets

This is the term used by racquet manufacturers for power-oriented racquets. In most cases, these racquet models feature oversize to super-oversize heads (107-135 square inches), are lightweight (8-9.5 ounces), longer (27-29 inches) stiffer and are balanced head-heavy (or evenly balanced) to retain enough weight in the hitting zone. Designed for players with shorter, slower swings and who want more power from the racquet.

Game-Improvement Racquets are usually for beginners, players with lower-level skills, and players with less mobility. These players generally have short, slow or tentative swings, and take the racquet back no more than six inches when they prepare to strike the ball. They need the racquet to provide most of the power, and the game-improvement frames provide the boost their users don’t have. How do these frames accomplish that? They have oversized prime hitting areas, or “sweet spots,” of 102-115 square inches, plus wide stiff beams measuring 27 millimeters or more at the sides, and “head heavy” balances (which means most of the weight is in the upper portion toward the head like a hammer). But these racquets’ overall weights are light (under 10.5 ounces) to counter the head-heaviness which would make them sluggish in motion.

Tweener Racquets

There are several models that offer a blend of features from game improvement and player’s racquets. They are often light-er (9.5-11 ounces), balanced anywhere from slightly head-light to slightly head-heavy, have midplus (95-102 square inches) heads and are usually extended length (27.5-28 inches). These racquet models offer low-medium to medium-high power and are most appealing to intermediate-advanced players, seeking enhanced maneuverability.

Control Or Player’s Racquets

Denotes racquets that would be used by professional and high-level club and college team players. These models are typically heavier in weight (11.5-13+ ounces), have smaller heads (85-98), thinner, more flexible beams and are balanced head light to retain maneuverability. The result is a low-power racquet, designed for players who provide their own power and prefer a racquet that offers more control. Can be standard or extended length.

Racket Name/Description	GripSize/String Pattern/Headsize/stiffness/strungW (oz)/SwingW	Reviews/Details,	Price/string/Comments
Babolat Aero Blast OS	3/8,16x19,112/65/10.20/340	Customer, Tennis.com	best offer
Bancroft Bjorn Borg	3/8,18x20,65	Customer, Tennis.com	Not for sale!!
Dunlop Max 200g	3/8,18x20,84/	customer, Tennis.com	best offer (Babolat Xcel Premium 17g)
Fischer M speed pro #1	3/8,16x19,105,56/11.80/321	customer, Tennis.com	best offer ( (Wilson NXT 16)
Head Agassi Radical LE OS	3/8,18x19,107,63/12.10/338	customer, Tennis.com	best offer ( (Head Intellitour)
Head Flexpoint 6 OS SOLD!!SOLD!!SOLD!!	3/8,16x19,112,61/9.9/337	customer , Tennis.com	best offer (Prince Premier softflex 17)
Head Flexpoint Radical OS SOLD!!SOLD!!SOLD!!	3/8,18x19,107,58/11.30/334	customer, Tennis.com	best offer ( (Multi ??)
Head Microgel Extreme Pro SOLD!!SOLD!!SOLD!!	3/8,16x19,100,69/11.70/338	customer, TW, Tennis.com	best offer ( (Technifible x1-biphase 16g)
Head Protector	3/8,16x19,86,56/14.00/???	customer, Tennis.com	best offer ( (Prince syntethic gut 16 duraflex)
Pro Kennex Black Ace 98 (old model)
Pro Kennex 5G	3/8,16x20,100,65/11.70/318	customer , Tennis.com	best offer ( (highly recommended for tennis/golfer's elbow problems)
Pro Kennex 7G	3/8,16x20,100,66/11.70/330	customer , Tennis.com	best offer (Head Intellitour) (highly recommended for tennis/golfer's elbow problems)
Pro Kennex KI-5 SOLD!!SOLD!!SOLD!!	3/8,16x20,100,61/11.80/325	customer	best offer ( (Prince syntethic gut multi 16) (highly recommended for tennis/golfer's elbow problems)
Pro Kennex KI-5 PSE	3/8,16x20,100,63,12.90,345	customer , Tennis.com	best offer (Wilson NXT 16) (highly recommended for tennis/golfer's elbow problems)
Prince 03 speedport Red	3/8,16x19,105,65/10.50/321	customer , Tennis.com	best offer (Gamma live wire 17)
Prince Graphite OS (POG)	3/8,16x19,107,63/12.20/333	customer , Tennis.com	best offer ( (Wilson Stamina 17 C,gosen proform tuff 15l m)
Prince Graphite Pro Series 90	1/2,14x18,90	customer, Tennis.com	best offer
Prince NXG Tour OS	1/4,16x19,107,63/11.90/328	customer, Tennis.com	best offer ( (Ashaway Dynamite 17)
Prince Ozone Tour	3/8,16x18,100/60/11.50/321	customer , Tennis.com	best offer (Prince syntethic gut 16 duraflex )
Volkl C10 Pro	3/8,16x19,98/63/12.20/323	customer , Tennis.com	best offer (babolat tonic\Unique Quasi-gut)
Wilson Advantage (wood)	3/8,18x20,65
Wilson Kfive OS (3)	3/8, 16x20,108/50/10.30/346	customer , Tennis.com	best offer (Head intellitour 17g)
Wilson Largehead	3/8,16x19,107/	customer, Tennis.com	best offer
Wilson Ncode 3 OS (2) SOLD!!SOLD!!SOLD!! 1	3/8,16x19,113/47/9.70/328	customer , Tennis.com	best offer

Learning Resources

2010-05-07T07:26:00.001-07:00

WebSphere Dynamic Process Edition

Learning Resources

Redbooks
Others

Tutorials

Websphere Business Services Fabric

Learning Resources

Redbooks
Others

Tutorials

Composite business applications in WebSphere Business Services Fabric
Developing adaptive composite business services using WebSphere Business Services Fabric
Use WebSphere Business Services Fabric v6.1 to Build Composite Business Services
Make composite business services adaptable with points of variability
Creating flexible service-oriented business solutions with WebSphere Business Services Fabric

IBM Websphere Business Services Fabric Related tutorials

Develop and Deploy Multi-Tenant Web-delivered Solutions using IBM middleware

WebSphere Business Modeler Advanced

Learning Resources

Redbooks
Others

Tutorials

WebSphere Integration Developer

Learning Resources

Redbooks
Others

Tutorials

Business Space

Learning Resources

Redbooks
Others

Tutorials

Websphere Business Monitor

Learning Resources

Redbooks
Others

Tutorials

Business Process Management

Learning Resources

Redbooks
Others

Tutorials

CICS Transaction Server (Mainframe)

Learning Resources

Redbooks
Others

Tutorials

TXSeries

Learning Resources

Redbooks
Others

Tutorials

Rational Application Developer for System Z

Learning Resources

Redbooks
Others

Tutorials

Rational Software Architect for Websphere

Learning Resources

Redbooks
Others

Tutorials

Others

Learning Resources

Redbooks
Others

Tutorials

WebSphere Dynamic Process Edition

Learning Resources

Redbooks

Leading Practices for WebSphere Dynamic Process Edition V6.2

Others

Tutorials

Websphere Business Services Fabric

Learning Resources

Redbooks

Getting Started with IBM WebSphere Business Services Fabric V6.1

Others

Tutorials

Composite business applications in WebSphere Business Services Fabric

Part 1: Authoring a CBA in Business Space
This article series shows you how to create a CBA in Business Space powered by WebSphere®, and then make governed changes to the application logic using Business Process Agility widgets.
Part 2: Modeling and implementing a composite business application
In Part 2 of this series, you'll learn how to enhance the model created in Part 1 in WebSphere® Business Modeler V6.2, and implement it in WebSphere Integration Developer V6.2 and WebSphere Business Services Fabric Composition Studio V6.2.

Developing adaptive composite business services using WebSphere Business Services Fabric

Part 1 Introducing IBM's new platform for business service modeling, assembly, and deployment (2007 April)
This series of articles discusses the end-to-end process of creating composite business services with IBM WebSphere Business Services Fabric Version 6.0. Part 1 introduces the idea of composite business services, and how WebSphere Business Services Fabric supports the development of these services.
Part 2: Analyzing the business requirements (2007 May)
With a conceptual understanding of composite business services from Part 1, this article looks at a sample business case to illustrate how IBM WebSphere Business Services Fabric supports the development of these services and how it can help resolve business problems.
Part 3: CBS modeling, ontology editing, and policy simulation (2007 August)
Part 3 in this series provides a step by step guide to create a Composite Business Service (CBS) model. This article covers the CBS modeling in IBM WebSphere Business Composition Studio, editing the ontology and policies definition, and using Policy Simulator to verify the assembly. Updated for IBM WebSphere Business Services Fabric V6.0.2. (IBM WebSphere Developer Technical Journal)
Part 4: Service assembly with the Dynamic Assembler SCA component (2007 August)
Continuing with composite business service modeling, ontology editing, and policy simulation from Part 3, this installment provides a step-by-step sample to demonstrate how to use the Business Services Dynamic Assembler SCA component to assemble services in the IBM WebSphere Business Services Fabric tooling environment. (IBM WebSphere Developer Technical Journal)

Use WebSphere Business Services Fabric v6.1 to Build Composite Business Services

Part 1: Overview of WebSphere Business Services Fabric v6.1 (2009 March)
IBM WebSphere Business Services Fabric is a comprehensive SOA offering that builds upon and extends IBM’s BPM platform and is designed to help companies assemble and manage composite business applications to achieve greater flexibility and business model innovation. This series of articles introduces you to WebSphere Business Services Fabric V 6.1 and shows you how to use it to build composite business services.
Part 2: Business analysis and component business services scenario (2009 March)
In Part 1 of this series, we gave an overview of, and described the new features in WebSphere Business Services Fabric (WBSF), v6.1. Now this article will introduce a small business case study to show the business problem, analyze the business requirements, and finally to provide a solution based on WBSF.
Part 3: Design and implementation (2009 May)
The first article in this series, Part 1: Overview of WebSphere Business Services Fabric v6.1, provides an overview of WebSphere Business Service Fabric 6.1. In Part 2: Scenario Introduction, Problem Statement, and Business Analysis, we introduced how WBSF can be used for a Visa Application scenario in which there is a need for dynamic service provider selection. In this third installment, we’ll detail all the steps involved in implementing the scenario in order to address the need bybuilding a Composite Business Service, using WBSF 6.1.
Part 4: Service Monitoring using Performance Manager (2009 May)
In the previous three articles of this series, we gave an overview for the WebSphere Business Service Fabric 6.1 and used business analysis to define WBSF artifacts that meet business goals. We then discussed the details of fabric development. In this final article in the series, we look at how to enable Performance Manager to enhance your fabric application to meet service monitor requirements.

Make composite business services adaptable with points of variability

Creating flexible service-oriented business solutions with WebSphere Business Services Fabric

Part 1: Overview (2008 June)
WebSphere Business Services Fabric provides an SOA platform to enable a new class of service-oriented business solutions. Business Services Fabric provides an integrated environment to model, assemble, deploy, manage and govern composite business services. This series of articles introduces you to WebSphere Business Services Fabric and shows you how to use it to build composite business services.
Part 2: Extending the ontology models (2008 June)
Learn how you can leverage the features of WebSphere Business Services Fabric to build composite business applications that support dynamic binding and orchestration. In Part 2, you'll learn how to model the variability points in the business process as ontology extensions using the Fabric Modeling Tool.
Part 3: Designing and implementing the business service (2008 September)
Learn how you can leverage the features of WebSphere Business Services Fabric to build composite business applications that support dynamic binding and orchestration. In Part 3, you'll implement a composite business process and enable it with dynamic binding and orchestration capabilities.
Part 4: Creating metadata for the business process (2008 November)
Learn how you can leverage the features of WebSphere Business Services Fabric to build composite business applications that support dynamic binding and orchestration. Part 4 of this series describes how to create metadata for a business process based on the Fabric Business Service Model. This metadata enables users to reuse and extend existing components, and enables dynamic endpoint selection at run-time.
Part 5: Testing the application (2009 February)
Learn how you can leverage the features of WebSphere Business Services Fabric to build composite business applications that support dynamic binding and orchestration. In the final article in this 5-part series you'll learn how to deploy and test the application that you've built in the previous parts of the series.

IBM Websphere Business Services Fabric Related tutorials

Develop and Deploy Multi-Tenant Web-delivered Solutions using IBM middleware

Part 1: Challenges and architectural patterns
Web-delivered solutions that follow a Software as a Service (SaaS) delivery model -- where customers subscribe to software and access it from a service provider site rather than get licenses and have software installed on their premises -- can offer compelling business value for businesses of any size. Solution developers who develop new solutions or transform existing solutions and service providers who deploy these solutions are faced with several technical challenges. One example is multitenancy, where a single instance of the software, running on a service provider's premises, serves multiple organizations. This article series describes different patterns to address these challenges, often using Service-Oriented Architecture (SOA) techniques. Also learn how IBM software products can help you build and deploy scalable, configurable, and cost-effective multitenant Web-delivered solutions.
Part 2: Approaches for enabling multi-tenancy
Part 1 of this series describes what multi-tenancy is and presents several technical challenges for building and deploying multi-tenant web-delivered solutions. In this article, we identify five representative approaches for enabling multi-tenancy in web-delivered solutions (also known as software-as-a-service) and compare their costs and benefits.
Part 3: Resource sharing, isolation and customization in the single instance multi-tenant application
This article focuses on the single shared application instance based on the multi-tenancy enablement model. It introduces the multi-tenant resources sharing, isolation and customization mechanisms of those important J2EE artifacts in such patterns. It also leverages a sample application to illustrate how to design a multi-tenant enabled J2EE application base on IBM middleware software.
Part 4: Design patterns for sharing resources in single instance multi-tenant applications
This article is the fourth in a series which addresses how to develop cost effective, secure and configurable Web deliverable applications by leveraging the multi-tenancy model. This model enables a single, shared application instance with the capability to support multiple client organizations (or tenants) simultaneously, so as to achieve the goal of cost effectiveness through sharing infrastructure and operation resource among tenants.
Part 5: A mediation approach for multi-tenancy and three implementation options
Part 1 of this series described multi-tenancy in a web-delivered business solution (a.k.a Software-as-a-Service) and Part 2 discussed the three different approaches for enabling multi-tenancy. In this article, we focus on the mediation approach for multi-tenancy first introduced in Part 2. We present three implementation options for this approach using different IBM middleware products and compare the relative benefits. The detailed implementation steps for each option will be described in the following three tutorials.
Part 6: Web service mediation proxy pattern for routing multiple tenant requests using WebSphere Business Services Fabric
Part 1 of this series describes multi-tenancy and several technical challenges faced by service providers for deploying multi-tenant web-delivered solutions. In part 5, we presented a mediation approach for addressing this challenge and introduced three implementation options using multiple IBM middleware products. In this tutorial, we describe detailed implementation steps for one of those three options i.e. how to use WebSphere Business Services Fabric in the context of a example multi-tenant banking application scenario also introduced in part 5.
Part 7: A Web service mediation proxy pattern for routing multiple tenant requests using WebSphere Enterprise Service Bus
Part 1 of this series describes multi-tenancy and several technical challenges faced by service providers for deploying multi-tenant web-delivered solutions. In part 4, we presented a technical challenge on how to enable multi-tenancy for existing single tenant Web services with little or no code changes for shorter time to market and lower costs. We presented a mediation approach for addressing this challenge andintroduced three implementation options using multiple IBM middleware products. In this tutorial, we describe detailed implementation steps for utilizing WebSphere Enterprise Services Bus for enabling multi-tenancy for existing Web services.
Part 8: A Web service mediation proxy pattern for routing of multiple tenant requests using WebSphere DataPower SOA appliance
Part 1 of this series describes multi-tenancy and several technical challenges faced by service providers for deploying multi-tenant web-delivered solutions. In part 4, we presented a technical challenge on how to enable multi-tenancy for existing single tenant web services with little or no code changes for shorter time to market and lower costs. In this tutorial we will present detailed implementations steps using a WebSphere DataPower SOA appliance in combination with Tivoli Access Manager.

Dynamic activity resequencing with WebSphere Business Services Fabric
This article describes how to use the run time dynamicity in IBM WebSphere Business Services Fabric to determine the execution order of activities within a business process. Instead of having a complex business process with a given order of activities, the article presents a solution that offers dynamic, real-time service selection rather than a fixed workflow structure. All necessary modeling and implementation steps –- in Business Space and WebSphere Integration Developer –- are explained.

Composite Business Applications in WebSphere Business Services Fabric, Part 1: Authoring a CBA in Business Space
This article series shows you how to create a CBA in Business Space powered by WebSphere, and then make governed changes to the application logic using Business Process Agility widgets.

Model business processes for flexibility and re-use: A component-oriented approach
This article describes a component-oriented approach to business process modeling that allows you to capture process variability and ensure that your model is reusable. It describes modeling patterns and practices in WebSphere Business Modeler that will help you achieve this goal.

Exploring the Enterprise Service Bus: Part 4: Federated connectivity in the enterprise
Driven by increasingly sophisticated business needs, service-oriented architectures have become more widespread, more mature and more sophisticated. A key driver of this growing sophistication is the need for multiple business units to cooperate and contribute to the overall business of the enterprise. From a business perspective, the result is generally called a federation or a federated enterprise. From an IT perspective, the enabler of a federated enterprise is often called a federated ESB, reflecting the role the ESB plays in providing service connectivity in SOA. But the ESB is just one part of an infrastructure that provides service connectivity in SOA, so it is more appropriate to discuss federated connectivity. This article describes the principles of federated connectivity and suggests an approach for creating efficient and effective federated topologies in SOA.

Customize your BPM user interfaces with business spaces
Business Space powered by WebSphere provides a unifying user interface to the products in the IBM BPM suite, based on Web 2.0 technology. This article introduces you to the capabilities, features and functions of Business Space, and shows how you can customize and extend it to fit your needs. (IBM Business Process Management Journal)

Speed CBS development using IBM WebSphere Business Services Fabric industry content packs, Part 1: Model phase
The model, assemble, deploy, manage, and governance activities of Service-Oriented Architecture (SOA) development can be time consuming and expensive when delivering new solutions from scratch. Adhering to industry standards is also challenging. This article series explains the end-to-end development of composite business services (CBSs) that leverage assets in the industry content packs of IBM WebSphere Business Services Fabric. In this first article in the series, walk through the development process in detail using a case study from the healthcare industry that involves using the IBM Healthcare Payor Content Pack. Find out how this content pack's assets accelerate the development of CBSs, thereby reducing the time to build.

WebSphere Business Services Fabric V6.1.2: Integrating with WebSphere Service Registry and Repository
WebSphere Business Services Fabric V6.1.2 now offers significant integration with WebSphere Service Registry and Repository V6.1 (WSRR). The old integration with WSRR no longer exists, as the new integration offers new ways of working with WSRR. This article describes how to use the new integration options.

Introduction to application server clustering with WebSphere Business Services Fabric
Clustered deployments are essential for growing enterprises because they enhance your ability to deliver reliable and scalable SOA solutions. This article provides an overview of how to deploy and configure WebSphere Business Services Fabric in a clustered environment.

Adding custom roles in WebSphere Business Services Fabric
Learn how you can add custom roles to the base WebSphere Business Services Fabric V6.1 Business Service Model using Rational Software Architect and the Fabric modeling tool. Once you add these roles, you can build policies and assertions around them.

Demystifying WebSphere Business Services Fabric policy evaluation and dynamic endpoint selection
Learn how the WebSphere Business Services Fabric Dynamic Assembler uses content, context and contract to dynamically select service endpoints. You'll learn how policies are used to select candidate endpoints, and how the Dynamic Assembler handles policy conflicts and policy resolution.

Using WebSphere Business Services Fabric with SEEC Web service components
Learn how you can use WebSphere Business Services Fabric in conjunction with SOA Web services provided by SEEC, Inc. using a business scenario that illustrates a customer insurance policy search followed by a policy inquiry. This article is written for architects and developers who want to understand what SEEC and similar well-written, packaged services and Business Services Fabric can do.

Integrate metadata between WebSphere Service Registry and Repository and WebSphere Business Services Fabric
This article shows you how to source service metadata from WebSphere Service Registry and Repository into WebSphere Business Services Fabric, including how to configure Business Services Fabric to enable replication of service metadata between the two products and how to use the sourced data in Business Services Fabric to assemble composite business services.

Dynamic activity resequencing with WebSphere Business Services Fabric
This article describes how to use the run time dynamicity in IBM WebSphere Business Services Fabric to determine the execution order of activities within a business process. Instead of having a complex business process with a given order of activities, the article presents a solution that offers dynamic, real-time service selection rather than a fixed workflow structure. All necessary modeling and implementation steps –- in Business Space and WebSphere Integration Developer –- are explained.

Adding custom roles in WebSphere Business Services Fabric
Learn how you can add custom roles to the base WebSphere Business Services Fabric V6.1 Business Service Model using Rational Software Architect and the Fabric modeling tool. Once you add these roles, you can build policies and assertions around them.

WebSphere Business Modeler Advanced

Learning Resources

Redbooks

Others

Tutorials

WebSphere Integration Developer

Learning Resources

Redbooks

Others

Tutorials

Business Space

Learning Resources

Redbooks

Others

Tutorials

Websphere Business Monitor

Learning Resources

Redbooks

Building Solutions with Business Space powered by WebSphere V7 (PDF)

Others

Tutorials

Business Process Management

Learning Resources

Redbooks

Building Solutions with Business Space powered by WebSphere V7 (PDF)

Others

Tutorials

CICS Transaction Server (Mainframe)

Learning Resources

Redbooks

Others

Tutorials

CA1P: Web services samples for use with CICS TS for z/OS V3

TXSeries

Learning Resources

Redbooks

Others

Tutorials

Rational Application Developer for System Z

Learning Resources

Redbooks

Installation Guide

Others

Tutorials

Using Rational Developer for System z to create a CICS COBOL Web service provider

Rational Software Architect for Websphere

Learning Resources

Redbooks

Installation Guide

Others

Tutorials

Using Rational Developer for System z to create a CICS COBOL Web service provider

Others

Learning Resources

Redbooks

Others

Tutorials

CICS Transaction Server for z/OS, V4.1 (InfoCenter)

IBM Rational Developer for System z 7.6

TXSeries V7.1 Information Center

Java Application Development for CICS

WebSphere Message Broker

IBM Enterprise Modernization Sandbox

Assembling in WebSphere Integration Developer

2010-04-22T16:38:00.001-07:00

Websphere Business Services Fabric v7.0
Contact us...

Assembling in WebSphere Integration Developer (WID)

Related links

Assembling in WebSphere Integration Developer (WID)

We will review the SCA modules created for this scenario. Instead of walking step-by-step through the definition of BPELs, services interfaces, and our mock backend service implementations, we'll start by importing a project interchange that contains several SCA modules. Then we'll walk through these modules and explain how it works. .

Importing the Loan Origination SCA Modules

Download LoanOriginationSCAModules.zip
Start WID and use a new workspace (i.e LoanOriginationPrebuilt)
In the Business Integration perspective in WID, Select File\Import. Select Other\Project Interchange option, and click Next ()
Browse to the location of the LoanOriginationSCAModules.zip file. The set of projects in the zip show up. Click Select All and then click Finish ()

Exploring the Loan Origination Assembly

This module exports the Loan Origination process and plays the role of the Business Application module. The process has one partner link for each business service that was modeled in the Fabric authoring space and these are wired to dynamic assembly components.

Open the assembly diagram for the LoanOrigination SCA module ()
At each step in the process, the dynamic assembly component is invoked. The dynamic assembler will use business policies and other configuration to dynamically select and invoke the most appropriate process variation to select for each business service. Wired before the BPEL and in between the final two dynamic assemblers are Mediation Flow Components that contain Fabric Context Extractor Mediation Primitives. These components are included in the process to provide context elements needed for evaluating policies.
Double click on the LoanOrigination process to open the BPEL editor ()

After an initial receive step, the Check Credit action invokes the check credit partner with a loan application and receives the loan application back with a credit score filled in.

The next invokes the review collateral partner with the loan application. The response is an updated loan status which is saved to the loanStatus variable. The following assign action updates the loan application with the value of loanStatus returned from the collateral review.

The final review step is similar in that the request is again a loan application and the response is an updated loanStatus.

The final action in the process invokes the notify customer partner with the loan application. The NotifyCustomer interface is modeled as a one-way operation.

Exploring the CheckCredit Assembly

The ChooseCreditCheck dynamic assembly component uses policies to dynamically bind to the most appropriate of three backend credit report services that implement the GetCreditReport interface.

Open the assembly diagram for the CheckCredit module ()
No context extraction is needed here. In this case, the necessary context will be established by the CreditCheck dynamic assembler in the loan origination process. At runtime, the necessary context elements are propagated so that they can be accessed anywhere within the automated credit check process variation.
Double-click to open the AutomatedCreditCheckProcess ()
The interface to this process takes a loan application and returns a loan application with a credit score. The process is used to create a CreditReportRequest, invoke the getCreditReport reference partner, and update the loan application with the credit score from the CreditReportResponse.
Open the assembly diagram for the BetterFinancialsBackend module ()
The BetterFinancialsBackend module provides simple mock implementations of the three backend credit services exposed via Soap/HTTP exports. To make it easier to distinguish which service is selected, each mock implementation returns a different fixed credit score. The following table shows the credit score returned by each implementation:

Table 1.

Credit Service Mock Credit Score

Trans Union 500

Experian 600

Internal Credit Check 700

Exploring the Review Collateral Assembly

This module provides implementations of two process variations for the Review Collateral business service. Although this example and others in this guide place variations in the same module, consider putting each variation in its own module. That way, a new service can be introduce or an old one modified by deploying a new or updated module for that one process variation

Open the Assembly Editor for the ReviewCollateral SCA Module ()

The No Collateral Review implementation will update the loanStatus to the INPROGRESS state if no loan status is provided.

The human collateral review launches a human task for someone to review the collateral and update the status of the loan. The human task is configured so that the work can be performed in the Business Process Choreographer.

Exploring the Final Review Assembly

This module provides implementation for the human and automated process variations for the Final Review business service. The automatic underwriting java implementation will set the loan status to APPROVED unless the loan has already been rejected or flagged for needing additional information.

Open the assembly editor for the Final Review SCA module ()

The manual underwriting human task will allow an underwriter to review the loan and determine the final status.

Exploring the Notify Customer Assembly

The Notify Customer SCA Module provides implementations for both the human and automated process variations of the Notify Customer business service.

Open the assembly diagram for the NotifyCustomer SCA module ()

The java implementation of AutomaticNotification “notifies” the customer by printing the customer name and final loan status as a system out message that will appear in the server console at runtime. The human implementation will spawn a human task so that customers can be directly contacted by a bank representative.

Defining an Application and Policies

2010-03-30T10:57:00.001-07:00

Websphere Business Services Fabric v7.0
Contact us...

Defining an Application and Policies

Pre-requisites
Creating an application
Create Policy overrides

Create an application-scoped Policy
Policy Override Semantics

Working with Changesets

Submitting a change set
Publishing a change set

Related links

Defining an Application and Policies

Applications represent the solution. In the authoring space, defining an application involves creating a simple process flow that represents the tasks, in the process in terms of existing business services. An application typically also contains policies. A policy defines the application.

Pre-requisites

Start WID
Start the server (Websphere Dynamic Process Edition Server v7.0) ().
Right-click the server and select Start.
Launch Business Space ().
After the server starts successfully, right-click the server and select Launch\Business Space.
Log-in window().
After you launch the business space, a log-in window appears. Enter your userID and password and click Login.
Space Manager window ().
In the Space Manager window, click the Loans Origination Authoring Space.

Creating an application

Create the following application using the following guide:

Application Name	Description
Loan Origination

In the Getting Started page (), click Start working with applications
In the Application Browser window, click on the “Actions” button and select “New Application” ()
In the Create New Application window, enter name and click OK()
In the Application Browser window, click on Loan Origination link in the Application Browser to open the Application details page ()
In the Application Details window, select Application Flow and then click Edit to make changes ().

Add the following channels and business services

Add channels

Click the New button to create a channel ()
Select Better Financials Online and click “OK” ()
Do Steps 1 and 2 again but this time select Customer Care Call Center. After adding the two channels, the application flow should look like this ().

Add business services

Add a Business Service to the application flow by clicking the small square button on the wire ().
Select a business service and click “OK” ().
Add the following business services in the order specified:

Check Credit
Review Collateral
Final Review
Notify Customer.

The application flow should now look like this ().

Add roles

Add roles to the services by hovering over the service square and clicking the “Add Role” button () and assigning the required role ().
You can also optionally associate a service performer or role with a given task. A policy may include a when condition that specifies a role, so that policy is only considered when a task with that role is invoked.
Business Service Role
Review Collateral Underwriter
Final Review Underwriter
Notify Customer CSR

Click “Save” to save the new application flow ().

Create Policy overrides

Create the following policy overrides using the guide below:

Policy Name	Business Service	Policy Details	Reason for Override
Credit Check Third-party override ()	Check Credit	FOR: Check Credit in this application (Loan Origination) WHEN:New Customer is equal to True THEN:Set Credit Check Type to Third-Party	New customers can't use the internal credit check because they are not applicable to new customer as this client type has no financial history with the bank. In the last chapter, a policy established that the credit check type should default to INTERNAL
Review Collateral Auto override	Review Collateral	FOR: Review Collateral in this application (Loan Origination) WHEN:Line of Business is equal to Auto Loan THEN:Select No Collateral Review in Review Collateral	The default policy establishes a client collateral review. However, the business decides that client collateral reviews are unnecessary for the auto line of business.
Final Review Override	Final Review	FOR: Final Review in this application (Loan Origination) WHEN:Amount of Loan is less or equal to 30000 OR Loan Status in (More Info Needed, Rejected) THEN:Select Automated Underwriting in Final Review	The business decides that an expensive manual underwriting can be replaced with the automated variation if the amount of the requested loan is less than $25,000. If the loan has already been rejected or flagged as needing more information, route it to the automatic variation.
Notify Customer Human override	Notify Customer	FOR: Notify Customer in this application (Loan Origination) WHEN:Loan Status is equal to More Info needed THEN:Select Human Notification in Notify Customer	Typically, the customer can automatically be notified of the status of their loan application. However, in some situations, it is determined that more information is needed to approve the loan. In that case, a customer service representative needs to get in contact with the applicant to acquire the needed information.

You may find it a requirement to create a policy to run a credit check.

New customers can't use the internal credit check because they are not applicable to new customer as this client type has no financial history with the bank.

In the last chapter, a policy established that the credit check type should default to INTERNAL. Refine that logic with a new policy as follows:

Add "Application Policies" by clicking the “add” link to the right of the “Application Policies” header ().
Enter "Credit Check Third-party override" (Name), select Check Credit (Business Service) and click “OK” ()
Edit the policy so that it looks as shown in the following figure and then click “Save” ()

For = Check Credit in this application (Loan Origination)
When = New Customer is equal to True
Then = Set Credit Check Type to Third Party

Create an application-scoped Policy

An application-scoped policy must be created next. Application-scoped policies come in two variants that are distinguished by their scoping statements.

If a policy has the statement FOR <Application> then it will apply for every step in the application flow based on the whether or not the WHEN condition is satisfied. Since this kind of policy is not specific to any business service, the results that can be added to the THEN clause are limited to setting business parameters as we did for some of our credit check policies in the last chapter.

If a policy has the statement, "FOR <Application> in <Business Service> then it will apply only in situations where the given business service is being invoked within the given application. Since this policy is specific to a business service, such policies can be used to specify a process variation to select when invoking that business service.

Policy Override Semantics

Often, it is necessary to use a policy to establish some default behavior and to have other policies that override this behavior for special circumstances. For example, we will want to override the business service policy that determines that the Final Review business service should use human underwriting.
At runtime, the system considers all policies that match given their FOR and WHEN conditions and merges the results into a single composite policy. In the end, there can be only one selected process variation and only one value assigned to any given concept. The system uses the following rules to determine which settings to use:

Settings from Application-scoped policies take precedence over settings from Business Service-scoped policies.
If two settings are both defined at the Application or Business-Service level, the priority field is used to disambiguate. The setting that comes from a policy with the largest integer priority value will take precedence.
If neither of these schemes can be used to disambiguate the value for a given setting, a policy conflict error will happen at runtime.

Working with Changesets

Once your application is complete you need to submit your changes to a change set. Once your changes have been submitted, the administrator or the user who created the change set must submit the changes.

Submitting a change set

Go to the Governance page by clicking the dropdown arrow to the left of the “Add Widgets” button and selecting “Governance” ()
Select the change set and then click the “Submit Change Set” button ()
Fill in the comment and click “OK” ()
As soon as you submit the changes, the change set moves from Draft to Pending state. Any object listed in a change set that is in Pending state is locked such that no user can change those objects until the changes are either published or rejected.

Publishing a change set

An administrator now needs to review and publish these changes.

An administrator logs in to Business Space, opens the “Loans Origination Authoring” space, and goes to the governance tab. Reviewing change sets can also be done from the administration space.
The “show” drop down in the upper right corner can toggle the view to show change sets in various states. The “Active” setting shows all change sets that have not been published or canceled.
Find the change Set and click “Approve Change Set” ()
Fill in the comment and click “OK”. The comments associated with a change set are visible under the history tab ()
Click “Publish Change set”, and then click “OK” in the dialog box that pops up (comment is already filled in) ()

Developing the Claim Status BPM solution
Understanding the Claim Status problem scenario Model phase Assemble phase Deploy phase Manage phase
1-Understanding the Claim Status problem scenario	2-Model phase	3-Assemble phase
Description Business process Key Pain Points Key Performance Indicators and Business Measures required Roles for the BPM solution	Performing gap analysis for identifying assets Searching for assets using the Asset Navigator Completing Process Decomposition Extending Insurance Process Models Modifying the Insurance Process Models Adding service tasks to the Insurance Process Models Modifying the mappings in the extended process Adding roles to the Insurance Process Model Adding or modifying Insurance KPIs and business measures Extending KPI and Business Measures Services Identification Extending Insurance Services Models Extending Insurance Common Components Creating implementation process models Importing Insurance process models from WebSphere Business Modeler to WebSphere Integration Developer Unit testing the Insurance Process implementation using WebSphere Integration Developer Creating the user interface Creating the user interface using Lotus Forms Associating a human task in WebSphere Integration Developer Model phase summary	Implementing services Implementing a service integration logic using Dynamic Assembler Importing an SCA module to create a composite service definition Unit testing services Implementing monitor models using KPI and Business Measures Modifying and exporting KPI and business measures in Monitor Models into WebSphere Business Monitor Toolkit Configuring the Process Flow to emit events Generating a monitor model Updating the generated monitor model Defining user-defined functions Defining Metrics Defining Key Performance Indicators Defining Dimensional Mode Defining the visual model Testing the monitor model Project Interchange file Implementing technical policies Creating WebSphere Business Services Fabric project and importing namespaces Implementing policies using Business Services Composition Studio Simulating and testing policies Assemble phase summary
4-Deploy phase	5-Manage Phase
Configuring the BPM solution manually Configuring the user registry in WebSphere Process Server Configuring user access in WebSphere Process Server for viewing the WebSphere Business Monitor widget Configuring dashboard alerts Configuring the Business Space dashboard Configuring Business Space themes Testing the BPM solution Verifying the widget Testing the process executions and viewing instances Verifying dashboards for KPI and metrics updates Executing the Claim Status BPM solution Updating the claims.csv file Accessing the Claim Status Business Space Accepting claim inquiry details Transferring the claim to a claim specialist Closing the claim inquiry Viewing reports Claim Status Dashboard Analysis Performance Report Viewing the Claim Status process flow Claim Status Process Claim Status Process Check Deploy phase summary

Credit Service	Mock Credit Score
Trans Union	500
Experian	600
Internal Credit Check	700

Business Service	Role
Review Collateral	Underwriter
Final Review	Underwriter
Notify Customer	CSR

Websphere Business Services Fabric Tutorials

Building an end-to-end business solution

Related links

Installing Lombardi 7.1

Performing an installation using Lombardi Installer Simple option

Verifying installation

Related links

Installing Lombardi 7.1

Performing an installation using Lombardi Installer Simple option

Verifying installation

Related links

Working with the WebSphere Insurance Content Pack

Working with the WebSphere Insurance Content Pack

Insurance Capability Models

Insurance Process Models

Insurance Service Models

Insurance Common Components

Insurance Business Vocabulary

Insurance Business Object Model

Insurance Solution Scenarios

Related Links

Developing the Claim Status BPM solution

Understanding the Claim Status problem scenario

Model phase

Assemble phase

Deploy phase

Manage phase

Related links

WebSphere Insurance Content Pack

Import Insurance Capability Models

Using the drill-down approach to identify the processes

Using the search feature to identify the processes

Moving the Solution to a new environment

Moving the Solution to a new environment

Re-creating Business Space

Related links

Changing Policies with the Business Process Agility Space

Changing Policies with the Business Process Agility Space

Editing Policies in the Agility Space

Related links

Configuring Technical Policies

Configuring Technical Policies

Set-In-Context Assertion

Matching Endpoints with Vocabulary-Based Assertions

Creating a Policy to Enable the DA (Dynamic Assembler) to Enforce Business Decisions

Related links

Configuring the Business Application Module

Configuring the Business Application Module

Map Business Services and Channels

Associate Endpoints with Process Variations

Related links

Importing SCA Modules to Create Composite Service Definitions

Importing SCA Modules to Create Composite Service Definitions

Related links

Creating Endpoints for a Credit Check Service

Creating Endpoints for a Credit Check Service

Related links

Simulate (Test) Business Service Decisions

Simulate (Test) Business Service Decisions

Testing the Choose Credit Check Decision

Submitting Changes for Approval

Related links

Implementing Context Extractors

Implementing an Initial Context Extractor

Related links

Deploying Modules to the Server

Deploying Modules to the Server

Testing Round Trips

Related links

Creating a Fabric Project

Creating a Fabric Project

Related links

Working with WebSphere Business Modeler

Working with WebSphere Business Modeler

Integrate Modeler with Fabric

Importing a Fabric application into the Modeler

Working with the Main Process Flow

Loan Origination application process flow

Setup Processes for each Process Variation

Export the project interchange file for WID