IBM United States Software Announcement , dated April 19, 2011

Transcription

1 IBM United States Software Announcement , dated April 19, 2011 IBM WebSphere Business Integration for Financial Networks V3.1.1 adds support for SWIFTNet 7 including an integrated Relationship Management Application Table of contents 1 Overview 11 Publications 2 Key prerequisites 11 Technical information 2 Planned availability date 17 Ordering information 2 Description 21 Terms and conditions 9 Product positioning 26 Prices 10 Statement of direction 27 Order now 10 Program number At a glance IBM WebSphere Business Integration for Financial Networks for z/os V3.1.1 and IBM WebSphere Business Integration for Financial Networks for Multiplatforms V3.1.1 add support for SWIFTNet 7 including an integrated Relationship Management Application (RMA). For ordering, contact your IBM representative or an IBM Business Partner. For more information contact the Americas Call Centers at 800-IBM-CALL ( ). Reference: YE001 Overview IBM WebSphere Business Integration for Financial Networks for z/os V3.1.1 and IBM WebSphere Business Integration for Financial Networks for Multiplatforms V3.1.1 help financial institutions remain competitive in the ever-changing world of financial message transfers. It provides a SWIFT-qualified single window interface to SWIFTNet FIN, InterAct, and FileAct services, and is able to process high volumes of financial messages reliably. IBM WebSphere Business Integration for Financial Networks delivers a model-driven approach that supports financial institutions in the development or transformation of their financial transaction management systems. Enhancements include: SWIFT-qualified support of new mandatory SWIFTNet 7 for FIN, InterAct and FileAct SWIFT-qualified integral Relationship Management Application for FIN, InterAct and FileAct Exploitation of new SWIFTNet 7 functions such as: Message and file distribution Message and file copy Input and output channels IBM United States Software Announcement IBM is a registered trademark of International Business Machines Corporation 1

2 Business insight into the message warehouse data based on IBM Cognos Business Intelligence Enablement of infrastructure monitoring based on the Java TM Management Extensions (JMX) standard Key prerequisites Refer to the Hardware requirements and Software requirements sections. Planned availability date April 29, 2011 Description Enhanced functions in Version SWIFT-qualified support of new mandatory SWIFTNet 7 for FIN, InterAct, and FileAct With the new and mandatory SWIFTNet 7 each messaging services interface to SWIFTNet FIN, InterAct, and FileAct needs to be SWIFT-qualified. While this in the past already has been true for SWIFTNet FIN, now also software accessing SWIFTNet InterAct and FileAct services needs to be SWIFT-qualified. As previous versions already did for SWIFTNet 6.3, IBM WebSphere Business Integration for Financial Networks V3.1.1 again provides this SWIFT-qualified single window to SWIFTNet FIN, InterAct, and FileAct of SWIFTNet 7. SWIFT-qualified integral Relationship Management Application for FIN, InterAct and FileAct A customer can use the SWIFT-qualified integrated Relationship Management Application to manage his business relationships for the SWIFTNet services FIN, InterAct, and FileAct. Its browser-based user interface supports all actions required such as creation, approval, or updating of authorizations, and allows the negotiation of changes with the business partners using queries and answers. A variety of filters is offered, for example, to quickly view what actions are required on authorizations or conversations. Communication with counterparts is done using the InterAct service of the Messaging Services for SWIFTNet InterAct and FileAct feature. Changes to the authorizations become effective immediately since they are done in the database used for runtime checks. Configuration and security configuration use the corresponding Base services. Exploitation of new SWIFTNet 7 functions IBM WebSphere Business Integration for Financial Networks V3.1.1 supports many of the new SWIFTNet 7 capabilities, including: Receiving of distributed messages and files Message and file copy (T-Copy and Y-Copy) Use of input and output channels Support of Application Service Profiles SnF system recovery Business insight into the message warehouse data based on IBM Cognos Business Intelligence To gain insight into the message and file transfers exchanged via SWIFTNet, enablement of IBM Cognos Business Intelligence is provided. A granular filtering on message warehouse data for ad-hoc queries as well as reporting-style analysis is possible using sample reports and queries, that a customer can use either integrated in the browser-based user interface or in the Cognos context. These reports allow him to search for all relevant warehouse data and to display IBM United States Software Announcement IBM is a registered trademark of International Business Machines Corporation 2

3 lists of resulting message or file transfers down to content and history of single messages. Enablement of infrastructure monitoring based on the Java Management Extensions (JMX) standard Integration of infrastructure monitoring is possible by providing events in the Java Management Extensions (JMX) standard. Any monitoring solution that is able to handle this standard, for example, IBM Tivoli Monitoring, then can monitor these events. Use of IBM Tivoli Monitoring is supported and allows a customer to display WebSphere Business Integration for Financial Networks events together with events of, for example, IBM DB2, IBM WebSphere MQ, or IBM WebSphere Message Broker, and to define custom situations for these events. Support of WebSphere Message Broker V7 IBM WebSphere Business Integration for Financial Networks V3.1.1 supports WebSphere Message Broker V6.1 and V7.0. Product structure IBM WebSphere Business Integration for Financial Networks V3.1.1 consists of the following features: Base Support for SWIFTNet FIN Financial Message Transfer Messaging Services for SWIFTNet InterAct and FileAct Message Management Financial Transaction Manager Base All WebSphere Business Integration for Financial Networks features take advantage of the basic, common services provided by the WebSphere Business Integration for Financial Networks Base feature. This feature provides a common integration platform allowing common and consolidated use of recording of audit data, message warehousing, event handling and logging, reference data, such as BIC address or currency data, access control, and configuration and administration. Full multi-bank support is reached by configuring organizational units and assigning access rights as well as separating message or file transfer data per organizational unit. The Message Validation Service checks the syntax of FIN, SWIFTNet Funds, SWIFTNet Exceptions and Investigations, and SWIFTNet 6.3 system messages and ensures they abide by the message rules. It is used by the FIN and FMT services (for FIN messages) and by the message entry and repair facility, and can also be used by backend applications, invoked by Java calls or by the corresponding WebSphere Message Broker node. You can configure and operate SWIFTAlliance Gateway (SAG) workstations, as well as monitor SAG events from within WebSphere Business Integration for Financial Networks, by issuing commands directly to WebSphere Business Integration for Financial Networks services, regardless of the SAG workstation operating system (AIX, Sun Solaris, or Windows ). Most of the services provided by the Base feature have public interfaces and can be used by customer applications and for integration tasks. For example, applications can add information to the WebSphere Business Integration for Financial Networks message warehouse or query whether valid relationships for a transfer exist. Support for SWIFTNet FIN This feature provides an implementation of the FIN protocol as specified by SWIFT and has been qualified by SWIFT. It is used by major banks throughout the world IBM United States Software Announcement IBM is a registered trademark of International Business Machines Corporation 3

4 and offers scalable and reliable access to SWIFTNet, combined with special highavailability capabilities such as automatic switching of logical terminal sessions using several SWIFTAlliance Gateway (SAG) workstations. In addition to message authentication capability, it can also validate all categories of FIN messages, including FIN and GPA system messages. Operators can use this feature to operate and monitor any number of logical terminal sessions. Financial Message Transfer (FMT) The FMT feature provides the means for logical terminals using WebSphere Business Integration for Financial Networks to exchange FIN messages outside of the SWIFT Secure IP Network (SIPN), without the sending or receiving applications being aware that the SIPN is not being used. This lets you avoid the costs associated with using the SIPN. Message Management A simple User Interface for message entry and repair The increasing cost pressure on financial message processing makes it imperative that you can handle high volumes of messages in a straight-through manner. While the goal of having no manual intervention applies to the vast majority of messages, there will always be a certain number of messages that require manual intervention, such as messages that contain invalid information and must be repaired, or messages for high value payments that must be manually authorized. The Message Management feature in WebSphere Business Integration for Financial Networks addresses not only the FIN messaging standard still used in the majority of high-value payment systems all over the world, but also the emerging MX standards such as SWIFTNet Funds. You can use its message entry and repair GUI, that runs on a WebSphere Application Server and employs browser-based graphical user interfaces (GUIs), to manually process FIN, SWIFTNet Funds, and SWIFTNet Exceptions and Investigations messages. It provides sample WebSphere Message Broker message flows that you can use to model your business processes. These sample flows contain the new processing steps and can be adapted according to your specific needs. The processing steps include: Creation of messages (for all FIN categories and FIN and GPA system messages as well as for all Funds, Exceptions and Investigations, and SWIFTNet 6.3 system messages) Use of message templates for creation Editing and display of messages (formatted and unformatted) Validation of messages (FIN, SWIFTNet Funds, SWIFTNet Exceptions and Investigations, SWIFTNet 6.3 system messages) Verification of messages (retyping of FIN messages) Authorization of messages (optionally four-eyes principle) Check of valid relations This processing can use BIC, currency, and country information provided by SWIFT BICplusIBAN directory to check for valid country or currency information, or to expand the addresses when displaying FIN messages. Roles assigned to users for each of the configured organizational units (OUs) define the tasks users are allowed. You can use the predefined roles supplied by WebSphere Business Integration for Financial Networks, or create your own roles with the level of granularity required. Each processing step is recorded in a message history, attached to the message and stored in the message warehouse. Integrate message processing with backend applications Besides manual message entry and repair, the Message Management feature includes various functions and services to simplify integration with backend applications. IBM United States Software Announcement IBM is a registered trademark of International Business Machines Corporation 4

5 WebSphere Business Integration for Financial Networks uses routing capabilities in WebSphere Message Broker to model message processing steps, such as routing of messages to anti-money-laundering filters, liquidity management programs, or other backend applications. Routing rules expressed in the public XPath standard can use criteria contained in each message (for example, the name of the organizational unit that issued the message or the value of a FIN subfield such as the amount) to determine the message path through a message flow. The routing rules of these nodes are defined using the graphical user interface of WebSphere Message Broker Toolkit. Sample message flows that illustrate routing capabilities are provided for FIN inbound and outbound processing as well as for MX messages. These samples can easily be adapted to meet your specific needs. WebSphere Business Integration for Financial Networks offers a printing service that enables automation of the printing of FIN, SWIFTNet Funds, SWIFTNet Exceptions and Investigations, and SWIFTNet 6.3 system messages in either formatted or unformatted mode. Messages to be printed are placed into logical print queues for printing control. An operator can start, stop, or display the status of these queues, and reprint messages. The printing of messages can be configured either to be automatic or require manual confirmation. The Sequential Data Facility (SDF) can be used by business applications to exchange FIN messages contained in files with WebSphere Business Integration for Financial Networks. These files can be either z/os datasets that use the SDI/SDO format of MERVA ESA or files in a UNIX file system that use the SWIFT RJE format. All FIN messages contained in these files are processed by the FIN service the same as any other FIN message. Migration path from MERVA ESA to WebSphere Business Integration for Financial Networks WebSphere Business Integration for Financial Networks has always provided a seamless connection to IBM MERVA ESA. WebSphere Business Integration for Financial Networks offers functions that were available only in MERVA ESA (for example, manual message entry and repair, message printing, callable message validation, message routing, and sequential data processing). These valuable functions are available to customers without MERVA ESA, and can ease migration of MERVA ESA customers to WebSphere Business Integration for Financial Networks. These functions enable you to migrate MERVA ESA applications at your own pace to WebSphere Business Integration for Financial Networks, consolidating all functionality within a single, modern platform based on IBM middleware products and gain the additional functions such as support for MX standards. Some environments have several MERVA ESA systems connected to a single WebSphere Business Integration for Financial Networks instance serving as a hub for all SWIFTNet access. You can choose to install the Message Management feature on the hub and phase out use of your MERVA ESA systems. To maintain decentralized control over user access to manual message-processing tasks, you may choose to replace each MERVA ESA system with a single WebSphere Business Integration for Financial Networks instance with only the Base and Message Management features installed, and use WebSphere MQ to connect this instance to the hub containing all functions of WebSphere Business Integration for Financial Networks. Messaging Services for SWIFTNet InterAct and FileAct Although FIN is still the most common standard message format, XML-based messages are steadily increasing. Examples of such formats are the SWIFT MX standards and XML formats introduced for SEPA retail payments. Messages that employ these formats are processed using SWIFTNet InterAct and FileAct, the support of which is consolidated in the Messaging Services for SWIFTNet InterAct and FileAct (MSIF) feature of WebSphere Business Integration for Financial Networks. The services contained in this MSIF feature comply with the SWIFT messaging interface specifications and are qualified by SWIFT, exceeding SWIFT IBM United States Software Announcement IBM is a registered trademark of International Business Machines Corporation 5

6 specifications in some cases (for example, processing system messages for delivery notifications and third-party notifications). Applications that use InterAct or FileAct services, or both, need only one messaging interface, reducing complexity and streamlining configuration, administration, and operation. The MSIF feature records the state of each message or file transfer request, and processes each request according to its current state. Error situations can be recovered by issuing a single command, automatically determined to initiate the appropriate corrective action. The message interface is highly flexible. You can configure defaults for almost all values, and override them by specifying values directly in each message. This lets you configure static data and specify only variable data for a specific message. Functions of the MSIF feature InterAct: Sends and receives messages in both real-time and store-and-forward delivery modes Automatically retries to send requests that encounter recoverable errors and switches SAGs if configured Correlates delivery and third-party notifications to the related transfer and provides them to business applications Supports new SWIFTNet 7 features including: Message distribution (receiving part) Message copy (T-Copy and Y-Copy) Input and output channels SnF system recovery Support of Application Service Profiles FileAct: Sends and receives files in both real-time and store-and-forward delivery modes Provides files for downloading to a counterparty and receiving files from a counterparty Automatically retries to send requests that encounter recoverable errors and switches SAGs if configured Correlates delivery notifications to the related transfer and provides them to business applications Supports new SWIFTNet 7 features including: File distribution (receiving part) File copy (T-Copy and Y-Copy) Output channels SnF system recovery Support of Application Service Profiles With SWIFTNet 7, to check whether a relationship exists is also performed for InterAct and FileAct transfers, based on the definitions in the Application Service Profiles distributed by SWIFT. All WebSphere Business Integration for Financial Networks services interfaces, including MSIF services and business applications, are implemented using WebSphere MQ messages: When the MSIF Transfer Service receives, from an application, a business message to be sent within an InterAct message, it creates the InterAct message and inserts the business message as its payload. When the MSIF Transfer Service IBM United States Software Announcement IBM is a registered trademark of International Business Machines Corporation 6

7 receives this InterAct message from the SWIFTNet, it extracts the business message from the payload of the InterAct message and forwards the business message to the receiving application to provide a response. Optionally, responses to received InterAct messages can be generated automatically by the MSIF Transfer service. When the MSIF Transfer Service has a file transfer, the application can either pass the file directly with the request or indicate the file location. The MSIF Transfer Service exchanges files with a SAG by using either the MQHA feature of the SAG or by using a Network File System, either directly or via a Remote File Handler. The MSIF feature provides all the commands needed to operate the store-andforward queues and channels used by InterAct and FileAct services. Financial Transaction Manager The Financial Transaction Manager feature contains the following industry software accelerators (specifications, standards, and physical code) that have been developed on top of the IBM industry-leading WebSphere middleware software to enable a platform for payments processing. Financial Transaction Manager is a service-oriented architecture (SOA) industry software package for the implementation of an integration layer on top of WebSphere Message Broker (an IBM Enterprise Service Bus) to manage, orchestrate, and monitor financial transactions. It provides the functionality to create and collect the state of transactions while providing integration capability as well as common data and message models based on an Industry Standard (ISO 20022). Financial Transaction Manager includes the following core components: A conceptual data model that supports the persistence of payment objects (files, batches, transactions, acknowledgements, and more), partner profile data, service, and channel definitions. It holds a rich repository of payment data stored from the ISO based Internal Standard Format (ISF), which provides rich views of payments from the Financial Transaction Manager user interface and for interrogation using the Transaction Processing Facility's MIS or other reporting products. This data model is delivered as a set of Entity Relationship Diagrams, Data Dictionary documents, and Data Definition Language iddl) for DB2 on AIX and DB2 on z/os. A standardized message model based on ISO This reduces the number of point-to-point interactions, which enables a more agile approach to introducing new services and promotes reuse of processes. It is delivered as XML schemas for use in WebSphere Message Broker. An engine to manage transaction processing lifecycle in the form of a state machine for process flow execution. It is an event driven architecture and is driven by data derived from IBM Rational Software Modeler. It is delivered as WebSphere Message Broker projects and also uses an Eclipse plug-in for IBM Rational Software Modeler to extract data to drive the state machine. A configuration and administrative user interface to provide a view of the data model. It also supports appropriately authorized operations personnel interacting with the processing steps of a transaction (for example, resubmit a transaction). It is delivered as WebSphere Application Server Enterprise Archive (EAR) files. Documentation for the development methodology, user interface, installation and setup, message model, data model, and sample application. A sample application to demonstrate capability of the environment. It contains a sample process to demonstrate the processing of individual payments (SWIFT MT 103) and batch payments (PAIN.001) in the Financial Transaction Manager environment. It shows how to go from functional requirements to high level design to implementation of these processes in Financial Transaction Manager. It is delivered as WebSphere Message Broker projects. Benefits of Financial Transaction Manager: IBM United States Software Announcement IBM is a registered trademark of International Business Machines Corporation 7

8 Has real-time dashboards with necessary payments insights and proactive actions Accelerates bringing on board new corporate customers Provides the solution to processing large volumes of global disbursements and invoice presentments Offers flexibility and control over volume of payments requests Expands support for new payments schemes and types Effectively manages cost associated with the modernization and adoption of updated payments schemes and types as they are introduced, such as SEPA Direct Debit, SEPA Credit Transfer, Same-day ACH, and more Accessibility by people with disabilities A U.S. Section 508 Voluntary Product Accessibility Template (VPAT) containing details on accessibility compliance can be requested at Business Partner information If you are a Direct Reseller - System Reseller acquiring products from IBM, you may link directly to Business Partner information for this announcement. A PartnerWorld ID and password are required (use IBM ID). Value Unit-based pricing Value Unit pricing for eligible IBM System z IBM International Program License Agreement (IPLA) programs enables a lower cost of incremental growth and enterprise aggregation. Each System z IPLA product with Value Unit pricing has a single price per Value Unit and a conversion matrix, called Value Unit Exhibit, for converting from some designated measurement to Value Units. Most commonly, Millions of Service Units (MSUs) is the measurement designated by IBM to be converted to Value Units. Some other measurements are engines or messages. Since MSUs are the most common measurement, that measurement will be used for the remainder of this description. Value Unit pricing offers price benefits for you. For each System z IPLA program with Value Unit pricing, the quantity of that program needed to satisfy applicable IBM terms and conditions is referred to as the required license capacity. Each of the various Value Unit Exhibits stipulate that the larger your required license capacity, the fewer Value Units per MSU you will need. Value Unit Exhibits are uniquely identified by a three digit code and referred to using the nomenclature VUExxx, where xxx is the three digit code. Subsequent acquisitions of Value Unit priced programs offer additional price benefits. The quantity of each System z IPLA program that you have acquired is referred to as entitled license capacity. If you wish to grow your entitled license capacity for a System z IPLA program, the calculation to determine additional needed Value Units is based upon the number of Value Units already acquired. For each System z IPLA program with Value Unit pricing, you should: Determine the required license capacity, in MSUs Aggregate the MSUs across the enterprise Convert the total MSUs to Value Units, using the applicable Value Unit Exhibit Multiply the price per Value Unit by the total number of Value Units to determine the total cost IBM United States Software Announcement IBM is a registered trademark of International Business Machines Corporation 8

9 To simplify conversion from the designated measurement to Value Units or viceversa, use the Value Unit Converter Tool. For additional information or to obtain a copy of the Value Unit Converter Tool, visit the Value Unit Converter Tool website Note that Value Units of a given product cannot be exchanged, interchanged, or aggregated with Value Units of another product. To determine the required license capacity for the System z IPLA program you selected, refer to the Terms and conditions section. Product positioning WebSphere Business Integration for Financial Networks is the IBM messaging solution for financial message processing, providing a highly flexible messaging infrastructure for financial applications, and takes advantage of new technologies while establishing a single window to SWIFTNet. Most financial institutions have the need to connect various SWIFTNet services seamlessly to backend business applications in order to: Exchange high-value financial messages with counterparts or infrastructures such as Real Time Gross Settlement (RTGS) and netting systems using the SWIFTNet FIN service Interactively exchange messages with infrastructures such as Continuous Linked Settlement (CLS) or the real-time gross settlement system TARGET2 to query status or account information Exchange files of financial messages with counterparts or infrastructures (for example, passing files to automatic clearing houses in the SEPA context) This integration is done many times in individual lines of business (LOB) as a unique silo for that LOB using different products for different SWIFTNet services. One product accessing all these services provides significant benefits. In addition to the consolidated access to SWIFTNet, an application should support easy integration to backend business applications via familiar and proven middleware. This integration, including message paths, needs to be tailored according to the specific demands of each customer. While the goal is to exchange as many messages as possible with straight-through processing, there are still situations where invalid messages are provided that have to be corrected, or messages have to be created manually. In addition to handling the requested amount of data in a straight-through-processing environment reliably, a single window to SWIFTNet has to address the need for an easy-to-use graphical interface for message entry and repair. WebSphere Business Integration for Financial Networks participates in the IBM Banking Industry Framework, offering unique possibilities to build SOA implementations and address many requirements of business integration. It can be used as a financial message-based integration layer and a network interface layer to build solutions. WebSphere Business Integration for Financial Networks provides a set of preintegrated solutions, built on our highly scalable platform designed to enable users to gain visibility and control of payments transactions, manage liquidity, balance financial risk, and facilitate effective financial planning and performance management. It provides the integration layer to manage and monitor messaging traffic, reduce integration complexity and increase performance, scale and reliability in the payments flow process. Wholesale Payments: This solution is a set of IBM products and services that includes WebSphere Business Integration for Financial Networks. With this solution, you can integrate and manage payment processes across your enterprise and beyond, and streamline related processes, including high-value, bulk, and IBM United States Software Announcement IBM is a registered trademark of International Business Machines Corporation 9

10 cross-border payments, as well as cash management and treasury services. By streamlining these processes, you can increase efficiency and reduce your operational costs. Liquidity Management: IBM Liquidity Manager offers centralized management of multicurrency and multichannel liquidity. This liquidity is managed across RTGS, netting, and correspondent channels, as well as for nostro accounts. Its functions include monitoring, forecasting, matching, and reconciliation, and rules-based scheduling. Bulk Payments: Based on the SWIFTNet FileAct service, this solution enables you to exchange bulked payments with your counterparts. To reduce file processing cost, WebSphere Business Integration for Financial Networks provides configurable filecompression capabilities. Cash Reporting: This solution uses WebSphere Business Integration for Financial Networks to access and provide comprehensive cash reporting information. It increases operational efficiency and improves the level of services financial institutions can provide to their clients. This solution is also certified by SWIFT. Investment Funds Distribution: This solution processes investment funds in compliance with ISO XML message templates. It includes message processing to support order initiation, order confirmation, order status, and balance reporting. Assisted by the single-window infrastructure of WebSphere Business Integration for Financial Networks, this solution helps reduce cost, improve operational efficiency, and enhance straight-through processing. Statement of direction IBM intends to end the support for IBM WebSphere Business Integration for Financial Networks for z/os V2.2 and IBM WebSphere Business Integration for Financial Services for Multiplatforms V2.2 effective with the planned end of support of SWIFTNet 6. The listed versions will only support SWIFTNet 6 but will not support SWIFTNet 7. All statements regarding IBM's plans, directions, and intent are subject to change or withdrawal without notice. Program number Program Program number VRM name 5655-FIN V3.1.1 IBM WebSphere Business Integration for Financial Networks for z/os 5724-D96 V3.1.1 IBM WebSphere Business Integration for Financial Networks for Multiplatforms Product identification number Subscription and Program PID number Support PID number 5655-FIN 5639-N51 Education support Contact your local IBM representative for more information. IBM United States Software Announcement IBM is a registered trademark of International Business Machines Corporation 10

11 Offering Information Product information is available via the Offering Information website Publications No hardcopy publications are shipped with these programs. The following publications are available in PDF format and in the Information Center at WebSphere Business Integration for Financial Networks (for both z/os and Multiplatforms in separate publications) V3.1.1 is described in: Concepts and Components Planning, Installation, and Customization System Administration Message Entry and Repair Facility User's Guide Relationship Management Application User's Guide Application Programming Messages and Codes Program Directory The Migration Guide is available at WebSphere Business Integration for Financial Networks Financial Transaction Manager feature: Installation, Migration, and User Guides can be downloaded from All other documentation needed to develop solutions based on Financial Transaction Manager is available on a Financial Transaction Manager documentation CD. Technical information Specified operating environment Hardware requirements WebSphere Business Integration for Financial Networks for z/os V3.1.1 z/os hardware: Any hardware explicitly compatible with and fully capable of running the specified operating system, the corresponding software, and associated applications unmodified. Responsibility to provide a statement of full compatibility between machines lies with the original equipment provider. Workstation requirements A Microsoft Windows workstation is required for: WebSphere Message Broker Toolkit. WebSphere Message Broker Configuration Manager, if the WebSphere Message Broker V6.1, is used. IBM United States Software Announcement IBM is a registered trademark of International Business Machines Corporation 11

12 For detailed information for the version used refer to A Microsoft Windows workstation is required for the Rational Software Modeler or Rational Software Architect used for the Financial Transaction Manager feature. SWIFTAlliance Gateway 6.1, 6.3, or 7.0 workstation Refer to S.W.I.F.T. for hardware requirements. Visit In addition to the SWIFT requirements, the following hardware and storage items are required for the WebSphere Business Integration for Financial Networks SWIFTAlliance Gateway Add-On: 120 MB of disk space is recommended. 30 to 100 MB of disk space for traces (depending on trace level). The Support for SWIFTNet FIN and Messaging Services for SWIFTNet InterAct and FileAct features require a LAN-based SWIFT HSM box. (USB HSM devices are not supported.) WebSphere Business Integration for Financial Networks for Multiplatforms V3.1.1 Any hardware explicitly compatible with and fully capable of running the specified operating system, the corresponding software, and associated applications unmodified. Responsibility to provide a statement of full compatibility between machines lies with the original equipment provider. Workstation requirements The hardware requirements are the same as those of WebSphere Business Integration for Financial Networks for z/os V Software requirements WebSphere Business Integration for Financial Networks for z/os V3.1.1 For the latest updates of software requirements and the required RSUs, PUTs, CSDs and FixPack levels, check the Preventive Service Planning (PSP) Bucket information. PSP information is provided in RETAIN and on IBM e-support. Visit WebSphere Business Integration for Financial Networks for z/os V3.1.1 Base feature: IBM z/os V1.10 (5694-A01), or IBM z/os V1.11, or IBM z/os V1.12. IBM DB2 UDB for z/os, V8.1 (5625-DB2), or IBM DB2 UDB for z/os, V9.1 (5635- DB2), or IBM DB2 UDB for z/os, V10.1 (5605-DB2). For the Financial Transaction Manager feature: IBM DB2 UDB for z/os, V9.1 (5635-DB2), or IBM DB2 UDB for z/os, V10.1 (5605-DB2), or any DB2 UDB for z/os version has to include SQLJ feature IBM DB2 Utilities Suite for z/os, V8.1 (5655-K61), or IBM DB2 Utilities Suite for z/os, V9.1 (5655-N97), or IBM DB2 Utilities Suite, V10.1 (5655-V41). IBM WebSphere MQ for z/os, V7.0.1 (5655-R36). IBM WebSphere MQ for z/os, V7.0.1 (5655-R36) client attachment feature installed on the z/os system is required if the SWIFTAlliance Gateway workstation or the WebSphere Application Server environment uses WebSphere MQ Client and connect to WebSphere MQ for z/os, V IBM United States Software Announcement IBM is a registered trademark of International Business Machines Corporation 12

13 IBM WebSphere Message Broker for z/os, V6.1 (5655-M74) plus WebSphere Message Broker V6.1 Toolkit, or IBM WebSphere Message Broker for z/os, V7.0.0 (5655-V60) (limited license included) plus WebSphere Message Broker V7.0.0 Toolkit (limited license included). For WebSphere Message Broker for z/os, V7.0.0, a mandatory WebSphere Business Integration for Financial Networks V3.1.1 APAR is required. Furthermore, WebSphere Business Integration for Financial Networks V3.1.1 supports this broker version only for z/os V1.11, or later. For details refer to the Preventive Service Planning bucket. IBM 31-bit SDK for z/os, Java 2 Technology Edition, V5 (5655-N98) (for use with IBM WebSphere Message Broker for z/os V6.1 only) or IBM 64-Bit SDK for z/os, Java Technology Edition, V6 (5655-R32) (for use with IBM WebSphere Message Broker for z/os V7.0 only). SWIFT Alliance Gateway (for details, refer to the SWIFTAlliance Gateway Workstation section). If the optional message warehouse reporting based on IBM Cognos is used, IBM Cognos 8 Business Intelligence V8.4.0 (5724-W12) or IBM Cognos Business Intelligence Reporting V10.1 (5724-W19, limited license included). Required are the following components: Cognos Connection Report Studio Cognos Viewer If for the optional infrastructure monitoring, based on the Java Management Extensions (JMX) standard IBM Tivoli is used, IBM Tivoli Monitoring V6.2.2 (5724-C04) is required. If the Relationship Management Application is used: IBM WebSphere Application Server for z/os, V7.0 (5655-N02) or IBM WebSphere Application Server, V7.0 (5724-J08), or IBM WebSphere Application Server Network Deployment, V7.0 (5724-H88) (the platforms supported are AIX, Solaris, and Windows: each is available in a 32-bit or a 64-bit version). Microsoft Internet Explorer 8.0 in full function mode or Mozilla Firefox 3.5 or 3.6. IBM C/C++ compiler (5694-A01) (optional and to be used if modified sample programs are to be compiled). WebSphere Business Integration for Financial Networks for z/os V3.1.1 features: WebSphere Business Integration for Financial Networks for z/os V3.1.1 (5655- FIN) Base and its prerequisites. Financial Message Transfer - requires the Support for SWIFTNet FIN feature. Messaging Services for SWIFTNet InterAct and FileAct - Network File System (NFS) server, corresponding to the z/os system installed is required if Messaging Services for SWIFTNet InterAct and FileAct feature is using NFS. Message Management If Message Entry and Repair is used: IBM WebSphere Application Server (refer to the software requirements for the Relationship Management Application). Microsoft Internet Explorer 8.0 in full function mode or Mozilla Firefox 3.5 or 3.6. SWIFTNet Funds, SWIFTNet Exceptions and Investigations, and SWIFTNet System Message schema files (optional and to be used if message definitions in the wizard of WebSphere Message Broker Toolkit Routing are required). They have to be downloaded from SWIFT website. IBM United States Software Announcement IBM is a registered trademark of International Business Machines Corporation 13

14 WebSphere Business Integration for Financial Networks for Multiplatforms V3.1.1 For the latest updates of software requirements, check the Service Information provided on IBM e-support. Visit IBM AIX V5.3 (5765-G03) or IBM AIX Standard Edition, V6.1 (5765-G62) or IBM AIX Standard Edition V7.1 (5765-G98). IBM DB2 Enterprise Server Edition V9.5 (5765-F41) or IBM DB2 Enterprise Server Edition V9.7 (5765-F41). IBM WebSphere MQ V7.0.1 (5724-H72). IBM WebSphere Message Broker V6.1 (5724-J05), plus WebSphere Message Broker V6.1 Toolkit and Configuration Manager, or IBM WebSphere Message Broker V7.0.0 (5724-J05) (limited license included) plus WebSphere Message Broker V7.0.0 Toolkit (limited license included) For WebSphere Message Broker V7.0, a mandatory WebSphere Business Integration for Financial Networks V3.1.1 APAR is required. For details, refer to Service Information in the support pages of the product documentation. IBM Java Runtime Environment 1.5.0, which is available in a 32-bit or 64-bit version (for use with WebSphere Message Broker V6.1 only) or IBM Java Runtime Environment (64-bit for use with WebSphere Message Broker 7.0 only). SWIFT Alliance Gateway (for details, refer to the SWIFTAlliance Gateway Workstation section). IBM XL C/C++ Enterprise Edition V (for use with WebSphere Message Broker ) or V11.1 (for use with WebSphere Message Broker ) for AIX Runtime Environment component. If the optional message warehouse reporting using IBM Cognos is used, IBM Cognos 8 Business Intelligence V8.4.0 (5724-W12) or IBM Cognos Business Intelligence Reporting V10.1 (5724-W19, limited license included). Required are the following components: Cognos Connection Report Studio Cognos Viewer If for the optional infrastructure monitoring based on Java Management Extensions (JMX) standard IBM Tivoli is used, IBM Tivoli Monitoring V6.2.2 (5724-C04). If the Relationship Management Application is used: IBM WebSphere Application Server, V7.0 (5724-J08) or IBM WebSphere Application Server Network Deployment V7.0 (5724-H88) (the platforms supported are AIX, Solaris and Windows; each is available in a 32-bit or a 64-bit version). Microsoft Internet Explorer 8.0 in full function mode or Mozilla Firefox 3.5 or 3.6. WebSphere Business Integration for Financial Networks for Multiplatforms V3.1.1 features: WebSphere Business Integration for Financial Networks for Multiplatforms V3.1.1 (5724-D96) Base and its prerequisites. Financial Message Transfer Requires the Support for SWIFTNet FIN feature. Refer to S.W.I.F.T. for software requirements. IBM United States Software Announcement IBM is a registered trademark of International Business Machines Corporation 14

15 Requirements of each Remote File Handler (RFH) workstation An RFH workstation is a workstation on which a SWIFTNet Remote File Handler (RFH) runs. Unlike the SAG workstation, an RFH workstation, like the host, can be located behind a firewall. If you use the MSIF services, and if you use Network File System (NFS) to share files between workstations and the host, storing the files to be transferred on an RFH workstation instead of on the SAG workstation can help keep the files more secure. Refer to S.W.I.F.T. for the requirements of this workstation. Software requirements for documentation Adobe Acrobat Reader 8.0 (or later), or an equivalent tool, for displaying PDF documents. The program's specifications and specified operating environment information may be found in documentation accompanying the program, if available, such as a readme file, or other information published by IBM, such as an announcement letter. Documentation and other program content may be supplied only in the English language. Planning information Software Maintenance is included with licenses purchased through Passport Advantage and Passport Advantage Express. Installation and technical support is provided by the Software Maintenance offering of the IBM International Passport Advantage Agreement. This fee service enhances your productivity, with voice and electronic access into IBM support organizations. Direct customer support For technical support or assistance, contact your IBM representative or visit Packaging WebSphere Business Integration for Financial Networks for z/os V3.1.1 WebSphere Business Integration for Financial Networks for z/os V3.1.1 Base feature consists of: A 3590 tape containing WebSphere Business Integration for Financial Networks for z/os V3.1.1 WebSphere Business Integration for Financial Networks for z/os V3.1.1 License Information, GH WebSphere Business Integration for Financial Networks V3.1.1 SWIFTAlliance Gateway Add-On CD (LCD7-2598) Limited License WebSphere Message Broker V tapes containing WebSphere Message Broker for z/os V7.0 Program Directory (GI ) License Information (GC ) 2 CDs containing WebSphere Message Broker V7.0 Toolkit for Windows (LCD and LCD7-4430) Limited License Cognos Business Intelligence Reporting V CDs containing Cognos BI Reporting V10.1 for AIX, Oracle Solaris, Linux x86, Linux on pseries, and Windows (all 32 bi and 64 bit), samples, and supplementary languages documentation IPLA Booklet (Z ) IBM United States Software Announcement IBM is a registered trademark of International Business Machines Corporation 15

16 Non-Base features License Information (GH ) is included with each WebSphere Business Integration for Financial Networks for z/os V3.1.1 feature. The WebSphere Business Integration for Financial Networks for z/os V3.1.1 Financial Transaction Manager feature consists of a documentation CD (LCD7-2606). WebSphere Business Integration for Financial Networks for Multiplatforms V3.1.1 WebSphere Business Integration for Financial Networks for Mutiplatforms V3.1.1 Base feature consists of: WebSphere Business Integration for Financial Networks for Multiplatforms V3.1.1 product code and License Information and Quickstart Guide copy - CD (CZXM7NA) or eimage (CZXN1NA) WebSphere Business Integration for Financial Networks V3.1.1 SWIFTAlliance Gateway Add-On - CD (CZXM8NA) or eimage (CZXN2NA) Limited License WebSphere Message Broker V7.0 1 CD containing WebSphere Message Broker V7.0 for AIX (CD CZEC4ML, eimage CZED4ML) 2 DVDs containing WebSphere Message Broker V7.0 for Windows (DVDs CB300ML and CB301ML, eimages: CZEE2ML, CZEE3ML, and CZEE4ML), Limited License Cognos Business Intelligence Reporting V CDs containing Cognos BI Reporting V10.1 for AIX, Oracle Solaris, Linux x86, Linux on System p, and Windows (all 32 bit and 64 bit), samples, and supplementary languages documentation Quickstart Guide as hardcopy (CF30DNA) or eimage (CZXN0NA) Non-Base features: The WebSphere Business Integration for Financial Networks for Multiplatforms V3.1.1 Financial Transaction Manager feature consists of a documentation CD (CZXM9NA) or eimage (CZXN3NA) and Quickstart Guide as hardcopy (CF30DNA) or eimage (CZXN0NA). Security, auditability, and control WebSphere Business Integration for Financial Networks uses the security and auditability features of the operating system. The customer is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities. Software Services IBM Software Services has the breadth, depth, and reach to manage your services needs. You can leverage the deep technical skills of our lab-based, software services team and the business consulting, project management, and infrastructure expertise of our IBM Global Services team. Also, we extend our IBM Software Services reach through IBM Business Partners to provide an extensive portfolio of capabilities. Together, we provide the global reach, intellectual capital, industry insight, and technology leadership to support a wide range of critical business needs. To learn more about IBM Software Services or to contact a Software Services sales specialist, visit IBM United States Software Announcement IBM is a registered trademark of International Business Machines Corporation 16

17 Ordering information This product is only available via Passport Advantage. It is not available as shrinkwrap. Licensed function title Product group Product category IBM WebSphere IBM WebSphere IBM WebSphere Business Integration Business Business for Financial Networks components components for Multiplatforms V3.1.1 (PID 5724-D96) Charge metric Program name PID number Charge metric IBM WebSphere Business 5655-FIN Server Integration for Financial Networks for z/os V Base IBM WebSphere Business 5655-FIN Value unit Integration for Financial Networks for z/os V Support for SWIFTNet FIN - Financial Message Transfer - Messaging Services for SWIFTNet InterAct and FileAct - Message Management - Financial Transaction Manager IBM WebSphere Business Integration for Financial Networks for Multiplatforms V Base IBM WebSphere Business Integration for Financial Networks for Multiplatforms V Support for SWIFTNet FIN - Financial Message Transfer - Messaging Services for SWIFTNet InterAct and FileAct - Message Management - Financial Transaction Manager Resource Value Unit (RVU) 5724-D96 Server 5724-D96 Resource Value Unit RVU is a unit of measure by which the program can be licensed. RVU Proofs of Entitlement (PoEs) are based on the number of units of a specific resource used or managed by the program. Licensee must obtain sufficient entitlements for the number of RVUs required for licensee's environment for the specific resources as specified in the table below. RVU entitlements are specific to the program and the type of resource and may not be exchanged, interchanged, or aggregated with RVU entitlements of another program or resource. Refer to the program specific RVU table. Note: Some programs may require licenses for the resources available to and the resources being managed by the program. In that case, the following applies. In addition to the entitlements required for the resources used by the program directly, licensee must obtain entitlements for this program sufficient to cover the resources managed by the program. IBM United States Software Announcement IBM is a registered trademark of International Business Machines Corporation 17