Release Notice:

BeanTransactions V3.1A10
Application Server for Enterprise JavaBeans

Version date:

May 2004

1 General

The subject of this Release Notice is the application server for Enterprise JavaBeans "BeanTransactions V3.1A10".

BeanTransactions V3.1A10 is available for the following operating systems:

• Windows 2000 / Windows Server 2003 / Windows XP
• Linux as of kernel 2.4.19 (corresponds to RedHat 8.0 and SuSE 8.1)
• Solaris as of version 8.

The application server BeanTransactions is the runtime environment for the component technology Enterprise JavaBeans according to EJB Specification 2.0.
BeanTransactions is based on the transaction monitor openUTM.

You will find further information under:
http://www.ts.fujitsu.com/beantransactions

The release level is that of V3.1A10 from May 2004.

This Release Notice is supplied as a README file. Customers will receive an updated version of this file should any subsequent changes be made.

This Release Notice is also available over the Internet.
http://serviceportal.ts.fujitsu.com/extranet/partner/fsc/its/index.htm

If one or more previous versions are skipped when this product version is used, the information from the Release Notices (and README files) of the previous versions must be noted.

The use of names, trademarks, etc. in this Release Notice does not entitle readers to assume that these names/designations may be used without restriction by anyone; the names/designations are often protected by law or contract, even if this is not indicated here.

1.1 Ordering

The product is available from your local distributor or via one of our sales partners. The general terms and conditions of the software product use and service agreement apply for Fujitsu Technology Solutions.

The following belong to the product scope:

• Usage rights
• Data media with software
• Manuals

The product DataDirect SequeLink 5.4 is a component part of BeanTransactions V3.1A10.
This product is used to communicate with databases from various manufacturers.
You will find a functional description in the manual supplement file (see 1.3).

In addition to BeanTransactions V3.1A10, the MicroDoc software MPF/J must be used if container-controlled persistence for Entity Beans is to be used.
The software is supplied with BeanTransactions V3.1A10, but can only be used with an appropriate license key (see 1.1.1).

1.1.1 Usage rights

• BeanTransactions V3.1A10:
  see Data Sheet under
  http://www.ts.fujitsu.com/beantransactions

• DataDirect SequeLink 5.4:
  The usage rights are included in BeanTransactions V3.1A10

• MPF/J :
  When you order MPF/J from Fujitsu Siemens, you also receive a web address under which you are provided with a form with which you can order the license key.
  Until an official order is placed, MicroDoc Computer Systems GmbH provides you with a test license key via the following web address: http://www.microdoc.de

• CMX(LINUX):
  No license is required for usage as long as CMX is only used together with BeanTransactions V3.1A10.

1.2 Delivery

The software is supplied on CD-ROM. You also receive the following manuals on CD-ROM:

• BeanTransactions V3.1A
  (Developer Manual, Administration and Installation Manual)
• openUTM Manuals (Unix/Windows)
• openUTM WinAdmin Description

1.3 Documentation

In addition to this Release Notice, the following manuals are valid for BeanTransactions V3.1A10:

You will also find the BeanTransactions V3.1A10 manuals under

http://manuals.ts.fujitsu.com/servers/man/man_de/appi_man/beanta.htm (German)
http://manuals.ts.fujitsu.com/servers/man/man_us/appi_man/beanta.htm (English)

You can also order the manuals in printed form at extra cost under http://manuals.ts.fujitsu.com.

In addition, you will also find the following documentation in the BeanTransactions installation directory under /docs:

• man-de.pdf / man-en.pdf :
  Manual supplement file that describes changes made after the BeanTransactions V3.1A10 manuals were published.

• BeanTA_Serverproperties_de.pdf /
  BeanTA_Serverproperties_en.pdf :
  This file contains a description of the properties that the EJB server reads via the "container.properties" file when the application is started.

• CmdLineTutorial_de.pdf / CmdLineTutorial_en.pdf:
  This tutorial illustrates how an EJB can be created using the BeanTransactions command line interface.

2 Software extensions

The software extensions over the previous version BeanTransactions V3.0A00 are described in the following sections. You will find detailed information on the software extensions in the BeanTransactions V3.1A10 manuals.

• BeanTransactions V3.1A10 fully supports Enterprise JavaBeans according to the EJB2.0 specification.
  • Home methods in EntityBeans:
    EntityBeans can now also contain home methods as well as business methods.

  • Named create methods:
    create methods can contain a method name as a suffix.

  • Security identity:
    The EJB2.0 specification offers the option of forwarding the security identity in the security context of a caller (caller identity) either unchanged or linking the caller with a new security identity.

  • Method permissions:
    You can now make a method accessible for all roles, forbid access or assign the method to the role(s) that are allowed to access it.

  • MessageDrivenBeans:
    • In a MessageDrivenBean, you can define a message selector that acts as a filter for receiving messages.
    • For each MessageDrivenBean and each asynchronous OLTP MessageDrivenBean, the redelivery of a JMS message after a rollback can be selectively limited with the redelivery threshold.

  • External resources:
    javax.mail.Session,java.net.URL and net.fsc.jca.communication.EISConnectionFactory can be specified as additional standard resource types. It is also possible to define the resources of any user-defined type.

  • Accessing the methods of other EJBs:
    References to EJBs in another jar archive can be specified during the bean development.

• The BeanTransactions development tools can now also be integrated into Eclipse.

• Cobol2Java:
  Using COBOL2JAVA, simplifies integrating BS2000/OSD COBOL and BeanTransactions applications.
  COBOL2JAVA allows you to map COBOL data structures object-oriented to Java classes.

• Diagnosing wit Log4j:
  BeanTransactions V3.1A10 uses the software product Log4j for tracing. The Log4j control is integrated into the BeanTransactions management console.

• Administering remote, non-available EJB servers:
  With the MCCmdHandler tool, you can still administer an EJB server on a remote system if it has not been started.

• External JMS server:
  BeanTransactions supports using an external JMS server (e.g. WebSphereMQ from IBM).

• Cooperation between EJB server and standalone web container (Tomcat 4.1 and Tomcat 5.0):
  • You can integrate BeanTransactions into the userspecific Tomcat instance by calling 'Prepare for BeanTA Usage' from the management console.

  • With the management console, WAR archives can be installed and administered in both local and remote Tomcat web containers.

• Load balancing:
  BeanTransactions V3.1A10 offers a mechanism with which you can implement load balancing over several identical EJB servers.
  The load balancer distributes the client queries over the EJB servers grouped into a cluster.
  You can configure and administer the cluster servers and the load balancer together via the management console.

• Configuring partner applications:
  • Administering remote services (LTACs) via the management console.

  • You can now generate connections between an EJB server and an OLTP application such that the communication can be used for OLTP destinations and for OLTP data sources.

  • KDCDEF input for UTM-D connections: Connections between two EJB servers are now supported as well as connections between an EJB server and an OLTP data source.

• EAR archives:
  EAR archives can be administered via the management console, i.e. new archives can be created or existing ones added to the EJB server, and their modules (EJB jar archives, resource adapters, WAR archives, files) can also be processed.

• Web services:
  Wsdlgen is now also available in the management console as a Wizard with a graphical user interface. In addition, Axis, the Soap engine of the Apache Group, is supported now as the follow-up product to Apache SOAP V2.3.

• External processes:
  You can now use the management console to administer external processes that are started automatically when the EJB server is started and stopped automatically when the EJB server is shut down.

• JDBC databases:
  JDBC databases with and without XA capability are now handled identically in the management console.

• Managing the EJB server settings:
  All parameter settings in the container.properties file are made via the management console.

• Save, reload and reset of a single EJB server:
  Via the context menu of each separate EJB server, you can save the configuration data, reload the server or reset the configuration to the last saved state.

• Extended display properties:
  Via the "Management Console Settings" dialog field, you can set various new display properties such as, e.g. the look and feel of the user interface. In addition, you can set a connection timeout for the administration connections to the servers.

• Replacement for the MCF files:
  All management console administration data is now stored in the "console.properties.xml" file.

• Updating:
  As of BeanTransactions V3.1A10, an update installation is available. It is used to install a new version of BeanTransactions, whereby the configuration data is taken over from an installed BeanTransactions container.

3 Technical information

3.1 Resource requirements

Disk storage space required for server and the openUTM, PCMX development tool:

Windows	: approx. 200 MB
Solaris	: approx. 300 MB
Linux	: approx. 200 MB

Recommended main memory: 512 MB

3.2 Software configuration

Windows 2000 / Windows Server 2003 / Windows XP
   or
Linux as of kernel 2.4.19
   or
Solaris as of version 8.

openUTM version:
An appropriate openUTM version for use by BeanTransactions is included on the CD.

PCMX/CMX versions:

The valid PCMX/CMX versions

• Linux: CMX V6.0
• Solaris: PCMX V6.0
• Windows: PCMX32 V4.2B20

are on the CD and must be installed.
If PMX is used, local port 102 should not be used.

Note: With Solaris, CMX as of V6.0 can be used in place of PCMX.

JDK version as of 1.3.1_08

Persistency Framework MPF/J as of version 4.1 from MicroDoc, can be ordered from Fujitsu Technology Solutions.

The following products are also supplied free of charge other manufacturers:

Database HSQLDB V1.7.1
Xerces (Apache XML Parser) V1.4.4

Sun-Basiskomponenten:

EJB V2.0
JDBC V2.0 Optional Package
JTA V1.0.1A
JCA V1.0
JMS V1.0.2b
JavaMail V1.2
JavaHelp V1.1.2_01
JAAS V1.0
JAF V1.0.1
JRE V1.3.1

Apache Group Software:

Log4J 1.2.8
AXIS 1.1
Xerces 1.4.4
Xerces 2.6.2
Xalan 2.6.0
Ant 1.6.1
Tomcat 4.1.30

GNU Software:

gzip 1.24
tar 1.13

Please read the copyright notes under the respective URLs. You will find them in the file "Copyright.htm" in the installation directories of BeanTransactions.

Note:

• AXIS V1.1 and Tomcat V4.1.30
  There is no guarantee included with the supplied products and no services are offered.
  If you require services, the software must be ordered with "openInternetServices" (available for Solaris and Linux).

Optional (not part of the software delivery):

Development environment JBuilder as of version 8
   or
TogetherControlCenter as of version 5.5
   or
Eclipse version 2.1

Database connection via JDBC:

JDBC compatibility has been checked with the following database systems (JDBC driver):

Oracle 9i (9.2) with Oracle JDBC 9.2.0.3
The following patches should be installed (available via Oracle MetaLink) :
   2632715
   ORACLEDATASOURCE IMPL DOES NOT ADHERE TO DATASOURCE
   INTERFACE CONTRACT
   2717235
   XA APPLICATION GETS XAER_PROTO WITH 9.2.0.1 JDBC THIN
   2881276
   JDBC XARECOVERY FAILS BECAUSE OF WRONG EXCEPTION WHEN
   SERVER CRASHES

Microsoft SQL Server 2000 Driver for JDBC Service Pack 2
   SESAM-SQL V3.1A:
   You will find information on the required software configuration, installation instructions and first-time operation under:
   http://www.ts.fujitsu.com/rl/products/software/sesamjdbc31.html

External JMS server

Correct functioning has been checked on:
Windows with WebSphereMQ V5.3, CSD01
Solaris with WebSphereMQ V5.3, CSD05
Linux with WebSphereMQ V5.3, CSD05

3.3 Product installation

Information on installation can be found in the Administration and Installation Manual.

Solaris/Linux:
You will find additional installation information and instructions for changing kernel parameters in the document "How2Install" on the BeanTransactions CD.

The information in the delivery cover letter must also be noted

3.4 Product use

• BeanTransactions uses the product MPF/J from MicroDoc for the container-controlled persistence (see 1.1 Ordering).
• The K shell is required for Solaris / Linux

3.5 Obsolete functions (and those to be discontinued)

In the
   de.siemens.utmejb.utm.legacy.OpenUTMConnectivity
   de.siemens.utmejb.utm.jupic.JUpicConnection
   de.siemens.utmejb.oltpmdb.OltpMessageDrivenContext
some method calls have been set to deprecated.

3.6 Incompatibilities

• The class path of EJB clients must contain BeanTAJ2EE.jar.

• In the environment de.siemens.utmejb.comm.CommEnvironment, the method "setDebugInformation()" is omitted.
  The functionality is now provided by the "log4j" logging component.

• All interface functions that use the JUpic restart feature have been deleted from the interface de.siemens.utmejb.utm.jupic.JUpicConnection, that is implemented by JUPICConnectionImpl in the same package.

• The new openUTM transaction concept causes incompatibilities that are relevant for BeanTransactions V3.1A10 in the following cases:
  • if an EJB is called via OSI TP or LU6.1
  • if an EJB uses a legacy communication
  • if an EJB calls an EJB in a remote container with "container managed transaction demarcation" in a transaction..

  You will find information on this in the appendix of the developer manual

• Pre-defined EJB role "all" is discontinued:
  To permit unlimited access to the methods of an EJB, BeanTransactions V3.0A contained the pre-defined EJB role called "all" that was automatically mapped to the BeanTransactions "ALL" role with all access rights during deployment. In BeanTransactions V3.1A10, these two roles are replaced with the "unchecked" attribute of the deployment descriptor method permissions that is displayed on the graphical user interface of the tool with <All Users>.
  When you do a BeanTransactions V3.1A10 update installation, the two roles "all" and "ALL" in EJB jars from BeanTransactions V3.0A that are already deployed are automatically replaced with the "unchecked" attribute.
  jml files from BeanTransactions V3.0A still contain the EJB "all" role. This EJB role must be deleted before such files are used for creating new EJB jars that are to be used under BeanTransactions V3.A10.
  You can do this with the assembly descriptor editor.
  Undeployed EJB jars created with BeanTransactions V3.0A also contain the EJB "all" role.
  If such EJB jars are to be installed in a BeanTransactions V3.1A10 container, this EJB role must be deleted with the deployment descriptor editor.

• The LTAC statement for kdcdef input in the EJB container is no longer created by the management console when the OLTP data source is created. The LTAC must instead be explicitly created with the new "Remote Service" function.

3.7 Restrictions / Notes

3.7.1 Restrictions

- / -

3.7.2 Notes

• In BeanTransactions V3.1A10, "HSQLDB" is supplied in place of "HypersonicSQL". If you make an update installation from BeanTransactions V3.0A to BeanTransactions V3.1A10, HypersonicSQL data files are taken over.

• Uniform masks for JDBC drivers and XADataSources in the management console:
  When you create a new JDBC data source, there is no longer any discrimination between JDBC drivers and XADataSources as there was with BeanTransactions V3.0A. The required JAR files are selected during creation. The management console automatically recognizes all JDBC drivers and XADataSources that the selected JAR files contain. You can then choose the desired implementation.

• Support for JDBC driver properties: A connection to a database system can be set up in two ways using a JDBC driver:
  1. by specifying the JDBC URL.username and password
  2. by specifying the JDBC URL and driver properties

  BeanTransactions V3.0A only supported the first form.
  You can still specify the JDBC URL.username and password under "System Properties" as previously. You can alternatively specify the JDBC driver properties under "Driver Properties".

• More parallel transactions (= using "Requires New") is possible with XADataSources, not with JDBC drivers.

3.8 Procedure in the event of errors

The following error documentation will be required for diagnostic purposes:

• a detailed description of the error condition

• a detailed description of the software configuration with version numbers of the software involved

• if still available, KDCDEF generations, i.e. the file def.out in the container home directory

• container log files : "logging.*"
  you will find these in the logs directory

• core files / UTM dumps

• openUTM system log files from the SYSLOG directory

• utmp.err file

• utmp.out file (Solaris/Linux platforms)

• Trace files, if available

• the file JVM_Info.txt, that logs the properties of the JVM (Java virtual Machine) used:

  You can create the file with "jvminfo":

  • To do this, start an input prompt or shell and change into the container home directory
  • call "jvminfo" as follows:
    under Windows shsc\jvminfo
    under Solaris/Linux shsc/jvminfo

  You will then find the file JVM_Info.txt in the container home directory

You will find more detailed information in the Administration and Installation Manual (chapter 13 Diagnostic information).

4 Hardware support

All systems based on Intel technology e.g. laptops, PCs, PRIMERGY systems, and SPARC systems, e.g. PRIMEPOWER systems

CPU at least 450 MHz, main memory at least 512 MB.

© 2004 Siemens Business Services GmbH & Co OHG

Last change: 2004-06-17