Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 1 Introduction : Overview

Overview
The following examples demonstrate the integration between the adapter and TIBCO ActiveMatrix BusinessWorks. The different communication paradigms and common business objects have been chosen to build an end-to-end enterprise wide integration and demonstrate the adapter capabilities.
The following table shows the communication paradigm, business object and the corresponding adapter service used to develop the examples.
The TIBCO ActiveMatrix BusinessWorks examples use both the transport types, RV and JMS. The procedure to arrive at the configurations using TIBCO Rendezvous is similar to that of configurations using JMS.
All examples use FML32 as buffer type.
All examples provided are for the adapter in workstation client mode. (To work with these examples in the native mode, WSNADDR should not be set. The ubbconfig file has to be modified so that the WSNADDR section should not be present)
Before running the examples, ensure that you change the paths of the input and output XMLs to the appropriate locations according to your TIBCO_HOME installation.
The example repositories have embedded TIBCO ActiveMatrix BusinessWorks processes.
Following is provided as part of each example:
The Tuxedo FML32 header files
ubbconfig files
Batch files to compile and boot the Tuxedo service
Using TIBCO ActiveMatrix BusinessWorks
If you are using the adapter with TIBCO ActiveMatrix BusinessWorks, the following software must be installed to run the examples. For the supported versions of the listed products, refer to TIBCO ActiveMatrix Adapter for Tuxedo readme.txt.
Tuxedo (For a list of supported Tuxedo versions, refer to TIBCO ActiveMatrix Adapter for Tuxedo Installation)
TIBCO Enterprise Message Service must be installed to run examples that use JMS as the transport. The EMS server must be running and accessible to the machine on which the adapter is installed.
The TIBCO ActiveMatrix BusinessWorks examples use TIBCO Designer to create an Enterprise Archive File (EAR). One of the examples explains deploying the EAR file using TIBCO Administrator Enterprise Edition. All the other examples use the Adapter tester functionality of TIBCO Designer to run and test the examples.
In TIBCO Administrator, make sure all software components needed by the adapter instance are installed on one or more machines that are part of a TIBCO Administration Domain and that the software is registered in the domain.
These topics are explained in the TIBCO Administrator documentation set.
Working with dat files in TIBCO Designer
You cannot directly open a dat file in TIBCO Designer and make modifications to the configurations. To do this, complete the following steps:
1.
a.
b.
Then click the Convert DAT to Files icon. In the window that is displayed, browse and select the dat file you wish to convert to a multi-file project. Click OK.
2.
Click the Open existing project icon from the first TIBCO Designer screen. Browse to the directory where the converted multi-file project is saved.
3.
Export the multi-file project to a dat. Select Project>Export Full Project from the menu. Browse and select the location of the directory you wish to save the dat file to. Ensure that the directory is different from the multi-file project. Enter the name of the project and click OK.
Location and Directory Structure
The samples are available in the following location of the adapter installation.
TIBCO_HOME\adapter\adtuxedo\version_number\examples
The directory structure is shown next.
Figure 1 Examples Directory Structure
For better organization the examples have been supplied in the given structure. Tuxedo imposes a limit on the length of characters for the variables that are set in the ubbconfig file. So before running any example, make a copy of the complete examples directory to a different location, which meets Tuxedo’s character length limits, modify as required and run them from that location.

Copyright © TIBCO Software Inc. All Rights Reserved