Release Notes

Applications Manager
V9.3.5
What's New?
Applications Manager
V9.3.4
What's New?
  • Broadcom may request you for the telemetry report as and when required. For more information, refer to Applications Manager Telemetry data.
  • You can now add a component with a right-click to an existing job or process flow and also retain the component's configuration. For more information, refer to Add components and retain the existing configuration.
  • You can now have different colors for Applications Manager main window for different deployments of Applications Manager. For example, you may want to have a Brown color for the development environment and Green color for the production environment. For more information, refer to Configure Applications Manager Main Window Color.
  • Applications Manager
    9.3.4 now supports RedHat Enterprise Linux 8.
Applications Manager
v9.3
What's New
Oracle 18c Now Supported
In
Applications Manager
9.3, Oracle 18c databases are supported. For special instructions, see
Creating the Database Account
in the
Installation Guide
.
Specifying a Unique Location for Multiple Keystore Files in v9.3.1
Starting with v9.3.1, you can specify a unique location for multiple keystore files. To do this, you create a
C:\Users\<user name>\AppWorx\<master name>
folder for each master in the
connections.properties
file on each user's client machine where
<user name>
is the actual user's name and
<master name>
is the name of the master. Then put copies of the
user_keystore
and
user_keystore_config
files for each master the sub-directory for that master.
RunClient.jar Error Messages Now in the
startClient.log
file in v9.3.1
When starting the local client by double clicking on
RunClient.jar
(or a shortcut to it) in version 9.3.1 or above, if it fails to start the error will now be in the
startClient.log
file.
Changes in Behavior
Executable .jar File for the Client Must Be Downloaded and Configured
You must now download the
Applications Manager
client from the URL set during installation. To get this URL, see your
Applications Manager
administrator. Before logging in the first time, you need to configure the client for the Automation Engine(s) you will be logging into. Once configured, you open an executable
.jar
file. For more information, see
Opening the
Applications Manager
Client and Logging In
in the
User Guide
.
Custom SSL Certificates for Connection Authentication Now Required
You must use a custom SSL certificate for connection authentication by creating
user_keystore
and
user_keystore_config
files on the Automation Engine and client machines. For more information, see
Using Custom SSL Certificates for Connection Authentication
in the
Installation Guide
.
Keyfiles No Longer Required
Starting with
Applications Manager
9.3, license checking with keyfiles is no longer required for Automation Engines or agents.
Applications Manager
v9.2
What's New
Requesting a Job or Process Flow from its Definition
You can now request a Job or Process Flow from it's definition. This opens the
Submit
window, like the
Request
window does. This is beneficial for testing changes you make to the object.
Using Retention Days for Notification Log Files
When you define a Job, you can set the number of days the output will be retained by
Applications Manager
in the
Retention days
setting on each Job's
Output
tab. When a Notification is assigned to the Job, it will use that Job's retention days to determine when to delete the Notification's log files.The SODELETE Job (alias DELDEFAULT) deletes the output files that have exceeded their retention settings.
Changing Database Login Passwords without Restarting
You can now change Database Login passwords used for Subvars and conditions without restarting.Ignoring Max Length Prompt Validation within Process Flow Component Prompt Overrides when { } Are UsedAny component prompt value beginning with { ignores field limitations in order to allow Subvar overrides.This functions the same regardless of whether
Upper Case
is checked at any level.
Using Oracle Advanced Queuing for OAE
Removed
DBMS_PIPE
from OAE-related code and replaced the functionality with Oracle Advanced Queuing (AQ).
This change requires a dedicated AQ admin account to manage the AQ tables and Queues.
All OAE related database schema objects can now be created in a dedicated OAE Oracle User, instead of using
APPS
User. The existing OAE User can continue to use APPS account to deploy OAE objects or migrate the OAE setup to the dedicated Oracle User through some easy steps.
Running an RA Oracle EBS Agent and
Applications Manager
OAE Agent in same EBS database
You can now running an RA Oracle EBS Agent and
Applications Manager
OAE Agent in same EBS database. This is beneficial when you are moving from the
Applications Manager
with the OAE Agent to
Applications Manager
or Automation Engine with the OEBS Agent.
Applications Manager
v9.1
What's New
Auto-logout Client Setting in Options.properties
You can now set the number of minutes of inactivity before an auto-logout of the Java client by adding
IdleLogoffTime=<number of minutes>
to the
Options.properties
file. To unset this options, set
IdleLogoffTime=0
.
Support for Stronger Strength Ephemeral DH keys in the SunJSSE Provider
We set
jdk.tls.ephemeralDHKeySize
to Java version-specific values: 2048 for Java 1.8 and above. If you want to use 2048 bit certificate keys, both the server (rmiserver) and the client (UI or AgentService) need to be running Java 1.8 or above. For more information, see your Java documentation.
Applications Manager
v9.0
What's New
Active-Passive Failover
The
Applications Manager
Automation Engine now supports active-passive failover. A secondary
Applications Manager
RMI server can be setup and run in stand-by mode (active-passive), so that in the event that the primary
Applications Manager
Automation Engine goes down, the stand-by RMI server will become the active Automation Engine. When the stand-by RMI server becomes active, the Agents will reconnect to it automatically; with the exception of the Local Agent. That is because the Local Agent is part of the Automation Engine installation, and integrated with the specific Automation Engine system. Therefore, in systems that require RMI server failover, it is recommended that all Jobs be setup to run on Remote Agents.
Platform and Oracle Support
Version 9 is the first
Applications Manager
release that supports Oracle 12c databases. When using Oracle 12c database and you have an Oracle Enterprise Edition multi-tenant system or Oracle Standard Edition single tenant system, you must install
Applications Manager
into a pluggable database (PDB) within a container. Your DBA is responsible for creating the pluggable database.
Enabling/Disabling RMI Server Debug with the RMI_DEBUG Job
You can now enable or disable RMI server debug by running the RMI_DEBUG Job. Like all
Applications Manager
Jobs, you can request and submit RMI_DEBUG to run it ad hoc, or schedule it. Activate or deactivate RMI server debug by setting the Enable prompt to
Yes
or
No
. The RMI_DEBUG Job is included in the
RMI_DEBUG
import file.
Desupported Features
The following features are desupported for
Applications Manager
v9:
  • The Dashboard
  • AppMaster
  • Remote Method Extension Agents
  • VMS Agents
  • OS400 Agents
  • ZOS (mainframe bridge) Agents
The supported platforms for the Automation Engine and its Agents change between releases. For a list of supported platforms for the Automation Engine and Agents in this release, see the Matrix below.
Known Issue: You Cannot Retrieve a Local WSDL File for a SOAP Login Object
You cannot retrieve a local WSDL file for a SOAP Login object using the Web Service Agent. This will be fixed in
Applications Manager
v9.0 Service Pack 1 and a patch is available from Broadcom Support.