2024 October FeatureLog
View the various changes made to the FairCom documentation in the month of October
Users can automate Replication Manager operations by creating JSON input files and sending them to the replutil
command-line utility. Otherwise, these operations must be individually executed through the Replication Manager UI or through direct calls to the Replication HTTP API.
FairCom DB 13.0.0
FairCom Edge 4.0.0
FairCom MQ 4..0.0
FairCom RTG COBOL 4.0.0
FairCom RTG Btrieve 4.0.0
Users , Developers , and Administrators
D404
New replication CLI utility
You can run certinfo against a PKCS12 (.12) file to show the primary key, the primary certificate, and any additional certificates.
FairCom DB 13.0.1
FairCom Edge 4.2.1
FairCom MQ 4.2.1
FairCom RTG COBOL 4.2.1
FairCom RTG Btrieve 4.2.1
Administrators
D1257
You can run certinfo against a PKCS12 (.12) file to show the primary key, the primary certificate, and any additional certificates
The documentation now includes use cases for using replication for high availability, disaster recovery, and scalability.
FairCom DB 13.0.1
FairCom Edge 4.2.1
FairCom MQ 4.2.1
FairCom RTG COBOL 4.2.1
FairCom RTG Btrieve 4.2.1
Developers and Administrators
D1411
use cases for using replication for high availability, disaster recovery, and scalability
FairCom enables applications to authorize JSON actions without the need for a username/password or client certificate using the permanentSession
property. While it is slightly less secure, it allows many servers to use the same authToken (API key) to simplify session management.
FairCom DB 13.0.1
FairCom Edge 4.2.1
FairCom MQ 4.2.1
FairCom RTG COBOL 4.2.1
FairCom RTG Btrieve 4.2.1
Administrators
D1435 and D1454
persistent sessions permanentSession property
You can now reduce the variability in performance of a client application by setting the maximum number of spin operations that a shared memory connection can use.
FairCom DB 13.0.1
FairCom Edge 4.2.1
FairCom MQ 4.2.1
FairCom RTG COBOL 4.2.1
FairCom RTG Btrieve 4.2.1
Administrators
D1302
use SHMEM_MAX_SPIN and ctSetCommProtocolOption to control the number of spin operations that a shared memory connection can use
The new variantFormat
property allows you to specify the format in which variant fields are returned from JSON DB API "getRecords..."
actions so that you can set the data format returned from a variant, such as hexadecimal, Base64, UTF-8, and the variant JSON object.
FairCom DB 13.0.1
FairCom Edge 4.2.1
FairCom MQ 4.2.1
FairCom RTG COBOL 4.2.1
FairCom RTG Btrieve 4.2.1
Developers and Administrators
D1437
variantFormat property get records actions
The new "authenticationMethods" property allows you to control which methods MQTT clients are allowed to use to authenticate. For example, you can limit client authentication to any combination of client certificate and/or username/password.
FairCom DB 13.0.1
FairCom Edge 4.2.1
FairCom MQ 4.2.1
FairCom RTG COBOL 4.2.1
FairCom RTG Btrieve 4.2.1
Developers Administrators
D1166
Improved MQTT communication security
Faircom now supports FIPS 140.2 through OpenSSL 3.0 to ensure secure communications. FIPS 140.2 is an encryption standard established by the US federal government for verifying the implementation of OpenSSL.
FairCom DB 13.0.1
FairCom Edge 4.2.1
FairCom MQ 4.2.1
FairCom RTG COBOL 4.2.1
FairCom RTG Btrieve 4.2.1
Developers Administrators
D586
FIPS validation for secure communications
This feature migrates previously encrypted files into FIPS-140.2 format for enhanced security, compatibility and functionality.
FairCom DB 13.0.1
FairCom Edge 4.2.1
FairCom MQ 4.2.1
FairCom RTG COBOL 4.2.1
FairCom RTG Btrieve 4.2.1
Developers Administrators
D586
Enable FIPS validation of encrypted files
This feature provides enhanced transaction log diagnostics capability when enabled using the CHECK_TRNLOG_BUFFER_WRITES configuration option. The DIAGNOSTICS TRNLOG_WRITES option writes transaction log entries that report when bytes are being skipped and when the transaction type is invalid.
FairCom DB 13.0.1
FairCom Edge 4.2.1
FairCom MQ 4.2.1
FairCom RTG COBOL 4.2.1
FairCom RTG Btrieve 4.2.1
Developers Administrators
D1433
Improved transaction log diagnostics using new configuration options
Quickly recover from a Pacemaker cluster failure state with our new tutorial on how to recover from cluster failure states with replication.
FairCom DB 13.0.1
FairCom Edge 4.2.1
FairCom MQ 4.2.1
FairCom RTG COBOL 4.2.1
FairCom RTG Btrieve 4.2.1
Administrators
D1456
Tutorial Pacemaker failover when using replication
You can now specify that DB Notify messages contain a whole record buffer instead of individual fields. This allows you to track changes to files that do not have field definitions or table names. Additionally, you can now use a pathname to specify non-SQL files that you want to track.
FairCom DB 13.0.1
FairCom Edge 4.2.1
FairCom MQ 4.2.1
FairCom RTG COBOL 4.2.1
FairCom RTG Btrieve 4.2.1
Developers
D1427 D1464
DB Notify ISAM records without fields and non-SQL data files
You can use JavaScript to transform the output of all JSON DB "getRecords..."
actions. You can add fields, change field values, and calculate aggregate values like min, max, and average.
FairCom DB 13.0.1
FairCom Edge 4.2.1
FairCom MQ 4.2.1
FairCom RTG COBOL 4.2.1
FairCom RTG Btrieve 4.2.1
Administrators
D1500