TIBCO ActiveMatrix Service Gateway ®

TIBCO ActiveMatrix

®

Service

Gateway

Release Notes

Software Release 1.2.0

August 2012

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.

TIBCO, The Power of Now, TIBCO BusinessEvents, TIBCO ActiveMatrix, TIBCO ActiveMatrix BusinessWorks,

TIBCO Administrator, TIBCO ActiveSpaces, TIBCO Designer, TIBCO Enterprise Message Service, TIBCO Hawk,

TIBCO Runtime Agent, TIBCO Rendezvous, are either registered trademarks or trademarks of TIBCO Software

Inc. in the United States and/or other countries. EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

All 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 © 2012 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

Contents

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

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

How to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

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

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Release 1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Release 1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Release 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

TIBCO ActiveMatrix Service Gateway Operational Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Module for Apache HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Core Engine Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Gateway Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Operational Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Release 1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Release 1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Release 1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Release 1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Release 1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Release 1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

| iii

TIBCO ActiveMatrix Service Gateway Release Notes

iv | Contents


Preface

TIBCO ActiveMatrix Service Gateway enables dynamic policy-based partner-centric governance of SOA systems by federating heterogeneous services and regulating access by external consumers and organizations. Through a high performance event server the

Service Gateway manages and enforces policies such as security, throttling, quotas, transformation and monitoring independent of service implementation and lifecycle.

With the separate purchase of Spotfire users can analyze service usage, subscriber behavior and performance.

| v

Topics

•

Typographical Conventions, page vi

•

Connecting with TIBCO Resources, page ix


vi | Typographical Conventions

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention

TIBCO_HOME

ENV_NAME

ASG_HOME

ASG_CONFIG_

HOME

Use

Many TIBCO products are installed within the same home directory. TIBCO

ActiveMatrix Service Gateway software requires TIBCO Rendezvous to be installed in the same home directory location. This directory is referenced in documentation as TIBCO_HOME.

Other TIBCO products are installed into an installation environment. Products installed into different installation environments do not share components.

Incompatible products and multiple instances of the same product must be installed into different installation environments. An installation environment consists of the following properties:

• Name: Identifies the installation environment. This directory is referenced in documentation as ENV_NAME.

• Path: The directory into which the product is installed. This directory is referenced in documentation as TIBCO_HOME. The value of TIBCO_HOME depends on the operating system.

TIBCO ActiveMatrix Service Gateway installs into a directory within

TIBCO_HOME . This directory is referenced in documentation as ASG_HOME. For example on Linux

®

platform, the value of ASG_HOME might be

/home/asg/tibcoasg/asg/1.2

TIBCO ActiveMatrix Service Gateway stores the configuration files in a directory which is seperate from the installation directory. This directory is referenced in documentation as ASG_CONFIG_HOME. For example on Linux

®

platform, the value of ASG_CONFIG_HOME might be

/home/asg/tibcoasgconfig/tibco/cfgmgmt/asg.

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use MyCommand to start the foo process.


Preface | vii

Table 1 General Typographical Conventions (Cont’d)

Convention bold code font

Use

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

Key combinations

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


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

| logical

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}


Preface | ix

Connecting with TIBCO Resources

How to Join TIBCOmmunity

TIBCOmmunity 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 Documentation

You can access TIBCO documentation here: http://docs.tibco.com

How to Contact TIBCO Support

For 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.


x | Connecting with TIBCO Resources


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 one. You must have a valid maintenance or support contract to use this site.

| 1

Topics

•

New Features, page 2

•

Changes in Functionality, page 13

•

Deprecated and Removed Features, page 14

•

Migration and Compatibility, page 15

•

Closed Issues, page 18

•

Known Issues, page 19


2 | Release Notes

New Features

This section lists the new features of the product for each release.

Release 1.2

In this release, the following functionality has been introduced:

New Platforms and Third Party Software Support

Support for the following platforms and third party software has been added in this release. See the product readme at TIBCO_HOME/release_notes for supported versions.

Operating Systems

• Microsoft Windows Server 2008 R2 (64 bit installer)

• Microsoft Windows 7 (32 bit and 64 bit installers)

• Oracle Solaris 10 SPARC (64-bit installer)

Third Party Software

• Microsoft SQL Server 2008 R2

• Microsoft Active Directory 2008 R2

• Microsoft Internet Explorer 8.0, 9.0

Dynamic JMS Destinations

Users can configure JMS destinations for southbound backend services. JMS queue and topic names are declared through the user interface. This functionality allows the users to override the default JMS destinations for the southbound services. See TIBCO ActiveMatrix Service Gateway User’s Guide for more information.

Service Retry

The retry mechanism for the southbound requests sent over http/http(s) transports allows resending of the request message to the backend service upon network failure. Users can configure the number of retries, retry interval and retry timeout for a http(s) service using the user interface.


New Features | 3

User Interface Enhancements

The user interface has been enhanced to support:

• More easily managed large configuration sets with new toolbar, Expand and

Collapse functions on each record.

• Configuration of service groups for load balancing.

• A new icon ’P’ to edit the engine property file ( asg.properties

).

• Configuration of asynchronous mode for southbound JMS service.

• Configuration of retry timeout parameters for http(s) transport.

• Configuration of WSS property files for https transport.

• No Authentication required flag for https transport.

• Configuration of destinations for southbound JMS services.

• Improved Error validation.

Binary Attachments

Binary payload attachments are supported in addition to the text attachments.

Asynchronous Support for Southbound JMS Channel

Southbound JMS requests can be sent to the backend service in asynchronous mode or synchronous mode.

SOAP Messages Support for JMS Transport

SOAP messages over JMS transport are supported for both northbound and southbound sides.

Documentation

In addition to PDF documentation, the HTML documentation is provided. See

ASG_HOME /doc/html/index.htm.

Release 1.1

In this release, the following functionality has been introduced:


4 | Release Notes

Installation and Packaging

Separation of software program files and configuration data

The Installer allows you to input a configuration folder which stores all the configuration files at one place making it seperate from the software installation files. This promotes to have one single product installation directory with multiple configurations (for example, one for test environment, another one for production environment).

User Interface

A new graphical user interface for configuration of operations, services, mappings, throttles, schemas, partner data, partner groups, partner operations, web services security, keystores, and errormaps has been introduced in this release. See TIBCO ActiveMatrix Service Gateway User’s Guide for details.

TIBCO ActiveMatrix Service Gateway Studio

TIBCO ActiveMatrix Service Gateway Studio provides a design time environment for adding custom extensions to a project. It is an Eclipse-based user interface, which is used to build, maintain, configure and modify deployments for the project. It is integrated into the standard Eclipse menus wherever appropriate, and works with many established Eclipse UI methodologies and plug-ins.

Design and Develop Custom Extensions

TIBCO ActiveMatrix Service Gateway Studio allows users to customize the default engine behavior by modifying the Default Implementation project. Using this functionality, users can develop their own extensions and integrate the custom extensions with the core functionality of the gateway engine.

Caching

Association Caches

TIBCO ActiveMatrix Service Gateway provides a mechanism to cache the previous acquired information and uses that information later to optimize the time taken for routing.

TIBCO ActiveMatrix Service Gateway uses the cache agents to store and serve cache data for all the objects of TIBCO ActiveMatrix Service Gateway cluster. The cache agents participate in distribution, partitioning, and storage of the objects in the cluster.



Cache Clearing Manager

TIBCO ActiveMatrix Service Gateway Cache Clearing Manager provides mechanism to clear the cache. The Cache Clearing Manager manages the eviction of entries in the association cache, especially for the entries that are not often referenced.

Extension Mechanism

Extension mechanism allows you to add custom code in the TIBCO ActiveMatrix

Service Gateway Studio using the rules language. This functionality provides the capability to add the new stages to the default transaction processing pipeline.

Following features have been implemented using the extension mechanism:

Field Translation

TIBCO ActiveMatrix Service Gateway allows the look ups of the fields from the external systems for data enrichments and cross referencing, which can use the association caching functionality for faster processing of requests.

Content Based Authorization Policy

This functionality allows you to authorize the partner identities or the customer references of the requestor. The references are sent by the requestor in the content of the request message, which are then identified against LDAP system using a set of LDAP catalog functions.

Response Cache

Response cache is implemented using association caches to store the responses of requests and uses these responses for later requests. Using this functionality,

TIBCO ActiveMatrix Service Gateway supports :

— Faster processing of requests.

— Offloading of service endpoints.

Sequential Orchestration

TIBCO ActiveMatrix Service Gateway supports light weight sequential orchestration. Sequential orchestration allows you to access multiple service endpoints by making a number of sequential calls to fulfill or authorize a request.


6 | Release Notes

Security

Support for SSL Authentication

TIBCO ActiveMatrix Service Gateway supports:

— Mutual authentication

WS Security Authentication

TIBCO ActiveMatrix Service Gateway supports the web services security authentication as follows:

— Authentication of northbound requests with the username token

— SAML based authentication of northbound requests

— X.509 based signature of northbound requests

— Process the signature and encryption of northbound requests

— Sign and encrypt elements, as specified, in the northbound response

Mapping Cababilities

Mapping of Transport Headers (Outbound and Inbound)

For any request and response message, the full access to the request context is available to the mapper, which provides you the option to:

— Map the transport level header fields and pass it through to the next stage in the processing pipeline

— Set the protocol level properties. For example, setting the JMS priority field in the protocol header.

Enumeration Orchestration

TIBCO ActiveMatrix Service Gateway supports enumeration or parallel orchestration, a technique useful for requests with the repeating fields. This functionality is supported using the mapping cabability.



Validation of Requests With Error Code

For any request message, if the responseType is set as Full for mapper registration, this functionality allows you to validate the message content using

Xpath and update the request context with an appropriate error code. The transaction completes with error processing path in the request processing pipeline and returns the error message to the requestor.

Routing

Transport/Protocol bridging between SOAP versions and XML/REST

The gateway engine is capable of bridging the messages between various standard protocol formats supported on the northbound and southbound side.

On the northbound (client) side, the gateway supports SOAP/HTTP, XML/HTTP,

REST/HTTP, and XML/JMS message formats.

On the southbound (back end services) side, the gateway can invoke services over

SOAP/HTTP, XML/HTTP, REST/HTTP, and XML/JMS.

For example, the common bridging cases, as follows are supported:

— REST/HTTP requests bridged to SOAP/HTTP

— SOAP/HTTP requests bridged to XML/JMS

Custom Routing

This functionality allows you to overwrite the routing key in mapping. The genaration of routing key based on the request content and context is supported.

Audit log and Reporting

— Error logging policy for security faults

— Statistics aggregation (KPI generation)

Operational Features

• Load balancing across:

— multiple gateway engines

— mutiple back end service endpoints

• Fault Tolerance

• Hot deployment of new configuration changes:


8 | Release Notes

TIBCO ActiveMatrix Service Gateway allows you to reload the project configuration changes without having to shut down the gateway engine.

Monitoring and Management Server

The Monitoring and Management Server is the central management component that enables you to monitor the status of TIBCO ActiveMatrix Service Gateway cluster. It also allows you to manage the operational tasks of TIBCO ActiveMatrix

Service Gateway cluster.

Release 1.0

The following are the new features in this release.

TIBCO ActiveMatrix Service Gateway Operational Features

This section explains the gateway operational features.

Module for Apache HTTP Server

TIBCO ActiveMatrix Service Gateway uses Apache HTTP web server to terminate the http(s) transport. The module for Apache web server communicates with the

TIBCO ActiveMatrix Service Gateway server to pass the consumer requests and partner responses.

Core Engine Features

Event Based Service Request Routing Engine

TIBCO ActiveMatrix Service Gateway is a high-performance event-based service-request routing engine. It treats requests and responses as events and implements the logic of a gateway layer using simple event-condition-action rules.

Routing Capabilities

TIBCO ActiveMatrix Service Gateway uses a staged event-driven architecture in its router component.



The router component of the TIBCO ActiveMatrix Service Gateway receives request as events and uses the rules engine to determine where requests are handled. The router implements rule logic to select the service handler. The selection of the service handler depends on the parameters, such as, service endpoint location, version, load, message content, operation and so on.

Transport Bridging between HTTP and JMS

This functionality allows you to route the http tranport northbound operation and southbound JMS operation.

Secure Multi-protocol and Multi-transport Support

TIBCO ActiveMatrix Service Gateway supports multiple protocols (HTTP or JMS,

HTTPS or JMS SSL) for service abstraction. This allows the gateway to integrate with multiple web services over various transports such as HTTP(S), JMS, and

REST or SOAP at the backend.

Authentication and Authorization Support

TIBCO ActiveMatrix Service Gateway requires positive identification of requestors. This functionality allows requestors to access the service interfaces in a secure fashion. Authorization rules determine whose requests are handled, and provides:

• Access control granularity down to service endpoint

• Single-edit configuration changes

TIBCO ActiveMatrix Service Gateway provides multiple authentication and authorization mechanisms, including:

— HTTP Basic and Digest Authentication

— Public Key Authentication

— Access policies based on consumer and partner certificate configuration

Throttle and Throttle Chain Capabilities

Throttling models determine whether the requests are handled or they are rejected. Throttles have a type and a metric against which some condition is checked.

TIBCO ActiveMatrix Service Gateway supports following throttle types:

• Rate

• High-Water Mark


10 | Release Notes

• Quota

• Error

• Group Logical

Example of metrics associated with throttle type include:

— Partner

— Operation

— Service

— Time-of-day

Throttle Chain Support

TIBCO ActiveMatrix Service Gateway allows you to assemble throttles into a throttle chain.

Mapping and Transformation Capabilities

TIBCO ActiveMatrix Service Gateway provides message transformations using mappings. The transformations allows you to:

— Add semantic content validation rules to the incoming requests

— Access the multiple versions and formats of service APIs

— Access the fields from the request context and payload

— Protect the service end-points using service validation policies

TIBCO ActiveMatrix Service Gateway supports the transformations of both request and response messages using:

• Forward mapping - The transformations are done from request canonical form to backend service API as per defined mapping.

• Reverse mapping - The transformations are done from backend service API to response canonical form as per defined mapping.

Policy Based Gateway

TIBCO ActiveMatrix Service Gateway supports policies including logging, throttling, quotas, routing, authentication, authorization and transformation.

TIBCO ActiveMatrix Service Gateway allows you to apply policies by service/operation, by partner/partner group, by message content and so on.

Policies can be fully extended through business rules.

TIBCO ActiveMatrix Service Gateway allows you to change policies with respect


New Features | 11 to access, quotas, service level agreements independent of service implementation.

Ping Operation Support

TIBCO ActiveMatrix Service Gateway can be configured to provide an implicit ping operation for each service.

The sample configuration contains an overall ping service for the gateway.

Gateway Management

TIBCO ActiveMatrix Service Gateway contains the following management components:

Central Logger

The TIBCO ActiveMatrix Service Gateway provides centralized logging via the

Central Logger component.

Global Throttle Manager

The Global Throttle Manager component maintains the state of all global throttles in both Façades (Façade Throttles) and Routers (Service Throttles). The Global

Throttle Manager exchanges the states of global throttles with active Façade

Throttle Managers and Service Throttle Managers.

Reporting Capabilities

TIBCO ActiveMatrix Service Gateway is capable of generating reports based on the data from the Central Logger component. The central logger database contains the transaction level data and the key performance indicators for each transaction.

TIBCO Spotfire Integration

TIBCO ActiveMatrix Service Gateway provides a sample TIBCO Spotfire analysis based on data captured by the Central Logger component. The sample shows the following metrics:

• Transaction rate per partner and service

• Throttle violation, Service quality, and Service timeouts failures


12 | Release Notes

• Load Visualization for operations and management

— Volume

— Latency

— Peaks

• Defect detection

• System Usage

Operational Features

Gateway Scalability

TIBCO ActiveMatrix Service Gateway is capable of managing large transaction volumes without any large specialized hardware.

As the rate of transactions to be processed by the gateway increases, it can rapidly scaled up and down through the addition or removal of additional gateway server instances.

TIBCO ActiveMatrix Service Gateway architecture has been designed so that when multiple gateway server instances are deployed, key management functions including throttle management and logging are co-ordinated across servers.

TIBCO ActiveMatrix Service Gateway uses a “shared nothing” model between the active gateway server instances to ensure that there is no shared state.

Resilience

TIBCO ActiveMatrix Service Gateway provides:

— No single-point-of-failure

— Deployment of multiple instances across multiple hosts

— Deployment across data centres for geo-resilience

— Instance-count can be scaled dynamically to address peak demand


Changes in Functionality | 13

Changes in Functionality

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

Release 1.2

There are no changes in functionality in this release.

Release 1.1

There are no changes in functionality in this release.


14 | Release Notes

Deprecated and Removed Features

This section describes deprecated features (if any), and lists features, if relevant, that may be useful alternatives to the deprecated features. Any use of a deprecated feature should be discontinued as it may be removed in a future release. You should avoid becoming dependent on deprecated features and become familiar with the suggested alternative features.

This section also lists features that are removed (if any).

Release 1.2

Deprecated Features

No features are deprecated in this release.

Removed Features

No features are removed in this release.

Release 1.1

Deprecated Features

No features are deprecated in this release.

Removed Features

No features are removed in this release.


Migration and Compatibility | 15

Migration and Compatibility

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

Release 1.2

This section describes the process of migrating the project and configuration from a previous release.

Make sure that you shut down TIBCO ActiveMatrix Service Gateway engine,

TIBCO ActiveMatrix Service Gateway user interface and any other TIBCO processes before starting the migration process.

Users can migrate from a previous release as follows:

Migrating User Configuration

Users define the configuration for TIBCO ActiveMatrix Service Gateway via an user interface that are stored in the ASG_CONFIG_HOME directory. The configuration files of TIBCO ActiveMatrix Service Gateway software for this release are backward compatible with the previous release, for example release

1.1.

If you want to use the configuration from a previous release (for example, 1.1) , do the following to migrate the configuration:

• Copy configuration folder stored in the ASG_CONFIG_HOME from previous release to the ASG_CONFIG_HOME of this release.

For example, if the CreditCheck configuration was created in the previous release, copy the CreditCheck directory from ASG_CONFIG_HOME of previous release to the ASG_CONFIG_HOME of this release.

• TIBCO ActiveMatrix Service Gateway stores the configuration files in a directory which is seperate from the installation directory. This directory is referenced as ASG_CONFIG_HOME. For example on windows platform, the value of ASG_CONFIG_HOME might be

C:\ProgramData\TIBCOASG\tibco\cfgmgmt\asg.

• Make sure that ASG_CONFIG_HOME for this release is seperate from

ASG_CONFIG_HOME of previous release.

• Start the user interface to load the migrated configuration. Verify that the configuration is loaded in the user interface.


16 | Release Notes

• You can edit your configuration, if needed, to use any new functionality. Save the changes to the configuration.

• Start the TIBCO ActiveMatrix Service Gateway engine to use the configuration at runtime.

Refer to the TIBCO ActiveMatrix Service Gateway User’s Guide for details on how to use the graphical user interface and TIBCO ActiveMatrix Service Gateway engine.

Migrating TIBCO ActiveMatrix Service Gateway Default Project

TIBCO ActiveMatrix Service Gateway software provides a default

ASG_DefaultImplementation project.

If you have made any changes to this project to extend the default behavior of

TIBCO ActiveMatrix Service Gateway engine in the previous release, then you must redo all the changes in this release as the ASG_DefaultImplementation project is not compatible with any previous release.

You can make the changes to the ASG_DefaultImplementation project using the

TIBCO ActiveMatrix Service Gateway Studio. Refer to the TIBCO ActiveMatrix

Service Gateway User’s Guide for details on how to work with TIBCO ActiveMatrix

Service Gateway Studio.

This step is not required if you have not made any changes in the

ASG_DefaultImplementation project in the previous release.

Migrating CDD Files

Users can set the logging configurations, enable EMS channels and other properties of the runtime processing units in the core engine or central logger

CDD files. The CDD files are stored in the ASG_HOME /bin directory.

If you have made any changes to the CDD files ( asg_core.cdd, asg_cl.cdd

) to set the logging configurations, enable JMS channels in the previous release, then all settings must be ported manually again in the CDD files ( asg_core.cdd, asg_cl.cdd

) of this release as the CDD files from the previous release are not compatible with this release.

You can port the settings by editing the CDD files manually using TIBCO

ActiveMatrix Service Gateway Studio.

This step is not required if you have not made any changes in the CDD files in the previous release.

Migrating Property Files


Migration and Compatibility | 17

TIBCO ActiveMatrix Service Gateway software defines the properties for runtime engine in the asg.properties

file and for central logger component in the asg_cl.properties

files respectively. The property files are stored in the

ASG_CONFIG_HOME directory.

If any changes were made to the property files ( asg.properties and asg_cl.properties

) in the previous release, you will require to redo these changes manually in the property files of this release as such changes are not backward compatible.

You can make the changes to the property files of this release by editing the files using a text editor.

This step is not required if you have not made any changes in the asg.properties and asg_cl.properties property files in the previous release.

Release 1.1

A new graphical user interface has been introduced in this release, which allows the users to enter the configuration. Users should use the configuration UI to manually enter the data from the old configuration files to ensure that the old configuration data is stored in a new format.


18 | Release Notes

Closed Issues

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

Closed in

Release

1.2.0

Key

ASG-30

1.2.0

1.2.0

1.2.0

1.2.0

1.2.0

ASG-31

ASG-212

ASG-602

ASG-546

ASG-221

Summary

TIBCO ActiveMatrix Service Gateway engine does not propagate the

HTTP response codes from south-side to north-side.

TIBCO ActiveMatrix Service Gateway engine does not propagate

HTTP response headers from South-side to north-side.

Binary SOAP MTOM attachments do not work.

When the apache server (httpd) is listening on the default port, invalid server host and port values are displayed in the request context.

When the properties for both signing and encrypting the response documents are specified in a single property file, then encryption does not work as the the type of keystore can only be specified as subject or trust.

The installer logs the following harmless error in the log files created in the .TIBCO

directory located under the home directory of the user:

ERROR::, ClassNotFoundException: com.tibco.installer.wizard.action.TIBCOUpdateBELegacyRegistryWiz

ardAction not found., class com.tibco.installer.util.TIBCOUniversalInstallerAction


Known Issues | 19

Known Issues

Key

ASG-605

ASG-126

ASG-511

ASG-603

ASG-657

ASG-658

The table in this section lists known issues in this release.

Summary/Workaround

Summary Multiple instances of asg-egine.exe engine can not be started using the deafult JMX port, as configured in the engine TRA file.

Workaround Start each instance of the engine to use a seperate JMX port, which can be done by using the --propVar jmx_port=XXXX (where XXXX is your port number) option at the command line to start the engine.

Summary When installation verification is tool is run against TIBCO

ActiveMatrix Service Gateway software installation, it reports some missing files.

Workaround None

Summary If any TIBCO ActiveMatrix Service Gateway agent (core or cache cleaner) is started before the cache agent, it starts the connect listener. If the first started agent is shut down and restarted, it gives the following error:

Waiting for quorum:

At least [1] or more storage enabled members (seeders) have to be present in the cluster for proper functioning. Currently there are [0] storage enabled members in the cluster.

Workaround: Start the agents in the following order : Cache Agent, Cache

Clearing Agent, Core Agent

Summary Client information is not available in the request context for the apache module.

Workaround None

Summary TIBCO ActiveMatrix Service Gateway Studio is not supprted on

Solaris Sparc platform.

Workaround None

Summary The configuration for SAML subject confirmation methods such as bearer, holder of key for WSS security are not supported.

Workaround None


20 | Release Notes

Key

ASG-512

ASG-506

ASG-455

ASG-310

ASG-115

Summary/Workaround

Summary For the configuration of XSLT files, when the New File option is used to browse and select a file which was previously selected and is present in the Existing Files drop down list box, the configuration UI throws an error when the configuration is saved.

Workaround Pick the file from the Existing Files drop down list box and save the configuration.

Summary When the user imports the

TIBCO_HOME / asg/1.1/projects/ASG_DefaultImplementation project in

ActiveMatrix Service Gateway Studio and builds the EAR file, the following error is displayed:

Project Library: Unable to resolve CustomFunctions

Workaround Clean the project one or two times by using the Project -> Clean menu option.

Summary Rule and Rule Functions source cannot be viewed directly from the asg_core.projlib project library under the

TIBCO_HOME / asg/1.1/lib/projectlib directory.

Workaround Uncompress the project library contents and view it in

ActiveMatrix Service Gateway Studio or with any text editor.

Summary When the JMS-XML is used as a backend service, the following

NumberFormatException is thrown by the gateway engine:

Message: java.lang.NumberFormatException: For input string:

"ID:EMS-SERVER.9C84F8F785911F0:18" where, "ID:EMS-SERVER.9C84F8F785911F0:18", is the message ID of the request message and will vary for each request.

Workaround Map the correlationID from the request message to the correlationID of the JMS response message.

Summary The installer fails to start the bundled JRE on some 64-bit Linux distributions including Ubuntu 11.04 with the following error:

Initializing Wizard........

Extracting Bundled JRE.

Bundled JRE is not binary compatible with host OS/Arch or it is corrupt.Testing bundled JRE failed.

Workaround Install 32 bit oracle JRE. Set JAVA_HOME environment variable.

For example, Java executable is installed in /opt/oracle/jre/1.6.0/bin , set

JAVA_HOME as: export JAVA_HOME=/opt/oracle/jre/1.6.0


Known Issues | 21


22 | Release Notes


TIBCO ActiveMatrix Service Gateway ®

TIBCO ActiveMatrix

®

Service

Gateway

Release Notes

Contents

Preface

Topics

Typographical Conventions

Connecting with TIBCO Resources

How to Join TIBCOmmunity

How to Access All TIBCO Documentation

How to Contact TIBCO Support

Release Notes

Topics

New Features

Release 1.2

Release 1.1

Release 1.0