BeanConnect
TM
Issue
V2.1
Product
April 2009
openSEAS
Connection of J2EE Application Servers with openUTM and CICS
Pages
5
BeanConnectTM connects applications based on J2EE application servers with applications of the TP monitor openUTM or with CICS
Transaction Server in accordance with the J2EE Connector Architecture (JCA) from SUN. New applications which are based on the
J2EE technology can thus be integrated into an existing IT environment using Java resources.
In addition, Java classes are contained for access to openUTM from any Java program.
JCA V1.5 conformable, bidirectional adapter with transaction security
The J2EE Connector Architecture (JCA) is part of the Java 2 platform, Enterprise Edition (J2EE) as well as part of the Java Platform, Enterprise
Edition 5 (Java EE 5). Based on this architecture user can write new applications using J2EE technology capabilities and can also encapsulate
existing Enterprise Information Systems (EIS) with Enterprise JavaBeans or JavaServer Page technologies.
BeanConnect implements the connection of openUTM and CICS applications as EIS systems.
BeanConnect uses the JCA V1.5, which is part of the J2EE V1.4 and Java EE 5.
BeanConnect supports a variety of communication paradigms:
It enables outbound communication, i.e. communication is initiated by the application on the application server, and inbound communication, i.e.
communication is initiated by the EIS application. The communication can be transactional or non-transactional and can be executed dialog
based as well as asynchronously.
BeanConnect
Management Console
J2EE
application
BeanConnect
UNIX systems, Linux, Windows
BS2000/OSD,
UNIX systems, Linux
Solaris, Linux, Windows
container
OSI TP
EIS
application
UPIC
J2EE application server
BeanConnect Proxy
Architecture of BeanConnect connecting an openUTM application
openUTM
Data Sheet ⏐ Issue: April 2009 ⏐ BeanConnect V2.1
Page 2 / 5
BeanConnect
Management Console
UNIX-systems, Linux, Windows
z/OS, Solaris, Windows
Data
Connection
J2EE
application
BeanConnect
Resource Adapter
SNAP-IX
Solaris
EIS
application
container
IBM
i
Communications
Server
J2EE application server
BeanConnect Proxy
CICS
Architecture of BeanConnect connecting a CICS application
Components
BeanConnect consists of the following components:
BeanConnect Resource Adapter,
BeanConnect Proxy,
BeanConnect Management Console.
The BeanConnect Resource Adapter makes the JCA interface (JCA V1.5) available to the user. It is embedded (deployed) in the J2EE
application server.
The BeanConnect Proxy represents the transactional connection between the resource adapter within the application server on the one hand
and the EIS application on the other hand.
BeanConnect Proxy includes a proxy container based on the transaction monitor openUTM. For the connection to CICS the proxy includes a
software gateway to support the protocol LU6.2. For implementation of a SNA stack Data Connections’s SNAP-IX (for Solaris) or IBM’s
Communications Server (for Windows and Linux) are needed. These two products are not part of BeanConnect and have to be ordered
separately if a connection to CICS is required.
The BeanConnect Management Console is the GUI for configuring and administering of BeanConnect.
BeanConnect doesn’t contain components which have to run on the openUTM platform itself.
The BeanConnect Tools are tools which you require in many BeanConnect applications. They include Cobol2Java, the MC-CmdHandler and
the BPEL WSDL Generator.
Java classes for access to openUTM (openUTM-JConnect)
openUTM-JConnect are Java classes for any applications written in Java for access to openUTM server applications. The previously
independent product openUTM-JConnect is also part of BeanConnect.
openUTM-JConnect supports all functions of the UPIC protocol and allows additionally the plug in of SLL security functions.
BeanConnect Interfaces and protocols
BeanConnect collaborates with the J2EE application server to provide system level mechanisms, the transactions, security and connection
pooling mechanisms. For this JCA V1.5 defines certain system contracts between application server and EIS which are implemented by
BeanConnect.
Contracts for outbound communication:
Connection Management
Transaction Management
Security Management
Contracts for inbound communication:
Transaction Inflow
Message Inflow
Contracts for the resource adapter lifecycle management and thread management:
Lifecycle Management
Work Management
Common Client Interface
The J2EE Connector Architecture defines a Common Client Interface (CCI) for EIS access. The CCI defines a standard API for application
components. BeanConnect supports the CCI and offers an additional interface which clearly decreases the programming effort.
For communication to the openUTM application the following protocols are used:
Outbound communication:
OSI TP protocol for distributed transactions
UPIC protocol (a proprietary protocol for clients of openUTM applications).
Inbound communication:
OSI TP protocol for distributed transactions
UPIC protocol
Transport protocols such as the openUTM socket protocol and the RFC1006 protocol.
For communication to the CICS application the communication protocol LU6.2 is supported.
BeanConnect supports CICS application programs which correspond to IBM’s Distributed Transaction Programming (DTP) paradigm. To
connect CICS application programs which use DPL (Distributed Program Link) a program example is offered. For detailed information on
connecting CICS applications and programming CICS programs please view the BeanConnect handbook.
License structure of the product
Processor licenses are assigned per processor core on which the J2EE application server with the BeanConnect Resource Adapter is running.
Processor licensing allows any number of users (end user, developers, testers).
If openUTM-JConnect is used, the licenses per processor core running the Java applications are assigned.
The cores of multi-core processors are counted by a factor of 0.5.
Licenses for developers and testers are assigned per user (developer or tester) for a system without processor licensing.
For openUTM and for CICS the processor licences as well as the development and test licenses have to be ordered separately.
The software and documentation are delivered on DVD.
Using BeanConnect with Oracle’s Application Servers and other J2EE application servers.
BeanConnect is only released and maintained in connection with Oracle’s Application Server. For other J2EE application servers the product
can be used as well if they are JCA V1.5 conformable. The interoperability with the requested J2EE application server can be assured with an
additional service package. The additional service package consists of two parts
BeanConnect AS Interoperability Check
BeanConnect AS Interoperability Service.
These service packages are described in separate data sheets. “BeanConnect AS Interoperability Check“ contains an initial test to secure the
interoperability between BeanConnect and the required application server and to fulfil the proprietary properties of the application server.
“BeanConnect AS Interoperability Service“ is a one-year-service-package to complement the standard service of BeanConnect for the use of
BeanConnect with the requested J2EE application server.
New features of V2.1:
Cluster support
Oracle BPEL support
Unified Proxy for openUTM and CICS
Unified Resource Adapter for openUTM and CICS
More than one Resource Adapter per Proxy possible
64 Bit Support for Solaris und Linux x86-64.
Technical Data
TECHNICAL REQUIREMENTS
HARDWARE
The hardware which is compatible to the operating system versions listed below is supported. The
BeanConnect components Resource Adapter, Proxy, Management Console and the BeanConnect
Tools may run on one system or may be distributed to more systems. The functionality of
BeanConnect remains unchanged when different operating systems or operating system versions
are coupled.
Resources required:
CPU for BeanConnect Proxy: at least 450 MHz; recommended at least 1 GHz.
Main memory demand for BeanConnect Proxy: at least 1 GB.
Hard disk:
BeanConnect Resource Adapter: Archive approx. 4 MB; extracted approx. 8 MB.
BeanConnect Proxy / Management Console:
BeanConnect System:
Solaris:
Linux:
openUTM:
openUTM-LU62:
Container:
Console:
approx. 37 MB
approx. 21 MB
Windows:
approx. 11 MB
Solaris:
approx. 630 MB
Linux:
approx. 180 MB
Windows:
approx. 54 MB
Solaris:
approx. 11 MB
Linux:
approx. 6 MB
Windows:
approx. 6 MB
Solaris:
approx. 59 MB
Linux:
approx. 59 MB
Windows:
approx. 56 MB
Solaris:
approx.
Linux:
approx.
44 KB
Windows:
approx.
400 KB
13 KB
Tools:
Cobol2Java: Archiv: approx. 7 MB; extracted approx. 10 MB.
MCCmdHandler : Archiv: approx. 3 MB; extracted approx. 3 MB.
BPEL WSDL Generator : Archiv: approx. 3 MB; extracted approx. 3 MB
JConnect : Archiv: approx. 2 MB; extracted approx. 7MB.
TECHNICAL REQUIREMENTS
SOFTWARE
The components BeanConnect Resource Adapter and BeanConnect Tools are available for the
following operating systems:
- Solaris(SPARC) V9 or higher (32 Bit and 64 Bit)
- Linux x86 and x86-64:
RedHat Enterprise Linux 4 or higher (32 Bit and 64 Bit)
SUSE LINUX Enterprise Server 9 or higher (32 Bit and 64 Bit)
- Windows Server 2003 (32 Bit and 64 Bit) / Windows XP (32 Bit and 64 Bit)
/ Windows Vista (32 Bit and 64 Bit)
- HP-UX 11i or higher (32 Bit and 64 Bit)
The components BeanConnect Proxy and BeanConnect Management Console are available for the
following operating systems:
Advice: For outbound communication with the UPIC protocol the BeanConnect Proxy and the
BeanConnect Management Console are not needed.
- Solaris(SPARC) V9 or higher (32 Bit and 64 Bit)
- Linux x86 and x86-64:
RedHat Enterprise Linux 4 (32 Bit and 64 Bit)
SUSE LINUX Enterprise Server 9 or higher (32 Bit and 64 Bit)
- Windows Server 2003 (32 Bit) / Windows XP (32 Bit)
/ Windows Vista (32 Bit)
BeanConnect V2.1 requires J2SE JDK 1.5.0_16 or higher.
BeanConnect V2.1 supports the following application servers:
- Oracle AS / OC4J 10.1.3.3 or higher:
- Oracle WebLogic Server 10g or higher: upon request
Under the prerequisite of an Interoperability Check is performed:
- IBM WebSphere AS 6.1.0.13 or higher
- RedHat JBoss 4.2.2 or higher
- SUN Glassfish V2
- Bea WebLogic V10
The BeanConnect Proxy also requires:
PCMX: The necessary PCMX versions do not require a separate license.
- Solaris : PCMX V6.0A60
- Linux : PCMX V6.0A70
- Windows : PCMX32 V5.0A30
are included on the DVD and must be installed (
Note: Under Solaris, CMX can be used as of V6.0 instead of PCMX.
openUTM:
A required openUTM version for use with BeanConnect Proxy is included on the DVD
and must be installed. It may only be used with BeanConnect and does not require a
separate license.
openUTM-LU62 Gateway:
An appropriate openUTM-LU62 version for use with BeanConnect Proxy is included on
the DVD and must be installed. It may only be used with BeanConnect and does not
require a separate license.
Enterprise Information System (EIS) openUTM:
- openUTM V5.2 or higher, on all platforms (32 and 64 Bit)
- Under BS2000/OSD, openUTM-D is required for transactional communication.
- openUTM-Client (UPIC) V5.2 or higher, on all platforms (32 and 64 Bit)
Enterprise Information System (EIS) CICS:
- CICS on z/OS: z/OS V1.4or higher; CICS V2.2 or higher;
Required connection software from other companies:
- Solaris: SNAP-IX V7.0.2.4 or higher, from Data Connection Ltd.
- Linux: IBM Communications Server for Linux, V6.2 or higher
- Windows : IBM Communications Server for Windows, V6.1.2 or higher
Note: SNAP-IX and the communications server are not part of the BeanConnect delivery.
Both the IBM Enterprise Extender and the ethernet (LLC2) are supported as connection
options.
openUTM-JConnect is available for the following operating systems:
- Solaris(SPARC) V9 or higher (32 Bit and 64 Bit)
- Linux x86 and x86-64:
RedHat Enterprise Linux 4 (32 Bit and 64 Bit)
SUSE LINUX Enterprise Server 9 or higher (32 Bit and 64 Bit)
- Windows Server 2003 (32 Bit) / Windows XP (32 Bit)
/ Windows Vista (32 Bit)
openUTM-JConnect requires J2SE JDK 1.5.0_16 or higher.
IMPLEMENTATION LANGUAGE
Java, C
USER INTERFACE
English
INSTALLATION
By the users themselves using the description in the manual
DOKUMENTATION
The documentation is available online at http://manuals.ts.fujitsu.com
USER REQUIREMENTS
Knowledge of the programming language Java and general knowledge of J2EE application server
TRAINING
Courses on the programming language Java and on J2EE application servers are recommended.
Workshops about BeanConnect are offered by Fujitsu.
CONDITIONS
This software product is supplied to the customer under the conditions for the use of software
products in return for a single payment or for regular payment.
ORDERING AND DELIVERY
This software product may be obtained from your local Fujitsu regional office.
Information about environmental care, policies, programs and our Environmental Guideline FSC 03230:
ts.fujitsu.com /aboutus
Take back and Recycling information: ts.fujitsu.com /recycling
All rights reserved, including intellectual property rights. Technical data subject to modifications and delivery subject to availability. Any
liability that the data and illustrations are complete, actual or correct is excluded. Designations may be trademarks and/or copyrights of
the respective manufacturer, the use of which by third parties for their own purposes may infringe the rights of such owner. For further
information see: ts.fujitsu.com/terms_of_use.html
Copyright © Fujitsu Technology Solutions GmbH 2012
Published by:
Fujitsu Technology Solutions GmbH
ts.fujitsu.com