21 September 2021
FIXEdge Java 1.8. release: multiple new features and improvements
B2BITS, EPAM Systems company, is pleased to share the release of version 1.8. of FIXEdge Java.
New Features and Improvements
- Password obfuscation in FIX storages and application logs
-
- Secret information is masked inside persisted FIX sessions data (see maskPasswordsInStorages configuration option).
- The single authentication mechanism for all administrative interfaces
-
- All users for different administrative interfaces are defined within the admin-users.properties file. Access to a specific interface is defined by a user role.
- RPM and DEB packages
-
- FIXEdge Java may be easier installed and upgraded via Linux native packages.
- Using configuration values from environment variables
-
- Secure passwords and other important configuration values may be defined as environment variables and then used within FIXEdge Java configuration
- Load/reload FIX sessions configuration via administrative interfaces
-
- Remote Shell CLI and JMX API support a new operation on adding a new FIX session in runtime or update its configuration from configuration files.
- Log details about incoming SSL connection
-
- FIXEdge Java logs information about negotiated cipher suite, SSL/TLS version, and used SSL certificate for incoming secure FIX connections.
- Encrypted keys for Remote Shell configuration
-
- Remote Shell uses a private key for establishing connections. Private keys may be represented via protected keystores.
- Custom Keystore format for Administrative Remote Shell CLI
-
- Administrative Remote Shell CLI can be configured to use secure keys from custom secure Keystores (HSM with JCA support, Bouncy Castle).
- Automatic Start of endpoints
-
- Non-FIX endpoints (JMS, Kafka, and another) will be started with FIXEdge Java server initialization automatically. The automatic endpoint start might be changed via the startOnload property.
- Schedule endpoints start/stop within their configuration files
-
- There is no need anymore to define the schedule via the schdule.xml file. It can be done within the Endpoint configuration.
- The default configuration for groups of FIX sessions
-
- Configuration of FIX sessions may be grouped with folders and each folder may have a separate default configuration, common for all included sessions.
- FIXEdge Java system configuration files are moved to a separate folder.
-
- System configuration files were moved into a separate folder (sysconf) for further easier FIXEdge Java server maintenance and upgrade. User-related configs (security, endpoint, routing configuration) remained in the conf directory.
- Inject Message converters for a JMS endpoint as Spring beans
-
- JMS endpoint can resolve a message converter from Spring configuration by its ID.
- Start FIXEdge server without listening FIX ports
-
- Ports for FIX sessions can be opened/closed dynamically during FIX acceptor session start/stop. (See Extended acceptor ports management.)
- Optional JMX disabling
-
- JMX is used for monitoring and management of FIXEdge Java services. It can be switched on or off via the jmx.enable option in the fixedge.properties file.
- Force flushing for writing operations.
-
- An operating system may use buffers for IO operations with files for better efficiency. This means that persisted data may not be stored at the moment when the application writes it. With enabled forced flush mode (storageFlushMode=Force), FIXEdge Java does the additional call for forcible flush IO buffers to the storage drive.
The complete Release Notes are available in Knowledge Base.
For our existing customers, the new version of FIXEdge Java is available for download in the B2BITS client space. For other interested parties, an evaluation of FIXEdge Java is available upon request. Please direct requests for evaluation to sales@btobits.com.