tibcoactivematrix adapterfor siebel · pdf filethe eai tibco http business service (using...

TIBCO ActiveMatrix® Adapter forSiebel

Release NotesSoftware Release 6.1.0March 2012

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDEDOR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITEDADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLEDSOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FORANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF ALICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSEAGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USERLICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THESOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARELICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATEDIN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMSAND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND ANAGREEMENT TO BE BOUND BY THE SAME.This document contains confidential information that is subject to U.S. and international copyright laws andtreaties. No part of this document may be reproduced in any form without the written authorization of TIBCOSoftware Inc.TIB, The Power of Now, TIBCO ActiveMatrix BusinessWorks, TIBCO Rendezvous, TIBCO Administrator,TIBCO Designer, TIBCO Runtime Agent, TIBCO Hawk, TIBCO Enterprise Message Service, TIBCO DesignerAdd-in for TIBCO Business Studio, TIBCO ActiveMatrix Service Grid, TIBCO ActiveMatrix Service Bus, TIBCOActiveMatrix BusinessWorks Service Engine, TIBCO ActiveEnterprise, and TIBCO Business Studio are eitherregistered 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 SunMicrosystems, Inc. in the U.S. and other countries.All other product and company names and marks mentioned in this document are the property of theirrespective owners and are mentioned for identification purposes only.THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALLOPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAMETIME. SEE THE README.TXT FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON ASPECIFIC OPERATING SYSTEM PLATFORM.THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, 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 BEINCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKEIMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED INTHIS DOCUMENT AT ANY TIME.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY ORINDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDINGBUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.Copyright © 1998-2012 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

Contents | iii

Contents

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

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

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiHow to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

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

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 6.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 6.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 6.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 6.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 6.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 6.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 6.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 6.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 6.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 6.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 6.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 6.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

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

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

TIBCO ActiveMatrix Adapter for Siebel Release Notes

iv | Contents


| v

Preface

TIBCO ActiveMatrix Adapter for Siebel is a bi-directional gateway between theSiebel application and applications configured for the TIBCO environment. It isassumed that you are familiar with the basic concepts of the TIBCO environmentand Siebel Enterprise technology.

Topics

• Typographical Conventions, page vi

• Connecting with TIBCO Resources, page viii


vi | Typographical Conventions

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

ENV_HOME

TIBCO_HOME

ADSBL_HOME

TIBCO products are installed into an installation environment. A productinstalled into an installation environment does not access components in otherinstallation environments. Incompatible products and multiple instances of thesame product must be installed into different installation environments.

An installation environment consists of the following properties:

• Name Identifies the installation environment. This name is referenced indocumentation as ENV_NAME. On Microsoft Windows, the name isappended to the name of Windows services created by the installer and is acomponent of the path to the product shortcut in the Windows Start > AllPrograms menu.

• Path The folder into which the product is installed. This folder is referencedin documentation as TIBCO_HOME.

TIBCO ActiveMatrix Adapter for Siebel installs into a directory within aTIBCO_HOME. This directory is referenced in documentation as ADSBL_HOME.The default value of ADSBL_HOME depends on the operating system. Forexample, on Windows systems, the default value isC:\tibco\adapter\adsbl\version_number.

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

Use MyCommand to start the foo process.

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

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


Preface | vii

italic font Italic font is used in the following ways:

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

• To introduce new terms For example: A portal page may contain severalportlets. 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

Keycombinations

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

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

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

The tip icon indicates an idea that could be useful, for example, a way to applythe 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


viii | Connecting with TIBCO Resources

Connecting with TIBCO Resources

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

How to Access All TIBCO DocumentationAfter you join TIBCOmmunity, you can access the documentation for allsupported product versions here:

http://docs.tibco.com/TibcoDoc

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

• For an overview of TIBCO Support, and information about getting startedwith 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 username, you can request one.


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


http://docs.tibco.com/TibcoDoc

http://www.tibcommunity.com

| 1

Release Notes

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

Topics

• New Features, page 2

• Changes in Functionality, page 4

• Deprecated and Removed Features, page 5

• Migration and Compatibility, page 6

• Closed Issues, page 7

• Known Issues, page 12



2 | Release Notes

New Features

This section lists features added since the last major release (6.0.0) of this product.

Release 6.1.0The following are new features in Release 6.1.0:

• Enhance for Multi-threaded Connection Management This release allows theadapter connection pool to process incoming requests even when one of theconnections in the connection pool goes stale.

• Support for the Use of the OR Keyword to Query Siebel Integration Objects Thisrelease allows the adapter to specify multiple query conditions using the ORkeyword to query Siebel Integration Objects.

• Added Platform Support Support has been added for the following platforms:

— Microsoft Windows

Windows 7

Windows Server 2008 R2

— Solaris 10

— HP-UX 11i v2 and 11i v3 (PA-RISC)

— Red Hat Enterprise Linux 6.x

— SUSE Linux Enterprise 10.x and 11



— Microsoft Windows 2008 SP2

— HPUX Itanium 11iv3

— AIX 6.1



New Features | 3


— Microsoft Windows 2008 Server Service Pack 1 (x86)

— Red Hat Enterprise Linux Edition 4.2 and higher for version 4

— Red Hat Enterprise Linux Edition 5.1 and higher for version 5

— HPUX 11iv2 on Itanium (11.23)

• Support for Siebel 8.0.0 and 8.1.1 This release adds support for Siebel 8.0.0 and8.1.1.

• Support for JMS Messaging Between Siebel Server and Adapter forRequest-Response Invocation and Publication Services This release supportsJMS messaging for communication between Siebel Server and the adapter forRequest-Response Invocation and Publication Services.

• Support for New EAI Business Services (EAIXMLConverter) This releasesupports EAI XML Converter in TIBCO Siebel Business Service in addition toXML Converter.

— Allows the adapter to read fields/schema information from the SiebelRepository without replacing spaces with underscores in the TIBCOschema.

— Allows information to be sent to the adapter in both XML and EAI XMLConverter format.

• Support for User Impersonation for Subscription Service The adapter acceptsusername/password passed as parameters in the incoming message and canperform actions under the identity of the user indicated.

• Support for Sending Timestamp in Milliseconds as Part of a Message inPublication Service This release adds the time in milliseconds to the outgoingmessage from the adapter.

• Support for Strongly Typed Variables in Packaged EAI TIBCO Business Servicesfor Siebel 8.0.0 and 8.1.1 This release adds support for strongly typedvariables in packaged eScript Business Services for Siebel 8.0.0 and 8.1.1

• Support for User Override of ErrorCode, ErrorMessage, and TIBErrorCodeAttribute Values in the SiebelHeader element This release allows the overrideof the ErrorCode, ErrorMessage, and TIBErrorCode attributes that arecontained in the SiebelHeader element.

• Support for Adding Custom Elements to the SiebelHeader when SendingIntegration Object Information to Siebel using the Adapter The adapter nowallows elements to be added to the SiebelHeader element when addingcustom data to the Siebel Message for Integration Objects for request-responseinvocation service. This allows the structure of the original message to remainintact.


4 | Release Notes

Changes in Functionality

This section lists changes in functionality of this product.

Release 6.1.0The following are changes in functionality in Release 6.1.0:

• Dropped Platform Support The Red Hat Enterprise Linux 4.x, AIX 5.2, andWindows Server 2003 platforms are no longer supported.

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

Release 6.0.0The following are changes in functionality in Release 6.0.0:

• Dropped Support for TIBCO IntegrationManager TIBCO IntegrationManager isno longer supported.

• Dropped Platform Support Microsoft Windows 2000 and XP Professionalplatforms are no longer supported.

• Dropped Support for Siebel Versions Siebel 6.2, 6.3, 7.0.3, 7.0.4, 7.5.2 and 7.5.3are not supported in this release.


Deprecated and Removed Features | 5

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 adeprecated feature should be discontinued as it may be removed in a futurerelease. You should avoid becoming dependent on deprecated features andbecome familiar with the suggested alternative features.

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

Release 6.1.0

Deprecated Features

No features are deprecated in this release.

Removed Features

The following features are removed in this release:

• Dropped Support for TIBCO ActiveMatrix Adapter Service Engine for Siebel TheTIBCO ActiveMatrix Adapter Service Engine component of TIBCOActiveMatrix Adapter for Siebel is no longer supported.

Release 6.0.1No features are deprecated or removed in this release.

Release 6.0.0No features are deprecated or removed in this release.


6 | Release Notes

Migration and Compatibility

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

For information on the adapter’s compatibility with TIBCO Runtime Agent andother TIBCO applications, see the TIB_adsbl_6.1.0_readme.txt file.

For information on migrating to a newer version of TIBCO Runtime Agent (TRA),see the TIBCO Runtime Agent documentation set. For example, if you needinformation on migrating to TIBCO Runtime Agent 5.7, see TIBCO Runtime AgentUpgrading to Release 5.7.

Release 6.1.0There are no migration procedures or compatibility issues in this release.



Back up the project before starting the migration process.


Closed Issues | 7

Closed Issues

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

Closed inRelease

ChangeRequest ID Summary

6.1.0 ASBL-1349 When using the JMS Integration to interact with EAI TIBCO JMS Agent, theRequest-Response Invocation service with the Send Receive IntegrationObjects event type was not able to trigger the adapter reconnectionmechanism.

6.1.0 ASBL-1254 On 64-bit Solaris 10 platforms, TIBCO ActiveMatrix Adapter for Siebel 6.0.1was not started with TIBCO Runtime Agent 5.7.1.

6.1.0 ASBL-1217 For the Request-Response Invocation service, the socket ID created for a newrequest was different from the one closed for the same event.

6.1.0 ASBL-1214 For the Request-Response service, all the request messages that had not beenconfirmed were lost during reconnection.

6.1.0 ASBL-1207 When you deployed a project using TIBCO Administrator on HP-UX IA64platforms, the adapter instance failed to start up with an incorrect JVM stacksize in the deployed TRA file.

6.1.0 ASBL-1199 When the adapter received several messages at the same time, some of themessages were handled even though a connection error (-76) occurred. Inaddition, the adapter did not try to reconnect, although the Reconnect BeforeService Execution option was enabled.

6.1.0 ASBL-856 In a TIBCO Designer project, for a Publication service with a Non-SiebelBusiness Component publication type, if more than one service using JMStransport was added to an adapter instance, the Configuration tab did notappear when switching from one service to another.

6.1.0 ASBL-758 In a TIBCO Designer project, when checking the Show All Tabs checkbox inthe Configuration tab of an adapter instance, then clicking the Reset button,the new settings were not reset to the original settings.

6.0.1 ASBL-1222 When the publish as XML option was enabled for the adapter Publicationor Request Response Invocation service, an error occurred indicating that theXML Message attribute was not found.

6.0.1 ASBL-1221 The values for the ErrorMessage and TIBErrorCode attributes could not beoverridden by setting the values of TibcoAppError.

6.0.1 ASBL-1205 If events came during the connection pool re-initiation, too many tempconnections were created between the adapter and Siebel.


8 | Release Notes

6.0.1 ASBL-1216 When the Siebel Server shut down, if the adapter Publication service passed amessage from the simulator in Siebel Call Center, an error message wouldoccur to show that the connection to the Siebel server failed. But if themessage was triggered again in Siebel Call Center, no error occurred.

6.0.1 ASBL-1215 On UNIX platforms, the adapter could not be terminated by sending amessage to the Termination Message Subject after Application Readyappeared in the runtime log.

6.0.1 ASBL-1210 The method to get adapter status through HTTP was missing support for theGET request method.

6.0.1 ASBL-1209 The adapter accepted ping requests from the browser, but returned incorrectstatus information.

6.0.1 ASBL-1195 The adapter process could not stop by invoking thestopApplicationInstance Hawk method.

6.0.1 ASBL-793 The adapter erroneously retrieved inactive workflow for section in the userinterface.

6.0.1 ASBL-1202 When a project containing Siebel Adapter Instances was validated forDeployment, TIBCO Designer threw subject validation errors for the defaultadvisory endpoints that were created with subjects starting with _RV and_SDK.

6.0.1 ASBL-1213 On the AIX platform, the SSL connection would not work when HTTPS wasused as the transport type instead of HTTP for the Publication and theRequest Response Invocation services.

6.0.1 ASBL-1208 The MessageType property could not be defined in the TibcoMessagegenerated by the adapter.

6.0.1 ASBL-1197 The adapter kept reprocessing the same timeout message in an infinite loop ifthis timeout event introduced connection reset.

6.0.1 ASBL-1198 When the performance monitoring (perfMon) setting in TIBCO ActiveMatrixAdapter for Siebel 6.0 was enabled through the adsbl.tra file, the adaptercaused high CPU load during reconnection on AIX.

6.0.1 ASBL-1194 The adapter instance could not be shut down using TIBCO HAWK throughTIBCO Administrator.

6.0.1 1-AXUMLY

(ASBL-860)

The adapter encountered a Connection Reset when accessing Siebel JDB forXML Converter conversion services.

Closed inRelease



Closed Issues | 9

6.0.1 1-AXRRP2

(ASBL-859)

The adapter did not get any reply from the application in the RequestResponse Invocation scenario. The MTimeoutException was not caught inINFO log level.

6.0.1 1-AVV6WL

(ASBL-854)

When working with Siebel 8.0 and above, a reply could not be larger than 25kin Request Response Invocation service.

6.0.1 1-ATV6GT

(ASBL-847)

When configuring the adapter in TIBCO Designer, change of the number ofsessions in the Multithreading tab could not be saved.

6.0.1 1-AU87TH

(ASBL-848)

The IO instance created by XML Converter with space characters betweenelements could not be mapped in run time.

6.0.1 1-AUAKT9

(ASBL-849)

The adapter could not pass special characters such as "<", ">", "'", etc., to Siebelby SiebelHeader attribute.

6.0.0 1-377G3P

(ASBL-335

While configuring a Subscription or Request-Response Service for Workflowinvocation, the palette was unable to fetch custom workflows from the SiebelRepository.

6.0.0 1-6VTL6R

(ASBL-509)

No sessions were listed as associating an existing subscriber endpoint in acustom RVCM session to a Subscriber Service.

6.0.0 1-1NTKMW

(ASBL-125)

The Subscription Service did not receive any events after the reactivation ofthe services while reconnecting to Siebel. This occurred when the SubscriptionService was configured for the Distributed Queue Quality of Service and wasreceiving messages from an RVCM publisher.

6.0.0 1-9Q3ZHG

(ASBL-731)

While using multibyte characters in the reply to the adapter, the HTTPresponse was sent with an incorrect length, because the multibyte characterswere counted as single byte characters.

6.0.0 1-92BRQ2

(ASBL-690)

When the transport type was set to the JMS connection factory type Queue,the adapter failed to start up and displayed the error:AESEBL-910005 Startup Error. SDK Exception "Invalidassoc key: deliveryMode/."

6.0.0 1-ACF61B

(ASBL-795)

The EAI TIBCO HTTP Agent Business Service caused Siebel to crash if theoutgoing message exceeded a certain byte size limit. This was caused by aSiebel eScript defect.

Closed inRelease



10 | Release Notes

6.0.0 1-A9RHHI

(ASBL-785)

When multiple Siebel Servers were configured to operate in load balancedconfiguration with the adapter, there could be a situation where theconnection was lost because of a server shutdown. The test for connectivityfirst succeeded in reconnecting but was subsequently lost because all serverswere shut down. In this case, the adapter stopped any reconnection attempts.

6.0.0 1-A4VEYG

(ASBL-779)

The adapter did not process Siebel messages that contained new-linecharacters.

6.0.0 1-9B841D

(ASBL-695)

When Integration Object was encoded using Siebel Business Service XMLConverter in Siebel 8.0 and above, a <PropertySet> tag was added to themessage that prevented the adapter from parsing the data correctly.

6.0.0 1-9CSEUB

(ASBL-700)

During the adapter initialization, the JMS stop topic was not created when themutex locked in TIBCO Adapter SDK.

6.0.0 1-9C7AL2

(ASBL-696)

The adapter failed to initialize if the Request and Reply endpoints were notcreated when using JMS on Linux or Solaris platforms and TIBCO RuntimeAgent 5.6.0.

6.0.0 1-9F7MX5

(ASBL-702)

The adapter did not send a valid HTTP response while trying to configure thereverse-proxy server to set up load balancing between the adapter and theSiebel application.

6.0.0 1-8WKIQA

(ASBL-683)

When configuring subscription or request-response services with workflowinvocation for Siebel 7.7.1 and above, some workflows could not be fetchedfrom the Siebel repository.

6.0.0 1-9CLR56

(ASBL-698)

The adapter invoked EAI TIBCO HTTP Agent Business Service for everyrequest even though the HTTP Agent was disabled in the environment.

6.0.0 1-9GHXM2

(ASBL-703)

A variable could not be found error occurred while executing thevalidateSendData function with EAI TIBCO HTTP Agent Business Servicein Siebel 8.0.

6.0.0 1-7ZLYXM

(ASBL-584)

When sending records to Siebel, if the key fields in the adapter to check theuniqueness were changed by Siebel rules, duplicated records were created inSiebel.

6.0.0 1-8QX8SL

(ASBL-676)

The adapter did not update special characters properly in Siebel.

6.0.0 1-90HQ2A

(ASBL-688)

HTTP reply from the adapter for large messages was fragmented intothousands of packets over the network.

Closed inRelease



Closed Issues | 11

6.0.0 1-8LH1JX

(ASBL-641)

Child IO data was lost after closing and reopening the project if that IO didnot have any fields.

6.0.0 1-8K7GXK

(ASBL-1252)

When configuring a Request Response Service with a JMS Topic transporttype with an Insert/Update Integration Object option, the adapter changedthe transport option to JMS Queue while saving the project.

6.0.0 1-8BFVO5

(ASBL-607)

When configuring an adapter instance with MultiValueLink in TIBCODesigner, even though the Match Condition was specified at design time, theadapter threw a Missing Match Conditions error during runtime.

6.0.0 1-8IE7GN

(ASBL-630)

1-8LDQTI

(ASBL-640)

In case a connection timeout was detected for the Publication orRequest-Response Invocation service, even with Reconnect beforeService Execution enabled, the adapter failed to process the last requestthat was received before reconnection.

Closed inRelease



12 | Release Notes

Known Issues

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

ChangeRequest ID Summary/Workaround

ASBL-1324 Summary When starting a Subscription service for the first time with the followingvariables settings in the Transport tab:

Wire Format=XML Message, Factory Type= Topic, Delivery Mode=Durable

the Subscription service does not start correctly, and the following error messageappears:java.lang.IllegalArgumentException: Durable name must bespecified.

Workaround To start the Subscription service successfully, complete the followingsteps:

1. In Project panel, expand the current Siebel configuration instance.

2. Expand Advanced > Sessions > DefaultJmsTopicSession, and select theSubscriptionServiceEndpoint item.

3. In the Configuration tab, place the cursor into the Durable Name field, then selectProject > Save from the menu.

4. Select Tools > Show Adapter Tester from the menu. The Adapter Tester dialogappears. Then select the Siebel configuration instance. Click the Start button.

ASBL-1280 Summary The adapter fails to establish connection with the Siebel server on Solarisplatforms.

Workaround Navigate to the TIBCO_HOME\designer\version_number\bindirectory, and add the following property at the end of the designer.tra file:

java.property.file.encoding ISO8859_1.

ASBL-1257 Summary The EAI TIBCO JMS Agent business service is not able to send and receivemessages when calling its sendReceive method.

Workaround Remove the line of intObj = null in thevalidateData4SendReceiveMethod method, or comment out this line(//intObj= null;), then compile EAI TIBCO JMS Agent to take effect.

ASBL-1255 Summary The usage of the adsbl.SiebelVersion property is not clearly specifiedin its associated comments in the adsbl.tra file. An improper setting of this propertyleads to a failure when converting between an XML file and a Siebel object (propertyset)by XMLConverter.

Workaround Do not modify the 753 default value of the adsbl.SiebelVersionproperty.


Known Issues | 13

ASBL-1259 Summary The actual output arguments for SendReceive method of EAI TIBCO JMSAgent are not visiable in Siebel Tools.

The following lists show the actual common output arguments for SendReceivemethod of EAI TIBCO JMS Agent for reporting status:

• ErrorCode String Output

• ErrorMsg String Output

• TIBErrorCode String Output

• Status String Output

The following lists show the actual output arguments for SendReceive method of EAITIBCO JMS Agent used for storing the actual reply data:

• ReplyString String Output

• ReplyNumeric String Output

• PropertySet Hierarchy Output

Workaround None.

ASBL-1047

(1-DDXZH)

Summary When Run Workflow Process is selected as an action for a workflow policy,the EAI TIBCO HTTP Business Service (using Siebel's EAI HTTP Transport BusinessService) does not forward the request to the adapter.

Workaround This is an issue with the Siebel Enterprise System. Use Run IntegrationProcess instead of Run Workflow Process.

Refer to FAQ 1354: Why does Workflow Process Manager fail to run HTTPTransport? on Siebel’s Support Web for more information.

ASBL-1045

(1-DDXYM)

Summary When you use the outbound EAI HTTP Transport Business Service, with theSend and SendReceive methods, the response data is truncated if it contains a largeamount of data.

Workaround This is an issue with Siebel Enterprise System. Reduce the size of theXML file sent or received by deactivating fields that are not required in the integrationcomponents being used.Refer to Alert 491: Response Data Is Truncated with the EAI HTTPTransport Business Service in Siebel 7.0.3 on Siebel’s Support Web formore information.

ChangeRequest ID Summary/Workaround


14 | Release Notes


tibcoactivematrix adapterfor siebel · pdf filethe eai tibco http business service (using...

Documents