Changes compared to the predecessor version

The most important changes in BeanConnect $(versionVDotA) compared to BeanConnect V6.5A are listed below. For a description concerning the software configuration please refer to the Release Notice:

New functions in V7.0A00

• As on Windows systems, a service for starting a BeanConnect proxy container can now also be set up on Linux systems
• On Linux systems the services are using the systemd technology.
• The BeanConnect proxy container V7.0A00 is based on openUTM V7.0A00.
• KornShell is no longer required for the master installation on Linux systems.
• A C compiler is no longer required for the installation of the BeanConnect proxy container on Linux systems.
• On Windows systems administration rights are only required during installation of the BeanConnect proxy container.

Feature enhancements in the Management Console

• UTM-BCAM Trace
  The length of the UTM-BCAM Trace may be controlled via the Management Console.

Feature enhancements in JConnect

• Encryption
  Modernization of the encryption functionality analogous to openUTM-Client V7.0. 
  Support of the ENCRYPTION-LEVEL=5 functionality of openUTM.

Other changes

• The names of the xml files needed for the automatic installation have changed. The names of the files will contain the prefix BC$(versionL)_ .
• BeanConnect $(versionVDot) is supported by default on Linux and Windows systems.
• As of BeanConnect $(versionVDot) the proxy container runs only in a 64-bit environment.
• As of BeanConnect $(versionVDot) only a JCA 1.6 compatible resource adapter will be delivered.
• In addition to Oracle Java 8 also OpenJDK 8 may be used for running BeanConnect components.
• Update of the OpenSource components in BeanConnect.

New functions in V7.0A23

• Log4J2 V2.17 is used for logging.

Feature enhancements in the BeanConnect proxy container

• The BeanConnect proxy container V7.0A23 is based on openUTM V7.0A23.

• The product PCMX is no longer required for running the BeanConnect proxy container.

New functions in V7.0A31

• As of BeanConnect V7.0A31 the Java versions 11, 17 and 21 are supported.
  

Feature enhancements in the BeanConnect proxy container

• The BeanConnect proxy container V7.0A31 is based on openUTM V7.0A31.

Actions when upgrading from BeanConnect V7.0A00 to a correction release of BeanConnect V7.0

For upgrading from BeanConnect V7.0A00 to a currection release of BeanConnect V7.0, you must reinstall BeanConnect and all BeanConnect components or perform an update installation and redeploy the BeanConnect resource adapter.