TIBCO ActiveMatrix Policy Director - docs.tibco.com · TIBCO ActiveMatrix® Policy Director Release...

Two-Second Adv

TIBCO ActiveMatrix® Policy Director

Release NotesSoftware Release 1.0.1April 2013

antage®

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc. TIB, TIBCO, TIBCO Software, TIBCO Adapter, Predictive Business, Information Bus, The Power of Now, BusinessWorks, TIBCO Administrator, TRA, TIBCO Enterprise Message Service, TIBCO Designer, TIBCO ActiveMatrix, TIBCO ActiveMatrix Policy Manager are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.EJB, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countriesAll other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.Copyright © 1999-2013 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiHow to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 1.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 1.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 1.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Deprecated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 1.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 1.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Governance Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

TIBCO ActiveMatrix Policy Director 1.0.1 Release Notes

iv | Contents


v| Preface

Preface

TIBCO ActiveMatrix ® Policy Director enables dynamic governance control-based SOA governance by allowing you to manage and enforce cross-functional requirements such as security, monitoring, and compliance independent of their implementation and deployment.

Through both embedded agents and intermediary proxy applications, TIBCO ActiveMatrix ® Policy Director can enforce a range of policies by inspecting, rejecting, recording, transforming, and redirecting messages.

Topics

• TIBCO Product Documentation, page vi

• Typographical Conventions, page vii

• Connecting with TIBCO Resources, page xi

• How to Contact TIBCO Support, page xi



vi| TIBCO Product Documentation

TIBCO Product Documentation

This section lists the documentation resources you may find useful.

The following documents form the TIBCO ActiveMatrix Policy Director documentation set:

• Concepts: Read this manual before reading any other manual in the documentation set. This manual describes terminology and concepts of the TIBCO ActiveMatrix Policy Director software. The other manuals in the documentation set assume you are familiar with the information in this manual.

• Administration: Read this manual to learn how to manage the runtime and deploy and manage applications.

• Installation and Configuration: Read this manual to learn how to install TIBCO ActiveMatrix Policy Director software and create and upgrade runtime objects.

• Release Notes: Read this manual for a list of new and changed features, steps for migrating from a previous release, and lists of known issues and closed issues for the release.

In addition, the following document provides additional information:

• TIBCO ActiveMatrix Composite Development: Read this manual to learn how to develop and package composites.

Typographical Conventions | vii

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME

ENV_HOME

Many TIBCO products must be installed within the same home directory. This directory is referenced in documentation as TIBCO_HOME. The default value of TIBCO_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco.

Other TIBCO products are installed into an installation environment. Incompatible products and multiple instances of the same product are installed into different installation environments. An environment home directory is referenced in documentation as ENV_HOME. The default value of ENV_HOME depends on the operating system. For example, on Windows systems the default value is C:\tibco.

CONFIG_HOME A TIBCO configuration folder stores configuration data generated by TIBCO products. Configuration data can include sample scripts, session data, configured binaries, logs, and so on. This folder is referenced in documentation as CONFIG_HOME.


viii| Typographical Conventions

code font Code font identifies commands, code examples, file names, path names, and output displayed in a command window. For example:

• Code example:

public class HelloWorldImpl extends AbstractHelloWorldImpl {... public HelloResponseDocument sayHello(HelloRequestDocumentfirstName) {...System.out.println("--> Generating Java Hello ComponentResponse...");String name =firstName.getHelloRequest()==null||firstName.getHelloRequest().equals("")?"Friend":firstName.getHelloRequest();HelloResponseDocument resp =HelloResponseDocument.Factory.newInstance();resp.setHelloResponse("Hi " + name + "! " + "This is the Javacomponent.\n");System.out.println("--> Java Hello Component Response: \n\t\t"+resp.getHelloResponse());...}}

• CONFIG_HOME/admin/enterpriseName/samples/remote_props.properties

• Output example:

C:\Program Files\tibco\amx-3\studio\3.5\eclipse>amx_eclipse_ant.exe-buildfile "C:/helloworld1/build.xml" -data "C:/hws"Buildfile: C:/helloworld1/build.xml

createApplicationDAA:[sds.createDAA] Waited for 47ms for workspace refreshes after building features.

all:BUILD SUCCESSFULBUILD SUCCESSFULTotal time: 2 minutes 18 seconds

Table 1 General Typographical Conventions (Cont’d)

Convention Use


Typographical Conventions | ix

bold code

font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin.

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO ActiveMatrix BusinessWorks Concepts.

• To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommand PathName

Key combinations

Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d)

Convention Use


x| Typographical Conventions

Table 2 Syntax Typographical Conventions

Convention Use

[ ] An optional item in a command or code syntax.

For example:

MyCommand [optional_parameter] required_parameter

| A logical OR that separates multiple items of which only one may be chosen.

For example, you can select only one of the following parameters:

MyCommand para1 | param2 | param3

{ } A logical group of items in a command. Other syntax notations may appear within each logical group.

For example, the following command requires two parameters, which can be either the pair param1 and param2, or the pair param3 and param4.

MyCommand {param1 param2} | {param3 param4}

In the next example, the command requires two parameters. The first parameter can be either param1 or param2 and the second can be either param3 or param4:

MyCommand {param1 | param2} {param3 | param4}

In the next example, the command can accept either two or three parameters. The first parameter must be param1. You can optionally include param2 as the second parameter. And the last parameter is either param3 or param4.

MyCommand param1 [param2] {param3 | param4}


Connecting with TIBCO Resources | xi

Connecting with TIBCO Resources

How to Join TIBCOmmunityTIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts, a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to http://www.tibcommunity.com.

How to Access All TIBCO DocumentationYou can access TIBCO documentation here:

http://docs.tibco.com

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, please contact TIBCO Support as follows.

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

http://www.tibco.com/services/support

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a user name, you can request one.


http://docs.tibco.com

http://www.tibco.com/services/support


http://www.tibcommunity.com

xii| Connecting with TIBCO Resources


1|Release Notes

Release Notes

Check the TIBCO Product Support web site at https://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request for one. You must have a valid maintenance or support contract to use this site.

Topics

• New Features, page 2

• Changes in Functionality, page 4

• Deprecated Features, page 5

• Migration and Compatibility, page 6

• Closed Issues, page 7

• Known Issues, page 10

• Troubleshooting, page 19



2 | New Features

New Features

This section lists the features added in this release of the product.

Release 1.0.1 The following are the new features in this release:

• Command-line support for governance controls, object groups, and proxy service management.

• This release supports TIBCO ActiveMatrix Updater Tool for Java Runtime Environment (JRE), a command-line utility for updating existing TIBCO ActiveMatrix based installations to use JRE 1.7. The Updater tool will be bundled with the service pack. However, the tool will not be embedded within the installer.

Release 1.0.0 The following are the new features in this release:

• Unified service-oriented architecture (SOA) governance across TIBCO ActiveMatrix Policy Director and the ActiveMatrix platform

• Support of services outside of the ActiveMatrix platform, including TIBCO ActiveMatrix BusinessWorks

• Proxy applications that can enforce policies on behalf of consumers or providers

• Governance controls that can be applied to all applications and to occur anywhere during processing

• Dynamic management and distribution of policies

• Full command-line interface support

• Apply policies to named groups of governed elements or selection criteria

• Support for the following policies:

Kerberos Authentication Policy

TIBCO ActiveMatrix Updater Tool for Java Runtime Environment (JRE) does not support the following platforms: IBM AIX 53 32 -bit, IBM AIX 53 64 -bit, HP UX 32 -bit , and HP UX64 -bit.


New Features | 3

WS-Addressing for Reference

WS-Addressing for Service

WS-Reliable Messaging


4 | Changes in Functionality

Changes in Functionality

This section lists the changes in functionality since the last major (1.0.0) release of this product.

Release 1.0.1There are no changes in functionality in this release.


Deprecated Features | 5

Deprecated Features

This section describes deprecated features and lists equivalent features that accomplish the same result, if relevant. Any use of a deprecated feature should be discontinued as it may be removed in a future release. Avoid becoming dependent on deprecated features and become familiar with the equivalent feature.

Release 1.0.1None


6 | Migration and Compatibility

Migration and Compatibility

This section explains how to migrate from a previous release to this release.

Release 1.0.1• There are no migration and compatibility steps in this release. To upgrade to

ActiveMatrix Policy Director 1.0.1, refer to the Upgrading to TIBCO ActiveMatrix Policy Director 1.0.0 Service Pack -001 section of the TIBCO ActiveMatrix Policy Director 1.0.1 Installation and Configuration guide.


Closed Issues | 7

Closed Issues

The table in this section list the issues that were closed in the named releases.

Reference # and Release Summary

Issues Closed in Release 1.0.1

PD-2433 TIBCO ActiveMatrix Policy Director did not support EMS over SSL for communication between the Distribution Engine and the Governance Agent for TIBCO ActiveMatrix BusinessWorks. This issue will now be resolved by performing the following steps:

1. Use TIBCO Configuration Tool to configure the parameters for EMS over SSL parameters for Distribution Engine and the Governance Agent for TIBCO ActiveMatrix BusinessWorks.

2. Update the ActiveMatrix BusinessWorks Engine TRA file to include the following java property:java.property.TIBCO_SECURITY_VENDOR=j2se.

PD-2853 The SSL setup for the EMS configuration of the Governance Agent for TIBCO ActiveMatrix BusinessWorks no longer offers PKCS12 for the trust store. PKCS12 is used to store private keys and not certificates.

PD-2027 While querying logs, the ViewLog utility for the Logging governance control did not support HTTP over SSL. The ViewLog utility did not work when TIBCO ActiveMatrix Administrator was configured to only use HTTP over SSL.

PD-2024 The Log service and Payload service of the Logging Policy did not support EMS over SSL. Only EMS over TCP was supported.

PD-2308 When the TIBCO Configuration Tool was used on Solaris Sparc, there was no option to specify the TIBCO configuration folder for Console Mode.

GWS-460 Proxy applications were not created if the registered WSDL file had WSDL or schema imports with http URLs.

GWS-462 While creating the proxy application, the application timed out with the following message: “Read Connection Time Out for many of the Services."

PD-2331 In the WSS Provider Policy, the Encrypt Response did not work when using the client certificate.

PD-3265 While specifying a governance control, the Authorization governance control did not allow commas in the name.


8 | Closed Issues

PD-3353 When Credential Mapping for Username Token Authentication was applied on an ActiveMatrix node, the application did not generate the WSS elements, <wss:Nonce> and <wss:Created>.

PD-2892 While using an existing database, when a logging governance control and a username token governance control was applied on a governance agent for ActiveMatrix BusinessWorks, the application was unable to fetch data related to the logging governance control.

PD-2180 When created using the UI, governance control creation failed if the service names had a hyphen in their end point address.

PD-1958 When a governance control was deployed using the command-line interface (CLI), Basic Credential Mapping failed on the ActiveMatrix domain.

PD-2707 The WSS Consumer governance control CLI incorrectly picked the default encryption algorithms.

PD-2645 Policy enforcement failed when a proxy application, on which a governance control was being enforced, was redeployed on multiple nodes.

PD-2648 When Policy Director was configured using the TIBCO Configuration Tool, the TIBCOHOST configuration folder was incorrectly displayed as an editable field containing config.home as the default value.

PD-2666 On an ActiveMatrix 3.2 server, ActiveMatrix Policy Director installation failed when it was configured with a non-default enterprise and instanceName.

PD-2602 When ActiveMatrix Policy Director was installed on an ActiveMatrix 3.2 server, TIBCO Configuration Tool did not provide an option to configure JNDI Connection Resource. The connection Resource helped communicate with the Governance Agent for TIBCO ActiveMatrix BusinessWorks.

PD-2722 Registering an external WSDL was unresponsive when the file size was over 1 MB.

GWS-371 ActiveMatrix Policy Director was unable to create proxy applications when WSDLs contained header declarations.

PD-2503 When TIBCO ActiveMatrix Policy Director Administration Server was created using the TIBCO Configuration Tool, the string,'[null' for null was uninformative in the option - Create a TIBCO ActiveMatrix Policy Director Administrator Server.



Closed Issues | 9

PD-3425 The Authorization governance control did not support role names with special characters.

PD-2571 When a Governance Control had an unfulfilled Shared Resource dependency with the Governed Objects in a Deployable state, no corresponding error message was displayed to the user.



10 | Known Issues

Known Issues

The tables in this section list the known issues in this release.

Installer

Key Summary/Workaround

AMX-11747 Summary To ensure that management binding works effectively, the following additional permissions are required for non-Admin users:

create topic AMX_MGMT.>grant topic AMX_MGMT.> user=<username> create, modify, subscribe, publishcreate queue AMX_MGMT.>grant queue AMX_MGMT.> user=<username> create, modify, send, receive

Workaround The EMS users should be granted the following privileges on queues and topics:

Topics: Create, Modify, Subscribe, and Publish.

Queues: Create, Modify, Send, and Receive.

PD-3411 Summary When you click Next and subsequently click Back in the installer, the TIBCO ActiveMatrix Hotfix 4 is wrongly displayed as one of the options.

Workaround Kill the installer instance, and relaunch the installer.


Known Issues | 11

Governance Control


MED-2984 Summary Retrieval of concrete WSDLs for proxy services does not work if the proxy services are built for services with WSDL definitions that have external schema dependencies.

Workaround To generate a concrete WSDL for proxy services, do the following:

1. Generate the WSDL using the proxy service binding configuration in TIBCO Administrator.

2. Change endpoint host from 0.0.0.0 either to the IP address of the machine the proxy service runs on, or to its host name.

GWS-381 Summary TIBCO ActiveMatrix Policy Director does not support SOAP with attachments.

Workaround None.

PD-2883 Summary In the AIX platform, the wrap command fails with the following error: "A file or directory name in the path name does not exist."

Workaround In PDBWPlugin.tra, update the tibco.env.JVM_LIB_DIR to point to PPC64.

PD-3354 Summary TIBCO ActiveMatrix Policy Director does not support EMS over SSL using JNDI configuration for communication between the Distribution Engine and the Governance Agent for TIBCO ActiveMatrix BusinessWorks. Only direct connection using EMS over SSL URL is supported.

Workaround Specify the following EMS over SSL URL:ssl://<IP_Address>:<SSL_Port_Number>/

PD-3268 Summary While configuring keystores for ActiveMatrix BusinessWorks domains, keystores do not support URL specifications with EMS over TCP or SSL.

Workaround Governance controls using keystore provider should be hosted externally using HTTP URL.

PD-3242 Summary Updates made to the Keystore Shared Resource Template are not send to the governance agent for ActiveMatrix BusinessWorks.

Workaround Create a new Keystore Shared Resource Template with the appropriate configurations, and redeploy the governance control.


12 | Known Issues

PD-3197 Summary When the associated JNDI resource instance was changed, the components of the application took a longer time to start.

Workaround Perform the following steps as a workaround:

1. When prompted to install resource instances, click Cancel.

2. Manually reinstall the resource instances.

3. Stop and restart the com.tibco.ampd.ogp.de application.

PD-2445 Summary In the TCT console mode, when you configure EMS SSL server, the summary displays all the properties of the EMS server correctly, but shows that the EMS Server was not selected.

Workaround None. This message will be ignored since this issue has no functional impact.



Known Issues | 13

PD-3137 Summary When using the ActiveMatrix BusinessWorks domain, the logging governance control does not work with EMS over SSL.

Workaround Perform the following steps:

1. If the EMS user has administrative privileges, do not grant any additional permissions.

2. If EMS user does not have administrative privileges:

a. Create the logging policy queue.

b. Grant send, receive, and create privileges to the following queues:

JNDI Name [policy_logservice_queue], Queue Name

policy_logservice_queue

JNDI Name [policy_payload_queue] Queue Name

policy_payloadservice_queue

3. Open log4j.xml file from $BW_HOME/bw/plugins/governanceagent/config/.

4. Add the following parameter to the Appenders element:

<param name="emsProperties"

value="$BW_HOME/bw/plugins/governanceagent/config/jmsconfi

g.properties"/>

5. Open jmsconfig.properties from $BW_HOME/bw/plugins/governanceagent/config/.

6. Add the following parameters:

com.tibco.tibjms.ssl.trusted_certs=$certs_location/server_

root.cert.pem (This is the trustkeystore file used while configuring EMS on SSL. This file should be in the same machine as the Governance Agent for ActiveMatrix BusinessWorks.)

com.tibco.tibjms.ssl.identity=$certs_location/client_ident

ity.p12 (This is the trustkeystore file used while configuring EMS on SSL. This file should be present in the same machine as the Governance Agent for ActiveMatrix BusinessWorks.)

com.tibco.tibjms.ssl.password=$password

com.tibco.tibjms.ssl.vendor=j2se ( Not required if TRA is 5.8 and above, EMS 6.3.0 and above)

com.tibco.tibjms.ssl.enable_verify_host=false

com.tibco.tibjms.ssl.expected_hostname=$server.



14 | Known Issues

PD-3124 Summary TCT fails when EMS is configured with non default Connection Factory names in the factories.conf file.

Workaround Change the configurations related to QueueConnectionFactory and GenericConnectionFactory in the following files under <TIBCO_CONFIG_HOME>\tct\pd\<TIME_STAMP>\scripts\templates:

With references to GenericConnectionFactory:

cl_logservice_data.xml.xsl cl_payloadservice_data.xml.xsl

With references to QueueConnectionFactory:

governance_integration_data.xml.xsl governance_ogp_config_data.xml.xsl

governance_pd_proxy_node_data.xml.xsl



Known Issues | 15

PD-3228 Summary The application is unable to create the ActiveMatrix Policy Director Administrator over HTTPS for AIX platform.

Workaround Perform the following steps as a workaround:

1. Setup an environment with SSL.

2. Open the script, edit-httpconnector-data.xml under TIBCO-HOME/administrator/3.2/scripts.

3. Modify TibcoHostConfig node.

4. Under ConnectionDetails node, add the following:

<SSLConfig>

<KeyStoreResource xsi:type="amxdata_bootstrap:KeystoreCspResource"

name="SslKeyStoreRT"

keyStoreLocation="/tibco/bw/Downloads/aip_https_server.p12"

keyStorePassword="password" keyStoreType="PKCS12"

keyStoreRefreshInterval="1000" />

<SSLServerResource xsi:type="amxdata_bootstrap:SslServerResource"

name="SslServerRT" description="This is SSL Server RT">

<GeneralConfiguration

xsi:type="amxdata_bootstrap:SslServerResource_General"

identityStoreServiceProvider="tibco.admin.default.ssl.keystore"

keyAlias="aip_https_server" keyPassword="password"

enableCredentialStoreAccess="true">

</GeneralConfiguration>

<AdvancedConfiguration securityProtocolToUseForSSL="SSL">

<VerifyHost/>

</AdvancedConfiguration>

</SSLServerResource>

</SSLConfig>

5. Modify the keyStoreLocation to point to the location of the server key file.



16 | Known Issues

6. Add the following line to edit-admin-server-config-build.xml:<property name="th.hpa.client.props" value="${th.inst.dir}/host/th/hpaclientcli.properties" />

7. In the following line, add data_3.2.x before \host\:<admin-conf>\admin1\tibcohost\Admin-amxadmin-instanceOne\data_3.2.x\host\th

8. Run the following ant command:/tibco/bw/apache-ant-1.8.2/bin/ant -f edit-admin-server-config-build.xml -Dadmin.server.dir=/tibco/bw/pd-admin/admin1/admin/amxadmin/private/instanceOne

9. Change admin.server.dir to point to the location of the admin configuration folder.

10. Wait for a few minutes for the SystemNode to complete restarting.

If you have more than one network interface, change the following line in dit-httpconnector-data.xml:<ConnectorDetails port="8120" host="localhost">Change localhost ----> 0.0.0.0

Run the script again after making the changes.

PD-3136 Summary WS-Addressing and WS-Reliable Messaging policies do not take effect when the policies are deployed for an object group.

Workaround The associated application has to be undeployed and deployed again for the policies to take effect.

PD-2997 Summary The WssProvider governance control is not enforced if there is a space in the name of the Keystore shared resource field.

Workaround Do not insert a space in the name of the field.

GWS-382 Summary TIBCO ActiveMatrix Policy Director Proxy agent does not support RPC-based encoding styles.

Workaround None.

PD-2167 Summary TIBCO ActiveMatrix Policy Director Governance Agent for TIBCO ActiveMatrix BusinessWorks does not support services built using the SOAP Event Source palette.

Workaround None.



Known Issues | 17

PD-2168 Summary When an Invoke Partner call is made from a sub process instead of directly from the process, the security context does not get propagated.

Workaround Call Invoke Partner directly through a process instead of a subprocess.

PD-2162 Summary TIBCO ActiveMatrix Policy Director Governance Agent for TIBCO ActiveMatrix BusinessWorks does not support the following governance controls: Basic Authentication and Basic Credential Mapping.

Workaround None.

GWS-404 Summary When changes are made to a configuration using the Proxy Application screen, the proxy application is not shown as "out-of-sync" in the Application screen or vice versa, until the application is deployed.

Workaround None.

PD-2564 Summary When you uninstall TIBCO ActiveMatrix Policy Director Governance Agent for TIBCO ActiveMatrix BusinessWorks, files installed by the TIBCO Configuration Tool under BW_HOME\bw\plugins\governanceagent do not get deleted.

Workaround Manually delete files under BW_HOME\bw\plugins\governanceagent.

PD-2516 Summary When the node on which a proxy application is deployed gets deleted, the proxy application displays a Lost Contact status. As a result, the Proxy Application UI does not respond to a management action, such as, Delete or Undeploy.

Workaround Manage the Proxy Application from the Applications screen instead of the Proxy Applications screen.

PD-2557 Summary While configuring TIBCO ActiveMatrix Policy Director, a Null Pointer exception is thrown if you do the following, using the TIBCO Configuration Tool:

• Clear the option, Use TIBCO ActiveMatrix Administrator Notification and Messaging Bus Server on the screen, Administrator Server Configuration: Governance Agent for BW Notification Server.

• Clear the option, Use TIBCO ActiveMatrix Administrator Notification and Messaging Bus Server on the screen, Administrator Server Configuration: Monitoring Notification Server.

Workaround Select the option, Use TIBCO ActiveMatrix Administrator Notification and Messaging Bus Server, on both the screens.



18 | Known Issues

PD-2017 Summary The Governance Agent for TIBCO ActiveMatrix BusinessWorks does not support Message Transmission Optimization Mechanism (MTOM).

Workaround None.

PD-2570 Summary When an existing Administrator is selected to deploy TIBCO ActiveMatrix Policy Director, the TIBCO ActiveMatrix BusinessWorksTM

Service Engine application does not get deployed on the TIBCO ActiveMatrix Policy Director Administrator server.

Workaround After running the TIBCO Configuration tool, deploy the TIBCO ActiveMatrix BusinessWorks Service Engine application manually.



Troubleshooting | 19

Troubleshooting

Troubleshooting may be necessary to clean up data for system nodes and governance agents.

Perform a clean up of the TIBCO ActiveMatrix Policy Director system nodes and governance agents.

Cleaning Up TIBCO ActiveMatrix Policy Director

1. Save your governance control drafts.

a. In ActiveMatrix Administrator UI, select Governance > Governance Controls.

b. For each governance control you have created or deployed, save a draft.Your configurations are saved so that you do not have to recreate them later.

2. Make a note of the required IDs.

a. Open the link to the governance data in your browser.The URL is based on the ActiveMatrix Administrator URL. For example:http://localhost:8120/ogp/viewogpdata.jsp

b. Click ViewGovControlPackage.

c. Click StandaloneRule.

d. Find and record the IDs for all rows with the value true in the Deployed column.You will use these IDs in Step 5.

3. Identify the system node process.Find the process ID for the system node process tibamx_SystemNode.

• Windows: Use Task Manager.

• Linux: Use ps -ef in a terminal window.

4. Launch JConsole.

a. Find and run the jconsole executable in JDK_Home/bin, where JDK_HOME is the directory where Java Development Kit (JDK) is installed.

— If JDK_HOME directory is in your system path, type jconsole in a command (shell) prompt.

— If JDK_HOME directory is not in your system path, type the full path name to the jconsole executable file.


20 | Troubleshooting

When JConsole launches, you can view the list of Java processing that are running.

b. Connect to the process ID for the system node.

5. Perform a reset. On your JConsole screen, do the following:

a. Click on the MBeans tab.

b. Expand the com.tibco.governance.ogp.de folder.

c. Expand AMXServiceProxy.Three operations display. You need to use the forceUndeploy and forceCleanup operations.

d. For each ID in Step 2:

— Select the forceUndeploy operation, put the ID in the Input box, and click the forceUndeploy button.

— Select the forceCleanup operation, put the ID in the Input box, and click the forceCleanup button.

Completing these steps removes each governance control from TIBCO ActiveMatrix Policy Director and leaves a saved draft of each control for later use.

Cleaning up Governance Agents

1. Stop the Node.

2. Use Browse to go to the ActiveMatrix installation folder for the Node with deployed user applications that has the policies you created.For example, if $tibcoInstall is the installation folder, go to $tibcoInstall/config.home/tibcohost/Admin-amxadmin-instanceOne/data_3.2.x/nodes/DevNode/work/cf

3. Search for a folder named GovernanceAgentRuntimeDB.

4. Delete or rename this folder.

5. Start the Node.

The agent creates a clean database.

You can browse to the Governance Control screen in ActiveMatrix Administrator and redeploy your governance controls.

JConsole in not bundled with TIBCO JRE. If you need to install TIBCO JRE, ensure that you have installed JDK installed on your machine.


TIBCO ActiveMatrix Policy Director - docs.tibco.com · TIBCO ActiveMatrix® Policy Director Release...

Documents

Transcript of TIBCO ActiveMatrix Policy Director - docs.tibco.com · TIBCO ActiveMatrix® Policy Director Release...