Search results

IBM® WebSphere® ILOG Rules for COBOL generates a COBOL sub-program from the rules that have been externalized and managed in the ILOG Rules Repository. The externalization of business rules provides benefit to your business, as well as improves the efficiency of maintaining your COBOL applications. Corporations today continue to see value in running their core business applications on large-capacity mainframes. An organization's success depends largely upon its ability to respond quickly to today's complex, ever changing markets and regulatory climate. Businesses today need a Business Rule Management Systems (BRMS) solution that supports business changes and cycles far more effectively than traditional methods and takes direct advantage of business expertise. This IBM Redpaper™ publication is intended for anyone who is interested in learning more about IBM WebSphere ILOG Rules for COBOL.

This IBM® Redpaper publication describes the steps involved in the installation, configuration and implementation of the new Optimized Local Adapters (OLA) support available with WebSphere® Application Server. A step-by-step approach is used to guide you through the OLA installation and configuration process. The OLA bi-directional communications functions are presented in detail through the development, deployment and execution phases using three sample application scenarios: - Modify the existing IBM benchmark application Trade6 to enable it to receive OLA inbound calls from an external application written in C. - A CICS® Cobol program modified to invoke an EJB™ within the WebSphere Application Server on z/OS® . - An EJB in the WebSphere Application Server on z/OS invoking a Cobol program in CICS.

Turn insight into action by engineering IBM System z business applications for compliance. React swiftly and effectively to patterns of events to mitigate risk and respond to opportunities with WebSphere Business Events and CICS Transaction Server.

This IBM Whitepaper is aimed at information technology (IT) architects, project managers, and other decision makers who are considering their options for new IT projects. It focuses on the merits of deploying new applications to the System z platform, and in particular, to an environment managed by CICS Transaction Server (CICS TS).

This document is aimed at CICS® application programmers who need to use COMMAREAs larger than the maximum 32k size supported by CICS Transaction Server for z/OS® (CICS TS) V2. It describes a programming technique using CICS’ Business Transaction Services’ Containers to manipulate and handle data larger than 32k bytes. This technique is referred to as BigCommarea processing.

This white paper focuses on the business challenges faced by the IT development and management teams that are responsible for creating the new applications demanded by their business users. This paper then shows how a formal process combined with some of the System z™ products can help to address these business challenges. A development life cycle is then played out using the IBM Rational® Unified Process, showing the value provided by the products used to develop and test a new application.

This white paper discusses how you can take advantage of the power of WebSphere® Process Server with CICS® Transaction Server to build new processes, take advantage of new channels and drive new business. IBM WebSphere® Process Server is designed to enable you to transform your business processes based on an SOA approach. This solution enables you to enhance business flexibility and IT responsiveness by directly integrating existing business transactions with new business processes.

This IBM Redpaper publication examines performance when using different SOAP message sizes in CICS Web Services. We used a preexisting basic Web Services environment with no message handlers or header handlers. Using WebSphere Studio Workload Simulator (WSWS), we ran a number of simulations using predefined scripts. For more information about WSWS, refer to WebSphere Studio Workload Simulator User's Guide, SC31-6307. We then processed the CICS SMF data using CICS Performance Analyzer (CICS PA) and collated the statistics. For more information about CICSPA, see CICS Performance Analyzer User's Guide, SC34-6307. This paper also reviews a customer scenario, DanskeBank. We provide an overview of the bank's ATM system, and briefly discuss the IFX framework. We detail our use of WebSphere Developer for zSeries (WD/z) to simulate request messages from an ATM, present a performance comparison between optimized and non-optimized schema versions, and cover schema versus container definitions, large fields, and schema complexity. Finally, we provide an example of the impact of mapping levels.

This IBM Redpaper discusses concepts and tasks that must be understood and applied when migrating from an existing session management product to IBM Session Manager. IBM Session Manager for z/OS is a VTAM or TCP/IP session manager that offers secure and user-friendly access to multiple z/OS systems from a single 3270 terminal or equivalent. It gives users a single secure sign-on and allows controlled access to all of their applications from multiple concurrent virtual sessions using a wide range of tools and facilities. This Redpaper: - Describes major activities that take place during migration to IBM Session Manager - Provides a checklist for use when creating and executing a successful migration plan - Offers specific aspects of the migration activities in detail This paper is intended for architects, systems programmers, analysts, and programmers wanting to understand the performance characteristics of IBM Session Manager. Readers should be familiar with the concepts and operation of IBM Session Manager.

This IBM Redpaper provides a high-level introduction to TXSeries® for Multiplatforms V6. In this Redpaper we describe the value proposition of this product and how you can use it to build robust enterprise middleware solutions. We cover the following topics: What is new in Version 6? Common deployment scenarios. Deployment, development, and administration choices. Comparing Mainframe Transaction Processing Monitors with Distributed Transaction Processing Monitors.