Using IBM Workplace Forms to consume and expose

Using IBM Workplace Forms to consume and expose web services Harry Puri TPC-4783 A Program Technical Track SOA Roadmap Entry Points. People

Agenda Introduction – Description W 3 C XForms – XForms Fundamentals – XForms Document Structure / Architecture IBM Workplace Forms and SOA – Enterprise Solution Requirements and Business Challenges – Watch out for Forms Solution Stove-Pipes – Enterprise E-Form Strategies – Componentization and Reuse – Loose Coupling – Composite Forms Applications 2

“More than 80% of the processes in public and private businesses depend on forms. ” - IDC Typical Form-Driven Processes – Health & Safety compliance processes – Threat and Risk Assessment – Supplier Management – Leave Request and Approval – Travel Request and Approval – Procurement Approval – Timesheet Recording & Approval – Performance Management – Personnel Profile and Updating – Records Management – Contract Management – Forms Management – Compliant Document Generation 3

Description: § Forms, a front end for the Enterprise SOA Forms are the most pervasive way to document business processes and a natural way to deliver SOA-based applications to end-users. This session describes how IBM has created a Forms Services Platform made up of reusable and extensible services components to integrate forms into ERP, CRM, content repositories, databases and workflow systems. This enables faster deployment of business processes that rely on forms to initiate or personalize the capture of information for a business process. 4

Key Driver: e. Forms Maturity Model SOA Process-Centric Compliance Security Integration Records 5 4 Content-Centric 3 2 1 Data Capture Enterprise Content/ Process Management Store, Process, Preserve Fill, (Sign) & Submit Fill & Print & Fill Print & Read Static Document Driven Dynamic Business Rule Driven 5

W 3 C XForms 6

W 3 C XForms is a W 3 C web standard for the creation of the “next generation of forms for the web” § In XForms 1. 0, the principal purpose of a web form is to process XML data. § For XForms-based forms, these processing rules may include : – – Data collection and formatting Data validation Application logic Submission rules § XForms 1. 1 is currently targeted to become a recommendation in early 2008 § Dr. John Boyer from IBM is editor of the XForms 1. 1 specification 7

Key Point: XForms are Not E-Forms “XForms” are NOT e-forms! § XForms is not designed to work alone. There is no such thing as a stand-alone XForms document. § Each “XForms Model” must be hosted inside a presentation layer. § XForms uses two sections to define data: The XForms model and the XForms user interface. 8

XForms Model § The XForms 1. 0 Recommendation provides a Model-View-Controller (MVC) expression of e-forms. § Model: § XForms defines an XML Data processing framework which includes: – A declarative business rules engine – Submission parameters for returning data and calling Web Services – Input validation by XML Schema and XML Schema Data Types <? XML. . 9

W 3 C XForms – User Interface Implementations § XForms defines “intent-based” controls § Actual implementation varies depending on host language . . using XFDL, is “skinned” by: – input – A generic input control – secret – Password entry Field – textarea – Multi-line text entry Field List, Checkgroup – select – Select from a set – select 1 – Exclusive select from set – range – Pick from range of values – upload – Upload data Popup, List, Checkgroup, Radiogroup – trigger – Activate command Button – submit – Trigger data submission § Without a host language, structure is flowbased only, no concept of pagination or location or even appearance Etc… 10

W 3 C XForms and “Host Languages” Skin #2 XFDL § For Enterprise solutions, XForms should be hosted by a presentation layer that can deliver on customer needs. <? XML. . – XHTML and XFDL are examples of suitable host languages – Consider offline usage requirements. § The host language can extend the baseline capabilities of XForms Skin #2 WML – Pagination – Support for attachment handling – Digital signatures – Precision layout – Whole-form submission – etc. 11

W 3 C XForms – Key Enterprise Considerations § Recall that the XForms Model is “hosted within” or “wrapped” by a presentation language § The features of each presentation language vary and are suited for different operating environments – Web Browsers – Disconnected or “hybrid” environments Presentation Options XFDL XForms Model XHTML – Mobile Phone Browsers – Etc. § For the Enterprise, rich features, such … as precision layout and security are typically mandatory – some presentation layers are unsuitable for this environment WML Other 12

XForms Document Architecture Example § Let’s examine the following example of an XForms-based eform: Host Language XForms Model XML Data Instances XForms “Binds” (Computes) XForms Submissions (Data Only) “Intent-Based” XForms Controls • User Interface Implementation • Pages • Location of “controls” (widgets) • Additional features, advanced controls • Computes (conditional logic) • Attachment Handling • Document-Centric Submissions • UI Specific Features • Digital Signatures 13

Application Specific Implementation E-Form Application Forms Application – Specific XForms Deployment (Platforms, Rich/Thin Client, UI Implementation) User Interface – XForms Intent-Based UI Description XForms Standardization: Innovation: XForms: Open Standards Form Technology Data Rules – XForms Processing Rules govern and describe the context, processing and usage of the form and its data Data Syntax – XML Data Schemas 14

Additional XForms session TDE-4164 A From models to forms: Building applications around XForms Marriott - San Antonio Thu, 24/May 01: 30 PM - 02: 45 PM 15

IBM Workplace Forms and SOA 16

Interfacing with Web Services § Initiate a call – Obtaining a form template – Form template pre population using web service calls – Consumption of web services during execution of a form § Respond to a user action – Submit instances or entire form to a URI. – Start workflow – Archive Form – Populate Back end 17

Example Service-Oriented e. Form Application § Example diagram – not exhaustive! § Standard design principles apply. § Componentization and reuse provide standard benefits and efficiency improvements. § Note the Content Manager Adapter … leveraged by both the Form Submission and Form Versioning Service. App specific Code 18

The Business Challenge § Maintaining an integration between disparately managed technologies becomes geometrically complex Pl a Form Versions § RDBMS § Content Management § Document Management § Application Servers § Portal Servers § Workflow tfo rm § Forms are a broad “horizontal” technology that can be used in many industries and applications. § To provide a complete solution, forms need to be used in conjunction with other enterprise technologies: Partner Versions So where does this leave us? 19

Enterprise Solution Requirements E-Form applications often consist of repeatable constituent actions such as: § Publishing a form template to a § § repository Retrieving a form template from a repository Retrieving data from a data tier or line-of-business system Pre-populating a form template with data Appending or inserting a form page § Appending or inserting form sections § Presenting a form to a user via a Web § § or Portal page Extracting form data Storing form data into the data tier or line-of-business system Storing or archiving a completed form …etc. . 20

Problem: Forms Solution Stovepipes Varied requirements + Integration complexity + Short delivery timelines Stove-piped forms solutions § Custom applications / solutions § Monolithic design +/or inflexible technology poor reusability § Programmers +/or complex scripting needed § Solution inflexibility leads to: – – Reduced business agility Greater long-term costs Increased competitive pressure Longer development cycles 21

Solution: Workplace Forms Services Platform An E-Form Application Framework 1. A simple, extensible platform to facilitate the integration of WPF with partner technologies. § § § 2. Shorten time-to-value and reduce cost/risk for customers, partners. Provide re-usable components Ensure integration interoperability Workplace Forms Viewer Integration with key IBM/partner technologies. § § § Provide “out-of-the-box” functionality Direct Integration - Portal, CM, Process Server Websphere TX – DB 2, SAP, SOA, etc. 3. Application Servers e. g. WAS User Interfaces e. g. Portal, Notes Workplace Forms Services Connector • Mapping Services • Transformation Services • Pre-population • Meta-data management • Create, Read, Update, Workflow e. g. Process Svr. , Notes, Application Design, e. g. Notes Workplace Designer Delete Packaged Applications e. g. SAP, Siebel Identity Management e. g. Tivoli Example modules and integrations. 4. Workplace Forms Webform Server Repositories, e. g. CM, JCR, Domino Best practices and integration guidelines. 22

Forms Services Platform q An enterprise application, framework and libraries which provide the ability to extend and integrate Workplace Forms q Service-oriented and extensible, promotes the development of reusable components q Designer Plugins to create Forms Services Platform projects, manage project repositories and generate Web. Sphere TX Type Trees and Maps from Workplace Forms data instances q An optional SDK and samples to support custom Pipe/Bundle development q Optional “Integrators*” for direct integration with other IBM/Partner technologies (PDM, File. Net, …) 23

Web. Sphere Transformation Extender What comes with base entitlement: Available at additional charge: Database §ODBC §DB 2 §Oracle §MS SQL Server §Informix §OLE DB §SQL/MP §SQL/MX §Sybase §Java Class §JCA Gateway §JMS §JDNI §Mime §MSMQ §Oracle. AQ §Quality stage §Quoted-printable §Shell script §Sink §Socket §TIBCO RV §Tuxedo §VAN § SAP r/3 § SAP XI § Siebel § Non-Database §Archive (tar) §Archive (zip) §base 64 §batch file §CICS §Com Automation §Corba §Database §e-mail §RHL Fastwine §File §RS Manager §FTP §GZip/ZLib §HTTP §IBM Websphere. MQ(client) §IBM Enterprise Application Adapters: Peoplesoft Industry Adapters: § SWIFTnet V 4. 2 § HIPAA § X 12 V 2. 7 § EDIFACT V 2. 7 Websphere. MQ(server) 24

Forms Services Platform Architecture Invocation and Bridging OSGI-Based Pipeline Assembly and Execution Pipeline Modules “Pipe-Stages” DB 2 Oracle Sybase SAP R/3 MS SQL Server Repository UI Pipe Stages People. Soft Portal 6/PDM Repository Connector Pipe Stages Teamspaces And Documents Content Manager Custom Pipe Stages Future Integration Deployment Pipe Stages Forms User (Viewer) Servlet Bridge Request Dispatcher Pipeline Execution Pipeline Constructor Forms User (Webform Server) Portlet Bridge Service Definition Forms Designer Launch Forms Services Quickly build Forms Services Mapping Pipe Stages Designer Integration Pipe Stages Websphere TX Mapping Integration SOA (SOAP) NEW Connectivity to Enterprise Systems and Support for Industry Standards 25

Connectivity: Critical Success Factors and Products § Ability to connect all assets § Universal transformation § Scalability and performance § Transactions § 24 x 7 operations § Complex event processing Key Products 4 Web. Sphere Transformation Extender Web. Sphere Message Broker Web. Sphere ESB Web. Sphere MQ Adapters 26

Web. Sphere Transformation Extender Universal Transformation Solution – Codeless Development, Reuse and Deploy anywhere §Ensure compliance and validation with the latest industry data standards § Map complex document structures with ease J 2 EE Standalone System z (native) Windows, UNIX, Linux § Embed § Execute Standalone § Event driven Application / Process Server MAP TRANSFORM ESB Advanced ESB § Make Advanced ESB more Advanced Deployment options to grow with your business needs 27

Core Components and “Pipelines” § As mentioned, the Forms Services Platform provides a range of out-of-the box components. § Examples include: – – – Receiving a form submission Extracting form data instances Inserting data instances into a form template Loading a Form template Storing a form template Using an adapter / connector to store or retrieve data – Using a “Transformation Extender” map to translate data or information – Returning a result to the user § The inputs and outputs for these components are clearly defined § Processing forms is as easy as assembling multiple components, aka “pipes” into a “pipeline”. 28

Example Pipeline Ex Let’s take a closer look at an example pipeline. Lo He ad Pi pe ad Fo rm Lo Pi ad pe Da Re ta tu Pi rn pe Er ro r. P ip e tra ct Da Re ta tu Pi rn pe Da ta Pi pe Tr an sf or m Pi pe St or e. D at a. P ip e § There are several “branches”, which are quite simple actually: – Process Form – Return Result – Error Handling § We can also create custom pipes – One can encapsulate any desired functionality into a Pipe for reuse. So what about reuse forms application User Interfaces (UI)? 29

Get Purchase Order Pipeline The Map is stored in the Project Repository via the Designer The form is loaded from the Project Repository Service Repo Load Pipe Map Pipe Repo Load Pipe The form is updated with the product information from TX Load Form Pipe /SOASample/Get. PO Hea d Pipe TX Map Service Restor e Map Pipe Retur n Form Pipe TX will be used to request information from a web service. The response will be formatted to the appropriate XML type for the form. Updat e Instan ce Pipe Preser ve Map Pipe Form Service 30

Forms Designer – Component Navigator 31

Web. Sphere TX Design Studio – mapping tool 32

Business Drivers for Workplace Forms and Portal What does Portal add to Workplace Forms? § Portal allows us to assemble UI elements, including forms (IPC) § Workplace Forms requires a repository to store template forms for access by end users with the ability to submit and store data and documents (PDM) § Workplace Forms may require workflow in the case of validation or approval processes (BPEL) § Application context is often required (Awareness) § Composite applications provide the standard benefits of SOA Web. Sphere Portal Server is an excellent choice to provide these capabilities 33

Data Integration: Inter-Portlet Communication § Key Point: We can push data into a Form from other Portlets. § Events based on UI input or conditional logic can trigger updates § This allows xml instance insertion or replacement, or modification of form state § Other portlets can be updated based on in-form events and form state 34

Data Integration: Inter-Portlet Communication Pushing data from Forms to other Portlets § Workplace Forms v 2. 6 added support for XForms §. . allowing use to perform XForms submits XForms Submit Web Service Servlet / Portlet – Data-centric not document-centric – Example: submit Client ID, receive XML fragment of client data Response Developer Tip: This approach works with both Viewer and Webform Server 35

Defining Workplace Form + Portal Integration § “Integrating” Portal and Forms can mean: – UI Integration (putting forms on the glass) – Data Integration – Process Integration – Security Context Integration § The IBM Workplace Forms Redbook provides coverage of the above integration topics UI Integration + Data Integration 36

Credits § Cayce Marston, Lotus Worldwide Technical Sales cmarston@ca. ibm. com § § Bob Levy, Sr. Product Manager boblevy@us. ibm. com Chris Phillips, Lead Developer Forms Services Platform Charles Bryson, WPLC Technical Sales Manager , Tampa Mike Mansell, Senior Product Architect Forms § Peter Van de Graaf, Program Director, Lotus Quickr Team Collaboration & Forms 37

References § Integrating XML forms-based processes into Service-Oriented Architectures using IBM Workplace Forms Services Platform http: //www-128. ibm. com/developerworks/workplace/library/forms-soa/ § Integrating IBM Workplace Forms with Web. Sphere Portal to create a form-centric application http: //www-128. ibm. com/developerworks/workplace/library/forms-portal/ § Create a form with IBM Workplace Forms Designer http: //www-128. ibm. com/developerworks/workplace/library/forms-designer/ Redbooks § IBM Workplace Forms 2. 6, SG 24 -7388 -00 § IBM Workplace Forms: Guide to Building and Integrating a Sample Workplace Forms Application, SG 24 -7279 -00 38

Thanks ! Please fill in the feedback FORMS Questions and Answers This is session TPC-4783 A

© IBM Corporation 2007. All Rights Reserved. The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are provided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to any participant. While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this presentation or any other materials. Nothing contained in this presentation is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. The following are trademarks of the International Business Machines Corporation in the United States and/or other countries. For a complete list of IBM trademarks, see www. ibm. com/legal/copytrade. shtml AIX, CICSPlex, DB 2 Universal Database, i 5/OS, IBM, the IBM logo, IMS, i. Series, Lotus, OMEGAMON, OS/390, Parallel Sysplex, pure. XML, Rational, RCAF, Redbooks, Sametime, System i 5, System z , Tivoli, Web. Sphere, and z/OS. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered 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. 40