TIBCO ActiveMatrix(R) Service Grid 3.3.0 Hotfix, TIB_amx_3.3.0

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_hotfix004 (This release)

This hotfix contains fixes that apply to the following types of installations:

- Administration

- Runtime Host

- TIBCO Business Studio

AMX-14462

TIBCO ActiveMatrix Service Performance Manager 2.2.0 is now supported. For more

information, refer to TIBCO ActiveMatrix Installation and Configuration Addendum,

tib_amx_3.3.0-HF-004_installation_addendum.pdf, provided with this hotfix.

BJMS-947

Deployment of an application with SOAP/JMS or JMS service bindings that use lengthy

name spaces in the WSDL no longer fails in the runtime node with the exception "Client

ID too long". The node automatically shortens the JMS client ID, using an internal

name mangling algorithm, to less than 255 chars by default. The following system

properties when added to the node.tra overrides the default behavior:

* java.property.com.tibco.amf.binding.jms.skip_client_id_generation=true

Causes the JMS Client ID to not be set, since as per JMS specification, the

Client ID is optional. The default behavior of setting a Client ID, however,

allows for better traceability of client connections.

* java.property.com.tibco.amf.binding.jms.max_client_id_length=255

Causes the internal algorithm for Client ID generation to shorten the value to the

specified length. TIBCO Enterprise Messaging Server has a Client ID limit of 255,

which is also the default value used. For your JMS provider, you can alter the

value as needed.

DSS-878

When not configured to require mutual authentication, an SSL-enabled HTTP connector no

longer prompts the client for mutual authentication during an SSL handshake.

MED-3322

On TIBCO ActiveMatrix 3.3.0 with a TIBCO ActiveMatrix Policy Director 1.0.1 HF01 setup,

proxy applications use proxy endpoint URI instead of external service URI when

invoking external service. For example, if the service endpoint URL is

http://host1:9191/service and the proxy endpoint URL is http://host2:9090/proxy/service/,

the proxy application sends the request to http://host1:9191/proxy/service/

instead of http://host1:9191/service.

SDS-7152

TIBCO Business Studio now allows overriding of substitution variable values in

the generated CLI scripts. To override, enable the generation of <SVar> elements

in the deployment-config.xml file, allowing you to manually change the <SVar> values.

- To enable this from the UI, select the check box 'Generate SVars with

default values' on the 'Property Configuration' screen of the 'Generate Admin

CLI Scripts' wizard.

- To enable this from the CLI, set a new attribute createSVars="true" in the

<sds.generateDeploymentScript> element of the Ant script.

For example:

<sds.generateDeploymentScript daaLoc="C:\Test1\Test12.daa" createSVars="true">

SDS-7208

In an installation with TIBCO Business Studio only, you can now configure a

third-party driver by running the following utility:

configure-third-party-driver -Dshell.name=com.tibco.tpcl.gen.oracle.jdbc

-Dshell.version=11.1.0.112100 -Dsource.jar.folders=/path/to/driver/jars

This utility is located in <TIBCO_HOME>/amx/3.3/bin/.

If you execute the utility without any options, help is displayed. The help lists

the third party driver options available from <TIBCO_HOME> in a tabular format.

SVCP-54

The TIBCO ActiveMatrix Service Performance Manager probe now emits metrics-related data

to SPM for applications that use Virtualization bindings.

SVCP-55

The TIBCO ActiveMatrix Service Performance Manager probe now emits metrics-related data

to SPM for applications that use JMS bindings.

SVCP-74

TIBCO ActiveMatrix life cycle events of Composite reference endpoints are now published

correctly if two or more endpoints shared the same WSDL portType.

TAP-13015

In TIBCO ActiveMatrix Administrator CLI, a new 'edit' action is now supported for

updating existing substitution variables. The 'edit' action has slightly different

behavior than the 'add' action, as follows:

-----------------------------------------------------------

Scenario (a): Substitution variable already exists.

-----------------------------------------------------------

* Action 'add' with overwrite 'false' : Existing Svar is preserved; no changes are made.

* Action 'add' with overwrite 'true' : Existing Svar is updated.

* Action 'edit': Existing Svar is updated.

-----------------------------------------------------------

Scenario (b): Substitution variable does not already exist.

-----------------------------------------------------------

* Action 'add' with overwrite 'false' : A new Svar is added.

* Action 'add' with overwrite 'true' : A new Svar is added.

* Action 'edit': An error is reported and the script fails.

-----------------------------------------------------------

TAP-13016

In TIBCO ActiveMatrix Administrator CLI, when a substitution variable is added using the

'add' action, the objects are now overwritten only when the 'overwrite' flag is set to

true. If the flag is set to false, existing substitution variables are not overwritten.

If the flag is set to true, existing substitution variables get updated to the new type

and value specified in the CLI data.xml file. Note that the 'merge' flag is always ignored

by this action.

TAP-13023

TIBCO ActiveMatrix Administrator now offers an option to disable queuing of actions for

hosts or nodes that are down. When disabled, the actions are asked to fail immediately

(instead of being pending in a queue) when targeted towards hosts or nodes that are down.

For example, you are deploying an application on three nodes, and one of the nodes is down.

The default behavior in TIBCO ActiveMatrix Administrator is to proceed with the deployment

on the two running nodes, while holding back the deployment on the stopped node in an

internal queue. Later, when the node becomes "running", the deployment action for that

node executes automatically (a rough analogy is about print-jobs on a printer machine

that was offline).

Adding the following line in the SystemNode.tra disables the default queuing behavior:

java.property.com.tibco.admin.taskservice.queue.actions=false

Restart the SystemNode after adding the line. Adding the line causes TIBCO ActiveMatrix

Administrator to make actions fail immediately for the nodes that were down. For example,

deploying an application to three nodes, when one of the nodes is down, succeeds

on the running nodes, and fail for the stopped node. The overall deployment action is

reported as a failure, and the application remains 'Out of Sync'. When the node is started

later, you must execute the action again explicitly. In this example, click [Deploy]

again to attempt the deployment on just this node; the other nodes which already have the

application remain unaffected.

TAP-13067

In a TIBCO ActiveMatrix Administrator CLI script, a boolean value (TRUE or FALSE) can

now be set as the value for the <properties> element under <ResourceTemplate> for a

JNDI Connection Configuration resource template. The <properties> element corresponds

to a single property under Shared Objects -> Resource Templates -> JNDI Connection

Configuration -> Advanced -> Application Properties, in the UI.

TAP-13119

This covers an alternate scenario of TAP-13058 that was fixed in 3.3.0 Hotfix 003. In the

following scenario applicable to TIBCO ActiveMatrix BPM user applications, the endpoints

of the old version of your application are no longer prematurely removed:

1. Version 'v1' of your application is deployed.

2. You attempt to upgrade it to version 'v2', but the deployment fails.

3. You force-undeploy 'v2', but while force-undeploy is in progress, you go to the next

step without waiting for the force-undeploy to complete.

4. You switch the current version of your application to 'v1', but do not deploy.

5. You switch the current version of your application to 'v3', and deploy. At this point,

a validation error prevents the deployment. This avoids the issue that caused

endpoints of your old version 'v1' to be prematurely removed.

TAP-13121

The Component Status and Binding Status panels in TIBCO ActiveMatrix Administrator

UI under Application details screen can now be optimized to render faster. To do

this, add the following line to the SystemNode.tra file:

java.property.com.tibco.admin.component.show.actionhistory=false

Restart the SystemNode after adding the line. Adding the line will avoid the

computation to display values in the Action History column for each component or

binding, thus making the view render faster. Instead of the Action History value,

it displays a "view action history" link which can be clicked to see the Action

History details.

WSBT-918

For SOAP/HTTP references you can now provide a complete URL in the SOAP binding

configuration using TIBCO Business Studio or TIBCO ActiveMatrix Administrator.

For example, you can provide http://<host>:<port>/<filespec> as an alternative to

just the filespec or URI (example: /weatherReportPT/).

Providing a complete URL overrides the host and port values defined in the

HTTP client shared resource. This is equivalent to the behavior in TIBCO ActiveMatrix 2.x.

The SOAP binding configuration editor UI has been modified as follows:

- 'Endpoint URI Filespec' field is renamed to 'Filespec or Endpoint URL'.

This field now accepts a complete URL or a URI, for example, http://<host>:<port>/weatherReportPT

or just /weatherReportPT.

Usage of Substitution Variables

You can also pick or enter a substitution variable for the value, for example,

%%MyPartnerEndPoint%%

You can define the value for the substitution variable with a complete URL, for

example, http://<host>:<port>/weatherReportPT.

SSL-enabled SOAP/HTTP Endpoints

You can override the protocol value in the 'Filespec or Endpoint URL' field to 'https://'

to enable SSL. This requires pre-configuration of HTTP Client shared resource to use

SSL Client Provider. Even if SSL is enabled in the HTTP Client shared resource,

the protocol value in that field determines whether SSL is enabled or not.

NOTE:

- It is recommended that in TIBCO Business Studio you pick a substitution variable

instead of entering it manually so that it is packaged correctly in the DAA and

correctly handles the 'Synchronization' state in the Administrator.

WSBT-927

In TIBCO Business Studio, the configuration screen for SOAP/HTTP Binding now allows

picking of substitution variables for the fields 'Connector Name' and 'HTTP Client'

corresponding to a SOAP service binding or a SOAP reference binding.

======================================================================

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_hotfix004 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_hotfix004

Issue/Introduction

TIBCO ActiveMatrix(R) Service Grid 3.3.0 Hotfix, TIB_amx_3.3.0_hotfix004, 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, 3.0.0 - TIBCO Business Studio BPM Edition 3.6.0 - TIBCO ActiveMatrix Policy Director 1.0.1 + Hotfix 001 NOTE: Existing TIBCO ActiveMatrix 3.3.0 customers who have been usingTIBCO ActiveMatrix with TIBCO Service Performance Manager 2.1.0 are affectedby Hotfix 004. After Hotfix 004 is applied to your TIBCO ActiveMatrix 3.3.0installation, it is required that you use TIBCO Service Performance Manager 2.2.0.

Additional Information

TIB_amx_3.3.0-HF-004_readme.txt, tib_amx_3.3.0-HF-004_installation_addendum.pdf

Attachments

TIBCO ActiveMatrix(R) Service Grid 3.3.0 Hotfix, TIB_amx_3.3.0_hotfix004, is now available. get_app

Welcome to "KB Articles"