IBM WebSphere Business Integration Server V4.3 integrates, automates, and manages business processes

Transcription

1 Software Announcement September 28, 2004 IBM WebSphere Business Integration Server V4.3 integrates, automates, and manages business processes Overview WebSphere Business Integration Server V4.3, the IBM business integration solution for process integration, workforce management, and enterprise application connectivity, enables you to: Create and deploy new business processes Synchronize business events in multiple systems Integrate applications on diverse platforms Transform information formats en-route between applications Link people into a new business approach What s new? Support for: Red Hat Enterprise Linux 3.0 and SUSE LINUX 8.1 for Intel 32-bit platforms Microsoft Windows 2003 runtime Sun Solaris 9 (Solaris 7 support withdrawn) New feature and performance release of WebSphere InterChange Server (ICS) and Toolset Eclipse Open Standards compatibility with WebSphere Studio AD/IE 5.1 MQ Workflow V3.5 and Message Broker V5 enhancements Adapter support for the new operating systems Key prerequisites Available on the following platforms: AIX Sun Solaris Microsoft Windows 2000 and 2003 Microsoft Windows XP (Tooling) HP-UX (PA-RISC) Linux (Red Hat, SUSE) For details, refer to the Software requirements and Hardware requirements sections. Planned availability dates September 30, 2004 (electronic software delivery including documentation) November 5, 2004 (media) At a glance WebSphere Business Integration Server V4.3 offers process management, process integration, workforce management, and enterprise application connectivity in a single solution. Delivers a broad spectrum of integration capabilities to suit any business challenge. Integrates people, partners, processes, and applications using a common infrastructure as a foundation. Maximizes the effectiveness of deployed business processes through real-time monitoring. Tailors refinements in processes to observed business process improvement needs, maximizing returns on incremental investments. Offers service-oriented architecture (SOA) and Enterprise Service Bus (ESB) architecture through mature, scalable support. This announcement is provided for your information only. For additional information, contact your IBM representative, call 800-IBM-4YOU, or visit the IBM home page at: IBM United States IBM is a registered trademark of International Business Machines Corporation

2 What it is Description The IBM Business Integration product portfolio provides the key capabilities needed for transforming business processes: Model business functions and processes Transform applications, processes, and data Integrate islands of applications, processes, and information Interact with resources anytime and anywhere Manage performance against business objectives Accelerate implementation of intelligent processes WebSphere Business Integration Server V4.3 delivers the integration capability by providing the IBM business integration solution for process integration, workforce management, and enterprise application connectivity. WebSphere Business Integration Server allows you to: Create and deploy new business processes Synchronize business events in multiple systems Integrate applications on diverse platforms Transform information formats en-route between applications Link employee groups as integral elements of process automation WebSphere Business Integration Server is particularly suited for solving integration problems through incremental implementation. The advanced architecture gives companies the greatest opportunity to reuse packaged application business logic and in-house application logic, as well as any process routines previously built to implement middleware logic. WebSphere Business Integration Server V4.3 is comprised of the following components: WebSphere ICS V4.3 WebSphere MQ Workflow V3.5 WebSphere Business Integration Message Broker V5.0.1 WebSphere Business Integration Toolset V4.3 Selected WebSphere Business Integration Adapters from the September 2004, release WebSphere MQ V and DB2 Universal Database Enterprise Server Edition V8.1 are included, only for restricted use with these components. Full licenses must be acquired for any purpose other than specified in the license. New content in WebSphere Business Integration Server V4.3 is primarily contained in the refresh of WebSphere ICS and WebSphere Business Integration Toolset V4.3. New in WebSphere ICS The focus for the V4.3 release is to deliver support for new operating systems, and address specific reliability, availability, and scalability enhancements requested by customers, together with significant performance and security improvements. For Microsoft Windows platform users, runtime support for Windows 2003 is introduced, in addition to Windows Tooling continues to be supported on Windows 2000 and Windows XP only. For Sun Solaris platform users, Solaris 9 (2.9) is now supported in addition to Solaris 8 (2.8). Solaris 7 (2.7) is no longer supported. New with this release, support for the Linux operating system running on Intel 32-bit architecture platforms is introduced. Both Red Hat Enterprise Linux 3.0 and SUSE LINUX 8.1 are supported by the ICS runtime as well as the WebSphere Business Integration Adapter components. Linux support is also included for Message Broker. The following reliability, availability, and serviceability enhancements have been made to ICS in this release. For details, refer to the Additional information section. Java Dynamic deployment Database connection retries Dynamic service calls Support for large business objects JMS transport optimizations Event sequencing Flow management Web-based Failed Event Manager Collaboration API for failed flows SNMP agent The following security enhancements have been made in this release. For details, refer to the Additional information section. Role-based access Role-based access clients Privacy/integrity Access audit log ICS addresses the need for data integrity in automating and synchronizing business activities executed across multiple applications as business processes. It provides a state full business object model that enables business processes to execute independently of the applications to which they connect, providing reusability of both process templates (collaborations) and the application adapters that connect ICS with the applications. ICS supports a compensation model rather than an XA model, complementing the MQ Workflow and Message Broker servers, by providing exception management for business applications that do not support XA, and business processes that extend outside the enterprise, which may be interrupted or long-lived. The ICS mapping (mediation) services include static, syntactical mapping as well as dynamic, semantic mapping of relationships between business objects described differently within each application. A work-in-progress service ensures key information of each application participating in a process is persistent during the processing of business events for recovery purposes. ICS is multithreaded, and can handle multiple processes and multiple instances of the same process concurrently. Sophisticated features to manage the ICS resources under load without manual intervention include flow governing and collaboration blocking. New in WebSphere MQ Workflow Workflow V3.5 was introduced into the release as a media refresh in April It consolidated service packs from the V3.4 and added these features: Expanded Workflow Portal client functions: initiate, observe, and participate in business processes Generalized framework for service-oriented program execution

3 Shared global data container Activity instance list Enhanced LDAP bridge with role-based authorization mapping e-support: Contextual online help in Web client Microsoft Windows 2003 Sun Solaris 9 Oracle 9.2 on AIX, HP-UX, and Solaris WebSphere Application Server V5.1 support WebSphere Portal Server V5 support Support Pac WA0C is downloadable for a new feature, the WebSphere MQ Workflow Native Java API. CSD1 for MQ Workflow V3.5 is downloadable and adds support for: Interfacing with WebSphere Application Server ND on distributed Platforms Interfacing with WebSphere Application Server ND on z/os A Workflow Web-client on Mozilla-based Web Browsers Microsoft Active Directory (using LDAP bridge) The role of MQ Workflow in WebSphere Business Integration Server is to support long running processes that require the participation and intervention of human workgroups. Optimized for parallel processing, MQ Workflow executes process definitions captured during modeling and ensures business functions are performed reliably and correctly. It supports the transactional integrity of WebSphere MQ messaging for application exceptions needing to be managed in an XA (2-phase commit) compliant architecture. It manages processes from sub-seconds, to months, with full restart and recovery making it fault tolerant. Modeling can be performed by using its own workflow tooling, or by accepting definitions from WebSphere Business Integration Modeler. Modeler allows design and simulation of ROI at the business analyst level, delivering its metadata for execution by the workflow runtime engine. Separating the process layer from the application layer, MQ Workflow delivers the design and execution capabilities for SOAs, where the services are reusable, and the impact and cost of changing how the service is implemented is minimized. New in WebSphere Business Integration Message Broker CSD3 for Message Broker V5 is supported in this release. Two versions of the Message Broker toolkit are available. The original version provides the Eclipse 2.0 workbench with an install option for WebSphere Studio AD/IE 5.0. The new version (V5.1) provides Eclipse 2.1 support with an install option for WebSphere Studio AD/IE 5.1. Note: Eclipse 2.0 and 2.1 use different models for artifacts; therefore, the use of mixed development environments is not recommended. Customers of WebSphere Business Integration Server 4.3 will receive both versions of the Message Broker toolkit. The role of the Message Broker component within WebSphere Business Integration Server enables solution designers to: Implement hub and spoke-based application integration Visualize in-flight message mediation and routing through the use of a visual design environment Transform, augment, apply rules, and route or distribute message-based data between high-performance systems Publish business information and application data from multiple applications to multiple authenticated subscribing applications using dynamic content and topic-based techniques The Message Broker transforms and enriches in-flight information to provide a level of intermediation between applications that use different message structures and formats. It features an open tooling framework where functions defined as nodes can be wired together and visualized as flow sequences to operate on the content of the messages. A Java API plug-in facility allows third-party processing nodes to manipulate message data and extend the broker capabilities. For example, specialist message format parsers and custom Java application invocation from message flows. New in WebSphere Business Integration Toolset V4.3 The focus of this release is on productivity enhancements together with Eclipse Workbench 2.1 compatibility with WebSphere Studio AD/IE V5.1 and V For details, refer to the Additional information section. Activity Editor Map Designer Integrated Test Environment (ITE) Connector Configurator Collaboration API for failed flows Deployment Configuration Tool Compile/Deploy Progress Indicator Collaboration deployment performance Installer Collaborations XML Parser replacement WebSphere Business Integration Adapters September 2004, release The primary focus for the September 2004, adapter release is to support the new platforms supported by ICS V4.3. The Adapter Framework is upgraded with JDK in this release. WebSphere Business Integration Adapter Framework V2.6 supports WebSphere Business Integration Adapters delivered in the September 2004, adapter release as well as adapters delivered in the June 2004, and December 2003, releases. For more information on adapter compatibility, refer to the Software requirements section. Also included with V4.3 is entitlement to use the WebSphere Business Integration Adapter components listed below for the purposes of integrating the ICS to the Message Broker and MQ Workflow components, and providing Web Services, MQ, and JMS adapter support to ICS: WebSphere Business Integration Adapter Framework V2.6 WebSphere Business Integration Data Handler for XML V2.7 WebSphere Business Integration Adapter for WebSphere MQ V2.7 WebSphere Business Integration Adapter for WebSphere MQ Workflow V2.7 WebSphere Business Integration Adapter for WebSphere Business Integration Message Broker V2.7 WebSphere Business Integration Adapter for JMS V

4 WebSphere Business Integration Adapter for Web Services V3.4 Note: The name of the adapter used to integrate Message Broker with ICS has been changed from Adapter for WebSphere MQ Integrator Broker to Adapter for WebSphere Business Integration Message Broker. Per-establishment authorizations are provided for WebSphere Business Integration Adapter Framework and WebSphere Business Integration Data Handler for XML. Multiple instances of these may be used at one location to implement a WebSphere Business Integration solution. Per-application instance authorizations are included for each adapter. They may each be used once only to provide a connection between one instance of a user s application and the ICS as part of the WebSphere Business Integration Server solution. It is highly recommend that customers acquire separate establishment authorizations for the WebSphere MQ, JMS, and Web Services adapters. Accessibility by people with disabilities This offering does not fully support use by people with disabilities. However, this offering is largely compatible with the accessibility features included with the supported operating systems. Product positioning WebSphere Business Integration, a comprehensive business integration platform, enables businesses to implement very rapid solutions to specific integration problems, and then grow with the requirements to solve complex business integration problems requiring a wide variety of integration capabilities. WebSphere Business Integration provides, in one offering, a business integration platform that can be used to: Solve many different business integration problems Integrate applications or systems on diverse platforms Create and deploy new processes Link people into a new business approach A business integration platform can help you meet a wide range of integration needs: Rapid deployment of integration to support an immediate departmental project to counter a competitive business threat Linking of a worldwide call center rollout to a range of local and central support systems to improve customer satisfaction Adopting a new application package that needs to be connected to other systems Introducing supply chain management to connect all parts of the value chain Creating a blueprint for an enterprise-wide integration platform to support a long-term strategic initiative These diverse needs imply a wide spectrum of integration requirements from straightforward application connectivity to full business process integration and include extending solutions beyond the traditional boundaries of the enterprise. Application connectivity addresses the requirements for connecting various applications, allowing information to be shared and used across the heterogeneous application systems typically found in the enterprise. Business process integration allows the business to control and coordinate activities across various process constituents, people and applications, internal and external to the enterprise, in ways that fully and efficiently implement defined business processes. With WebSphere Business Integration Server businesses can start small and scale rapidly. They can support multiple platforms and implement a reusable open integration infrastructure that spans departmental initiatives, and evolves as more projects emerge, becoming the integration backbone of whole enterprise. With IBM s open, modular, standards-based WebSphere middleware, businesses can decide which project to implement first, and achieve the end-to-end integration with a phased approach. WebSphere Business Integration Toolset provides comprehensive tooling to generate the artifacts required for an enterprise integration solution (including process collaborations, workflows, message flows, and business objects). The toolset specifically provides the tools for the artifacts of the WebSphere ICS. The WebSphere Business Integration overall architecture enables projects to be designed and implemented based on the concept of separation of function: Core business application logic remains in the packaged and legacy applications that are being integrated Logic specific to routing and transformation is contained in an application connectivity layer Cross-application business process logic is contained in the process integration layer This means that WebSphere Business Integration Server is particularly suited for solving integration problems through incremental implementation. The advanced architecture gives companies the greatest opportunity to reuse packaged application business logic and in-house application logic, as well as any process routines previously built to implement middleware logic. Reference information Software Announcement , dated April 9, 2002 Software Announcement , dated May 20, 2003 Software Announcement , dated September 9, 2003 Software Announcement , dated December 9, 2003 Software Announcement , dated December 9, 2003 Software Announcement , dated March 23, 2004 Software Announcement , dated June 22, 2004 Software Announcement 204-XXX, (RFA40090) dated September 28, 2004 Software Announcement 204-XXX, (RFA40177) dated September 28, 2004 Trademarks WebSphere, AIX, DB2 Universal Database, z/os, and MQ Integrator are registered trademarks of International Business Machines Corporation in the United States or other countries or both. Intel is a trademark of Intel Corporation

5 Microsoft and Windows are trademarks of Microsoft Corporation. Java is a trademark of Sun Microsystems, Inc. Linux is a trademark of Linus Torvalds in the United States, other countries or both Other company, product, and service names may be trademarks or service marks of others

6 IBM US Announcement Supplemental Information September 28, 2004 New in WebSphere ICS Additional information The following enhancements have been made to ICS in this release. Reliability, availability, and serviceability enhancements Java The Java Runtime Environment (JRE) and Java Development Kit (JDK) versions for ICS, Adapter Framework, and WBI Toolset has been upgraded from V1.3.1 to V1.4.2 with this release. This has contributed to the overall performance improvements. Dynamic deployment The requirement to stop the ICS before adding or removing an adapter connector or updating the collaboration and business objects incurs an overhead, especially the more ICSs you manage. The need to maintain consistency of the cross-dependencies in a live server takes priority but with this release additional hot deployment scenarios are made available for adapter connections, collaborations, business objects, and maps to avoid stopping an ICS to make changes. Database connection retries In this release, ICS will attempt to establish database connections when these connections are broken due to a database shutdown or a temporary network failure. For work-in-progress transactions, ICS may be able to re-execute a failed transaction. The number of retries and the time interval between retries is configurable. This feature allows the automatic recovery from a few scenarios where previously the ICS would require a reboot. Dynamic service calls Dynamic service calls provide a mechanism for collaboration developers to make service requests to any collaboration or connector at runtime without having to bind explicitly to a destination port. In prior versions of ICS, the choice of a destination connector or collaboration to which a service request is made had to be determined at compile time in a static manner. In V4.3, dynamic service calls can be enabled using a new API that is available to collaboration developers. Dynamic service calls are synchronous in nature. Support for large business objects The goal of this enhancement is to increase the physical size of business objects passed through the ICS without causing memory exhaustion issues. A large business object is usually one that has a large hierarchy of attributes, or is a wrapper object for multiple business objects for batch processing. JMS transport optimizations Several enhancements are provided to improve event handling performance and avoid bottlenecks in processing events and event recovery at the ICS connector controller interface when the JMS transport is selected. Some of these enhancements are already implemented for the WebSphere MQ interface in previous 4.2 releases. An optimized JMS service will be selectable, which will deliver improvements when business objects are reasonably large, and the database overheads of caching them are higher. Optimizations also include caching improvements, batching non-critical activities, and synchronizing critical sections and expensive operations in parallel. Event sequencing The ability to engage or disengage the event sequencing service within ICS has been added. Where event sequencing is not critical to a process, throughput can be enhanced if this feature is disabled. Flow management A new event status of USER_GENERATED has been added to distinguish between saved failed events and other events. A saved failed event can subsequently be deleted or resubmitted. The status of a saved failed event will transform from USER_GENERATED to USER_GENERATED_RESUBMITTED_INPROGRESS when it is resubmitted to the ICS, and will transform back to USER_GENERATED again in case of repeat of a failure. The Flow Manager tool has been enhanced to display these new status messages. Web-based Failed Event Manager This new browser-based tool provides the same functions as Flow Manager. It supports the new event status (USER_GENERATED) and provides the ability to retrieve, resubmit, and delete failed events. Collaboration API for failed flows A programming interface is provided to support custom administration solutions for failed flows outside of ICS. This will provide the capability to save failed events with the collaboration s subscribed event type, and to retrieve, delete, and resubmit failed events. For example, when iterating through the child business objects in a batch event, the API allows customers to save individual failed flows and manage these failed records in user collaborations. Saving failed events delivered through the Server Access Interface (WebSphere InterChange Access) is not supported in this release. SNMP agent In this release, the SNMP stack underpinning the ICS SNMP agent, previously provided by a third-party supplier, is replaced with an SNMP protocol stack provided by Tivoli. The SNMP agent does not change at the user level. A new MIB is provided for This announcement is provided for your information only. For additional information, contact your IBM representative, call 800-IBM-4YOU, or visit the IBM home page at: IBM United States IBM is a registered trademark of International Business Machines Corporation

7 loading into the customer s chosen enterprise management console (such as Tivoli TME ). Security enhancements Role-based access A role-based authentication service is provided in this release. This can be switched on and off by the system administrator for backwards compatibility when migrating from an earlier release. Roles and their privileges are set up by the administrator. When role-based access is turned on, all permissions/access checks will be operational. Roles and privileges are stored in the ICS repository. A Lightweight Directory Access Protocol (LDAP) V3 interface is also provided to enable user names and passwords to be managed and authenticated from an external directory service that supports LDAP. Role-based access clients WebSphere Business Integration Adapters configured to use MQ or IIOP as transport and IIOP clients will be authenticated. By default, adapters using MQ or IIOP as the delivery transport will use the guest identity to login. Authentication for Internet-based client applications connecting via the Server Access Interface (SAI) will be enforced in this release. An API call is added for the client call to be authenticated. Also for SAI clients, the user ID is made available to the collaboration. A collaboration can now be designed to check if the caller is in a specific role and to customize the business process based on caller identity. Privacy/integrity The ability to encrypt the content of messages sent by the ICS is provided in this release as a privacy option. This can be for all messages including system messages or for an individual business object. The ability to add a digital signature is also provided. Access audit log When providing role-based access, the ability to audit who logs in under which role is desirable to ensure no accidental or deliberate breaches of the security policy have occurred. The ability to create an audit log is provided in this release. The administrator can configure where the audit log files will be created by ICS. This should be secured from unauthorized viewing or editing using the operating system capabilities. New audit files can be created on a daily, weekly, or monthly basis, as required, to quickly locate the period of interest. The maximum file size can also be set. When it is exceeded, it triggers a new file to be created. A fixed file naming format allows for 999 files per day, week, or month. New in WebSphere Business Integration Toolset V4.3 The focus of this release is on productivity enhancements together with Eclipse Workbench 2.1 compatibility with WebSphere Studio AD/IE V5.1 and V Activity Editor Activity Editor is the component used by both Map Designer and Process Designer tools for creating custom mapping transformations and actions for collaboration templates. Various fixes and enhancements have been made including import/export of activity definitions and contextual labeling of custom function blocks. The properties of custom function blocks can now be configured directly from the Map Designer tool. Map Designer With today s enterprise business applications, business objects can consist of hundreds of attributes. With such large business objects, it is very time-consuming and repetitive to create mapping files. To improve usability, the Map Designer has been enhanced with auto-mapping features. Auto-mapping can be set to ignore upper/lower case differences, ignore mismatched data types, and map by prefix or suffix. A reverse mapping capability is added to speed up the creation of target maps from source maps. For example, a Split becomes a Join and a Join becomes a Split while transformations that cannot be automated, are listed as warnings and remain unchanged. When the user clicks on the Reverse Map menu item, a dialog box will show asking for the name to be given to the reverse map. Synonym mapping is also added in this release. The term applies to mapping multiple, alternative, source element names to a single target element name. An example might be Customer_ID Account_ID => NEW_CUSTOMER_ID. Integrated Test Environment (ITE) The ITE perspective now supports the connection to any ICS started as a test server, local or remote, for unit testing of collaboration processes. The ICS itself can be hosted on a UNIX platform. This removes the restriction of installing an ICS on each developer s workstation to use the ITE. The requirement that only one client is allowed to be testing against an ICS test server at any given time, remains to ensure the integrity of the tests. Connector Configurator A short description column is added to standard properties for consistency with the configuration properties sheet. A hot button capability is provided to display extended help files. Collaboration API for failed flows A programming interface is provided to support custom administration solutions for failed flows outside of ICS. This will provide the capability to save failed events with the collaboration s subscribed event type, and to retrieve, delete, and resubmit failed events. For example, when iterating through the child business objects in a batch event, the API allows customers to save individual failed flows and manage these failed records in user collaborations. Saving failed events if they are delivered through the Server Access Interface (WebSphere Server InterChange Access) is not supported. Deployment Configuration Tool New to this release is the ability to configure the parameters of objects just prior to their deployment to an ICS, overriding values set at design time. This can speed up deployment considerably where the same objects are deployed to multiple ICS runtimes, which are particularly useful for test and deployment servers. The deployment configuration tool, selectable from the System Manager, is a visual tool that allows selection of the target ICS, viewing and selection of objects to be deployed, display of parameter names, and the setting of values. It can configure properties for connectors, collaborations, maps, relationships,

8 and most database connection properties. Properties and values can be assigned to more than one ICS and deleting a property from one server does not impact the others. The System Manager applies these runtime parameters when deploying to the target ICS. Compile/deploy progress indicator The progress of collaboration object creation and deployment activities are now cached by the ICS and displayed in a visual progress indicator from the System Manager. Collaboration deployment performance To improve performance when deploying processes, the ability to accept pre-compiled collaboration instances and maps is supported. The import/export facilities also recognize the Java class files added to the JAR file used for deployment, import, and export. Installer Collaborations The pre-built WebSphere Business Integration Collaborations previously included with ICS, but licensed separately, have been removed from the WebSphere ICS packaging in this release. The installer has been updated to reflect this. Collaborations are now available packaged as collaboration groups and are made available via electronic download only. The Collaboration Foundation templates remain packaged with WebSphere Business Integration Toolset for educational and development purposes only. A separate authorization is required to deploy custom collaborations based on the Collaboration Foundation. XML Parser replacement The XML parsing functionality for internal use by the tools has previously been provided by the libraries developed under the Apache Software Foundation s Xerces Project. These libraries have been replaced in this release with IBM s own library implementation for XML parsing, namely XML4J and XML4C. Education support For information about WebSphere Business Integration education, visit websphere/education/ IBM Global Services, IT Education Services, provides education to support many IBM offerings. Descriptions of courses for IT professionals and managers are on the IBM IT Education Services Web site Refer to the IBM IT Education Services Web site for information on course locations and availability dates. Call IBM IT Education Services at 800-IBM-TEACH ( ) for catalogs, schedules, and enrollments. Offering information Product information is available via the Offering Information Web site Also, visit the Passport Advantage Web site Publications No unique publications are shipped with WebSphere Business Integration Server. Publications are provided with each component of WebSphere Business Integration Server. Links to these documentation sets can also be accessed from integration/wbiserver/library Note: The publications for WebSphere ICS, WebSphere Business Integration Toolset, and WebSphere Business Integration Adapter products are provided as Eclipse document plug-ins (to be viewed with the WebSphere Help System) and PDF documents (to be viewed with Adobe Acrobat V4.05 or later). The WebSphere Help System requires the following software: One of these operating systems: Microsoft Windows 2000 Microsoft Windows XP Linux for Intel -based platforms One of these browsers: Microsoft Internet Explorer 5.5 or later (Windows platforms) Mozilla-based browser 1.1 or later (Windows and Linux platforms) Technical information Specified operating environment Hardware requirements: Recommendations for hardware requirements are supplied for guidance only. Specific hardware configuration will be dependent on the exact WebSphere Business Integration Server configuration implemented and production loadings. The following minimum system requirements are recommended for server components: Windows environment Processor: An IBM eserver xseries and Intel-based system, or equivalent, with a minimum processor speed of 1 GHz RAM: 512 MB Disk space: 40 GB AIX environment Processor: An IBM eserver pseries or RS/6000 system with either a uniprocessor or symmetric multiprocessor (SMP) and a minimum processor speed of 375 MHz RAM: 512 MB Disk space: 40 GB

9 Solaris environment Processor: A Sun Microsystems UltraSPARC processor system with a minimum processor speed of 450 MHz RAM: 512 MB Disk space: 40 GB HP-UX environment Processor: A Hewlett-Packard HP-9000 PA-RISC processor system with a minimum processor speed of 440 MHz RAM: 512 MB Disk space: 40 GB Linux environment Processor: An xseries and Intel-based system (or equivalent) with a minimum processor speed of 1 GHz RAM: 512 MB Disk space: 40 GB The following minimum system requirements are recommended for buildtime components: Windows environment Processor: An IBM xseries and Intel-based system, or equivalent, with a minimum processor speed of 1 GHz RAM: 512 MB Disk space: 10 GB Software requirements: The software requirements for WebSphere Business Integration Server depend on which of the elements of the product components are being used and whether singly or in combination on a particular server. The general specification of software requirements for use in combination on a single server are: Operating systems supported in a combined environment: AIX 5.2 or AIX 5.1 Windows 2003 or Windows 2000 Windows XP (Tooling only) Solaris 9 (2.9) or 8 (2.8) HP-UX 11i (11.11) Combined administrative, configuration, and operational data: DB2 Universal Database 8.1 WebSphere MQ and DB2 Universal Database Enterprise Server Edition 8.1 for Windows, AIX, Solaris, HP-UX, and Linux platforms are provided with this offering. Each of the products may, however, be run on its own server. A summary of the software requirements follows for each component. WebSphere ICS V4.3 For more details, refer to the System Installation Guide for Windows and the System Installation Guide for UNIX. Note: The WebSphere Business Integration Collaborations announced in December 2003, support WebSphere ICS V4.3. For more information, refer to Software Announcement , dated December 9, 2003 (WebSphere Business Integration Collaborations Restructuring). Note: Scripts that assist with configuring WebSphere ICS in High Availability (HA) environments are available as unsupported Category 2 SupportPacs at support/supportpacs/category.html General software requirements for HA environments are also documented in the SupportPacs. Windows environment Windows 2003 Standard Edition or Enterprise Edition Windows 2000 (Professional, Server, or Advanced Server) with Service Pack 4 Windows XP Professional with Service Pack 1A (not recommended for production use) DB2 Universal Database Enterprise Server Edition 8.1 with Fix Pack 5; a DB2 -supported C or C++ compiler is also required to compile DB2 stored procedures for relationships Oracle RDBMS or (9i) Microsoft SQL Server 2000 with Service Pack 3A Communication: WebSphere MQ Client and Server with CSD 7 WebSphere MQ Internet pass-thru (optional for Remote Agent; requires Windows 2000) an SMTP mail protocol system (for example, Microsoft Outlook, Microsoft Exchange, or Eudora) Java compiler (IBM 32-bit SDK for Windows 1.4.2) required for compiling customer-generated maps and collaborations (included with this product) A Web application server to support the Web-based System Monitor and the Failed Event Manager components (one of the following): WebSphere Application Server 5.1 or with Fix Pack 4 Tomcat V or V (not supported in double-byte character set (DBCS) language environments) Browser to support the Web-based System Monitor and the Failed Event Manager components (one of the following): Microsoft Internet Explorer 6.0 with Service Pack 1 Microsoft Internet Explorer 5.5 with Service Pack 2 Netscape Navigator 4.7x Adobe SVG Viewer 3.0 browser plug-in (to support the Web-based System Monitor) An LDAP V3 compliant directory service (optional for external authentication of user access) Any WebSphere Application Server that supports Enterprise JavaBeans 1.1 (to support WebSphere ICS Access for Enterprise JavaBeans only)

10 Any WebSphere Application Server that supports J2EE Java Connector Architecture 1.0 (to support WebSphere ICS Access for J2EE Connector Architecture only) WebSphere Business Integration Adapter Framework 2.6 (to support adapter connectivity) AIX environment AIX 5.2 Maintenance Level 2 AIX 5.1 Maintenance Level 5 DB2 Universal Database Enterprise Server Edition 8.1 with Fix Pack 5; a DB2-supported C or C++ compiler is also required to compile DB2 stored procedures for relationships Oracle RDBMS or (9i) Communication: WebSphere MQ Client and Server with CSD 7 WebSphere MQ Internet pass-thru (optional for Remote Agent; requires AIX 5.1) An SMTP mail protocol system Java compiler (IBM 32-bit SDK for AIX 1.4.2) required for compiling customer-generated maps and collaborations (included with this product) A Web application server to support the Web-based System Monitor and the Failed Event Manager components (one of the following): WebSphere Application Server 5.1 or with Fix Pack 4 Tomcat or (not supported in DBCS language environments) Netscape Navigator 4.7x (to support the Web-based System Monitor and the Failed Event Manager components) Adobe SVG Viewer 3.0 browser plug-in (to support the Web-based System Monitor) An LDAP V3 compliant directory service (optional for external authentication of user access) Any WebSphere Application Server that supports Enterprise JavaBeans 1.1 (to support WebSphere ICS Access for Enterprise JavaBeans only) Any WebSphere Application Server that supports J2EE Java Connector Architecture 1.0 (to support WebSphere ICS Access for J2EE Connector Architecture only) WebSphere Business Integration Adapter Framework 2.6 (to support adapter connectivity) Solaris environment Solaris 9 (2.9) with latest Solaris 9 Patch Cluster and J2SE Solaris 9 Patch Cluster Solaris 8 (2.8) with latest Solaris 8 Patch Cluster and J2SE Solaris 8 Patch Cluster DB2 Universal Database Enterprise Server Edition 8.1 with Fix Pack 5; a DB2-supported C or C++ compiler is also required to compile DB2 stored procedures for relationships Oracle RDBMS or (9i) Communication: WebSphere MQ Client and Server with CSD 7 WebSphere MQ Internet pass-thru (optional for Remote Agent; requires Solaris 2.8) an SMTP mail protocol system Java compiler (IBM 32-bit SDK for Solaris ) required for compiling customer-generated maps and collaborations (included with this product) A Web application server to support the Web-based System Monitor and the Failed Event Manager components (one of the following): WebSphere Application Server 5.1 or with Fix Pack 4 Tomcat or (not supported in DBCS language environments) Netscape Navigator 4.7x (to support the Web-based System Monitor and the Failed Event Manager components) Adobe SVG Viewer 3.0 browser plug-in (to support the Web-based System Monitor) An LDAP V3 compliant directory service (optional for external authentication of user access) Any WebSphere Application Server that supports Enterprise JavaBeans 1.1 (to support WebSphere ICS Access for Enterprise JavaBeans only) Any WebSphere Application Server that supports J2EE Java Connector Architecture 1.0 (to support WebSphere ICS Access for J2EE Connector Architecture only) WebSphere Business Integration Adapter Framework 2.6 (to support adapter connectivity) HP-UX environment Operating system: HP-UX (11i) with June 2003, BUNDLE11i (B ), December 2003, Quality Pack GOLDQPK11i (B ), and patch PHCO_29960 DB2 Universal Database Enterprise Server Edition 8.1 with Fix Pack 5; a DB2-supported C or C++ compiler is also required to compile DB2 stored procedures for relationships Oracle RDBMS or (9i) Communication: WebSphere MQ Client and Server with CSD 7 WebSphere MQ Internet pass-thru (optional for Remote Agent) An SMTP mail protocol system Java compiler (HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, V ) required for compiling customer-generated maps and collaborations (included with this product)

11 A Web application server to support the Web-based System Monitor and the Failed Event Manager components (one of the following): WebSphere Application Server 5.1 or with Fix Pack 4 Tomcat or (not supported in DBCS language environments) Netscape Navigator 4.7x (to support the Web-based System Monitor and the Failed Event Manager components) Adobe SVG Viewer 3.0 browser plug-in (to support the Web-based System Monitor) An LDAP V3 compliant directory service (optional for external authentication of user access) Any WebSphere Application Server that supports Enterprise JavaBeans 1.1 (to support WebSphere ICS Access for Enterprise JavaBeans only) Any WebSphere Application Server that supports J2EE Java Connector Architecture 1.0 (to support WebSphere ICS Access for J2EE Connector Architecture only) WebSphere Business Integration Adapter Framework 2.6 (to support adapter connectivity) Linux environment Red Hat Enterprise Linux AS 3.0 with Update 1 Red Hat Enterprise Linux ES 3.0 with Update 1 Red Hat Enterprise Linux WS 3.0 with Update 1 SUSE LINUX Enterprise Server x with SP3 SUSE LINUX Standard Server x with SP3 Database: DB2 Universal Database Enterprise Server Edition 8.1 with Fix Pack 5; a DB2-supported C or C++ compiler is also required to compile DB2 stored procedures for relationships Communication: WebSphere MQ Client and Server with CSD 6 + ifix for RHEL 3.0 (for supported Red Hat Linux distributions) or CSD 6 (for supported SUSE LINUX distributions) An SMTP mail protocol system Java compiler (IBM 32-bit SDK for Linux 1.4.2) required for compiling customer-generated maps and collaborations (included with this product) A Web application server to support the Web-based System Monitor and the Failed Event Manager components (one of the following): WebSphere Application Server 5.1 Tomcat or (not supported in DBCS language environments) Netscape Navigator 4.7x (to support the Web-based System Monitor and the Failed Event Manager components) Adobe SVG Viewer 3.0 browser plug-in (to support the Web-based System Monitor) An LDAP V3 compliant directory service (optional for external authentication of user access) Any WebSphere Application Server that supports Enterprise JavaBeans 1.1 (to support WebSphere ICS Access for Enterprise JavaBeans only) Any WebSphere Application Server that supports J2EE Java Connector Architecture 1.0 (to support WebSphere ICS Access for J2EE Connector Architecture only) WebSphere Business Integration Adapter Framework 2.6 (to support adapter connectivity) WebSphere Business Integration Toolset V4.3 Windows environment Windows 2000 (Professional, Server, or Advanced Server) with Service Pack 4 Windows XP Professional with Service Pack 1A WebSphere Business Integration Adapter Framework V2.6 (required for the Integrated Test Environment, Test Connector and the Adapter Monitor) Source Code Control: One of the following is required for optional System Manager source code control only: Rational ClearCase LT 4.2 Concurrent Version System (CVS) 1.11 Integrated Test Environment: A separate installation of WebSphere ICS is required for this feature. A separate instance of the database is also required and is used as the ICS repository dedicated for testing purposes only. Note: WebSphere Business Integration Toolset may also be installed and used in a WebSphere Studio Application Developer Integration Edition 5.1 or environment. WebSphere Business Integration Adapters September 2004, release The requirements described in this section apply to all of the following WebSphere Business Integration Adapter products included with this offering (unless otherwise noted): WebSphere Business Integration Adapter Framework 2.6 WebSphere Business Integration Data Handler for XML 2.7 WebSphere Business Integration Adapter for 5.4 WebSphere Business Integration Adapter for WebSphere MQ 2.7 WebSphere Business Integration Adapter for WebSphere Business Integration Message Broker 2.7 WebSphere Business Integration Adapter for WebSphere MQ Workflow 2.7 WebSphere Business Integration Adapter for JMS 2.7 WebSphere Business Integration Adapter for Web Services 3.4 Operating system requirements Windows environment (one of the following): Windows 2003 Standard Edition or Enterprise Edition Windows 2000 (Professional, Server, or Advanced Server) with Service Pack 4 Windows XP Professional with Service Pack 1A (for WebSphere Business Integration Adapter Framework administrative tools only)

12 AIX environment (one of the following): AIX 5.2 Maintenance Level 2 AIX 5.1 Maintenance Level 5 Solaris environment (one of the following): Solaris 9 (2.9) with latest Solaris 9 Patch Cluster and J2SE Solaris 9 Patch Cluster Solaris 8 (2.8) with latest Solaris 8 Patch Cluster and J2SE Solaris 8 Patch Cluster HP-UX environment: HP-UX (11i) with June 2003 BUNDLE11i (B ), December 2003 Quality Pack GOLDQPK11i (B ) and patch PHCO_29960 Linux environment (one of the following): Red Hat Enterprise Linux AS 3.0 with Update 1 Red Hat Enterprise Linux ES 3.0 with Update 1 Red Hat Enterprise Linux WS 3.0 with Update 1 SUSE LINUX Enterprise Server x with SP3 SUSE LINUX Standard Server x with SP3 Broker requirements All of the WebSphere Business Integration Adapter components included in this offering support WebSphere ICS 4.3. In addition, the following components support WebSphere Business Integration Message Broker 5.0.1: WebSphere Business Integration Adapter Framework 2.6 WebSphere Business Integration Adapter for JMS 2.7 WebSphere Business Integration Data Handler for XML 2.7 Adapter Framework compatibility WebSphere Business Integration Adapter Framework V2.6 supports WebSphere Business Integration Adapters delivered in the September 2004, June 2004, and December 2003, releases. Enhancements to Framework V2.6 require modifications to the startup scripts for many of the adapters in the June 2004, and December 2003, releases. New startup scripts and instructions for updating your existing adapters for Framework V2.6 compatibility will be provided in a migration guide and in a WebSphere Business Integration technote within 30 days of product availability. WebSphere Business Integration Message Broker for Multiplatforms V5.0.1 Note: The latest software requirements are available at wbimessagebroker/requirements CSD03 (or later) is recommended for all components. The following requirements apply to Message Broker Servers and User Name Servers: Windows environment Windows 2003 Standard Edition or Enterprise Edition Windows 2000 (Server or Advanced Server) with Service Pack 3 DB2 Universal Database 8.1 with Fix Pack 2 DB2 Universal Database 7.2 with Fix Pack 9 (not supported on Windows 2003) Oracle RDBMS 9i Rel 2 Microsoft SQL Server 2000 with Service Pack 3 Sybase Adaptive Server Enterprise (ASE) 12.5 (not supported on Windows 2003) Communication: WebSphere MQ with CSD4 Java requirement: JRE AIX environment Operating system (one of the following); AIX 5.2 Maintenance Level 1 AIX 5.1 Maintenance Level 3 DB2 Universal Database 8.1 with Fix Pack 2 DB2 Universal Database 7.2 with Fix Pack 9 Oracle RDBMS 9i Rel 2 Sybase Adaptive Server Enterprise (ASE) 12.5 (ESD #1 required for AIX 5.2) Communication: WebSphere MQ with CSD 4 Java requirement: JRE SR3 or later Solaris environment Solaris 9 (2.9) with SunSolve recommended patch level Solaris 8 (2.8) with SunSolve recommended patch level DB2 Universal Database 8.1 with Fix Pack 2 DB2 Universal Database 7.2 with Fix Pack 9 Oracle DDBMS 9i Rel 2 Sybase Adaptive Server Enterprise (ASE) 12.5 (ESD #1 is required for Solaris 9) Communication: WebSphere MQ with CSD 4 Java requirement: JRE HP-UX environment HP-UX 11.0 with September 2002, Quality Pack HP-UX with December 2002, Quality Pack DB2 Universal Database 8.1 with Fix Pack 2 (not supported on HP-UX 11.0) DB2 Universal Database 7.2 with Fix Pack 9 Oracle RDBMS 9i Rel 2 Sybase Adaptive Server Enterprise (ASE) 12.5 (ESD #1 (EBF 10976) is required for HP-UX 11.11) Communication: WebSphere MQ with CSD4 Java requirement: JRE