TIBCO ActiveMatrix(R) Service Grid 3.3.0 Hotfix, TIB_amx_3.3.0_hotfix003, is now available.
Article ID: KB0104694
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix Service Grid | - |
| Not Applicable | - |
Description
Description:
================================================================================
Hotfixes are cumulative. This hotfix includes all previous generally available
hotfixes for TIBCO ActiveMatrix(R) Platform 3.3.0.
================================================================================
Closed Issues in 3.3.0_hotfix003 (this release)
This hotfix contains fixes that apply to the following types of installations:
- Administration
- Runtime Host
- TIBCO Business Studio
AMRP-2669
The JMS Transacted One-Way Policy and Threading Policy are now compatible, provided
the binding and component services run on the same node without a Virtualize Policy.
BJMS-1569
TIBCO ActiveMatrix Administrator now allows use of a substitution variable
for JNDI connection configuration in the JMS Connection Factory resource template.
DSS-836
The following fatal error, "...TrinityRuntimeException: TCSConnection object is null:;",
caused by the expiry of an internal identity certificate is now resolved. The above
error occurred when there were TIBCO ActiveMatrix nodes that are more than two years old.
DSS-864
Sporadic credential-mapping errors no longer occur when different operations within
the same composite application are invoked.
HKAM-274
This fix worked correctly on fresh nodes only in 3.3.0_hotfix001. Now, this fix works on
patched nodes as well.
PER-1934 and PER-1940
After removing the security policy at an endpoint the governance agent no longer enforces
security policy.
PER-1945
Two timestamps are no longer added to the security header when using a policy set with
WSS SAML Credential Mapping and Timestamp policies.
PER-1946
Users now have the option to immediately log the policy messages to the syslog-ng
appender when the custom log policy receives a request message, or log the message
after the operation is complete.
Use the following steps to set up the option:
1. From Administrator, select Infrastructure -> Nodes.
2. Select the node on which the logging policy is deployed.
3. Select the Configuration tab and Logging link.
4. Select the Advanced button.
5. Set the 'governance.policy.logger' level to TRACE.
6. Save and Apply.
PER-1951
Enforcing SSO SAML Credential Mapping policy no longer
results in an error following upgrade from TIBCO ActiveMatrix 3.1.5.
SCF-249
Exporting of TIBCO Business Studio projects using Mac OS X is now consistent with
Microsoft Windows. Users can now specify a new file name for archiving from the
archive dialog of Mac OS X.
SDS-7320
In TIBCO Business Studio, users now have the option to include or exclude the
application template and feature version qualifiers in the 'Administrator CLI Script Generation'
wizard. By default, this option is disabled, and to enable it uncheck
'Exclude version qualifier(s) for Application Template and Features' option.
SDS-7356
The NullPointerException no longer occurs intermittently while attempting to
validate a project in TIBCO Business Studio.
SDS-7407
In TIBCO Business Studio, when a project is launched in debug and run mode, the
console message now prominently indicates the port number configured for the HTTP connector.
For example:
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
*** HTTP connector listening on port '5002' ***
Use URL: http://localhost:5002/sample/ for SOAP or Web access.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
TAP-12597
TIBCO ActiveMatrix Administrator now supports substitution variable for
Connection Retrieval Timeout, Maximum Total Connections, and Maximum
Total Connections per Host fields of the HTTP Client resource template.
TAP-12922
Upgrading an application in TIBCO ActiveMatrix Administrator no longer fails
when two nodes have the same name in different environments.
TAP-12972
Deleting a feature version using CLI using in TIBCO ActiveMatrix Administrator
works as specified. For example, let us say there are four features:
Feature 1 - A.1.2.3
Feature 2 - A.B.1.2
Feature 3 - A.B.C.1
Feature 4 - A.B.C.D
When CLI is used to delete features using version as wildcard:
Specifying "A" will delete all the four features.
Specifying "A.B" will delete features 2,3 and 4.
Specifying "A.B.C" will only delete feature 3 and 4.
Specifying "A.B.C.D will delete feature 4.
TAP-12973
Users can now remove a feature using wildcard in the TIBCO ActiveMatrix Administrator
CLI configuration file when the force attribute is set to 'true' even if the feature
is enabled on any node. When the force attribute is set to 'false' only those features
that are not enabled on any of the nodes are deleted.
TAP-13058
Deploying an ActiveMatrix BPM application a second time after an earlier upgrade failure
that was not cleaned up using force undeploy no longer prematurely removes the endpoints
of the older version. Instead, users see a validation error, and the second deploy action
is blocked. The error message is as follows:
"Not allowed to deploy the version '<new version>' of application '<app name>'.
This version may have failed to deploy earlier, and if so it should be force-undeployed first."
Note that force undeploy destroys BPM data for a given version, which means all existing
work items and process instances of the current version are cancelled. Force undeploy must be
used only when you are sure that the BPM data for the version you are force undeploying
is not needed and its loss is acceptable. Otherwise, contact TIBCO Support.
TAP-13062
Running TCT workflow "Edit Tibco ActiveMatrix Administrator Server Configuration" for replicated
administration no longer fails with the error "SystemNode does not exist".
======================================================================
NOTE: See attached Readme document for installation instructions and issues resolved in previous hotfix releases.
================================================================================
TIBCO ActiveMatrix(R) Service Grid 3.3.0 Hotfix, TIB_amx_3.3.0_hotfix003 can be downloaded from the TIBCO Product Support file transfer server, mft.tibco.com, using you username and password for the TIBCO Support Central website. Please note you should use an FTP or SFTP client or command-line FTP. TIBCO employees must use a secure protocol.
Server name: mft.tibco.com
Credentials: use your TSC (TIBCO Support Central website) login.
Browser: https://mft.tibco.com
FTP: port 21
SFTP: port 22
Once logged on you can find the hotfix under:
available_downloads/ActiveMatrix/ActiveMatrixServiceGrid/3.3.0/TIB_amx_3.3.0_hotfix003
Issue/Introduction
TIBCO ActiveMatrix(R) Service Grid 3.3.0 Hotfix, TIB_amx_3.3.0_hotfix003, is now available.
Environment
Applicable Products
This hotfix applies to the following products and versions:
- TIBCO ActiveMatrix Service Bus 3.3.0 - TIBCO ActiveMatrix Service Grid 3.3.0 - TIBCO ActiveMatrix BusinessWorks Service Engine 5.11.0 - TIBCO ActiveMatrix BPM 2.2.0 - TIBCO Business Studio BPM Edition 3.6.0
Additional Information
TIB_amx_3.3.0-HF-003_readme.txt
Attachments
Feedback
Yes
No
Powered by
