You are on page 1of 48

TIBCO BusinessConnect™ Palette Reference

Software Release 5.3 May 2009

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 LICENSE.PDF) 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, TIBCO BusinessConnect, TIBCO Runtime Agent, TIBCO ActiveMatrix BusinessWorks, TIBCO Administrator, TIBCO Designer, TIBCO Rendezvous, and TIBCO Enterprise Message Service are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries. EJB, J2EE, JMS 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.TXT 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-2009 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information

| iii

Contents

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii TIBCO BusinessConnect Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x How to Contact TIBCO Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Chapter 1 BusinessConnect Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Using Schemas in BusinessConnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 BCServerConfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Provide Information for the TIBCO BusinessConnect Server Access Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Update the Configuration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Configure the Rendezvous or the JMS Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Configure Private Processes for Smart Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Working with Nested Schemas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Receive Misc. Msg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Misc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receive Request/Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Misc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receive Response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Misc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send Misc. Msg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 18 22 22 23 23 25 25 26 26 28 28 29 29 29 29

Send Request/Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

TIBCO BusinessConnect Palette Reference

iv

| Contents
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Send Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 32 33 33

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

TIBCO BusinessConnect Palette Reference

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Connection Transport Fields: Rendezvous . . . . . . . . . . . . . . . Msg Configuration Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Msg Misc Fields . . . . . . . . . 25 Receive Response Configuration Fields . . . . . . . . . 29 Send Request/Notification Configuration Fields. . . . . . . . . . . . . . . . . . . . . . . . 30 Send Response Configuration Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Msg Configuration Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Receive Misc. . . . . . . . . . .|v Tables Table 1 Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 General Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Send Misc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x TIBCO BusinessConnect Server Access Fields. . . . . . . . . . 4 TIBCO BusinessConnect Connection Configuration Fields . . . . . . . . . . . . . . . . . . . 22 Receive Request/Notification Configuration Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Receive Response Misc Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Configure the JMS Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Receive Request/Notification Misc Fields . . . . . . . . . . . . . . . . . . . . . . . . . 10 Configure the Secure JMS Transport. . . . . . . . . . . . . . 32 TIBCO BusinessConnect Palette Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Receive Misc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

vi | Tables TIBCO BusinessConnect Palette Reference .

TIBCO BusinessConnect™ software is a B2B (business-to-business) gateway that allows your company to engage in electronic commerce with your business partners. page xii TIBCO BusinessConnect Palette Reference .txt file for the availability of this software version on a specific operating system platform. However. Topics • • • Related Documentation. Please see the readme. page viii Typographical Conventions. page x How to Contact TIBCO Customer Support. not all operating system platforms for a specific software version are released at the same time.| vii Preface This software may be available on multiple operating systems.

EZComm is installed with TIBCO BusinessConnect. TIBCO BusinessConnect Trading Partner Administration Guide: Read this guide to configure and manage trading partners. TIBCO BusinessConnect Server Administration Guide: Read this guide in order to administer (install. • • Other TIBCO Product Documentation You may find it useful to read the documentation for the following TIBCO products.viii | Related Documentation Related Documentation This section lists documentation resources you may find useful. This guide contains a detailed tutorial. TIBCO BusinessConnect Palette Reference: Read this guide to learn about the resources available in the TIBCO BusinessConnect Palette for TIBCO BusinessWorks. which may be used or integrated with BusinessConnect: • TIBCO Administrator™ software: The software allows you to manage users. deprecated features. operate. protocols. therefore no separate installation guide for this protocol is provided. known issues. The TIBCO BusinessConnect Palette Reference . and manage) the BusinessConnect server. • TIBCO BusinessConnect Scripting Deployment User’s Guide: Read this guide to configure and manage TIBCO BusinessConnect using the command line interface. This document is supplied for each release and is available only in PDF format. TIBCO BusinessConnect EZComm Protocol User’s Guide: Read this guide to learn about using TIBCO BusinessConnect EZComm Protocol. and security. and closed issues for each release. TIBCO BusinessConnect Documentation The following documents form the BusinessConnect documentation set: • • • • TIBCO BusinessConnect Concepts: Read this guide to learn about TIBCO BusinessConnect architecture. which is a recommended reading for new TIBCO BusinessConnect users. deployment modes. machines and applications defined in a TIBCO Administration Domain. TIBCO BusinessConnect Release Notes: Read this document to learn about new features. changes in functionality.

Java Runtime Environment (JRE). In addition to TIBCO Runtime Agent components. TIBCO Runtime Agent™ software: This software suite is a prerequisite for other TIBCO software products.Preface ix | TIBCO Administrator graphical user interface enables users to deploy. TIBCO BusinessWorks includes a graphical user interface (GUI) for defining business processes and an engine that executes the process. the software suite includes the third-party libraries used by other TIBCO products such as TIBCO Designer. extensible. TIBCO Hawk®. The EAR can then be used by TIBCO Administrator for deploying and running the application. TIBCO Enterprise Message Service ™ software: This software provides a message service that enables integration of applications within an enterprise based on the Java Message Service (JMS) specifications. monitor. and start and stop TIBCO applications. • • • • TIBCO BusinessConnect Palette Reference . and the Rendezvous daemon. and easy to use integration platform that allows you to develop integration projects. • TIBCO ActiveMatrix BusinessWorks™ software: This software is a scalable. TIBCO Designer™ software: This graphical user interface is used for designing and creating integration project configurations and building an Enterprise Archive (EAR) for the project. and TIBCO Rendezvous®. It includes two main components: the Rendezvous programming language interface (API) in several languages. TIBCO Rendezvous®: This software enables programs running on many different kinds of computers on a network to communicate seamlessly.

to indicate the default parameter for a command. For example. Other TIBCO products are installed into an installation environment. This directory is referenced in documentation as TIBCO_HOME. on Windows systems the default value is C:\tibco. the default value is C:\tibco. MyCommand is enabled: MyCommand [enable | disable] italic font Italic font is used in the following ways: • • • To indicate a document title. pathnames. In large code samples. For example. bold code font Bold code font is used in the following ways: • • • In procedures. For example: MyCommand PathName TIBCO BusinessConnect Palette Reference . For example: See TIBCO ActiveMatrix BusinessWorks Concepts. To indicate a variable in a command or code syntax that you must replace. to indicate what a user types. on Windows systems. The value of TIBCO_HOME depends on the operating system. Portlets are mini-applications that run in a portal. Incompatible products and multiple instances of the same product are installed into different installation environments. For example: Type admin. In command syntax. if no parameter is specified. and output displayed in a command window. For example. code font Code font identifies commands. To introduce new terms For example: A portal page may contain several portlets. The directory into which such products are installed is referenced in documentation as ENV_HOME. Table 1 General Typographical Conventions Convention TIBCO_HOME ENV_HOME Use Many TIBCO products must be installed within the same home directory. For example: Use MyCommand to start the foo process. filenames. code examples. The value of ENV_HOME depends on the operating system. to indicate the parts of the sample that are of particular interest.x | Typographical Conventions Typographical Conventions The following typographical conventions are used in this manual.

for example. an additional action required only in certain circumstances. The note icon indicates information that is of special interest or importance. a way to apply the information provided in the current section to achieve a specific result. Ctrl+Q. For example: Ctrl+C. data loss or corruption if certain steps are taken or not taken. for example. The tip icon indicates an idea that could be useful. The warning icon indicates the potential for a damaging situation.Preface xi | Table 1 General Typographical Conventions (Cont’d) Convention Key combinations Use Key name separated by a plus sign indicate keys pressed simultaneously. for example. Key names separated by a comma and space indicate keys pressed one after the other. TIBCO BusinessConnect Palette Reference . For example: Esc.

tibco. and information about getting started with TIBCO Product Support.com Entry to this site requires a user name and password. TIBCO BusinessConnect Palette Reference .com/services/support • If you already have a valid maintenance or support contract. visit this site: http://www.xii | How to Contact TIBCO Customer Support How to Contact TIBCO Customer Support For comments or problems with this manual or the software it addresses. you can request one. please contact TIBCO Support Services as follows. visit this site: https://support. • For an overview of TIBCO Support Services. If you do not have a user name.tibco.

|1 Chapter 1 BusinessConnect Palette This chapter provides information about the TIBCO BusinessConnectTM palette and shared resources. page 26 Send Misc. Msg. Topics • • • • • • • • Overview. page 29 Send Request/Notification. page 18 Receive Request/Notification. page 32 TIBCO BusinessConnect Palette Reference . page 30 Send Response. page 23 Receive Response. page 2 BCServerConfig. Msg. page 3 Receive Misc.

Only schemas that are loaded in the operations editor will be loaded down by the TIBCO BusinessConnect palette.2 | Chapter 1 BusinessConnect Palette Overview This chapter provides information about the TIBCO BusinessConnectTM palette and shared resources. You can later use the custom schema to complete validation based on the partner name or any other property of the received message. The TIBCO BusinessConnect palette does not evaluate partner-level overrides. This book assumes familiarity with TIBCO Designer and palette resources. Using Schemas in BusinessConnect For more information about schema implementation in BusinessConnect. see TIBCO BusinessConnect Trading Partner Administration Guide. Export Schemas. TIBCO BusinessConnect Palette Reference . you can disable validation on the receiving event source and implement a validation task after the message was received and forwarded by the event source. see TIBCO BusinessConnect Concepts. Schemas. refer to the TIBCO Designer User’s Guide and the TIBCO Designer Palette Reference. To Implement Custom Schemas If you need to implement partner-specific behavior with regards to validation. To learn how to export schemas for use in another BusinessConnect installation. see TIBCO BusinessConnect Trading Partner Administration Guide. File Specification Dialog. To Manage Schemas To learn how to reference a schema for use in BusinessConnect. To learn the basics of working with resources within TIBCO Designer.

This shared resource is used when specifying activities in the BusinessConnect palette. but the type of transport cannot be changed.BCServerConfig 3 | BCServerConfig The BCServerConfig resource contains the information needed to connect to a TIBCO BusinessConnect server. TIBCO BusinessConnect Palette Reference . To configure the BCServerConfig resource. you can override the settings using the provided GUI. When you import the TIBCO BusinessConnect configuration store. This folder is accessed through a configured path and its name must be preserved. Using TIBCO Designer. follow these steps: • Provide Information for the TIBCO BusinessConnect Server Access Tab This tab provides access to the fields that allow you to configure a connection to the database used for the configuration store. • Configure the Rendezvous or the JMS Tab The type of transport is selected and configured using TIBCO Administrator. will become available. Private Process Configuration. as explained in TIBCO BusinessConnect Trading Partner Administration Guide. which is hard-coded and shared. a folder named BCSchemas. • Update the Configuration Tab This tab provides access to the TIBCO BusinessConnect configuration store and allows you to refresh the list of available protocols. Do not rename the folder BCShemas. containing imported schemas.

copy wlbase. Users must use the Weblogic driver from the Weblogic Server 10 and above. The old Weblogic driver is JDBC 2.0 calls made by TIBCO BusinessConnect.0 compliant and does not support JDBC 3. but they will be removed in future releases. Oracle OCI Client Path must be manually set at the deployed . wlclient. follow the instruction given in Table 1. You should start using the listed vendor-specific native drivers that are supported by their corresponding databases. wlutil.jar. select one of the available JDBC driver types: • • • • • Oracle Thin Oracle OCI. • • • TIBCO Oracle (deprecated) TIBCO MSSQL (deprecated) TIBCO DB2 (deprecated) Note The deprecated drivers are currently still supported.jar.jar and wlsqlserver. To do so. JDBC Driver JDBC URL DB User DB Password Available drivers for the database. In the dropdown menu. A valid user name for the database. Table 1 TIBCO BusinessConnect Server Access Fields Field JDBC Driver Type Description Type of the JDBC driver. The URL for the configuration store database for the selected JDBC driver. This is optional.4 | Chapter 1 BusinessConnect Palette Provide Information for the TIBCO BusinessConnect Server Access Tab To provide the database parameters.tra file. Microsoft SQL Server MySQL Weblogic MSSQL (deprecated). The password associated with the user name TIBCO BusinessConnect Palette Reference .jar file from the installation to TIBCO_HOME/tpcl/version/jdbc.

To be consistent. Table 2 TIBCO BusinessConnect Connection Configuration Fields Field Name Description Server Description Any unique string identifying this connection resource This optional field allows you to provide a text description of the resource. PP Transport TIBCO BusinessConnect Palette Reference . you can define the following environmental variable as follows: 1.ORACLE_CLIENT_PATH=<Oracle Client native library path> 2. different library paths may need to be appropriately updated.env. The installation name of the TIBCO BusinessConnect server.tra file. Prepend %ORACLE_CLIENT_PATH% to the variables PATH.BCServerConfig 5 | Oracle Client Library Path Usage If you are planning to use the Oracle OCI drivers. It provides valid parameters for the database on the TIBCO BusinessConnect Server Access tab. you must specify this path in the TIBCO Administrator . When dealing with the TIBCO BusinessConnect configuration UI. The method of transport for the private process: TIBCO Rendezvous or JMS.2. such as C:\oracle\product\10. Follow the instruction in Table 2. SHLIB_PATH and LIBPATH. click the button Update from Configuration Store to connect to the Tibco BusinessConnect Configuration and to fetch the private process and protocol configuration. This field is read-only and appears after successful connection to the database used by TIBCO BusinessConnect (the configuration store). Depending on the platform where TIBCO Administrator is installed. This field is read-only. LD_LIBRARY_PATH. The value should point to the Oracle native client libraries directory as follows: • • On Windows This is typically ORACLE_CLIENT_HOME/BIN directory. you must specify the Oracle Client Library path. TIBCO BusinessConnect retrieves the information from the configuration store. Set tibco.0\client\BIN On UNIX This is typically the directory ORACLE_CLIENT_HOME/lib or ORACLE_CLIENT_HOME/lib32 Update the Configuration Tab Once all database parameters are provided. This is for design-time use only.

TIBCO BusinessConnect gives you the option of identifying and deleting any obsolete schemas from the project. TIBCO BusinessConnect gives you the option to delete those schemas from the project. If you need to communicate with multiple protocols. Protocol Name The available protocols. TIBCO BusinessConnect Palette Reference . • If you select this checkbox. To do this. Clear the checkbox to retrieve only protocol-specific settings. If you do not select all of the operations in blue. you can elect to have BusinessConnect delete obsolete schemas. After the first time. You can choose one protocol. Select Operations Available if the selected protocol includes one or more operations and allows to define which operations to import instead of importing all operations. BusinessConnect asks if you want to delete unimported schemas. reimport the protocol and select all operations. you need to have multiple shared resources. Entries in blue have already been imported but will be updated if selected. TIBCO BusinessConnect displays a dialog box with a list of operations for the protocol. This list is populated using information from the configuration store. Then select Yes. • • • Note When you import a business protocol. Entries in black will be imported if selected. Note: During initial configuration of a connection resource. delete unimported schemas. do not select operations for which you want the associated schema deleted. If you re-import a protocol and select all operations. If there are unused schemas on the server for a protocol that has already been imported. one for each protocol. TIBCO BusinessConnect activates this field for editing. for which the information has to be retrieved from the configuration store. TIBCO BusinessConnect imports all operations for the selected protocol. Note Click on the button Import Selected Business Protocol to import the list of selected operations. If you clear this checkbox. then click OK. Select the checkbox next to each operation you want to import/update.6 | Chapter 1 BusinessConnect Palette Table 2 TIBCO BusinessConnect Connection Configuration Fields Field Update Transport Settings Description Retrieve the transport settings from the configuration store and overwrite any custom transport settings specified on the Transport tab for this connection resource. this checkbox is selected and you cannot deselect it until you retrieve the transport settings the first time.

BCServerConfig 7 | Table 2 TIBCO BusinessConnect Connection Configuration Fields Field Imported Operations (read only) Use Smart ID Description Displays a list of operations that have been imported from the configuration store. You can also override an inherited smart ID by providing a different smart ID in the event source. you will get a different palette depending on the transport that was selected for communication with these processes. The messages will be routed to this private process event source. the event source will use the same Smart ID as the shared resource. Use of Smart Routing requires that you define business rules in the TIBCO BusinessConnect console. Provide an identifier for the private process instance. In this case. If the checkbox Use Smart ID is selected. See Configure Private Processes for Smart Routing for detailed information. • Smart Routing ID Type the desired Smart ID into this field in order to have a different Smart ID on the event source level . an additional row Smart ID appears on the screen to enter the Smart ID name. depending on the transport that was configured for a specific project: • • Rendezvous Tab JMS Tab TIBCO BusinessConnect Palette Reference . Event sources that reference a shared resource can inherit the smart ID if you enable Smart Routing for the event source. One of these two tabs will be available. Smart ID • Shared Smart ID Select this checkbox to inherit the Smart ID from the shared resource directly into this event source. Configure the Rendezvous or the JMS Tab When you are configuring Private Processes for TIBCO BusinessConnect.

messages are confirmed even though there is no active listener loaded in the palette for this message (messages are not dispatched successfully to any listener). See TIBCO Designer User’s Guide for more information. if it exists. TIBCO BusinessConnect Palette Reference . it configures the certified listener transport to automatically confirm delivery of messages from the TIBCO BusinessConnect server to the private process. If left blank. The network to be used by the Rendezvous daemon The client socket used for the Rendezvous daemon Specifies the quality of service for messages transmitted to the TIBCO BusinessConnect server. otherwise it uses port 7500.8 | Chapter 1 BusinessConnect Palette Rendezvous Tab This tab provides access to the fields that allow you to configure TIBCO BusinessConnect for use with TIBCO Rendezvous. Table 3 provides brief descriptions of the fields on the TIBCO Rendezvous tab. Otherwise. If you selected Reliable. the private process is responsible for confirming delivery. For detailed information. TIBCO Rendezvous messages will be confirmed only if the Confirm task is executed for the event. you are done. This quality of service corresponds to TIBCO Rendezvous protocols. To avoid this behavior. The available options are: • • • Reliable Certified Distributed Queue Network Daemon Quality of Service The remaining fields vary based on the quality of service you select. refer to the TIBCO Rendezvous documentation. TIBCO Rendezvous uses the Rendezvous service. disable the option Auto Confirm and use the explicit confirmation: in such case. Table 3 Connection Transport Fields: Rendezvous Field Installation Name Subject Prefix Service Description The name of the TIBCO BusinessConnect installation The subject prefix from the TIBCO BusinessConnect installation Either the name of the Rendezvous service or its port number. You will need to create a Confirm task and specify which event to confirm. Server to PP CM Auto Confirm If this checkbox is selected. Note If this option is enabled and any listener using this BCServerConfig is loaded.

and Scheduler Activation fields to appear. This name must be different from the name specified in the CM Name field (otherwise there is a name collision exception at runtime). Scheduler Heartbeat. a process-based ledger is used for interaction between TIBCO BusinessWorks and the TIBCO BusinessConnect server. The maximum number of tasks this worker can accept.BCServerConfig 9 | Table 3 Connection Transport Fields: Rendezvous Field Local CM Name Preregistered BC Queue Name Use Process Based Ledger File Based Ledger Description The name of the local certified messaging transport. See the TIBCO Rendezvous documentation for more information about setting the number of tasks. Weight represents the ability of this member to fulfill the role of scheduler. this option is not available. Worker Tasks Scheduler Weight Scheduler Heartbeat (seconds) TIBCO BusinessConnect Palette Reference . When the number of accepted tasks reaches this maximum. All members with the same distributed queue name must specify the same value for this parameter. Scheduler Weight. If this checkbox is selected. relative to other members with the same name. See the TIBCO Rendezvous documentation for more information about setting the scheduler heartbeat. Worker Weight The weight to assign to this worker member of the distributed queue. TIBCO Rendezvous certified ledger file name for interaction between TIBCO BusinessWorks and the TIBCO BusinessConnect server. Specify the properties of the distributed queue. See the TIBCO Rendezvous documentation for more information about assigning worker weight. Checking this field causes the Worker Weight. The scheduler sends heartbeat messages at this interval (in seconds). the worker cannot accept additional tasks until it completes one or more of them. See the TIBCO Rendezvous documentation for more information about setting the scheduler weight. A comma-separated list of certified messaging sessions to register at TIBCO BusinessWorks. QOS (Quality of Service) Properties specific for TIBCO Rendezvous Local Distributed Queue Queue Settings The name of the distributed queue. If Use Process Based Ledger checkbox is selected. Worker Tasks.

10 | Chapter 1 BusinessConnect Palette Table 3 Connection Transport Fields: Rendezvous Field Scheduler Activation (seconds) Worker Complete Time Description When the heartbeat signal from the scheduler has been silent for this interval (in seconds). Settings for configuring JMS are imported from the configuration store and are user modifiable. which specifies no limit on the completion time—that is. If the JMS provider does not require access control. The complete time property influences scheduler behavior. the scheduler reassigns the task to another worker member. The complete time must be non-negative. the scheduler does not set a timer. Table 4 Configure the JMS Transport Field Installation Name Installation Prefix JMS User Name Explanation The name of the TIBCO BusinessConnect installation. See the TIBCO Rendezvous documentation for more information about setting the scheduler activation. and does not reassign tasks when task completion is lacking. If the complete time is non-zero. Refer to your JMS provider documentation and consult your system administrator to determine if your JMS server requires a user name and password. this field can be empty. JMS Tab The JMS tab provides access to the fields that allow you to configure TIBCO BusinessConnect for use with JMS. All members implicitly begin with a default complete time value of zero. Not all JMS servers require user names and passwords. If the complete time elapses before the scheduler receives completion from the worker member. Example: BC-user_name-BC_domain Prefix that defines an installation User name to use when logging into the JMS server. Zero is a special value. the scheduler waits for a worker member to complete an assigned task. TIBCO BusinessConnect Palette Reference . the member with the greatest scheduler weight takes its place as the new scheduler.

See TIBCO BusinessConnect Trading Partner Administration Guide. If the deployed JMS/JNDI provider(s) requires no authentication with the client. the JMS/JNDIPassword field may be left blank. This can help to reduce the load on JMS providers. See TIBCO BusinessConnect Trading Partner Administration Guide. Table 21. Table 21. Regarding message types that are set on topics and will not need confirmation. JMS. this field can be empty. JNDI Context Factory JNDI Context URL JNDI User Name JNDI Password Topic Connection Factory Queue Connection Factory Auto Confirm The initial context factory class for accessing JNDI. The QueueConnectionFactory object stored in JNDI. Specifies whether inbound JMS messages will be confirmed to the provider automatically (after successfully dispatching them to at least one of the subscribing event sources). TIBCO BusinessConnect business protocols may specify JMS topic transports and expect non-durable receivers on some miscellaneous messages (specified by the AE schemas of these messages) that can be lost without causing problems. Table 21. which means that inbound JMS messages dispatched to BusinessWorks will be acknowledged so that the JMS provider can remove them accordingly. The TopicConnectionFactory object stored in JNDI. messages may be left in the JMS provider's persistent store. JMS. This is the URL to the JNDI service provider. Once this checkbox is selected. See TIBCO BusinessConnect Trading Partner Administration Guide. inbound messages are automatically confirmed. See TIBCO BusinessConnect Trading Partner Administration Guide. Table 21. or the process definition will need to explicitly take care of that by placing a Confirm activity in the process definition and confirming the corresponding event.BCServerConfig 11 | Table 4 Configure the JMS Transport Field JMS Password Explanation Password to use when logging into the JMS server If the JMS provider does not require access control. If the deployed JMS/JNDI provider(s) requires no authentication with the client. consult the corresponding business protocol’s User’s Guide. TIBCO BusinessConnect Palette Reference . Otherwise. JMS. JMS. the JMS/JNDI User Name field may be left blank.

If the secured transport was already selected and the factory field receives an inconsistent value. the palette can create the required queues and topics automatically and dynamically. the user's guides of the specific protocols can provide more guidance. is generally the responsibility of the JMS provider’s administrator. Regarding the requirements of the destinations. the Secured checkbox moves back to the unselected state and the secure JMS transport remains (or becomes) disabled. Secure JMS can only be selected if the TIBCO Enterprise Message Service specific JNDI Context Factory has been specified. the credentials for the JMS server and client identity will be fetched and stored in the project at a specific location. (See the checkbox Auto create destinations on the JMS configuration panel on the shared resource. Upon failure. the starting JMS transport will attempt to create the needed destinations (queues and/or topics) in the specified transport modes. the cause is indicated if available. If privileges allow it. When the dialog box is accepted. Test JMS Connection Click the Test JMS Connection button to test whether a proper connection is established.) If checked. the secure JMS transport will be used. then clicking the “Apply” button will result in the same error. Reconnect Max Duration (mins) Secured Timeout configuration property in minutes both for the TIBCO BusinessConnect server and the TIBCO BusinessConnect palette . an exception will be raised and either the privileges need to be adjusted or the administered objects need to be created manually. a dialog box appears when selecting the box and gives an error.12 | Chapter 1 BusinessConnect Palette Table 4 Configure the JMS Transport Field Auto Create Destination Explanation Managing administered objects. such as JMS topics and queues on the preferred JMS provider. If unsuccessful. Upon a successful connection. a dialog box reports the status and the name/version of the provider with whom the connection has been established. Secure JMS When you click on the Import Selected Business Protocol button and the TIBCO BusinessConnect Palette imports the configuration from the TIBCO BusinessConnect configuration store. TIBCO BusinessConnect Palette Reference . If selected. If the context factory field is empty or it specifies a different provider's factory.

If either the trusted CA certificates or the expected host name do not match. a new folder structure will be created and you need to configure the secure JMS transport as follows: 1. further configuration imports will either update the existing credential objects or add new ones if their names are different: • • If a new certificate has a different issuer and a different serial number from the existing certificate. do the following: 1. as well as reconfiguring or changing the credentials that were configured for the TIBCO BusinessConnect server transport. A New Folder Named BCCredentials is Created TIBCO BusinessConnect palette creates a new folder named BCCredentials. which contains a subfolder called TrustedCerts.BCServerConfig 13 | The retrieved configuration properties can always be overridden on the TIBCO BusinessConnect Palette level using new values. Select or enter data as explained in Table 4. Once this folder structure exists. TIBCO BusinessConnect Palette Reference . Table 5 Configure the Secure JMS Transport Field Verify JMS Server Description If selected. the JMS server's identity (its X509 certificate as well as the specified value in the “Expected JMS Server Host Name” field) will be verified against the data received during the SSL handshake. TIBCO BusinessConnect can establish a JMS connection with any TIBCO Enterprise Message Service server whose credentials are different from the configured properties. 2. If the TIBCO Enterprise Message Service server requires a secure transport. If the certificate name is different. only the existing certificate will be updated. That includes turning on or off the secure transport. This subfolder is used for storing the leaf and CA X509 certificates of the JMS server in PEM format). If this verification is not required. the certificate will not be imported from the configuration store. Configure the JMS Transport. First time when you import a configuration from the TIBCO BusinessConnect configuration store with the secure JMS transport enabled. Continue with entering the fields listed in Table 5. 2. the transport creation fails. then disabling this transport — although possible in the palette — will result in a connection failure when the project is building up the JMS transport at runtime. Configure the Secure JMS Transport To configure the secure JMS transport.

after correcting the JMS problem. both BusinessConnect and BusinessConnect palette need to be restarted. JMS. such as when there is a network failure or the JMS server is down. both BusinessConnect and the BusinessConnect palette will not reestablish the connection. See the corresponding field in TIBCO BusinessConnect Trading Partner Administration Guide. both BusinessConnect and BusinessConnect palette for BusinessWorks make connection to the configured JMS server during startup. section Advanced. This is the value of the common name component of the TIBCO Enterprise Message Service server's leaf certificate. See comments in TIBCO ActiveMatrix BusinessWorks Palette Reference. the common name (CN) value may be any arbitrary string. BusinessConnect will terminate with a warning message. On the BusinessConnect palette. Chapter 9: JMS Palette section Advanced. Also. It is usually the hostname of the resource that is running the TIBCO Enterprise Message Service server. If the connection to the JMS server could not be established during startup. Chapter 9. If it is a test system. Using JMS auto reconnect. both the BusinessConnect server and the BusinessConnect palette will try to establish connection with the JMS server when the connection is down without restarting. Strong Ciphers Only Use Trace Use Debug Expected JMS Server Host name JMS Auto Reconnect for the TIBCO BusinessConnect Palette When JMS is used for private process communication in BusinessConnect. if the connection to the JMS server is established during startup but terminated during runtime. Therefore. no changes in the configuration are needed after the import of the configuration on the palette. JMS Palette. this will happen as follows: TIBCO BusinessConnect Palette Reference . If the credentials are supposed to be identical on both the TIBCO BusinessConnect server and the TIBCO BusinessConnect palette-based private process. See comments in TIBCO ActiveMatrix BusinessWorks Palette Reference.14 | Chapter 1 BusinessConnect Palette Table 5 Configure the Secure JMS Transport Field Trusted JMS Server Certificates Description Reference the trusted folder Users can create arbitrary new folders for referencing the trusted certificates location. which must match the value of this field if the “Verify JMS Server” checkbox is selected. These objects will have to be created and maintained manually. which is enabled by default. Table 21.

To enable or disable Smart Routing.BCServerConfig 15 | • If the JMS server is down or the network connection is down when the palette starts up. Smart Routing for private processes can be configured at two levels: • • Shared resource level Event source level Configure Private Process at the Shared Resource Level To configure a private process for Smart Routing at a shared resource level. the palette will send to and receive messages from BusinessConnect. Open your TIBCO BusinessConnect project in TIBCO Designer. the palette activity will time out and eventsources will no longer be able to receive messages even if the JMS provider comes back up after the timeout. Navigate to the shared resource you want to configure. you can route messages that include specific smart IDs to specific private processes. When the connection is established. perform these steps: 1. • Configure Private Processes for Smart Routing If you have created business rules for Smart Routing through the TIBCO BusinessConnect application within TIBCO Administrator. such as Initiator. If the connection is not established within the specified period of time. a new field SmartID appears. and select it. select or clear the Use Smart ID checkbox. Figure 1 Configure Smart Routing at the Shared Resource Level 4. Once this checkbox is selected. the palette will try to establish connection with the JMS server. 3. If the connection between palette and the JMS server is terminated during runtime. The duration of the initial attempts to establish a valid JMS connection is infinite. the palette will try to establish connection with the JMS server. Type the Smart ID into the field for the messages that you want to be routed to this private process shared resource. 2. TIBCO BusinessConnect Palette Reference .

Navigate to the event source you want to configure.RESPONSE messages that are responses to synchronous (blocking) requests from the BusinessConnect Palette are not published on a Smart ID subject. Click Apply. or Receive Response. To enable or disable Smart Routing. 4.16 | Chapter 1 BusinessConnect Palette Configure Private Process at the Event Source Level 1. and select it. type the desired Smart ID for the messages that you want to be routed to this private process event source. In this case the event source would use the same Smart ID as the shared resource. Subjects on Which Messages are Published For any other private process implementations and/or message types subject to Smart Routing. 6. two new fields appear: — Shared Smart ID — Smart Routing ID Figure 2 Configure Smart Routing at the Event Source Level 5. 2. In this case. such as Receive Misc Msg. This will happen if the checkbox Don’t Wait for Response is cleared (see Don’t Wait for Response). then just enable this check box. the BusinessConnect Palette will automatically associate the reply with the response internally and forward it to the relevant event source. — Smart Routing ID If a user wants to have a different Smart ID at the event source level. Receive Request Notification. 3. If the private process implementation uses the BusinessConnect Palette then INITIATOR. Open your TIBCO BusinessConnect project in TIBCO Designer. select or clear the Use Smart ID checkbox. the subject on which the message is published from BusinessConnect to the private process will always use the following format: TIBCO BusinessConnect Palette Reference . Once this checkbox is selected. Configure the fields as follows: — Shared Smart ID If a user wants to inherit the Smart ID from the shared resource directly into this event source.

For JMS AX./ This task is simple in most cases.BC-SERVER.RESPONDER. there are two cases when users of nested schemas may experience closure conflicts : • • Different operations of the same protocol using the same or overlapping nested schemas. or Different operations of different protocols using the same or overlapping nested schemas In both cases.RosettaNet.installation_name. you should manually delete any closure on either of the operations from the project until TIBCO Designer reports no further closure conflicts..installation_name.REQUEST AX. This applies to the file named rootElement_closureX in the folder BCSchemas/protocol/Operation/.RESPONDER.BC.REQUEST AX.RESPONDER.BCServerConfig 17 | For RV AX. TIBCO BusinessConnect Palette Reference .BC.REQUEST.REQUEST.SMARTID1. Working with Nested Schemas After importing operations into the TIBCO BusinessConnect palette from the configuration store.BC-SERVER.BC.smart_routing_id.standardID. when schemas have a relatively small number of nested schemas.BC.RESPONDER.

Shared Smart ID Smart Routing ID TIBCO BusinessConnect Palette Reference . See BCServerConfig for more information. Configuration Table 6 Receive Misc. the Receive Misc Msg process starter cannot be used for that protocol. If there are no miscellaneous messages for the specified protocol. Type the desired Smart ID into this field in order to have a different Smart ID on the event source level . Event sources that reference a shared resource can inherit the smart ID if you enable Smart Routing for the event source. Not all business protocols support miscellaneous messages. Msg Any message that is not an inbound or outbound request or response is a miscellaneous message. the event source will use the same Smart ID as the shared resource. The messages will be routed to this private process event source. Use the Receive Misc Msg process starter to start a process when a miscellaneous message is received from TIBCO BusinessConnect. You can also override an inherited smart ID by providing a different smart ID in the event source. Msg Configuration Fields Field Name Description Server Details Use Smart Routing Description The name to appear as the label for the activity. Short description of the activity. Select this checkbox to inherit the Smart ID from the shared resource directly into this event source. Provide an identifier for the private process instance. In this case.18 | Chapter 1 BusinessConnect Palette Receive Misc. The BCServerConfig shared configuration resource used to connect to the TIBCO BusinessConnect server. This process starter requires a BCServerConfig shared configuration resource that is configured for a specific protocol.

A message disposition notification (MDN) receipt is a transport level acknowledgement. RosettaNet.RECEIVED JMS subject prefix.INFO. and TIBCO BusinessConnect successfully received and verified the receipt returned by the trading partner. Select one of the available miscellaneous messages from the drop down list.RECEIPT.ERROR. Some of the protocols. In this scenario. such as EZComm and EDI. notification to the Private Process is sent on the following subjects: TIBCO Rendezvous subject prefix.RECEIPT. and some of them do (SOAP. Some miscellaneous messages are related to message disposition notifications. These messages can occur when the AS1.installation_name. Msg 19 | Table 6 Receive Misc.Receive Misc.installation_name. Msg Configuration Fields Field Message Name Description This field contains a dropdown list of the available miscellaneous messages for BCServerConfig selected for the Server Details field above. AS2 or Email transports are used and receipts (MDNs) are utilized.RECEIVED TIBCO BusinessConnect Palette Reference .INFO.standardID. notification to the Private Process is sent on the following subjects: TIBCO Rendezvous subject prefix.RECEIVED An MDNAlertError message is sent to the Private Process in the case when a receipt was requested with an outbound message that was sent to a trading partner.standardID.installation_name. and the trading partner returned a receipt which indicated that the trading partner encountered an error in the outbound message it received. cXML). In this scenario. An MDNAlert message is sent to the Private Process in the case when a receipt was requested with an outbound message that was sent to a trading partner.RECEIPT.installation_name. don’t suppress these messages.RECEIVED JMS subject prefix.RECEIPT.ERROR. Consult documentation for a specific business protocol for more information.

installation_name.RECEIPT. for example.20 | Chapter 1 BusinessConnect Palette Table 6 Receive Misc. notification to the private process is sent on the following subjects: TIBCO Rendezvous subject prefix. Msg Configuration Fields Field Description An MDNResponseAlert message is sent to the private process in the case when all three listed conditions are met: • • BusinessConnect received a receipt request for an inbound document.SENT TIBCO BusinessConnect Palette Reference .installation_name.installation_name.RECEIPT. BusinessConnect returned a receipt to the trading partner indicating the inbound document was received and unpackaged successfully.RECEIPT.INFO.SENT An MDNErrorResponseAlert message is sent to the private process in the following case: • • BusinessConnect receives a receipt request for an inbound document. but BusinessConnect could not successfully verify the signature for the document.standardID.SENT JMS subject prefix.standardID.ERROR. BusinessConnect could successfully unpackage the inbound document for which a receipt was requested. • In this scenario. the signature of the inbound document could be verified if the document was signed.SENT JMS subject prefix. notification to the private process is sent on the following subjects: TIBCO Rendezvous subject prefix.RECEIPT.installation_name. and it returned a receipt to the trading partner indicating the inbound document was received but the signature could not be successfully verified In this scenario.ERROR.INFO.

ERROR.installation_name.installation_name.Receive Misc.installation_name.TIMEOUT. notification to the private process is sent on the following subjects: TIBCO Rendezvous subject prefix.ERROR.ERROR JMS subject prefix. notification to the Private Process is sent on the following subjects: TIBCO Rendezvous subject prefix.standardID.TIMEOUT. but the trading partner did not return a receipt within the receipt timeout period.RECEIPT An ErrorNotify message is sent to the Private Process whenever BusinessConnect encounters an error during the processing of an inbound or outbound message. Msg 21 | Table 6 Receive Misc.RECEIPT JMS subject prefix.installation_name.ERROR TIBCO BusinessConnect Palette Reference .standardID. When an error occurs. In this scenario. Msg Configuration Fields Field Description An MDNTimeout message is sent to the Private Process in the case when a receipt was requested for an outbound document.

The schema that displays is based on the input of the message selected in the Configuration tab for this process starter.22 | Chapter 1 Misc BusinessConnect Palette Table 7 Receive Misc. Custom Id Output The output tab lists output schema information. Process instances whose sequencing key evaluates to the same value will be executed sequentially in the order in which the process instance was created. Msg Misc Fields Field Sequencing Key Description Can contain an XPath expression that specifies which processes should run in order. and it is also available in the $_processContext process variable. TIBCO BusinessConnect Palette Reference . This ID is displayed in the View Service dialog of TIBCO Administrator. Can contain an XPath expression that specifies a custom ID for the process instance.

Pre-configured operations that are available for the protocol associated with the server configuration TIBCO BusinessConnect Palette Reference .RESPONDER.installation_name.installation_name.standardID.Receive Request/Notification 23 | Receive Request/Notification Use the Receive Request/Notification process starter to process an incoming request/reply message forwarded by the TIBCO BusinessConnect server. or to process an incoming notify message forwarded by the TIBCO BusinessConnect server. See BCServerConfig for more information. Receive Request/Notification activity will receive the messages that are published on the following subjects: TIBCO Rendezvous subject prefix.REQUEST JMS subject prefix.REQUEST Configuration Table 8 Receive Request/Notification Configuration Fields Field Name Description Server Details Operation Name Description The name to appear as the label for the activity in the process definition Short description of the activity The BCServerConfig shared configuration resource used to connect to the TIBCO BusinessConnect server.RESPONDER.

• This is particularly useful in cases where the document need not be processed (parsed) immediately in the TIBCO BusinessConnect activity. Checkbox cleared The XML document in the message is treated as a String. the event source will use the same Smart ID as the shared resource.24 | Chapter 1 BusinessConnect Palette Table 8 Receive Request/Notification Configuration Fields Field Parse XML Payload Description • Checkbox selected The document in the inbound or outbound message is parsed and validated according to the corresponding Schema defined for this B2B operation. In this case. a parse /validate task can be used after the event source. In this case. assuming that the operations belong to the same business protocol. Use Smart Routing Provide an identifier for the private process instance. The messages will be routed to this private process event source. If parsing or validation are required for the messages that are received on these wildcard listeners. You can also override an inherited smart ID by providing a different smart ID in the event source. Event sources that reference a shared resource can inherit the smart ID if you enable Smart Routing for the event source. Shared Smart ID Smart Routing ID TIBCO BusinessConnect Palette Reference . Select this checkbox to inherit the Smart ID from the shared resource directly into this event source. no parsing or validation of the message happens at the event source level. If the checkbox Parse XML Payload is cleared. the event sources will list a wild card (“*”) entry in their dropdown list. Type the desired Smart ID into this field in order to have a different Smart ID on the event source level . You can select this entry (“*” ) in order to start receiving multiple operations on the given event source instance.

This ID is displayed in the View Service dialog of TIBCO Administrator. Contain an XPath expression that specifies a custom ID for the process instance. TIBCO BusinessConnect Palette Reference . Custom Id Output The Output tab lists output schema information.Receive Request/Notification 25 | Misc Table 9 Receive Request/Notification Misc Fields Field Sequencing Key Description Contain an XPath expression that specifies which processes should run in order. which is based on the input of the operation selected in the Configuration tab for this activity. Process instances whose sequencing key evaluates to the same value will be executed sequentially in the order in which the process instance was created. and it is also available in the $_processContext process variable.

Pre-configured operations available for the protocol associated with the server configuration TIBCO BusinessConnect Palette Reference . Receive Response activity would receive the messages that are published on the following subjects: TIBCO Rendezvous subject prefix. See BCServerConfig for more information.installation_name.INITIATOR.RESPONSE Configuration Table 10 Receive Response Configuration Fields Field Name Description Server Details Operation Name Description The name to appear as the label for the activity in the process definition Short description of the activity The BCServerConfig shared configuration resource used to connect to the TIBCO BusinessConnect server.26 | Chapter 1 BusinessConnect Palette Receive Response The Receive Response activity is used to receive a response to a previously sent request from the Send Request/Notification activity.standardID.RESPONSE JMS subject prefix.INITIATOR.installation_name.

The messages will be routed to this private process event source. Event sources that reference a shared resource can inherit the smart ID if you enable Smart Routing for the event source. Select this checkbox to inherit the Smart ID from the shared resource directly into this event source. If the checkbox Parse XML Payload is cleared. • Checkbox cleared The XML document in the message is treated as a String. You can select this entry (“*”) in order to start receiving multiple operations on the given event source instance. the event sources will list a wild card (“*”) entry in their dropdown list. If parsing or validation are required for messages that are received on these wildcard listeners.Receive Response 27 | Field Parse XML Payload Description • Checkbox selected The document in the inbound or outbound message is parsed and validated according to the corresponding Schema defined for this B2B operation. This is particularly useful in cases where the document need not be processed (parsed) immediately in the TIBCO BusinessConnect activity. In this case when no parsing or validation of the message will happen at the event source level. Shared Smart ID Smart Routing ID TIBCO BusinessConnect Palette Reference . a parse /validate task can be used after the event source. You can also override an inherited smart ID by providing a different smart ID in the event source. the event source will use the same Smart ID as the shared resource. assuming that the operations belong to the same business protocol. Type the desired Smart ID into this field in order to have a different Smart ID on the event source level . In this case. Use Smart Routing Provide an identifier for the private process instance.

28 | Chapter 1 Misc BusinessConnect Palette Table 11 Receive Response Misc Fields Field Sequencing Key Description Contain an XPath expression that specifies which processes should run in order. TIBCO BusinessConnect Palette Reference . Custom Id Output The output tab lists output schema information. which is based on the output of the operation selected in the Configuration tab for this activity. Process instances whose sequencing key evaluates to the same value will be executed sequentially in the order in which the process instance was created. This ID is displayed in the View Service dialog of TIBCO Administrator. Contain an XPath expression that specifies a custom ID for the process instance. and it is also available in the $_processContext process variable.

Msg 29 | Send Misc. Msg Configuration Fields. Input The input tab lists input schema information. Msg This activity is provided for backward compatibility purposes only. Configuration Table 12 Send Misc.Send Misc. The schema that displays is based on the input of the miscellaneous message selected in the Configuration tab for this activity. TIBCO BusinessConnect Palette Reference . See BCServerConfig for more information. Field Name Description Server Details Message Name Description The name to appear as the label for the activity in the process definition Short description of the activity The BCServerConfig shared configuration resource used to connect to the TIBCO BusinessConnect server. Miscellaneous message types available for the selected protocol of the specified BusinessConnect Connection shared configuration resource. Output This activity requires no output.

You can receive the response to the request on the same activity or in a different process instance by using the Receive Response process starter. • Checkbox selected The document in the inbound or outbound message is parsed and validated according to the corresponding Schema definition defined for this B2B operation. Field Name Description Server Details Operation Name Parse XML Payload Description The name to appear as the label for the activity in the process definition Short description of the activity. the unique transaction ID will be generated regardless of what is provided for the transactionID input field.installation_name. Send Request/Notification would publish the messages on the following subjects: TIBCO Rendezvous subject prefix.INITIATOR. See BCServerConfig for more information. TIBCO BusinessConnect Palette Reference . The BCServerConfig shared configuration resource used to connect to the TIBCO BusinessConnect server. Checkbox cleared Generate Unique Transaction ID If selected.30 | Chapter 1 BusinessConnect Palette Send Request/Notification The Send Request/Notification activity can be used to send an outgoing request/reply message or an outgoing notify message to the TIBCO BusinessConnect server. Pre-configured operations that are available for the protocol associated with the server configuration.REQUEST JMS subject prefix.INITIATOR. This is particularly useful in cases where the document need not be processed (parsed) immediately in the TIBCO BusinessConnect activity. • The XML document in the message is treated as a String.REQUEST Configuration Table 13 Send Request/Notification Configuration Fields.installation_name.standardID.

minutes and seconds. TIBCO BusinessConnect Palette Reference . Refer to the documentation for a specific protocol for more information. This option appears only if the checkbox Don’t Wait for Response is cleared.Send Request/Notification 31 | Field Don’t Wait for Response Response Wait Time Description Specifies that the activity should not wait for a response from the TIBCO BusinessConnect server. This tab is protocol specific. Output The output tab lists output schema information. Input The input tab lists input schema information based on the input of the operation selected in the Configuration tab for this activity. Refer to the documentation for a specific protocol for more information. It lets you specify the exact time to wait for a response in days. This tab is protocol specific. hours.

RESPONSE JMS subject prefix.32 | Chapter 1 BusinessConnect Palette Send Response The Send Response activity sends an outgoing response message to the local TIBCO BusinessConnect server. Short description of the activity. Parse XML Payload • Checkbox selected: When checked. the document in the inbound or outbound message is parsed and validated according to the corresponding Schema definition defined for this B2B operation.installation_name.RESPONSE Configuration Table 14 Send Response Configuration Fields.RESPONDER.RESPONDER.installation_name. This is particularly useful in cases where the document need not be processed (parsed) immediately in the TIBCO BusinessConnect activity. Send Response would publish the messages on the following subjects: TIBCO Rendezvous subject prefix. the XML document in the message is treated as a String. Operation Name Pre-configured operations that are available for the protocol associated with the server configuration.standardID. Only the Request. Field Name Description Server Details Description The name to appear as the label for the activity in the process definition. See BCServerConfig for more information.Response operations will be populated for this activity. TIBCO BusinessConnect Palette Reference . • Checkbox cleared: When this checkbox is cleared. The BCServerConfig shared configuration resource used to connect to the TIBCO BusinessConnect server.

you must set the values for the Server Details and Operation Name fields. If you choose a non-custom request. The schema that displays is based on the input of the operation selected in the Configuration tab for this activity. and a response is sent back to TIBCO BusinessConnect. This is typically used in conjunction with a Receive Request process starter. Output This activity produces no output. TIBCO BusinessConnect Palette Reference . For EZComm. About Schema Validation in EZComm. This tab is protocol specific. the Server Details and Operation Name fields are filled automatically. whereby in the same process definition a request is received. If you choose <Custom Request>. see TIBCO BusinessConnect EZComm Protocol User’s Guide. Refer to the documentation for a specific protocol for more information. some processing occurs. Figure 3 Send Response Configuration Tab Input The input tab lists input schema information.Send Response 33 | Field Request Name Description Receive Request/Notification operations and custom requests.

34 | Chapter 1 BusinessConnect Palette TIBCO BusinessConnect Palette Reference .

Msg 29 Send Request/Notification 30 Send Response 32 customer support xii P process starter Receive Misc. configuration 18 TIBCO BusinessConnect Palette Reference . setting up 10 JMS. Msg configuration fields 18 Receive Request/Notification configuration fields 23 Receive Response 26 Send Misc.| 35 Index A activity Receive Response 26 Send Misc. configuration 5 manage schemas 2 O Oracle client library path usage 5 C configure private processes for smart routing 15 configuring BusinessConnect Server Access 4 Receive Misc. Msg 29 Send Request/Notification 30 Send Response 32 auto confirm. JMS 11 J JMS auto reconnect 14 JMS. Msg. connection transport 10 JMS. Msg 18 Receive Request/Notification 23 Q QOS (quality of service) 8 quality of service (QOS) 8 I implement custom schemas 2 R Receive Misc. test connection 12 M B BCServerConfig 3 BCServerConfig.

output 22 Receive Request/Notification. 28 Receive Request/Notification. configuring BCServerConfig 8 resource BCServerConfig 3 S secure JMS 12 Send Misc. input 29 Send Misc. Misc fields 25.36 | Index Receive Misc. configuration 26 Receive Response. Msg. configuration 30 Send Response. Msg. Msg. configuration 23 Receive Request/Notification. configuration 29 Send Misc. output 28 Rendezvous 5 Rendezvous. Misc fields 22 Receive Misc. configuration 32 Smart ID 7 smart routing 7 support. contacting xii T technical support xii TIBCO_HOME x U using schemas in BusinessConnect 2 TIBCO BusinessConnect Palette Reference . output 25 Receive Response. Msg. output 29 Send Request/Notification. Msg.