IBM Software Supporting ACORD Insurance Standards

An IBM Redbook Publication
IBM Redbook Form Number: SG24-7649-00
ISBN: 0738432431
ISBN: 9780738432434
Publication Date: 18-Mar-2009
Find Similar Download

Related People

Rufus Credle - Author [+5] [-5]
Brian Bokor - Author
Don Buddenbaum - Author
Stephanie Fetzer - Author
Bruce Wallman Ph.D. - Author
Qianq Wang - Author

Abstract

This IBM® Redbooks® publication helps you design and create demonstrations or solutions that meet ACORD insurance standards with minimal application coding. If you are not interested in creating such demonstrations yourself, we show you two and provide you with contacts to show those demonstrations.

ACORD has published and maintains insurance industry standards. The two most complete and often used standards are ACORD eForms and ACORD messaging. ACORD eForms includes hundreds of electronic forms, which can be used as-is with the IBM Lotus® Forms Viewer or modified slightly for use with the Lotus Forms Server to support straight-through processing scenarios. ACORD messaging formats can be tailored to the needs of individual insurance companies by using industry supplied tools.

This book shows you how to use IBM tools and tool content such as Lotus ACORD Forms, WebSphere® Transformation Extender ACORD Pack, and DB2® PureXML® to minimize efforts to build and maintain ACORD solutions. The solutions used in this book are available from the authors as demonstrations. This can help IBM clients understand both the value of using ACORD standards and the value of using IBM products that already incorporate these standards.

We review both developer and run-time environments. We do this to maximize the discussion potential for both open and industry standards.

The run-time environment provides a demonstration utilizing ACORD eForms (Lotus Forms) and the IBM SOA software stack to produce a seamless showcase of eForms interaction using a Workflow (BPEL) engine with Business Rules. WebSphere Business Service Fabric is also utilized to showcase how a service call can be mitigated into a business service call.

Language

English

Table of Content

Chapter 1. Overview
Chapter 2. The development environment solution
Chapter 3. User scenarios
Chapter 4. eForms + SOA Solution architectural overview
Chapter 5. eForms + SOA Solution installation and configuration
Chapter 6. eForms + SOA Solution application installation and configuration
Appendix A. Additional material

ibm.com/redbooks
IBM Software Supporting
ACORD Insurance Standards
Rufus Credle
Brian Bokor
Don Buddenbaum
Stephanie Fetzer
Bruce Wallman, Ph.D.
Qianq Wang
IBM supports ACORD standards with its
middleware
IBM capabilities demonstrate
enterprise integration and
implementation of ACORD
Standards
IBM SOA Product Portfolio
supports ACORD eForms
and Messaging
Front cover


IBM Software Supporting ACORD
Insurance Standards
March 2009
International Technical Support Organization
SG24-7649-00

© Copyright International Business Machines Corporation 2009. All rights reserved.
Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.
First Edition (March 2009)
This edition applies to ACORD eForms and ACORD messaging, Lotus ACORD Forms,
WebSphere Transformation Extender ACORD Pack, and DB2 pureXML.
Note: Before using this information and the product it supports, read the information in
“Notices” on page vii.

© Copyright IBM Corp. 2009. All rights reserved.
iii
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi
The team that wrote this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
Chapter 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 The goal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 The scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 The audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4 The solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Chapter 2. The development environment solution. . . . . . . . . . . . . . . . . . . 7
2.1 Workstation setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2 Using Lotus Forms Designer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Using WebSphere Transformation Extender ACORD Pack . . . . . . . . . . . 15
2.4 Using the DB2 9 database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.5 Summary from the Development Environment solution . . . . . . . . . . . . . . 29
Chapter 3. User scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.1 Scenario diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.2 Exercising the ACORD forms and SOA demonstration scenarios . . . . . . 35
3.2.1 Personal Inland Marine Application through Portal Channel. . . . . . . 35
3.2.2 Personal Inland Marine application through Viewer Channel. . . . . . 40
3.2.3 Business rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.2.4 Commercial Business Auto application through Portal Channel. . . . 44
3.2.5 Commercial Auto application through Viewer Channel. . . . . . . . . . . 48
Chapter 4. eForms + SOA Solution architectural overview. . . . . . . . . . . . 49
4.1 Architectural design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.1.1 Multi-channel support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.1.2 Business rule based context evaluation . . . . . . . . . . . . . . . . . . . . . . 53
4.1.3 Template based eForm population. . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.1.4 XForms Data Transformation Engine . . . . . . . . . . . . . . . . . . . . . . . . 55
4.1.5 Security considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.2 Implementation overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.2.1 ACORD Gateway Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

iv
IBM Software Supporting ACORD Insurance Standards
4.2.2 Services specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Chapter 5. eForms + SOA Solution installation and configuration . . . . . 65
5.1 Planning and scenario overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
5.1.1 Scenario overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
5.1.2 Hardware and software prerequisites. . . . . . . . . . . . . . . . . . . . . . . . 68
5.1.3 Hardware used within the ITSO eForms + SOA Solution. . . . . . . . . 70
5.1.4 Software used within the ITSO eForms + SOA Solution. . . . . . . . . . 71
5.1.5 Software installation paths and variables . . . . . . . . . . . . . . . . . . . . . 72
5.2 Install and configure the Data Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.2.1 Microsoft Windows 2003 Enterprise Server configuration . . . . . . . . 73
5.2.2 DB2 Enterprise Server Edition with pureXML configuration . . . . . . . 74
5.2.3 Tivoli Directory Server installation. . . . . . . . . . . . . . . . . . . . . . . . . . . 79
5.2.4 IBM Tivoli Directory Server configuration . . . . . . . . . . . . . . . . . . . . . 84
5.2.5 IBM WebSphere Business Service Fabric - Foundation Pack (DB only)
configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
5.3 Install and configure the Web Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
5.3.1 Microsoft Windows 2003 Enterprise Server configuration . . . . . . . . 88
5.3.2 IBM WebSphere Process Server configuration. . . . . . . . . . . . . . . . . 88
5.3.3 DB2 Runtime Client configuration. . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.3.4 IBM WebSphere Portal Server configuration . . . . . . . . . . . . . . . . . 116
5.3.5 IBM WebSphere Business Service Fabric - Foundation Pack
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
5.3.6 IBM WebSphere Business Service Fabric - Insurance P&C Pack
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
5.3.7 IBM WebSphere Transformation Extender configuration . . . . . . . . 146
5.3.8 IBM Lotus Forms Server configuration . . . . . . . . . . . . . . . . . . . . . . 146
5.3.9 IBM WebSphere Portal Server: Lotus Forms enablement . . . . . . . 151
Chapter 6. eForms + SOA Solution application installation and
configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
6.1 Database configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
6.1.1 Application database installation. . . . . . . . . . . . . . . . . . . . . . . . . . . 154
6.1.2 Set submitting URL for sample forms. . . . . . . . . . . . . . . . . . . . . . . 154
6.1.3 Import Database information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
6.2 Configuration in WebSphere Process Server . . . . . . . . . . . . . . . . . . . . . 157
6.2.1 Configuration data source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
6.2.2 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
6.3 Configuration in WebSphere Business Service Fabric . . . . . . . . . . . . . . 160
6.3.1 Import the eForm + SOA Fabric project that utilizes the P&C Content
Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
6.3.2 Further details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
6.4 Configuration in WebSphere Portal server . . . . . . . . . . . . . . . . . . . . . . . 163

Contents
v
6.4.1 Virtual Portal configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
6.4.2 WebForm Server API configuration . . . . . . . . . . . . . . . . . . . . . . . . 163
6.5 Deploy service projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
6.5.1 Deployment steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
6.5.2 ACORD projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
6.5.3 Deploy Portal projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Appendix A. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Locating the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
How to use the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
How to get IBM Redbooks publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

vi
IBM Software Supporting ACORD Insurance Standards

© Copyright IBM Corp. 2009. All rights reserved.
vii
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult
your local IBM representative for information on the products and services currently available in your area.
Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product, program, or service that
does not infringe any IBM intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document.
The furnishing of this document does not give you any license to these patents. You can send license
inquiries, in writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer
of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the program(s) described in this publication at
any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any
manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm
the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on
the capabilities of non-IBM products should be addressed to the suppliers of those products.
This information contains examples of data and reports used in daily business operations. To illustrate them
as completely as possible, the examples include the names of individuals, companies, brands, and products.
All of these names are fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating platform for which the
sample programs are written. These examples have not been thoroughly tested under all conditions. IBM,
therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

viii
IBM Software Supporting ACORD Insurance Standards
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corporation in the United States, other countries, or both. These and other IBM trademarked
terms are marked on their first occurrence in this information with the appropriate symbol (® or ™),
indicating US registered or common law trademarks owned by IBM at the time this information was
published. Such trademarks may also be registered or common law trademarks in other countries. A current
list of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml
The following terms are trademarks of the International Business Machines Corporation in the United States,
other countries, or both:
AIX®
BladeCenter®
DB2®
DB2 Connect™
DB2 Universal Database™
developerWorks®
eServer™
IBM®
Lotus®
Passport Advantage®
pureXML®
Redbooks®
Redbooks (logo) ®
System x®
Tivoli®
Transformation Server®
WebSphere®
xSeries®
z/OS®
zSeries®
The following terms are trademarks of other companies:
Snapshot, and the NetApp logo are trademarks or registered trademarks of NetApp, Inc. in the U.S. and
other countries.
Java, JavaScript, JDBC, JDK, JSP, JVM, Solaris, and all Java-based trademarks are trademarks of Sun
Microsystems, Inc. in the United States, other countries, or both.
Microsoft, Windows Server, Windows, and the Windows logo are trademarks of Microsoft Corporation in the
United States, other countries, or both.
Intel Core, Intel Core Duo, Intel Xeon, Intel, Intel logo, Intel Inside logo, and Intel Centrino logo are
trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States, other
countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
Portions of the material herein incorporate copyrighted or other proprietary material of ACORD Corporation
and include part of or is based on the ACORD Property & Casualty/Surety Standards © 1971-2008 ACORD
Corporation. All rights reserved. Used with permission.
The name ACORD and the ACORD logo are registered marks of ACORD Corporation. Any usage that
suggests expressly or by implication that anyone is allowed to use ACORD’s marks in any way to detract
from their significance is not agreed to or permitted.
The XML representations presented in this document are solely the opinions of the document's author(s)
and state, only in such author(s)’ opinions, how the ACORD Property & Casualty/Surety Standards
referenced or reproduced in this document should be implemented for the specific business processes and
solutions addressed. The rules and any interpretations thereof by the author(s) of this document in its XML
representations is neither an official nor an authoritative part of such Standards.

Notices
ix
Though the ACORD Property & Casualty/Surety Standards are licensed by ACORD for limited distribution
within this document, this document is not endorsed, sponsored, promoted or otherwise supported by
ACORD, nor shall it be deemed warranted by ACORD for technical accuracy or for the use in any process or
for any other purpose.
For official documentation on the use of the ACORD Property & Casualty/Surety Standards referenced or
reproduced in this document, refer to www.acord.org.
Any copyrighted or other proprietary material of ACORD Corporation contained in this document is provided
“AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
TO WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, ACCURACY,
COMPLETENESS, TITLE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. In no event shall
ACORD Corporation, its members, its participants or its contributors be liable for any claim, or any direct,
special, indirect or consequential damages, or any damages whatsoever resulting from loss of use, data,
profits, business revenue or goodwill or other economic loss, whether in an action of contract, tort or
otherwise, arising out of or in connection with the use or performance of, or reliance on, any copyrighted or
other proprietary material of ACORD Corporation contained in this documentation, even if ACORD
Corporation has been advised, knew or should have known of the possibility of such damages.

x
IBM Software Supporting ACORD Insurance Standards

© Copyright IBM Corp. 2009. All rights reserved.
xi
Preface
This IBM® Redbooks® publication helps you design and create demonstrations
or solutions that meet ACORD insurance standards with minimal application
coding. If you are not interested in creating such demonstrations yourself, we
show you two and provide you with contacts to show those demonstrations.
ACORD has published and maintains insurance industry standards. The two
most complete and often used standards are ACORD eForms and ACORD
messaging.
ACORD eForms are hundreds of electronic forms. There are two versions of
ACORD forms available. One of the versions is done using IBM Lotus® Forms.
The forms that are published cover general insurance processing such as new
policy information and claims notice of loss. They can be used in an isolated way
with the Lotus Forms Viewer, or they can be modified slightly for use with the
Lotus Forms Server to support straight-through processing scenarios.
Companies can create and get state approvals for their own forms. However, if
many form formats are needed, the cost is much higher than starting with the
ACORD formats.
ACORD messaging has hundreds of message types. These message types exist
in two sets of formats. The first message format was a flat file format called AL3.
ACORD transitioned the formats to XML. There are many versions of these
formats. Given the number of formats and versions that exist, a small industry
has grown up around supplying tools that help transition between data in different
ACORD messaging formats. It is important in many insurance companies to
transition ACORD messages to legacy formats, third-party message suppliers,
and forms or user interface formats. Doing this work for hundreds of formats and
many versions of some formats is a costly maintenance effort when handled by
individual insurance companies. Using industry supplied tools that already
contain the ACORD message formats saves most of these costs.
This book shows you how to use IBM tools and tool content such as Lotus
ACORD Forms, WebSphere® Transformation Extender ACORD Pack, and
DB2® pureXML® to minimize efforts to build and maintain ACORD solutions.
The solutions used in this book are available from the authors as
demonstrations. This can help IBM clients understand both the value of using
ACORD standards and the value of using IBM products that already incorporate
these standards.

xii
IBM Software Supporting ACORD Insurance Standards
We review both developer and run-time environments. We do this to maximize
the discussion potential for both open and industry standards, The run-time
environment provides a demonstration utilizing ACORD eForms (Lotus Forms)
and the IBM SOA software stack to produce a seamless showcase of eForms
interaction using a Workflow (BPEL) engine with Business Rules. WebSphere
Business Service Fabric is also utilized to showcase how a service call can be
mitigated into a business service call.
The team that wrote this book
This book was produced by a team of specialists from around the world working
at the International Technical Support Organization, Raleigh Center.
Rufus Credle is a Certified Consulting IT Specialist at the ITSO, Raleigh Center.
In his role as Project Leader, he conducts residencies and develops IBM
Redbooks publications about network operating systems, ERP solutions, voice
technology, high availability and clustering solutions, Web application servers,
pervasive computing, IBM and OEM e-business applications, IBM System x®,
IBM x-Series, and IBM BladeCenter®. Rufus’ various positions during his IBM
career have included assignments in administration and asset management,
systems engineering, sales and marketing, and IT services. He holds a BS
degree in business management from Saint Augustine's College. Rufus has
been employed at IBM for 28 years.
Brian Bokor is a Senior Software Engineer and Emerging Standards leader, in
Research Triangle Park, NC USA, focusing on service-oriented architecture
(SOA), Web 2.0, team leadership, I/T architecture, and Web development. Brian
drives the adoption of Open Technical and Industry Standards, focusing on the
Insurance Industry, to provide a robust layer of service interfaces and business
objects for industry consumption. Brian currently works on driving SOA adoption
within the NAVA community by transforming STP into a Future State of
technologies. Brian started his career with IBM in 1999 with Global Business
Services immersed in various customer engagements which grew into many
different job roles. As a technical team leader, he successfully drove his team to
develop, implement, and deploy a worldwide educational project, Reinventing
Education. Brian's technical knowledge led him to the Emerging Standards team,
where he aids in the development of industry and technical standards, which
long has been a passion in his work. He has filed 28 patents and has five
publications. Brian holds a Bachelor of Science in Information Science degree
from Robert Morris University, in Pittsburgh, PA.

Preface
xiii
Don Buddenbaum is a Sr. Software Engineer, based in Raleigh, NC USA. Don
is currently the IBM Software Group service-oriented architecture (SOA) play
lead for the insurance industry, responsible for driving SOA growth by leveraging
emerging standards within vertical-industry standards organizations. Don has
over 20 years of varied experience in the life industry and the vendor community
including consulting, systems development, and operations. In 1996, Don joined
IBM as the lead architect charged with driving the modernization of IBM life
insurance application software offerings within the Insurance Industry Software
Unit. He has helped IBM leverage middleware as the basis for financial service
solutions. During this time, Don served as the Chief Architect for the IBM
Software Group Insurance Solutions, participated on the Financial Services
Architecture Board, contributes to IBM Academy studies and IBM Software
Group Architecture Board initiatives, participates in industry standards initiatives
such as NAVA and ACORD, has filed numerous patents, and publishes articles
related to technology and insurance. Prior to IBM, Don designed and
implemented solutions in the life insurance industry.
Stephanie Fetzer is a Software Engineer in Charlotte, NC USA. She has 22
years experience in data processing including 10 years working with the
WebSphere Transformation Extender product. Her area of expertise includes
data transformation and mapping primarily in the Healthcare and Insurance
industries. She holds a degree in Business Administration from the Pennsylvania
State University.
Bruce Wallman, Ph.D. is an Executive IT Architect in the United States. He has
over 30 years experience in information technology, much of it in the Insurance
Industry. Bruce holds a Bachelor of Science in Industrial Engineering from
Columbia University and a Ph.D. in Conflict Analysis/Organizational Modeling
from the University of Pennsylvania. He holds a patent System and Method for
Eliminating Viruses at a Web Page Server and published a developerWorks®
article last year Using WebSphere Business Services Fabric with SEEC (now
part of Polaris SWL) Web Service Components.
Qianq Wang is the technical leader of the SOA Standards Growth team in IBM
China Software Development Lab where he has worked for over four years. His
department is focused on service oriented architecture (SOA) and Industry
standards related projects. Qiang leads the Insurance standards related projects.
His team works closely with different IBM insurance solution teams. Prior to the
SOA Standards Growth team, he worked in the China SOA Design Center.
Qiang has worked as major developer, designer, architect, and project manager
on various projects. Qiang has a great passion for technology and project
management. He is a Project Management Professional (PMP) certified by
Project Management Institute (PMI) and an Enterprise Architect certified by SUN.
He has published over 20 articles on IBM developerWorks China and US and he
holds a Masters degree in Computer Science from Beijing Jiaotong University, in
Beijing, China.

xiv
IBM Software Supporting ACORD Insurance Standards
Thanks to the following people for their contributions to this project:
Tamikia Barrows, Carla Sadtler, Linda Robinson
International Technical Support Organization, Raleigh Center
Become a published author
Join us for a two- to six-week residency program! Help write a book dealing with
specific products or solutions, while getting hands-on experience with
leading-edge technologies. You will have the opportunity to team with IBM
technical professionals, Business Partners, and Clients.
Your efforts will help increase product acceptance and customer satisfaction. As
a bonus, you will develop a network of contacts in IBM development labs, and
increase your productivity and marketability.
Find out more about the residency program, browse the residency index, and
apply online at:
ibm.com/redbooks/residencies.html
Comments welcome
Your comments are important to us!
We want our books to be as helpful as possible. Send us your comments about
this book or other IBM Redbooks publications in one of the following ways:
Use the online Contact us review IBM Redbooks publications form, found at:
ibm.com/redbooks
Send your comments in an e-mail to:
redbooks@us.ibm.com
Mail your comments to:
IBM Corporation, International Technical Support Organization
Dept. HYTD Mail Station P099
2455 South Road
Poughkeepsie, NY 12601-5400

© Copyright IBM Corp. 2009. All rights reserved.
1
Chapter 1.
Overview
The goal of this book is to showcase IBM software supporting ACORD Insurance
standards. It is depicted by two demonstrations, one being a localized
development environment demonstration, and another being an eForms + SOA
Enterprise Solution demonstration. Both of these scenarios are important in the
implementation of a different context of the ACORD standards. It allows for the
leverage of the ACORD standards, utilizing electronic forms and service-oriented
architecture (SOA) best practices, in how to develop, create, implement, and
realize the advantages of IBM software in a flexible, reusable way.
1

2
IBM Software Supporting ACORD Insurance Standards
1.1 The goal
ACORD maintains the most successful insurance B2B messaging and forms
standards worldwide. It is the most successful insurance standards organization
in the United States and is making some inroads in Europe and Asia Pacific.
IBM has several products that contain ACORD content. These include Lotus
Forms (ACORD eForms), the WebSphere Transformation Extender (WTX)
ACORD Pack, DB2 9 pureXML templates, and the WebSphere Business
Services Fabric (WBSF) Property & Casualty (P&C) Content Pack. The IBM
Insurance Application Architecture/Insurance Information Warehouse (IAA/IIW)
models are also interoperable with the ACORD messaging and form standards.
The goal of this book is to showcase the IBM products that are used directly with
the ACORD standards. Our intention is to raise awareness of both the existing
ACORD insurance standards, and the ability of IBM products to consume these
standards.
1.2 The scope
The scope of this book is limited to published ACORD standards and generally
available IBM products supporting those standards as of late 2008; so we do not
describe standards that “might” get published or tools that “might” be able to
support future standards.
The published ACORD standards considered in this document that use IBM
products are:
Life and Annuity messaging XML
Property & Casualty/Surety messaging XML
ACORD eForms

Chapter 1. Overview
3
1.3 The audience
The audience for this book is people who want to understand the enterprise
capabilities that IBM provides for ACORD standards. This includes insurance
industry business decision-makers, architects, and developers.
The early parts of this book can be read by anyone interested in the ACORD
standards and the IBM adoption of such standards. The latter parts of the book
go into details about demonstrations that IBM has built in support for ACORD
standards and are targeted to architects and developers.
1.4 The solutions
There are two IBM ACORD solutions that we describe in this book. These
solutions cover a simple developer workstation and a full-fledged eForms + SOA
Solution integration scenario. The focus of the developer workstation
environment is purposefully narrow enough so that the environment can run on
Windows® notebooks and be transported on a VMWare image. This
environment is described in Chapter 2, “The development environment solution”
on page 7.
The eForms + SOA solution, described in Chapter 3, “User scenarios” on
page 31 through Chapter 6, “eForms + SOA Solution application installation and
configuration” on page 153, is much more robust than the one in Chapter 2, “The
development environment solution” . In the case of the eForms + SOA solution,
our goal is to show the value of IBM SOA components beyond the narrow scope
of ACORD content.

4
IBM Software Supporting ACORD Insurance Standards
The first solution is a developer workstation showing IBM Lotus ACORD Forms
supporting data input flowing into WebSphere Transformation Extender ACORD
Pack. WTX provides data conversion from the form data model into an ACORD
XML data structure for storage into a DB2 9 pureXML table. The left-hand side of
Figure 1-1 shows a high-level view of the components in this demonstration.
Figure 1-1 IBM ACORD Solutions Flow diagram
IBM ACORD Solutions Flow
Demo in light blue
HTTP/HTML
ACORD XML
XQuery
ACORD XML
Internal
Format
Queries
IVANS
®
TransactNOW
®
ACORD XML
Flow
DB2 PureXML
ACORD
Transactions
IAA/IIW or other
Legacy
Processing
WTX ACORD Pack
Transformation
WTX ACORD Pack
Transformation
ACORD Forms
UI

Chapter 1. Overview
5
The second solution uses ACORD forms in the context of a service-oriented
architecture built for production. The production workstation (Figure 1-2) shows
IBM Lotus ACORD Forms from either the stand alone viewer or as portlets in
WebSphere Portal flowing through a business process in WebSphere Process
Server. WebSphere Fabric is used to dynamically invoke services depending on
the form context such that a set of services and business rules are invoked
against the form data. Upon successful completion of the services and rules, the
WebSphere Transformation Extender ACORD Pack provides data conversion
from the form data model into an ACORD XML data structure for storage into a
DB2 9 pureXML table.
Figure 1-2 ACORD Forms run-time Business Process diagram
The eForms + SOA solution is a set of servers depicted as the Web Node and
the Data Node, showing the integration and collection of IBM products to build
out a Proof of Concept. The goal of the Proof of Concept is to show the
integration of ACORD standards into an IBM SOA Infrastructure that can allow
real business value to be obtained.
ACORD Form UI
Viewer Based
ACORD Form UI
WebSphere
Portal Based
ACORD Forms
Business Process
ACORD
Transformation
Pack
WebSphere Fabric
Services/Rules
&
PCS Content Pack
DB2 PureXML
ACORD Transaction
&
Form Component
Storage
LDAP
Authentication/
Authorization

6
IBM Software Supporting ACORD Insurance Standards
The key elements of the Forms + SOA solution are as follows:
Web Portal - WebSphere Portal Server: This product was used for displaying
widgets of content, more specifically the integration of ACORD eForms.
Automatic Service Routing, Discovery, and Mediation: WebSphere Business
Service Fabric was used to allow Web Services to be organized by Business
Function or Business Services and to attach metadata to allow for the
automatic nature that the WBSF product allows.
Workflow Management: WebSphere Process Server was utilized to allow
forms to engage a BPEL/Workflow Process from a service call embedded into
the form. This allows for loose coupling of Processes from forms.
Rule Engine: WebSphere Process Server comes with a minimal Business
Rules engine for easy interaction. The rules engine was used to provide extra
capabilities outside of the eForms data and to attach extra data, questions,
and error routines, allowing for more robust form validation. This enables the
flexibility of these rules to be approved by an outside body or implementer
without having the rules standardized, allowing business flexibility.
XML Transformation: WebSphere Transformation Extender: This product was
designed to manipulate and modify ACORD XML and XML Schemas to a
format required by an enterprise. The product showcases the need for
integration with existing Data Structures that exist within a current
infrastructure and the ease of mapping and transforming data.
XML Storage: DB2 pureXML allows for storage of the XML content
represented by an ACORD eForms to be directly stored with the content
entered on the form straight into the database. This enables easy formatting
and data retrieval without having to rely on an ever changing data model.
One of the key reasons for the eForms + SOA Solution was to prove out the
integration of ACORD standards and their ability to be implemented within a
Stack of core SOA business capabilities that are needed for moving forward to a
future state
. The software that was utilized for the eForms + SOA Solution had
major components within the IBM SOA software stack to showcase the effective
integration and adoption of open and Industry standards as well as the loose
coupling of each core business function, being performed to gain maximum
business value and maximum maintainability. This concept allows for the
flexibility of updates and changes from ACORD or other outside standards
bodies, vendors, or legal entities without having sustained impacts to the
software stack.
In the eForms + SOA Solution sections, this book shows you the architecture,
and how to install and configure this environment as well as the benefits that
these IBM software components can provide to each part of the business. That
section also showcases how to effectively take the ACORD standards and
merge them into an open, discoverable, and flexible environment.

© Copyright IBM Corp. 2009. All rights reserved.
7
Chapter 2.
The development
environment solution
In this chapter, we show the IBM ACORD development environment solution as
a developer workstation in order to provide a simple and quickly executable
demonstration of straight through processing from an ACORD Form to back-end
database activity.
This relatively small demonstration is transportable across notebook computers
on a VMWare image. The core products are Lotus ACORD Forms, WebSphere
Transformation Extender (WTX) with the WebSphere Transformation Extender
ACORD Pack, and DB2 9 pureXML.
2

8
IBM Software Supporting ACORD Insurance Standards
2.1 Workstation setup
The content of a developer workstation is shown in light blue (Figure 2-1), with
related run-time servers and content that are not within this demonstration shown
in grey.
Figure 2-1 IBM ACORD Solutions as subset of potential production implementation
The developer workstation starts with Lotus Forms and an ACORD form. The
demonstration uses ACORD form 2 - Automobile Loss Notice. Fields are entered
into this form and saved using a Save link as a standard HTTP message.
IAA/IIW
Insurance
Models
Demo in light blue
WTX
Designer
WAS Fabric WPS Portal MQ
WTX ACORD Pack
DB2
Command
Line
Informal DB2 examples
Forms
WTX
DB2 9
IBM Servers
Forms
Designer
and Viewer
Fabric
Composition
Studio
IBM Designers
and content
ACORD eForms
WBSF P&C Content Pack
Application Architecture

Chapter 2. The development environment solution
9
The demonstration follows these steps:
1.Enter data into the Automobile Loss Notice, making sure to change the Agent
and a Policy ID, select Save at the top of the form, and save the file as HTM.
2.Run the transformation from the HTTP file to ACORD XML in WTX Designer
with the WTX ACORD Pack. Designer writes a record to a DB2 XML table
using a macro.
3.Run an XQuery in the DB2 Command Line Editor to display the new record.
After being installed and set up, this demonstration can be shown and
understood in under a minute. It is most appropriate for use in a booth
environment and has been used at multiple ACORD shows.
Installation of the main three products used in the demonstration was done on a
Windows VMWare image. Lotus Forms Designer 3.0, WebSphere
Transformation Extender (WTX) Designer 8.2 (including the WTX ACORD
Pack), and DB2 9.5 were all installed on this image using default set-ups.
Figure 2-2 shows the parameters used in the VMWare image.
Figure 2-2 ACORD VM Demo
IBMers can get a copy of a VMWare image (for VMWare licensed IBM users)
from bruce.wallman@us.ibm.com. Most of the files used by Lotus Forms,
WebSphere Transformation Extender, and DB2 in the demonstration cannot be
printed, and the VMWare image is the simplest way to transport the working
demonstration.

10
IBM Software Supporting ACORD Insurance Standards
2.2 Using Lotus Forms Designer
Lotus Forms Designer has three modes: Designer, Source, and Viewer. The
Viewer mode is used to see the form as a user would see it. It can also be used
for the entry of test data. A disadvantage when entering the Viewer mode is that
Forms clears the data fields. Thus it is not possible to re-enter the Viewer mode
with prior data already loaded. The way to overcome this disadvantage for
demonstration purposes is to run the demonstration from a Virtual Machine. A
VMWare Snapshot™ is saved with data in the Viewer mode and, upon reloading
this image, the Viewer shows the prior data.
The ACORD Automobile Loss Notice looks similar to Figure 2-3 in the Lotus
Forms Viewer mode.
Figure 2-3 ACORD Form. Courtesy of ACORD Corporation. Reprinted with permission.
When running a demonstration, we suggest that the Agency Name (Agency 129
in Figure 2-4) and the Policy Number (PRE123456129 in the example) are
changed before each Save. This provides unique records easily searched by the
DB2 XQuery.

Chapter 2. The development environment solution
11
Figure 2-4 ACORD Form development. Courtesy of ACORD Corporation. Reprinted with permission.
Example 2-1 is a small sample of the source for the ACORD Loss Notice form.
Example 2-1 ACORD Loss Notice form - sample of source
<?xml version="1.0" encoding="UTF-8"?>
<XFDL xmlns:custom="http://www.ibm.com/xmlns/prod/XFDL/Custom"
xmlns:designer="http://www.ibm.com/xmlns/prod/workplace/forms/designer/2.6"
xmlns:pecs="http://www.PureEdge.com/XFDL/PECustomerService"
xmlns:xfdl="http://www.ibm.com/xmlns/prod/XFDL/7.5"
xmlns="http://www.ibm.com/xmlns/prod/XFDL/7.5">
<globalpage sid="global">
<global sid="global">
<custom:publisher>PureEdge</custom:publisher>
<designer:date>4/12/2003</designer:date>
<formid>
<serialnumber>76B9AA27-47C7-48B5-B040-D177ABEE46D6</serialnumber>
<version>9.55.6</version>
<title>ACORD 2 (2005/06)</title>
</formid>
<custom:setHelp xfdl:compute="&#xA;

12
IBM Software Supporting ACORD Insurance Standards
toggle(activated,'off','on') == '1' ? ((viewer.getHelpMode() == 'off') &#xA;
? viewer.setHelpMode('on') &#xA;
: viewer.setHelpMode('off') &#xA;
) &#xA;
: ''"></custom:setHelp>
<custom:setHelpOnPrint xfdl:compute="&#xA;
toggle(activated,'on','off') == '1' ? ((viewer.getHelpMode() == 'off') &#xA;
? viewer.setHelpMode('on') &#xA;
: viewer.setHelpMode('off') &#xA;
) &#xA;
: ''"></custom:setHelpOnPrint>
<custom:attachment_filename>2.XFD</custom:attachment_filename>
<custom:on_formLoad xfdl:compute="&#xA;
(toggle(activated, 'off', 'on') == '1') &#xA;
? ((viewer.getDefaultFilename() != '') &#xA;
? set('custom:attachment_filename', viewer.getDefaultFilename()) &#xA;
: viewer.setDefaultFilename(custom:attachment_filename) &#xA;
) &#xA;
: ''"></custom:on_formLoad>
<fontinfo>
<fontname>Times New Roman</fontname>
<size>10</size>
<effect>plain</effect>
</fontinfo>
<printsettings>
<border>off</border>
<dialog>
<printpages>
<active>on</active>
</printpages>
</dialog>
</printsettings>
<xmlmodel xmlns:xforms="http://www.w3.org/2003/xforms">

Chapter 2. The development environment solution
13
<instances>
<xforms:instance xmlns="http://www.ibm.com/xmlns/prod/XFDL/Custom">
<DEFAULT_MAP>
<PAGE1>
<CB1>off</CB1>
<CB2>off</CB2>
<CHECK3>off</CHECK3>
<AGENCY_CUSTOMER_ID></AGENCY_CUSTOMER_ID>
<FIELD9></FIELD9>
<FIELD10></FIELD10>
<SINGLE_LIMIT></SINGLE_LIMIT>
<MEDICAL_PAYMENT></MEDICAL_PAYMENT>
<OTC_DEDUCTIBLE></OTC_DEDUCTIBLE>
<ref>[custom:DEFAULT_MAP][custom:PAGE1][custom:CHECK3]</ref>
<boundoption>PAGE1.CHECK3.value</boundoption>
</bind>
<bind>
<ref>[custom:DEFAULT_MAP][custom:PAGE1][custom:HTMLoutputfields]</ref>
<boundoption>PAGE1.HTMLoutputfields.value</boundoption>
</bind>
</bindings>
<submissions></submissions>
</xmlmodel>
<designer:version>3.0.0.130</designer:version>
<saveformat>application/x-www-form-urlencoded</saveformat>
<ufv_settings>
<pagedonewithformaterrors>permit</pagedonewithformaterrors>
</ufv_settings>
</global>
</globalpage>
</page>
</XFDL>

14
IBM Software Supporting ACORD Insurance Standards
The last step in the Forms portion of the demonstration is to save the output.
A necessary change to the source file available from ACORD is to use this save
format:
<type>saveas</type>
<saveformat>application/x-www-form-urlencoded</saveformat>
This statement forces the output to be HTTP rather than the Forms XFDL
default. XFDL cannot be transformed, whereas HTTP can be. This change is
already in place on the VMWare image.
When the Save is selected, a Save dialog appears as in Figure 2-5. The file
name should use an HTM extension. In this example, it was Agency123.htm. The
first tim, the file name must be entered and placed in a known directory. This is
used when the file is read by WebSphere Transformation Extender. If a VMWare
snapshot is used, the file name remains in place each time the Save is selected.
When the Save button is selected in the Save dialog, an
Already Exists
dialog
might appear. Saving over the prior name is the easiest way to run the
demonstration.
The standard HTTP (.HTM) file that is saved looks like this:
HTMLoutputfields=Start&DATE=05%2F05%2F2008&FIELD1=NAIC555555&EF2=Age
ncy+129&POLICY_NUMBER=PRE123456129&
Fields are listed by internal form name, data contained, and & delimiter.
Figure 2-5 ACORD Save Form diagram. Courtesy of ACORD Corporation. Reprinted
with permission.

Chapter 2. The development environment solution
15
2.3 Using WebSphere Transformation Extender ACORD
Pack
This HTTP message from WTX Designer 8.2 must be translated into an ACORD
XML standard message. In the demonstration, WTX Designer saves the
transformed message directly into a DB2 9.5 XML field in a new record.
After the ACORD Lotus Form data has been saved as HTM, the WTX type trees
and map are needed. The side by side type trees inside WTX Designer look
similar to those in Figure 2-6.
Figure 2-6 ACORD XML Mapping Development
In Figure 2-6, the type tree on the left side is the First Notice of Loss file saved
from the Forms Viewer Save. The type tree on the right side describes the
ACORD XML message for a loss that comes from the WTX ACORD Pack. This
is a large and complex format that does not need to be coded if the WTX ACORD
Pack is purchased. Again, the WTX input files are too complex to reproduce in
print.

16
IBM Software Supporting ACORD Insurance Standards
The first time that the saved file name from Lotus Forms is brought into WTX, a
new map must be built. This is done with the Build Map button in WTX. The Run
Map button is used to do the transformation from HTTP to ACORD XML data
and to place the record into the DB2 9 database. If the same file name is reused
for subsequent inputs, then running Build Map is not necessary.
The file name to be read is entered into WTX. Selecting the 1# form and
right-clicking yields the following pop-up as shown in Figure 2-7.
Figure 2-7 ACORD XML Mapping menu
Selecting Edit from this pop-up yields the dialog in Figure 2-8.

Chapter 2. The development environment solution
17
Figure 2-8 ACORD XML Edit Input Card (form)
Selecting the GET FilePath changes the FilePath to an editable field with a "…"
in Figure 2-9.
Figure 2-9 Edit FilePath

18
IBM Software Supporting ACORD Insurance Standards
Selecting the "…" creates another dialog that allows changing the path by
selecting its "…" as in Figure 2-10.
Figure 2-10 Selecting Agency123.htm file
When a new file path and name are entered, the Build Map button is clicked.
This creates a short-lasting dialog that shows the map from FNOL to
ACORD_PCS being built. Again, if using a VMWare image, this process of
creating a new map is bypassed by not reloading WTX and reusing the same file
name each time a file record is Saved from Lotus Forms.
When the map is available, the Run Map button is clicked, yielding the
Command Server dialog in Figure 2-11.

Chapter 2. The development environment solution
19
Figure 2-11 Run Map Example on the Command Server
This dialog is closed by selecting the X in the upper-right corner. Run Map
creates a new record in the DB2 database.
The original WTX ACORD Pack demonstration map (Figure 2-12) was a
transformation from the HTML format of Lotus Forms to the ACORD PCS XML
structure on output card 1. It wrote the XML instance document as a file. We
changed the map to instead write a row containing the XML as pureXML to a
database. In WTX, there are multiple ways to do this. The DBLOOKUP (map
rule) approach worked well.
A second map output card was added specifically for handling the database
work. The tree that was created for this output card was step-based. It is used to
orchestrate a series of commands (or calls), but not used to create actual output.

20
IBM Software Supporting ACORD Insurance Standards
Figure 2-12 Tree view from Output Map
Each step in the tree has several optional components to make the call
construction as simple as possible. In WTX, it is easier to manipulate things in
small pieces and combine them, than it is to manipulate multi-part instructions.
The DB2 call is the last component of each step to create the call detailed next.
There are two database
steps
for this demonstration. The first is to look up the
last CID used in the table. This is SELECT MAX(Cid) FROM ACORD__DEMO.
The Cid column was used because we needed a unique value to utilize.
In Step 1, we get the Cid and add one to it. In Step 2, we use that Cid of the new
row that we add. The following map rules are used.

Chapter 2. The development environment solution
21
For Step 1:
Param[1] ="SELECT MAX(Cid) FROM ACORD__DEMO"
- The table name is ACORD__DEMO and the column we are looking for is
Cid
Param[2]= "-DBTYPE DB2 -SOURCE SAMPLE -T trace.mtr"
- The database name is SAMPLE and it is a DB2 database and we have
trace set
Call=NUMBERTOTEXT ( TEXTTONUMBER ( VALID (DBLOOKUP ( Param [1]:STEP
[1]:DATABASE , Param [2]:STEP [1]:DATABASE ) ,
FAIL ( "ERROR: "+LASTERRORCODE ( )+"-"+LASTERRORMSG ( ))) )+1)
The call executes the SQL (gets highest Cid in the table) and adds one to it.
The call also transforms Cid to a numeric so that it can perform math on it,
then switches it back to text so that it can be used as text later on.
For Step 2:
Param[1]= "INSERT INTO ACORD__DEMO (Cid,Info) VALUES ("+Call:STEP
[1]:DATABASE+",<<27>>"+TEXT(ACORD_PCS_XML)+"<<27>>)"
The Table name is ACORD__DEMO.
We are populating both Cid and Info.
Call from step one is used for the Cid value.
Info is the actual XML.
It is set to the value in ACORD_PCS_XML, which is the result of the
transformation map output card one.
ACORD_PCS_XML is simple the name of output card one of this map.
Single quotes replaced with <<27>> keep from confusing the map designer
into thinking that we are ending the rule.

22
IBM Software Supporting ACORD Insurance Standards
Param[2]= "-DBTYPE DB2 -SOURCE SAMPLE -T trace.mtr"
The database name is SAMPLE, it is a DB2 database, and we are using
trace.
Call=VALID (DBLOOKUP ( Param [1]:STEP [2]:DATABASE , Param [2]:STEP
[2]:DATABASE ) , FAIL ( "ERROR: "+LASTERRORCODE ( )+"-"+LASTERRORMSG (
)))
When the map is run, the first output card creates the transformed XML.
The second output card then goes to the table and gets the next Cid.
We then put the new Cid and the XML into the table. See Figure 2-13.
Figure 2-13 Transformed XML Tree view

Chapter 2. The development environment solution
23
2.4 Using the DB2 9 database
The DB2 9 database requires database and table definitions before starting. For
the demonstration, the DB2 9 Sample database was used to house a new table
called ACORD__DEMO (two underscores after ACORD). This was done by
using the Create New Table wizard in the DB2 Control Center as in Figure 2-14.
Figure 2-14 DB2 9 Control Center view

24
IBM Software Supporting ACORD Insurance Standards
The following characteristics were used (Figure 2-15).
Figure 2-15 DB2 9 Control Center ACORD_DEMO Table view
The two fields in the demonstration are
CID
as a unique key incrementing each
time a record is written and
INFO
as an XML field. This XML field contains each
ACORD XML schema written by WTX.

Chapter 2. The development environment solution
25
When records have been written by WTX, then opening the ACORD__DEMO
table provides a dialog showing its records or rows as in Figure 2-16.
Figure 2-16 DB2 9 Table View of ACORD_DEMO

26
IBM Software Supporting ACORD Insurance Standards
Selecting the "…" by any row provides entry into that row and displays a window
similar to Figure 2-17.
Figure 2-17 DB2 9 XML Viewer
Selecting Expand All and scrolling shows the main Agency (Producer - Addr1)
and Policy Number fields (Figure 2-18) in the record.

Chapter 2. The development environment solution
27
Figure 2-18 DB2 9 XML Viewer Tree View example
The DB2 Command Editor is used with a DB2 XQuery to display this or prior
records added to the database.
A sample XQuery used in the demonstration is:
Connect To sample;
XQUERY for $data in db2-fn:xmlcolumn('ACORD DEMO 1
VM.ACORD__DEMO.INFO')
where $data/ACORD//Producer//Addr/Addr1[text()="Agency_129"]
return
<result>
<Producer>{$data/ACORD//Producer//Addr/Addr1}</Producer>
<PolicyNumber>{$data/ACORD//Policy/PolicyNumber}</PolicyNumber>
<LossDate>{$data/ACORD//Policy/Loss/LossDt}</LossDate>
</result>;

28
IBM Software Supporting ACORD Insurance Standards
The Command pasted into the DB2 Command Editor looks like Figure 2-19.
Figure 2-19 DB2 9 Command Window view
Clicking the Execute button displays the results as shown in Figure 2-20.
Figure 2-20 DB2 9 Results view

Chapter 2. The development environment solution
29
2.5 Summary from the Development Environment
solution
The purpose of this solution was to show a quick, straight through process of
ACORD Forms data hitting a database in a format usable by back-end systems.
We succeeded in reaching that goal and, as mentioned before, have shown this
demonstration at multiple ACORD conference booths. A production
implementation is always more complex than a demonstration. For example,
we did not handle any error conditions, which would be a big part of handling
key-entered data. Figure 2-21 shows the Development Environment solution
demonstration surrounded by all the servers and other IBM content that might be
part of a production implementation.
Figure 2-21 Other potential tools and content in an IBM ACORD production implementation
IAA/IIW
Insurance
Models
Demo in light blue
WTX
Designer
WAS Fabric WPS Portal MQ
WTX ACORD Pack
DB2
Command
Line
Informal DB2 examples
Forms
WTX
DB2 9
IBM Servers
Forms
Designer
and Viewer
Fabric
Composition
Studio
IBM Designers
and content
ACORD eForms
WBSF P&C Content Pack
Application Architecture

30
IBM Software Supporting ACORD Insurance Standards

© Copyright IBM Corp. 2009. All rights reserved.
31
Chapter 3.
User scenarios
This section describes the online scenario for the ITSO working example of IBM
software supporting the ACORD Standards runtime environment, and provides
information regarding signing on and navigating the available windows as a part
of the demonstration scenarios.
3

32
IBM Software Supporting ACORD Insurance Standards
3.1 Scenario diagram
Figure 3-1 illustrates several possible demonstration scenarios that can be
navigated based on the ACORD Forms and SOA runtime environment.
Figure 3-1 ACORD Forms and SOA Demo activities
These demonstration scenarios are:
Personal Inland Marine Application through Portal Channel
Personal Inland Marine Application through Viewer Channel
Business Rules
Commercial Business Auto Application through Portal Channel
Commercial Business Auto Application through Viewer Channel
2.Personal Inland Marine
Application through
Viewer Channel
Demo Flow
3.Business Rules
4.Commercial Business Auto
Application through Portal
Channel
5.Commercial Business Auto
Application through Viewer
Channel
1.Personal Inland Marine
Application through Portal
Channel

Chapter 3. User scenarios
33
Regardless of the demonstration scenario to be executed, the first step is to
logon to the portal. In the VM Image for the demonstration, the configured
credentials are userid
John
and password
JohnJohn
; which provides customer
level authorization, or userid
Jane
and password
JaneJane
; which provides
agent/producer level authorization. See Figure 3-2.
Figure 3-2 ACORD Forms and SOA Demo Logon Portal window

34
IBM Software Supporting ACORD Insurance Standards
Logging into the portal yields the portal window in Figure 3-3.
Figure 3-3 ACORD Forms and SOA Demo Welcome Portal window
The welcome portal window is just a mock-up; a real implementation would
create something relevant to the roles that would use the application. For the
purposes of the ACORD Forms SOA Demo, the relevant choices of Online Form
Service or Offline Form Service are used to access the documented user
scenarios. Selecting the Online Form Services option allows us to exercise the
first and fourth scenarios. Selecting the Offline Form Service allows us to
exercise the second and third scenarios.

Chapter 3. User scenarios
35
3.2 Exercising the ACORD forms and SOA
demonstration scenarios
This section describes the five demonstration scenarios.
3.2.1 Personal Inland Marine Application through Portal Channel
Selecting Online Form service allows you to select Personal Inland Marine from
the Catalog and allows access to the Personal Inland Marine Forms available in
the demonstration. There are two options, an empty form that allows you to fill in
the appropriate data, exercising the available edits, and a pre-filled form that
contains sample data. See Figure 3-4.
Figure 3-4 ACORD Forms SOA Data Personal Inland Marine Portal Use Case

36
IBM Software Supporting ACORD Insurance Standards
Selecting one of the form options yields the form in Figure 3-5.
Figure 3-5 ACORD Form SOA Data Personal Inland Marine Portal form. Courtesy of ACORD Corporation.
Reprinted with permission.
Fill in the data in the form, and click the Submit option to process the form.
The way the demonstration was originally made, entering unemployed in the
OCCUPATION field of the form trips the business edit built into the form that
enables the form to operate reflexively. This is simply an example of the kind of
behavior that the SOA infrastructure enables for the form, above and beyond the
dynamic behavior that can be built into the logic of the forms themselves.

Chapter 3. User scenarios
37
Entering unemployed in the OCCUPATION field of the form, and then clicking
Submit, creates the response window shown in Figure 3-6.
Figure 3-6 ACORD Form SOA Data Personal Inland Marine Portal Response form
This window indicates that more questions need to be answered based on the
business rules that were entered for this form and the data entered into the form.

38
IBM Software Supporting ACORD Insurance Standards
In the Personal Inland Marine scenario, clicking the Fill Again button brings up a
new form with additional questions, as shown in Figure 3-7. Unlike in the
Commercial Auto scenario described later, this brings up a new form with
additional pages.
Figure 3-7 ACORD Form SOA Data Personal Inland Marine Portal Form with additional questions.
Courtesy of ACORD Corporation. Reprinted with permission.
The additional questions are found by paging though the form using the
Next/Previous option. Answer these questions and then use the Submit option
again to reprocess. Note that the original demonstration was not given business
rules to evaluate the responses to these questions.

Chapter 3. User scenarios
39
Clicking Submit on this form results in the portal displaying the response window
shown in Figure 3-8.
Figure 3-8 ACORD Form SOA Data Personal Inland Marine Portal finished form
The section of the window showing that the form has been submitted indicates
that the form was successfully accepted by the SOA infrastructure for further
processing and that user data entry is now completed. The portal view showing
this section of the window was viewed from the personal workplace option that is
shown in Figure 3-4 on page 35.
This view happens when the in-progress form, shown in Figure 3-6 on page 37,
is instead activated by going to the Personal Workplace view shown in Figure 3-4
and selecting the form with the correct reference ID instead of opening the form
directly from the button in Figure 3-6 on page 37.

40
IBM Software Supporting ACORD Insurance Standards
Figure 3-16 on page 47 shows an example of the portal page when the Online
Form Service page is used to complete processing of the form. Either route is
acceptable for completing the form user entry scenario, and does not change the
processing result, but does illustrate that the demonstration supports either
single or multi-session data entry for a form.
3.2.2 Personal Inland Marine application through Viewer Channel
Selecting Offline Form service allows you to select Selecting Personal Inland
Marine from the Catalog and allows access to the Personal Inland Marine Forms
available in the demonstration. There are two options, an empty form that allows
you to fill in the appropriate data, exercising the available edits, and a pre-filled
form that contains sample data. See Figure 3-9.
Figure 3-9 ACORD Form SOA Data Personal Inland Marine Viewer Use Case

Chapter 3. User scenarios
41
Selecting one of the form options yields the form in Figure 3-10.
Figure 3-10 ACORD Form SOA Data Personal Inland Marine Viewer Use Case download
Clicking Save on the File Download dialog allows you to save a copy of the
ACORD form so that it can be used offline outside of the portal via the viewer.
At this point, this use case operates the same as the portal version, so the
windows are omitted. Simply open the saved file in the viewer. Enter data on the
form. If the OCCUPATION is set to Unemployed when the form is submitted,
you get a response window indicating the new URL for the updated form. This
new window looks similar to Figure 3-11, except that it has a link to the new form.
At this point, download the new form, answer the questions, and re-submit.

42
IBM Software Supporting ACORD Insurance Standards
After the form is either re-submitted or if the OCCUPATION was not set to
unemployed, you get the response window in Figure 3-11.
Figure 3-11 ACORD Form SOA Data Personal Inland Marine Viewer Use Case finished. Courtesy of
ACORD Corporation. Reprinted with permission.

Chapter 3. User scenarios
43
3.2.3 Business rules
Exercising this use case simply requires you to build rule scenarios based on the
WPS rule manager data entry guide. As you can see from Figure 3-12, this
window illustrates the rules that were configured in the demonstration to drive the
other four use cases.
Figure 3-12 ACORD Form SOA Demo Business Rules

44
IBM Software Supporting ACORD Insurance Standards
3.2.4 Commercial Business Auto application through Portal Channel
Selecting Online Form Service allows you to select Commercial Auto from the
Catalog and allows access to the Commercial Auto Forms available in the
demonstration. As shown in Figure 3-4 on page 35 for the Personal Inland
Marine use case, there are two options, an empty form that allows you to fill in
the appropriate data, exercising the available edits, and a pre-filled form that
contains sample data. Selecting one of the options yields the form shown in
Figure 3-13.
Figure 3-13 ACORD Form SOA Demo Commercial Auto Portal Use Case Form. Courtesy of ACORD
Corporation. Reprinted with permission.
Fill in the data in the form, and click the Submit option to process the form. The
way the demonstration was originally created, checking the BUSINESS AUTO
option of the form trips the business edit built for the form that enables the form to
operate reflexively. This is simply an example of the kind of behavior that the
SOA infrastructure enables for the form, above and beyond the dynamic
behavior that can be built into the logic of the forms themselves.

Chapter 3. User scenarios
45
Checking the BUSINESS AUTO option the form, and then clicking Submit,
creates the response window shown in Figure 3-14.
Figure 3-14 ACORD Form SOA Demo Commercial Auto Portal Use Case Response form

46
IBM Software Supporting ACORD Insurance Standards
This window indicates that more questions need to be answered based on the
business rules that were entered for this form and the data entered into the form.
As in the Personal Inland Marine Scenario, clicking the Fill Again button brings
up a new form, but in this case the form contains additional pages as shown in
Figure 3-15.
Figure 3-15 ACORD Form SOA Demo Commercial Auto Portal Use Case Form with additional pages.
Courtesy of ACORD Corporation. Reprinted with permission.
The additional pages, including the third page containing form 137 as shown in
Figure 3-15, are found by paging though the form using the Next/Previous
option. This scenario shows an example of dynamically building a form package
where there is too much variability to determine what pages are required for data
entry before the user enters data on the first form.
Instead, the SOA provides a reflexive response to data entered on the initial form
with a response that contains the additionally required pages. Included in this
scenario is the automatic propagation of data from each page to the next based
on the shared data model in the dynamically constructed pages.

Chapter 3. User scenarios
47
After the additional pages of data are entered, use the Submit option again to
reprocess. Clicking Submit on this form results in the portal displaying the
response window shown in Figure 3-16.
Figure 3-16 ACORD Form SOA Demo Commercial Auto Portal Use Case Form finished
The section of the window showing that the form has been submitted indicates
that the form was successfully accepted by the SOA infrastructure for further
processing and that user data entry is now completed. Unlike in the Personal
Inland Marine scenario, Figure 3-16 shows the portal view with this section of the
window as viewed from the original Online Form Service workplace option.
Whereas, the Personal Inland Marine scenario, previously discussed, shows a
view from the personal workplace view shown in Figure 3-4 on page 35 and
selecting the form with the correct reference ID is used, instead of opening the
form directly from the button on Figure 3-6 on page 37 or Figure 3-14 on
page 45. Either route is acceptable for completing form data entry, and does not
change the processing result, but does illustrate that the demonstration supports
either single or multi-session data entry for a form.

48
IBM Software Supporting ACORD Insurance Standards
3.2.5 Commercial Auto application through Viewer Channel
Selecting Offline Form Service allows you to select Commercial Auto from the
Catalog and allows access to the Commercial Auto Forms available in the
demonstration. As shown in Figure 3-4 on page 35 for the Personal Inland
Marine use case, there are two options, an empty form that allows you to fill in
the appropriate data, exercising the available edits, and a pre-filled form that
contains sample data. Selecting one of the options yields the Open or Save
dialog form shown in Figure 3-10 on page 41.
Clicking Save on the File Download dialog allows you to save a copy of the
ACORD form so that it can be used offline outside of the portal via the viewer.
At this point, the use case operates the same as the portal version starting with
Figure 3-13 on page 44, so the windows are omitted. Simply open the saved file
in the viewer. Enter data on the form. If the BUSINESS AUTO option of the form
is checked when the form is submitted, you get a response window indicating the
new URL for the updated form. This new window looks similar to Figure 3-11 on
page 42, except it has a link to the new form. At this point, download the new
form, answer the questions, and re-submit.
After the form is either re-submitted or if the BUSINESS AUTO option of the form
is not checked, you get the response window in Figure 3-11 on page 42.

© Copyright IBM Corp. 2009. All rights reserved.
49
Chapter 4.
eForms + SOA Solution
architectural overview
This section describes the architecture for the ITSO working example of IBM
software supporting the ACORD Standards eForms + SOA Solution, and
provides information regarding the software levels that we used to implement the
environment.
In our solution, many IBM software products are involved. We first introduce the
whole architecture design for this solution, and then dive into the detailed
implementation.
The architecture is defined by the ITSO working example of IBM software
supporting the ACORD Standards eForms + SOA Solution with the following
high level layout of steps:
Architecture design:
– Multi-Channel Support:
• Lotus Form Viewer Channel
• Web Portal Channel
– Business rule based context evaluation
– Template based eForm population
– XForm Transformation Engine
– Security considerations
4

50
IBM Software Supporting ACORD Insurance Standards
Implementation overview:
– Gateway Service
– Service Specifications:
Authentication Service
Authorization Service
Form Processing Service
Insurance Business Service
4.1 Architectural design
To integrate eForm as an entry to an SOA solution, we need provide a generic
form gateway that seamlessly merges the form based UI to an SOA architecture.
The whole request from eForm with a digital signature is submitted to a Gateway
Service, which is sitting in front of business services. This Gateway Service
validates the signature and extracts the XForms model from the submitted
eForm. Then the XForms model is sent to eForm processing services to form
processing. If the form is validated, the XForms model is translated to an
ACORD message and sent to Insurance Business Services to do a business
process. Otherwise, a new eForm is populated and stored in an XML database
and responded to the client site. (Refer Figure 4-1 for a diagram of the process.)
Figure 4-1 ITSO architectural overview: IBM software supporting ACORD Insurance Standards eFORMS +
SOA Solution (Gateway Service introduction)
Industry SOA Foundation
CBS Reference
Implementations
PCS Message Transform
I
nsura
nce Business Service
Contents Evaluation
Form Processing
Authentication
Forms Processing
Authentication
Commercial Auto
business services
Other Insurance business
services ...
LOB
Forms Population
Content Evaluation
Authentication Authorization
LDAP
Authentication and
Authorization
Proxy
Servlet
eForms Model
eForms Model
Form Rendering
Portlet
Portal
Server
eForm
Server
Channel 2
Channel 1
Gateway Service
I
Off-line
Web
Browser
eForm
Server
Invoke
Personal Inland
Marine business services

Chapter 4. eForms + SOA Solution architectural overview
51
The Gateway Service, which uses the ACORD content from within the
WebSphere P&C Content Pack, acts as a facade proxy service for all ACORD
eForms submissions. Agency client application can interact with Gateway
Service to submit ACORD eForms and get the receipt of the business process
result.
ACORD Gateway Service includes a Gateway process, that coordinates the
invocation of necessary services, including Authentication/Authorization service,
Form Processing Service, application review human task, business rule group,
and Insurance Business Service. ACORD Gateway Service performs these
major tasks:
1.Accept requests from various channels:
– Requests that are sent through Web Portal
– Requests that are sent through eForm Viewer
2.Authenticate and authorize the user.
3.Review/approve, and run operation services as business rules.
4.Invoke Form Processing Service to process the message (validate, analyze,
modify/populate, and so on).
5.Invoke the appropriate Insurance business service, for example, Personal
Inland Marine Application Service and Commercial Business Auto Application
Service. These Insurance Services execute the real business transactions in
the back-end.
The ApplicationReview service is implemented as a Human task component that
offers manual business interaction capability besides the automatic process. By
using an IBM integration development tool, the UI of application review is JSP™
based a Web page that is generated from ApplicationReview service interface
automatically without additional development.
The appropriate Process Insurance Service is invoked based on the message
content, thus the Forms data model is dispatched for process operation, and a
service result is returned from a back-end business service.
The business rule component can be deployed in this solution to provide
dynamic business rule adjustment capability, thus a business administrator can
operate through a business rule console at runtime without having to restart the
IT system.
Note: Requests could also be sent through a WebService Channel.

52
IBM Software Supporting ACORD Insurance Standards
4.1.1 Multi-channel support
In this solution, we support two channels to invoke the business services; from
IBM Lotus Form Viewer (for example, offline channel) and from Web Portal page
(for example, online channel).
Lotus Form Viewer Channel
Agents operate ACORD XForms in IBM Lotus Form Viewer. First, agents need to
login to the Portal Web site and download relevant form template files to local
storage. Then they open the form in Lotus Form Viewer and fill it together with
the customer. Finally, when the content is ready, the customer signs the form on
a signature pad and submits it to the remote server.
Web Portal Channel
Agents operate ACORD XForms through the Internet/intranet portal Web site,
which offers online business capabilities such as insurance policies, quotes,
claims, and so on. The ACCORD XForms agent needs to fill the online form and
submit it in the same Web session. Temporary form local storage is not
supported in this channel. Figure 4-2 represents how Lotus WebForm Server
works with Portal together to do the Web Page rendering. When the user
requests a form from the Application Server, Webform Server translates the form
into HTML before sending it to the user.

Chapter 4. eForms + SOA Solution architectural overview
53
Figure 4-2 Lotus WebForm Server for Portal Web Page Rendering
Figure 4-2 on page 53 shows the following steps:
1.The user requests a form from the portlet/servlet. This request is usually
triggered by clicking a link in a browser.
2.The portlet/servlet receives the request and locates the correct file in a Form
Repository or triggers a Form Application which returns an XFDL form.
3.The form is passed to the portlet/servlet.
4.The servlet passes the form to the Translator.
5.The Translator converts the form to a combination of HTML and JavaScript™
and sends the converted form back to the portlet/servlet.
6.The portlet/servlet passes the converted form to the Web server, which
returns it to the user.
4.1.2 Business rule based context evaluation
In the real world, sometimes additional questions are required for the agent to
answer during the application process. After the agent submits the form for the
first time, a link to a new form with additional questions attached can be
responded. We call it additional form processing. Because the logic of the
Webform Server
XFDL form
Repository
WebSphere
Portal Server
Portlets
Web Browser
1
5
4
3
2
6

54
IBM Software Supporting ACORD Insurance Standards
additional form processing is different in different companies and different
insurance businesses, we use business rules to implement such logic.
Context evaluation service (refer to the architecture diagram) is a service that
evaluates the input form according to business rules, determines whether
additional questions are needed to fill or not, and what the additional questions
are. The input of this service is an XForms model, and the output is a structure to
describe the context evaluation result. Business rules are used in this service in
order to provide the flexibility and the ability to configure.
Figure 4-3 shows the business rules definition for a Personal Inland Marine
application, where ACORD Form 81 should be used. The rules say that if the
applicant occupation is for an
engineer
, two additional questions are to be
attached to the old form. The parts in bold font are editable. Administrators can
add new rules and edit the old rule contents at runtime.
Figure 4-3 Business Rules Console view
4.1.3 Template based eForm population
When the context evaluation returned indicates that additional form processing is
required, a new form with the agent's original inputs and the additional questions
is generated. eForm population service, which is used to implement this function,
populates a given XForms model into the corresponding eForm template, stores
it to a database, and returns the ID of the new form. For example, if there are
additional questions for users to answer, it populates the questions into the
XForms model and generate a corresponding eForm. Response forms are
populated based on the user request forms, form templates, and context
evaluation results.
The empty forms are stored in a repository. Because XForms enable the MVC
structure, in order to fill the empty form with the agent's original inputs, we can
just replace the empty form model with the original submitted form model filled
with data. But for the additional questions, because there is no eForm controls
binding with them, we have to update the user interface of the form first, add new
control items to the original form, and then set additional question data to the
form model.

Chapter 4. eForms + SOA Solution architectural overview
55
In order to facilitate the update of the user interface (UI), we use a template for
the question UI generation. We create a template with a question UI template
using the eForm editor. During the population, the question template file is
parsed, and question UI is generated according to the template, such as the
color, the size of Lines, and so on. The generated question UI page is added into
the populated eForm document, and the binding between question UI and
question model is set. We can easily adjust the look and feel of question UI by
modifying the question template document using eForm designer; there is no
need to modify form population service code or restart form population service.
Figure 4-4 shows the user interface with the additional questions.
Figure 4-4 ITSO ACORD eForm Example: Additional Question driven from Business Rules. Courtesy of
ACORD Corporation. Reprinted with permission.
4.1.4 XForms Data Transformation Engine
In our solution, we need to transform the submitted XForms data (from ACORD
eForms) to the back-end ACORD PCS message. Then we need a mature
Transformation Engine to help with this. In our solution, we defined a common
transform service with a standard interface to do the transformation work.
The concrete implementation of this service depends on what kind of
Transformation Engine we want to leverage. For example, if we do not want to
buy or leverage some commercial Transformation Engine, then we can try to
implement the transformation requirements by ourselves. We can write some
utilities to do this. But of course, it would be more powerful and stable if we could
just leverage some existing mature Transformation Engine, such as WebSphere
Transformation Extender (WTX).

56
IBM Software Supporting ACORD Insurance Standards
WTX is a powerful, transaction-oriented, data integration solution that automates
the transformation of high-volume, complex transactions without the need for
hand-coding. This provides enterprises with a quick return on investment. This
product supports EDI, XML, SWIFT, HIPAA, and other standards-based B2B
integration, as well as the real-time integration of data from multiple applications,
databases, messaging middleware, and communications technologies across
the enterprise.
If we involve WTX to be the dependent Transformation Engine to help us do the
XForms data transformation work, then the transform service is realized to
depend on WTX to transform the submitted ACORD XForms data model to the
standard data model of the ACORD PCS message. We just need use the WTX
studio drag and drop to create a mapping file, and the mapping file is referenced
by the WTX during runtime to do the transformation work. You can find a sample
mapping file as shown in Figure 4-5.
Figure 4-5 ITSO XML Mapping: Mapping tool view

Chapter 4. eForms + SOA Solution architectural overview
57
If we depend on the WebSphere Transformation Extender product to help us
realize the runtime data transformation, then we can easily deliver the following
features to the Insurance customers:
Connectivity to a wide range of mainframe, legacy, and enterprise
applications, databases, messaging systems, and external information
sources
A comprehensive library of more than 120 pre-built functions to reduce
development time and simplify specification of rules for validation,
transformation, and routing
Multiple execution options to support right-time, right-style transformation,
whether it is batch, real-time, or embedded
Enterprise-class capabilities for development, deployment, and maintenance,
plus high-availability platform support.
4.1.5 Security considerations
In our solution, we design and implement security mechanism in two layers.
Form security
In ACCORD XFDL form, we add a Silanis signature on customer content. This
kind of signature blends a digital signature and a Signature Pad signature. After
a customer completes filling the form, they need to write their signature on a
digital pad that captures the handwriting. Then the actual signature on customer
content is created using a digital certificate. The image of the handwritten
signature is stored as part of the digital signature for later reference.
Besides the Signature Pad signature for customers, we also add an
Authenticated Clickwrap signature on the agent content. After a customer signs
the form, an agent fills some extra information according to the customer's input,
and finally, sign the form. Here the agent needs to provide their LDAP account
and password as Authenticated Clickwrap ID and shared secret to sign the form.
Whenever the form is submitted to the server, the Gateway Service calls the
Lotus Form API to verify these signatures:
1.Verify the data integrity and security. If the content corresponding to a certain
signature is changed after it is signed, the signature breaks.
2.Verify whether the agent's signature is signed by a correct ID and secret of a
certain agent.

58
IBM Software Supporting ACORD Insurance Standards
Authentication and authorization
On the server side, we offer an Authentication and Authorization service to
authenticate the agent and authorize their operation. First, the Authentication
service verifies the login agent's information in LDAP towards information
retrieved in the agent signature and form content. The authorization service then
authorizes the agent for corresponding operation privileges on the server side.
4.2 Implementation overview
In this solution, a set of processes and services are designed and realized to
support different functional features. We briefly describe the major processes
and services in this section.
4.2.1 ACORD Gateway Service
The ACORD Gateway Service (Figure 4-6) acts as a facade proxy service for all
of the ACORD Forms submissions. Agency client application can interact with
the ACORD Gateway Service to submit ACORD Forms and get the receipt of the
business process result.

Chapter 4. eForms + SOA Solution architectural overview
59
Figure 4-6 ITSO Service: ACORD Gateway Service
The ACORD Gateway Service (Figure 4-6 on page 59) includes a Gateway
process, which coordinates the invocation of necessary services, including
Authentication/Authorization service, Form Processing Service, and Insurance
Business Service.
These are the major tasks that ACORD Gateway performs:
1.Accepts requests from various channels:
– Requests that are sent through Portal
– Requests that are sent through Lotus Form Viewer.
2.Authenticates and authorizes the user.
3.Invokes Form Processing Service to process the message (validate, analyze,
modify/populate, and so on).
4.Invokes the appropriate Insurance business service, such as Personal Inland
Marine Application Service and Commercial Business Auto Application

60
IBM Software Supporting ACORD Insurance Standards
Service. These Insurance Services execute the real business transactions in
the back-end.
The appropriate Process Insurance Service is invoked based on the message
content. If the message is Personal Inland Marine Application, Personal Inland
Marine Application Service is invoked. If the message is Commercial Business
Auto Application, Commercial Business Auto Application Service is invoked.
4.2.2 Services specifications
In this section, we list detailed service specifications for your reference. For each
service, you can find its specification including service description, preconditions,
postconditions, success/failure conditions and interface definition.
Authentication service
This service authenticates if the agent is an available user. For this solution, we
extract user credential information from the user signed ACORD XForms model,
authenticate the user to the Tivoli® LDAP User registry, and return the
authentication status. Both the Viewer and Portal channel are supported.
Preconditions
Preconditions include a valid ACORD XForms model conforming to ACORD
XForms model schema, and the agent has signed the ACORD Form before
submitting it.
Postconditions
Postconditions include success or failure messages as described:
Success: A valid ACORD XForms model with ACORDXFormAuthenStatus type
with attributes
StatusCd
and
StatusDesc
populated with a successful
authentication message.
Failure: A valid ACORD XForms model with ACORDXFormAuthenStatus type
with attributes
StatusCd
and
StatusDesc
populated with failure messages.
Interface: Figure 4-7
shows details of the interface
.
Figure 4-7 Form AuthenticationService

Chapter 4. eForms + SOA Solution architectural overview
61
Authorization service
This service authorizes if the agent is able to submit this kind of request. The
user's access permission is checked according to user credential extracted from
the signed ACORD XForms model. Given the user group information exists in
the Tivoli LDAP User registry, this service determines user access permission,
and returns the Authorization status. It supports both Viewer and Portal
Channels.
Preconditions
Preconditions include a valid ACORD XForms model conforming to ACORD
XForms model schema. And the agent has signed the ACORD Form before
submitting it.
Postconditions
Postconditions include success or failure messages as described:
Success: A valid ACORD XForms model with ACORDXFormAuthorStatus type
with attributes
StatusCd
and
StatusDesc
populated with a successful
authentication message.
Failure: A valid ACORD XForms model with ACORDXFormAuthorStatus type
with attributes
StatusCd
and
StatusDesc
populated with failure messages.
Interface: Figure 4-8 shows details of the interface
.
Figure 4-8 FormAuthorizationService
Form Processing services
Form Processing service transform, validate, and modify the ACORD messages.
Common services are invoked to transform and validate ACORD messages, and
Form Population Service is invoked to modify ACORD messages.
The Forms data model is sent to process operation, and a service result is
returned from the back-end business service.
Interface: Figure 4-9 shows details of the interface
.

62
IBM Software Supporting ACORD Insurance Standards
Figure 4-9 FormProcessInterface
The transform service is invoked inside, which translates ACORD XForms data
model to ACORD PCS message standard data model. This can be done easily
through IBM WTX (WebSphere Transformation Extender) shown in Figure 4-10.
The Developer needs to use the WTX studio drag and drop to create a mapping
file, and WBSF can invoke the mapping file during run time as a Web service.
Figure 4-10 ITSO Mapping: WebSphere Transaction Extender (WTX) Mapping

Chapter 4. eForms + SOA Solution architectural overview
63
Insurance business services
We invoke back-end business services to simulate the Personal Inland Marine
Insurance service and Commercial business auto insurance service. The
back-end business services invoke a service to a persistence user request
message, deal the user request message, and return an ACORD message that
contains a Personal Inland Marine Insurance service response.
This back-end business service implements the Record Quote business service
interface of the Insurance P&C Content Pack reference business service
template. The record quote processes service for a multi-channel, multi-line,
pre-underwriting, quote processing capability that enables straight through quote
processing.
The Record Quote business service interface is described in the
Rate Quote and
Issue
application of the
New Business
Application Suite in Insurance P&C
Content Pack as a Business service reference templates exposed common
service interface.
Interface: Figure 4-11 shows details of the interface.
Figure 4-11 ProcessInsuranceServiceInterface

64
IBM Software Supporting ACORD Insurance Standards

© Copyright IBM Corp. 2009. All rights reserved.
65
Chapter 5.
eForms + SOA Solution
installation and
configuration
In this chapter we describe the installation and configuration for the ITSO
working example of IBM software supporting the ACORD Standards eForms +
SOA Solution. We provide information regarding how and why the solution was
constructed.
In our solution, many IBM software products are involved. We showcase the
detailed infrastructure utilized, and then dive into the detailed installation and
configuration of the enterprise solution.
5

66
IBM Software Supporting ACORD Insurance Standards
5.1 Planning and scenario overview
This section describes the scenario for the ITSO working example of IBM
software supporting the ACORD Standards eForms + SOA Solution, and
provides information regarding the software levels we used to implement the
environment.
5.1.1 Scenario overview
The implementation procedures for the ITSO working example of IBM software
supporting the ACORD Standards eForms + SOA Solution include the following
software as shown in Figure 5-1:
IBM HTTP Server
WebSphere Portal Server
Lotus Forms Server
WebSphere Process Server
WebSphere Business Service Fabric Server
WebSphere Transformation Server®
Tivoli Directory Server
DB2 Client and Enterprise Server
ACORD Application Demo
Note: This chapter does not include implementation procedures for network
configurations or firewalls.

Chapter 5. eForms + SOA Solution installation and configuration
67
Overview
Figure 5-1 shows the high-level infrastructure utilized for the solution showcase.
On the left, in the outside zone, the channels that were made available to access
the showcase are shown. The Web Node and Data Node provide a high level
view of the server software installed and configured.
Figure 5-1 ITSO scenario overview: IBM software supporting ACORD Insurance Standards eForms + SOA
Solution
Detailed architecture
Figure 5-2 shows a low-level infrastructure view for the solution infrastructure.
The Web Zone and Data Zone shows the actual IBM SOA software stack and
software levels used, and the servers used in the installation configuration
process. This view gives a better understanding of the implementation and
integration that took place for this eForm + SOA Solution.
Web Node Data Node
Request
HTTP Server
Portal Server
Process Server
Business
Service
Server
XML
Transformation
Server
Forms Server
Database Client
Response
Database Server
Directory Server
(LDAP)
Outside Zone
Client Browser
Client Forms Viewer

68
IBM Software Supporting ACORD Insurance Standards
Figure 5-2 ITSO scenario detailed architecture: IBM software supporting ACORD Insurance Standards
eForms + SOA Solution
5.1.2 Hardware and software prerequisites
For detailed information about the hardware and software prerequisites of IBM
software supporting ACORD Insurance Standards eForms + SOA Solution, refer
to the product Web content in the following links.
For more information on the installation and configuration of IBM Products, refer
to these links for assistance with installation, configuration, and best practices.
IBM HTTP Server - 6.0
– Product documentation
swgdemo.raleigh.ibm.com swgdemodb2.raleigh.ibm.com
IBM HTTP
Server 6.0
Web Server Plugin
for WAS ND
WebSphere
Application
Server – ND
6.0.2.23
XML
Transformation
Server
Forms Server
DB2
Connect
9.1.4
DB2 Enterprise
Server Edition
w/pureXML 9.1.4
Tivoli Directory
Server 6.1.0.0
Request
Response
WebSphere
Business Service
Fabric 6.0.2
Foundation Pack
WebSphere
Business Service
Fabric 6.0.2
Insurance P&C Pack
Lotus Forms
Server 3.0
(Server/API/SDK)
WebSphere
TX 8.1
(Server/SDK)
Outside Zone
Client Browser
Client Forms Viewer
WebSphere
Business Service
Fabric 6.0.2
Database Components Only

Chapter 5. eForms + SOA Solution installation and configuration
69
IBM WebSphere Portal Server - 6.0.1.1
– InfoCenter
IBM WebSphere Application Server - Network Deployment - 6.0.2.23
– InfoCenter
– Library
IBM WebSphere Process Server - 6.0.2.3
– InfoCenter
– Library
IBM WebSphere Business Service Fabric - 6.0.2 Foundation Pack
– InfoCenter
– Library
IBM WebSphere Business Service Fabric - 6.0.2 Insurance P&C Pack
– Library
– Whitepaper
IBM Lotus Forms Server - 3.0 API
InfoCenter
IBM Lotus Forms Server - 3.0 Forms Server Platform SDK
– InfoCenter
IBM Lotus Forms Server - 3.0 WebForms Server
– InfoCenter
WebSphere Transformation Extender - 8.1
– InfoCenter - Note that this is for 8.2 but contains helpful information
– Library
WebSphere Transformation Extender - 8.1 SDK
– InfoCenter - Note that this is for 8.2 but contains helpful information
– Library
DB2 Runtime Client - 9.1.4
– InfoCenter
DB2 Enterprise Server Edition with pureXML - 9.1.4
– InfoCenter
Tivoli Directory Server - 6.1.0.0
– InfoCenter

70
IBM Software Supporting ACORD Insurance Standards
5.1.3 Hardware used within the ITSO eForms + SOA Solution
We used the following hardware for the ITSO working example. Refer to the
product documentation or developerWorks for best practices for installation and
configuration for a production environment.
The following nodes, which are depicted in Figure 5-1 on page 67 and Figure 5-2
on page 68, show how they fit into the solution infrastructure.
1. Web Node
IBM eServer™ xSeries® x3400:
2 CPU, Intel® Xeon 2.0 GHz
8 GB main memory
500 GB DASD
1 IBM Gigabit Ethernet adapter
Hostname: swgdemo.raleigh.ibm.com
2. Data Node
IBM ThinkCenter M55:
1 CPU, Intel Core™ Duo™ 2.66GHz
4 GB main memory
160 GB DASD
1 IBM Gigabit Ethernet adapter
Hostname: swgdemodb2.raleigh.ibm.com

Chapter 5. eForms + SOA Solution installation and configuration
71
5.1.4 Software used within the ITSO eForms + SOA Solution
The ITSO working example of IBM software supporting ACORD Insurance
Standards eForms + SOA Solution was implemented using the software levels
listed in each of following tables (Table 5-1 and Table 5-2) listed by node.
Table 5-1 Web node
Table 5-2 Data node
Software Version
Microsoft® Windows 2003 Enterprise Server 2003 Enterprise Server + Service Pack 2
IBM HTTP Server 6.0
NOTE: Comes with WAS ND 6.x
IBM WebSphere Portal Server 6.0.1.1
IBM WebSphere Application Server - Network Deployment 6.0.2.23
IBM WebSphere Process Server 6.0.2.3
IBM WebSphere Business Service Fabric -Foundation Pack 6.0.2
IBM WebSphere Business Service Fabric - Insurance P&C
Pack
6.0.2
IBM Lotus Forms Server - API 3.0
IBM Lotus Forms Server - Forms Server Platform SDK 3.0
IBM Lotus Forms Server - WebForms Server 3.0
WebSphere Tranformation Extender 8.1
WebSphere Transformation Extender - SDK 8.1
DB2 Runtime Client 9.1.4
Software Version
Microsoft Windows 2003 Enterprise Server 2003 Enterprise Server + Service Pack 2
DB2 Enterprise Server Edition with pureXML 9.1.4
Tivoli Directory Server 6.1.0.0
IBM WebSphere Business Service Fabric -Foundation Pack
(DB Config Only Install)
6.0.2

72
IBM Software Supporting ACORD Insurance Standards
Software downloads from IBM
For all IBM software, follow all guidelines and best practices for downloading,
unpacking, and proper installation and configuration of all IBM software. Newer
versions of software should be tested and validated with usage, because this
might require alternatives to other software packages and tooling.
5.1.5 Software installation paths and variables
Table 5-3 and Table 5-4 list the software installation paths and variables used to
implement the Web Node and Data Node.
Table 5-3 Web Node - Software installation paths and variables
Software ITSO install path Variable
IBM HTTP Server C:\IBM HTTP Server\<http_home>
IBM WebSphere Portal Server C:\WebSphere\PortalServer\<portal_server_home>
IBM WebSphere Application Server -
Network Deployment
Option of WebSphere Process Server <was_nd_home>
IBM WebSphere Process Server C:\WebSphere\ProcServer\<process_server_home>
IBM WebSphere Business Service
Fabric - Foundation Pack
C:\WebSphere\Fabric\FoundationPack\<wbsf_foundation_home>
IBM WebSphere Business Service
Fabric - Insurance P&C Pack
C:\WebSphere\Fabric\Insurance\P_C\<wbsf_p&c_home>
BM Lotus Forms Server - API C:\Lotus Forms\Server\3.0\API\<lotus_forms_api_home>
IBM Lotus Forms Server - Forms
Server Platform SDK
C:\Lotus Forms\Server\3.0\Deployment
Server\
<lotus_forms_sdk_home>
IBM Lotus Forms Server - WebForms
Server
C:\Lotus Forms\Server\3.0\Webform
Server\
<lotus_forms_server_home>
WebSphere Tranformation Extender C:\WebSphere\Transformation
Extender 8.1\
<wtx_home>
WebSphere Transformation Extender
- SDK
C:\WebSphere\Transformation
Extender 8.1\
<wtx_sdk_home>
DB2 Runtime Client C:\db2_9.1\IBM\SQLLIB\<db2_runtime_client_home>

Chapter 5. eForms + SOA Solution installation and configuration
73
Table 5-4 Data Node - Software installation parts and variables
5.2 Install and configure the Data Node
The Data Node is the testing area for all server components associated with
creating and loading the ACORD Web application demo's data and users and
the IBM software supporting ACORD Insurance Standards eForms + SOA
Solution. This node controls all database, XML, and LDAP users. We
recommend that you install these components first to prepare the data
environment before installing the Web node components. The implementation in
this node includes the following tasks:
1.Microsoft Windows 2003 Enterprise Server installation
2.DB2 Enterprise Server Edition with pureXML
3.Tivoli Directory Server
4.IBM WebSphere Business Service Fabric - Foundation Pack (DB only)
5.2.1 Microsoft Windows 2003 Enterprise Server configuration
We included this section to state that Microsoft Windows 2003 Enterprise Server
was utilized as the base operating system (OS). All Windows Installation Guides
and Best Practices are recommended while installing and configuring the OS.
After the OS installs and security and updates are applied to the server, two user
IDs are needed:
Administrator
Database Administrator
Software ITSO install path Variable
DB2 Enterprise Server Edition with
pureXML
C:\db2_9\IBM\SQLLIB\<db2_ese_home>
Tivoli Directory Server C:\Tivoli\DirectoryServer\LDAP\<tds_home>
IBM WebSphere Business Service
Fabric - Foundation Pack (DB Only
Install)
C:\WebSphere\Fabric\FoundationPack\<wbsf_db_home>
Note: All security and fixpacks should be installed before installing the IBM
products and ACORD Web Application Demo Code.

74
IBM Software Supporting ACORD Insurance Standards
All products were installed under the Administrator ID, and all database instances
and database were created by the Database Administrator ID.
5.2.2 DB2 Enterprise Server Edition with pureXML configuration
This section describes how to install the IBM DB2 Universal Database™ V9.1,
Enterprise Server Edition, and supporting Fixpack 4. This section is organized
into the following tasks:
Install DB2 ESE V9.1
Install DB2 ESE V9.1 Fixpack 4
Install DB2 ESE V9.1 pureXML
Verify DB2 ESE
Configure DB2 ESE for Product Installations and ACORD Demo
Install DB2 ESE V9.1
describes how to install the IBM DB2 Universal Database™ V9.1
To install the IBM DB2 V9.1 Enterprise Edition Server, complete these steps:
1.Insert the DB2 ESE V9.1 Enterprise Server Edition CD or use the download.
2.Navigate to the
<CD_Root>
or
<UnZipped_Download_Root>
and run Setup
to start the installation.
3.When the DB2 Installer window appears, click Install Products.
4.When the Select the Product to Install window appears, select DB2
Enterprise Server Edition (default and only option) and then click Next.
5.When the Welcome window for the DB2 Setup Wizard appears, click Next.
6.When the License Agreement window appears, review the agreement and
select I accept the terms in the license agreement and click Next.
7.When the Select the installation type window appears, select Typical and
then click Next.
8.When you see a warning message, regarding connection to remote DB2
servers using APPC, click OK.
Note: This gets created as part of the DB2 installation.
Note: Depending on the DB2 ESE V9.1 CD distribution you are using, the
installation panels might be slightly different than those we have described.
Refer to the IBM InfoCenter for product installations beyond these steps.

Chapter 5. eForms + SOA Solution installation and configuration
75
9.When the Select the Installation Action window appears, check Install DB2
Enterprise Server Edition on this computer and then click Next.
10.When the Select the Installation Folder window appears, we entered
<db2_ese_home> and then clicked Next.
11.When the Set User Information for DB2 Administration Server window
appears, enter the following information and then click Next:
– Domain: <we left this field blank>
– User name: db2admin (default)
– Password: <password>
– Confirm password: <password>
– Check Use the same username and password for remaining DB2
services (default)
12.When the Setup the Administration Contact List appears, we accepted the
default settings (local) and then clicked Next.
13.When the warning message Notification SMTP server has not been specified,
click OK.
14.When the Configure DB2 instances window appears, we accepted the default
(DB2) and then clicked Next.
15.When the Prepare the DB2 tools catalog window appears, you can prepare or
not prepare the tools, but install them into the default DB2 instance if you do
then click Next.
16.When the Specify a contact for health monitor notification window appears,
select Defer the task after installation is complete, and then click Next.
17.When the Start copying files window appears, review the selected options and
then click Install.
18.When the Setup is Complete window appears, click Finish.
19.When the IBM DB2 First Steps window appears, click Exit First Steps.
Note: Depending on the DB2 UDB V9.1 CD distribution that you are using,
the installation panels might be slightly different than what we have
described.
Note: The DB2 UDB installation, with the Typical installation type, takes
approximately 376 MB of disk space.

76
IBM Software Supporting ACORD Insurance Standards
Install DB2 ESE V9.1 Fixpack 4
We installed IBM DB2 ESE V9.1 Fixpack 4 for 32 bit Windows. We chose to use
Fixpack 4 because it was the Enterprise Server Edition that was recommended
for the WebSphere Portal, WebSphere Process Server, and Tivoli Directory
Server installations. Also, we wanted to use the same version of DB2 Fixpack on
all of the nodes for DB2 compatibility reasons.
To download and install the IBM DB2 ESE V9.1 Fixpack 4, do the following:
1.The IBM DB2 ESE V9.1 Fixpack 4 can be downloaded at:
ftp://ftp.software.ibm.com/ps/products/db2/fixes2/english-us/db2winI
A32v9/fixpack/FP4_WR21396/v9fp4_win_ese.exe
2.We downloaded the FP4a_WR21338_ESE.exe, which is the fixpack 4 for the
IBM DB2 Universal Database V9.1, Enterprise Server Edition.
3.Stop all DB2 services in the Windows services.
4.Install the IBM DB2 ESE V9.1 Fixpack 4. We accepted the default installation
options.
5.We recommend that you restart your system after installing the fixpack to
ensure that all fixes are applied and active in memory.
6.After the system has restarted, open a DB2 command window (or Windows
command window) and enter the following command:
db2level
It should return 9.1.400.359 after Fixpack 4 has been installed.
Install DB2 ESE V9.1 pureXML
To install the DB2 ESE V9.1 pureXML functionality, the DB2 License file needs to
be downloaded:
db2xmlese.lic DB2 pureXML Feature for Enterprise Server Edition
From the License Center, use the Add License window to add new licenses on
Linux® or Windows operating systems. This action is also referred to as applying
license entitlement certificates or registering a license key.
Note: The instructions in this section are from the IBM InfoCenter, however,
key items were modified where applicable.
http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/
com.ibm.db2.udb.uprun.doc/doc/t0008699.htm

Chapter 5. eForms + SOA Solution installation and configuration
77
To complete this task, you must have the appropriate license file (*.lic). Refer to
DB2 license files. On Linux operating systems, the instance owner must have
read and write privileges on the directory where the license files are located.
1.Click in the Control Center to open the License Center. Select the system
for which you want to add a new license.
2.Select an instance.
3.The Installed Products field displays the name of the products that you have
installed. Select a product.
4.Select Add from the License menu. The Add License dialog opens.
5.Select the license key (*.lic) that you want to add.
6.Click OK to add the license key.
Verify DB2 ESE
After you install DB2 ESE V9.1 and fixpack, and have restarted your system, we
recommend that you verify that DB2 ESE is working properly.
Configure DB2 ESE for product installations and ACORD
demonstration
After your install has been verified, the following steps are requires for
configuring DB2 to contain all of the appropriate configuration required to run the
ACORD demonstration:
Create the following instances:
a.Start the DB2 Command Window.
b.Run the command db2icrt <INSTANCE_NAME> in the order listed:
i.WPSINST
ii.WBSFINST
iii.FORMINST
iv.APPINST
Create db2profile files:
a.Go to Directory C:\<db2_ese_home>\DB2 directory.
b.Copy file db2profile.bat.
c.Paste into each instance directory (C:\
<db2_ese_home>\<INSTANCE_NAME\), while opening the file and
modifying the instance name:
@echo off
SET DB2INSTANCE=<INSTANCE_NAME>

78
IBM Software Supporting ACORD Insurance Standards
Update the Windows Services File:
a.Go to Directory C:\WINDOWS\System32\drivers\etc\.
b.Open the file services.
c.Go to the end of the file and update the ports as follows:
DB2_WPSINST 60004/tcp
DB2_WPSINST_1 60005/tcp
DB2_WPSINST_2 60006/tcp
DB2_WPSINST_END 60007/tcp
db2c_WPSINST 50001/tcp
DB2_WBSFINST 60008/tcp
DB2_WBSFINST_1 60009/tcp
DB2_WBSFINST_2 60010/tcp
DB2_WBSFINST_END 60011/tcp
db2c_WBSFINST 50002/tcp
DB2_FORMINST 60012/tcp
DB2_FORMINST_1 60013/tcp
DB2_FORMINST_2 60014/tcp
DB2_FORMINST_END 60015/tcp
db2c_FORMINST 50003/tcp
DB2_APPINST 60016/tcp
DB2_APPINST_1 60017/tcp
DB2_APPINST_2 60018/tcp
DB2_APPINST_END 60019/tcp
db2c_APPINST 50004/tcp
Update the DB2 configuration for each instance:
a.Open DB2 command window.
b.Goto first instances directory C:\<db2_ese_home>\<INSTANCE_NAME>.
c.Run db2profile.bat for that instance.
d.Run the following command:
db2 UPDATE DATABASE MANAGER CONFIGURATION USING SVCENAME
db2c_WPSINST
e.Repeat the steps for each instance, updating the SVCENAME to the
instance connection port that was added to the service file.
Note: Replace WPSINST with the current <INSTANCE_NAME> that
you are working with.

Chapter 5. eForms + SOA Solution installation and configuration
79
Run the following DB2Set command for each instance:
a.Open DB2 command window.
b.Goto first instances directory C:\<db2_ese_home>\<INSTANCE_NAME>.
c.Run db2profile.bat for that instance.
d.Run the following commands:
db2set DB2_INLIST_TO_NLJN=YES
db2set DB2_EVALUNCOMMITTED=YES
db2set DB2PORTRANGE=60004:60007
db2set DB2_RR_TO_RS=YES
db2set DB2COMM=TCPIP
e.Repeat the steps for each instance, updating the port range to match what
was put into the services file.
Restart Windows Server® after all steps are completed.
Configure Windows Services to Auto Start every Instance.
a.Right-click each of the instances and click Properties.
b.Select Automatic in the Startup type.
5.2.3 Tivoli Directory Server installation
Installing with the Typical installation path on Windows
systems
To install IBM Tivoli Directory Server 6.1 using the Typical installation path:
1.Be sure that you are logged on as any member of the Administrators group.
Note: Windows Services are listed, similar to these:
DB2- DB2COPY1 - <INSTANCE_NAME>
Note: The instructions in this section are from the IBM InfoCenter, however,
key items were modified where applicable:
http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm
.IBMDS.doc/install09.htm#shield

80
IBM Software Supporting ACORD Insurance Standards
2.On the computer where you are installing IBM Tivoli Directory Server, stop
any programs that are running and close all windows. If you have open
windows, the initial IBM Tivoli Directory Server installation window might be
hidden behind other windows.
3.If you are installing from a CD:
a.Insert CD 1 in your CD-ROM drive.
b.Go to the drive for your CD-ROM, and then go to the \tds folder.
If you are installing from downloaded .zip files, go to the folder where you
unzipped the downloaded .zip files, and then go to the tdsV6.1\tds folder.
4.Double-click install_tds.bat icon.
If you prefer, you can use the command line to begin installation and specify a
temporary directory other than the one specified by the TEMP environment
variable. To use this option, go to the appropriate directory (from step 3) and
type the following command at a command prompt:
install_tds.bat -is:tempdir directory
Where directory is the directory you want to use for temporary space. Be
sure that you have at least 255 MB of free space in this directory. If you are
installing any of the co-requisite products (IBM Tivoli Directory Integrator,
Embedded WebSphere Application Server, or DB2) be sure that you also
have 150 MB in the directory specified by the TEMP environment variable.
For example:
install_tds.bat -is:tempdir c:\My Documents\temp
The language window is displayed.
5.Select the language you want to use during IBM Tivoli Directory Server
installation. Click OK.
6.On the Welcome window, click Next.
Note: If the installation program exits without displaying the language
window, it might be because there is not enough space in the directory
specified by the TEMP environment variable or the directory you specified
for temporary space. Be sure that you have at least 255 MB of free space
in this directory.
Note: This is the language used in the installation program, not in IBM
Tivoli Directory Server. The language used in IBM Tivoli Directory Server is
determined by the language pack you install.

Chapter 5. eForms + SOA Solution installation and configuration
81
7.After reading the Software license agreement, select I accept both the IBM
and the non-IBM terms. Click Next.
8.If you have any components already installed, they are displayed with their
corresponding version levels. Click Next.
9.To install in the default directory, click Next. You can specify a different
directory by clicking Browse or typing the directory path to C:\<tds_home>
listed above.
10.Click Typical.
11.Because DB2 is already installed, make sure that you use the DB2
Administrator ID and the IDSINST to be created.
12.The installation program now has enough information to begin installing.
A summary window displays the components to be installed, the installation
locations, and the amount of disk space required. The Typical installation
path installs all features that are not already installed. If you want to install
different features, you must click Back until you reach the window where you
selected Typical installation, and select Custom installation instead. Then
use the instructions in Installing with the Custom installation path on Windows
systems. Typical installation does not allow you to select features for
installation.
13.Click Install to begin installation.
Progress windows are displayed as features are installed.
If you are installing from CDs, you are prompted to insert different CDs during
the installation. Be sure to follow the instructions carefully and insert the
correct CDs, or installation does not proceed correctly and unpredictable
results might occur.
Notes:
If you have already installed one or more language packs, the
installation location is set to the path where you installed the language
packs, and you are not asked where you want to install.
Be sure that the installation location is not the same as the path where
another version of the client or the server is installed.
Do not use special characters, such as hyphen (-) and period (.) in the
name of the installation directory. For example, use
ldapdir
rather than
ldap-dir
or
ldap.dir
.

82
IBM Software Supporting ACORD Insurance Standards
14.The Typical installation path creates the default directory server instance with
the following information, which you cannot change:
– Name: IDSINST
– Instance location: c:\IDSINST
– Group name: Administrators
– Administrator DN: cn=root
– Database name: LDAPDB
In addition, the o=sample suffix is created for the default directory server
instance. You can add other suffixes later with the Configuration Tool or the
idscfgsuf command. See Managing suffixes for information.
Notes:
The <tds_home>\bin, <tds_home>\sbin, and <tds_home>\lib directories
are not added to the Path environment variable. This allows IBM Tivoli
Directory Server 6.1 to coexist with IBM Tivoli Directory Server 6.0.
If the Web Administration Tool is installed, Directory Services Markup
Language (DSML) files are also copied to your computer. See
Appendix M. Installing and configuring DSML for information about
installing and configuring DSML.
If the Web Administration Tool is installed, a Web application server is
required to run the tool, and Embedded WebSphere Application Serve
6.1.0.7 is installed and configured for you. If version 5.0, 5.0.2, or 5.1.1
of Embedded WebSphere Application Server is already installed, the
InstallShield GUI installation program automatically upgrades it to
version 6.1.0.7. Any configuration files from the previous Web
Administration Tool are backed up and restored. If you want to use
another WebSphere Application server, you must use Custom
installation to select a Web application server.
When Embedded WebSphere Application Server is installed and an
application (such as the Web Administration tool or the IBM Tivoli
Directory Integrator Administration and Monitoring Console) is installed
into Embedded WebSphere Application Server, the Embedded
WebSphere Application Server server for that application is also
installed as a service.
Attention: After installation has begun, do not try to cancel the installation.
If you inadvertently cancel the installation, see the information about
recovering from a failed installation in the IBM Tivoli Directory Server
version 6.1 Problem Determination Guide before you attempt to reinstall.

Chapter 5. eForms + SOA Solution installation and configuration
83
Type the following additional information about the default directory server
instance in the appropriate fields:
User password
Type the system password for user idsinst. If this user does not exist on
the system, the user ID is created with the password you specify. If the
user ID already exists, be sure to type the correct password for the user.
Confirm password
Type the password again for confirmation.
Encryption seed
Type an encryption seed string (used as a seed for generating encrypted
stash files). The string can use characters a-z, A-Z, or 0-9. This string
must be a minimum of 12 characters and a maximum of 1016 characters.
Confirm seed
Type the encryption seed string again for confirmation.
Administrator DN password
Type a password for the administrator DN for the directory server
instance. (The Administrator DN for the default directory instance is
cn=root.)
Confirm DN password
Type the administrator DN password again for confirmation.
Click Next when you have completed all the fields.
15.Click Finish.
Notes:
If you are asked if you want to restart your computer now or later, select
the option you want and click Finish. (You might need to restart your
system to complete IBM Tivoli Directory Server installation. You are
unable to use IBM Tivoli Directory Server until this is completed.)
If your computer is restarted, log in using the same user ID that you
used to install IBM Tivoli Directory Server.
If you installed DB2, the DB2 First Steps GUI might be started. You can
go through the DB2 First Steps or close this GUI.

84
IBM Software Supporting ACORD Insurance Standards
5.2.4 IBM Tivoli Directory Server configuration
To configure IBM Tivoli Directory Server 6.1, perform the following steps:
1.Start Program: Start → All Programs → Tivoli Directory Server 6.1 →
Instance Administration Tool or run the command idscfgsuf in the
C:\<tds_home>\bin directory.
2.Select the instance that was just created and click the Configure button.
3.Click Manage Administrator Password and type in a password for the
cn=root ID.
4.Select Manage Suffixes and enter in the following two suffixes:
dc=nava, dc=com (then click Add button).
dc=swgdemo, dc=com (then click Add button).
5.Now select Import LDIF data.
6.The users.ldif file is used for this step. Follow the instructions in
Appendix A, “Additional material” on page 169 to obtain the file.
7.Select Standard Import and click the Import button at the bottom.
8.At this point all your users for the ACORD Demo are now in the LDAP
database and ready to use.
Notes:
A license subdirectory is created in the directory where IBM Tivoli Directory
Server is installed. This subdirectory contains IBM Tivoli Directory Server
license files in all provided languages.
The Instance Administration Tool starts. You can use the Instance
Administration Tool to add more directory server instances or edit existing
directory server instances. See Creating and administering instances for
instructions.
To make changes to your configuration at a later time, see Configuration
for more information about using the Configuration Tool.
If any errors occurred during installation, instance creation, or
configuration, see the information in the IBM Tivoli Directory Server version
6.1 Problem Determination Guide for information about recovering from
these errors.
Note: The users.ldif should be used for the demonstration but not for a
production system.

Chapter 5. eForms + SOA Solution installation and configuration
85
IBM Tivoli Web Administration configuration
To configure IBM Tivoli Web Administration, perform the following steps:
1.First verify that the following Windows Services are running (Figure 5-3).
Figure 5-3 Windows Services
2.After each of these services are started, open a browser and go to the
following URL:
a.http://swgdemodb2.raleigh.ibm.com:12100/IDSWebApp/IDSjsp/Login.jsp
?showConsoleAdminLogin=true
3.To log into the Web Admin function: If logging in for the first time, use the
following userid and password.
a.UserID::
b.Password::
4.Update the Console Administration Login for security purposes. See
Figure 5-4.
Figure 5-4 Change console administrator login
Note: Replace
swgdemodb2.raleigh.ibm.com
with your Data Node Host
Name.

86
IBM Software Supporting ACORD Insurance Standards
5.Click Manage Console Servers and Add a new server, which is your Data
Node server where the product is installed. See Figure 5-5.
Figure 5-5 Manage console servers
6.After these steps are complete, you can use the Web Administration Console
to add new user IDs as well as any other administration functions you might
need to utilize (Figure 5-6). To do so, the following URL is needed to access
the Web administration. Click:
http://swgdemodb2.raleigh.ibm.com:12100/IDSWebApp/IDSjsp/Login.jsp
Figure 5-6 Directory server login window
7.To use this URL you must login with the cn=root id that was configured in the
original Tivoli Directory Server installation.
8.Verify the installation and configuration.
5.2.5 IBM WebSphere Business Service Fabric - Foundation Pack
(DB only) configuration
In this section we describe how to install the IBM WebSphere Business Service
Fabric - Foundation Pack.

Chapter 5. eForms + SOA Solution installation and configuration
87
Complete the following steps:
1.Open the DB2 command window.
2.cd to the WBSFINST directory (C:\<db2_ese_home\WBSFINST\).
3.Run the db2profile.bat.
4.In the same command window, cd to the directory where the Installation CD
or Files are, and run the install_fabric_win.exe file.
5.Follow the default installation of the db only option.
5.3 Install and configure the Web Node
The Web Node is the testing area for all server components associated with
creating and loading the ACORD Web application demonstration. This node
controls all Web Services, XML Transforms, eForms, SCA Composites,
Business Services, Processes, and Web Code. The configuration in this node
includes the following tasks to be performed before deploying the ACORD Web
Application Demo code:
1.Microsoft Windows 2003 Enterprise Server
2.IBM WebSphere Process Server
3.IBM WebSphere Portal Server
4.IBM WebSphere Business Service Fabric - Foundation Pack
a.IBM WebSphere Business Service Fabric - Insurance P&C Pack
5.IBM Lotus Forms Server
6.WebSphere Tranformation Extender
7.DB2 Connect™
l
Note: Depending on the IBM WebSphere Business Service Fabric -
Foundation Pack distribution that you are using, the installation might be
slightly different than we have described. Refer to the IBM InfoCenter for
product installations beyond these steps.
Note: The assumption is that all manuals and best practices should be
followed for basic installation of all products. The configuration sections
explain how to take the base installation and configure them for application
demonstration deployment.

88
IBM Software Supporting ACORD Insurance Standards
5.3.1 Microsoft Windows 2003 Enterprise Server configuration
We included this section to state that Microsoft Windows 2003 Enterprise Server
was utilized as the base operating system (OS). All Windows Installation Guides
and Best Practices are recommended while installing and configuring the OS.
After the OS installs and security and updates are applied to the server, two user
IDs are needed:
Administrator
Database Administrator
All products were installed under the Administrator ID, and all database
instances and database were created by the Database Administrator ID.
5.3.2 IBM WebSphere Process Server configuration
IBM WebSphere Process Server configuration consists of a default installation,
based on the IBM InfoCenter into the <process_server_home> directory, with a
connection to DB2.
Starting the Launchpad
1.Log on as root on a Linux or UNIX® system, or as a member of the
Administrator group on a Windows system.
2.Insert the product CD labeled WebSphere Process Server CD 1 into the
CD-ROM drive and mount the drive if necessary, as described in Mounting
CD-ROMs on Linux and UNIX operating systems.
3.Start the Launchpad by doing the following tasks:
– On Linux and UNIX platforms: Execute the command
mount_point/launchpad.sh where mount_point represents the mount
point on the Linux or UNIX system.
Note: All security and fixpacks should be installed before installing the IBM
products and ACORD Web Application Demo Code.
Note: The instructions in this section are from the IBM InfoCenter. For more
information, visit:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?t
opic=/com.ibm.wsps.602.ins.doc/welcome_wps_ins.html

Chapter 5. eForms + SOA Solution installation and configuration
89
– On Windows platforms: If the Launchpad does not start automatically
when you insert the product CD, from a command line, execute the
command CD-ROM_drive:\launchpad.exe.
The Launchpad is displayed.
4.Select your language in the Language selection field.
Installing WebSphere Process Server or the client interactively
Use this procedure to install WebSphere Process Server or the Client using the
Installation wizard graphical user interface (GUI). You can install WebSphere
Application Server Network Deployment as part of your installation. You can also
install WebSphere Process Server or the Client over an existing installation of
WebSphere Application Server or WebSphere Application Server Network
Deployment, version 6.0.x.x.
Before you begin
Before installing using this procedure, ensure that:
You have decided on the type of installation you prefer:
– A Complete (default) installation, which installs WebSphere Process
Server and WebSphere Application Server Network Deployment using
default installation selections and configurations. It also creates a
stand-alone process server profile named default with a server named
server1.
– A Custom installation, which lets you select the product features you wish
to install. It can also install WebSphere Application Server Network
Deployment, and allows you to run the Profile wizard at the end of the
installation to create a WebSphere Process Server profile.
– A Client installation, which installs the WebSphere Process Server Client
and can install WebSphere Application Server Network Deployment.
You have decided whether to install WebSphere Application Server Network
Deployment as part of your WebSphere Process Server or Client installation
or to instead use an existing installation of WebSphere Application Server or
WebSphere Application Server Network Deployment, version 6.0.x.x.
You have reviewed possible installation topologies in Planning installation
topologies.
Important: This selection does not create a sample Business Process
Choreographer configuration for the stand-alone process server profile.

90
IBM Software Supporting ACORD Insurance Standards
Your system meets all hardware requirements and that you have installed all
required software co-requisites and prerequisites. See Hardware and
software requirements for more information.
You have prepared your operating system for installation. See Preparing the
operating system for installation for instructions.
You are installing the product as the root user on a Linux or UNIX system, or
as a member of the Administrator group on a Windows system.
You are installing from product CDs. If you plan to install from images
obtained from Passport Advantage®, see Special considerations when
installing from Passport Advantage for important information.
Why and when to perform this task
This procedure assumes that you want to install interactively and that you do not
have WebSphere Process Server already installed. If your proposed installation
does not meet these criteria, see Installing the software for descriptions of other
installation procedures.
Use the following procedure to install the product.
Steps for this task
Follow these steps to install:
1.Log on as the root user on a Linux or UNIX system, or as a member of the
Administrator group on a Windows system.
2.Start the WebSphere Process Server installer.
Do these tasks:
a.Start the Launchpad by following the procedure in Starting the Launchpad.
b.From the right pane of the Launchpad, select WebSphere Process
Server installation > Launch the Installation wizard for WebSphere
Process Server for Multiplatforms.
3.From the Welcome panel of the installer, select Next.
4.In the License agreement panel, review the IBM and non-IBM licensing terms,
select I accept both the IBM and the non-IBM terms, and select Next.
The Installation wizard checks for a supported operating system with
prerequisite patches. At the end of the process, the Checking prerequisites
panel indicates whether your system passed the check. This procedure
assumes that your system passed.
If your system did not pass, cancel the installation, make the required
changes, and restart the installation.

Chapter 5. eForms + SOA Solution installation and configuration
91
5.In the Checking prerequisites panel, select Next.
The Installation wizard checks for existing installations of WebSphere
Process Server, WebSphere Process Server Client, WebSphere Enterprise
Service Bus, WebSphere Application Server, and WebSphere Application
Server Network Deployment. This procedure assumes that you do not have
an existing WebSphere Process Server, Client, or WebSphere Enterprise
Service Bus installation, but that you might have an existing WebSphere
Application Server or WebSphere Application Server Network Deployment
installation.
If you do
not
have an existing installation of WebSphere Application Server or
WebSphere Application Server Network Deployment, the Installation location
panel is displayed. Proceed to Step 7 on page 92.
If you do have an existing installation of one of these products, an Existing
installation detected panel is displayed. Proceed to step 6.
6.In the Existing installation detected panel, do one of the following tasks:
– If you want to install a new copy of WebSphere Application Server Network
Deployment, select Install a new copy of WebSphere Application Server
Network Deployment, Version 6.0 and select Next. A warning panel
outlines considerations you must make when installing the product on a
system with an existing installation. Select Next to close the warning
panel. The Installation location panel is displayed. Proceed to step 7 on
page 92.
– If you want to install WebSphere Process Server over an existing
installation of WebSphere Application Server or WebSphere Application
Server Network Deployment, select Use an existing installation of
WebSphere Application Server Network Deployment, Version 6.0 or
Use an existing installation of WebSphere Application Server,
Version 6.0 and select Next. (If you have multiple installations, be sure to
select the one you want to use from the drop-down list.) A warning panel
alerts you to stop servers before continuing if the application you chose
has running servers. Select Next to close the warning panel. The
Installation type panel is displayed. Proceed to step 8 on page 92.
Note: The installer also detects unregistered instances of WebSphere
Application Server or WebSphere Application Server Network Deployment
if they have entries in the .WASRegistry file. This file is located in the
$USER_HOME directory of the installation. Using an unregistered
installation of one of these products with your WebSphere Process Server
installation is neither recommended nor supported.

92
IBM Software Supporting ACORD Insurance Standards
7.In the Installation location panel, accept the default installation root directory
for the products, or specify a different directory, and select Next. See Default
installation paths for the default installation directories.
8.In the Installation type panel, select the type of installation you want and
select Next. The Installation Wizard provides three installation paths (not all
might appear based on selections you made on previous panels):
– The Complete path installs WebSphere Process Server and WebSphere
Application Server Network Deployment, and creates a stand-alone
process server profile.
– The Custom path allows you to select those features you want to install,
plus can install WebSphere Application Server Network Deployment. It
does not create a profile, but allows you to run the Profile wizard at the end
of the installation.
– The Client path installs the WebSphere Process Server Client and can
install WebSphere Application Server Network Deployment. It does not
create a profile.
If you selected Complete or Client, proceed to step 10. If you selected
Custom, proceed to step 9.
9.In the Feature selection panel, select the features you want to install and
select Next. See Product components for descriptions of the features you can
select from this panel.
10.In the Installation summary panel, review the components to be installed, the
amount of space they are to consume, and where they are to be located on
the system, and select Next to install or Back to change your specifications.
Important:
– You must provide a value for the installation root directory to
continue.
– Do not use non-ASCII special characters in directory names; they
are not supported.
– On Linux and UNIX platforms: Do not use symbolic links as the
installation root directory - they are not supported. Also, do not use
spaces in the directory path.
– On Linux platforms: The installation root directory path must be no
longer than 256 characters to successfully install the products.
– On Windows platforms: When performing a Complete installation,
the installation root directory path must be no longer than 60
characters to successfully create the default stand-alone profile.

Chapter 5. eForms + SOA Solution installation and configuration
93
The Installation wizard creates the uninstaller program and shows a progress
panel to indicate that components are being installed.
If you elected to use an existing version of WebSphere Application Server or
WebSphere Application Server Network Deployment, the Installation wizard
examines it and does one of the following:
– Does nothing if the installation is at the correct service level.
– If the installation is at an earlier service level, applies the necessary fixes
to bring the installation up to the appropriate level and also applies any
necessary interim fixes.
– If you selected the WebSphere Process Server Sample applications
gallery feature, and you are installing over an installation of WebSphere
Application Server Network Deployment that does not have its Samples
gallery feature installed, the Samples gallery feature is added silently to
the WebSphere Application Server Network Deployment installation.
At the end of the installation, the Installation complete panel is displayed.
Each of these panels identifies the log file to reference in order to
troubleshoot the problems. See the descriptions of relevant log files listed in
Log files, error messages in Error messages: installation and profile creation
and augmentation, and refer to Troubleshooting installation for tips on
troubleshooting your installation. If you performed a Complete installation and
the default profile did not create successfully, refer to Recovering from profile
creation or augmentation failure for troubleshooting tips.
Restriction: The Sample applications gallery feature can be
incrementally installed only over a WebSphere Application Server
Network Deployment installation. Thus, if you select the WebSphere
Process Server Sample applications gallery feature, and you are
installing WebSphere Process Server over an installation of
WebSphere Application Server that does not have its Samples gallery
feature installed, the Sample applications gallery feature is not added
silently to the WebSphere Application Server installation.
Attention: If errors are detected during installation, other panels might be
displayed in place of the Installation complete panel. Here are some
examples:
Installation is complete with errors panel, which indicates that the
installation completed but errors were generated.
Installation failed panel, which indicates that the installation failed
completely.

94
IBM Software Supporting ACORD Insurance Standards
11.The Installation complete panel differs depending on the type of installation
you performed:
– If you performed a Complete installation, ensure the check box to launch
the First Steps console is selected, and select Finish to close the
Installation wizard and launch the First Steps console.
– If you performed a Client installation, select Finish to close the Installation
wizard.
– If you performed a Custom installation, do one of the following tasks
depending on whether you want to create a new profile:
• To create a new profile, leave the check box beside Launch the Profile
Wizard selected and select Next. The Installation wizard closes and
the Profile wizard is launched. See Creating profiles using the Profile
wizard and Augmenting profiles using the Profile wizard for instructions
on how to use this wizard to create new process server profiles or
augment existing application server profiles into process server
profiles.
• To not create a new profile, unselect the check box beside Launch the
Profile Wizard and select
• Next. In this case, a warning panel is displayed, which explains that
without a profile there is no operational server. Do one of the following:
• Select Back for another chance to launch the Profile wizard.
• Select Next. The Installation complete panel is displayed with a
check box to launch the First Steps console. Ensure that this
check box is selected and select Finish to close the Installation
wizard and launch the First Steps console.
Creating profiles using the Profile wizard
You can create a stand-alone server profile, a deployment manager profile, or a
custom profile using the Profile wizard graphical user interface (GUI).
Before you begin
Before using this procedure, ensure that you have reviewed the list of
prerequisites for creating or augmenting a profile at Prerequisites for creating or
augmenting profiles.
Note: To have an operational environment, a WebSphere Process
Server stand-alone profile or deployment manager profile with
managed nodes must exist.

Chapter 5. eForms + SOA Solution installation and configuration
95
For instance, to start the Profile wizard in the German language on a Linux
system, type the following commands:
install_root/java/bin/java -Duser.language=de -cp install_root/ \
bin/ProfileCreator_wbi/pcat.jar run
Why and when to perform this task
Complete the following steps to create the following profiles for all the products
and the ACORD Application Demo:
wps
wbsf
forms
apps
Steps for this task
Follow these steps to create the profiles:
1.Start the WebSphere Process Server Profile wizard. You can start the wizard
in several ways:
Important: You cannot have two instances of the WebSphere Process Server
Profile wizard or WebSphere Application Server or WebSphere Application
Server Network Deployment Profile creation wizard running concurrently on
one set of core product files. Attempts to create profiles concurrently result in
a warning. If a warning panel is displayed, determine if there is another profile
creation or augmentation action occurring.
If there is, you must wait until it completes.
If there is not, delete the file profileRegistry.xml_LOCK in the directory
install_root/properties if it exists. You can then run the Profile wizard.
Important: The language of the Profile wizard is determined by the default
language on the system. If the default language is not one of the supported
languages, then English is used. You can override the system's default
language by starting the Profile wizard from the command line and using the
java user.language setting to replace the default language, as follows:
On Linux and UNIX platforms: install_root/java/bin/java
-Duser.language=locale -cp install_root/bin/ProfileCreator_wbi/pcat.jar run
On Windows platforms: install_root\java\bin\java -Duser.language=locale
-cp install_root\bin\ProfileCreator_wbi\pcat.jar run

96
IBM Software Supporting ACORD Insurance Standards
– On all platforms, from the First Steps console. See Starting the First Steps
console for how to start the First Steps console.
– On Windows platforms: From the Windows Start menu, or by executing
the command install_root\bin\ProfileCreator_wbi\pcatWindows.exe.
– On Linux and UNIX platforms: By executing the appropriate command in
the install_root/bin/ProfileCreator_wbi directory. The name of the
command varies by platform:
• On AIX® platforms: ./pcatAIX.bin
• On HP-UX platforms: ./pcatHPUX.bin
• On Linux x86 32-bit platforms: ./pcatLinux.bin
• On Linux x86 64-bit platforms: ./pcat.bin
• On Linux zSeries® 31-bit and 64-bit platforms: ./pcatLinux390.bin
• On Linux Power platforms: ./pcatLinuxPPC.bin
• On Solaris™ SPARC platforms: ./pcatSolaris.bin
• On Solaris x86 64-bit platforms: ./pcatSolarisx86_64.bin
Important: Do not execute the similar pct command found in
install_root/bin/ProfileCreator on Linux and UNIX platforms and
install_root\bin\ProfileCreator on Windows platforms. This command
creates WebSphere Application Server profiles --
not
WebSphere Process
Server profiles.

Chapter 5. eForms + SOA Solution installation and configuration
97
2.In the Welcome panel (Figure 5-7), click Next.
Figure 5-7 Welcome window

98
IBM Software Supporting ACORD Insurance Standards
3.In Figure 5-8, select Stand-alone profile and click Next.
Figure 5-8 Profile type selection window

Chapter 5. eForms + SOA Solution installation and configuration
99
4.Replace the Variable <PROFILE_NAME> in Figure 5-9, with one of the
following profiles, because all four of these profiles have to be created.
– wps
– wbsf
– forms
– apps
Click Next.
Figure 5-9 Profile name

100
IBM Software Supporting ACORD Insurance Standards
5.Make sure that the directory you place the profiles in are no more than 250+
chars, Figure 5-10 shows the recommended directory for profile creation.
Click Next.
Figure 5-10 Profile directory

Chapter 5. eForms + SOA Solution installation and configuration
101
6.The node and hostname we kept as default for this demonstration
(Figure 5-11). Click Next.
Figure 5-11 Node and host names

102
IBM Software Supporting ACORD Insurance Standards
7.All ports were kept as default in this example (Figure 5-12). Click Next.
Figure 5-12 Profile Wizard window

Chapter 5. eForms + SOA Solution installation and configuration
103
8.Running as a Windows Service is a deployment decision (Figure 5-13). For
this demonstration, we recommend making sure that you use it as a service,
for ease of rebooting. Click Next.
Figure 5-13 Windows service definition window

104
IBM Software Supporting ACORD Insurance Standards
9.Service Component Architecture Configuration (Figure 5-14) is
recommended to use the wasadmin ID and password that was in the Tivoli
directory server installation/configuration steps, because this is useful when
configuring security in WebSphere. Click Next.
Figure 5-14 Service Component Architecture configuration

Chapter 5. eForms + SOA Solution installation and configuration
105
10.Common Event Infrastructure (CEI) Configuration (Figure 5-15) is
recommended to also use the wasadmin ID and password from the Tivoli
Directory Server installation/configuration. Follow the window displays for the
other options. Click Next.
Figure 5-15 Common Event Infrastructure Configuration window

106
IBM Software Supporting ACORD Insurance Standards
11.The Common Event Infrastructure (CEI) additional DB parameters
(Figure 5-16) should utilize the database installation instance information
from the Data Node DB2 installation/configuration steps. The database user
ID should be the db2admin ID and password created with the Windows 2003
installation or the ID used in the db2 installation. Click Next.
Figure 5-16 Additional DB parameters

Chapter 5. eForms + SOA Solution installation and configuration
107
12.Business Process Choreographer Configuration (Figure 5-17) is
recommended to also use the wasadmin ID and password from the Tivoli
Directory Server installation/configuration. Follow the window displays for the
other options. Click Next.
Figure 5-17 Business Process Choreographer Configuration

108
IBM Software Supporting ACORD Insurance Standards
13.Application Scheduler Configuration (Figure 5-18) used the standard
parameter of server1. Click Next.
Figure 5-18 Application Scheduler configuration

Chapter 5. eForms + SOA Solution installation and configuration
109
14.Database Configuration (Figure 5-19 and Figure 5-20) is recommended to
set up a new or existing database separately. This generates scripts for
deployment on the Data Node in the current instance you are working. Use all
Data Node DB2 Instance Ports, Parameters, and the default db2admin id/pwd
for this section. Click Next.
Figure 5-19 Database Configuration window

110
IBM Software Supporting ACORD Insurance Standards
Figure 5-20 Additional Database Configuration Information

Chapter 5. eForms + SOA Solution installation and configuration
111
15.For the Profile Summary (Figure 5-21) , click Next to start the creation of the
profile.
Figure 5-21 Profile Summary

112
IBM Software Supporting ACORD Insurance Standards
16.Profile Creation is complete (Figure 5-22). If you keep the Launch First Steps
Console, it gives you the options that you can perform for the newly created
profile. Click Finish.
Figure 5-22 Profile creation is complete

Chapter 5. eForms + SOA Solution installation and configuration
113
17.The next step is to install the databases on the Data Node that was selected
to be created later:
– Common DB
– Event (CEI)
18.cd to directory <profile_home_dir>\dbscripts\CommonDB\DB2\WPRCSDB:
– example <profile_home_dir> = C:\WebSphere\profiles\<PROFILE_NAME>\
19.Copy or FTP files to the Data Node directory temp folder, C:\temp\CommonDB
20.cd to directory <profile_home_dir>\event\dbscripts\db2\
– example <profile_home_dir> = C:\WebSphere\profiles\<PROFILE_NAME>\
21.Copy or FTP all Files to the Data Node Directory temp folder, C:\temp\Event.
22.After all the files are copied to the Data Node Server, start the db2 command
window.
23.cd to the <db2_ese_home>\INSTANCENAME\ directory of the corresponding
instance:
– wps profile → wpsinst instance
– wbsf profile → wbsfinst instance
– forms profile → forminst instance
– apps profile → appinst instance
24.Run the bat file db2profile.bat.
25.cd to the C:\temp\CommonDB directory.
26.Run the following script:
– configCommonDB.bat createDB
27.Verify success with the following command:
– db2 list database directory
28.cd to the C:\temp\event directory.
29.Run the following script:
– cr_event_db2.bat server db2admin
30.Verify success with the following command:
– db2 list database directory
31.Go back to the Web node cd to <profile_home_dir>\event\dsscripts\db2.
32.Run the following script:
– cr_db2_jdbc_provider.bat cell

114
IBM Software Supporting ACORD Insurance Standards
33.Verify that JDBC™ provider was created (Figure 5-23).
Figure 5-23 JDBC providers
5.3.3 DB2 Runtime Client configuration
This task describes how to install a DB2 Runtime client on the Windows
operating system. The instructions apply to any DB2 client type, namely the DB2
Client and the DB2 Runtime Client. In this installation, the demonstration utilizes
the DB2 Runtime Client.
Attention: Repeat All Creating Profiles steps for each profile required for this
demonstration.
Note: The instructions in this section are from the IBM InfoCenter, however,
key items were modified where applicable:
http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/
com.ibm.db2.udb.uprun.doc/doc/t0007315.htm

Chapter 5. eForms + SOA Solution installation and configuration
115
Prerequisites
Ensure that the following prerequisites are met:
Locate the CD or other install image that you need. Ensure you have the
appropriate 32-bit or 64-bit version, depending on your machine.
Ensure that your system meets memory, disk space, and installation
requirements. The installation program checks these and notifies you if there
is a problem.
You need to have a Windows user account that is part of either the
Administrators or Power Users group. Alternatively, you need a
non-Administrator user account that has been properly configured.
If the machine already has a prior version of a DB2, follow the info center for
suggestions on how to process. The demonstration suggestions and
recommends that the installation is performed on machines that are newly
configured.
This procedure covers the simple case. To install the DB2 Runtime Client on
Windows:
1.Log on to the system with the Administrator User Account.
2.Optional: Shut down any other programs.
3.Insert the CD into the drive. The auto-run feature starts the DB2 Setup wizard
which determines the system language and starts the setup program for that
language.
4.Follow the DB2 Setup wizard's prompts. Help is available in the wizard to
guide you through the remaining steps.
Restriction: If you install a DB2 Runtime Client on a Windows operating
system, no other DB2 database products can be installed in the same path as
the client. Though the installation program does not prevent you from installing
DB2 database products in the same location as DB2 Runtime Clients, this
situation causes subsequent maintenance activities (such as applying fix
packs) to fail.
Note: The ACORD Demo utilized a default installation for the DB2 Runtime
Client, except for the installation directory. As defined previously, use the
<db2_runtime_client_home> as the installation directory to keep with the
documentation requirements.

116
IBM Software Supporting ACORD Insurance Standards
After completing this procedure, the product is now installed at the location you
specified during the installation. The default installation path for the first copy of a
DB2 client is <db2_runtime_client_home>,
This installation does not include product documentation. See the related links
for options for installing or accessing the DB2 Information Center.
After installing the DB2 Runtime Client, the next step is to configure it to access
remote DB2 servers, as covered in the next section about WebSphere Portal
Server Configuration, when the installation requires configuring the Runtime
Client to access remote databases.
5.3.4 IBM WebSphere Portal Server configuration
Installing and Configuring WebSphere Portal Server utilizes some of the previous
steps that have already been accomplish at this point. Because WebSphere
Process Server has been installed and configured, the WebSphere Portal Server
Installation utilizes the wps profile of the previous configuration of WebSphere
Process Server.
Installing with an existing instance of WebSphere Application
Server
This section provides information on installing IBM WebSphere Portal on an
existing instance of IBM WebSphere Application Server, ultimately the
WebSphere Application Server instance that is installed with WebSphere
Process Server.
Before you begin, you should review Planning for deployment, Supported
hardware and software for WebSphere Portal Version 6.0, Preparing your
operating system, and Choosing an installation source.
Note: The instructions in this section are from the IBM InfoCenter, however,
key items were modified where applicable:
http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index.jsp?topic=
/com.ibm.wp.ent.doc/wpf/inst_wp_exwas.html

Chapter 5. eForms + SOA Solution installation and configuration
117
To install a new version of WebSphere Portal on an existing instance of
WebSphere Process Server, follow these instructions.
Follow these steps:
1.Ensure that the installed WebSphere Process Server is at the supported level
before continuing. Refer to Supported hardware and software for more
information:
http://www-01.ibm.com/support/docview.wss?rs=2307&uid=swg27006205
2.Ensure that the installed WebSphere Process Server has the following
required features installed. See Table 5-5.
Important: If you attempt to install WebSphere Portal to an existing
WebSphere Process Server and have not used the WebSphere Portal media
to install WebSphere Process Server, the installation fails. For a successful
installation, follow the special instructions in the technote: Custom portal
install fails for a full WebSphere Process Server (WPS) Version 6.0.1.1
installation (not installed via Portal CDs) .
Attention: Resource paths in WebSphere Application Server configuration
can exceed the 256 character path length limitation of the Windows JDK™,
causing portlet installation or portal upgrades to fail. Therefore, we strongly
recommend that you keep your Application Server installation path short, for
example, use <process_server_home>. In particular, you should not install
portal into a profile inside the application server installation directory if the
default installation path C:\Program Files\IBM\WebSphere\AppServer has
been chosen. Use a shorter installation path or create a new profile outside
the main application server installation path, for example, in
C:\WebSphere\profiles\wps for portal installation.
Note: When installing on Linux, if you install WebSphere Portal into a directory
that does not have write permissions, the installation is not affected and
proceeds normally. This is because the installation is performed with the
Administrator user, which always has full permissions over files.

118
IBM Software Supporting ACORD Insurance Standards
Table 5-5 WebSphere Process Server required installed features
The components in Table 5-6 can be optionally installed on WebSphere
Application Server.
Table 5-6 WebSphere Application Server optional components
3.If you are installing on a machine with a firewall enabled, disable the firewall
before beginning the installation. If you do not disable the firewall and the
installation program detects it, a warning message displays during the
installation.
4.Choose one of the following options to start the installation program:
– Use the Setup disc:
If you have the Setup disc, perform the steps that are appropriate for your
operating system:
• Windows: Insert the Setup disc into the CD-ROM drive. The
installation program automatically starts when you insert the Setup
disc. If the autostart function is disabled, run the following command
from the root directory of the CD:
install.bat
– Access the downloaded product code:
If you downloaded the product code, perform the steps that are
appropriate for your operating system:
• Windows: Run the install.bat command from the install_root directory.
Product Features
IBM WebSphere Application Server
Network Deployment
Application Server
Administration
– Scripted Administration
– Administrative Console
Ant and Deployment Tools
– Deploy Tool
– Ant Utilities
Product Features
WebSphere Process Server Process Choreographer
– Configure a Sample Business Process
Container

Chapter 5. eForms + SOA Solution installation and configuration
119
5.Select the language for the installation and click OK. The welcome panel
displays.
6.If you want to view the WebSphere Portal information center, you can click
Launch Information Center, and the information center is opened in a
browser. Otherwise, click Next to continue.
7.Select I accept the terms in the license agreement. Click Next. The
installation program checks the machine for operating system and software
prerequisites.
8.Select Custom, and click Next.
9.Select the wps profile already existing WebSphere Process
Server/WebSphere Application Server ND. If the installation program does
not detect a WebSphere Application Server instance, but you know that it is
present on the machine, exit the install and pass the location using the
command line; for example: ./install.sh -W
was.undetectedWas="C:\WebSphere\profiles\wps\".
If you are installing to a node that is already under deployment manager
control, ensure that Install on a managed node is checked.
Click Next and the custom location is validated.
10.Enter the user ID and password for the WebSphere Application Server
administrator. These credentials are used to access WebSphere Application
Server with administrator authority after installation. These credentials are
only used to log in to WebSphere Application Server and are not related to
any other system access IDs. We recommend to stick with the wasadmin ID
and wasadmin password because this is configured later to use security
using Tivoli Directory Server as LDAP. Click Next.
11.Managed Node only: If you choose to install on a managed node, you must
have a profile created.
12.Specify the directory where you want to install WebSphere Portal, as the
directory recommended in Table 5-3 on page 72 <portal_server_home>. The
directory that you specify must NOT exist; it is created during the installation.
If you are installing on Windows, do not include periods (.) or special
characters in the installation path, and avoid using a long path name. Click
Next.
13.Enter the user ID and password for the WebSphere Portal administrator (we
recommend that you use
wpsadmin ID
and
wpsadmin password.
This is
changed later for using security with the Tivoli Directory Server Configuration
as LDAP is configured later in the process) and then click Next. This user ID
is used to access WebSphere Portal with administrator authority after
installation.

120
IBM Software Supporting ACORD Insurance Standards
14.Verify the components to be installed and click Next.
The installation program begins installing the selected components.
Throughout the installation and configuration process, the installation
program displays progress indicators for the different components.
15.When the installation is finished, the installation program displays a
confirmation panel listing the components that have been installed. Write
down the following information before clicking Finish:
– The port number that is used to access WebSphere Portal is displayed on
the confirmation panel. Write down the port number for use in verifying the
WebSphere Portal URL. This value is also stored in the WpsHostPort
property in the <portal_server_home>/config/wpconfig.properties file.
– Windows and Linux only: If you want to use the WebSphere Portal First
Steps, ensure that Launch First Steps is selected. From First Steps you
can access WebSphere Portal or read the documentation. If you are
installing on a UNIX system, the Launch First Steps check box is not
displayed.
16.Click Finish.
17.To verify that WebSphere Portal is running, open the following URL in a
browser: http://example.com:port_number/wps/portal, where example.com is
the fully qualified host name of the machine that is running WebSphere Portal
and port_number is the port number that is displayed on the confirmation
panel. For example, http://www.ibm.com:10038/wps/portal.
18.If the WebSphere Application Server where you installed WebSphere Portal
is part of a cell managed by WebSphere Application Server Network
Deployment, you can create a cluster of WebSphere Portal application
servers. Refer to Clustering and WebSphere Portal for more information.
Note: This user ID is only used to log in to WebSphere Portal and is not
related to any user IDs that are used to access the operating system.
Important: At this point, you are running with security enabled.
Note: The Security is only WebSphere security and not Tivoli Directory
Server LDAP enablement yet
Note: ACORD Demo did NOT utilize a cluster for testing purposes.

Chapter 5. eForms + SOA Solution installation and configuration
121
19.By default WebSphere Portal uses the internal HTTP transport within
WebSphere Application Server to handle requests, but if you have an external
Web server, such as IBM HTTP Server, you can configure WebSphere Portal
to use the Web server. Refer to Setting up a Web server with WebSphere
Portal for instructions.
20.When performing certain tasks, you might need to increase your JVM™ heap
size; see Setting the JVM max heap size for information about when and how
to increase your heap size.
Next steps
At this point, you can login and start using WebSphere Portal or you can continue
to extend your WebSphere Portal environment.
To learn how to login, refer to Logging in to your portal and to explore
WebSphere Portal, refer to Take a test drive of the site.
To transfer WebSphere Portal data to another supported database, such as
DB2, refer to Configuring databases.
To configure WebSphere Portal to connect to a user registry, such as LDAP or
another database, refer to Configuring security.
Configuring DB2 Enterprise Server database on Data Node
This section provides information on setting up DB2 to work with WebSphere
Portal.
Note: For the ACORD Demo, HTTP Server was configured and installed
along with the WebSphere Plug-in during the WebSphere Process Server
installation. It was configured to utilize WPS Profile as port 80. This is not
required to make the demonstration functional, but it would be a
recommended installation for a product system, as the InfoCenter
suggests. Refer to the following document to install the IBM HTTP Server
and WebSphere Webserver plug-in:
http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/topic/com.ibm
.wp.ent.doc/wpf/inst_ihs_main.html
Note: The instructions in this section are from the IBM InfoCenter, however,
key items were modified where applicable.
http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index.jsp?topic=
/com.ibm.wp.ent.doc/wpf/setup_db2.html

122
IBM Software Supporting ACORD Insurance Standards
Because the ACORD Demo requires you install a Data Node, the installation
requires using a remote DB2 server, which means you must manually create the
databases that are required by WebSphere Portal before performing WebSphere
Portal database transfer to work with DB2. If you use a local DB2, WebSphere
Portal can create and set up the required databases for you.
Creating remote databases
A remote database resides on a different machine than WebSphere Portal. If you
use a remote DB2 server, you must manually create the databases that are
required by WebSphere Portal. See Planning for DB2 for more information on the
database architecture recommendations. Before creating these databases, note
the following information:
6.0.1+ If the DB2 JDBC type 4 driver is used, only the instructions on the
remote server are required. You do not need to install the DB2 client software,
and you do not need to complete the steps related to the DB2 client.
The client software, DB2 Runtime Client, must be properly configured to
connect to the remote DB2 server instance, wpsinst.
These instructions assume that a remote DB2 server and DB2 Client are
already installed and running, based on the previous DB2 Enterprise Server
and DB2 Runtime Client installation/Configuration instructions.
These instructions assume that you use the DB2 RunTime Client to connect
to the remote DB2 server on the Data Node
1.Log in to the DB2 Enterprise Server Data Node Machine as the db2admin
user with sufficient database privileges.
2.Ensure that the user you are using for the JCR Database User has been
created, granted appropriate privileges, and has a password assigned to it. If
the user has not been created, refer to the Creating users section for
information on how to create users.
3.Initialize a DB2 command environment on the Data Node:
– Windows:
i.Open the DB2 command window.
Note: WebSphere Portal Version 6.0 does not support the DB2 JDBC Type
3 driver, also known as Net Driver.
Note: The instructions recommend a separate user, but in the
demonstration we used the default db2admin ID that was created and used
for all database access for all instances for ease of demoing.

Chapter 5. eForms + SOA Solution installation and configuration
123
ii.cd to the <db2_ese_home>\wpsinst directory and run the command
db2profile.bat or the instance that was dedicated to the portal server
databases.
4.Run the following command on the DB2 server machine to configure the DB2
database instance:
For DB2 Version 9:
db2 "UPDATE DBM CFG USING query_heap_sz 32768"
db2 "UPDATE DBM CFG USING maxagents 500"
db2 "UPDATE DBM CFG USING sheapthres 0"
5.Download the following bat file called DB2_Create_Portal_Databases.bat
(see Appendix A, “Additional material” on page 169 to obtain the file) and
store in the C:\temp directory, on the DB2 Enterprise Server Data Node
machine to create the necessary databases. In the same db2 command
window, cd to the C:\temp directory and run the bat file just created for the
WPSINST DB2 Instance.
6.Moving to the DB2 Runtime Client on the Web Node: Catalog the TCP/IP
node with the IP address of the remote database server from the DB2
Command Window, as follows:
db2 "catalog tcpip node demodbs remote swgdemodb2.raleigh.ibm.com
server 50001"
Where the following is true:
demodbs is the alias name of the Data Node
swgdemodb2.raleigh.ibm.com is the fully qualified host name of your Data
Node Machine
50001 is the DB2 Connection Service Port number listed in the services file
on the Data Node Machine. It is the port number listed under the follow
parameter in the services file which is the port number needed for
connections to the server from the Runtime Client.
db2c_WPSINST 50001/tcp
7.After running the CATALOG TCPIP NODE command, run the following
command:
db2 "TERMINATE"
Note: WPSINST was the one created in this demonstration.
Note: The alias name can contain one to eight characters.

124
IBM Software Supporting ACORD Insurance Standards
This clears db2 caching and the new node becomes available to use for the
next step.
8.On the DB2 Runtime Client on the Web Node: The next step is to catalog the
WebSphere Portal, JCR, Member Manager, Feedback and LikeMinds
databases to the remote DB2 Enterprise Server Data Node as follows:
Run the following commands in the DB2 Runtime Client DB2 Command
Window:
db2 "CATALOG DB WPSDB AS WPSDB AT NODE demodbs"
db2 "CATALOG DB CMDB AS CMDB AT NODE demodbs"
db2 "CATALOG DB LMDB AS LMDB AT NODE demodbs"
db2 "CATALOG DB FDBKDB AS FDBKDB AT NODE demodbs"
db2 "CATALOG DB WMMDB AS WMMDB AT NODE demodbs"
db2 "CATALOG DB JCRDB AS JCRDB AT NODE demodbs"
db2 "CATALOG DB CSTMDB AS CSTMDB AT NODE demodbs"
db2 "CATALOG DB RELEASE AS RELEASE AT NODE demodbs"
db2 "TERMINATE"
9.On the DB2 Runtime Client machine, test your remote connection by issuing
the following command in the DB2 command window:
db2 "CONNECT TO WPSDB user db2admin using password"
where the following is true:
db2admin is the Database Administrator user Id that was created on the Data
Node
password is password for the db2admin user id.
10.Restart your database server.
Transferring databases to DB2 Enterprise Server on Data Node
This section provides information on how to transfer your data between
databases using the configuration wizard. Follow these steps:
1.Start server1 and stop WebSphere Portal. See Starting and stopping
WebSphere Application Server and WebSphere Portal for instructions.
2.Start the configuration wizard window located in
<portal_server_home>\config\wizards\configwizard.bat
Note: See Configuring WebSphere Portal with the configuration wizard for
more information on how to start the configuration wizard.

Chapter 5. eForms + SOA Solution installation and configuration
125
3.In the Select the configuration task that you want to perform dialog box, select
Transfer Data to Another Database, and then click Next.
4.If the WebSphere Application Server global security is enabled... dialog box
appears, type the IBM WebSphere Application Server administrative user
name and password in the appropriate fields, and then click Next.
5.In the Source Database Type (Figure 5-24), select the database type as IBM
Cloudscape that you want to transfer from, and then click Next.
Figure 5-24 Source Database Type
Note: Passwords should not contain spaces.

126
IBM Software Supporting ACORD Insurance Standards
6.In the Target Database Type (Figure 5-25), select the database type as IBM
DB2 Universal Database that you want to transfer to, and click Next.
Figure 5-25 Target Database Type
7.In the Properties dialog box (Figure 5-26), review the properties in the image
and values for the database(s) that you are transferring to. Modify the values
for your environment and click Next. Repeat this step for each database you
are transferring.
Note: The values used next align with all of the previous parameters used
for this demonstration, and we recommend that you use the properties in
the following diagram.

Chapter 5. eForms + SOA Solution installation and configuration
127
Figure 5-26 IBM DB2 Universal Database Properties
8.The next step is to identify all the database properties. Follow the diagrams
and utilize the properties outline in the diagrams. Update the Database User
ID and Password, but keep the other properties the same. Click Next after
each of the properties are updated. Repeat this step for each domain that you
are transferring from the diagrams.

128
IBM Software Supporting ACORD Insurance Standards
CMDB is shown in Figure 5-27.
Figure 5-27 Community Database Properties for Data Transfer

Chapter 5. eForms + SOA Solution installation and configuration
129
CSTMDB is shown in Figure 5-28.
Figure 5-28 Customization Database Properties for Data Transfer

130
IBM Software Supporting ACORD Insurance Standards
JCRDB is shown in Figure 5-29.
Figure 5-29 Java™ Content Repository Database Properties for Data Transfer

Chapter 5. eForms + SOA Solution installation and configuration
131
LMDB is shown in Figure 5-30.
Figure 5-30 LikeMinds Database Properties for Data Transfer

132
IBM Software Supporting ACORD Insurance Standards
RELEASE is shown in Figure 5-31.
Figure 5-31 Release Database Properties for Data Transfer

Chapter 5. eForms + SOA Solution installation and configuration
133
WMMDB is shown in Figure 5-32.
Figure 5-32 Member Manager Database Properties for Data Transfer

134
IBM Software Supporting ACORD Insurance Standards
The final step before data transfer should look like Figure 5-33.
Figure 5-33 Final Step before Data Transfer
9.In the Running task dialog box, the status bar shows the progress of the
transfer. To view the log file for the transfer, click Open. When the transfer
has completed, click Next.
10.If the task runs successfully, the message The wizard ran the task
successfully is displayed. Click Finish to exit the wizard.
11.If the task runs with errors, the message The wizard ran the task with
errors is displayed. For more information, click Open Message File. To
perform additional configuration, click Run Wizard Again. Click Finish to exit
the wizard.
Note: JDBC Drivers have been created for use within WebSphere Portal
Server to access the Remote Databases.

Chapter 5. eForms + SOA Solution installation and configuration
135
Configuring security with Tivoli Directory Server on Data Node
This section provides information on how to configure your Tivoli Directory
Server (LDAP user registry) using the configuration wizard:
1.Start server1 and stop WebSphere Portal. See Starting and stopping
WebSphere Application Server and WebSphere Portal for instructions.
2.Start the configuration wizard window located in
<portal_server_home>\config\wizards\configwizard.bat
3.Switch to the configuration wizard window.
4.In the Select the task that you want to perform dialog box, select Enable
LDAP security and then click Next (Figure 5-34).
Figure 5-34 First Step before Enabling Security
Note: See Configuring WebSphere Portal with the configuration wizard for
information on how to start the configuration wizard.

136
IBM Software Supporting ACORD Insurance Standards
5.If the WebSphere Application Server global security is enabled... dialog box
appears, type the IBM WebSphere Application Server administrative user
name and password in the appropriate fields, and then click Next.
6.Enter the following additional parameters if security is enabled on the Disable
security settings continued... dialog box and then click Next:
– WebSphere Portal administer ID: wpsadmin
– Password: wpsadmin
– Confirm password: wpsadmin
– WebSphere Portal administer group: <leave blank>
– Member Manager password: <leave blank>
7.The wizard is ready to run the following task dialog box displays; click Next to
continue with the disabling security task.
8.Select the LDAP server that you intend to use for authentication from the list
and then click Next.
9.Enter the following parameters to connect WebSphere Portal to the LDAP
server and then click Next:
– Host name: swgdemodb2.raleigh.ibm.com
– Port: 389
– User name: cn=root
– Password: <your_password>
– LDAP suffix: dc=swgdemo, dc=com
10.Enter the following user parameters for authenticating with the servers and
then click Next:
– WebSphere Portal administer ID: uid=wpsadmin, cn=users, dc=swgdemo,
dc=com
– Password: <your_password>
– WebSphere Application Server administer ID: uid=wasadmin, cn=users,
dc=swgdemo, dc=com
– Password: <your_password>
– Bind distinguished name: uid=wpsbind, cn=users, dc=swgdemo, dc=com
– Password: <your_password>
Note: Passwords should not contain spaces and these are the id/pwd
combinations that were used during the original installation.

Chapter 5. eForms + SOA Solution installation and configuration
137
– User search filter: (&(uid=%v)(objectclass=inetOrgPerson)
11.Enter the following group parameters for authenticating with the servers and
then click Next:
– WebSphere Portal administrator group: cn=wpsadmins, cn=groups,
dc=swgdemo, dc=com
– Web Content Management administrators group: cn=wpsadmins,
cn=groups, dc=swgdemo, dc=com
– WebSphere Portal Server content administrators group: cn=wpsadmins,
cn=groups, dc=swgdemo, dc=com
– WebSphere Portal Server document reviewer group: cn=wpsadmins,
cn=groups, dc=swgdemo, dc=com
– Group search filter: (&(cn=%v)(objectclass=groupOfUniqueNames)
12.Enter the following group short name parameters and then click Next:
– Web Content Management administrators group: wpsadmins
– WebSphere Portal Server content administrators group: wpsadmins
– WebSphere Portal Server document reviewer group: wpsadmins
13.Enter the following Member Manager parameters and then click Next:
– User name: uid=wpsadmin, cn=users, dc=swgdemo, dc=com
– Password: <your_password>
14.Enter the LDAP user and group prefixes and suffixes and then click Next.
– LDAP User Prefix: uid
– LDAP User Suffix: cn=users
– LDAP Group Prefix: cn
– LDAP Group Suffix: cn=groups
15.Enter the following single sign-on parameters and then click Next:
– The domain name for all allowed single sign-on hosts: raleigh.ibm.com
– Does the single sign-on require an SSL connection: yes
– Enter a password to be used to encrypt LTPA keys: <your_password>
– Confirm password: <your_password>
– LTPA token expiration time in minutes: 120
Note: This window only displays if the database type is NOT Cloudscape.

138
IBM Software Supporting ACORD Insurance Standards
16.Enter the following node parameters for the users and groups in this
configuration and then click Next:
– User object class: inetOrgPerson
– Group object class: groupOfUniqueNames
– Group membership attribute: <Keep_Default>
– User base attributes: <Keep_Default>
– Minimum user attributes: <Keep_Default>
– Minimum group attributes: <Keep_Default>
17.Enter the following additional LDAP parameters and then click Next:
– Allow only qualified user names within the security domain: Yes
– Issue a warning if an application is installed with a permission that is
disallowed by the policy files: Yes
– Security cache timeout in seconds: 600
– Authentication protocol for RMI/IIOP requests: BOTH
18.Enter the following additional LDAP parameters and then click Next:
– Host name of the Web server handling HTTP requests: <Hostname if
used>
– Port: 80
– LDAP server response timeout in seconds: 120
– Reuse LDAP connections: Yes
– Ignore case when checking user names and passwords: Yes
– Enable Lookaside: No
19.The wizard is ready to run the following task dialog box displays with a list of
the configuration settings; click Next to continue with the enabling security
task.
20.If the task runs successfully, the message The wizard ran the task
successfully displays. Click Finish to exit the wizard or click Run Wizard
Again to perform additional configurations.
Note: If the task runs with errors, the message The wizard ran the task
with errors displays. For information, click View Log File. Fix the issue
that is causing the error and then rerun the task.

Chapter 5. eForms + SOA Solution installation and configuration
139
Security is enabled
After you have enabled security with your LDAP directory, you need to provide
the user ID and password required for security authentication on WebSphere
Application Server when you perform certain administrative tasks with
WebSphere Application Server. For example, to stop the WebSphere Portal
application server, you would issue the following command:
Windows: stopServer.bat WebSphere_Portal -user admin_userid -password
admin_password
5.3.5 IBM WebSphere Business Service Fabric - Foundation Pack
Configuration
Use this procedure to install IBM Business Services Foundation Pack using the
installation wizard. Installing IBM Business Services Foundation Pack using the
Installation Wizard section walks you step-by-step through the installation steps.
This procedure details a complete (default) installation, and it assumes that a
prior installation of WebSphere Business Services Fabric does not exist.
1.Insert the product CD labeled IBM WebSphere Business Services Fabric
Foundation Pack 6.0.2 into the CD-ROM drive. Select the preferred language
version from the drop down list of supported languages.
2.The installation wizard files are located in the Installers directory. Run the
installation wizard by double-clicking on the executable file for the platform.
Windows platform: install_fabric_win.exe
3.On the Language Selection panel:
– Select preferred language from the drop down box.
– Click OK.
4.From the Welcome panel, select Next to continue.
Note: The instructions in this section are from the IBM InfoCenter, however,
key items were modified where applicable.
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/topic/com.i
bm.ws.fabric.install.doc/foundationpkinstall/task/t_installing_fp_wi
zard.html
Note: At any point during the installation, you can cancel the installation and
restart it by running the installer.

140
IBM Software Supporting ACORD Insurance Standards
5.In the Software License agreement panel, you have to review and accept the
licensing terms to proceed. After reviewing the licensing terms, select the I
accept the terms in the license agreement radio button, and click Next.
6.Now the Select Install Features panel displays. Select Fabric Installation
Files and Fabric Runtime Components. Click Next button to continue.
– The Fabric Installation Files copy the WBSF installation artifacts to the
folder designated by the user.
– The Fabric Runtime components deploy Fabric runtime components into
WPS.
7.On the following Select Install Folder panel, accept the default installation root
directory for WebSphere Business Services Fabric, or specify a different
directory, <wbsf_foundation_home>, to install WBSF into the Where Would
You Like to Install field. Click the Next button to continue.
8.On the WebSphere Process Server Location panel, specify the WebSphere
Process Server Home Directory. You can accept the default installation path
as the WebSphere Process Server Home Directory, or specify the directory in
the Installation Directory field. Click Next to continue. The following step lists
the default paths for WPS installation:
Windows: <process_server_home>
In this step, the installation wizard checks for a supported WPS version in the
specified directory. After verifying the prerequisites, the wizard continues with
the next step in the installation process.
If you do not have a supported WPS version or the correct prerequisite
patches on your system, the wizard cannot proceed with the installation
process. You must click Cancel to stop the installation, make the required
changes, and restart the installation.
Note:
a.Deleting the default root directory and leaving the field empty
prevents you from continuing.
b.Non-ASCII special characters in directory names are not supported.
c.On Linux and UNIX platforms: Do not use symbolic links as the
destination directory. Symbolic links are not supported. Also, do not
use spaces in the installation directory path.
d.On Linux platforms: The installation directory path must be no longer
than 256 characters to successfully install the product.
e.On Windows platforms: The installation directory path must be no
longer than 60 characters

Chapter 5. eForms + SOA Solution installation and configuration
141
9.Next the WebSphere Process Server Profile panel displays. The "Profile"
drop-down box for the WebSphere Process Server profile name field should
be empty. The drop-down box lists all WPS profiles on the system. Select the
wbsf profile. Click Next to continue.
10.The next display is the Security Settings panel that requires you to enter your
current security configuration for WPS, with the following three options LDAP,
or None. Select LDAP. Click Next to continue.
11.The WebSphere Process Server Authentication Panel now displays.
– Enter the correct WPS username into the Username field.
– Enter the corresponding password into the Password field.
– Click Next to continue.
12.Next the JDBC Settings panel displays. Enter the Server Name and Port. In
the JDBC Driver Path field, specify the path to where your JDBC drivers are
installed in order to connect to the database. Click Next to continue.
13.On the JDBC Authentication panel, use the database administration ID and
password. Click Next to continue. The JDBC Username and password help
connect the JDBC to the database.
14.To set up WPS to send notifications to the administrator, you have to specify
the email account that should be used for this purpose. In the next Email
Server panel, specify the correct Host Name and the User Name in the
respective fields. Enter the corresponding password into the Password field.
Click Next to continue.
15.In the following Pre-Installation Summary panel, review the details of the
components to be installed, the amount of space they are to consume, and
where they are to be located on the system. If satisfactory, click Install to
install the product. If not, click Previous to change your specifications. The
installation wizard displays a progress bar to indicate that components are
being extracted and installed. At any point, you can cancel the installation and
restart it by running the installer. However, if you cancel the installation at this
point, you have to perform the uninstallation procedure to clean up any
residual artifacts before restarting the installation process.
16.At the end of the installation, the installation wizard provides a successful
installation panel with a summary of the components installed.
Note: Ensure that you have updated the WPS installation with the required
fix pack.

142
IBM Software Supporting ACORD Insurance Standards
Each of these panels identifies the log file to reference in order to
troubleshoot the problems. See the descriptions of relevant log files and refer
to the Uninstalling IBM Business Services Foundation Pack section of this
document for tips on troubleshooting your installation.
17.Click Done to close the installation wizard. If a successful installation panel
was displayed, the following IBM Business Services Foundation Pack
server-side components are installed:
– IBM Business Services Repository
– IBM Business Services Dynamic Assembler
– IBM Business Services Subscriber Manager
– IBM Business Services Performance Manager
– IBM Business Services Governance Manager
Configuring Security using LDAP
LDAP is an open protocol that provides access to directories in order to locate
people, organizations, and other resources. An LDAP directory holds information
describing users, applications, and other resources accessible from a network.
Organizations use it to store their user, password, and group membership
information in a single location so that changes like updating an e-mail address,
changing a password, and so on do not need to be made in different locations.
WebSphere Business Services Fabric federation capabilities enable integration
with an organization's LDAP database such that its LDAP users, those whose
information is stored in the LDAP directory, assimilate into the WebSphere
Business Services Fabric system and have the same interface to its business
services.
Note: If errors are detected during installation, other panels might be
displayed in place of the successful installation panel. Examples include
these possibilities:
Installation is complete with errors panel
Installation failed panel
Note: To install the IBM Business Services Foundation Pack Runtime and
Database components independently or on separate systems, which is what
this demonstration has used, follow these steps:
1.On the Select Install Features panel, select either Fabric Database or
Fabric Runtime Components, depending on which one is appropriate for
the system on which the you are installing the product.
2.Click Next and proceed with the rest of the installation similar to that for a
single system, enumerated previously.

Chapter 5. eForms + SOA Solution installation and configuration
143
WebSphere Business Services Fabric requires LDAP to be configured for a
proper production installation. However, a demonstration security version can be
installed that is useful for evaluation purposes only. WebSphere Business
Services Fabric also provides a bootstrap function that must be used to integrate
with an LDAP directory immediately after installing the former.
LDAP configuration for WebSphere Business Services Fabric
After you have configured WebSphere Application Server to use LDAP, you
need to follow these steps:
1.Register LDAP with WBSF. For this, go to:
http://<host>:<port>/fabric/bootstrap.jsp
– 1: Copy Settings - Enter WAS administrator Username and Password in
order to copy those settings to the LDAP binding. THE SOAP port settings
however need to be customized if it is on a non-standard port. You can
determine the port the server is using by accessing the admin console and
clicking on Application Server, name of the Server and then Ports. Find the
SOAP_CONNECTOR_ADDRESS entry, find the value for the port
associated with it and then enter it on the SOAP port field.
– 2: If you did not copy the settings, you need to enter the binding settings.
The settings, for example, could be set as follows:
• Hostname: Value A
• Port: Value B
• username: Value C
• Password: Value D
• Admin: Value F (note that for active directory, this is not a DN)
• Mapping data:
- a.BaseDN: Value E
- b.UserID: Value G. a)
- c.LastName: Value G b)
- d.EmailAddress: Value G. c)
- e.CompleteName: Value G d)
Now, test the connection and save the changes if the test was successful.
WBSF indicates success when settings are correct. Follow the login link and
log in as the user in Value F.
2.Set up administrative user: When you are logged into WBSF, you must select
your desired services. We recommend just to select them all.
LDAP provides the following capabilities:
a.Ability to run in Network Deployment mode so WBSF can be clustered.
b.Comprehensive password policy and management features.

144
IBM Software Supporting ACORD Insurance Standards
Recommended performance settings for WebSphere Business
Services Fabric in a production environment
The following settings are additionally recommended:
Disable diagnostic trace
Disable Performance Monitoring infrastructure
JVM configuration (minimum heap size: 1024)
Thread Pool Webcontainer settings
Datasource connection pool properties
Enable Dynamic Cache
5.3.6 IBM WebSphere Business Service Fabric - Insurance P&C Pack
Configuration
The WebSphere product stack uses Launchpad to aggregate various installation
related functions into a standardized main menu.
The Launchpad provides the following functionality:
1.Welcome: This consists of the information about the Content Pack you are
about to install, and a link to the product Web site.
2.Release Information: This page provides the Insurance Property and
Casualty Content Pack version 6.1 release information.
3.Prerequisite Information: This page provides the prerequisite information for
the installation, with links to those specific details.
4.Install Insurance P&C Content Pack: This page provides links to initiate the
product installations.
5.First Steps: This page provides the following details:
– Information Center: This provides the information on installing and using
the IBM WebSphere Business Service Fabric information center.
– Notices and Trademark Information: This provides information for the IBM
WebSphere Business Service Fabric information center.
The different installation options for the Insurance P&C Content Pack, and their
procedures are provided in the following sections.
Note: The instructions in this section are from the IBM InfoCenter, however,
key items were modified where applicable.
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp?t
opic=/com.ibm.ws.fabric.inspk.doc/inspcins/concept/c_installing_insp
c.html

Chapter 5. eForms + SOA Solution installation and configuration
145
Installation snapshot
The flowchart (Figure 5-35) is an overview of the complete installation procedure.
Figure 5-35 Installation Snapshot
Note: The launchpad is meant only for the Distributed Platforms. For z/OS®
systems you need to follow the instructions provided in the section, Installing
the Insurance P&C Content Pack on z/OS.
Is Custom
Specify the Installation path for CP
Specify the WebSphere Process Server location
Select the appropriate profile for the CP install
Verify the Pre-Installation summary
Select Install
Verify the installation
Yes
Accept the License Agreement
Welcome Window
Provide the WebSphere Business Services
Fabric authentication details
Select the Language from Language Selection dropdown
Select CP from the left navigation and click Install
IBM CP Pack 6.1 to commence install
Manually install the EAR files in
WebSphere Process Server
Manually import the FCA files into
WebSphere Business Services Fabric
Verify the installation
Verify that Automated
Install steps take place
with Files Only option
Unzip/Untar the
installation package
Select the install_{cp}_aix from
WBSFCP_CD_Image_Multiplatform-
private.zip
Select Launchpad.sh
Select Launchpad.exe
Linux/Sun Solaris
platform
AIX
platform
z/OS platform
All other platforms
Automated installation
Manual installation
Content Packs Installation Snapshot
Specify the Installation path for CP
Windows platform
No

146
IBM Software Supporting ACORD Insurance Standards
5.3.7 IBM WebSphere Transformation Extender configuration
The installation and configuration of the WebSphere Transformation Extender
and Transformation Extender SDK was installed by taking the default values from
the installation wizard. The <wtx_home> and <wtx_sdk_home> are the
installation directories.
5.3.8 IBM Lotus Forms Server configuration
The IBM Lotus Forms Server configuration is the main component to running
forms within the portal configuration or standalone. The following steps describe
how to install the Lotus Forms components so that forms can be eventually
utilized by the WebSphere Portal Server configuration.
Installing the API
The API is bundled as a self-extracting Windows executable file. To install the
API:
1.Double-click LFServer_30_API_Win32.exe. The InstallShield Wizard opens
and prepares the installation.
2.Select a language and click OK.
3.Click Next and read the license agreement.
4.Click I accept the terms in the license agreement then click Next.
5.In the Directory Name field, enter the directory in which to install the API
[<lotus_forms_api_home>], then click Next.
6.Choose an installation type, then click Next.
7.If you chose Custom installation: Select the features that you want to install,
then click Next.
8.If you want the Wizard to deploy the API to an existing WebSphere
Application Server or WebSphere Process Server:
a.Select the check box, then click Next.
b.Enter the location of the server, then click Next.
c.Enter the profile, forms, then click Next.
Note: The instructions in this section are from the IBM InfoCenter, however,
key items were modified where applicable.
http://publib.boulder.ibm.com/infocenter/forms/v3r0m0/index.jsp?topi
c=/com.ibm.help.forms.doc/API_Install_Guide/i_wfsa_g_using_the_api_w
ith_windows.html

Chapter 5. eForms + SOA Solution installation and configuration
147
9.Click Install.
The installation includes components for the C, Java, and COM development
environments, as well as the Java Streaming API.
The Classic APIs are installed in: <lotus_forms_api_home>. The Streaming API
is installed in: <lotus_forms_api_home>\redist\java.
The API installation also provides the installation files for IBM Lotus Forms
Server - Deployment Server. To install and configure Deployment Server, see
the Deployment Server Administration Manual.
Forms Services Platform installation and configuration
The IBM Lotus Forms Server - Forms Services Platform (hereafter referred to as
the Forms Services Platform) lets you extend the functionality of IBM Lotus
Forms products and integrate them with back-end systems.
The Forms Services Platform is the foundation of all the Lotus Forms integration
solutions. It provides an architectural style and tool kit that allows you to define
modules that can be connected together to integrate applications. These
modules are OSGi bundles that contain Java code (pipes) and configuration data
(pipelines). Some bundles also contain dependency information such as
database drivers, which can link the bundle to outside mechanisms (such as
log4j).
Furthermore, the modularity of the Forms Services Platform allows you to easily
extend the functionality of these applications. For example, you can use the
Forms Services Platform to integrate with IBM Lotus Forms Server - Webform
Server. You could also use the Forms Services Platform to connect WebSphere
Transformation Extender (TX) and Lotus Forms so that data can be mapped
between forms, databases, and Web services.
Note: If you are unsure about this option, do not select it. You can
manually deploy to a WebSphere server after installing the API. See Using
the API with WebSphere Application Server.
Note: The instructions in this section are from the IBM InfoCenter, however,
key items were modified where applicable.
http://publib.boulder.ibm.com/infocenter/forms/v3r0m0/index.jsp?topi
c=/com.ibm.help.forms.doc/forms_services_platform/fsp_g_manual_intro
duction.html

148
IBM Software Supporting ACORD Insurance Standards
The Forms Services Platform also includes Designer plug-ins that let you use the
IBM Lotus Forms Designer to generate TX maps from your form's instances and
schemas. Thereby significantly reducing any custom coding required to integrate
your forms with a third party database.
This manual contains the following major sections:
Understanding the Forms Services Platform: Explains how the Forms
Services Platform works.
Preparing your development environment: Explains how to set up your
integrated development environment (IDE) and install the Forms Services
Platform.
Extending the Forms Services Platform: Explains how to customize the
Forms Services Platform by creating pipes, configuring pipelines, compiling
pipes, and packaging your files. Also explains how to install the Forms
Services Platform SDK.
Using the Forms Services Platform samples: Explains how to deploy and use
the News Reader and TX sample pipelines.
Using Webform Server with the Forms Services Platform: Explains how to
use the Forms Services Platform with Webform Server.
Using the Designer in an integrated environment: Explains how to use the
Designer plug-ins to manage repository servers and map form instances and
schemas to TX maps.
Installing Webform Server on a single server
To install Webform Server on a single server:
1.Restart the server immediately before installing Webform Server.
2.Ensure that you are logged in as an administrator or root user.
3.Run one of the following installation programs:
– For Windows, LFServer_xxx_WebformServer_Win32.exe
4.Select the directory in which to install Webform Server. Do one of the
following choices:
– To accept the default directory, click Next.
Note: The instructions in this section are from the IBM InfoCenter, however,
key items were modified where applicable.
http://publib.boulder.ibm.com/infocenter/forms/v3r0m0/index.jsp?topi
c=/com.ibm.help.forms.doc/Webform_Server_Admin_Guide/i_wfsws_g_insta
lling_webform_server_on_a_single_server.html

Chapter 5. eForms + SOA Solution installation and configuration
149
– To set a different directory, click Browse, locate and select the directory
you want, click OK to confirm your selection, then click Next to continue.
5.Select the Webform Server components and features that you want to install.
Typically, if you are installing Webform Server on a single server, you would
install every component.
6.Next, select the type of installation that suits your needs:
Install Webform Server on a managed node (for use with WebSphere
Application Network Deployment), select Managed Nodes.
7.Indicate whether you are deploying the Translator component to WebSphere
Application Server. Do one of the following:
– To automatically deploy both the Translator component and the sample
servlet to WebSphere Application Server, select Deploy to WebSphere
Application Server and Deploy Sample Servlet.
– To automatically deploy to WebSphere Application Server, select Deploy
to WebSphere Application Server.
– To deploy with an alternate servlet runner or to manually configure
WebSphere Application Server, clear both options.
8.Next, select the Access Control Database type. If you select DB2, you must
provide the following database information:
a.Database name. The default database name is WS_ACDB.
b.Host IP and port. The default values are localhost and 50000.
i.Use the formsinst, db2 instance, and the host of the data node for this
param.
c.Username and password
Note: The default install locations are:
Windows: <lotus_forms_server_home>
Note: Pick forms wps profile when picking the profile to install Forms
server into.
Note: If you choose not to automatically deploy to WebSphere Application
Server, the install still includes the Translator files. However, your existing
WebSphere Application Server configuration is not changed.

150
IBM Software Supporting ACORD Insurance Standards
d.Browse to the location containing the db2jcc.jar DB2 driver.
<db2_runtime_home>\java
9.If you did not choose to install the Log Server component, specify the Log
Server host name and then click Next.
10.If you are deploying the Translator to WebSphere Application Server and
installing the Sample Servlet, complete steps 11 through 14 on page 151.
Otherwise, go to step 14 on page 151.
11.Specify where WebSphere Application Server is installed. Make one of the
following choices:
– To accept the default folder, click Next.
– To set a different folder, click Browse, locate and select the folder you
want, click OK to confirm your selection.
12.Next, provide the following WebSphere Application Server information:
Under Profile, ensure that the installer has displayed the correct profile name
for your WebSphere Application Server configuration. This profile is forms
from this demonstration:
a.Under Cell, ensure that the installer is displaying the correct cell name for
your WebSphere Application Server configuration.
b.Under Node, ensure that the installer has displayed the correct node name
for your WebSphere Application Server configuration.
c.Under Server Name, type the name you want to give to the Translator
server.
d.Under Application Name, type the name you want to give to the Translator
application, then click Next to continue.
If you chose to deploy the Sample Servlet, complete step 13. Otherwise go to
step 14 on page 151.
13.If you want to install the Sample Servlet, provide the following information:
Under Application Name, type the name of the Sample Servlet application.
This can be any name, as long as it is valid under WebSphere Application
Server.
Note: If your server has this setting defined, you can leave the DB2 driver
value blank, because this is inherited from the server.
Note: The default application name is: WebformSampleApp.

Chapter 5. eForms + SOA Solution installation and configuration
151
Under Application Context, type the context you want to give to the Sample
Servlet application.
14.Review the summary information and then click Install to start the installation.
The installer installs all Webform Server components in the directory that you
selected.
After you have installed Webform Server, you should test your installation.
5.3.9 IBM WebSphere Portal Server: Lotus Forms enablement
After the Lotus Forms components are installed, the next steps are to enable
WebSphere Portal Server to be able to utilize these forms components so that
forms can be used within the portal itself. Follow the steps outlined in this
developerWorks article for successful integration:
http://www.ibm.com/developerworks/lotus/library/forms-portal/
Note: The default context is: /Samples.

152
IBM Software Supporting ACORD Insurance Standards

© Copyright IBM Corp. 2009. All rights reserved.
153
Chapter 6.
eForms + SOA Solution
application installation and
configuration
The ACORD XForms PoT demonstration includes the front-end user interface
and back-end business services. The front-end is WebSphere Portal, which
works with Lotus WebForm server to display eForms which interact with the
insurance customer/agent. The back-end is a set of business services and
processes.
All of the business services and processes are deployed in WebSphere Process
Server (WPS); some of the services are deployed with WebSphere Business
Services Fabric (WBSF) runtime so as to utilizing the WBSF dynamic service
routing capability. The insurance common service uses WebSphere
Transformation Extender (WTX) to do transformation of XML messages, so WTX
and WPS server must be installed on the same OS. The Tivoli Directory Server is
used for security control of Portal and the PoT use cases.
6

154
IBM Software Supporting ACORD Insurance Standards
6.1 Database configuration
In the following sections we discuss the database configuration of the ACORD
POC demonstration utilizing DB2 9 pureXML capabilities.
6.1.1 Application database installation
There are seven tables (AGENT, NAGENT, FORMS, NFORMS, FORMTRACE,
NFORMTRACE, and FORMTRACK) in XFORM database. The tables (AGENT,
FORMS, and FORMTRACE) are used for ACORD process. The tables
(NAGENT, NFORMS, NFORMTRACE) are used for NAVA process. The tables
(NAGENT, NFORMS, FORMTRACK) are used for NAVA process.
There is an xformdb.ddl file that includes database and tables' definition. This file
is available for download via Appendix A, “Additional material” on page 169.
We can run this DDL (db2 -ivf xformdb.ddl) in DB2 command console to create
XFORM database and tables. See Figure 6-1.
Figure 6-1 xformdb.ddl file
6.1.2 Set submitting URL for sample forms
There are some template forms for the demonstration environment. We need to
customize some information inside those template forms. For example, if
ACORD template form and NAVA template form are separately
forms.txt.001.xml and nforms.txt.001.xml.
Then for ACORD form in form.txt001.xml, we should change the action
properties of submission element of forms according the Gateway Service
endpoint. For example: the red color word should be replaced in this XML section
<xforms:submission action=http://FORMS_HOSTNAME:FORMS_PORT
NUMBER/ViewerChannelServlet/ViewerChannelServlet id=doGateWayExport
mediatype=application/soap+xml; action=process method=post/> with the action
endpoint referring to the 3.1->PCSHistoryFormViewPortlet->GateWayService
Endpoint:http://<host>:<port>/GatewayServiceWeb/sca/GatewayServiceInterfac
eExport.

Chapter 6. eForms + SOA Solution application installation and configuration
155
For NAVA form in nforms.txt.001.xml, we should change the online action
properties of submission element with 3.1-><nava proxy servlet context>/online
and change the offline action properties of submission element with 3.1-><nava
proxy servlet context>/offline.
Here are the endpoint samples.
ACORD
These are samples for ACORD.
online
http://<yourgatewayserviceendpoint>/GatewayServiceWeb/sca/GatewayServic
eInterfaceExport
offline
http:// <your servlet
endpoint>/ViewerChannelServlet/ViewerChannelServlet
NAVA
These are samples for NAVA.
online
http://<yourservletendpoint>/wps/PA_1_QB0RLKG10GFIE02T2MLS5K2000/FormPr
ocessServlet?channel=online
offline
http://<yourserveletendpoint>/wps/PA_1_QB0RLKG10GFIE02T2MLS5K2000/FormP
rocessServlet?channel=offline
6.1.3 Import Database information
There is some initial data that should be imported to the AGENT, NAGENT,
FORMS, and NFORMS tables. We put the sample data in some txt files. The
agent.txt is for AGENT table, nagent.txt is for NAGENT table.
As shown in Figure 6-2 and Figure 6-3, we can use the DB2 Control Center to
easily import AGENCY data into the AGENCY table. The agency.txt file is
available for download via Appendix A, “Additional material” on page 169.

156
IBM Software Supporting ACORD Insurance Standards
Figure 6-2 XFORM Tables

Chapter 6. eForms + SOA Solution application installation and configuration
157
Figure 6-3 Import table window
6.2 Configuration in WebSphere Process Server
In the next section we discuss the approach and steps needed to configure
WebSphere Process Server to utilize all the applications developed to fully
implement the ACORD Demo.
6.2.1 Configuration data source
We need to configure WebSphere data source to get our applications be able to
connect to our DB2 server.

158
IBM Software Supporting ACORD Insurance Standards
6.2.2 Procedure
We need to perform the following steps to get the data source ready:
1.Create DB2 JDBC Provider.
Go to WebSphere Application Server console → Resource → JDBC
Provider.
We need to select the database type, provider type and implementation type
as shown in Figure 6-4.
Figure 6-4 Create new JDBC provider window

Chapter 6. eForms + SOA Solution application installation and configuration
159
2.Create DataSource.
Go to Resource → JDBC Providers → <DB2 Provider> → Datasource:
On the configuration panel (Figure 6-5), we need to set the following
parameters:
– Name: xform
– JNDI Name: jdbc/xform
– Database Name: xform
– Driver Type: 4
– Server Name: <data_node_hostname> [Data Node URL:
swgdemodb2.raleigh.ibm.com]
– Port: <instance_port_number> [DataNode DB instance Port Number]
Figure 6-5 Configurations panel
3.Set JDBC lib path.
Go to Environment → WebSphere Variable:
We need to set the JDBC lib path here (Figure 6-6).
DB2UNIVERSAL.JDBC.DRIVER.PATH= <db2_runtime_client_home>
[From the WebNode] .
Figure 6-6 DBUNIVERSAL.JDBC.DRIVER.PATH

160
IBM Software Supporting ACORD Insurance Standards
6.3 Configuration in WebSphere Business Service
Fabric
The business service metal data, such as service interface, endpoint, service
policy, are modeled in Fabric Project, which can be exported/imported from/into
WBSF in the form of Fabric Content Archive (FCA) file. In our PoT demonstration.
we have created two Fabric Projects for ACORD and NAVA. To configure the
Fabric project, we just need to import the two exported FCA into WBSF.
6.3.1 Import the eForm + SOA Fabric project that utilizes the P&C
Content Pack
In this solution, we created Fabric projects in WBSF composite studio. We can
use Fabric Web admin console to import the created Fabric projects. Here are
the steps:
1.Log on to Fabric Web admin console with the URL:
http://fabric_host:port/fabric
2.Go to My Service=> Governance Manager=>Configure Projects. Click Create
Project button to create a Business Service project in WBSF whose name is
AcordFormPoT. See Figure 6-7.
Figure 6-7 Configure Projects window

Chapter 6. eForms + SOA Solution application installation and configuration
161
3.Go to Configure Projects. Click AcordFormPoT project.
In the Namespace Tab, create a schema name space
http://www.ibm.com/acord/pot/assertions#. See Figure 6-8.
Figure 6-8 Configure Namespaces 1 window
4.Click Save.
5.Create an instance name space http://www.ibm.com/acord/pot/instances# in
WBSF. See Figure 6-9.

162
IBM Software Supporting ACORD Insurance Standards
Figure 6-9 Configure Namespaces 2 window
6.Switch to Governance Manager=>Import/Export. The Governance
Manager is a link in the left navigation (not shown). On the Import Tab
(Figure 6-10), browse the ACORD Fabric archive file and NAVA Fabric archive
file to import. Make sure that the import finishes successfully.
Figure 6-10 Import/Export

Chapter 6. eForms + SOA Solution application installation and configuration
163
6.3.2 Further details
For more detailed steps for creating WBSF projects and importing contents, refer
to the Governance Manager Section of the WBSF InfoCenter.
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topi
c=/com.ibm.ws.fabric.tools.doc/governancemanager/concept/c_gm_overview.
html
6.4 Configuration in WebSphere Portal server
Portal provides the major user interface for our customers. In order to get Portal
run to support the multi-tenants feature and get integrated with the Lotus
WebForm Server, we need to perform several configurations.
6.4.1 Virtual Portal configuration
In this section, we perform the Virtual Portal configuration:
1.Create ACORD Virtual Portal:
a.Create a virtual Portal named pot for the ACORD case.
b.Deploy the ACORD case portlets on the pot portal and grant group
agents

to access them.
2.Create NAVA Virtual Portal:
a.Create a virtual Portal named nava for the NAVA case.
b.Deploy the NAVA Portlets on the nava portal and grant group
agents
and
customers
to access them.
6.4.2 WebForm Server API configuration
For the common WebForm server API configuration (see Figure 6-11), we can
refer to Lotus form InfoCenter.
http://publib.boulder.ibm.com/infocenter/forms/v3r0m0/index.jsp

164
IBM Software Supporting ACORD Insurance Standards
Figure 6-11 Configuring WebSphere Application Server to Access the API
6.5 Deploy service projects
In our PoT demonstration. there are some service projects which contain the
implementation of back-end business services and processes. We need to
deploy them to WBSF server or WPS server.
6.5.1 Deployment steps
Perform the following deployment steps:
1.Copy all jars in the lib folder to <portal_server_home>\lib\, and restart WPS.
2.Copy maps folder under C:\ of the system where WTX is installed.
3.Open the WBSF Web admin console, and import the necessary project FCA
files. Import AcordFormPoT-owl.zip first, and then import
NAVAFormPoT-owl.zip, because the NAVA FCA depends on Acord FCA.
4.Deploy all the services and processes EARs to the WPS server.
5.Deploy all the WBSF EARs to the WPS server where WBSF runtime is
installed.
6.Copy Question.xfdl to C:\ of the system where WPS server is installed.

Chapter 6. eForms + SOA Solution application installation and configuration
165
6.5.2 ACORD projects
Listed in Table 6-1 are the major projects for the ACORD demonstration.
Table 6-1 ACORD major demonstration projects
Project Name Description Deployment Comments
GatewayService A facade proxy service for all
ACORD Forms submissions
Deploy to WBSF server as
normal
FormProcessingService A SCA module to handle form
processing flow
Deploy to a same WPS server
with GatewayService
ApplicationPersistenceService Service that persists an ACORD
message into form repository
Deploy to WPS server as normal
ContextEvaluationService This service evaluate an ACORD
XForms model according to
business rule, and decide if
additional information is needed
in the model
Deploy to WPS server as norma
FormAuthenticationService This service performs
authentication against the user
contained in a XForms model
Deploy to WPS server as normal
CommercialAutoBusinessServic
e
The fake service used to
simulate Commercial Auto
insurance business service
Deploy to WPS server as normal
PersonalInlandMarineBusinessS
ervice
The fake service used to
simulate Personal Inland Marine
insurance business service
Deploy to WPS server as normal
FormRepositoryService The service is used to configure
Form Repository information and
LDAP user registry information
Deploy to WPS server as normal
FormPopulateService This service populate an empty
Form template with given
XForms data model, and creates
a form filled with data
Deploy to WPS server as normal
FormPrePopulateService This service populate an empty
Form template with agency
information
Deploy to WPS server as normal
FormAuthorizationService This service performs
authorization against the user
contained in a XForms model
Deploy to WPS server as normal

166
IBM Software Supporting ACORD Insurance Standards
6.5.3 Deploy Portal projects
In this section are the major projects for the ACORD demonstration.
Create pages as in Figure 6-12, and deploy the Portlets on pages as Table 6-2.
Figure 6-12 Major projects
Table 6-2 Deployment of Portlets
PCSServiceWar Acord online portlets Deploy to Portal Server
PCSHistoryWar Acord workplace portlets Deploy to Portal Server
PortletUtilProject Util projects for portlet projects
PrePopJavaClient Prepop service Java client
TraceJavaClient Acord trace service Java client
AboutUSPortlet About us portlet project Deploy to Portal Server
ContactUSPortlet Contact us portlet project Deploy to Portal Server
HomePagePortlet Home page portlet project Deploy to Portal Server
ViewerChannelServlet The offline proxy servlet project Deploy to WPS Server
FormTraceModule This service use for store form
and record form status.
Deploy to WPS server as normal
Project Name Description Deployment Comments
Page Portlet Permission group
Home HomePagePortlet Agents, customers
Properties and Casualty PCSFormsListPortlet
PCSFormViewPortlet
PCSFormIntroPortlet
Agents
PCS Workplace PCSHistoryListPortlet
PCSHistoryFormViewPortlet
PCSHistoryFormIntroPortlet
Agents
About Us AboutUSPortlet Agents, customers
Contact Us ContactUSPortlet Agents, customers

Chapter 6. eForms + SOA Solution application installation and configuration
167
Modify the Portlets configuration parameters as shown in Table 6-3.
Table 6-3 Portlets configuration parameters
Portlet Parameters' name/value
PCSFormsListPortlet PrePopulate Service EndPoint:
http://<web_node_url>:<port>/PrePolulateModuleWeb/sca/PrePopula
teExport
Portal Server Host and Port:
http://<web_node_url>:<port>
PCSFormViewPortlet GateWay Service Endpoint:
http://<web_node_url>:<port>/GatewayServiceWeb/sca/GatewayServi
ceInterfaceExport
PrePopulate Service Endpoint:
http://<web_node_url>:<port>/PrePolulateModuleWeb/sca/PrePopula
teExport
LDAP Server Host: <ldapserver ip address> [data node url:
swgdemodb2.raleigh.ibm.com]
LDAP Server Port: <ldap server port> [389]
LDAP Server User: <ldap instance admin user> [cn=root]
LDAP Server Password: <ldap instance admin password>
PCSHistoryListPortlet GateWay Service Endpoint:
http://<web_node_url>:<port>/GatewayServiceWeb/sca/GatewayServi
ceInterfaceExport
Trace Service Endpoint:
http://<web_node_url>:<port>/FormTraceModuleWeb/sca/FormTraceSe
rviceExport1
Portal Server Host and Port: http://<web_node_url>:<port>
PCSHistoryFormViewPortlet GateWay Service Endpoint:
http://<web_node_url>:<port>/GatewayServiceWeb/sca/GatewayServi
ceInterfaceExport
Trace Service Endpoint:
http://<web_node_url>:<port>/FormTraceModuleWeb/sca/FormTraceSe
rviceExport1

168
IBM Software Supporting ACORD Insurance Standards

© Copyright IBM Corp. 2009. All rights reserved.
169
Appendix A.
Additional material
This book refers to additional material that can be downloaded from the Internet
as described below.
Locating the Web material
The Web material associated with this book is available in softcopy on the
Internet from the IBM Redbooks publications Web server. Point your Web
browser at:
ftp://www.redbooks.ibm.com/redbooks/SG247649
Alternatively, you can go to the IBM Redbooks publications Web site at:
ibm.com/redbooks
Select the Additional materials and open the directory that corresponds with
the IBM Redbooks publications form number, SG247649.
A

170
IBM Software Supporting ACORD Insurance Standards
Using the Web material
The additional Web material that accompanies this book includes the following
files:
File name Description
users.ldif Demo directory file
DB2_Create_Portal_Databases.bat Bat file of DB2 commands
xformdb.ddl Includes database and tables' definition
agency.txt Sample data in the agent.txt is for
AGENT table
How to use the Web material
Create a subdirectory (folder) on your workstation, and unzip the contents of the
Web material zip file into this folder.

© Copyright IBM Corp. 2009. All rights reserved.
171
Related publications
The publications listed in this section are considered particularly suitable for a
more detailed discussion of the topics covered in this book.
Online resources
These Web sites are also relevant as further information sources:
Directory Server, Version 6.2 - Considerations before you install on AIX,
Linux, Solaris, and HP-UX systems:
http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm
.IBMDS.doc/install09.htm#shield
Installing and configuring WebSphere Process Server:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?t
opic=/com.ibm.wsps.602.ins.doc/welcome_wps_ins.html
Installing DB2 clients (Windows):
http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/
com.ibm.db2.udb.uprun.doc/doc/t0007315.htm
Installing with an existing instance of WebSphere Application Server:
http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index.jsp?topic=
/com.ibm.wp.ent.doc/wpf/inst_wp_exwas.html
WebSphere Process Server detailed system requirements:
http://www-01.ibm.com/support/docview.wss?rs=2307&uid=swg27006205
Configuring Web servers:
http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/topic/com.ibm.wp
.ent.doc/wpf/inst_ihs_main.html
Creating databases and users for DB2:
http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index.jsp?topic=
/com.ibm.wp.ent.doc/wpf/setup_db2.html
Installing IBM Business Services Foundation Pack interactively:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/topic/com.i
bm.ws.fabric.install.doc/foundationpkinstall/task/t_installing_fp_wi
zard.html

172
IBM Software Supporting ACORD Insurance Standards
WebSphere Business Services Fabric, Version 6.1 - Installation overview:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp?t
opic=/com.ibm.ws.fabric.inspk.doc/inspcins/concept/c_installing_insp
c.html
Using the API With Windows:
http://publib.boulder.ibm.com/infocenter/forms/v3r0m0/index.jsp?topi
c=/com.ibm.help.forms.doc/API_Install_Guide/i_wfsa_g_using_the_api_w
ith_windows.html
Forms Server 3 - Forms Services Platform - Introduction:
http://publib.boulder.ibm.com/infocenter/forms/v3r0m0/index.jsp?topi
c=/com.ibm.help.forms.doc/forms_services_platform/fsp_g_manual_intro
duction.html
Installing Webform Server on a Single Server:
http://publib.boulder.ibm.com/infocenter/forms/v3r0m0/index.jsp?topi
c=/com.ibm.help.forms.doc/Webform_Server_Admin_Guide/i_wfsws_g_insta
lling_webform_server_on_a_single_server.html
Integrating IBM Lotus Forms with WebSphere Portal to create a form-centric
application:
http://www.ibm.com/developerworks/lotus/library/forms-portal/
Introduction to IBM Business Services Governance Manager:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?t
opic=/com.ibm.ws.fabric.tools.doc/governancemanager/concept/c_gm_ove
rview.html
IBM Lotus Forms 3 information center:
http://publib.boulder.ibm.com/infocenter/forms/v3r0m0/index.jsp
How to get IBM Redbooks publications
You can search for, view, or download IBM Redbooks publications, IBM
Redpaper publications, Technotes, draft publications, and Additional materials,
as well as order hardcopy IBM Redbooks publications, at this Web site:
ibm.com/redbooks

Related publications
173
Help from IBM
IBM Support and downloads
ibm.com/support
IBM Global Services
ibm.com/services

174
IBM Software Supporting ACORD Insurance Standards

© Copyright IBM Corp. 2009. All rights reserved.
175
Index
A
ACCORD XFDL form 57
ACORD Application Demo 66
ACORD Automobile Loss Notice 10
ACORD eForms 2
ACORD form 8
ACORD Forms and SOA runtime environment 32
ACORD Forms SOA Demo 34
ACORD Forms submission 58
ACORD Gateway Service 58
ACORD Insurance Standards eForms 68
ACORD Loss Notice form 11
ACORD Lotus Form data 15
ACORD major demo projects
AboutUSPortlet 166
ApplicationPersistenceService 165
CommercialAutoBusinessService 165
ContactUSPortlet 166
ContextEvaluationService 165
FormAuthenticationService 165
FormAuthorizationService 165
FormPopulateService 165
FormPrePopulateService 165
FormProcessingService 165
FormRepositoryService 165
FormTraceModule 166
GatewayService 165
HomePagePortlet 166
PCSHistoryWar 166
PCSServiceWar 166
PersonalInlandMarineBusinessService 165
PortletUtilProject 166
PrePopJavaClient 166
TraceJavaClient 166
ViewerChannelServlet 166
ACORD PCS message 55
ACORD PCS XML structure 19
ACORD Web application 73
ACORD XForms 52
ACORD XForms model 60
ACORD XForms model schema 60
ACORD XForms PoT demo 153
agency name 10
agent 9
agent content 57
APPINST 77
Application Scheduler Configuration 108
ApplicationReview service 51
architecture design 49
Authenticated Clickwrap ID 57
Authenticated Clickwrap signature 57
Authentication and Authorization service 58
authentication service 50
authorization service 50
Automatic Service Routing, Discovery, and
Mediation 6
Automobile Loss Notice 8
B
back-end systems 29
BPEL 6
Build Map button 16
build rule scenarios 43
Business Function 6
Business Process Choreographer Configuration
107
business rule based context evaluation 49
business rule component 51
business rules 32, 46
Business Services 6
Business Services Dynamic Assembler 142
Business Services Foundation Pack Runtime 142
Business Services Governance Manager 142
Business Services Performance Manager 142
Business Services Repository 142
Business Services Subscriber Manager 142
C
Command Server dialog 18
Commercial Auto scenario 38
Commercial Business Auto Application service 60
Commercial Business Auto Application through
Portal Channel 32
Commercial Business Auto Application through
Viewer Channel 32
Common Event Infrastructure (CEI) 106

176
IBM Software Supporting ACORD Insurance Standards
Common Event Infrastructure (CEI) Configuration
105
comprehensive library 57
customer level authorization 33
D
data integration solution 56
Data Node 5, 67, 70, 73
data structures 6
Data Zone 67
Database Configuration 109
databases 57
Datasource connection pool properties 144
DB2 9 database 23
DB2 9 pureXML 2, 7, 154
DB2 9.5 9
DB2 call 20
DB2 Client and Enterprise Server 66
DB2 Command Editor 27
DB2 Command Line Editor 9
DB2 Enterprise Server Edition w/ pureXML 69, 73
DB2 pureXML 6
DB2 Runtime Client 69, 114
DB2 XQuery 10, 27
db2xmlese.lic 76
DBLOOKUP 19
demo scenarios 32
deployment decision 103
deployment manager profile 94
developer workstation 4, 8
developerWorks 70
developerWorks article 151
Development Environment solution 29
diagnostic trace 144
Directory Services Markup Language 82
Dynamic Cache 144
E
EDI 56
eForm controls binding 54
eForm designer 55
eForms 1, 5
enterprise applications 57
F
Fabric Content Archive 160
facade proxy service 58
FCA 160
First Notice of Loss file 15
form 137 46
Form Processing Service 59
Form Processing service 61
form processing service 50
form.txt001.xml 154
FORMINST 77
Forms data model 61
Forms Server Platform SDK 69
Forms Services Platform 147
Foundation Pack 69
G
Gateway Service 50
GET FilePath 17
H
HIPAA 56
I
IAA/IIW 2
IBM Business Services Foundation Pack 139
IBM HTTP Server 66, 68
IBM Insurance Application Architecture/Insurance
Information Warehouse 2
IBM Lotus ACORD Forms 4–5
IBM Lotus Form Viewer 52
IBM Lotus Forms Server 69, 146
IBM Redbooks publications Web site 172
Contact us xiv
IBM SOA software stack 6, 67
IBM Tivoli Directory Integrator Administration and
Monitoring Console 82
IBM WebSphere Application Server - Network
Deployment 69
IBM WebSphere Business Service Fabric 69
IBM WebSphere Business Service Fabric -
Foundation Pack 73
IBM WebSphere Portal Server 69
IBM WebSphere Process Server 69
Instance Administration Tool 84
Insurance Business Services 50
Insurance P&C Pack 69
Insurance Property and Casualty Content Pack 144

Index
177
J
JDBC lib path 159
jdbc provider 114
JVM configuration 144
L
LDAP directory 142
legacy 57
legal entities 6
license subdirectory 84
Life and Annuity messaging XML 2
Linux platforms 92
Lotus ACORD Forms 7
Lotus Form API 57
Lotus Form Viewer 59
Lotus Form Viewer Channel 49
Lotus Forms 2, 8
Lotus Forms Designer 10
Designer mode 10
Source mode 10
Viewer mode 10
Lotus Forms Designer 3.0 9
Lotus Forms Server 66, 87, 146
Lotus Forms Viewer mode 10
Lotus WebForm server 153
low-level infrastructure view 67
M
mainframe 57
Member Manager parameters 137
messaging systems 57
metadata 6
Microsoft Windows 2003 Enterprise Server 73
O
Offline Form Service 34
Offline Form service 40
Online Form Service 34
OSGi bundles 147
P
P&C 2
Performance Monitoring infrastructure 144
Personal Inland Marine Application through Portal
Channel 32
Personal Inland Marine Application through Viewer
Channel 32
Personal Inland Marine Forms 35
Policy ID 9
policy number 10
portal window 34
portal yields 34
PoT use cases 153
Pre-Installation Summary panel 141
Process Insurance Service 51, 60
production environment 70
Profile Summary 111
Profile wizard graphical user interface 94
Proof of Concept 5
Property & Casualty Content Pack 2
Property & Casualty/Surety messaging XML 2
R
Rate Quote and Issue application 63
Record Quote business service interface 63
Rule Engine 6
Run Map button 16, 18
S
second map output card 19
security considerations 49
Service Component Architecture Configuration 104
service-oriented architecture 1, 5
Signature Pad signature 57
Silanis signature 57
SOA Enterprise Solution 1
SOA infrastructure 39
SWIFT 56
T
template based eForm population 49
Thread Pool Webcontainer settings 144
Tivoli Directory Server 66, 69, 73
Tivoli LDAP User registry 60–61
Transformation Engine 55
Transformation Extender SDK 146
U
UNIX platforms 92
use case 41, 43
V
vendors 6
Viewer mode 10

178
IBM Software Supporting ACORD Insurance Standards
VMWare image 3, 9
VMWare Snapshot 10
W
WBSF 2, 6, 62, 160
WBSFINST 77
Web Administration Tool 82
Web Node 5, 67, 70
Web Portal 6
Web Portal Channel 49
Web Services 6
Web Zone 67
WebForms Server 69
WebSphere Application Network Deployment 149
WebSphere Application Server global security 136
WebSphere Application Server Network
Deployment 89
WebSphere Business Service Fabric 6
WebSphere Business Service Fabric - Foundation
Pack 87
WebSphere Business Service Fabric information
center 144
WebSphere Business Service Fabric Server 66
WebSphere Business Services Fabric 2, 139, 153
WebSphere Business Services Fabric federation
142
WebSphere Fabric 5
WebSphere Portal 5
WebSphere Portal Server 6, 66, 87, 146
WebSphere Process Server 5–6, 66, 87, 153
WebSphere Process Server Client 92
WebSphere Process Server Sample applications
93
WebSphere Transformation Extender 2, 4, 7, 14,
55, 62, 69, 146, 153
WebSphere Transformation Extender Designer 8.2
9
WebSphere Transformation Server 66
welcome portal window 34
Windows platforms 92
Workflow Management 6
Workflow Process 6
WPSINST 77
WTX 2, 9, 56
WTX ACORD Pack 2
WTX ACORD Pack demo map 19
WTX Designer 9
WTX Designer 8.2 15
X
XForm Transformation Engine 49
xformdb.ddl file 154
XForms model 50, 54
XML 56
XML Storage 6
XML Transformation 6
XQuery 9

(0.2”spine)
0.17”<->0.473”
90<->249 pages
IBM Software Supporting ACORD Insurance Standards



®
SG24-7649-00 ISBN 0738432431
INTERNATIONAL
TECHNICAL
SUPPORT
ORGANIZATION
BUILDING TECHNICAL
INFORMATION BASED ON
PRACTICAL EXPERIENCE

IBM Redbooks are developed by
the IBM International Technical
Support Organization. Experts
from IBM, Customers and
Partners from around the world
create timely technical
information based on realistic
scenarios. Specific
recommendations are provided
to help you implement IT
solutions more effectively in
your environment.
For more information:
ibm.com/redbooks
®
IBM Software Supporting
ACORD Insurance Standards
IBM supports ACORD
standards with its
middleware
IBM capabilities
demonstrate
enterprise
integration and
implementation of
ACORD Standards
IBM SOA Product
Portfolio supports
ACORD eForms and
Messaging
This IBM Redbooks publication helps you design and create demonstrations
or solutions that meet ACORD insurance standards with minimal application
coding. If you are not interested in creating such demonstrations yourself, we
show you two and provide you with contacts to show those demonstrations.
ACORD has published and maintains insurance industry standards. The two
most complete and often used standards are ACORD eForms and ACORD
messaging. ACORD eForms includes hundreds of electronic forms, which can
be used as-is with the Lotus Forms Viewer or modified slightly for use with
the IBM Lotus Forms Server to support straight-through processing
scenarios. ACORD messaging formats can be tailored to the needs of
individual insurance companies by using industry supplied tools.
This book shows you how to use IBM tools and tool content such as Lotus
ACORD Forms, WebSphere Transformation Extender ACORD Pack, and DB2
pureXML to minimize efforts to build and maintain ACORD solutions. The
solutions used in this book are available from the authors as demonstrations.
This can help IBM clients understand both the value of using ACORD
standards and the value of using IBM products that already incorporate these
standards.
We review both developer and run-time environments. We do this to
maximize the discussion potential for both open and industry standards.
The run-time environment provides a demonstration utilizing ACORD eForms
(Lotus Forms) and the IBM SOA software stack to produce a seamless
showcase of eForms interaction using a Workflow (BPEL) engine with
Business Rules. WebSphere Business Service Fabric is also utilized to
showcase how a service call can be mitigated into a business service call.
Back cover
First page image
We are pleased to offer a download of this document free of charge.
Files available for download:
  • a representative PDF of the primary file (contains all the relevant information for most users)
To obtain the file, please enter the "captcha" below and click the Download button.
Avoid entering CAPTCHAs! Sign In or Create a Free Account.

Challenge image
  • Please enter letters and numbers only; no spaces.
  • Cannot read this one? Click the image.
  • Difficulty with captchas? Contact us with the URL of this page and we will email it to you.