Powering Enterprise Process Advantage Metastorm PM 4 Data

Powering Enterprise Process Advantage® Metastorm PM 4 Data Managed File Transfer Chris Howarth 2005 Metastorm, Inc. chowarth@metastorm. com

Powering Enterprise Process Advantage® Product History • • First developed as FTF/MQ in 1994 The first commercially available product for MQ IBM ISV of the year 3 times Currently version 8 300+ customers Previously Commerce. Quest/Message. Quest Sold by IBM just like any Web. Sphere product Also sold as part of Metastorm BPM Suite 2005 Metastorm, Inc. 2

Powering Enterprise Process Advantage® Web. Sphere Business Integration Reference Architecture Development Platform Business Performance Management Services Interaction Services WBIC Partner Services Process Services Information Services WBIMB WMQ ESB WMQ PM 4 DATA and PM 4 CICS Application and Data Access Services Business Application and Data Services Enterprise Applications and Data Infrastructure Services 2005 Metastorm, Inc. 3

Powering Enterprise Process Advantage® PM 4 Data is the File and Database Adapter for the Enterprise Service Bus Utilize MQ Messaging to access and provide managed transfer facilities for Files and Databases Portal Service B 2 B Interactions Service Flow Data Existing Applications XML enable Files, Databases WMQ & XML Onramp 2005 Metastorm, Inc. SOAP Service Request (e. g. J 2 EE, . NET) New Service Logic 4

Powering Enterprise Process Advantage® Metastorm 2005 Metastorm, Inc. What is PM 4 Data?

Powering Enterprise Process Advantage® What isn’t PM 4 Data? • PM 4 Data is not: – A simple F 2 M/M 2 F utility – An MQ file adapter – An FTP wrapper – A point solution 2005 Metastorm, Inc. 6

Powering Enterprise Process Advantage® What is PM 4 Data? • PM 4 Data is: – A high-performance, highly scalable solution for “managed” high volume data transfer of almost any type of data between two or more distributed heterogeneous systems (Managed File Transfer Solution). – A solution that leverages the award winning IBM transactional MOM (Web. Sphere MQ ®) for assured, high performance, reliable and secured asynchronous delivery of data. – A extendible, customizable, reliable and scalable foundation for a modern visible process-centric WMQ based data transfer & integration solution. – A powerful WBI companion and WMQ implementation accelerant tool – A Web. Sphere MQ and XML Power Tool. 2005 Metastorm, Inc. 7

Powering Enterprise Process Advantage® Supported Platforms • Mainframe z/OS (running OS/390, MVS or z/OS) • Unix – AIX – HP-UX – Sun Solaris – Linux • OS/400 (i 5) • Windows – NT, 2000, XP, 2003 • HP (Tandem) NSK • IBM 4690 Point of Sale System – Optional “Continuous Extract Facility” for TLOG Trickle Feed • Both Web. Sphere MQ Client or Server supported 2005 Metastorm, Inc. 8

Powering Enterprise Process Advantage® Features and Functions Summary High performance, secured, bulk data transfer solution that delivers real-time and batch File or Database Integration capabilities. Features Usability • Eclipse® based Workbench IDE for developing and • Customizable process flows for end to end status tracking. testing multiplatform integration Scripts & XML Policies • Accelerates file and message based integration. • Centralized management • XML-enabler (Files and Databases). • Built-in Status and Statistics Tracking • XML Control interface. • Common multi-platform scripting language • Distribution list for one-to-many transfers. • Web based Command/Control Center and Status • Transfer list support for many-to-many transfers. • User profile and access control • Service-oriented architecture. • File and Database Integration Service • Accelerates integration with IBM WMQ Broker • File Transfer request repository • Logical record processing • Interactive retry / fail selection of failed transfers • SSL based data encryption (WMQ SSL) • Performance analysis reports and graphs • Policy driven I/O: • Native multi-platform Interface • File or Database to Message • TSO, JCL, Command, Message, Shell script, bat/cmd • Message to File or Database • Simple file extract, transfer, and load capabilities. • Directory Monitoring: Sense creation/arrival of file to initiate a file transfer • Highly scalable, both in volume and platform capabilities • Automated exception handling facility 2005 Metastorm, Inc. 9

Powering Enterprise Process Advantage® PM 4 Data new features List in V 8 – Central Registry • Management and configuration artefacts – MQ Dashboard • Easily Monitor Enterprise MQ load and Usage • Daily Summary reports – Process Flow Editor to create customized Process Flows – JMX based Systems Management infrastructure • JMX (Java Management Extensions) infrastructure and support – Web Browser Component Launcher Console • LOG 4 J (STDOUT / STDERR) log management • Email notifications for exception • Alert Management integration to Tivoli Console 2005 Metastorm, Inc. 10

Powering Enterprise Process Advantage® Managed Data Movement Simplified Data Movement Scenario Data broken into messages Messages received and assembled Target platform Source Platform End-to-end detailed transfer status § § Far more sophistication, reliability and performance than putting a data in a single message Platform file differences handled automatically during transfer Extended functionality with customizable exits End-to-end data transfer visibility 2005 Metastorm, Inc. 11

Powering Enterprise Process Advantage® PM 4 DATA Files, Databases and Queue Integration Simple Example • Example – Source Data needs to be moved to one or more targets – This can be caused by application updates and sensed by PM 4 DATA – End-to-end visibility with Status and Notification or or PM 4 Data Queue DB Queue New or Append file or PM 4 Database update Data transfer request Queue File or PM 4 Data New file or Database update 2005 Metastorm, Inc. 12

Powering Enterprise Process Advantage® Process Flow Editor Business Provides the “What needs to be done” IT provides the “How it gets done” Exception Handler Routing File Transfer as a sub Flow Activity 2005 Metastorm, Inc. 14

Powering Enterprise Process Advantage® PM 4 Data Registry – Central HFS based Artifact Registries Application 1 • Eclipse Workbench IDE – Web Browser access for transfer request / policies • Version and Change Control Support (CVS or similar product) • Customized or template based Node configuration support • Support for “Application” or “Project” level Registry • Support for MQ / TCP and File based registry drivers • Support for Registry chaining and search order control Messages Process Registry Programs Contents XMScript XML Request Group 1 Group 2 Policies <Registry. List> Search Order <registry location="C: CQDemosdataRegistry">Emergency</registry> <registry location="C: CQDemosdataRegistry">Application 1</registry> <registry location="C: CQDemosdataRegistry"> Application 2 </registry> <registry location="C: CQDemosdataRegistry"> Application 3 </registry> <registry location="C: CQdataRegistry">Commerce. Quest</registry> </Registry. List> Physical Location 2005 Metastorm, Inc. 15 “Registry Name” Typically used to group artifacts for a project or “Application”

Powering Enterprise Process Advantage® Transfer Process Monitor • • • Web Server support for: Web. Sphere, JBOSS (included) – Status – Component Configuration / Management (JMX) – Component Logs (LOG 4 J) Status display – End-to-End transfer status Access Control – User management, with roles & rights Transfer request management – Ping nodes – Create, save, and submit transfer requests – Transfer grouping – Distribution List Management – Directory monitoring 2005 Metastorm, Inc. 16

Powering Enterprise Process Advantage® Conclusion • Satisfies Enterprise Managed File Transfer requirements • Strategic Component of the Enterprise Service Bus Architecture • Accelerates the On Demand Strategy 2005 Metastorm, Inc. 18

Powering Enterprise Process Advantage® Metastorm 2005 Metastorm, Inc. Process Manager for Data Architecture Overview

Powering Enterprise Process Advantage® PM 4 Data Architecture 2005 Metastorm, Inc. 20

Powering Enterprise Process Advantage® Process Flow Manager (Coordinator) 1 Request Message WBI Message Broker Initiating Application Process Flow Definition Status Tracking Audit Sub System 2 Process Flow Manager 3 5 Message 6 4 Response 5 Message 3 Message Business Process Definition Repository 4 Response Synchronous External Service, including WS, EJB 2005 Metastorm, Inc. Asynchronous Workflow Enabled Component (response required) Asynchronous Workflow Enabled Component (NO response req) 21 Synchronous In-line Workflow Enabled Service Program Or Shared Library

Powering Enterprise Process Advantage® Auditor Sub System PM 4 Data Apache Web Server MQ XML Status Query Request Control Center JSP Application Status Query Server MQ XML Status Query Response DB 2 MQ XML Status Datagram Process Flow (Coordinator) Server 2005 Metastorm, Inc. Status Loader MQ XML Status Datagram User Components 22

Powering Enterprise Process Advantage® Metastorm 2005 Metastorm, Inc. PM 4 Data Components

Powering Enterprise Process Advantage® Registry Service • Stores transfer-related artifacts created in the Process Monitor – Transfer requests – Destination entries – Destination lists – Directory Monitor entries – Policies Object – Scripts – Process Flows – Message Object – Meta Data 2005 Metastorm, Inc. 24

Powering Enterprise Process Advantage® Coordinator Service • Directs all file-transfer activity – Receives transfer request in XML format from the PM 4 Data interface • Process Coordinator • Command Line • XML Interface – Manages file transfers from end to end • Sends transfer request to sending File Transfer Service (FTS) • Uses XML to direct file transfer processing • Receives status information back from the receiving FTS • At least one must exist in the enterprise – More than one can exist on a host 2005 Metastorm, Inc. 25

Powering Enterprise Process Advantage® File Transfer Service (FTS) • Can send and receive files, based on direction from the Coordinator – A single instance of the FTS can both send and receive files • Each host that performs transfers must have at least one FTS – The FTS must have access to the source and destination file system • Multiple instances of the FTS can run on one host – Typically, two instances of the FTS are placed on a host at installation – More instances of FTS can be added to provide additional throughput 2005 Metastorm, Inc. 26

Powering Enterprise Process Advantage® Exit Service • Responsible for running PM 4 Data exits • Can be accessed from any exit point in the transfer process – Receives XML message directing execution – Contains name of script and entry point in script – Returns result element to PM 4 Data • Uses XMScript modules – User can easily additional methods • Exits run at any node – Sender, Receiver, Process Coordinator – Pre-process, Post-process • Multiple exits at any exit point – Exits can be chained 2005 Metastorm, Inc. 27

Powering Enterprise Process Advantage® Auditor Service – Status Query Server • Provides interface between the GUI interface and the status database – Process Monitor – web-based – Explorer – MMC-based • Obtains status information for display 2005 Metastorm, Inc. 28

Powering Enterprise Process Advantage® Auditor Service – Status Logger • Provides interface between each component that reports status and the status database – Receives status information from the following components: • • Process Coordinator Sending FTS Receiving FTS Exit Service – Puts header and detail status information in the status database 2005 Metastorm, Inc. 29

Powering Enterprise Process Advantage® User Service • Provides interface between the Process Monitor web interface and the user database • Manages user accounts for the web interface – Govern access to create and submit transfers and view status • Typically only used in planning and administration 2005 Metastorm, Inc. 30

Powering Enterprise Process Advantage® Metastorm 2005 Metastorm, Inc. Policy based I/O

Powering Enterprise Process Advantage® Why use policy based I/O? Issues Solutions Benefits Integration requires custom “glue” code at the end points. Describe end points or data stores with a policy. Improve time to market by replacing coding with configuration. Files are “familiar” and nontransactional, while databases, queues or other data targets require transactional properties for integration. Use file metaphor for all data targets including databases, queues, TCP/IP sockets, HTTP protocol. Bridge file based “legacy” applications with queue, database, or other data stores applications. File based integration requires costly operational support. A managed file transfer with flexibility for non-file based data stores. Simplifies development, without burdening operations. 2005 Metastorm, Inc. 32

Powering Enterprise Process Advantage® Metastorm PM 4 Data Managed File Transfer Chris Howarth 2005 Metastorm, Inc. chowarth@metastorm. com