You can now install your on-premises Workload Automation environment also on Google Cloud SQL for SQL server, a fully-managed database service that helps you set up, maintain, manage, and administer your relational databases on Google Cloud Platform.
You only need to install your database, then proceed with the command-line installation for master domain manager and Dynamic Workload Console, as always, specifying MSSQL as the database type.
For the complete command-line installation procedure, see the section about Typical installation in Planning and installation.
For more information, see Creating the database for Azure SQL or Google Cloud SQL for SQL server for the master domain manager and Creating and populating the database for Azure SQL or Google Cloud SQL for SQL server for the Dynamic Workload Console in Planning and installation.

You can now configure WebSphere Application Server Liberty Base and fault-tolerant agents in SSL mode and provide your certificates at installation time using the command-line installation and setting the sslkeysfolder and sslpassword parameters. This ensures encryption in motion for all data moving within your environment.
Note: You are strongly recommended to customize the default certificates straight after the installation process has completed to ensure your environment is secure.For more information about installation parameters, see Master components installation - serverinst script and Agent installation parameters - twsinst script in Planning and installation.
Workload Automation also generates certificates in GSKit format. To enable FIPS compliance, set the ssl fips enabled option to yes in the localopts file after the installation has completed and restart the product. As a result, options for GSKit are automatically used by Workload Automation.
For more information about the localopts file, see Setting local options in Planning and installation.

You can now set up a proxy in case the master domain manager is located on a network without Internet access.

You only need to set up a proxy server and indicate the specifics of the proxy server when installing the master domain manager using the serverinst command.
​For more information, see How do I connect to the license server if the master domain manager cannot connect to the Internet and no proxy server is available? in Planning and installation.

​The File Transfer integration, already available on Automation Hub, now provides full capabilities for managing and processing all your file transfers using Workload Automation with no need for third-party products. The main enhancements are as follows:

Support for File Proxy
A new component, named File Proxy, is now available by default on each master domain manager. You can use the File Proxy to store and manage securely files to be transferred with the File Transfer integration available on Automation Hub. All transfer operations are performed by Workload Automation, with no need of third-party products.

You can also optionally install your File Proxy as a stand-alone component on a workstation different from the master domain manager, for example to reduce network traffic and resource usage on the master domain manager. You can configure your stand-alone File Proxy in high availability by defining the URLs of alternate file proxies or a load balancer in the Broker.fileproxy.urls property in the BrokerWorkstation.properties file. For more information, see BrokerWorkstation.properties file in the Administration Guide.
​
Ensure the selected workstation runs a supported version of a Windows or Linux operating system and proceed with the installation and start of the service, as described in File proxy installation - fileproxyinst script and File proxy start - fileproxystart script in Planning and installation.

Support for file transfers via the Workstation-to-Workstation internal protocol
You can now easily transfer files to and from agents connected to the same master domain manager. You no longer have to specify the address of the workstations involved in the file transfer, but you can simply define the workstations from the File Transfer integration. Ensure both the master domain manager and agents are at version 10.1. For more information about the integration, see File Transfer integration.

Search on remote file systems
You can now perform a search operation on the file system of a remote workstation. On Linux systems, if you do not specify a path, the search is performed on the working directory. On Windows systems, the path is required.

Integrations with Managed File Transfer (MFT) tools as well as Robotic Process Automation (RPA) tools
More integrations with other MFT tools as well as RPA tools to support orchestration of all data transfer using Workload Automation.

Starting from this release, key Workload Automation files are automatically encrypted for all fresh installations using AES-256 or AES-128 cryptography.
Data breaches are becoming more and more common and pervasive in today's business world. Encryption is a key feature when it comes to protect sensitive data, such as the data at rest stored in your Symphony plan or message queues. For this reason, all fresh installations starting from this release automatically encrypt key product files using AES-256 or AES-128 cryptography.
Data at rest means data is not being accessed or used but instead stored on your computer, external hard drive, cloud storage, server, or database. Encryption at rest ensures that this data is protected and encrypted.
If you want Workload Automation to encrypt files such as the Symphony file, messages queues, and the useropts file at runtime, you do not need to take any actions. By default, the product is automatically encrypted without your intervention. You can also define the folder containing the certificates and the certificates password using the sslpassword and sslkeysfolder parameters when installing the master domain manager and agents, both fault-tolerant agents and dynamic agents.
You can optionally avoid the encryption at installation time, by setting the useEncryption parameter in the serverinst and twsinst commands to false.
For more information, see Automatic encryption for key product files, Master components installation - serverinst script, and Agent installation parameters - twsinst script in Planning and installation.

You can now monitor the availability of your infrastructure and services, monitor performance, and analyze bottlenecks. Workload Automation features an improved mechanism for monitoring and auditing events. The monitoring engine generates a .json file containing all Workload Automation events, a file which is consumable by all applications using .json and meeting the OpenMetrics standard, for example AI Data Advisor (AIDA), Splunk and Fluentd.

By further analyzing these values through a data analytics tool, such as AI Data Advisor (AIDA), you detect anomalies and anticipate failure or degradations. For more information about AIDA and how to use it, see AI Data Advisor (AIDA) User's Guide.

You can also install Instana and monitor the whole infrastructure, both on-premises and cloud, on which you have installed Workload Automation.

On the cloud side, within the server and agent containers you have a number of sidecar containers which monitor .json log files.
On the on-premises side, you can feed your monitoring tool the .json log files and monitor your environment by creating custom dashboards in the monitoring tool.
This enhancement grants an immediate deep dive into all events generated in the Workload Automation environment.

For more information about the metrics IBM® Workload Scheduler exposes, see the section about monitoring Workload Scheduler in User's Guide and Reference.

The support statement for SAP S/4HANA, on-premise edition, has been extended to 2020 and future fix packs, based on SAP_BASIS 7.55 component.

OneDB database V2.0.1.0 is now supported.

OneDB is now supported also for pre-defined and customized reports.

The procedure for creating the OneDB database for the master domain manager is the same as the procedure for Informix. For more information, see the section about Typical installation in Planning and installation.

Job logs are now more secure and compliant with the PCI standard.

You can optionally avoid the temporary download of the job logs on the master domain manager if the job logs contain confidential information.

For more information, see Log files and archived files section in the Administration Guide.

You can now install or upgrade your master domain manager and dynamic domain manager in SSL mode. This ensures encryption in motion for all data moving within your environment.

For more information, see Configuring the master domain manager and broker in SSL mode in the Readme File for V9.5 Fix Pack 5

For more information about the localopts file, see Setting local options in the Administration Guide.