GridServer 7.1.0 Hotfix05 has been released

GridServer 7.1.0 Hotfix05 has been released

book

Article ID: KB0100068

calendar_today

Updated On:

Products Versions
TIBCO DataSynapse GridServer 7.1.0

Description

GridServer 7.1.0 Hotfix05 has been released. Here are the release notes:
================================================================================
Introduction
 
Hotfixes are cumulative.
 
================================================================================
Affected Components for 7.1.0_hotfix05
 
The following components are updated by this hotfix:
 
.NET Specific
C++ Specific
Communication and Network
Database
Documentation
Drivers-All
Engine
Java Specific
Manager
Security
Server
Services
 
================================================================================
Closed Issues in 7.1.0_hotfix05 (This Release)
 
.NET Specific
GS-18504
.NETdriver(.NET framework) is upgraded to 4.6.
 
GS-18325
.NET core version is updated to .NET6. So, the artifacts with naming convention .NET5 refer to .NET6.
This would be handled in upcoming release.
 
 
C++ Specific
GS-17841
An issue with regenerating the encryption key on Linux machines is resolved.
 
 
Communication and Network
GS-18202
Internal File Server is implemented to have HTTPS protocol with Server side and Client side authentication. This is configurable at both Driver and Engine end.
Supported Drivers - Java, CPP, .NET Framework version 4.6.
 
A. To use this functionality at Driver end:
>Set Property
A new property, "DSDDTTLSEnabled" is added in driver.properties.
Set "DSDDTTLSEnabled" property to True to enable HTTPS File Server at Driver end. The default value is False.
 
>Place Certs
 
>>Set property through API
Java:
import com.datasynapse.gridserver.driver.DriverManager;
DriverManager.setProperty(DriverManager.FILESERVER_TLS_ENABLED,"true");
OR
Properties driverProperties = new Properties();
driverProperties.put(DriverManager.FILESERVER_TLS_ENABLED,"true");
DriverManager.addProperties(driverProperties);
 
CPP:
#include "driver/DriverManager.h"
DriverManager::setProperty(DriverManager::FILESERVER_TLS_ENABLED,"true");
OR
StringProperties driverProperties;
driverProperties.put(DriverManager::FILESERVER_TLS_ENABLED, "true");
 
.NET:
using DataSynapse.GridServer.Driver;
NameValueCollection option = new NameValueCollection();
option.Add(DriverManager.FILESERVER_TLS_ENABLED, "true");
OR
DriverManager.SetProperty(DriverManager.FILESERVER_TLS_ENABLED, "true");
 
OR
 
>>Set property through driver.properties
DSDDTTLSEnabled=true
When DSDDTTLSEnabled is set to True, other properties need to be set for respective drivers. The details are provided in driver.properties.
 
For .NET, the environment variable DS_ServerCertificate_pwd can be set for server certificate password.
It overwrites the value set in Driver.properties (DSCertificatePassword) and API (FILESERVER_SERVER_CERTIFICATE_PWD).
 
>Place Certs:
Java:
ssl.keystore : The SSL TrustStore which contains the signing authority, Certificate Authority (CA).
server.keystore : The SSL KeyStore which must contain the keypair and optional certificate signed by a default CA.
 
CPP:
ssl.pem : contains the signing authority (CA).
server.pem : SSL cert for Driver (in pem format).
key.pem : SSL Private key for Driver, key should be decrypted (in pem format).
 
.NET:
ssl.crt : This is ssl.pem renamed so that Windows recognizes it.
ca.pfx : Certificate file for X509Certificate.
openssl pkcs12 -export -out ca.pfx -inkey key.pem -in server.crt
 
ssl.keystore and ssl.pem are used for Java and CPP respectively for Driver-Manager communication, same is used for Engine-Driver communication.
 
B. To use this functionality at Engine end:
>Set Property
>Set JVM options
>Place Certs
 
>Set Property
A new property, "File Server TLSEnabled" is added under Grid Components > Engines > Engine Configuration > File Server section.
Set the "File Server TLSEnabled" property to True to enable HTTPS Internal File Server at Engine end. The default value is False.
 
>Set JVM options
When a non-default password is used, such as "changeitnew", for ssl.keystore and server.keystore, set JVM Options under Grid Components > Engine Configuration to:
-Djavax.net.ssl.keyStorePassword=changeitnew
-Djavax.net.ssl.trustStorePassword=changeitnew
-DkeyPassword=changeitnew
 
>Place Certs
Place the following Certs in Engine Home directory:
ssl.pem : contains the signing authority, Certificate Authority (CA).
ssl.keystore : The SSL TrustStore which contains the signing authority (CA).
server.keystore : The SSL KeyStore which must contain the keypair and optional certificate signed by a default CA.
server.pem : SSL cert for Engine (in .pem format).
key.pem : SSL Private key for Engine, key should be decrypted (in .pem format).
 
-------------------------------------------------------------------
 
Note:
If any class similar to GridLibDeployer is used to build and deploy the grid library, then update the class to include the following code for a non-default password, such as "changeitnew", for ssl.keystore and server.keystore, by setting the properties:
 
import com.datasynapse.gridserver.driver.DriverManager;
DriverManager.setProperty(DriverManager.FILESERVER_TLS_ENABLED,"true");
DriverManager.setProperty(DriverManager.FILESERVER_KEYPAIR_PWD,"changeitnew");
DriverManager.setProperty(DriverManager.FILESERVER_SERVER_CERTIFICATE_PWD,"changeitnew");
DriverManager.setProperty(DriverManager.FILESERVER_TRUSTSTORE_PWD,"changeitnew");
 
----------------- -------------------------------------------------
 
Note:
> The HTTPS File Server is supported for Java, CPP, and .NET drivers, but for other drivers, only the HTTP File Server is supported.
> HTTPS File Server is implemented at Engine end.
> Client Side Authentication is by default enabled at both Engine end and at Driver end when TLSEnabled is set to True.
> At Driver end, HTTP implementation is configurable. But when TLSEnabled is set to True, only ApacheHttpClientSupport is supported.
> There can be four possible configurations with TLSEnabled set to True or False at Engine and Driver end. Support is provided only for setting either True at both ends or False at both ends.
 
-------------------------------------------------------------------
 
For an upgrade scenario, perform the below steps manually :
> Update the configuration files "Config.xml.unix" and "Config.xml.win32" present in datasynapse/manager-data/conf to include below changes in <FILE_SERVER> section:
<DDTTLSEnabled VALUE="false" TYPE="boolean" JVM_ARG="DSDDTTLSEnabled" />
 
> Update driver.properties present under manager-data/driverInstall, to include below changes:
DSDDTTLSEnabled=false
 
 
Database
GS-18296
An issue where data in engine_stats is not getting recorded for the engines that lived less than 5 mins is resolved.
 
 
Documentation
GS-17939
The Build Version value is added in 7.1.0 hotfix Readme file.
 
 
Drivers-All
GS-18531
Gridserver now supports Microsoft Windows Server 2022.
 
 
Engine
GS-18246
A new property, "File Server TLSEnabled" under File Server section is added in the Engine Configuration.
If the property is set to True, then the Internal File Server launches at Engine's end using HTTPS.
If the property is set to the default value False, then the File Server launches using HTTP.
 
Set the "File Server TLSEnabled" property to True to access Engine logs through HTTPS.
It is expected that Manager is configured using SSL when using this property.
 
Certificates should be provided when trying to access the logs through the Browser or using Curl as the Client Side Authentication is enabled by default.
 
A. For supported Browser, perform the following steps:
1. Create a PKCS #12 format file using server.crt and server.key:
openssl pkcs12 -export -in server.crt -inkey server.key -out server.pkcs12.
2. Import the certificate in the browser.
 
B. Using CURL:
On Linux machine:
curl --cert ./server.crt --key server.key --cacert ssl.pem <log_url>
 
On Windows machine:
curl --cert server.crt --key server.key --cacert ssl.pem <log_url>
 
For an upgrade scenario, perform the following steps manually:
Update the configuration files "Config.xml.unix" and "Config.xml.win32" at datasynapse/manager-data/conf to include below changes in <FILE_SERVER> section:
<DDTTLSEnabled VALUE="false" TYPE="boolean" JVM_ARG="DSDDTTLSEnabled" />
 
 
Java Specific
GS-18462
GridServer now supports Oracle JDK 1.8.0.401.
 
GS-18465
GridServer supports Oracle JDK 11.0.22.
Engine: By default Engine JRE is Oracle Java 11.0.22 for Win64 and linux64.
Support is not provided to Java 11 for 32-bit versions.
 
GS-18399
GridServer now supports Azul Java 17.0.12.
 
Broker and Manager:
There are no changes for Broker and Manager installation.
 
Engine:
For Win64 and linux64, Oracle Java 11 is the default Engine JRE. Grid-library for running the engine on Azul Java 17 is added for Linux64 and Windows64.
 
To run the engine on Azul Java 17 perform the following steps:
1. Add the JVM parameter under Grid components -> Engine -> Engine Configurations. Select engine configuration file based on the operating system.
2. Update 'Command-line Arguments' with '--add-exports=java.desktop/com.sun.beans.editors=ALL-UNNAMED' under 'Engine JVM'.
Note: The above 'Command-line Arguments' parameter is only necessary for Java 17 and it should not be added for lower Java versions, such as Java 8 and Java 11.
 
Driver :
To run Java driver using Azul Java 17, add the following parameter as a JVM argument:
'--add-exports=java.desktop/com.sun.beans.editors=ALL-UNNAMED'
 
For reference, check the adder service example at GridServerSDK-Windows\examples\service\adder\runJava.bat.
 
 
Manager
GS-17884
When starting Manager as a Windows service by using Java 11 to setup 7.1.0 Gridserver, the Manager logs shows GMT/UTC instead of local timezone.
 
 
Security
GS-18439
When UserDatabaseHook is deployed, there is no differentiation for an authentication failure whether it is because of incorrect password or it is because of database connection failure.
This is handled by adding the UserDatabaseException unchecked exception.
 
 
Services
GS-17859
GridServer Manager fails to start when installed as Windows Service using Java11.
 
================================================================================
To download this hotfix, login to the Support Portal and navigate to Downloads > Hotfixes > AvailableDownloads > DataSynapse > GridServer > 7.1.0.
 

Issue/Introduction

GridServer 7.1.0 Hotfix05 Release Announcement

Attachments

GridServer 7.1.0 Hotfix05 has been released get_app