| Wiki Markup |
|---|
h1. Release Notes
Universal Agent release 6.7 contains the following high level features, for a complete list of all the included features and fixes please refer to the [Universal Agent 6.7.x Maintenance list|Universal Agent 6.7.x Maintenance].
|| Backlog ID || Tile || Description ||
| B-10383 | Upgrade OpenSSL to Version 111B | Upgrading our OpenSSL environment to version 102f will require some changes to the Ciphers being used or available within the Agent Infrastructure.
Windows, Linux, and Unix platforms, apart from HP-UX, have been upgraded with Universal Agent 6.7.0.0.
z/OS and z-Linux will be upgraded as part of Universal Agent 6.8.0.0, as it requires a couple of prerequisites not being manageable for the 6.7.0.0 Release.
HP-UX will currently remain undone and will be re-evaluated if there is a customer requirement for that specific platform.
With GA of Universal Agent Version 6.7.0.0, as part of the OpenSSL upgrade, the following Cipher will no longer be available: DES-CBC-SHA. This is due to the fact that that Cipher are no longer supported with OpenSSL 111B. Nevertheless, for compatibility reasons it will remain in the cipher list for platforms still supporting it. Selecting it for a platform not supporting it will flag it as an invalid value. Customers using that Cipher need to use the TLS null-null Cipher suites instead if neither of the supported ciphers is suitable for the platform or the environment.
For Universal Agent 6.7.0.0, the following Ciphers remain available:
{html}<ul>
<li> AES256-GCM-SHA384
<li> AES256-SHA
<li> AES128-GCM-SHA256
<li> AES128-SHA
<li> RC4-SHA
<li> RC4-MD5
<li> DES-CBC3-SHA
<li> DES-CBC-SHA
<li> NULL-SHA
<li> NULL-SHA256
<li> NULL-MD5
</ul>{html}
In a future release of Universal Agent, the following Ciphers will be deprecated and no longer available:
{html}<ul>
<li> DES-CBC3-SHA
<li> RC4-SHA
<li> NULL-SHA
<li> NULL-MD5
</ul>{html} |
| B-10357 \\
B-10313 | Open JRE 8 for Windows and Linux | For the SOA Connector, the Open JRE Version 8 is now packaged, supported, and validated.
On the Agent side, the SOA Connector is the only component we do package as a Java run-time component. |
| B-05491 | Add message _dest LogFile support for Windows Platform | Allow changing of the Logfile Destination for the Agent Log on Windows systems.
You can now change the destination of the UNCLOGUNVLOG to a destination of your choice on Windows systems as well.
New Parameter option have been added to message_dest.
{html}<ul>
<li> log_directory defining where the Ubroker Log should be stored.
<Li> message_dest allowing to define the location for Broker Log messages.
</ul>{html}
System is the default and routes all messages to the system Console
Logfile directs messages to the UNVLOG as specified in the log:directory Parameter
STDERR directs messages to the STDERR file of the Job Output |
| B-10731 | Research AWS S3 file monitoring | AWS file systems have been researched, alongside the technology of the currently available universal Tasks, and a basic design for making this technology available as part of the Universal Agent has been created. |
| B-10329 | Research HDFS File Monitoring | HDFS file systems have been researched, alongside the technology of the currently available universal Tasks, and a basic design for making this technology available as part of the Universal Agent has been created. |
| B-07363 | OMS Server should enforce the usage of SSL connections | A new Option in configuration Member OMSS:
*Option: require_ssl*
*Default: no*
\# Whether to require clients to establish SSL connections.
\# If set to 'yes', the OMS server will reject all non-SSL
\# client connections.
The processing when require ssl is set to yes is as follows:
# require_ssl = “yes”, min_ssl_protocol = “TLS1_0” or “TLS1_2”, then SSL must be used
the session cannot be negotiated to an SSL level lower that the one specified in min_ssl
# require_ssl = “yes”, min_ssl_protocol = default (‘tls1_0’), then SSL must be used
lowest, supported sslL level in this case is TLS 1.0
# require_ssl = “no”, min_ssl_protocol = “TLS1_0” or “TLS1_2”, then SSL is not required
The session can be negotiated on whatever level is agreeable between both parties
# require_ssl = “no”, min_ssl_protocol = default, then SSL is not required
The session can be negotiated on whatever level is agreeable between both parties
# require_ssl = default (‘yes’), min_ssl_protocol = “TLS1_0” or “TLS1_2”, same as #1
# require_ssl = default(‘yes’), min_ssl_protocol = default, then same as #2 |
| B-10229 \\
B-10800 | Update Windows Installer package to 64-bit Installation | The Windows Installer package, as well as all required routines, has been upgraded to support native 64-bit installation process. |
| B-10308 | Deliver USOA for 64-bit windows systems | Effective immediately, a standard download package for 64-bit windows systems is available. |
| B-10687 | UPPS Web Services Call to become Fault Tolerant | Fault Tolerance for UPPS Connector based WEB-Services. |
| B-06684 | Threshold to avoid memory consumption of UDM when using the acknowledge window. | |
| B-03322 | Specify UAG z/OS log-data sets as GDG | z/OS Log datasets can now be defined as GDG and managed by the z/OS catalog accordingly. We do consider Backlog B-03644 as solved by this implementation as well, as deleting the log datasets can now be handled by the definition of generations available.
Job UNVIN07 has been updated to create a GDG for the UAG log dataset by default.
A new job, UNVIN11, has been created for use during upgrades. It is optional if a customer wishes to continue using sequential datasets for the log.
In order to switch to using GDGs for the UAG log dataset, create a GDG base with the same name as the log dataset.
The log dataset is named by appending ".UAG.AGENT.LOG" to the value specified for the &PHLQ parameter in the UBROKER JCL PROC. Deleting the GDG will cause UAG to switch back to using sequential datasets.
Sample JCL to create a GDG base:
{panel}{html}<pre>
//STEP1 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINE GENERATIONDATAGROUP -
( -
NAME(<&PHLQ>.UAG.AGENT.LOG) - <=== replace &PHLQ
LIMIT(7) -
SCRATCH -
)
/*
</pre>{html}{panel} |
| B-10795 \\
B-10701 \\
B-10794 | Upgrade Regex support for identifying UTF 8 and UTF 16 encoded file names | Introduce extended REGEX support, based on BOOST, for all platforms to allow identification of filenames regardless of UTF8 or UTF16 encoding.
Linux and Windows systems, as well as all Unix derivatives, have been upgraded with 6.7.0.0.
z/OS Agent will be updated with 6.8.0.0 as the required BOOST Library is not available/supported on the z/OS platform we are running on.
Also, this enhancement is currently available only for internal use in identifying the file names but will be opened to the general use of Extended REGEX support with Universal Agent 6.8.0.0. |
| B-10801 | Port Universal Configuration Manager to 64-bit Windows. | The configuration manager is now also available as a 64-bit application under Windows. |
| B-10934 | Agent Certification | Universal Agent now tested and validated for Windows 2019. |
| B-10628 | Update xpsmsgnt.dll to include messages ids of all Universal Agent message catalogs | Universal Agent 6.6.0.0 identified a couple of missing messages. This backlog ensures messages to be present as in the message catalog. | |
Manage space
Manage content
Integrations