4. Click Apply. This pushes the new logging configuration, with a new HTTP URL, to the node, host, or application.
TAP-12860 Summary: If you have a main process and a subprocess application and one or more dependent main process applications deployed in ActiveMatrix version 3.1.5 (and any ActiveMatrix BPM version between 1.3.0 and 2.1.0), then upgrade the BPM platform version to BPM 2.2.0 (ActiveMatrix 3.3.0), and subsequently attempt to upgrade the subprocess, you will see a warning similar to the following
example:
TIBCO-AMX-ADMIN-012430: Provided capability
'com.example.my.subprocess.pe.capability' provided by component
'MySubAppProcessFlow' cannot be removed. It is being used by the following components:Component 'MyMainAppProcessFlow' from application
'com.example.my.mainapp.process
This warning is issued erroneously and can be safely ignored. The subprocess will be upgraded successfully and the main processes will run fine, provided the subprocess maintains the same major version number as before.
Workaround: None.
TAP-12878 Summary: If you import a resource template into an upgraded user application that did not previously contain a resource template (that is, if no resource templates had previously been imported into the application), the scope of the imported resource template will automatically be set to Global, rather than Application. This occurs even if you specify Application scope in the CLI.
Workaround: After the resource template is imported (to Global scope), you change its scope as required (to Application scope, for example) in the ActiveMatrix Administrator UI. To do this:
1. Go to Shared Objects > Resource Templates 2. Select the imported resource template
3. Click Change Scope, and change the scope to the Application or Environment level as desired
TAP-13696 Summary: If a Management URL is unreachable and you try to unregister the TIBCO Host, a warning message about the unreachable URL is not displayed.
Workaround: None
TAP-13777 Summary: If the TIBCO Host name in the ActiveMatrix Administrator GUI and run time is different and the TIBCO Host name from the ActiveMatrix
Administrator GUI is specified in the CLI data, the install/start/uninstall actions fail.
Workaround: None
TAP-13828 Summary: When installing or uninstalling a node, the most recent state of the node is displayed in the Action History column and not in the Node State column. For example, after uninstalling a node, the Node State is Not Installed while the action is in progress. This happens when there are incomplete tasks for an action but the node state has already changed.
Workaround Refer to the most recent state displayed in the Action History column instead of the Node State column.
TAP-13910 Summary: While exporting Logging Appenders, one logging appender
<CustomName>_Root is exported when the following conditions are met:
● host name of the replicated admin server is changed from the default SystemHostReplica to a custom name.
● Include System Objects option is NOT selected.
Workaround: None
TAP-13942 Summary: On the <Host> -> <ResourceInstance> page and Shared Objects ->
Resource Templates -> Resource Instances tab, environment or duplicate node information is not displayed.
Workaround: On the Details pane of <Host> -> <ResourceInstance> page and Shared Objects -> Resource Templates -> Resource Instances tab, navigate to the tree view in the left side pane. This tree view provides the exact node name:
.
TAP-13994 Summary: The Hostname in the Management URL of a TIBCO Host instance gets replaced with the Hostname of its source TIBCO Host, when TIBCO Host Instance is installed successfully.
Workaround: None
TAP-14052 Summary: The uninstall action does not work as expected with a wildcard if the given feature versions have strict (1.0.0) and qualified strict (1.0.0.01) versions together.
In a wildcard behaviour, the following behaviour is observed:
If the user has two versions for the same featureId in the form of 1.0.0 (Strict version without qualifier) and 1.0.0.001 (Strict version with qualifier), precedence is given to 1.0.0.001 only and 1.0.0 is not uninstalled.
Workaround: To uninstall 1.0.0 explicitly, perform the same action again.
TAP-14699 Summary: When the TRA property
java.property.com.tibco.amx.decouple.Manual.Nodes is not set to true in the tibcohost.tra file, the status of a Manual Node is marked as Stopped even when it is Running (Node process remains in task manager).
Workaround: None
TAP-14766 Summary: Ideally, in TIBCO ActiveMatrix, the user should update the Notification Transport for all TIBCOHosts in the Enterprise. If a particular TIBCOHost has to be updated using the "hosts" option from Administrator CLI, the user must update the SystemHost's Notification Transport first, and then proceed with updating the Notification Transport for other TIBCOHosts.
If SystemHost is not updated first, then while updating Remote TIBCOHosts, Administrator CLI may show the update as having been completed succesfully, but the TIBCOHosts may not actually be updated.
Workaround: Update the Notification Transport for the SystemHost first.
TAP-14772 Summary: Even when the Notification transport update was completed
successfully using the ActiveMatrix Administrator Command Line Interface, the following error message was displayed:
TIBCO-AMX-ADMIN-021085: Failed to update the notification transport!, Caused by:
TIBCO-AMX-ADMIN-021281: The number of hosts in this enterprise is more than 10.
Please use the Administrator Command Line Interface for updating the Notification Transport.
Workaround: None
TAP-14874 Summary: After reconnecting to EMS, ActiveMatrix Administrator shows the correct status but the Action History continues to show "In Progress(n)".
Workaround: None
TAP-15057 Summary: While upgrading to 3.3.1, the startAllHosts command of Patch Manager fails for each host if an old service with name "TIBCO ActiveMatrix Admin-amxadmin-instanceOne" exists on the machine.
Workaround: None
TAP-15060 Summary: After successfully downgrading to a previous version, you must uninstall the higher version.
Workaround: None
TAP-4645 Summary: In the Dashboards > Infrastructure screens, resource instances cannot be filtered by promoted reference or promoted service.
Workaround: In the Application Screen, check properties of the reference or service bindings.
TAP-4890 Summary: In the dashboards, a text filter is ignored when you maximize or minimize a gadget.
Workaround: Re-enter the text filter.
TAP-5653 Summary: Updating the value of a substitution variable for the Timeout property in a JMS or SOAP/JMS binding in a deployed application does not take effect after the application is redeployed.
Workaround: Undeploy and deploy the application.
TAP-6584 Summary: When the extended monitoring is enabled the two new periodic windows (24 hours and 7 days) do not show on some Dashboard tabs.
Workaround: Refresh the browser.
TAP-7423 Summary: You may see an Errors in dashboard dialog box when using the Dashboard.
Workaround: Click OK to proceed using the Dashboard. This error message can be safely ignored.
TAP-7571 Summary: Users who have permissions only to view an application and an
environment but do not have permissions to view a node are not able to see the list of selected nodes when distributing an application.
Workaround: Permissions to view the node have to be explicitly granted by a superuser.
TAP-7644 Summary: You may see the following error message when undeploying an application
[ERROR] com.tibco.amf.admin.server.axis2.RPCMessageReceiver - Error occured in Administrator... about to throw AxisFault for this exception
Workaround: Refresh the browser. This error message can be safely ignored.
WSBT-1112,
WSBT-1117 Summary: For SOAP Bindings containing all in-only operations, the Enable Response Message Validation field in TIBCO ActiveMatrix Administrator and TIBCO Business Studio is not applicable. At present, this field is not disabled for SOAP Bindings containing all in-only operations and if selected, it will have no effect.
Workaround: None
WSBT-1134 Summary: In case of SOAP Bindings, context parameters of Type "Message" can be defined using "Message/Part" from the WSDL used by the Binding. These
Message context parameters can be used for declared unbound SOAP Headers. The Body of a SOAP Message is also defined using "Message/Part" configuration from the WSDL used by the Binding. Using the same "Message/Part" configuration for the SOAP Header and the SOAP Body will result in incorrect behavior while generating the SOAP Message, in that, either the <Header> or the <Body> element may be empty. This applies to SOAP Request, SOAP Response and SOAP Fault Messages.
For example, if the Body of the SOAP Response is configured with
Message="GetSOAPResponse"/Part = "param1" in the WSDL and the context parameter of Type "Message" is defined with the same Message/Part Definition
"GetSOAPResponse/param1", the generated SOAP Response Message may contain empty <Header> or <Body> element.
Workaround: None However, if distinct "Message/Part" pair are used for SOAP Header and Body, this issue will not occur. For example, if the Body of the SOAP Response is configured with Message="GetSOAPResponse"/Part = "param1" in the WSDL and the context parameter of Type "Message" is defined with Message/
Part Definition "GetSOAPHeader/headerparam1", the generated SOAP Response Message will contain both <Header> and <Body> elements.
WSBT-881 Summary: Policies and policy sets cannot be added, edited, or deleted via the ActiveMatrix Administrator UI. Policy set properties can be viewed but not added, edited, or deleted.
Workaround: Edit policy sets and properties in Business Studio.
WSBT-888 Summary: Substitution Variables are not available for all the fields in SOAP Service and Reference Bindings. On the Service side, Substitution Variables are supported for the following fields:
1. Enable Request Message Validation 2. Enable Response Message Validation 3. Sender Identified Expression
On the Reference side, Substitution Variables are supported for the following fields:
1. Enable Request Message Validation 2. Enable Response Message Validation 3. Filespec of Endpoint URL
Workaround: None
XPD-1858 Summary: When opening a native file browse dialog on RedHat Linux for the first time, can crash.
Workaround: Type the path to the file in the text control.
XPD-5331 Summary: Deploying DAAs or applications with the characteristics listed below in ActiveMatrix BPM 2.2.0 runtime may result in the following error during runtime:
No request message is found to add the username token.
● The DAA or application was created in TIBCO Business Studio prior to version 3.6.0.
● The DAA or application contains a Web Service invocation (that is, the application is a consumer)
● The application has a UsernameToken policy type in its security
Workaround: Open the project in TIBCO Business Studio 3.6.0, build the DAA, and upgrade the existing application.