2. Infrastructure > Environments > Configuration > Messaging Bus > Test Connection
With this fix, EMS test connection gives the correct status of the connection.
TAP-14197,
TAP-13069 A limitation in the post-uninstall cleanup operations for a Node resulted in growth of the number of virtualization queues on the EMS Messaging Bus server. This has now been fixed and the required queues are deleted as part of the cleanup process.
The user must make sure that the OS ports have been configured to be open for the Messaging bus to ensure that the cleanup operations can be executed.
TAP-14201 Previously in the TIBCO ActiveMatrix Administrator CLI, in the event of an error, the Error Code for the failure was not displayed as part of the CLI output.
With this fix, the Error Code is displayed in the CLI output if there is failure.
TAP-14204 Starting with TIBCO ActiveMatrix 3.3.0 Hotfix 006, the format of the Governance Control Component URI was modified to include the Component Version (new convention format), and a 'Repair Policy' tool (delivered by PER-2000), using TIBCO ActiveMatrix Administrator CLI, was created to regenerate policies for Applications that were deployed before Hotfix 006. In Hotfix 012, this tool is enhanced to add two new CLI options, 'oldPolicyKey' and 'newPolicyKey'.
By default 'oldPolicyKey' is taken to regenerate policies for applications with old convention. The option 'newPolicyKey' is specified to regenerate policies for the new convention for Governance Control Components of applications that were deployed after Hotfix 006.
The sample scripts are installed as part of the TIBCO ActiveMatrix Installation at:
<TIBCO_HOME>/administrator/3.3/samples/
● repair_policies_build.xml
● repair_policies_data.xml
Additionally, the Repair Policy tool has also been enhanced to regenerate policies for Components, in addition to Endpoints.
The 'newPolicyKey' option only can be used for specific Applications, that is "Environment//Application", not for Environments or Nodes, that is "Environment" or "Environment//Node".
TAP-14206 TIBCO ActiveMatrix Administrator provides access to certain administrative functions via web service APIs. It was observed that use of
ApplicationService.getAllApplications() returned too much information and hence its performance was not optimum. To get better performance, a new web service ApplicationService.getAllUserApplications() with fewer fields has now been introduced, to return information for user Applications only.
TAP-14207 Previously, after an upgrade, the state of an already deployed TIBCO ActiveMatrix BPM application was set to "Out of Sync", even after an explicit redeploy.
With this fix the TIBCO ActiveMatrix Administrator correctly sets the TIBCO ActiveMatrix BPM application to 'In Sync' after a deploy following an upgrade where the new version has fewer endpoints than the previous running version.
TAP-14242 Logging into Administrator Server using SSL-Enabled LDAP Authentication
TAP-14303 Before this fix, initialization of TIBCO ActiveMatrix Administrator would take a long time when the SPM probe was enabled on a large deployment. This issue is now fixed and initialization of TIBCO ActiveMatrix Administrator now happens significantly faster even with a large setup.
TAP-14343 It was not possible to obtain TIBCO Host Name using the Built-in substitution variable.
TAP-14353 If the ActiveMatrix CLI targets were invoked, the piping error was directed to the standard out file. With this fix, the error and the output can be bifurcated into separate files. You can use different configuration properties as per your requirement.
TAP-14361 ActiveMatrix Administrator GUI did not retain user selections.
TAP-14369 TIBCO ActiveMatrix now supports Enterprise Deployment Health Check to help the user assess the overall health of an Enterprise, with a focus on the TIBCO ActiveMatrix Administrator.
With this feature, users can gather comprehensive metadata and runtime
configuration information of the Administrator at various levels (to include Hosts, Nodes, Environments), carry out real-time test deployments, and review all the collected information in a comprehensive report, to better equip them in making decisions about substantial upcoming deployments.
TAP-14370 There was no provision to download TRA file for TIBCO Node and Host as attachment and also to view them in Administrator UI.
TAP-14375 Previously in TIBCO ActiveMatrix Administrator, the LDAP group search was not displaying ALL expected top-level groups as specified in the group search filter.
With this fix, the LDAP group search now displays ALL expected top-level groups.
TAP-14377 Any user attempt to access TIBCO ActiveMatrix Administrator webpage during the initialization phase (when the System node was starting) would result in a "404 page not found" HTTP error response. The user had to periodically refresh the page to determine whether TIBCO ActiveMatrix Administrator was completely initialized and ready for service.
With this fix, when a user tries to access TIBCO ActiveMatrix Administrator web page while it is loading or types in the wrong URL (correct with respect to IP address and port number), then a new 404 page is displayed to the user. This web page will automatically redirect the user to the login page once TIBCO
ActiveMatrix Administrator is fully initialized and ready for service.
TAP-14381 Previously in TIBCO ActiveMatrix Administrator, having "owner" permissions on an Application did not imply "Deploy" permissions for the user. With this fix, the user with "owner" permissions on an Application is also able to deploy the Application.
TAP-14399 TIBCO Activematrix Administrator allows users to start TIBCOHost as a Windows Service through Host Life Cycle using Administrator UI/CLI.
With this, any TIBCOHost that is created as a Windows Service, will always start as Windows Service only.
TAP-14413,
AMX-15331 In TIBCO ActiveMatrix Administrator UI and CLI, when an Application is in a failure state, the Action History was incomplete as it did not display the complete stack trace, which is seen only in the Node log.
With this fix, when an Application goes in the 'failed to deploy/start' state, the Action History displays the complete stack trace, in both Administrator UI and CLI.
TAP-14418 Previously in TIBCO ActiveMatrix Administrator UI, the confirmation pop-up for Undeploy/Force Undeploy was shown for all the Applications (BPM as well as SOA) in the BPM Environment, where the BPM Environment Name was set to the default value, that is, "BPMEnvironment". If the Applications were under a differently named Environment, the pop-up for confirmation would not show.
With this fix, the confirmation pop-up will be shown for all BPM Applications in all Environments.
TAP-14517 In TIBCO ActiveMatrix Administrator, if a TIBCOHost is in "Lost Contact" state, the user was unable to start the TIBCOHost from the Administrator UI since the
"Start" button was disabled. With this fix, if a TIBCOHost is in "Lost Contact"
state, the "Start" button is no longer disabled and the user is now able to start the TIBCOHost from the TIBCO ActiveMatrix Administrator UI.
TAP-14542 If ‘%%_node.name%%’ was added in the Description field of the ‘Node_ROOT’ logging appender, it changed the name of the log file of SystemNode. With this fix, the log file name is not changed even if ‘%%_node.name%%’ is added in
Description field of ‘Node_ROOT’ logging appender.
TAP-14547,
TAP-14594 In TIBCO ActiveMatrix, if a TIBCOHost shutdown is not invoked from TIBCO ActiveMatrix Administrator UI or CLI, or using a TIBCOHost "stop" command, the TIBCOHost goes into "LOST_CONTACT" state after the shutdown completes, that is, if a TIBCOHost is killed by typing the "CTRL + C" command or from the Services panel (if running as a Windows Service), the TIBCO ActiveMatrix Administrator UI shows the TIBCOHost status as "LOST_CONTACT". This was due to incomplete shutdown of the TIBCOHost that forces the TIBCOHost and the Nodes managed by it, into "LOST_CONTACT" state.
With this fix, the TIBCOHost is now able to complete its cleanup and shut down gracefully even if it was terminated by typing "CTRL + C" or from the Services panel (if running as a Windows Service).
TAP-14567 Previously in TIBCO ActiveMatrix Administrator, CLI Actions for Node Start task would wait indefinitely, in Environments containing a large number of Nodes, as a result of certain exceptions not being surfaced to the Administrator CLI.
With this fix, the exceptions occurring during Node Start task will be captured by the Administrator and propagated to the CLI, thus preventing the indefinite wait.
TAP-14590 There was no provision to show EMS and Database Connection Status in TIBCO ActiveMatrix Administrator GUI.
TAP-14592,
AMX-15441 Currently in TIBCO ActiveMatrix, when the TIBCOHost's and/or Node's
connection to the Notification Server is terminated as a result of a network issue or due to a physical disruption, such as disabling the network adapter, the TIBCO ActiveMatrix Administrator UI shows the TIBCOHost's and/or Node's status as
"LOST CONTACT", and both the TIBCOHost and/or Node fail to reconnect to the Notification Server.
This issue has been addressed by making the TIBCOHost and/or Node reconnect to the Notification Server in the event of a network interruption.
With this fix, the TIBCO ActiveMatrix Administrator UI will no longer show the TIBCOHost's and/or Node's status as "LOST CONTACT".
TAP-14597 Adding or updating JVM Arguments from ActiveMatrix Administrator for Hosts was not supported.
TAP-14621,
TAP-14731 TIBCO ActiveMatrix Administrator erroneously removed existing Logging Configuration of TIBCOHost when Logging Configuration was updated from Administrator UI or CLI.
With this fix, the existing Logging Configuration of TIBCOHost will not be removed.
Additionally, the Logging Appender name has been changed from
SystemHost_Root to Host_ROOT. For an Environment upgraded to Hotfix14, both SystemHost_ROOT and Host_ROOT will be available. For newly created Hotfix 14 environment, only the Host_ROOT Logging Appender name will be available.
TAP-14661 The Database Info was not displayed in ActiveMatrix Administrator > Deployment Healthcheck UI.
TAP-14662 TIBCO ActiveMatrix Administrator CLI now supports the following types of timeout:
Normal Invocation timeout: The CLI times out if the CLI action cannot be finished by the specified time. By default, no timeout is set. This timeout value can be specified in two ways using the "timeout" attribute:
● In the Ant target. For example, to set the timeout to 60 seconds, set the following "timeout" attribute. The unit for the timeout is seconds.
<target name="deploy-applications">
<AMXAdminTask action="deploy"
objectSelector="Environment//Application"
remote="true"
propsFile="${instanceProperties}"
dataFile="${dataFile}"
force="true"
failOnError="true"
timeout="60"/>
</target>
● In the remote_props.properties file. For example, to set the timeout to 60 seconds, add the following "timeout" attribute. The unit for the timeout is seconds.
adminURL=http://localhost:8120 username=root
password=
httpConnectionTimeout=360000 timeout=60
This option can be used to set the timeout value for all Ant targets, without having to specify the timeout value in each Ant target separately).
The timeout value set in the Ant target takes precedence over the value set in the remote_props.properties file.
No progress timeout: The CLI times out if there is no progress on processing the tasks within the specified time. To specify the "no progress timeout", set the property com.tibco.admin.cli.noprogress.timeoutInMinutes in the SystemNode's TRA file. The unit for the timeout is minutes. For example, to set the "no progress timeout to 30 minutes, set the property as follows:
java.property.com.tibco.admin.cli.noprogress.timeoutInMinutes = 30
To disable the property, set the value to 0. The default value for "No progress timeout" is 45 minutes.
The "Normal Invocation timeout" takes precedence over the "No progress timeout". If Normal Invocation timeout value is set, the "No progress timeout" is ignored.
TAP-14673 Previously in TIBCO ActiveMatrix, the process of Node Uninstallation finished successfully, but the following directory was not removed since it was
continuously in use for the Node's life cycle operations: <CONFIG_HOME>\admin\
<enterpriseName>\shared\repo\trunk\env\<environmentName>\apps
\com.tibco.amx.platform\<nodeName>. As a result the following error was seen when the Node installation was attempted again:
"AMX-CLI-000020: Error invoking bulk action install on Node: TIBCO-AMX-ADMIN-012368: The application key already exists!".
With this fix, the directory is removed successfully during the Node Uninstallation process and the error is no longer seen.
TAP-14678 Previously, the TIBCO ActiveMatrix Administrator CLI console printed the first
"pending" task as the currently executing task, which was misleading
With this fix, the CLI console actually prints the first task that Administrator is currently executing.
TAP-14733 When the JVM was set using "\", the Node JVM setting could not be changed later and threw the error "java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence near index 49".
TAP-14737 Previously, the Command Line Interface (CLI) output did not show the root cause related to JMX remote port conflicts during Node startup.
With this fix, the root cause for any exception caught during Node startup is shown.
TAP-14748 Previously in TIBCO ActiveMatrix Administrator, when performing simultaneous Host uninstall actions, the following error was reported while removing Hosts from Administrator database: "Transaction not successfully started". With this fix, Administrator ignores the uninstall transaction if it is not active, instead of throwing an exception.
TAP-14758 Previously in TIBCO ActiveMatrix, if multiple Component References were promoted to the same Promoted Reference, and were distributed to different Nodes, the capability links for the distribution were not being created for the new Nodes.
This resulted in Application deployment failure with an error stating that the Component Reference configuration was not found. With the fix, Application deployment works successfully for this case.
TAP-14813 Previously, TIBCO ActiveMatrix Administrator did not create an Endpoint for a newly added Component Reference during Application upgrade. With this fix, all necessary Endpoints are created during Application upgrade and the Application goes into a "Running" state.
TAP-14815 The Action History state was "Stop Successful” even though the host state was
“Running”.
TAP-14819 The Operations Attempted on Nodes, belonging to non running hosts, did not result in immediate failure.
TAP-14822 The ActiveMatrix Administrator GUI welcome page now contains a hyperlink for the viewstatus.jsp page. Clicking this navigates to Infrastructure > viewstatus page.
This is not supported by Internet Explorer. For Internet Explorer, a link is provided on the page which opens viewstatus.jsp in a new tab.
TAP-14837 For error context TIBCO-AMX-ADMIN-012136, missing capabilities were shown in a single line and were truncated. With this fix, the error message provides helpful details and information on the missing capabilities is displayed in a separate row.
TAP-14844 There was no Restart Option for Nodes in ActiveMatrix Administrator GUI and also from CLI.
TAP-14850 There was no Restart Option for Hosts in ActiveMatrix Administrator GUI and also from CLI.
TAP-14862 TIBCO ActiveMatrix now enforces appropriate authentication on various HTTP Methods.
TAP-14863 TIBCO ActiveMatrix Administrator now enforces appropriate file type validation while uploading files.
TAP-14875 Previously, when using TIBCO ActiveMatrix Administrator CLI to Start or Stop a Node which is already in the process of Starting or Stopping respectively, the CLI Action would come back very quickly with "success", even though the Node Starting or Stopping activity was still in progress. With this fix, Administrator CLI fails with an informative error message when the user tries to Start or Stop a Node which is already in the process of Starting or Stopping respectively.
To enable this change the property
"com.tibco.amx.admin.node.start.stop.fail.if.in.progress" needs to be set to "true" in SystemNode.tra, as follows:
java.property.com.tibco.amx.admin.node.start.stop.fail.if.in.progre ss=true
Default value for this property is "false".
TAP-14876 As part of the Application Upgrade in TIBCO ActiveMatrix Administrator, the fields "Description" and "Contact" were not being updated in Administrator database, when the Application was being upgraded using CLI scripts generated from the TIBCO ActiveMatrix Studio. With this fix, the fields "Description" and
"Contact" will be updated during the Application upgrade process and the specified values can also be seen in Administrator UI.
To enable this change the property
"com.tibco.amx.admin.application.update.description.contact.during.upgrade"
needs to be set to "true" in SystemNode.tra, as follows:
java.property.com.tibco.amx.admin.application.update.description.co ntact.during.upgrade=true
Default value for this property is "false".
During the Application upgrade process, if values specified for
"Description" and "Contact" are empty, then these fields will NOT be updated in Administrator database. The values previously set for these fields will remain in effect.
TAP-14900 Changing the HTTP setting for ActiveMatrix Administrator using TIBCO Configuration Tool threw Null Pointer Exception.
TAP-14914 In TIBCO ActiveMatrix 3.3.0 Hotfix14, the Administrator Server Configuration could not be updated using TIBCO Configuration Tool (TCT) due to an internal error. With this fix, the Administrator Server Configuration can be updated using TCT.
TAP-14925 With ActiveMatrix 3.3.0 Hotfix14, editing ActiveMatrix Administrator
configuration (for example, HTTP Connection Settings) from TCT failed with a Null Pointer Exception. With this fix, ActiveMatrix Administrator configuration can be edited from TCT successfully.
TAP-14951 Previously, Jetty accepted /j_security_check via GET HTTP method. For example, http://localhost:8120/amxadministrator/j_security_check?
j_username=root&j_password=t lead to successful login or if user was already logged in, the user was not logged out. This enhancement disables the access to
j_security_check via GET HTTP method, so whenever the user tries to access
http://localhost:8120/amxadministrator/j_security_check?
j_username=root&j_password=t, the user will be redirected to login page.
TAP-15075 When adding an user-defined Java property for a Node, if the property had a backslash in the value, a PatternSyntaxException was thrown. With this fix, an exception is not thrown and the Java property is added to the node's TRA file with a double backslash.
For example:
-Dcom.sun.management.
jmxremote.password.file="E:\Java\jmx-management\jmxremote.password"
is added to the TRA file as:
-Dcom.sun.management.
jmxremote.password.file="E:\\ Java\\jmx-management\
\jmxremote.password"
TOOL-1675 Unable to setup a replicated admin server as TCT screen fails with "Unable to access the shared folder".
TOOL-1705 Passing a lower case drive letter in the machine model path for enabling the driver target "install.support.instantiate.tpcl.shell" resulted in an error:
"Caused by: unknown machine model installation file:/c:/
AMX_3.3.0_Full/components/shared/1.0.0/." With this fix, a more meaningful message is provided: "Caused by: unknown machine model installation
[Please check whether this path exists] file:/c:/AMX_3.3.0_Full/
components/shared/1.0.0/".
TOOL-1741 Previously, when TIBCO Configuration Tool (TCT) was launched from the
<TIBCO_HOME>\bpm\3.x\bin directory on the following setup, two options were not visible in the TCT wizard.
TIBCO ActiveMatrix BPM 3.0 or 3.1 Hotfix installed on a TIBCO ActiveMatrix BPM 3.0 or 3.1 setup
TIBCO ActiveMatrix 3.3.0 Hotfix-006, 007, or 008
The options that were not visible in the TCT wizard were:
● Upgrade TIBCO ActiveMatrix BPM Instance
● Configure TIBCO ActiveMatrix BPM Server Node Type
With this fix, the above options are visible in the TCT wizard when TCT is launched from <TIBCO_HOME>\bpm\3.x\bin directory.
With this fix, the above options are visible in the TCT wizard when TCT is launched from <TIBCO_HOME>\bpm\3.x\bin directory.