Databridge 7.0 Release Notes
Last Updated: September 2021
The following outlines new features and functions provided by this version.
Introducing a new browser-based Administrative Console providing a modern interface to monitor, configure and execute commands in conjunction with Client Manager. For more information on the Administrative Console see the Databridge Administrative Console Help.
Added support for DMSII SSR 62.0
Communication between the Databridge Client and the Databridge Server on the MCP can now be encrypted using TLS (Transport Layer Security). For more information on setting up encryption, see the Using TLS With Databridge section below.
Implemented a second set of commit parameters in the client and a new configuration file parameter named
batch_job_periodparameter defines the time slot during which batch jobs typically run. This allows the client to automatically switch between the two sets of commit parameters based on the value of the audit timestamp. This enhancement will improve performance during batch periods, and particularly when using low values for the commit parameters during daytime hours.
Added the ability for the client to override the parameter
COMMIT DURING IDLE DATABASEin the Engine control file by using the
commit_idle_databaseparameter, which has been added to the client configuration file.
Added a control table named
AF_STATS. This was added to optionally store the audit file statistics for the last 9999 audit files.
Added the column
dflt_optionsto the DATASETS, DMS_ITEMS, DATATABLES and DATAITEMS Client control tables. For more information about
dflt_optionssee the Databridge Client Administrator's Guide.
- Starting with SQL Server 2016, enhanced security no longer allows you to add "NT AUTHORITY\SYSTEM" to the sysadmin role. We suggest one of the following options to mitigate this problem:
- Run the service under the user account that is setup to run the command-line client (dbutility) and use Integrated Windows authentication.
- Setup the client to use SQL Server authentication to connect to the database, and continue to run the service under the SYSTEM account.
Using TLS With Databridge
There are several steps to configure data encryption for use with Databridge Clients, which are outlined below. A Databridge Server can support only one type of connection. When configured to use TLS, then only TLS connections are supported.
Using the MCP Cryptographic Services Manager, create a new key in Trusted Keys > Other Keys. Complete the form and create a certificate request to submit to a certificate authority. When the certificate has been obtained, install it into the newly created key.
The Application and Service entries are concatenated to form a key container id. If the application is
DATABRIDGE and the service is
SSLKEY, then the key container will be
DATABRIDGE_SSLKEY. Note that the trusted key usercode must be that of the Databridge install.
Edit the DATA/SERVER/CONTROL file located in the Databridge usercode and uncomment the KeyContainer parameter and set it equal to the key container created above. Using the example key container from above, the parameter in DATA/SERVER/CONTROL should be:
KEYCONTAINER = “DATABRIDGE_SSLKEY”
Restart Databridge Server to use the new KeyContainer.
To configure a Client to use TLS, the enable encryption parameter must be set to True. The server certificate requires either the CAFile or CAPath parameters to be verified. The CAFile is the full path to a file that can be used to verify the server certificate, and the CAPath references a directory where the server certificate can be verified. See the Databridge Administrative Console Help for more information on setting up Encryption for the Administrative Console.
License Key Update
For Databridge 6.5 and subsequent releases, a new license key algorithm is required to run Databridge. This new key is based on the components you currently have licensed. When upgrading from a release prior to Databridge 6.5, a new license key will be required.
For more information on license keys, contact Micro Focus Customer Support before installing this upgrade.
Before installing CSS 3.0 on a ClearPath Software Series machine please contact Micro Focus Customer Care for assistance. A CSS 3.0 migration changes the system type name which invalidates the license key required to use Databridge.
Databridge 7.0 includes the following security guidelines:
|For||To decrease security risk|
|Databridge Host||Install Databridge Host to the Unisys mainframe under its own privileged usercode. This is preferable to installing under the usercode of the DMSII database. If you install and run Databridge under multiple usercodes, you must install a copy of DBEngine under each of those usercodes.Alternatively, you can establish DBEngine as a system library (SL).|
|Databridge Enterprise Server||File security is automatically enabled when you install Databridge Enterprise. File security protects the configuration and log files by restricting privileges on the PC to users who need to modify the configuration.By default, any user in the Administrators group can modify the configuration files and delete the read-only log files. If you create a user group in Windows called DBEAdmins, only the users in that group will be able to alter the configuration files and delete log files. Likewise, if you create a group called DBEUsers, only the users in that group will be able to view the configuration. For more information, see Implementing File Security in the Databridge Enterprise Server Help.|
The Databridge components and utilities are listed below with their corresponding version number for the 7.0 release. All host programs have been compiled with MCP Level 57.1 software.
|Databridge Host||Base Release|
|Databridge FileXtract||Base Release|
|Enterprise Server||Base Release|
The directory structure has slightly changed in this release as the console is now a separate install that is located in the Console\Windows directory on the release DVD image. The console install includes a private JRE.
Subsequent Hot Fixes, Updates and Service Packs will use the same directory structure as the release DVD.
Hot Fixes, Updates and Service Packs still contain a patch in the Windows directory, which updates the Client and Enterprise Server. The console is patched by running the
setup.exe from from the Console\Windows directory, which reinstalls the console software (including the private JRE).
Databridge 7.0 includes support for the following hardware and software requirements:
System Support Updates
- Databridge will remove support for operating systems and target databases when their respective software company ends mainstream and extended support.
|Databridge Host||Unisys mainframe system with an MCP level SSR 59.1 through 62.0
DMSII or DMSII XL software (including the DMALGOL compiler)
DMSII database DESCRIPTION, CONTROL, DMSUPPORT library, and audit files
|Databridge Enterprise Server||ClearPath PC with Logical disks or MCP disks (VSS disks in MCP format)
Windows PC that meets the minimum requirements of its operating system, which is one of the following:
|Databridge Administrative Console||It is recommended that you install the Administrative Console to a different machine than the Client. Installing the Administrative Console on the same machine as the client can lead to performance issues as well as monitoring failures as connection issues on the Client machine will also affect the Administrative Console's ability to monitor activity.
The Administrative Console install includes a private JRE that is used to run the Administrative Console server.
|Databridge Client||NOTE: Disk space requirements for replicated DMSII data are not included here. For best results, use a RAID disk array and store the client files on a separate disk from the database storage.
NOTE: Memory requirements do not include the database requirements when running the Client in the server that houses the relational database (consult your database documentation for these). The numbers are for a stand-alone client machine that connects to a remote database server.
If you run the Administrative Console on the same machine as the Client, it will need an additional 1-2 GB of memory depending on how many data sources you have and how long you let it run. All log information is saved in memory.
|Client - Windows||Unisys ES7000
Pentium PC processor 3 GHz or higher (multiple CPU configuration recommended)
2 GB of RAM (4 GB recommended)
100 GB of disk space in addition to disk space for the relational database built from DMSII data)
One of the following operating systems:
+ For Windows systems only
++ Oracle 18c requires Solaris 11.4 or newer.
|Client - UNIX and Linux||One of the following systems:
100 GB of free disk space for installation (in addition to disk space for the relational database built from DMSII data)
One of the following databases:
Read the Installation Guide for information on system and installation requirements, upgrade instructions, and other helpful tips.
The new Administrative Console must be installed following the installation of the Databridge software. See the Databridge Installation Guide section on Installing the Databridge Administrative Console for instructions on installing the Administrative Console on Windows and UNIX machines.
We recommend that you install the Administrative Console in a separate server from the client machine(s) for the following two reasons.
- The Administrative Console can use significant resources that may impact the client's performance.
- If the Administrative Console is installed with a Client machine, the Administrative Console would not be able to monitor activity when the client machine is down. By having the Administrative Console on a different machine you can monitor Client Manager(s) and receive alerts for to address warnings and connectivity errors.
Contacting Micro Focus Customer Support
For specific product issues, contact Micro Focus Technical Support.
Additional technical information or advice is available from several sources:
- Product documentation, Knowledge Base articles and videos - see the Support Resources for Databridge
- The Micro Focus Community pages - see Micro Focus Communities.
For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights, patent policy, and FIPS compliance, see https://www.microfocus.com/about/legal/.
© Copyright 2021 Micro Focus or one of its affiliates.
The only warranties for products and services of Micro Focus and its affiliates and licensors ("Micro Focus") are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.
Contains Confidential Information. Except as specifically indicated otherwise, a valid license is required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
Any links to third-party websites take you outside Micro Focus websites, and Micro Focus has no control over and is not responsible for information on third party sites.