Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
SAP
Examples
Software Release 7.2
February 2016
Two-Second Advantage®
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED
OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED
ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED
SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR
ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A
LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE
AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER
LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE
SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE
LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED
IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS
AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN
AGREEMENT TO BE BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright laws and
treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO
Software Inc.
TIBCO, Two-Second Advantage, TIBCO ActiveMatrix Adapter for SAP, TIBCO ActiveMatrix BusinessWorks,
TIBCO ActiveMatrix Service Bus, TIBCO Adapter SDK, TIBCO Administrator, TIBCO Business Studio, TIBCO
Designer, TIBCO Enterprise Message Service, TIBCO Hawk, TIBCO Rendezvous, and TIBCO Runtime Agent are
either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.
Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition
(J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation
in the U.S. and other countries.
All other product and company names and marks mentioned in this document are the property of their
respective owners and are mentioned for identification purposes only.
THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL
OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME
TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC
OPERATING SYSTEM PLATFORM.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS.
CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE
INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE
IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN
THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR
INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING
BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.
Copyright © 1999-2016 TIBCO Software Inc. All rights reserved.
TIBCO Software Inc. Confidential Information
| iii
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
TIBCO ActiveMatrix Adapter for SAP Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Third-Party Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
How to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Chapter 1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Examples Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
BusinessWorks 5 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
BusinessWorks 6 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Prerequisites of Running Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Required Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Importing the Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Starting the EMS Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Preface
Topics
Related Documentation
TIBCO® Adapter SDK This product provides a class library that helps developers
implement an adapter with minimal effort.
TIBCO Business Studio This product provides capabilities that help business analysts
document business processes, solution engineers implement
business processes, and SOA developers create composite
applications.
TIBCO Enterprise Message Service™ This product sends messages from your applications in a
format that conforms to the Java Messaging Service (JMS)
specification.
TIBCO Runtime Agent™ This product is a bundle of TIBCO software and third-party
software that is required to run many TIBCO applications
such as TIBCO ActiveMatrix BusinessWorks, TIBCO
Adapters, and so on.
Third-Party Documentation
You may also find it useful to read the documentation on the following websites:
• http://help.sap.com
This website is the SAP Help Portal where you can find documentation on all
SAP products, including SAP ECC 6.0 releases and SAP NetWeaver. In order
for TIBCO ActiveMatrix Adapter for SAP to exchange data with SAP systems,
you must make configurations in the SAP system to allow for communication
and the exchange of messages to take place. This website offers detailed
information on such configuration.
• http://service.sap.com/instguides
This website is provided by the SAP Support Portal and contains
documentation on installations and upgrades. The documentation available
contains information on components that can be used along with TIBCO
ActiveMatrix Adapter for SAP, and the installation of the Secure Network
Communications (SNC) libraries where security is required between the
adapter and SAP systems.
• http://service.sap.com/connectors
This website provides information on the different types of SAP Connectors
available. TIBCO ActiveMatrix Adapter for SAP is based on the SAP Java
Connector libraries. You can download the latest versions of these libraries
from this website.
Typographical Conventions
Convention Use
ENV_NAME TIBCO products are installed into an installation environment. A product
TIBCO_HOME installed into an installation environment does not access components in other
installation environments. Incompatible products and multiple instances of
the same product must be installed into different installation environments.
An installation environment consists of the following properties:
• Name Identifies the installation environment. This name is referenced in
documentation as ENV_NAME. The default value is TIBCO_HOME.
• Directory The folder into which the product is installed. This folder is
referenced in documentation as TIBCO_HOME.
TIB_ADR3_HOME TIBCO ActiveMatrix Adapter for SAP is installed into a directory within a
TIBCO_HOME directory. This directory is referenced in documentation as
TIB_ADR3_HOME. The default value of TIB_ADR3_HOME depends on the
operating system. For example, on Windows systems, the default value is
C:\tibco\adapter\adr3\ReleaseNumber.
code font Code font identifies commands, code examples, filenames, pathnames, and
output displayed in a command window. For example: Use MyCommand to start
the foo process.
bold code font Bold code font is used in the following ways:
• In procedures, to indicate what a user types. For example: Type admin.
• In large code samples, to indicate the parts of the sample that are of
particular interest.
• In command syntax, to indicate the default parameter for a command. For
example, if no parameter is specified, MyCommand is enabled:
MyCommand [enable | disable].
Convention Use
italic font Italic font is used in the following ways:
• To indicate a document title. For example: See TIBCO ActiveMatrix Adapter
for SAP Concepts.
• To introduce new terms. For example: A portal page may contain several
portlets. Portlets are mini-applications that run in a portal.
• To indicate a variable in a command or code syntax that you must replace.
For example: MyCommand PathName.
Key combinations Key name separated by a plus sign indicate keys pressed simultaneously. For
example: Ctrl+C.
Key names separated by a comma and space indicate keys pressed one after
the other. For example: Esc, Ctrl+Q.
The note icon indicates information that is of special interest or importance, for
example, an additional action required only in certain circumstances.
The tip icon indicates an idea that could be useful, for example, a way to apply
the information provided in the current section to achieve a specific result.
The warning icon indicates the potential for a damaging situation, for
example, data loss or corruption if certain steps are taken or not taken.
Convention Use
[ ] An optional item in a command or code syntax.
For example:
MyCommand [optional_parameter] required_parameter
| A logical OR that separates multiple items of which only one may be chosen.
For example, you can select only one of the following parameters:
MyCommand param1 | param2 | param3
In the next example, the command requires two parameters. The first parameter
can be either param1 or param2 and the second can be either param3 or param4:
MyCommand {param1 | param2} {param3 | param4}
In the next example, the command can accept either two or three parameters.
The first parameter must be param1. You can optionally include param2 as the
second parameter. And the last parameter is either param3 or param4.
MyCommand param1 [param2] {param3 | param4}
Chapter 1 Introduction
This chapter describes the example projects packaged with TIBCO ActiveMatrix
Adapter for SAP and preparation you need to do before running the sample
projects.
Topics
Examples Overview
TIBCO ActiveMatrix Adapter for SAP provides seven examples to show how the
adapter interacts with the SAP system.
After installing TIBCO ActiveMatrix Adapter for SAP, navigate to the
TIBCO_ADR3_HOME\examples directory. You can find two example folders. The
ActiveMatrix BusinessWorks 5 examples are in the BusinessWorks5 folder. And
the ActiveMatrix BusinessWorks 6 examples are in the BusinessWorks6 folder.
BusinessWorks 5 Examples
You can find the following examples in the BusinessWorks5 folder:
• Dynamic Logon and External Commit
This example shows how to use the dynamic logon and the Inbound BAPI
transaction support features provided by the adapter in TIBCO Designer.
• Inbound IDoc with Inbound BAPI
This example shows how to use the Subscription Service service and
Request-Response Service service in TIBCO Designer.
• Outbound IDoc with Remote TIDManager
This example shows how to use the remote TIDManager instance and how to
use the Publication Service service in multiple adapter instances in TIBCO
Designer.
• Outbound RFC with Inbound BAPI
This example shows how to use the Request-Response Invocation Service
service and Request-Response Service service in TIBCO Designer.
• IDocFormat Publishing Mode
This example shows how to use the adapter for sending and receiving IDocs
without any significant mapping, and the usage of JMS properties for the
Publication Service service and the IDoc confirmation.
• Salesforce
— Salesforce Opportunity to SAP Order
This example shows how to set up communication between the SAP
system and Salesforce.com by using the adapter in TIBCO Designer.
Before running these examples, you need to import the example projects into
TIBCO Designer. See Importing Examples to TIBCO Designer on page 5.
BusinessWorks 6 Example
You can find the following example in the BusinessWorks6 folder:
• Saleforce
— Salesforce Opportunity to SAP Order
This example shows how to set up communication between the SAP
system and Salesforce.com by using the adapter in TIBCO Business Studio.
Before running this example, you need to import the example project into TIBCO
Business Studio. See Importing the Example to TIBCO Business Studio on page 5.
Before running the examples, you need to install the required software, import the
examples and start the TIBCO Enterprise Message Service (EMS) server.
For the required software, see Required Software on page 4.
For how to import examples and start the EMS server, see Importing the
Examples on page 4 and Starting the EMS Server on page 6.
Required Software
You need to install the following software to run the ActiveMatrix BusinessWorks
5 examples:
• TIBCO ActiveMatrix Adapter for SAP
• TIBCO ActiveMatrix BusinessWorks 5.x
• TIBCO Runtime Agent
• TIBCO ActiveMatrix BusinessWorks™ Plug-in for Salesforce.com
You need to install the following software to run the ActiveMatrix BusinessWorks
6 example:
• TIBCO ActiveMatrix Adapter for SAP
• TIBCO ActiveMatrix BusinessWorks 6.x
• TIBCO ActiveMatrix Adapter Framework
• TIBCO Runtime Agent
• TIBCO ActiveMatrix BusinessWorks Plug-in for Salesforce.com
4. In the Import Projects window, click Select archive file. Then click Browse
next to the Select archive file field to locate the example to be imported.
The example is located in the
TIBCO_ADR3_HOME\examples\BusinessWorks6\Salesforce directory.
5. Click Finish.
The selected example is displayed in TIBCO Business Studio.
Topics
Example Overview
However, these two processes use different function models and mechanisms to
commit and roll back a sales order in the SAP system:
• In the Create SalesOrder process, if the adapter fails to create a sales order, the
adapter invokes the BAPI_TRANSACTION_ROLLBACK function module to roll
back the sales order.
Otherwise, the adapter invokes the BAPI_TRANSACTION_COMMIT function
module to commit the created sales order.
• In the Create SaleOrder with Auto Commit process, if the adapter fails to
create a sales order, the sales order is automatically rolled back without the
invocation of any function module.
Otherwise, the BAPI_TRANSACTION_COMMIT function module is automatically
invoked to commit the created sales order.
— UDConnection Client
— UDConnection\ConnectionType
— UDConnection\GroupName
— UDConnection\Language
— UDConnection\MsgServer
— UDConnection\Password
— UDConnection\SNC_lib
— UDConnection\SNC_mode
— UDConnection\SNC_partnername
— UDConnection\SNC_qop
— UDConnection\SNC_bSSO
— UDConnection\SNC_ssoSend
— UDConnection\SNC_x509
— UDConnection\SystemName
— UDConnection\SystemNumber
— UDConnection\UserName
— JMSProviderUrl
— ASAP_HOME
ASAP_HOME is the home directory where you install the adapter. For
example, E:\TIBCO_HOME\adapter\adr3\7.2.
4. Click OK.
5. In the Project panel, click the adapter instance, and then, in the Configuration
panel, click the Design-Time Connection tab.
6. Click Test Connection to validate your connection.
Ensure that you have configured the example, as described in Configuring the
Example on page 9.
To run the example, complete the following tasks:
• Task A, Start the Adapter, page 11
• Task B, Run the Process, page 11
Expected Results
DynamicLogonWithExternalCommit directory.
When the process is finished, all the results of creating a sales order are written to
the output file named OrderStatus.xml. If the creation is successful, you can also
check the sales order information in the SAP system.
You can also check the symbolic destination of the active connection in the SAP
server or check the adapter log file to get the dynamic connection result.
The log file is located in the TIBCO_ADR3_HOME\logs directory.
Topics
Example Overview
— Client
— GatewayService
— Password
— SystemNumber
— UserName
— JMSProviderUrl
— ASAP_HOME
ASAP_HOME is the home directory where you install the adapter. For example,
E:\TIBCO_HOME\adapter\adr3\7.2.
4. Click OK.
5. (Optional) Change the Inbound TID management mode:
a. In the Project panel, click the R3AdapterConfiguration adapter instance.
b. In the Configuration panel, click the Adapter Services tab.
c. Change the TID management mode.
Ensure that the TIDmanager clients in all the adapter instances match the TID
manager server in the TIDManager instance, when you select the Remote TID
management mode.
6. In the Project panel, click the adapter instance, and then, in the Configuration
panel, click the Design-Time Connection tab.
7. Click Test Connection to validate your connection.
Ensure that you have configured the example, as described in Configuring the
Example on page 15.
To run the example, complete the following tasks:
• Task A, Start the Adapter, page 16
• Task B, Run the Process, page 16
If you have configured the adapter instance with the remote Inbound
TIDManagement, before start the adapter, first start the TIDManager.
Expected Results
Topics
Example Overview
— Client
— GatewayService
— Password
— SystemNumber
— UserName
— JMSProviderUrl
— ASAP_HOME
ASAP_HOME is the home directory where you install the adapter. For example,
E:\TIBCO_HOME\adapter\adr3\7.2.
4. Click OK.
5. In the Project panel, click the adapter instance, and then, in the Configuration
panel, click the Design-Time Connection tab.
6. Click Test Connection to validate your connection.
Ensure that you have configured the example, as described in Configuring the
Example on page 21.
To run the example, complete the following tasks:
• Task A, Start the Adapter and TIDManager, page 22
• Task B, Run the Process, page 22
4. Log on to the SAP system and send an IDoc to start the process:
— To start the MATMAS process:
Send a MATMAS01 IDoc using ALE/IDoc messaging and execute the SAP
transaction BD10.
— To start the DEBMAS process:
Send a DEBMAS01 IDoc using ALE/IDoc messaging and execute the SAP
transaction BD12.
— To start the CREMAS process:
Send a CREMAS01 IDoc using ALE/IDoc messaging and execute the SAP
transaction BD14.
The process is triggered automatically.
Expected Results
OutboundIDocWithRemoteTIDManager directory:
• The CREMAS_IDocNumber.xml file that contains the Vendor Master Data is
created, when the CREMAS process completed.
• The DEBMAS_IDocNumber.xml file that contains the Customer Master Data is
created, when the DEBMAS process completed.
• The MATMAS_IDocNumber.xml file that contains the Material Master Data is
created, when the MATMAS process is completed.
Topics
Example Overview
When the value of the EVENTID parameter in the incoming event is neither
CUSTOMER nor VENDOR, the Request-Response Invocation Service service receives
an error message.
— GatewayHost
— ProgramID
— Client
— GatewayService
— Password
— SystemNumber
— UserName
— JMSProviderUrl
— ASAP_HOME
ASAP_HOME is the home directory where you install the adapter. For example,
E:\TIBCO_HOME\adapter\adr3\7.2.
4. Click OK.
5. In the Project panel, click the adapter instance, and then, in the Configuration
panel, click the Design-Time Connection tab.
6. Click Test Connection to validate your connection.
Ensure that you have configured the example, as described in Configuring the
Example on page 27.
To run the example, complete the following tasks:
• Task A, Start the Adapter, page 28
• Task B, Run the Process, page 28
Expected Results
• The SAP system receives an error message when the value of the EVENTID
parameter is neither VENDOR nor CUSTOMER.
Topics
Example Overview
— Client
— GatewayHost
— GatewayService
— Password
— ProgramID
— SystemNumber
— UserName
— ASAP_HOME
ASAP_HOME is the home directory where you install the adapter. For example,
E:\TIBCO_HOME\adapter\adr3\7.2.
4. Click OK.
5. In the Project panel, click the adapter instance, and then, in the Configuration
panel, click the Design-Time Connection tab.
6. Click Test Connection to validate your connection.
Ensure that you have configured the example, as described in Configuring the
Example on page 33.
To run the example, complete the following tasks:
• Task A, Start the Adapter, page 34
• Task B, Run the Process, page 34
Expected Results
Topics
Example Overview
• SyncOpportunityProcess process
The workflow action is triggered to send outbound messages to the process
when you create a record of the Opportunity object with the stage of Closed
Won or edit a record of the Opportunity object by setting the stage to Closed
Won in the Salesforce.com.
The adapter invokes the BAPI_SALESORDER_CREATEFROMDAT1 function
module to create a sales order in the SAP system based on the outbound
messages. When an error occurs in the invocation, this error is written to the
OrderStatus.xml file.
If the adapter fails to create the sales order, the adapter invokes the
BAPI_TRANSACTION_ROLLBACK function module to roll back the sales order.
Otherwise, the adapter invokes BAPI_TRANSACTION_COMMIT function module
to commit the created sales order. Then update the opportunity object in the
Salesforce.com with the sales order number.
• OrderDeliveryProcess process
This process is triggered when the adapter publishes a DESADV05 IDoc
containing the Opportunity ID. This process updates the Opportunity object
in Salesforce.com with the SAP delivery number as the tracking number.
— Client
— GatewayHost
— Password
— ProgramID
— SystemNumber
— UserName
— GatewayService
— Salesforce.connection\salesforce.password
— Salesforce.connection\salesforce.username
— Salesforce.connection\serverURL
— ASAP_HOME
ASAP_HOME is the home directory where you install the adapter. For example,
E:\TIBCO_HOME\adapter\adr3\7.2.
4. Click OK.
5. In the Project panel, click the adapter instance, and then, in the Configuration
panel, click the Design-Time Connection tab.
6. Click Test Connection to validate your connection.
4. Click Save.
Ensure that you have configured the example, as described in Configuring the
Example on page 39.
To run the example, complete the following tasks:
• Task A, Start the Adapter, page 41
• Task B, Run the Process, page 42
Expected Results
You can view the results of the ActiveMatrix BusinessWorks 5 example in the
TIBCO_ADR3_HOME\examples\BusinessWorks5\Salesforce\
SalesforceOpportunityToSAPOrder directory:
When the SyncOpportunityProcess process is finished, all the results of creating a
sales order are written to the OrderStatus.xml file. If the creation is successful,
you can also update the Salesforce.com to check the sales order number.
When the OrderDeliveryProcess process is finished, the sales order information is
written to the DOCNUM.xml file. You can update the Salesforce.com to check the
tracking number.
For the ActiveMatrix BusinessWorks 6 example, there is no ouput file. You can
update Salesforce.com to check the sales order number or the the tracking
number, when the processes are finished.
Index
D
documentation
third-party vii
TIBCO ActiveMatrix Adapter for SAP vi
TIBCO products vi
dynamic logon 7
E
ENV_NAME ix
example
configuration 9, 15, 21, 27
description 8, 14, 20, 26
prerequisites 4
procedure 11, 16, 22, 28
results 12, 17, 24, 30
T
TIB_ADR3_HOME ix
TIBCO support
contacting xii
TIBCO documentation xii
TIBCOmmunity xii
TIBCO_HOME ix