tibco adapter™ for ejb · pdf filebea weblogic application server 7.0 and bea weblogic...

TIBCO Adapter™ for EJB

Examples GuideSoftware Release 5.3December 2006

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 TIBCO ADAPTER FOR EJB USER’S GUIDE). 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, Information Bus, The Power of Now, TIBCO Adapter, TIBCO Rendezvous, TIBCO Designer, TIBCO ActiveEnterprise, TIBCO Administrator, TIBCO Hawk, and TIBCO Enterprise 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. Please 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-2006 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiTIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiOther TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiThird Party Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

How to Contact TIBCO Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Chapter 1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Using TIBCO BusinessWorks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Using TIBCO IntegrationManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Example Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Basic Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Business Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2 Deploying and Running the Basic Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Before Starting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Setting Up the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Publication Service Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Subscription Service Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Standalone Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Inbound Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Request-Response Server Service Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Standalone Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Inbound Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Request-Response Invocation Service Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 3 Running the Preconfigured Business Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Deploying the Examples to Run with TIBCO IntegrationManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Example Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Setting Up the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Deploying the Examples to Run with TIBCO BusinessWorks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Example Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Setting Up the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

TIBCO Adapter for EJB Examples Guide

iv | Contents

Employee Business Object Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Publish an Employee Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Insert or Update an Employee Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Get an Employee Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Delete an Employee Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Purchase Order Business Object Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Insert or Update a Purchase Order Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Get a Purchase Order Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Delete a Purchase Order Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Customer Party Business Object Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Publish a Customer Party Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Sales Order Business Object Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Insert or Update a Sales Order Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Get a Sales Order Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Delete a Sales Order Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Item Master Business Object Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Publish an Item Master Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Insert or Update an Item Master Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Get an Item Master Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Delete an Item Master Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Appendix A Setting Up the Environment to Run the Basic Tests . . . . . . . . . . . . . . . . . . . . . . . 57

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Starting the Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Modifying the Repository URL, Configuration URL and TRA File Name of the Connector Configuration . . . . . . 60BEA WebLogic Application Server 7.0 and BEA WebLogic Application Server 7.0 with SP2, SP4, SP5, SP6, and SP7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60BEA WebLogic Application Server 8.1, BEA WebLogic Application Server 8.1 with SP1, SP2, SP3, SP4, SP5, and SP6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61BEA WebLogic Application Server 9.0, 9.1, and 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62IBM WebSphere 5.1, 6.0 6.0.2, and 6.1 Application Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Sun Java System Application Server Platform Edition 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Sun Java System Application Server Platform Edition 8.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Oracle 9i Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Oracle 10g Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67JBoss 3.2.3 Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68JBoss 4.0.0, 4.0.1, 4.0.2, 4.0.3, and 4.0.4 Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Preparing the Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71BEA WebLogic Application Server 6.1 with SP1, SP2, or SP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71BEA WebLogic Application Server 7.0 and BEA WebLogic Application Server 7.0 with SP2, SP4, SP5, SP6, and SP7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74BEA WebLogic Application Server 8.1, BEA WebLogic Application Server 8.1 with SP1, SP2, SP3, SP4, SP5, and SP6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78


Contents | v

BEA WebLogic Application Server 9.0, 9.1, and 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81IBM WebSphere 5.1 Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85IBM WebSphere 6.0, 6.0.2, and 6.1 Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Sun Java System Application Server Platform Edition 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Sun Java System Application Server Platform Edition 8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Oracle 9i Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Oracle 10g Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93JBoss 3.2.3 Application Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94JBoss 4.0.0, 4.0.1, 4.0.2, 4.0.3, and 4.0.4 Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Deploying the Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99BEA WebLogic Application Server 6.1 with SP1, SP2, or SP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99BEA WebLogic Application Server 7.0 and BEA WebLogic Application Server 7.0 with SP2, SP4, SP5, SP6, and SP7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100BEA WebLogic Application Server 8.1 and BEA WebLogic Application Server 8.1 with SP1, SP2, SP3, SP4, SP5, and SP6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101BEA WebLogic Application Server 9.0, 9.1, and 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102IBM WebSphere 5.1 Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103IBM WebSphere 6.0 and 6.0.2 Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Sun Java System Application Server Platform Edition 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Sun Java System Application Server Platform Edition 8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Oracle 9i Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Oracle 10g Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109JBoss 3.2.3 Application Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110JBoss 4.0.0, 4.0.1, 4.0.2, 4.0.3, and 4.0.4 Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Preparing the Test or Example Beans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Java 2 Platform, Enterprise Edition Application Server 1.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113BEA WebLogic Application Server 6.1 with SP1, SP2, or SP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113BEA WebLogic Application Server 7.0 and BEA WebLogic Application Server 7.0 with SP2, SP4, SP5, SP6, and SP7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113BEA WebLogic Application Server 8.1, BEA WebLogic Application Server 8.1 with SP1, SP2, SP3, SP4, SP5, and SP6, and BEA WebLogic Application Server 9.0, 9.1, and 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114IBM WebSphere5.1 Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114IBM WebSphere 6.0 and 6.0.2 Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Sun Java System Application Server Platform Edition 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Sun Java System Application Server Platform Edition 8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Oracle 9i Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Oracle 10g Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115JBoss 3.2.3 Application Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116JBoss 4.0.0, 4.0.1, 4.0.2, 4.0.3, and 4.0.4 Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Deploying the Test or Example Beans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Java 2 Platform, Enterprise Edition Application Server 1.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117BEA WebLogic Application Server 6.1 with SP1, SP2, or SP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118BEA WebLogic Application Server 7.0 and BEA WebLogic Application Server 7.0 with SP2, SP4, SP5, SP6, and SP7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118BEA WebLogic Application Server 8.1 and BEA WebLogic Application Server 8.1 with SP1, SP2, SP3, SP4, SP5, and SP6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119


vi | Contents

BEA WebLogic Application Server 9.0, 9.1, and 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120IBM WebSphere 5.1, 6.0, 6.0.2, and 6.1 Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Sun Java System Application Server Platform Edition 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Sun Java System Application Server Platform Edition 8.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Oracle 9i Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Oracle 10g Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123JBoss 3.2.3 Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124JBoss 4.0.0, 4.0.1, 4.0.2, 4.0.3, and 4.0.4 Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124


| vii

Preface

TIBCO Adapter™ for EJB is a bi-directional gateway between Enterprise Java Beans and the TIBCO environment. It enables data to be pushed, both in to, and out of, an application server.

The adapter installation includes a set of basic examples and a set of business scenarios, both of which are designed to help you understand the use of the adapter.

Topics

• Related Documentation, page viii

• How to Contact TIBCO Customer Support, page xi


viii | Related Documentation

Related Documentation

This section lists documentation resources you may find useful.

TIBCO Product DocumentationThe following documents form the TIBCO Adapter for EJB documentation set:

• TIBCO Adapter Concepts: Read this manual to gain an understanding of adapters in general. You can apply concepts learned from this manual while using the adapter.

• TIBCO Adapter for EJB User’s Guide: This manual explains concepts relating to the adapter and the applications with which it interacts. It includes installation, configuration, and deployment information.

• TIBCO Adapter for EJB Examples Guide: Read this manual to work through the examples provided with the adapter.

• TIBCO Adapter for EJB Release Notes: Read this document for information about new features, deprecated features, and open and closed issues.

• README for TIBCO Adapter for EJB: Read this document to get information on the current release version, supported platforms, and required software.

Other TIBCO Product DocumentationYou may find it useful to read the documentation for the following TIBCO products. Note that only books that relate to the adapter are listed. Each of the books is available from the doc directory in the product’s installation area.

You may find it useful to read the documentation for the following TIBCO products. Note that only books that relate to adapters are listed. Each of the books is available from the doc directory in the product’s installation area.• TIBCO BusinessWorks™ Software

— TIBCO BusinessWorks Concepts

— TIBCO BusinessWorks QuickStart

— TIBCO BusinessWorks Business Palette Reference

— TIBCO BusinessWorks Process Design Guide

— TIBCO BusinessWorks Error Codes

— TIBCO BusinessWorks Release Notes


Preface | ix

• TIBCO Designer™ software:

— TIBCO Designer User’s Guide

— TIBCO Designer Palette Reference

— TIBCO Designer Release Notes

• TIBCO Administrator™ software:— TIBCO Administrator User’s Guide

— TIBCO Administrator Server Configuration Guide

— TIBCO Administrator Release Notes

• TIBCO IntegrationManager™ software:

— TIBCO IntegrationManager Concepts

— TIBCO IntegrationManager Administrator’s Guide

— TIBCO IntegrationManager Process Design Guide

— TIBCO IntegrationManager Reference

— TIBCO IntegrationManager Release Notes

• TIBCO Rendezvous™ software:

— TIBCO Rendezvous Concepts

— TIBCO Rendezvous Administration

— TIBCO Rendezvous Configuration Tools

• TIBCO Enterprise Message Service™ software:

— TIBCO Enterprise Message Service User’s Guide

— TIBCO Enterprise Message Service Installation

— TIBCO Enterprise Message Service Application Integration

— TIBCO Enterprise Message Service Release Notes

• TIBCO Hawk® software:

— TIBCO Hawk Installation and Configuration

— TIBCO Hawk Administrator’s Guide

• TIBCO Adapter SDK

— TIBCO Adapter SDK Concepts


x | Related Documentation

• TIBCO Runtime Agent

— TIBCO Runtime Agent Release Notes

— TIBCO Runtime Agent Installation

— TIBCO Runtime Agent Domain Utility User’s Guide

— TIBCO Runtime Agent Upgrading to Release 5.4

Third Party DocumentationSeveral products from Sun Microsystems, Inc. are used with the adapter. For information on EJB, J2EE, and JRE, see the relevant documentation provided by Sun at http://www.sun.com.

Additionally, if you have installed any third-party application server, you must obtain the relevant installation, configuration, and usage documentation from that third-party.


Preface | xi

How to Contact TIBCO Customer Support

For comments or problems with this manual or the software it addresses, please contact TIBCO Support Services as follows.

• For an overview of TIBCO Support Services, and information about getting started with TIBCO Product Support, visit this site:

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

• If you already have a valid maintenance or support contract, visit this site:

http://support.tibco.com

Entry to this site requires a username and password. If you do not have a username, you can request one.


xii | How to Contact TIBCO Customer Support


| 1

Chapter 1 Introduction

The adapter installation includes a set of basic examples and a set of pre configured complex business scenarios that demonstrate how the adapter enables communications between the TIBCO world (adapter services) and application servers (EJBs). These examples are located in the examples subdirectory of the adapter installation.

Chapter 2 of this document describes the basic examples (also called basic tests) that diagnose the rudimentary functionality of the adapter and demonstrate its use in primitive scenarios.

Chapter 3 of this document describes the business scenarios that demonstrate the use of the adapter in complex, real-world scenarios.

This document also explains how both sets of examples can be configured to use one or more of the following:

• TIBCO Administrator

• TIBCO BusinessWorks

• TIBCO IntegrationManager

• TIBCO Rendezvous

Topics

• Overview, page 2

• Example Description, page 4

For version number of the following TIBCO Software to be used, see TIBCO Adapter for EJB Readme.txt


2 | Chapter 1 Introduction

Overview

The examples shipped with TIBCO Adapter for EJB are designed to help you become familiar with the different ways in which the adapter can be used to enable interactions between TIBCO IntegrationManager or TIBCO BusinessWorks, and EJBs deployed in an application server.

When the examples are run, the activities performed during the interactions can be viewed on the TIBCO IntegrationManager or TIBCO BusinessWorks console. Also, for your convenience, html pages that display the relevant data have been provided along with the pre configured business scenarios.

The basic tests demonstrate the use of the adapter with the publication, subscription, request-response invocation, and request-response server services. For more details on these examples, and how they can be applied to real-world scenarios, see Deploying and Running the Basic Tests on page 13.

The business scenarios demonstrate the use of the adapter with the publication and request-response services. The publication service is used to demonstrate a typical database Sync operation, and the request-response server service is used to demonstrate database Insert-Update, Delete, and Get operations. For more details on these scenarios, and how they can be applied to real-world scenarios, see Running the Preconfigured Business Scenario on page 27.

To run these examples:

• You must be familiar with TIBCO concepts and the working of TIBCO infrastructure components.

• You must be familiar with J2EE, EJB, JMS, and Java Connector Architecture concepts.

• If you are running the TIBCO BusinessWorks examples, you must be familiar with TIBCO Administrator and TIBCO BusinessWorks.

• If you are running the TIBCO IntegrationManager examples, you must be familiar with the working of TIBCO IntegrationManager.

Using TIBCO BusinessWorksIf you are using the adapter with TIBCO BusinessWorks, the following software must be installed to run the examples:

• TIBCO BusinessWorks


• TIBCO Adapter for EJB


Overview | 3

• IBM WebSphere Application Server


The TIBCO BusinessWorks examples use TIBCO Designer to create an Enterprise Archive File (EAR) and TIBCO Administrator to deploy the EAR file.

In TIBCO Administrator, make sure all software components needed by the adapter instance are installed on one or more machines that are part of the TIBCO Administration Domain and that the software is registered in the domain.

• Use the TIBCO Domain Utility to add a machine to a TIBCO Administration Domain.

• In TIBCO Administrator, use the Resource Management>Machines console to register software.

These topics are explained in the TIBCO Administrator documentation set.

Using TIBCO IntegrationManagerIf you are using the adapter with TIBCO IntegrationManager, the following software must be installed to run the examples:

• TIBCO IntegrationManager


• TIBCO Adapter for EJB

• IBM WebSphere Application Server


If you are using TIBCO Administrator, you deploy by editing the adapter’s properties files and start and stop the adapter on the command line. The TIBCO IntegrationManager examples are deployed using this method.



Example Description

Adapter examples use the TIBCO Rendezvous ticket from the PATH variable that points to your TRA location. This ticket expires after a set duration (1 hour). For details on the License Expiry message, see Appendix A in TIBCO Rendezvous Concepts.

If you have a permanent TIBCO Rendezvous license, make sure this ticket file is in your path. To upgrade your temporary TIBCO Rendezvous license, see Licensing Information in the TIBCO Rendezvous Administration Guide.

The TIBCO Adapter for EJB installation includes the following examples:

• Basic Tests

• Business Scenarios

Basic TestsThe basic tests are a set of examples that demonstrate the use of the adapter in four main modes of operation— the publication, subscription, request-response invocation, and request-response server services. They diagnose the rudimentary functionality of the adapter and demonstrate its use in primitive scenarios. For details see Prerequisites on page 58 and Deploying and Running the Basic Tests on page 13.

When installed, the basic tests are organized as follows:

A description of each basic test scenario is given below.

Publication Service

The files for this test are located in the <ADEJB_HOME>\examples\publish folder.


Example Description | 5

Description/Purpose

This basic example demonstrates and tests the ability of the connector to publish EJB data originating from an application server, onto the TIBCO infrastructure.

The publication service test shows a thin Java client — EJBPublisherClient — making a call to an EJB — Publish_CustomerBean — via Remote Method Invocation (RMI), which broadcasts a message to the TIBCO environment, using the TIBCO J2EE Connector library.

Figure 1 Publisher Block Diagram

Typical Real-World Usage Scenario

For example, the publication service (connector) can be used to publish stock quotes in a real-time environment. An EJB deployed in an application server reads stock quotes from a backend system, such as a database and pushes the quotes to the connector. The connector in turn, transforms the data and publishes the quotes to the TIBCO infrastructure, such as TIBCO IntegrationManager or TIBCO BusinessWorks.

Subscription Service

The subscription service can be tested for two scenarios: Stand-alone adapter component. and inbound connector component.

Standalone adapter component—The files for this test are located in the <ADEJB_HOME>\examples\subscribe\adapter folder.

Inbound adapter component—For using inbound connector component, application server must be JCA 1.5 compliant. Files for this test are located in the <ADEJB_HOME>\examples\subscribe\connector folder.

The files for this test are located in the <ADEJB_HOME>\examples\subscribe folder.

RMIEJBPublisherClient

Publish_BRFCKNA1Bean

Con

nect

or

AESubscriber

TIBC

O M

essa

ging

Messages Messages

EJB Container

Repository Server

(ejb_sample)



Description/Purpose

This basic example demonstrates and tests the ability of the adapter to subscribe to TIBCO ActiveEnterprise data originating from the TIBCO infrastructure, and push it into an EJB residing on an application server.

The subscription service test shows an incoming TIBCO ActiveEnterprise message being received by the adapter process, which in turn calls an EJB deployed in the application server — Subscribe_CustomerBean — via Remote Method Invocation and sends the data to the EJB container.

Figure 2 Subscriber using standalone adapter block diagram

Figure 3 Subscriber using inbound connector block diagram


TIBCO Adapter for EJB

RMI

TIBC

O M

essa

ging AEPublisher

EJB Container

Subscribe_BRFCKNA1Bean

Messages

Repository Server

(ejb_sample)

Subscribe_Customer MDB

Con

nect

or

AEPublisher

TIBC

O M

essa

ging

Messages Messages

EJB Container

Repository Server

(ejb_sample)



For example, the subscription service (adapter) can be used to update an event database in a real-time environment. An application, such as TIBCO Adapter for Files, may read events from a flat file and push each event into the TIBCO infrastructure. The adapter subscribes to the incoming events, transforms the data, and pushes them to an EJB deployed in an application server. The EJB then updates the event database.

Request-Response Server Service

The files for this test are located in the <ADEJB_HOME>\examples\rpc\adapter folder.

This test can be executed in two ways:

• Using standalone adapter component: The files for this test are located in the <ADEJB_HOME>\examples\rpc\adapter folder.

• Using inbound connector component: For using inbound connector component, application server must be JCA 1.5 compliant. Files for this test are located in the <ADEJB_HOME>\examples\rpc\connector\inbound folder.

Description/Purpose

This basic example demonstrates and tests the ability of the adapter to behave as a request-response server. It functions as follows:

1. Listens to a TIBCO ActiveEnterprise request originating from the TIBCO infrastructure.

2. Translates the request.

3. Forwards the request into an EJB residing on an application server.

4. Waits for a response from the EJB.

5. Translates the EJB's response into a TIBCO ActiveEnterprise response.

6. Replies back to the TIBCO infrastructure.

The request-response server service test shows an ActiveEnterprise client — AERPCClient — making a call to the adapter process via a TIBCO ActiveEnterprise message. The adapter, in turn, invokes the EJB — RFC_CUSTOMER_GETServerBean — in the application server, and returns the result to the client.



Figure 4 Request-response server service using standalone adapter block diagram

Figure 5 Request-response server service using inbound connector block diagram


For example, the request-response server service (adapter) can be used to retrieve a sales order from a database in a real-time environment. A thin web client, such as a web page, may send a request to the TIBCO infrastructure to retrieve a sales order record. The adapter listens to the incoming request, transforms the data and forwards it to an EJB deployed in an application server. The EJB retrieves the record from the database and responds with it to the adapter, which then sends the record back to the web page as a response.

EJB Container

TIBC

O M

essa

ging

TIBCO Adapter for EJB

AERPCClientRFC_CUSTOMER_GETServerBean

RMIRequest

Reply

Repository Server

(ejb_sample)

RPC_CustomerGET MDB

Con

nect

or

AERPCClient

TIB

CO

Mes

sagi

ng

Messages Request

EJB Container

Repository Server

(ejb_sample)

Reply



Request-Response Invocation Service

The files for this test are located in the <ADEJB_HOME>\examples\rpc\connector folder.

Description/Purpose

This basic example demonstrates and tests the ability of the connector to receive a request from an EJB residing in an application server, invoke a TIBCO ActiveEnterprise server with the request, wait for a response from the server, and send the reply back to the EJB.

The request-response invocation service test shows a thin Java client — EJBRPCClient — making a call to an EJB — RFC_CUSTOMER_GETBean_Connector — deployed in an application server, via RMI. The EJB, in turn, uses the TIBCO J2EE Connector library to invoke the TIBCO ActiveEnterprise server, AERPCServer, which responds to the request. The RFC_CUSTOMER_GETBean_Connector EJB then returns the results to the EJBRPCClient.

Figure 6 Request-Response Invocation Service Block Diagram


For example, the request-response invocation service (connector) can be used to send news on-demand to a mobile device. A WAP-enabled cell phone sends a request for news headlines to an application server. An EJB residing in the application server sends this request to the connector. The connector translates the request and sends it to a news monitoring service on the TIBCO infrastructure, which responds back to the connector with the latest headlines. The connector replies to the EJB, which replies to the mobile device.

RMI

EJB Container

Reply

RequestEJBRPCClientRFC_CUSTOMER_GETBean_

Connector Con

nect

orAERPCServerMessages

TIBC

O M

essa

gingRepository

Server(ejb_sample)



Business ScenariosThese examples are designed to help you effectively use the adapter with TIBCO BusinessWorks or TIBCO IntegrationManager and TIBCO Enterprise Message Service to solve business problems. The pre configured business scenarios show the working of common business objects with the Sync, Insert-Update, Delete, and Get operations. For details, see Running the Preconfigured Business Scenario on page 27.

Preconfigured business scenarios are available only for the WebSphere Application Server.



When installed, the business scenarios are organized as follows:

The business scenarios are examples that show how the adapter’s publication and request-response server services can be used in a TIBCO BusinessWorks or TIBCO IntegrationManager process.



The examples demonstrate four typical database operations — Sync, Insert-Update, Delete, and Get.

• The Delete operation uses the adapter’s request-response server service to delete a record from a flat file database maintained in the application server. You specify the ID of the record to be deleted through a web page.

The Delete operation queries the EJB based on the given ID and then deletes the record. Information that the record has been deleted is sent back by the adapter to TIBCO BusinessWorks or TIBCO IntegrationManager and is displayed on the html page.

• The Get operation uses the adapter’s request-response server service to fetch data from a flat file database maintained in the application server. You specify the ID of the record to be fetched through a web page.

The Get operation queries the EJB based on the given ID and fetches the data. The data is sent back by the adapter to TIBCO BusinessWorks or TIBCO IntegrationManager and is written into an output file and displayed on the html page.

• The Insert-Update operation uses the adapter’s request-response server service to update a flat file database maintained in the application server. You specify the ID of the record and the details to be inserted or updated through a web page.

The Insert-Update operation queries the EJB based on the given ID. If the record exists, the data in the record is updated. Information that the record has been updated is sent back by the adapter to TIBCO BusinessWorks or TIBCO IntegrationManager and displayed on the html page. If the record does not exist, it is inserted and the information that the record has been inserted is sent back by the adapter to TIBCO BusinessWorks or TIBCO IntegrationManager and displayed on the html page.

• By calling the Sync operation, a client can receive all publications that happen on a particular subject. The Sync operation uses the adapter’s publication service to send a message out of the EJB on-demand. A thin java client triggers the Sync operation on invocation.

• For TIBCO BusinessWorks, the data of only the first publish call is displayed on the HTML page whereas for TIBCO Integration Manager, the data of the subsequent publish calls keeps getting appended to the displayed HTML page.

On receiving the modified data, TIBCO IntegrationManager and TIBCO BusinessWorks display the data on the html page.

In TIBCO BusinessWorks, the data of only the first publish call is displayed on the HTML page whereas in case of TIBCO IntegrationManager, the data of publish calls get appended to the data already displayed on the HTML page.


| 13

Chapter 2 Deploying and Running the Basic Tests

The basic tests are a set of examples that demonstrate the use of the adapter in four main modes of operation — the publication, subscription, request-response invocation, and request-response server services. They diagnose the rudimentary functionality of the adapter and demonstrate its use in primitive scenarios.

The modes of operation of the adapter can be classified into two broad categories:

• Inbound Communication — This includes the subscription and request-response server services. Data and requests flow into the EJB and application server from the TIBCO environment through the adapter.

• Outbound Communication — This includes the publication and request-response invocation services. Data and requests flow out of the EJB and application server into the TIBCO environment through the connector.

This chapter describes how to run the basic tests that are supplied with the adapter.

Topics

• Before Starting, page 14

• Setting Up the Environment, page 15

• Publication Service Example, page 16

• Subscription Service Example, page 18

• Request-Response Server Service Example, page 21

• Request-Response Invocation Service Example, page 24


14 | Chapter 2 Deploying and Running the Basic Tests

Before Starting

You must ensure the following before attempting to deploy and run the basic tests on the TIBCO Adapter for EJB:

• You have installed an application server. See the TIBCO Adapter for EJB Release Notes for a list of supported application servers and platforms. Also see Preparing EJB Application Interfaces in the TIBCO Adapter for EJB User's Guide for information on how to install and configure a supported application server.

• You have correctly installed the adapter. See Installation in the TIBCO Adapter for EJB User's Guide for instructions on how to install the adapter.

• You have read Concepts in the TIBCO Adapter for EJB User’s Guide, and are aware of the terms and phrases used in conjunction with the adapter, other TIBCO products, and J2EE, EJB, and Java Connector Architecture specifications.

• You have prepared your application server based on the instructions in Preparing EJB Application Interfaces in the TIBCO Adapter for EJB User's Guide.

• You have read Example Description on page 4 for an overview of the examples you are about to execute.

• You are familiar with TIBCO Administrator and TIBCO BusinessWorks if you are running the examples in TIBCO BusinessWorks.

• You are familiar with the working of TIBCO IntegrationManager if you are running the examples in TIBCO IntegrationManager.


Setting Up the Environment | 15

Setting Up the Environment

Setting up the environment involves the following tasks:

1. Preparing the Connector.

2. Deploying the Connector.

3. Modifying the Repository URL, Configuration URL and TRA File Name of the Connector Configuration.

4. Making sure that you have installed, configured, and started the requisite TIBCO infrastructure components.

5. Deploying the Test or Example Beans.

For details, see Appendix A, Setting Up the Environment to Run the Basic Tests, on page 57.



Publication Service Example

Location

The files for this test are located in the <ADEJB_HOME>\examples\publish folder.

Example Components

The example consists of the following five components:

• A thin Java client, that invokes an EJB residing on an application server.

• An EJB residing on the application server that pushes out data to the connector. The EJB is called Publish_CustomerBean for the publication service test.

• A generated glue bean, that acts as a bridge between the EJB and the connector. For this example, the glue bean has been packaged along with the example bean.

• The connector, an implementation of the Java Connector Architecture specification, that receives data from the EJB, via the generated glue bean, and publishes the data onto the TIBCO infrastructure.

• A TIBCO ActiveEnterprise server that subscribes to data published by the connector.

Repository Components

• Repository URL: <ADEJB_HOME>\examples\data\ejb_sample.dat

• Configuration URL for the connector's publication service: /tibco/private/adapter/Connector/RPC/EJBAdapter

• Configuration URL for the TIBCO ActiveEnterprise server's subscription service: EXAMPLE_SAP/SampleSubscriber

The following section explains how to set up, configure, and run the test.

To run the test program:

1. Start and configure the application server.

2. Deploy the connector in the application server. The connector will receive data from the test bean and publish it to the TIBCO environment. For details on how to deploy the connector in the application server, see Deploying the Connector on page 99.

3. Prepare the connector for use in the example. During installation, the adapter configures the connector for use with a local repository. If the installation did not complete successfully, or if you wish to run the example with a remote


Publication Service Example | 17

repository server, you will need to modify and prepare the connector accordingly. For details on how to prepare the connector, see Preparing the Connector on page 71.

4. Prepare the Publish_CustomerBean for use in the example. During installation, the adapter configures the sample EJB for use with a local repository. If the installation did not complete successfully, or if you wish to run the example with a remote repository server, you will need to modify and prepare the test bean accordingly. For details on how to prepare the test or example bean, see Modifying the Repository URL, Configuration URL and TRA File Name of the Connector Configuration on page 60.

5. Deploy the test/example bean in the application server. This test bean will push data to the connector. For details on how to deploy the test or example bean in the application server, see Deploying the Test or Example Beans on page 117.

6. Run the TIBCO ActiveEnterprise server. The server subscribes to data published by the connector. To do this, go to the <ADEJB_HOME>/examples/publish/bin directory and at the command line type RunSubscriber.

7. Run the thin Java client. The Java client invokes the Publish_CustomerBean EJB that resides on the application server. This will trigger the EJB to push data out to the connector. To do this, open another command window, go to the <ADEJB_HOME>/examples/publish/bin directory, and type RunPublisherTestClient.

Results on Running the Test Program

Data is pushed out by the Publish_CustomerBean EJB. This action is visible in the application server's application log.

The data is received by the connector. This action is visible in the application server's application log.

The connector converts and publishes the data to the subscribing ActiveEnterprise server/subscriber. This action is displayed in the subscriber server's command window.



Subscription Service Example

The section includes the example for:

• Standalone Adapter, page 18

• Inbound Connector, page 19

Standalone AdapterLocation

The files for this test are located in the <ADEJB_HOME>\examples\subscribe folder.

Example Components

The example consists of the following four components:

• A TIBCO ActiveEnterprise client, that publishes data to the TIBCO infrastructure.

• The adapter, that subscribes to the data from the TIBCO infrastructure, and pushes it to the EJB via a generated glue bean.

• A generated glue bean that acts as a bridge between the adapter and the EJB. For this example, the glue bean has been packaged along with the example bean.

• The EJB that receives the data from the adapter, via the generated glue bean. The EJB is called Subscribe_CustomerBean for the subscription service test.



• Configuration URL for the adapter's subscription service: EJB/Subscriber/Subscriber

• Configuration URL for the TIBCO ActiveEnterprise client's publication service: EXAMPLE_SAP/SamplePublisher.




2. Deploy the test/example bean in the application server. The Subscribe_CustomerBean test bean is used in the example. This test bean receives data from the adapter. For details on how to deploy the test or example beans, see Deploying the Test or Example Beans on page 117.


Subscription Service Example | 19

3. Run the adapter. The adapter standalone executable subscribes to the TIBCO ActiveEnterprise client that publishes data to the TIBCO infrastructure, and in turn invokes the EJB in the application server. To do this, go to the <ADEJB_HOME>/examples/subscribe/adapter/bin directory and at the command line type RunTestAdapter.

4. Run the thin Java client publisher. The Java client publishes the data to the TIBCO environment, to be subscribed by the adapter and forwarded to the EJB. To do this, open another command window, go to the <ADEJB_HOME>/examples/subscribe/adapter/bin directory, and type RunPublisher.


Data is pushed out by the Java publisher client. This action is visible in the client's command window.

The data is received by the adapter. This action is visible in the adapter's log and command window.

The EJB receives the data from the adapter. This action is displayed in the application server's application log.

Inbound ConnectorLocation

The files for this test are located in the <ADEJB_HOME>\examples\subscribe\connector folder.

Example Components


• A TIBCO ActiveEnterprise client that publishes data to the TIBCO infrastructure.

• The connector that subscribes to the data from the TIBCO infrastructure, and pushes it to the EJB via a generated glue bean.

• A generated glue bean that acts as a bridge between the adapter and the EJB. For this example, the glue bean is included with the example bean.



• Configuration URL for the TIBCO ActiveEnterprise client's publication service: EXAMPLE_SAP/SamplePublisher.






2. Deploy the connector RAR file.

3. Deploy the test/example bean in the application server. The Subscribe_CustomerMDB test bean is used in the example. This test bean receives data from the adapter. For details on how to deploy the test or example beans, see Deploying the Test or Example Beans, page 117. Run the adapter. The inbound connector component subscribes to the TIBCO ActiveEnterprise client that publishes data to the TIBCO infrastructure, and in turn invokes the EJB in the application server.

4. Run the thin Java client publisher. The Java client publishes the data to the TIBCO environment, to be subscribed by the adapter and forwarded to the EJB. To do this, open another command window, go to the <ADEJB_HOME>/examples/subscribe/connector/bin directory, and type RunPublisher.


Data is pushed out by the Java publisher client. This action is visible in the client's command window.

The data is received by the connector deployed in application server. This action is visible in the connector's log and application server command window.

The EJB receives the data from the adapter. This action is displayed in the application server's application log.


Request-Response Server Service Example | 21

Request-Response Server Service Example

The section includes the example for:

• Standalone Adapter, page 21

• Inbound Connector, page 22

Standalone AdapterLocation

The files for this test are located in the <ADEJB_HOME>\examples\rpc\adapter folder.

Example Components


• A TIBCO ActiveEnterprise client, AERPCClient, that makes a request to the TIBCO infrastructure.

• The adapter that listens to the request from the TIBCO infrastructure, and forwards it to the EJB via a generated glue bean.

• A generated glue bean that acts as a bridge between the adapter and the EJB. For this example, the glue bean has been packaged along with the example bean.

• The EJB, RFC_CUSTOMER_GETServerBean, that receives the request from the adapter, via the generated glue bean, and responds to the adapter via the generated glue bean.



• Configuration URL for the adapter's request-response server service: EJB/RPC/RPC

• Configuration URL for the TIBCO ActiveEnterprise client's request-response invocation service: EXAMPLE_SAP/SampleRPCClient




2. Deploy the test/example bean in the application server. The RFC_CUSTOMER_GETServerBean test bean is used in this example. This test bean will respond to RPC requests from the adapter. For details on how to



deploy the test or example beans, see Deploying the Test or Example Beans on page 117.

3. Run the adapter. The adapter standalone executable subscribes to the TIBCO ActiveEnterprise client that sends a request to the TIBCO infrastructure, and in turn invokes the EJB in the application server. To do this, go to the <ADEJB_HOME>/examples/rpc/adapter/bin directory and at the command line type RunTestAdapter.

4. Run the thin Java ActiveEnterprise RPC client. The Java ActiveEnterprise RPC client — AERPCClient — sends a request to the TIBCO environment. The request is received by the adapter and forwarded to the EJB. To do this, open another command window, go to the ADEJB_HOME>/examples/rpc/adapter/bin directory, and type RunAdapterTestClient.


Data is pushed out by the Java ActiveEnterprise RPC client. This action is visible in the client's command window.

The data is received by the adapter. This action is visible in the adapter's log and command window.

The EJB receives the data from the adapter and sends back a reply. This action is displayed in the application server's application log.

Inbound ConnectorLocation

The files for this test are located in the <ADEJB_HOME>\examples\rpc\connector\inbound folder.

Example Components


A TIBCO ActiveEnterprise client, AERPCClient, that makes a request to the TIBCO infrastructure.

The connector that listens to the request from the TIBCO infrastructure, and forwards it to the EJB via a generated glue bean.

A generated glue bean that acts as a bridge between the adapter and the EJB. For this example, the glue bean has been packaged along with the example bean.


Repository URL: <ADEJB_HOME>\examples\data\ejb_sample.dat


Request-Response Server Service Example | 23

Configuration URL for the TIBCO ActiveEnterprise client's request-response invocation service: EXAMPLE_SAP/SampleRPCClient




2. Deploy the connector RAR file.

3. Deploy the test/example bean in the application server. The RFC_CUSTOMER_GETMDB test bean is used in this example. This test bean will respond to RPC requests from the adapter. For details on how to deploy the test or example beans, see , Deploying the Test or Example Beans, on page 117.

4. Run the thin Java ActiveEnterprise RPC client. The Java ActiveEnterprise RPC client - AERPCClient - sends a request to the TIBCO environment. The request is received by the adapter and forwarded to the EJB. To do this, open another command window, go to the ADEJB_HOME>/examples/rpc/connector/inbound/bin directory, and type RunAdapterTestClient.


Data is pushed out by the Java ActiveEnterprise RPC client. This action is visible in the client's command window.

The data is received by the connector deployed in application server. This action is visible in the connector's log and application server command window.

The EJB (Message Driven Bean) receives the data from the connector and sends back a reply. This action is displayed in the application server's application log.



Request-Response Invocation Service Example

Location

The files for this test are located in the <ADEJB_HOME>\examples\rpc\connector folder.

Example Components

The example consists of the following five components:

• A thin Java client, EJBRPCClient, that invokes an EJB residing on an application server.

• An EJB, RFC_CUSTOMER_GETBean_Connector, residing on the application server that sends the request to the connector.

• A generated glue bean that acts as a bridge between the EJB and the connector. For this example, the glue bean has been packaged along with the example bean.

• The connector, an implementation of the Java Connector Architecture specification, that receives request from the EJB, via the generated glue bean, and forwards the request onto the TIBCO infrastructure.

• A TIBCO ActiveEnterprise server, AERPCServer, that responds to the request from the connector.



• Configuration URL for the connector's request-response invocation service: /tibco/private/adapter/Connector/RPC/EJBAdapter

• Configuration URL for the TIBCO ActiveEnterprise server's request-response server service: EXAMPLE_SAP/SampleRPCServer




2. Deploy the connector in the application server. The connector will receive the request from the test bean and forward it to the TIBCO environment. For details on how to deploy the connector in the application server, see Deploying the Connector on page 99.

3. Prepare the connector for use in the example. During installation, adapter configures the connector for use with a local repository. If the installation did not complete successfully, or if you wish to run the example with a remote


Request-Response Invocation Service Example | 25

repository server, you will need to modify and prepare the connector accordingly. For details on how to prepare the connector, see Preparing the Connector on page 71.

4. Prepare the RFC_CUSTOMER_GETBean_Connector for use in the example. During installation, the adapter configures the sample EJB for use with a local repository. If the installation did not complete successfully, or if you wish to run the example with a remote repository server, you will need to modify and prepare the test bean accordingly. For details on how to prepare the test or example bean, see Modifying the Repository URL, Configuration URL and TRA File Name of the Connector Configuration on page 60.

5. Deploy the test/example bean in the application server. This test bean will send the request to the connector. For details on how to deploy the test or example beans, see Deploying the Test or Example Beans on page 117.

6. Run the ActiveEnterprise server. The server replies to the request sent by the connector. To do this, go to the <ADEJB_HOME>/examples/rpc/connector/outbound/bin directory and at the command line type RunConnectorTestServer.

7. Run the thin Java RPC client. The Java RPC client invokes the RFC_CUSTOMER_GETBean_Connector EJB residing on the application server. This will trigger the EJB to send the request to the connector. To do this, open another command window, go to the <ADEJB_HOME>/examples/rpc/connector/outbound/bin directory, and type RunConnectorTestClient.


The RFC_CUSTOMER_GETBean_Connector EJB is triggered by the thin Java RPC client. This action is visible in the client's command window.

The request is pushed out by the RFC_CUSTOMER_GETBean_Connector EJB. This action is visible in the application server's application log.

The request is received, converted, and forwarded by the connector. This action is visible in the application server's application log.

The TIBCO ActiveEnterprise server receives the request and replies to the connector. This action is displayed in the server's command window.


| 27

Chapter 3 Running the Preconfigured Business Scenario

This chapter explains how to perform the Sync, Insert-Update, Delete, and Get operations on the business objects in the pre configured business scenarios. This chapter explains how you can set up and run the examples with TIBCO BusinessWorks or TIBCO IntegrationManager.

Topics

• Deploying the Examples to Run with TIBCO IntegrationManager, page 28

• Deploying the Examples to Run with TIBCO BusinessWorks, page 35

• Employee Business Object Examples, page 43

• Purchase Order Business Object Examples, page 46

• Customer Party Business Object Examples, page 49

• Sales Order Business Object Examples, page 51

• Item Master Business Object Examples, page 54


28 | Chapter 3 Running the Preconfigured Business Scenario

Deploying the Examples to Run with TIBCO IntegrationManager

If you are running the examples with TIBCO IntegrationManager, make sure that the following tasks are completed:

1. The WebSphere Application Server is started.

2. The connector is deployed.

3. The Example Beans are deployed and running in the application server.

4. The repourl and configurl of the connector tibco/aeconnector are set to the values required by the example being run.

5. The Repository URL must point to the adejbIMRVExamples.dat file location for the employee, customer party, and purchase order business objects.

6. The Repository URL must point to the adejbIMJMSExamples.dat file location for the Item Master and sales order business object.

Preconfigured Business Scenarios Implementation Matrix

The following table highlights the operations that have been implemented for the business objects in the preconfigured business scenarios.

Legend:X — The operation has not been implemented with the business object.RV — The operation has been implemented using the Reliable Quality of Service in the TIBCO Rendezvous messaging transport for the business object.JMS — The operation has been implemented in the JMS messaging transport for the business object.

Table 1 Examples implementation matrix

Business Object Sync Insert-Update Get Delete

employee RV RV RV RV

purchase order X RV RV RV

customer party RV X X X

sales order X JMS JMS JMS

item master JMS JMS JMS JMS


Deploying the Examples to Run with TIBCO IntegrationManager | 29

Example PrerequisitesThe TIBCO IntegrationManager business scenarios are available in the examples/business/im/data subdirectory of the adapter installation directory. This subdirectory contains the two project files, adejbIMRVExamples.dat and adejbIMJMSExamples.dat, that contain the configuration information.

The <ADEJB_HOME>/examples/business/ directory contains folders for the business objects. Each business object folder contains the files necessary to run the business scenarios. The html folder contains the Index.htm file.

You can access the data subdirectory from the command prompt:

• On Microsoft Windows, go to:<ADEJB_HOME>\<version_num>\examples\business\im\data

• On UNIX, go to:<ADEJB_HOME>/<version_num>/examples/business/im/data

Setting up the environment to run the business scenarios involves the following tasks:

1. Setting the Repository and Configuration URLs in the Application Server.

2. Starting TIBCO Enterprise Message Service Server.

3. Starting TIBCO IntegrationManager.

4. Deploying Example Beans.

5. Modifying the Repository URL in the Example TRA Files

6. Modifying the TRA files

7. Executing Operations for Business Objects on page 33.

Setting Up the EnvironmentSetting up the example involves the following tasks:

Task A Setting the Repository and Configuration URLs in the Application Server

This section describes the procedure to set repository and configuration URLs for IBM WebSphere 5.1 Application Server.

The typical values of repository and configuration URLs for these examples is as follows:



• For the employee, customer party, and purchase order examples, configURL = /tibco/private/adapter/EJB/OutboundServices/EJBAdap

ter

repoURL = <ADEJB_HOME>/examples/business/im/data/adejbIMRVExamples.dat

traFileName = <ADEJB_HOME>/bin/connector.tra

• For the sales order and item master examples, configURL = /tibco/private/adapter/EJB/OutboundServices/EJBAdap

ter

repoURL = <ADEJB_HOME>/examples/business/im/data/adejbIMJMSExamples.dat


To set the repository and configuration URLs to the value specified in the examples:

1. Start the WebSphere Administrator Console.

2. Click Resource Adapters under Resources.

3. Click TibcoAeConnector and then click J2C Connection Factories.

4. Click TibcoAeConnector under J2C Connection Factories.

5. Click Custom Properties under TibcoAeConnector.

6. Select the RepoUrl property and enter <repoUrl> in the Value field.

7. Click OK.

8. Select the ConfigUrl property and enter <configUrl> in the Value field.

9. Click OK.

10. Select the TraFileName property and enter <traFileNamel> in the Value field.

11. Click OK and click Save to save the master configuration.

Task B Starting TIBCO Enterprise Message Service Server

To start TIBCO Enterprise Message Service Server on Microsoft Windows, at the command prompt:

1. Go to the <JMS_HOME>\bin directory.

2. Run the tibjmsd command.

To start TIBCO Enterprise Message Service Server on UNIX, at the command prompt:

1. Go to the <JMS_HOME>/bin directory.



2. Run the tibjmsd command.

Task C Starting TIBCO IntegrationManager

To start TIBCO IntegrationManager with the specified project file:

1. Go to the <IM_HOME>\bin directory at the command prompt.

2. Run the following command:imse -name <engine> <project file path and name>

For example:

imse -name engine1 <ADEJB_HOME>\examples\im\data\adejbIMRVExamples.dat

Before you start TIBCO IntegrationManager, check the following:

• The <IM_HOME>\5.0\java directory contains the fesi.jar file

• The tibco.env.STD_CP_EXT property of the imse.tra file includes the following .jar files:

tibco.env.STD_CP_EXT=<TRA_HOME>/lib;<RV_HOME>/lib

Task D Starting the Administrative Server

You need to start the Administrative Server if you want to access the repository from the repository server. For details, see Starting the Repository Server on page 59.

Task E Deploying Example Beans

To deploy test beans:

1. Start the WebSphere Administrative Console and click Enterprise Applications under Applications. A list of the applications that are installed is displayed.

2. Click Install. The Preparing for the application installation screen is displayed.

You must start TIBCO Enterprise Message Service Server if you are running the JMS examples.

You must start the JMS server before you start TIBCO IntegrationManager for the adejbIMJMSExamples.dat project file.



3. Click Browse to locate the IMExampleBeans.jar file. This file is in the <ADEJB_HOME>/examples/business/lib directory.

4. Click Next twice to continue EJB deployment.

5. Select the Deploy EJBs check box and click Next to continue EJB deployment.

6. Click Next and check that the JNDI names are accurate in the Provide JNDI Names for Beans screen.

7. Click Next and check the JNDI names of the connector reference in the Map resource references to resources page. Make sure that only three beans use the resource Reference Binding and that the JNDI name is tibco/aeconnector.

8. Click Next. The Map modules to application servers page is displayed.

9. Select the server from the Cluster and Servers list box.

10. Select IMExampleBeans.jar to deploy the beans.

11. Click Next until the Finish button is displayed.

12. Click Finish to complete the generation of the stubs and deploy the beans. This process will take a few minutes.

13. Click Save to save the master configuration. After you have deployed the beans, you must start them.

14. Click Enterprise Applications under the Applications folder.

15. Select IMExampleBeans.jar.

16. Click Start. The status of IMExampleBeans changes from red to green.

Task F Modifying the Repository URL in the Example TRA Files

You must modify the repository URLs as follows:

• Change the repository URLs in the <ADEJB_HOME>/examples/business/Employee/RPCServer/bin/employeeserver.tra and <ADEJB_HOME>/examples/business/PurchaseOrder/RPCServer/bin/employeeserver.tra files to <ADEJB_HOME>/examples/business/im/data/adejbIMRVExamples.dat.

• Change the repository URLs in the <ADEJB_HOME>/examples/business/ItemMaster/RPCServer/bin/employeeserver.tra and <ADEJB_HOME>/examples/business/SalesOrder/RPCServer/bin/employeeserver.tra files to <ADEJB_HOME>/examples/business/im/data/adejbIMJMSExamples.dat.



Task G Modifying the TRA files

1. In the following .tra files, replace <your_node_name> with the node name with which the application server you are using is started:

— <ADEJB_HOME>/examples/business/CustomerParty/Publisher/bin/customerpartypublisher.tra

— <ADEJB_HOME>/examples/business/Employee/Publisher/bin/employeepublisher.tra

— <ADEJB_HOME>/examples/business/Employee/RPCServer/bin/employeeserver.tra

— <ADEJB_HOME>/examples/business/ItemMaster/Publisher/bin/itemmasterpublisher.tra

— <ADEJB_HOME>/examples/business/ItemMaster/RPCServer/bin/itemmasterserver.tra

— <ADEJB_HOME>/examples/business/PurchaseOrder/RPCServer/bin/purchaseorderserver.tra

— <ADEJB_HOME>/examples/business/SalesOrder/RPCServer/bin/salesorderserver.tra

Task H Executing Operations for Business Objects

1. Open Index.htm from the <ADEJB_HOME>\examples\business\Html directory. The TIBCO Adapter for EJB Examples page is displayed. The top



left panel displays the business objects, and the bottom-left panel displays the operations available for each business object.

2. Select a business object and run the operations against it:

— Employee Business Object Examples

— Purchase Order Business Object Examples

— Customer Party Business Object Examples

— Sales Order Business Object Examples

— Item Master Business Object Examples


Deploying the Examples to Run with TIBCO BusinessWorks | 35

Deploying the Examples to Run with TIBCO BusinessWorks

If you are running the examples with TIBCO BusinessWorks, make sure that the following tasks are complete:

1. The WebSphere Application Server is started.

2. The connector is deployed.

3. The Example Beans are deployed and running in the application server.

4. The repourl of the connector tibco/aeconnector is set to the values required by the example being run.

5. The project archive has been imported.

6. The adapter is started.

7. TIBCO BusinessWorks is started.

Preconfigured Business Scenarios Implementation Matrix

The following table highlights the operations that have been implemented for the business objects in the preconfigured business scenarios.

Legend:X — The operation has not been implemented with the business object.RV — The operation has been implemented using the Reliable Quality of Service in the TIBCO Rendezvous messaging transport for the business object.JMS — The operation has been implemented in the JMS messaging transport for the business object.

Table 2 Examples implementation matrix

Business Object Sync Insert-Update Get Delete

employee RV RV RV RV

purchase order X RV RV RV

customer party RV X X X

sales order X JMS JMS JMS

item master JMS JMS JMS JMS



Example PrerequisitesThe preconfigured business scenarios are located in the <ADEJB_HOME>\examples\business\bw\data directory. The project file, adejbBWJMSExamples.zip contains configuration information for each business scenario that uses TIBCO Enterprise Message Service. The project file, adejbBWRVExamples.zip contains configuration information for each business scenario that uses TIBCO Rendezvous.

You can start the adapter, TIBCO BusinessWorks, and the business scenarios in one of the following ways:

• Using TIBCO Designer

• Using TIBCO Administrator

Using TIBCO Designer

Successfully running the examples using TIBCO Designer involves the following tasks:

1. Setting the Repository and Configuration URLs in the Application Server on page 29.

2. Starting TIBCO Enterprise Message Service Server on page 30.

3. Deploying Example Beans on page 31.

4. Importing the Project Zip Archive on page 39.

5. Starting the Adapter on page 40.

6. Starting TIBCO BusinessWorks on page 40

7. Modifying the TRA Files on page 42


Using TIBCO Administrator

Successfully running the examples using TIBCO Administrator involves the following tasks:

1. Setting the Repository and Configuration URLs in the Application Server on page 29.

2. Starting TIBCO Enterprise Message Service Server on page 30.

3. Starting the Administrative Server on page 31.

4. Deploying Example Beans on page 31.

5. Generating the EAR File on page 40.



6. Deploying the Example on page 41.

7. Modifying the TRA Files on page 42


Setting Up the EnvironmentSetting up the environment involves the following tasks:

Task A Setting the Repository and Configuration URLs in the Application Server

This section describes the procedure to set repository and configuration URLs for the IBM WebSphere 5.1 Application Server.

The typical values of repository and configuration URLs for these examples are as follows:

• For the employee, customer party, and purchase order examples, configURL = /tibco/private/adapter/EJB/OutboundServices/EJBAdap

ter

repoURL = <ADEJB_HOME>/examples/business/im/data/adejbIMRVExamples.dat


• For the sales order and item master examples, configURL = /tibco/private/adapter/EJB/OutboundServices/EJBAdap

ter

repoURL = <ADEJB_HOME>/examples/business/im/data/adejbIMJMSExamples.dat


To set the Repository URL to the value specified in the examples:

1. Start the WebSphere Administrative Console and click Resource Adapters under Resources.

2. Click TibcoAeConnector and then J2C Connection Factories.



5. Select the RepoUrl property and enter <repoUrl> in the Value field.

6. Click OK.

7. Select the ConfigUrl property and enter <configUrl> in the Value field.

8. Click OK.



9. Select the TraFileName property and enter <traFileNamel> in the Value field.


Task B Starting TIBCO Enterprise Message Service Server

To start TIBCO Enterprise Message Service Server:

• On Microsoft Windows, go to the <JMS_HOME>\bin directory, and run the following command:

tibjmsd

• On UNIX, go to the <JMS_HOME>/bin directory and run the following command:

tibjmsd

Task C Deploying Example Beans

To deploy test beans:



3. Click Browse to locate the IMExampleBeans.jar file. This file is in the <ADEJB_HOME>/examples/business/lib directory.




7. Click Next and check the JNDI names of the connector reference in the Map resource references to resources page. Make sure that only three beans use the resource Reference Binding and that the JNDI name is tibco/aeconnector.



You must start TIBCO Enterprise Message Service Server if you are running the JMS examples.



10. Select IMExampleBeans.jar to deploy the beans.





15. Select IMExampleBeans.jar.

16. Click Start. The status of IMExampleBeans changes from red to green.

Task D Importing the Project Zip Archive

To import the project zip archive:

1. Start TIBCO Designer and click New Empty Project.

2. Click Browse in the Project Directory field under the Multi-File Project tab. Navigate to the folder in which you want the project to be saved and specify a name for the project, for example, sample1.

3. Click Project > Import Full Project and in the Import Project dialog box, click the Zip Archive tab.

4. Click Browse in the File field and:

— Navigate to <ADEJB_HOME>/examples/business/bw/data/adejbBWJMSExamples.zip if you are using TIBCO Enterprise Message Service.

— Navigate to <ADEJB_HOME>/examples/business/bw/data/adejbBWRVExamples.zip if you are using TIBCO Rendezvous.

5. Click OK and then click Apply in the Import-Options dialog box. The contents of the zip archive will be imported into the project you created in step 2.

If you receive an error while saving the project, try re importing the zip archive by selecting the Overwrite on name conflict option in the Import-Options dialog box.



Task E Starting the Adapter

The Adapter Tester tool provided by TIBCO Designer uses the adejb.tra file located in the <ADEJB_HOME>/bin directory as a template to generate the project-specific tra. The adejb.tra file provided with the installation contains all the required jar files in its classpath except for the Stubs generated for the IMExampleBeans.jar.

Therefore, before you start the adapter, go to the adejb.tra file in the <ADEJB_HOME>\bin directory and add <WAS_HOME>/installedApps/<your_node_name>/IMExampleBeans_jar.ear/IMExampleBeans.jar in the tibco.env.CUSTOM_CP_EXT1 property. Replace <your_node_name> and <TIBCO_ADEJB_HOME>/examples/business/lib with the node name with which the application server you are using is started and <WAS_HOME> with the WebSphere installation directory.

To start the adapter:

1. In TIBCO Designer, click Tools > Show Adapter Tester. The Adapter Tester dialog box is displayed.

2. Navigate to sample1 > EJB > InboundServices, select the Run Settings tab and do the following:

a. In the Working Directory field, click Browse to select a working directory.

b. In the Adapter Executable field, click Browse to select the adejb.exe file.

3. Click Start and save the project when prompted. The adapter will start.

Task F Starting TIBCO BusinessWorks

To start TIBCO BusinessWorks:

1. Navigate to sample1 > EJB_BW_Scenarios > Main in the TIBCO Designer project panel.

2. Click the Tester tab and then click the Start testing viewed process button.

3. Select the Main check box in the Select Processes to Load dialog box.

4. Click Start Selected. The TIBCO BusinessWorks processes will be started.

Task G Generating the EAR File

To generate the EAR file:

1. Complete Task D, Importing the Project Zip Archive, on page 39.



2. Click sample1 > EJB_BW_Scenarios > Deployment and select the adejbBWJMSExampleArchive enterprise archive in the project panel.

3. Click Browse in the File Location field under the Configuration tab to specify the folder in which you want to save the EAR file. You can use the default file location to save the EAR file.

4. Click Project > Save.

5. Click the Build Archive button. A message informing you that the enterprise archive file is built correctly will be displayed.

Task H Deploying the Example

In TIBCO Administrator:

1. Go to Application Management and click New Application.

2. Upload the EAR file you generated in Task G and click OK. On the next screen, clear the Quick Configure check box, and then click Save.

3. Click Configuration in the newly created application, if it is not already selected. Click on the top-level application name in the configuration view.

a. Change the values under the Advanced tab, if necessary.

b. Click Save. The Configuration screen is displayed.

c. Click the adapter archive, Adapter Archive.aar, and click Add To Additional Machines.

d. Select the machine and click OK. In the following screen, click Save.

e. Expand the Adapter Archive.aar node, and click on <domain_name>-Adapter Archive.

f. Click Server Settings and add the following to the Append to Classpath field:

<WAS_HOME>/installedApps/<your_node_name>/IMExampleBeans_jar.ear/IMExampleBeans.jar.

g. Click Save.

h. Click the process archive, Process Archive.par, in the Configuration screen. Click Add to Additional Machines. Select the machine and click OK. In the next screen, click Save.

4. In the Configuration screen, click Deploy. Click OK.

5. Once the deployment is complete, click Service Instances under the application. The adapter and TIBCO BusinessWorks are listed. Select the



adapter and the TIBCO BusinessWorks engine and click Start Selected. The adapter instance and TIBCO BusinessWorks are started.

Task I Modifying the TRA Files

1. In the following .tra files, replace <your_node_name> with the node name with which the application server you are using is started:

— <ADEJB_HOME>/examples/business/CustomerParty/Publisher/bin/customerpartypublisher.tra

— <ADEJB_HOME>/examples/business/Employee/Publisher/bin/employeepublisher.tra

— <ADEJB_HOME>/examples/business/Employee/RPCServer/bin/employeeserver.tra

— <ADEJB_HOME>/examples/business/ItemMaster/Publisher/bin/itemmasterpublisher.tra

— <ADEJB_HOME>/examples/business/ItemMaster/RPCServer/bin/itemmasterserver.tra

— <ADEJB_HOME>/examples/business/PurchaseOrder/RPCServer/bin/purchaseorderserver.tra

— <ADEJB_HOME>/examples/business/SalesOrder/RPCServer/bin/salesorderserver.tra

Task J Executing Operations for Business Objects

1. Open Index.htm from the <ADEJB_HOME>\examples\business\Html directory. The TIBCO Adapter for EJB Examples page is displayed. The top left panel displays the business objects, and the bottom-left panel displays the operations available for each business object.

2. Select a business object and run the operations against it:

— Employee Business Object Examples

— Purchase Order Business Object Examples

— Customer Party Business Object Examples

— Sales Order Business Object Examples

— Item Master Business Object Examples


Employee Business Object Examples | 43

Employee Business Object Examples

The examples for the employee business object have been implemented for the TIBCO Rendezvous messaging transport as follows:

• For the Get and Delete operations, the employee ID is specified in the HTML page and the results are displayed after the operation has been performed.

• For the Insert-Update operation, the employee data is entered in the fields for the employee record and the results of the operation are displayed after you click the Add button.

• For the Sync operation, the employee data is displayed on the HTML page.

The schema used by the employee business object is as follows:

Figure 7 Employee business object schema

To run the examples with TIBCO IntegrationManager, make sure that you complete the following tasks:

1. Start TIBCO IntegrationManager with the adejbIMRVExamples.dat configuration file at the command prompt.

EmployeeStr EMPIDPERSONAL_DATAADDRESS PersonalDataClas

sStr GENDERStr BIRTH_DATEStr PHONENAME

NameClassStr

LAST_NAMEStr

FIRST_NAME

AddressClassStr ADDRESS1Str CITYStr STATEStr COUNTRYStr POSTALStr EMAIL



2. Start the request-response server service and at the command prompt:

— On Microsoft Windows, go to the <ADEJB_HOME>\examples\business\Employee\RPCServer\bin directory and run the RunEmployeeServer.bat command.

— On UNIX, go to the <ADEJB_HOME>/examples/business/Employee/RPCServer/bin directory and run the RunEmployeeServer command.

To run the examples with TIBCO BusinessWorks, make sure that you complete the following tasks:

1. Start the Adapter Tester with the InboundServices configuration.

2. Start TIBCO BusinessWorks using the Tester.

3. Open the Index.htm file that is located in the <ADEJB_HOME>\examples\business\Html directory.

4. Click Employee on the Index.htm page. The Employee panel with the available operations is displayed.

Publish an Employee RecordThe Sync operation demonstrates a publish scenario.

To publish an employee record:

1. Click Sync under Employee on the Index.htm page.

2. Click Start on the Sync Operation page to start the Sync operation. A new browser window opens.

3. Start the publisher client and at the command prompt:

— On Microsoft Windows, go to the <ADEJB_HOME>\examples\business\Employee\Publisher\bin directory and run the RunEmployeePublisherClient.bat command.

— On UNIX, go to the <ADEJB_HOME>/examples/business/Employee/Publisher/bin directory and run the RunEmployeePublisherClient command.

4. The employee details are displayed in the new browser window.

Insert or Update an Employee RecordThe Insert-Update operation demonstrates a request-response server service scenario.


Employee Business Object Examples | 45

To insert or update an employee record:

1. Click Insert-Update under Employee. The Employee Insert_Update page is displayed.

2. Click Add on the Employee Insert_Update page. The employee record is inserted or updated and a message is displayed on the HTML page. If an error occurs during the operation, the error message is displayed on the HTML page.

Get an Employee RecordThe Get operation demonstrates a request-response server service scenario.

To retrieve an employee record:

1. Click Get under Employee on the Index.htm page.

2. Type the employee ID in the Employee ID field and click Get on the Get Employee Details page. If the employee record exists, it is retrieved and displayed on the HTML page.

If the employee record does not exist, a message informing you that the record is not found is displayed.

If errors occur during the operation, an error message is displayed on the HTML page.

Delete an Employee RecordThe Delete operation demonstrates a request-response server service scenario.

To delete an employee record:

1. Click Delete under Employee on the Index.htm page.

2. Type the employee ID in the Emp ID field on the Delete Employee Details page and click Delete. If the employee record exists, it is deleted and a message informing you that the record has been deleted is displayed on the HTML page.

Otherwise, a message stating that the record does not exist is displayed.

If errors were encountered during the operation, a message is displayed on the HTML page.



Purchase Order Business Object Examples

The examples for purchase order business object have been implemented for the TIBCO Rendezvous messaging transport as follows:

• For the Get and Delete operations, the purchase order ID is specified in the HTML page and the results are displayed after the corresponding operation has been performed.

• For the Insert-Update operation, the purchase order data is entered in the corresponding fields and the results of the operation are displayed after you click Add.

The schema used by the purchase order business object is as follows:

Figure 8 Purchase order business object schema

To run the purchase order examples using TIBCO IntegrationManager, make sure that you complete the following:

1. Start TIBCO IntegrationManager with the adejbIMRVExamples.dat configuration file at the command prompt.

2. Start the adapter request-response server service and at the command prompt:

— On Microsoft Windows, go to the <ADEJB_HOME>\examples\business\PurchaseOrder\RPCServer\bin directory and run the RunPurchaseOrderServer.bat command.

— On UNIX, go to the <ADEJB_HOME>/examples/business/PurchaseOrder/RPCServer/bin directory and run the RunPurchaseOrderServer command.

SalesOrder

HeaderLINE_ITEM

HeaderClassStr DOCUMENT_IDFROMTO

DestinationClassStr ORGANIZATIONStr COUNTRYStr UR1Str DOMAIN

LineItemClass

Str ITEM_TYPEInt QUANTITYFloat DISCOUNT

sequence


Purchase Order Business Object Examples | 47





4. Click Purchase Order on the Index.htm page. The Purchase Order panel with the available operations is displayed.

Insert or Update a Purchase Order RecordThe Insert-Update operation demonstrates a request-response server service scenario.

To insert or update a purchase order record:

1. Click Insert-Update under Purchase Order on the Index.htm page.

2. Click Add on the Purchase Order Insert_Update page. The purchase order record is inserted or updated and a message is displayed on the HTML page. If an error occurs during the operation, an error message is displayed on the HTML page.

Get a Purchase Order RecordThe Get operation demonstrates a request-response server service scenario.

To retrieve a purchase order record:

1. Click Get under Purchase Order on the Index.htm page. The Get PO Details page is displayed.

2. Type the purchase order ID in the PO ID field and click Get on the Get PO Details page.

If the purchase order record exists, it is retrieved and displayed on the HTML page.

Otherwise, a message stating that the record was not found is displayed in the HTML page.

If an error occurs during the running of the example, a message is displayed on the HTML page.



Delete a Purchase Order RecordThe Delete operation demonstrates a request-response server service scenario.

To delete a purchase order record:

1. Click Delete under Purchase Order on the Index.htm page.

2. Type the purchase order ID in the PO ID field and click Delete on the Delete PO Details page.

If the purchase order record exists, it is deleted and a message is displayed on the HTML page.

Otherwise, a message stating that the record does not exist is displayed on the HTML page. If an error occurs during the running of the example, a message is displayed on the HTML page.


Customer Party Business Object Examples | 49

Customer Party Business Object Examples

The examples for the customer party business object have been implemented for the TIBCO Rendezvous messaging transport. For the Sync operation, the customer party data is displayed on the HTML page.

The schema used for the customer party business object is shown below. This is a simple schema with string fields and a class field.

Figure 9 Customer party business object schema

Before you run this example with TIBCO IntegrationManager, make sure that you start TIBCO IntegrationManager with the adejbIMRVExamples.dat configuration file at the command prompt.

Publish a Customer Party RecordThe Sync operation demonstrates a publish scenario.

To publish a customer party record:


2. Click Customer Party on the Index.htm page. The Customer Party panel with the available operations is displayed.

3. Click Sync under Customer Party on the Index.htm page.

4. Click Start on the Sync Operation page to start the Sync operation. A new browser window opens.

CustomerPartyStr EMPIDStr CUSTOMER_NAMEStr ORGANIZATIONStr UR1PERSONAL_DETAILS

PersonalDetailsClassStr ADDRESSStr CITYStr STATEStr PINStr COUNTRYStr EMAILStr PHONE



5. Start the publication service and at the command prompt:

— On Microsoft Windows, go to the <ADEJB_HOME>\examples\business\CustomerParty\Publisher\bin directory and run the RunCustomerPartyPublisher.bat command.

— On UNIX, go to the <ADEJB_HOME>/examples/business/CustomerParty/Publisher/bin directory and run the RunCustomerPartyPublisher command.

6. The details of the customer party are displayed in the new browser window.


Sales Order Business Object Examples | 51

Sales Order Business Object Examples

The examples for the sales order business object have been implemented for the JMS messaging transport as follows:

• For the Get and Delete operations, the Order Number is specified in the HTML page and the results are displayed after the corresponding operation has been performed.

• For the Insert-Update operation, the sales order data is entered in the corresponding fields and the results of the operation are displayed after you click the Add button.

The schema used for the sales order business object is shown below.

Figure 10 Sales order business object schema

To run the sales order business object examples, make sure that you complete these tasks:

1. Start TIBCO IntegrationManager with the adejbIMJMSExamples.dat configuration file at the command prompt.

2. Start the JMS Server and at the command prompt run the tibjmsd command.


— On Microsoft Windows, go to the <ADEJB_HOME>\examples\business\SalesOrder\RPCServer\bin directory and run the RunSalesOrderServer.bat command.

— On UNIX, go to the <ADEJB_HOME>/examples/business/SalesOrder/RPCServer/bin directory and run the RunSalesOrderServer command.

SalesOrder

HEADERLINE_ITEM

LineItemClassStr ITEMInt QUANTITYFloat DISCOUNT

HeaderClassStr SALES_ORDER_NOStr SALES_PERSONStr SALES_ORGFloat COMMISSION_AMT

sequence







4. Click Sales Order on the Index.htm page. The Sales Order panel with the available operations is displayed.

Insert or Update a Sales Order RecordThe Insert-Update operation demonstrates a request-response server service scenario.

To insert or update a sales order record:

1. Click Insert-Update under Sales Order on the Index.htm page.

2. Click Add on the Sales Order Insert_Update page. The sales order record is inserted or updated and a message is displayed on the HTML page. If an error occurs during the operation, an error message is displayed on the HTML page.

Get a Sales Order RecordThe Get operation demonstrates a request-response server service scenario.

To retrieve a sales order record:

1. Click Get under Sales Order on the Index.htm page.

2. Type the order number in the Order Number field and click Get.

If the sales order record exists, it is retrieved and displayed on the HTML page.

Otherwise, a message stating that the record does not exist is displayed on the HTML page. If an error occurs during the running of the example, a message is displayed on the HTML page.

Delete a Sales Order RecordThe Delete operation demonstrates a request-response server service scenario.

To delete a sales order record:


Sales Order Business Object Examples | 53

1. Click Delete under Sales Order on the Index.htm page.

2. Type the order number in the Order Number field and click Delete. If the sales order record exists, it is deleted and a message is displayed on the HTML page. Otherwise, a message stating that the record does not exist is displayed. If an error occurs during the running of the example, a message is displayed on the HTML page.



Item Master Business Object Examples

The examples for the item master business object have been implemented for the JMS messaging transport as follows:

• For the Get and Delete operations, the item ID is specified in the HTML page and the results are displayed after the operation has been performed.

• For the Insert-Update operation, the item data is entered in the fields and the results of the operation are displayed after you click the Add button.

• For the Sync operation, the item data is displayed on the HTML page.

The schema used for the item master business object is shown below.

Figure 11 Item master business object schema

To run the item master business object examples for the Insert-Update, Get, and Delete operations, complete these common tasks:

1. Make sure that TIBCO IntegrationManager has been started using the adejbIMJMSExamples.dat configuration file and is running.

2. Make sure that TIBCO Enterprise Message Service server is running.


— On Microsoft Windows, go to the <ADEJB_HOME>\examples\business\ItemMaster\RPCServer directory and run the RunItemMasterServer.bat command.

— On UNIX, go to the <ADEJB_HOME>/examples/business/ItemMaster/RPCServer directory and run the RunItemMasterServer command.

ItemMaster

HEADERITEM_LOCATION

HeaderClassStr ITEM_IDStr TYPEStr PRODUCT_LINEStr COMMODITY_CODEFloat ITEM_COST

sequence

LocationClassStr NAMEStr LOCATION_CODEStr DESCRIPTION


Item Master Business Object Examples | 55





4. Click Item Master on the Index.htm page. The Item Master panel with the available operations is displayed.

Publish an Item Master RecordThe Sync operation demonstrates a publish scenario.

To publish an item master record:

1. Click Sync under Item Master on the Index.htm page.

2. Click Start on the Item Details page to start the Sync operation. A new browser window opens.

3. Start the JMS Server and at the command prompt:

— On Microsoft Windows, go to the <JMS_HOME>\bin directory and run the tibjmsd command.

— On UNIX, go to the <JMS_HOME>/bin directory and run the tibjmsd command.

4. Start the publication service and at the command prompt:

— On Microsoft Windows, go to the <ADEJB_HOME>\examples\business\ItemMaster\Publisher\bin directory and run the RunItemMasterPublisherClient.bat command.

— On UNIX, go to the <ADEJB_HOME>/examples/business/ItemMaster/Publisher/bin directory and run the RunItemMasterPublisherClient command.

The item details are displayed in the new browser window.

Insert or Update an Item Master RecordThe Insert-Update operation demonstrates a request-response server service scenario.

To insert or update an item master record:

1. Click Insert-Update under Item Master on the Index.htm page.



2. Click Add on the Item Details Insert_Update page. The item master record is inserted or updated and a message is displayed on the HTML page. If an error occurs during the operation, an error message is displayed on the HTML page.

Get an Item Master RecordThe Get operation demonstrates a request-response server service scenario.

To retrieve an item master record:

1. Click Get under Item Master on the Index.htm page.

2. Type the item ID in the Item ID field and click Get on the Get Item Details page. If the item record exists, it is retrieved and the details are displayed on the HTML page. Otherwise, a message stating that the record does not exist is displayed on the HTML page. If an error occurs during the running of the example, a message is displayed on the HTML page.

Delete an Item Master RecordThe Delete operation demonstrates a request-response server service scenario.

To delete an item master record:

1. Click Delete under Item Master on the Index.htm page.

2. Type the item ID in the Item ID field and click Delete on the Delete Item Details page. If the item record exists, it is deleted and a message is displayed on the HTML page. Otherwise, a message stating that the record does not exist is displayed on the HTML page. If an error occurs during the running of the example, a message is displayed on the HTML page.


| 57

Appendix A Setting Up the Environment to Run the Basic Tests

This chapter describes the application server-specific prerequisite steps required to set up the environment to run the examples installed with the TIBCO Adapter for EJB.

Topics

• Prerequisites, page 58

• Starting the Repository Server, page 59

• Modifying the Repository URL, Configuration URL and TRA File Name of the Connector Configuration, page 60

• Preparing the Connector, page 71

• Deploying the Connector, page 99

• Preparing the Test or Example Beans, page 113

• Deploying the Test or Example Beans, page 117


58 | Appendix A Setting Up the Environment to Run the Basic Tests

Prerequisites

Setting up the environment to run the basic tests involves the following tasks:

1. Modifying the Repository URL, Configuration URL and TRA File Name of the Connector Configuration on page 60

2. Starting the Repository Server on page 59

3. Preparing the Connector on page 71

4. Deploying the Connector on page 99

5. Preparing the Test or Example Beans on page 113

6. Deploying the Test or Example Beans on page 117

Supported Application Servers

The following application servers are supported:

• BEA WebLogic Application Server 7.0 and BEA WebLogic Application Server 7.0 with SP2, SP4, SP5, SP6, and SP7

• BEA WebLogic Application Server 8.1 and BEA WebLogic Application Server 8.1 with SP1, SP2, SP3, SP4, SP5, and SP6

• BEA WebLogic Application Server 9.0, 9.1, and 9.2

• IBM WebSphere 5.1 Application Server

• IBM WebSphere 6.0, 6.0.2, and 6.1 Application Servers

• JBoss 3.2.3 Application Server

• JBoss 4.0.0, 4.0.1, 4.0.2, 4.0.3, and 4.0.4 Application Servers

• Sun Java System Application Server Platform Edition 7

• Sun Java System Application Server Platform Edition 8.1

• Oracle 9i Application Server 9.0.3

• Oracle 10g Application Server 9.0.4, 10.1.2, and 10.1.3


Starting the Repository Server | 59

Starting the Repository Server

Follow the process described in this section if you want to run the examples by accessing the repository from the repository server. Skip this section, if you want to run the examples using a local repository.

To start the repository server:

1. Make sure that you have the following files:

— ejb_sample.dat, which is located in the <ADEJB_HOME>\examples\data directory. This file is the repository instance file in XML format which is to be used to run the basic tests. You must start the repository server using this file as input.

— tibcoadmin_<domain_name>.tra, which is located in the <ADMINISTRATOR_HOME>\bin directory and is used by the repository when it starts.

2. Verify the following in the file:

— The repository is set up to accept file instances. To do this, comment out the line defining the repo.dbtype parameter.

— There is a valid directory defined as the value of the repo.directory parameter.

3. Copy the ejb_sample.dat file into the directory defined in the repo.directory parameter in the tibcoadmin_<domain_name>.tra file. For example, D:/Projects.

4. Start the TIBCO Administrator server and this will start the repository server.

You cannot run two repository instances with the same name on the same subnet. Therefore, make sure that multiple repository instances on the same network are uniquely named.



Modifying the Repository URL, Configuration URL and TRA File

Name of the Connector Configuration

Before deploying the connector, the configuration needs to be changed to provide the values for the configUrl, repoUrl and traFileName properties of the connector. Please follow the steps in the following sections for changing these values.

Although you do not need to change the configuration URL when switching from a local repository to a remote repository, this section explains the procedure to modify the configuration URL, in case you should need it for some other scenarios.

Typically, the repository URL for accessing a repository is as follows:

• For accessing the remote repository:

repoUrl=tibcr://ejb_sample:userName=adejb:password=adejb

• For accessing the local repository:

d:/tibco/adapter/adejb/<version_num>/examples/data/ejb_sample.dat

BEA WebLogic Application Server 7.0 and BEA WebLogic Application Server 7.0 with SP2, SP4, SP5, SP6, and SP7

To edit the repository and configuration URLs:

1. Click Start > Programs > BEA WebLogic E-Business Platform > WebLogic 7> Start Default Console to start the Administrator Console.

2. Click Deployments > Connectors. If the connector (Aeconnector.rar) is deployed it will appear in the list of connectors.

3. Click Aeconnector and then click Edit Connector Descriptor.

The AeConnector.rar file is displayed in a new browser window.

This section assumes that the user name and password used to access the repository server are adejb and adejb respectively. If you need to use a different user name and password replace these values in the repository URL with the values you want to use.

By default, the properties file for the connector configuration, connector.tra, is available in <ADEJB_HOME>/bin. This file name and/or the location of this file can be changed in the same way as you change the repoUrl and configUrl properties of the connector configuration.


Modifying the Repository URL, Configuration URL and TRA File Name of the Connector Configuration | 61

4. Click Config Properties under WebLogic RA, and click repoUrl. The configuration page is displayed.

5. In the configuration page, change the repoURL property as follows:

— For accessing the remote repository:


— For accessing the local repository:


6. In the same page, change the configURL as follows:configUrl=/tibco/private/adapter/Connector/RPC/EJBAdapter

7. Change the TRA File Name to: d:/tibco/adapter/adejb/<version_num>/bin/connector.tra

8. Click Apply.

BEA WebLogic Application Server 8.1, BEA WebLogic Application Server 8.1 with SP1, SP2, SP3, SP4, SP5, and SP6

To edit the repository and configuration URLs:

1. In a temporary directory, run the following command:

— On Microsoft Windows:jar -xvf <ADEJB_HOME>\lib\AeConnector.rar

— On UNIX:jar -xvf <ADEJB_HOME>/lib/AeConnector.rar

2. Go to the META-INF directory and edit the ra.xml files as follows:

— Change the configuration URL to /tibco/private/adapter/Connector/RPC/EJBAdapter for the basic tests

— Change the TRA File Name to: d:/tibco/adapter/adejb/<version_num>/bin/connector.tra

— Change the repository URL to one of the following:


(for accessing the remote repository)


(For accessing the local repository)



3. Go back to the temporary directory you accessed in step 1 and run the following command:

— On Microsoft Windows:jar -uvf <ADEJB_HOME>\lib\AeConnector.rar META-INF

— On UNIX:jar -uvf <ADEJB_HOME>/lib/AeConnector.rar META-INF

4. Deploy the connector as explained in the TIBCO Adapter for EJB User’s Guide.

BEA WebLogic Application Server 9.0, 9.1, and 9.2To edit the repository and configuration URLs:


— On Microsoft Windows:jar -xvf <ADEJB_HOME>\lib\AeConnector.rar

— On UNIX:jar -xvf <ADEJB_HOME>/lib/AeConnector.rar

2. Go to the META-INF directory and edit the ra.xml files as follows:

— Change the configuration URL to /tibco/private/adapter/Connector/RPC/EJBAdapter for the basic tests

— Change the TRA File Name to: d:/tibco/adapter/adejb/<version_num>/bin/connector.tra







— On Microsoft Windows:jar -uvf <ADEJB_HOME>\lib\AeConnector.rar META-INF

— On UNIX:jar -uvf <ADEJB_HOME>/lib/AeConnector.rar META-INF

Deploy the connector as explained in the TIBCO Adapter for EJB User’s Guide.



IBM WebSphere 5.1, 6.0 6.0.2, and 6.1 Application Servers

To modify the repository and configuration URLs:



3. Click TibcoAeConnector and then click Custom Properties under TibcoAeConnector.

4. Select the repoUrl property and enter

— For accessing the remote repository:


— For accessing the local repository:

d:/tibco/adapter/adejb/<version_num>/examples/data/ejb_sa

mple.dat

in the Value field.

5. Click Apply.

6. Select the configUrl property and enter /tibco/private/adapter/Connector/RPC/EJBAdapter in the Value field.

7. . Select the traFileName property and enter d:/tibco/adapter/adejb/<version_num>/bin/connector.tra in the Value field.

Sun Java System Application Server Platform Edition 7To edit the repository and configuration URLs:


— On Microsoft Windows:

jar -xvf <ADEJB_HOME>\lib\AeConnector.rar

— On UNIX:

jar -xvf <ADEJB_HOME>/lib/AeConnector.rar

In the tibco.env.CUSTOM_CP_EXT1 property in the tra files for the examples, locate the <WebSphere_HOME>/.../<your node name> entry and replace <your node name> with the name of the node that you have created.



2. Go to the META-INF directory and edit the ra.xml file as follows:

a. Change the repository URL to one of the following:





b. Change the configuration URL to configUrl= /tibco/private/adapter/Connector/RPC/EJBAdapter

c. Change the traFileName to d:/tibco/adapter/adejb/<version_num>/bin/connector.tra



jar -uvf <ADEJB_HOME>\lib\AeConnector.rar META-INF

— On UNIX:

jar -uvf <ADEJB_HOME>/lib/AeConnector.rar META-INF

4. Deploy the connector as explained in the TIBCO Adapter for EJB User's Guide.

Sun Java System Application Server Platform Edition 8.1To edit the repository and configuration URLs:




— On UNIX:









(for accessing the local repository)






— On UNIX:


4. Deploy the connector as explained in the TIBCO Adapter for EJB User's Guide.

Oracle 9i Application ServerYou must change the set of .tra files used by the adapter to classes and add additional environment variable required specifically for the Oracle application server.

The following tra files need to be changed:

• <TIBCO_ADEJB_HOME>\examples\rpc\connector\outbound\bin\ rpcconnectorclient.tra

• <TIBCO_ADEJB_HOME>\examples\rpc\connector\outbound\bin\ rpcconnectorexcclient.tra

• <TIBCO_ADEJB_HOME>\examples\rpc\adapter\bin\ rpcadapterserver.tra

• <TIBCO_ADEJB_HOME>\examples\subscribe\adapter\bin\subscribeserver.tra

• <TIBCO_ADEJB_HOME>\examples\publish\bin\publishclient.tra

In each tra file, add or update the following attributes with the values listed:

• java.property.java.naming.security.principal=admin

• java.property.java.naming.security.credentials=system123







— On UNIX:













— On UNIX:


4. Stop the application server.

5. Copy the modified AeConnector.rar file to the <ORACLE9IAS-ROOT>/j2ee/home/connectors/standalone directory.

6. Restart the application server so that it unpacks the rar file again.

7. Copy oc4j-ra.xml from the <ORACLE9IAS-ROOT>/j2ee/home/connectors/standalone/AeConnector/META-INF directory to the <ORACLE9IAS-ROOT>/j2ee/home/application-deployments/default/standalone directory.

8. Restart the application server for the changes to take effect.



Oracle 10g Application ServerYou must change the set of .tra files used by the adapter to classes and add additional environment variable required specifically for the Oracle application server.

The following tra files need to be changed:

• <TIBCO_ADEJB_HOME>\examples\rpc\connector\outbound\bin\ rpcconnectorclient.tra

• <TIBCO_ADEJB_HOME>\examples\rpc\connector\outbound\bin\ rpcconnectorexcclient.tra

• <TIBCO_ADEJB_HOME>\examples\rpc\adapter\bin\ rpcadapterserver.tra

• <TIBCO_ADEJB_HOME>\examples\subscribe\adapter\bin\subscribeserver.tra

• <TIBCO_ADEJB_HOME>\examples\publish\bin\publishclient.tra

In each tra file, add or update the following attributes with the values listed:

• java.property.java.naming.security.principal=admin

• java.property.java.naming.security.credentials=system123





— On UNIX:















— On UNIX:


4. Stop the application server.

5. Copy the modified AeConnector.rar file to the <ORACLE10gAS-ROOT>/j2ee/home/connectors/standalone directory.

6. Restart the application server so that it unpacks the rar file again.

7. Copy oc4j-ra.xml from the <ORACLE10gAS-ROOT>/j2ee/home/connectors/standalone/AeConnector/META-INF directory to the <ORACLE10gAS-ROOT>/j2ee/home/application-deployments/default/standalone directory.

8. Restart the application server for the changes to take effect.

JBoss 3.2.3 Application ServerTo edit the repository and configuration URLs:

1. Run the following command in a temporary directory:

— On Microsoft Windows, run jar -xvf <ADEJB_HOME>\lib\AeConnector.rar.

— On UNIX, run jar -xvf <ADEJB_HOME>/lib/AeConnector.rar.

2. Edit the ra.xml file in the temporary directory as follows:

— Change the value of the configuration URL to /tibco/private/adapter/Connector/RPC/EJBAdapter for the basic tests.








— Change the traFileName to d:/tibco/adapter/adejb/<version_num>/bin/connector.tra


— On Microsoft Windows, run jar -uvf <ADEJB_HOME>\lib\AeConnector.rar META-INF

— On UNIX, run jar -uvf <ADEJB_HOME>/lib/AeConnector.rar META-INF

4. Copy AeConnector.rar to the <JBOSS_HOME>\server\default\deploy directory while the application server is running.

JBoss 4.0.0, 4.0.1, 4.0.2, 4.0.3, and 4.0.4 Application ServersTo edit the repository and configuration URLs for JBoss 4.0.0 application server:

1. Edit the ra.xml file in <JBOSS_HOME>\server\default\deploy directory as follows:

a. Change the value of the configuration URL to /tibco/private/adapter/Connector/RPC/EJBAdapter for the basic tests.

b. Change the repository URL to one of the following:






d. Restart the application server.

To edit the repository and configuration URLs for JBoss 4.0.1, 4.0.2, 4.0.3, and 4.0.4 application servers:



1. Run the following command in a temporary directory:

— jar -xvf <ADEJB_HOME>\lib\AeConnector.rar (on Microsoft Windows)

— run jar -xvf <ADEJB_HOME>/lib/AeConnector.rar (on UNIX)

2. Edit the AeConnector-ds.xml file in the temporary directory as follows:

— Change the value of the configuration URL to /tibco/private/adapter/Connector/RPC/EJBAdapter for the basic tests.







— jar -uvf <ADEJB_HOME>\lib\AeConnector.rar META-INF (on Microsoft Windows)

— jar -uvf <ADEJB_HOME>/lib/AeConnector.rarMETA-INF (on UNIX)

Copy AeConnector.rar to the <JBOSS_HOME>\server\default\deploy directory while the application server is running.


Preparing the Connector | 71

Preparing the Connector

This section explains how to prepare the connector for the application server you are using.

BEA WebLogic Application Server 6.1 with SP1, SP2, or SP3You can prepare the connector on the following platforms:

• Microsoft Windows Platforms

• UNIX Platforms

Microsoft Windows Platforms

To prepare the connector:

1. The setEnv.cmd file is located under the <WebLogic_HOME>\config\<domain name> directory. Add the following environment variables to the Set user-defined variables section of the file. The environment variable must point to the installation directory for the product.

— set TIBCO_TRA_HOME=<TRA installation directory>

— set TIBCO_RV_HOME=<TIBCO Rendezvous installation directory>

— set TIBCO_ADEJB_HOME=<Adapter installation directory>

— set TIBCO_TPCL_HOME=<Third party core libraries installation directory>

— set TIBCO_JRE_HOME=<JRE installation directory>

The setEnv.cmd file also sets the environment for user applications. Add the following jar files to the CLASSPATH environment variable in the setEnv.cmd file:

set CLASSPATH=%CLASSPATH%;%TIBCO_RV_HOME%\lib\tibrvj.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOxml.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOrt.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOtsm.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOjms.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCrypt.jarset CLASSPATH=%CLASSPATH%;%TIBCO_ADEJB_HOME%\lib\EjbSupport.jarset CLASSPATH=%CLASSPATH%;%TIBCO_ADEJB_HOME%\lib\GlBeansSupport.jarset CLASSPATH=%CLASSPATH%;%TIBCO_ADEJB_HOME%\lib\AeConnector.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TPCL_HOME%\lib\xmlParserAPIs.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TPCL_HOME%\lib\xercesImpl.jar

2. The startWebLogic.cmd file is located under the <WebLogic_HOME>\config\<domain name> directory. Add the following



environment variables to the :runWebLogic section of the file. The environment variable must point to the installation directory for the product.






The startWeblogic.cmd file sets the required environment for starting the WebLogic server. Add the following jar files to the CLASSPATH environment variable in the:runWeblogic section of the script after the Set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar line.


UNIX Platforms


1. The setEnv.sh file can be located under the <WebLogic_HOME>/config/<domain name> directory. Add the following

If you are using the HTTPS protocol to access the repository or if you are using a repository present in a repository server, do the following:

• Add <TPCL_HOME>/lib/entrust/unsigned to the tibco.env.STD_CP_EXT property in the tra file associated with the request-response server and subscription services. You must include this path before the reference to <TPCL_HOME>/lib/entrust.



environment variables after the section related to setting WL_HOME. The environment variable must point to the installation directory for the product.

— export TIBCO_TRA_HOME=<TRA installation directory>

— export TIBCO_RV_HOME=<TIBCO Rendezvous installation directory>

— export TIBCO_ADEJB_HOME=<Adapter installation directory>

— export TIBCO_TPCL_HOME=<Third Party Core Libraries installation directory>

— export TIBCO_JRE_HOME=<JRE installation directory>

The setEnv.sh file sets the environment for user applications. Add the following jar files to the CLASSPATH environment variable in the setEnv.sh file.

CLASSPATH=$CLASSPATH:$TIBCO_RV_HOME/lib/tibrvj.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOxml.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOrt.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOtsm.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOjms.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCrypt.jarCLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/EjbSupport.jarCLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/GlBeansSupport.jarCLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/AeConnector.jarCLASSPATH=$CLASSPATH:$TIBCO_TPCL_HOME/lib/xmlParserAPIs.jarCLASSPATH=$CLASSPATH:$TIBCO_TPCL_HOME/lib/xercesImpl.jar

2. At the end of the setEnv.sh file add the following lines to update the LD_LIBRARY_PATH or SHLIB_PATH.

— For HP-UX:

SHLIB_PATH=$SHLIB_PATH:$TIBCO_TRA_HOME/libSHLIB_PATH=$SHLIB_PATH:$TIBCO_RV_HOME/libexport SHLIB_PATH

— For Solaris and Linux:

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$TIBCO_TRA_HOME/libLD_LIBRARY_PATH=$LD_LIBRARY_PATH:$TIBCO_RV_HOME/libexport LD_LIBRARY_PATH

— For AIX:LIBPATH=$LIBPATH:$TIBCO_TRA_HOME/libLIBPATH=$LIBPATH:$TIBCO_RV_HOME/libexport LIBPATH

3. The startWebLogic.sh file can be located under the <WebLogic_HOME>/config/<domain name> directory. Add the following



environment variables after the section related to setting WL_HOME. The environment variable must point to the installation directory for the product.




— export TIBCO_TPCL_HOME=<Third Party Core Libraries installation directory>


The startWebLogic.sh file sets the required environment for starting the WebLogic server. Add the following jar files to the CLASSPATH environment variable.

CLASSPATH=$CLASSPATH:$TIBCO_RV_HOME/lib/tibrvj.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOxml.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOrt.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOtsm.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOjms.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCrypt.jarCLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/EjbSupport.jarCLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/GlBeansSupport.jarCLASSPATH=$CLASSPATH:$TIBCO_TPCL_HOME/lib/xmlParserAPIs.jarCLASSPATH=$CLASSPATH:$TIBCO_TPCL_HOME/lib/xercesImpl.jar

4. In the startWebLogic.sh file, modify the LD_LIBRARY_PATH for the SunOS and Linux, SHLIB_PATH for HP-UX, and LIBPATH for AIX to include TIBCO Rendezvous shared objects.

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$TIBCO_RV_HOME/lib

5. In the command window from which you are starting the application server, set TIBCO_RV_HOME/bin in the PATH environment variable.


You can prepare the connector on the following platforms:






• UNIX Platforms



1. The setWLSEnv.cmd file is located under the <WebLogic_HOME>\server\bin directory. Add the following environment variables to the :setWLSEnv section of the file. The environment variable must point to the installation directory for the product.






The setWLSEnv.cmd file also sets the environment for user applications. Add the following jar files to the CLASSPATH environment variable in the :setWLSEnv section:


2. The startWLS.cmd file is located under the <WebLogic_HOME>\server\bin directory. Add the following environment variables to the :runWebLogic section of the file. The environment variable must point to the installation directory for the product.






The startWLS.cmd file sets the required environment for starting the WebLogic server. Add the following jar files to the CLASSPATH environment



variable in the:runWeblogic section of the script after the Set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar line.

set CLASSPATH=%CLASSPATH%;%TIBCO_RV_HOME%\lib\tibrvj.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOxml.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOrt.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOtsm.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOjms.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCrypt.jarset CLASSPATH=%CLASSPATH%;%TIBCO_ADEJB_HOME%\lib\EjbSupport.jarset CLASSPATH=%CLASSPATH%;%TIBCO_ADEJB_HOME%\lib\GlBeansSupport.jarset CLASSPATH=%CLASSPATH%;%TIBCO_ADEJB_HOME%\lib\AeConnector.jar

UNIX Platforms


1. The setWLSEnv.sh file can be located under the <WebLogic_HOME>/server/bin directory. Add the following environment variables after the section related to setting WL_HOME. The environment variable must point to the installation directory for the product.




— export TIBCO_TPCL_HOME=<Third party core libraries installation directory>


The setWLSEnv.sh file sets the environment for user applications. Add the following jar files to the CLASSPATH environment variable in the setWLSEnv.sh file.

CLASSPATH=$CLASSPATH:$TIBCO_RV_HOME/lib/tibrvj.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOxml.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOrt.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOtsm.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOjms.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCrypt.jarCLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/EjbSupport.jarCLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/GlBeansSupport.jarCLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/AeConnector.jar





CLASSPATH=$CLASSPATH:$TIBCO_TPCL_HOME/lib/xmlParserAPIs.jarCLASSPATH=$CLASSPATH:$TIBCO_TPCL_HOME/lib/xercesImpl.jar

2. At the end of the setWLSEnv.sh file add the following lines to update the LD_LIBRARY_PATH or SHLIB_PATH.

— For HP-UX:




— For AIX:LIBPATH =$LIBPATH:$TIBCO_TRA_HOME/libLIBPATH=$LIBPATH:$TIBCO_RV_HOME/libexport LIBPATH

3. The startWLS.sh file can be located under the <WebLogic_HOME>/server/bin directory. Add the following environment variables after the section related to setting WL_HOME. The environment variable must point to the installation directory for the product.






The startWLS.sh file sets the required environment for starting the WebLogic server. Add the following jar files to the CLASSPATH environment variable.

CLASSPATH=$CLASSPATH:$TIBCO_RV_HOME/lib/tibrvj.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOxml.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOrt.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOtsm.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOjms.jarCLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCrypt.jarCLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/EjbSupport.jarCLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/GlBeansSupport.jarCLASSPATH=$CLASSPATH:$TIBCO_TPCL_HOME/lib/xmlParserAPIs.jarCLASSPATH=$CLASSPATH:$TIBCO_TPCL_HOME/lib/xercesImpl.jar

4. In the startWLS.sh file, modify the LD_LIBRARY_PATH for the SunOS and Linux, SHLIB_PATH for HP-UX, and LIBPATH for AIX to include the TIBCO Rendezvous shared objects.





BEA WebLogic Application Server 8.1, BEA WebLogic Application Server 8.1 with SP1, SP2, SP3, SP4, SP5, and SP6

You can prepare the connector on the following:


• UNIX Platforms



1. The setWLSEnv.cmd file is located under the WebLogic_HOME>\server\bin directory. Add the following environment variables to the :setWLSEnv section of the file. The environment variable must point to the installation directory for the product.






The setWLSEnv.cmd file also sets the environment for user applications. Add the following jar files to the CLASSPATH environment variable in the :setWLSEnv section after the section after the set:CLASSPATH=%WEBLOGIC_CLASSPATH%;%CLASSPATH% line:

set CLASSPATH=%CLASSPATH%;%TIBCO_RV_HOME%\lib\tibrvj.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOxml.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOrt.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOtsm.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOjms.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCrypt.jar





set CLASSPATH=%CLASSPATH%;%TIBCO_ADEJB_HOME%\lib\EjbSupport.jarset CLASSPATH=%CLASSPATH%;%TIBCO_ADEJB_HOME%\lib\GlBeansSupport.jarset CLASSPATH=%CLASSPATH%;%TIBCO_ADEJB_HOME%\lib\AeConnector.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TPCL_HOME%\lib\xmlParserAPIs.jarset CLASSPATH=%CLASSPATH%;%TIBCO_TPCL_HOME%\lib\xercesImpl.jar







The startWLS.cmd file sets the required environment for starting the WebLogic server. Add the following jar files to the CLASSPATH environment variable in the:runWeblogic section of the script after the Set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar line.


UNIX Platforms

To configure the application server:

1. The setWLSEnv.sh file is located under the following directory:

<WebLogic_HOME>/server/bin


• For the publication and request-response invocation services, add all the jar files present in the <TPCL_HOME>/lib/entrust directory to the WebLogic classpath.



2. Add the following environment variables after the section related to setting WL_HOME. The environment variable must point to the installation directory for the product.






The setWLSEnv.sh file also sets the environment for user applications. Add the following jar files to the CLASSPATH environment variable:

export CLASSPATH=$CLASSPATH:$TIBCO_RV_HOME/lib/tibrvj.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOxml.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOrt.jarexport CLASSPATH=$CLASSPATHVTIBCO_TRA_HOME/lib/TIBCOtsm.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOjms.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCrypt.jarexport CLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/EjbSupport.jarexport CLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/GlBeansSupport.jarexport CLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/AeConnector.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TPCL_HOME/lib/xmlParserAPIs.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TPCL_HOME/lib/xercesImpl.jar


— For HP-UX:





4. The startWLS.sh file is located under the following directory:











export CLASSPATH=$CLASSPATH:$TIBCO_RV_HOME/lib/tibrvj.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOxml.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOrt.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOtsm.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOjms.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCrypt.jarexport CLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/EjbSupport.jarexport CLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/GlBeansSupport.jarexport CLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/AeConnector.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TPCL_HOME/lib/xmlParserAPIs.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TPCL_HOME/lib/xercesImpl.jar

6. In the startWLS.sh file, modify the LD_LIBRARY_PATH for the SunOS and Linux, SHLIB_PATH for HP-UX, and LIBPATH for AIX to include TIBCO Rendezvous shared objects.



BEA WebLogic Application Server 9.0, 9.1, and 9.2You can prepare the connector on the following:


• UNIX Platforms







1. The setWLSEnv.cmd file is located under the WebLogic_HOME>\server\bin directory. Add the following environment variables to the :setWLSEnv section of the file. The environment variable must point to the installation directory for the product.






The setWLSEnv.cmd file also sets the environment for user applications. Add the following jar files to the CLASSPATH environment variable in the :setWLSEnv section after the section after the set:CLASSPATH=%WEBLOGIC_CLASSPATH%;%CLASSPATH% line:








The startWLS.cmd file sets the required environment for starting the WebLogic server. Add the following jar files to the CLASSPATH environment



variable in the:runWeblogic section of the script after the Set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar line.


UNIX Platforms

To configure the application server:

1. The setWLSEnv.sh file is located under the following directory:








The setWLSEnv.sh file also sets the environment for user applications. Add the following jar files to the CLASSPATH environment variable:

export CLASSPATH=$CLASSPATH:$TIBCO_RV_HOME/lib/tibrvj.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOxml.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOrt.jarexport CLASSPATH=$CLASSPATHVTIBCO_TRA_HOME/lib/TIBCOtsm.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOjms.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCrypt.jarexport CLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/EjbSupport.jar





export CLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/GlBeansSupport.jarexport CLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/AeConnector.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TPCL_HOME/lib/xmlParserAPIs.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TPCL_HOME/lib/xercesImpl.jar


— For HP-UX:





4. The startWLS.sh file is located under the following directory:









export CLASSPATH=$CLASSPATH:$TIBCO_RV_HOME/lib/tibrvj.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOxml.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOrt.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOtsm.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOjms.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TRA_HOME/lib/TIBCrypt.jarexport CLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/EjbSupport.jarexport CLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/GlBeansSupport.jarexport CLASSPATH=$CLASSPATH:$TIBCO_ADEJB_HOME/lib/AeConnector.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TPCL_HOME/lib/xmlParserAPIs.jarexport CLASSPATH=$CLASSPATH:$TIBCO_TPCL_HOME/lib/xercesImpl.jar



6. In the startWLS.sh file, modify the LD_LIBRARY_PATH for the SunOS and Linux, SHLIB_PATH for HP-UX, and LIBPATH for AIX to include TIBCO Rendezvous shared objects.



IBM WebSphere 5.1 Application ServerTo install and set up the application server, follow the steps highlighted in http://www-3.ibm.com/software/webservers/appserv/library/index.html. The trial version of Application Server can be downloaded from the IBM web site, at http://www-3.ibm.com/software/websphere/info/platformv5/wstrialv5.jsp.

Set the following environment variables. The environment variable must point to the installation directory for the product.

— TIBCO_TRA_HOME=<TRA installation directory>

— TIBCO_RV_HOME=<TIBCO Rendezvous installation directory>

— TIBCO_ADEJB_HOME=<Adapter installation directory>

— TIBCO_TPCL_HOME=<Third party core libraries installation directory>

— WAS_HOME=<WebSphere installation directory>

— TIBCO_JRE_HOME=<JRE installation directory>






1. Copy the following jar files to the location of IBM WebSphere Application server, <WAS_HOME>/lib/ext:

— <TIBCO_ADEJB_HOME>/<version_num>/lib/EjbSupport.jar

— <TIBCO_TRA HOME>/lib/TIBCOrt.jar

— <TIBCO_TRA HOME>/lib/TIBCOxml.jar

— <TIBCO_TRA HOME>/lib/TIBCOtsm.jar

— <TIBCO_TRA HOME>/lib/TIBCOjms.jar

— <TIBCO_TRA HOME>/lib/TIBCrypt.jar

— <TIBCO_RV_HOME>/lib/tibrvj.jar

— <TIBCO_TPCL_HOME>/5.3/lib/xmlParserAPIs.jar

— <TIBCO_TPCL_HOME>/5.3/lib/xercesImpl.jar

2. Modify the LIBRARY PATHs in the startServer.sh script on UNIX. This file is located in the <WAS_HOME>/bin directory:

TIBCO_RV_HOME=<TIBCO Rendezvous installation directory>export TIBCO_RV_HOME

PLATFORM=`/bin/uname`case $PLATFORM in AIX)

EXTSHM=ONLIBPATH="$WAS_LIBPATH":$TIBCO_RV_HOME/lib:$LIBPATHexport LIBPATH EXTSHM ;;

Linux)LD_LIBRARY_PATH="$WAS_LIBPATH":$TIBCO_RV_HOME/lib:$LD_LIBRARY_PATHexport LD_LIBRARY_PATH ;;SunOS)LD_LIBRARY_PATH="$WAS_LIBPATH":$TIBCO_RV_HOME/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH ;;HP-UX)SHLIB_PATH="$WAS_LIBPATH":$TIBCO_RV_HOME/lib:$SHLIB_PATHexport SHLIB_PATH ;;

On UNIX:

Define the TIBCO_RV_HOME variable in the startServer.sh script that will be used to start the application server.

In the command window from which you are starting the application server, set TIBCO_RV_HOME/bin in the PATH environment variable.



esac

IBM WebSphere 6.0, 6.0.2, and 6.1 Application ServersTo install and set up the application server, follow the steps highlighted in http://www-3.ibm.com/software/webservers/appserv/library/index.html. The trial version of Application Server can be downloaded from the IBM web site, at http://www-3.ibm.com/software/websphere/info/platformv5/wstrialv5.jsp.






— WAS_HOME=<WebSphere installation directory>



• For the publication and request-response invocation services, copy all the jar files present in <TPCL_HOME>/lib/entrust to the <WAS_HOME>/lib/ext directory.




1. Copy the following jar files to the location of IBM WebSphere Application server, <WAS_HOME>/lib/ext:

— <TIBCO_ADEJB_HOME>/<version_num>/lib/EjbSupport.jar

— <TIBCO_TRA HOME>/lib/TIBCOrt.jar

— <TIBCO_TRA HOME>/lib/TIBCOxml.jar

— <TIBCO_TRA HOME>/lib/TIBCOtsm.jar

— <TIBCO_TRA HOME>/lib/TIBCOjms.jar

— <TIBCO_TRA HOME>/lib/TIBCrypt.jar

— <TIBCO_RV_HOME>/lib/tibrvj.jar

— <TIBCO_TPCL_HOME>/5.3/lib/xmlParserAPIs.jar

— <TIBCO_TPCL_HOME>/5.3/lib/xercesImpl.jar

2. Modify the LIBRARY PATHs in the startServer.sh script on UNIX. This file is located in the <WAS_HOME>/bin directory:

TIBCO_RV_HOME=<TIBCO Rendezvous installation directory>export TIBCO_RV_HOME

PLATFORM=`/bin/uname`case $PLATFORM in AIX)

EXTSHM=ONLIBPATH="$WAS_LIBPATH":$TIBCO_RV_HOME/lib:$LIBPATHexport LIBPATH EXTSHM ;;

Linux)LD_LIBRARY_PATH="$WAS_LIBPATH":$TIBCO_RV_HOME/lib:$LD_LIBRARY_PATHexport LD_LIBRARY_PATH ;;SunOS)LD_LIBRARY_PATH="$WAS_LIBPATH":$TIBCO_RV_HOME/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH ;;HP-UX)SHLIB_PATH="$WAS_LIBPATH":$TIBCO_RV_HOME/lib:$SHLIB_PATHexport SHLIB_PATH ;;

On UNIX:

Define the TIBCO_RV_HOME variable in the startServer.sh script that will be used to start the application server.




esac

Sun Java System Application Server Platform Edition 7To install and configure the Sun Java System Application Server Platform Edition 7, follow the steps outlined in:

• http://docs.sun.com/

• http://wwws.sun.com/software/products/appsrvr/appsrvr_download.html








1. Click Start > Programs > Sun Microsystems > Sun ONE Application Server V7 > Start Application Server to start the application server. The application server will take a few minutes to start.

2. Click Start > Programs > Sun Microsystems > Sun ONE Application Server V7 > Start Administrative Console to start the administrative console. A browser with two panels is displayed.

3. Click JVM Settings and then click Path Settings and enter a class path.


• For the publication and request-response invocation services, copy all the jar files present in <TPCL_HOME>/lib/entrust to the <WAS_HOME>/lib/ext directory.

On UNIX, in the command window from which you are starting the application server, set TIBCO_RV_HOME/bin in the PATH environment variable.



4. Enter the following jar files in the Class Path suffix field, and use the semicolon (;) as a file separator:

— <TIBCO_ADEJB_HOME>\lib\EjbSupport.jar

— <TIBCO_ADEJB_HOME>\lib\AeConnector.jar

— <TIBCO_TRA HOME>\lib\TIBCOrt.jar

— <TIBCO_TRA HOME>\lib\TIBCOxml.jar

— <TIBCO_TRA HOME>\lib\TIBCOtsm.jar

— <TIBCO_TRA HOME>\lib\TIBCOjms.jar

— <TIBCO_TRA HOME>\lib\TIBCrypt.jar

— <TIBCO_RV_HOME>\lib\tibrvj.jar

— <TIBCO_TPCL_HOME>\lib\xmlParserAPIs.jar

— <TIBCO_TPCL_HOME>\lib\xercesImpl.jar

5. Enter D:\tibco\tra\5.3\bin in the Native path prefix and Native path suffix fields.

6. Add the following to the end of the server.policy file that is present in the <APPSERVER_HOME>\domains\domain1\server1\config directory:

// Permissions for TIBCO Rendezvous"grant {permission java.util.PropertyPermission "*", "read,write";};

Sun Java System Application Server Platform Edition 8.1To install and configure the Sun Java System Application Server Platform Edition 8.1, follow the steps outlined in:

• http://docs.sun.com/

• http://www.sun.com/software/products/appsrvr/index.xml










1. Click Start > Programs > Sun Microsystems > Application Server PE > Start Default Server to start the application server. The application server will take a few minutes to start.

2. Click Start > Programs > Sun Microsystems > Application Server PE > Admin Console to start the administrative console. A browser with two panels is displayed.

3. Click JVM Settings and then click Path Settings and enter a class path.

4. Enter the following jar files in the Class Path suffix field, and use the semicolon (;) as a file separator:

— <TIBCO_ADEJB_HOME>\lib\EjbSupport.jar

— <TIBCO_ADEJB_HOME>\lib\AeConnector.jar

— <TIBCO_TRA HOME>\lib\TIBCOrt.jar

— <TIBCO_TRA HOME>\lib\TIBCOxml.jar

— <TIBCO_TRA HOME>\lib\TIBCOtsm.jar

— <TIBCO_TRA HOME>\lib\TIBCOjms.jar

— <TIBCO_TRA HOME>\lib\TIBCrypt.jar

— <TIBCO_RV_HOME>\lib\tibrvj.jar

— <TIBCO_TPCL_HOME>\lib\xmlParserAPIs.jar

— <TIBCO_TPCL_HOME>\lib\xercesImpl.jar

5. Enter D:\tibco\tra\5.3\bin in the Native path prefix and Native path suffix fields.




6. Append the following to the end of the server.policy file present in the <APPSERVER_HOME>\domains\domain1\server1\config directory:

// Permissions for TIBCO Rendezvous"grant {permission java.util.PropertyPermission "*", "read,write";};

Oracle 9i Application ServerTo install and set up the supported container for this application server, follow the procedure outlined in http://otn.oracle.com/tech/java/oc4j/htdocs/oc4j-install-note.html (for J2EE 1.3 Developer Preview). You can download the Oracle9iAS Containers with J2EE 1.3 Developer Preview from http://otn.oracle.com/tech/java/oc4j/htdocs/utilsoft.html.

Before you start, do the following:

1. Set the following environment variables. The environment variable must point to the installation directory for the product.





— ORACLE9IAS-HOME=<Oracle 9i application server installation>


Oracle J2EE containers have a predefined configuration stored in the server-side configuration file — server.xml. If you want to make a Java library available to the application server, the library reference must be added in the server.xml file. This file is located in the <ORACLE9IAS-ROOT>\j2ee\home\config directory.

For example, if you have installed the adapter at D:\tibco\adapter\adejb\<version_num>; the TRA at D:\tibco\tra\5.3; TPCL at D:\tibco\tpcl\5.3; and TIBCO Rendezvous at D:\tibco\tibrv, you would add the following entry to server.xml file:<library path="<Existing_Jar_Files>;D:\Tibco\adapter\adejb\<version_num>\lib\EjbSupport.jar;D:\Tibco\adapter\adejb\<version_num>\lib\AeConnector.jar;D:\Tibco\tra\5.3\lib\TIBCOrt.jar;D:\Tibco\tra\5.3\lib\TIBCOjms.jar; D:\Tibco\tra\5.3\lib\TIBCOtsm.jar;D:\Tibco\tra\5.3\lib\TIBCOxml.jar;D:\Tibco\tra\5.3\lib\TIBCrypt



.jar;D:\Tibco\tpcl\5.1\lib\xmlParserAPIs.jar;D:\Tibco\tpcl\5.3\lib\xercesImpl.jar;D:\tibco\tibrv\lib\tibrvj.jar;"/>

Oracle 10g Application ServerYou can download the Oracle10gAS Containers for J2EE 10g from http://www.oracle.com/technology/software/htdocs/devlic.html?/technology/software/products/ias/htdocs/utilsoft.html#1012

To install and set up the supported container for this application server, follow the procedure outlined in http://otn.oracle.com/tech/java/oc4j/htdocs/oc4j-install-note.html. (Even though these instructions are specifically for Oracle 9iAS, they can be used for Oracle 10gAS also.

Before you start, do the following:






— ORACLE10gAS-HOME=<Oracle 10g application server installation>


Oracle J2EE containers have a predefined configuration stored in the server-side configuration file —application.xml. If you want to make a Java library available to the application server, the library reference must be added in the server.xml file. This file is located in the with <ORACLE10gAS-ROOT>\j2ee\home\config directory.

For example, if you have installed the adapter at D:\tibco\adapter\adejb\<version_num>; the TRA at D:\tibco\tra\5.3;

If you are using the HTTPS protocol to access the repository or if you are using a repository present in a repository server, do the following for the subscription and request-response server services:




TPCL at D:\tibco\tpcl\5.3; and TIBCO Rendezvous at D:\tibco\tibrv, you would add the following entry to server.xml file:<library path="<Existing_Jar_Files>;D:\Tibco\adapter\adejb\<version_num>\lib\EjbSupport.jar;D:\Tibco\adapter\adejb\<version_num>\lib\AeConnector.jar;D:\Tibco\tra\5.3\lib\TIBCOrt.jar;D:\Tibco\tra\5.3\lib\TIBCOjms.jar; D:\Tibco\tra\5.3\lib\TIBCOtsm.jar;D:\Tibco\tra\5.3\lib\TIBCOxml.jar;D:\Tibco\tra\5.3\lib\TIBCrypt.jar;D:\Tibco\tpcl\5.3\lib\xmlParserAPIs.jar;D:\Tibco\tpcl\5.3\lib\xercesImpl.jar;D:\tibco\tibrv\lib\tibrvj.jar;"/>

JBoss 3.2.3 Application ServerYou can prepare the connector on the following:


• UNIX Platforms




— JBOSS_HOME=<JBOSS installation directory>




— TIBCO_TPCL_HOME=<Third Part Core Libraries installation directory>


2. Add the following classpath to the run.bat file located in the <JBOSS_HOME>\bin directory:

set TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_RV_HOME%\lib\tibrvj.jarset TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOrt.jar

If you are using the HTTPS protocol to access the repository or if you are using a repository present in a repository server, do the following for the subscription and request-response server services:




set TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOjms.jarset TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCrypt.jarset TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOtsm.jarset TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOxml.jarset TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_ADEJB_HOME%\lib\EjbSupport.jarset TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_ADEJB_HOME%\lib\GlBeansSupport.jarset TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_ADEJB_HOME%\lib\AeConnector.jarset TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_TPCL_HOME%\lib\xmlParserAPIs.jarset TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_TPCL_HOME%\lib\xercesImpl.jarset TIBCLASSPATH=%TIBCLASSPATH%;%JBOSS_HOME%\server\default\lib\jboss-j2ee.jar

3. Add the following variable to the JBOSS classpath in the run.bat file in the <JBOSS_HOME>\bin directory:

set JBOSS_CLASSPATH=%JBOSS_CLASSPATH%;%JAVAC_JAR%;%RUNJAR%;%TIBCLASSPATH%

UNIX Platforms








2. Add the following classpath to the run.bat file located in the <JBOSS_HOME>/bin directory:

export TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_RV_HOME/lib/tibrvj.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOrt.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOjms.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_TRA_HOME/lib/TIBCrypt.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOtsm.jar


• For the publication and request-response invocation services, add all the jar files present in the <TPCL_HOME>/lib/entrust directory to the JBoss classpath.




export TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOxml.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_ADEJB_HOME/lib/EjbSupport.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_ADEJB_HOME/lib/GlBeansSupport.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_ADEJB_HOME/lib/AeConnector.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_TPCL_HOME/lib/xmlParserAPIs.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_TPCL_HOME/lib/xercesImpl.jarexport TIBCLASSPATH=$TIBCLASSPATH:$JBOSS_HOME/server/default/lib/jboss-j2ee.jar

3. Add the following variable to the JBOSS classpath in the run.sh file in the <JBOSS_HOME>/bin directory:

export JBOSS_CLASSPATH=$JBOSS_CLASSPATH:$JAVAC_JAR:$RUNJAR:TIBCLASSPATH

JBoss 4.0.0, 4.0.1, 4.0.2, 4.0.3, and 4.0.4 Application ServersYou can prepare the connector on the following:


• UNIX Platforms










2. Add the following classpath to the run.bat file located in the <JBOSS_HOME>\bin directory:

set TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_RV_HOME%\lib\tibrvj.jarset TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOrt.jar





set TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOjms.jarset TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCrypt.jarset TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOtsm.jarset TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_TRA_HOME%\lib\TIBCOxml.jarset TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_ADEJB_HOME%\lib\EjbSupport.jarset TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_ADEJB_HOME%\lib\GlBeansSupport.jarset TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_ADEJB_HOME%\lib\AeConnector.jarset TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_TPCL_HOME%\lib\xmlParserAPIs.jarset TIBCLASSPATH=%TIBCLASSPATH%;%TIBCO_TPCL_HOME%\lib\xercesImpl.jarset TIBCLASSPATH=%TIBCLASSPATH%;%JBOSS_HOME%\server\default\lib\jboss-j2ee.jarset TIBCLASSPATH=%TIBCLASSPATH%;%JBOSS_HOME%\client\jmx-client.jarset TIBCLASSPATH=%TIBCLASSPATH%;%JBOSS_HOME%\client\jboss-common-client.jarset TIBCLASSPATH=%TIBCLASSPATH%;%JBOSS_HOME%\client\concurrent.jarset TIBCLASSPATH=%TIBCLASSPATH%;%JBOSS_HOME%\client\log4j.jarset TIBCLASSPATH=%TIBCLASSPATH%;%JBOSS_HOME%\lib\dom4j.jarset TIBCLASSPATH=%TIBCLASSPATH%;%JBOSS_HOME%\lib\jboss-system.jar

3. Add the following variable to the JBOSS classpath in the run.bat file in the <JBOSS_HOME>\bin directory:

set JBOSS_CLASSPATH=%JBOSS_CLASSPATH%;%JAVAC_JAR%;%RUNJAR%;%TIBCLASSPATH%

UNIX Platforms








2. Add the following classpath to the run.bat file located in the <JBOSS_HOME>/bin directory:






export TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_RV_HOME/lib/tibrvj.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOrt.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOjms.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_TRA_HOME/lib/TIBCrypt.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOtsm.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_TRA_HOME/lib/TIBCOxml.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_ADEJB_HOME/lib/EjbSupport.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_ADEJB_HOME/lib/GlBeansSupport.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_ADEJB_HOME/lib/AeConnector.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_TPCL_HOME/lib/xmlParserAPIs.jarexport TIBCLASSPATH=$TIBCLASSPATH:$TIBCO_TPCL_HOME/lib/xercesImpl.jarexport TIBCLASSPATH=$TIBCLASSPATH:$JBOSS_HOME/server/default/lib/jboss-j2ee.jarexport TIBCLASSPATH=$TIBCLASSPATH;$JBOSS_HOME/client/jmx-client.jarexport TIBCLASSPATH=$TIBCLASSPATH;$JBOSS_HOME/client/jboss-common-client.jarexport TIBCLASSPATH=$TIBCLASSPATH;$JBOSS_HOME/client/concurrent.jarexport TIBCLASSPATH=$TIBCLASSPATH;$JBOSS_HOME/client/log4j.jarexport TIBCLASSPATH=$TIBCLASSPATH;$JBOSS_HOME/lib/dom4j.jarexport TIBCLASSPATH=$TIBCLASSPATH;$JBOSS_HOME/lib/jboss-system.jar

3. Add the following variable to the JBOSS classpath in the run.sh file in the <JBOSS_HOME>/bin directory:

export JBOSS_CLASSPATH=$JBOSS_CLASSPATH:$JAVAC_JAR:$RUNJAR:TIBCLASSPATH


For the publication and request-response invocation services, add all the jar files present in the <TPCL_HOME>/lib/entrust directory to the JBoss classpath.


Deploying the Connector | 99

Deploying the Connector

This section describes how to deploy the connector for the application server you are using. The adapter installation by default is configured to run using a local repository. However, in case there are problems in the installation, you must configure the connector to run with the local repository. See Modifying the Repository URL, Configuration URL and TRA File Name of the Connector Configuration on page 60, which explains the specific procedure for each of the supported application servers.

BEA WebLogic Application Server 6.1 with SP1, SP2, or SP3You can deploy the connector on the following:


• UNIX Platforms


To deploy the connector:

1. Start the application server by running the following commands in the <WebLogic_HOME>\config\<domain name> directory:

— setEnv.cmd

— startWebLogic.cmd

2. Click Start > Programs > BEA WebLogic E-Business Platform > WebLogic <version_num> > Start Default Console to start the Administrator Console.

3. Select Connectors under the Deployments section and then click Install a New Connector Component.

4. Click Browse to select the AeConnector.rar file from the <ADEJB_HOME>\lib directory.

5. Click Upload to deploy the connector in the container.

UNIX Platforms


1. At the command prompt, go to the <WebLogic_HOME>/config/<domain name> directory and run startWebLogic.sh.

2. Start the Administrator Console.



3. Select Connectors under the Deployments section and then click Install a New Connector Component.

4. Click Browse to select the AeConnector.rar file from the <ADEJB_HOME>/lib directory.

5. Click Upload to deploy the connector in the container.


You can deploy the connector on the following:


• UNIX Platforms



1. Start the application server by running the following commands in the <WebLogic_HOME>\server\bin directory:

— setWLSEnv.cmd

— startWLS.cmd

2. Click Start > Programs > BEA WebLogic Platform 7.0 > WebLogic Server 7.0 > Server Tour and Examples > Start Admin Console.

3. Enter your user name and password.

4. Click Connectors under the Domain Configuration section and then click Configure a new Connector Component.

5. Click upload it through your browser.

6. Click Browse to select the AeConnector.rar file from the <ADEJB_HOME>\lib directory.

7. Click Upload to deploy the connector in the container. The file will be listed in the browser.

8. Click Select for the connector.

9. Choose your application server from the Available Servers list and move it to the Target Servers list. The connector, AeConnector.rar, will be displayed in the Enter a name for this application field.

10. Click Configure and Deploy to deploy the connector.



UNIX Platforms


1. At the command prompt, go to the <WebLogic_HOME>\server\bin directory and run startWLS.sh.

2. Enter your username and password.

3. Click Connectors under the Domain Configuration section and then click Configure a new Connector Component.


5. Click Browse to select the AeConnector.rar file from the <ADEJB_HOME>/lib directory.

6. Click Upload to deploy the connector in the container. The file will be listed in the browser.

7. Click Select for the connector.

8. Choose your application server from the Available Servers list and move it to the Target Servers list. The connector, AeConnector.rar, will be displayed in the Enter a name for this application field.

9. Click Configure and Deploy to deploy the connector.

BEA WebLogic Application Server 8.1 and BEA WebLogic Application Server 8.1 with SP1, SP2, SP3, SP4, SP5, and SP6

You can deploy the connector on both Microsoft Windows and UNIX platforms.


1. Start the WebLogic server:

— At the command prompt, go to the <WebLogic_HOME>\server\bin directory on Microsoft Windows and run the startWLS command

— At the command prompt, go to the <WebLogic_HOME>/server/bin directory and run the startWLS.sh command

2. Start the Administrator Console:

— Click Start > Programs > BEA WebLogic Platform 8.1 > Examples > WebLogic Server Examples > Server Admin Console on Microsoft Windows

3. Type the username and password to start the WebLogic server.

4. Click Connector Modules under Deployments.

5. Click Deploy a new Connector Module.



6. Click Upload your file(s).

7. Click Browse and choose AeConnector.rar under the <ADEJB_HOME>\lib directory.

8. Click the myserver folder.

9. Click Upload folder.

10. Select AeConnector.rar and click Target module.

11. Click Deploy. The Status of Last Action column will display a message that states that the deployment is successful.

BEA WebLogic Application Server 9.0, 9.1, and 9.2You can deploy the connector on both Microsoft Windows and UNIX platforms.


1. Start the WebLogic server:

— At the command prompt, go to the <WebLogic_HOME>\server\bin directory on Microsoft Windows and run the startWLS command.

— At the command prompt, go to the <WebLogic_HOME>/server/bin directory on UNIX and run the startWLS.sh command.

2. Start the Administrator Console:

3. Type the username and password to start the WebLogic server.

4. Click Lock & Edit under Change Center.

5. Click Deployments under Domain Structure.

6. Click Install under Deployments.

7. Choose AeConnector.rar under the <ADEJB_HOME>\lib directory.

8. Click Next.

9. Choose Install this deployment as an application and click Next.

10. Click Next.

11. Click Finish.

12. Click Save to save the changes.

13. Click Activate Changes under Change Center.




14. Click Deployments under Domain Structure.

15. Select the check box for AeConnector under deployments. Click Start > Servicing all requests.

The State column will display the Active value if the deployment is successful.

IBM WebSphere 5.1 Application ServerYou can deploy the connector on both Microsoft Windows and UNIX platforms. Deploying the connector involves the following tasks:

• Starting the application server

• Adding a connection factory:

Task A Starting the application server

1. To start the server:

— On Microsoft Windows, select Start > Programs > IBM WebSphere > Application Server V5.0 > Start the Server to start the WebSphere Application Server 5.0. The application server may take a few minutes to start.

— On UNIX, go to the <WebSphere_HOME>/bin directory and run startServer <node_name>.

2. To start the administrative console:

— On Microsoft Windows, select Start > Programs > IBM WebSphere > Application Server V5.0 > Administrative Console to start the administrative console. A browser with two panels is displayed.

— On UNIX, open a browser window and in the Address field enter <local host>://<port>/admin/.

3. Click Resources and then click Resource Adapters. The Resource Adapters page is displayed.

4. Click Install RAR, to install the connector.

5. Click Browse to locate the AeConnector.rar file. This file is in the lib subdirectory of the adapter installation.




6. Select Node depending on which machine you will use to install the connector. By default, only the local machine is listed.

7. Click Next to continue installing the connector.

8. Enter the connector name as TIBCOAeConnector in the Name field.

9. Click OK to complete the deployment. The connector, TIBCOAeConnector, is displayed.

10. Click Save to apply changes to the master configuration.

Task B Adding a connection factory:



3. Click New to display the J2C Connection Factory Properties window.

4. Enter the connection reference name as TIBCOAeConnector in the Name field.

5. Enter the JNDI binding path as tibco/aeconnector in the JNDI Name field.

6. Click Apply to create a connection factory.

7. Click Save to save the master configuration.


9. Click J2C Connection Factories under TibcoAeConnector.



12. Select the RepoUrl property and enter the <repoUrl> in the Value field.

For example, D:/tibco/adapter/adejb/<version_num>/examples/data/ejb_sample.d

at

13. Click OK.

14. Select the ConfigUrl property and enter the <configUrl> in the Value field.

For example, /tibco/private/adapter/Connector/RPC/EJBAdapter

15. Click OK.

16. Select the TraFileName property and enter d:\tibco\adapter\adejb\<version_num>\bin\connector.tra




IBM WebSphere 6.0 and 6.0.2 Application ServersYou can deploy the connector on both Microsoft Windows and UNIX platforms.

Deploying the connector involves the following tasks:

• Starting the application server

• Adding a connection factory

Task A Starting the application server

1. To start the server:

• On Microsoft Windows, select Start > Programs > IBM WebSphere > Application Server V6.0 > Profiles > <Server Name> > Start the server to start WebSphere Application Server 6.0. The application server may take a few minutes to start.

• On UNIX, go to the <WebSphere_HOME>/bin directory and run startServer <node_name>.

To start the administrative console:

1. Do one of the following:

— On Microsoft Windows, select Start > Programs > IBM WebSphere > Application Server V6.0 > Profiles -> <Server Name>Administrative Console to start the administrative console. A browser with two panels is displayed.

— On UNIX, open a browser window and in the Address field enter <localhost>://<port>/admin/.

2. Enter the User Id to continue.

3. Click Resources and then click Resource Adapters. The Resource Adapters page is displayed.

4. Click Install RAR, to install the connector.

5. Click Browse to locate the AeConnector.rar file. This file is in the lib subdirectory of the adapter installation.

6. Click Next to continue installing the connector.

7. Enter the connector name as TIBCOAeConnector in the Name field.

8. Click OK to complete the deployment. The connector, TIBCOAeConnector, is displayed.

9. Click Save to apply changes to the master configuration.



Task B Adding a Connection Factory



3. Click New to display the J2C Connection Factory Properties window.


5. Enter the JNDI binding path as tibco/aeconnector in the JNDI Name field.

6. Click Apply to create a connection factory.



9. Click J2C Connection Factories under TibcoAeConnector.



12. Select the RepoUrl property and enter the <repoUrl> in the Value field. For example, D:/tibco/adapter/adejb/<version_num>/examples/data/ejb_sample.d

at

13. Click OK.

14. Select the ConfigUrl property and enter the <configUrl> in the Value field. For example, /tibco/private/adapter/Connector/RPC/EJBAdapter

15. Click OK.

16. Select the TraFileName property and enter, d:\tibco\adapter\adejb\<version_num>\bin\connector.tra

17. Click OK. Click Save to save the master configuration.

Task C Adding a Activation Specification


2. Click TibcoAeConnector and then J2C Activation specifications.

3. Click New to display the J2C Activation Specification properties window




5. Enter the JNDI binding path as tibco/resourceadapter in the JNDI Name field.

6. Click Apply to create an activation specification.


Sun Java System Application Server Platform Edition 7You can deploy the connector on both Microsoft Windows and UNIX platforms.


1. Click Start > Programs > Sun Microsystems > Sun ONE Application Server V7 > Start Application Server to start the application server. Typically, the application server will take a few minutes to start.

2. Click Start > Programs > Sun Microsystems > Sun ONE Application Server V7 > Start Administrative Console to start the administrative console. A browser with two panels is displayed.

3. Click Applications for your server instance.

4. Click Connector Modules.

5. Click Deploy to install the connector.

6. Click Browse to locate the AeConnector.rar file in the <ADEJB_HOME>\lib directory.

7. Click OK to complete the deployment of the connector. A window is displayed and the connector is named TIBCOAeConnector.

Sun Java System Application Server Platform Edition 8.1You can deploy the connector on both Microsoft Windows and UNIX platforms.


1. Click Start >Programs >Sun Microsystems >Application Server PE >Start Default Server to start the application server. Typically, the application server will take a few minutes to start.

2. Click Start > Programs > Sun Microsystems > Application Server PE > Admin Console to start the administrative console. A browser with two panels is displayed.

3. Click Applications for your server instance.



4. Click Connector Modules.

5. Click Deploy to install the connector.

6. Click Browse to locate the AeConnector.rar file in the <ADEJB_HOME>\lib directory.

7. Click OK to complete the deployment of the connector. A window is displayed and the connector is named TIBCOAeConnector.

Oracle 9i Application ServerYou can deploy the connector on both Microsoft Windows and UNIX platforms.


1. Create a subdirectory called standalone in the <ORACLE9IAS-ROOT>/j2ee/home/connectors directory.

2. Add the following code to the oc4j-connectors.xml file in the <ORACLE9IAS-ROOT>/j2ee/home/config/ directory.

If this file does not exist, create it, and add the following information. If the file already exists, only add the content marked in the bold type face.

------------------------------------------------------------------<?xml version="1.0" standalone='yes'?><!DOCTYPE oc4j-connectors PUBLIC "-//Oracle//DTD Connectors configuration//EN" "http://xmlns.oracle.com/ias/dtds/oc4j-connectors.dtd"><oc4j-connectors>

<connector name="standalone" path="AeConnector.rar"></connector>

</oc4j-connectors>------------------------------------------------------------------

3. In the <ORACLE9IAS-ROOT>/j2ee/home/config/server.xml file, make sure that the connector-directory attribute is specified in the <application-server> element as connector-directory="../connectors"

4. In the <ORACLE9IAS-ROOT>/j2ee/home/config/application.xml file, make sure the <connector path> element is defined under the <orion-application> element as follows:

<connectors path="./oc4j-connectors.xml"/>

5. Copy the Resource adapter (RAR) file (AeConnector.rar) from <ADEJB_HOME>/lib to the <ORACLE9IAS-ROOT>/j2ee/home/connectors/standalone directory.

6. Go to the <ORACLE9IAS-ROOT>/j2ee/home directory and run java -jar oc4j.jar to start the OC4J Container. OC4J will automatically unpack



AeConnector.rar in the <ORACLE9IAS-ROOT>/j2ee/home/connectors/standalone/AeConnector/ directory.

7. Restart the OC4J Container (Oracle Application Server).

8. Stop the container. The standalone directory will be created in <ORACLE9IAS-ROOT>/j2ee/home/application-deployments/default/ when you start the OC4J process. Copy oc4j-ra.xml from the <ORACLE9IAS-ROOT>/j2ee/home/connectors/standalone/AeConnector directory to the <ORACLE9IAS-ROOT>/j2ee/home/application-deployments/default/standalone directory.

Oracle 10g Application ServerYou can deploy the connector on both Microsoft Windows and UNIX platforms.


1. Create a subdirectory called standalone in the <ORACLE10gAS-ROOT>/j2ee/home/connectors directory.

2. Add the following code to the oc4j-connectors.xml file in the <ORACLE10gAS-ROOT>/j2ee/home/config/ directory.

If this file does not exist, create it, and add the following information. If the file already exists, only add the content marked in the bold type face.

------------------------------------------------------------------<?xml version="1.0" standalone='yes'?><!DOCTYPE oc4j-connectors PUBLIC "-//Oracle//DTD Connectors configuration//EN" "http://xmlns.oracle.com/ias/dtds/oc4j-connectors.dtd"><oc4j-connectors>

<connector name="standalone" path="AeConnector.rar"></connector>

</oc4j-connectors>------------------------------------------------------------------

3. In the <ORACLE10gAS-ROOT>/j2ee/home/config/server.xml file, make sure that the connector-directory attribute is specified in the <application-server> element as connector-directory="../connectors"

If you want to deploy the connector as a JAR (library) instead of a RAR, use the ejb-jar.xml file. EJB deployment descriptors should not refer to any Resource type.



4. In the <ORACLE10gAS-ROOT>/j2ee/home/config/application.xml file, make sure the <connector path> element is defined under the <orion-application> element as follows:

<connectors path="./oc4j-connectors.xml"/>

5. Copy the Resource adapter (RAR) file (AeConnector.rar) from <ADEJB_HOME>/lib to the <ORACLE10gAS-ROOT>/j2ee/home/connectors/standalone directory.

6. Go to the <ORACLE10gAS-ROOT>/j2ee/home directory and run java -jar oc4j.jar to start the OC4J Container. OC4J will automatically unpack AeConnector.rar in the <ORACLE10gAS-ROOT>/j2ee/home/connectors/standalone/AeConnector/ directory.

7. Restart the OC4J Container (Oracle Application Server).

8. Stop the container. The standalone directory will be created in <ORACLE10gAS-ROOT>/j2ee/home/application-deployments/default/ when you start the OC4J process. Copy oc4j-ra.xml from the <ORACLE10gAS-ROOT>/j2ee/home/connectors/standalone/AeConnector directory to the <ORACLE10gAS-ROOT>/j2ee/home/application-deployments/default/standalone directory.

JBoss 3.2.3 Application ServerYou can deploy the connector on the following:


• UNIX Platforms



1. If the JBoss server is not running, open a new command window and run the following command:<JBOSS_HOME>\bin\run.bat

2. Copy the <ADEJB_HOME>\lib\AeConnector.rar to the <JBOSS_HOME>\server\default\deploy directory.

If you want to deploy the connector as a JAR (library) instead of a RAR, use the ejb-jar.xml file. EJB deployment descriptors should not refer to any Resource type.



3. Restart the server after you have deployed the connector.

UNIX Platforms


1. If the JBoss server is not running, open a new command window and run the following command:<JBOSS_HOME>/bin/run.sh

2. Copy the <ADEJB_HOME>/lib/AeConnector.rar to the <JBOSS_HOME>/server/default/deploy directory.


JBoss 4.0.0, 4.0.1, 4.0.2, 4.0.3, and 4.0.4 Application ServersTo deploy the connector for the JBoss 4.0.0 application server:

1. Copy AeConnector.rar from <ADEJB_HOME> to the temporary directory, for example, d:\connector.

a. Open a command prompt window and change to the directory d:\connector.

b. Run the command jar xvf AeConnector.rar

The directory will now have AeConnector-ds.xml, AeConnector.jar and META-INF\ra.xml files.

c. From the same command prompt, run the following command:Jar cvf Aeconnector.rar META-INF Aeconnector.jar

2. Copy AeConnector.rar and AeConnector-ds.xml from the temporary directory created (d:\connector) to <JBOSS_HOME>\server\default\deploy directory.


To deploy the connector for the JBoss 4.0.1, 4.0.2, 4.0.3, and 4.0.4 application servers:

1. If the JBoss server is not started, open a new command window and run the following command:<JBOSS_HOME>\bin\run.bat

JBoss 4.0.0 application server expects AeConnector-ds.xml file outside the rar file. The steps above make sure that the AeConnector.rar file is repackaged without the AeConnector-ds.xml file in it.



2. Copy <ADEJB_HOME>\lib\AeConnector.rar to the <JBOSS_HOME>\server\default\deploy directory.



Preparing the Test or Example Beans | 113

Preparing the Test or Example Beans

This section explains how you must prepare the test or example beans for the supported application servers.

Java 2 Platform, Enterprise Edition Application Server 1.3.1

The example beans that ship with the adapter have been tested with the Java 2 Platform, Enterprise Edition Application Server 1.3.1. Do not use the 1.2 version of the Java 2 Platform, Enterprise Edition application server.

For details on modifying the repository and configuration URLs for the connector, see Modifying the Repository URL, Configuration URL and TRA File Name of the Connector Configuration on page 60.

No additional changes are required for configuring the Example Beans.

BEA WebLogic Application Server 6.1 with SP1, SP2, or SP3For details on modifying the repository and configuration URLs for the connector, see Modifying the Repository URL, Configuration URL and TRA File Name of the Connector Configuration on page 60.





If the adapter is installed for multiple application support, the example beans do not contain the application server-specific deployment descriptors. Before deploying the beans on a particular application server, the application server-specific deployment descriptor needs to be added to the ExampleBeans.jar file. The deployment descriptors for the Example Beans, for the supported application servers are available in <ADEJB_HOME>/examples/beans/META-INF. The version number in these files need to be removed before the file is added to the ExampleBeans.jar.



BEA WebLogic Application Server 8.1, BEA WebLogic Application Server 8.1 with SP1, SP2, SP3, SP4, SP5, and SP6, and BEA WebLogic Application Server 9.0, 9.1, and 9.2



IBM WebSphere5.1 Application ServerIn the tibco.env.CUSTOM_CP_EXT1 property in the tra files for the examples, locate the <WebSphere_HOME>/.../<your node name> entry and replace <your node name> with the name of the node that you have created.



IBM WebSphere 6.0 and 6.0.2 Application ServersIn the tibco.env.CUSTOM_CP_EXT1 property in the .tra files for the examples, locate the <WebSphere_HOME>/.../<server name>/installedApps/<your node name> entry and replace <server name> and <your node name> with the name of the server and node that you have created.



Sun Java System Application Server Platform Edition 7For details on modifying the repository and configuration URLs for the connector, see Modifying the Repository URL, Configuration URL and TRA File Name of the Connector Configuration on page 60.



Preparing the Test or Example Beans | 115

Sun Java System Application Server Platform Edition 8.1For details on modifying the repository and configuration URLs for the connector, see Modifying the Repository URL, Configuration URL and TRA File Name of the Connector Configuration on page 60.


Oracle 9i Application ServerTo run the examples, do the following:

1. Modify some of the properties present in the following set of tra files that shipped with the adapter:

— <TIBCO_ADEJB_HOME>\examples\rpc\connector\outbound\bin\ rpcconnectorclient.tra

— <TIBCO_ADEJB_HOME>\examples\rpc\connector\outbound\bin\ rpcconnectorexcclient.tra

— <TIBCO_ADEJB_HOME>\examples\rpc\adapter\bin\ rpcadapterserver.tra

— <TIBCO_ADEJB_HOME>\examples\subscribe\adapter\bin\ subscribeserver.tra

— <TIBCO_ADEJB_HOME>\examples\publish\bin\publishclient.tra

2. In each tra file, add or update the following attributes:

— java.property.java.naming.provider.url=ormi://localhost/<ApplicationName>

— java.property.java.naming.security.principal=<admin_user_name>

— java.property.java.naming.security.credentials=<admin_password>

3. Enter EJBAdapter as the <ApplicationName>. This is the value that will be used when the beans are deployed.

4. Replace <admin_user_name> and <admin_password> with the user name and password that will be used during the installation of the application server.

Oracle 10g Application ServerTo run the examples, do the following:



1. Modify some of the properties present in the following set of tra files that shipped with the adapter:

— <TIBCO_ADEJB_HOME>\examples\rpc\connector\outbound\bin\ rpcconnectorclient.tra

— <TIBCO_ADEJB_HOME>\examples\rpc\connector\outbound\bin\ rpcconnectorexcclient.tra

— <TIBCO_ADEJB_HOME>\examples\rpc\adapter\bin\ rpcadapterserver.tra

— <TIBCO_ADEJB_HOME>\examples\subscribe\adapter\bin\ subscribeserver.tra

— <TIBCO_ADEJB_HOME>\examples\publish\bin\publishclient.tra

2. In each tra file, add or update the following attributes:

— java.property.java.naming.provider.url=ormi://localhost/<ApplicationName>

— java.property.java.naming.security.principal=<admin_user_name>

— java.property.java.naming.security.credentials=<admin_password>

3. Enter EJBAdapter as the <ApplicationName>. This is the value that will be used when the beans are deployed.

4. Replace <admin_user_name> and <admin_password> with the user name and password that will be used during the installation of the application server.

JBoss 3.2.3 Application ServerFor details on modifying the repository and configuration URLs for the connector, see Modifying the Repository URL, Configuration URL and TRA File Name of the Connector Configuration on page 60.


JBoss 4.0.0, 4.0.1, 4.0.2, 4.0.3, and 4.0.4 Application ServersFor details on modifying the repository and configuration URLs for the connector, see Modifying the Repository URL, Configuration URL and TRA File Name of the Connector Configuration on page 60.



Deploying the Test or Example Beans | 117

Deploying the Test or Example Beans

This section explains how to deploy the test or example beans for the supported application servers.

The examples packaged with the adapter do not run with application servers that do not support the Java Connector Architecture.

The adapter examples are packaged to run with application servers that support Java Connector Architecture (JCA). If you want to deploy the beans in non-resource adapter mode, modify the bean code accordingly.

Java 2 Platform, Enterprise Edition Application Server 1.3.1To deploy the beans:

1. Start the application server deployment tool and click File > New > Application.

2. Click File > Add to Application > EJB JAR.

3. Click Browse in the dialog box that is displayed and add the ExamplesBeans.jar file from the <ADEJB_HOME>\examples\lib directory.

4. Click Tools > Deploy Application.

5. Enter <ADEJB_HOME>\examples\lib\ExampleStubs.jar in the Client jar field. This file should be in the same directory as ExampleBeans.jar.

6. Click Next. The JNDI Names screen displays.

7. In the JNDI Names screen, you are prompted for JNDI names to use for the Connector and the bean. Use the names given in the Component/Reference Name column as the JNDI names.

For example, if the name in the Component column is RFC_CUSTOMER_GETBean, the JNDI is also RFC_CUSTOMER_GETBean.

The .bat file names are documented for the task of deploying the test beans. Use the corresponding shell script to deploy the test beans on UNIX.

If you are running the examples using a 4.x AeConnector.rar with a dat file created using TIBCO Designer 5.x, the configuration URL in the deployment descriptor must be changed from /tibco/private/adapter/Connector/RPC/SampleEJBAdapter to /tibco/private/adapter/Connector/RPC/EJBAdapter.



The JNDI for the Connector is the same as the name in the Reference Name column, that is, tibco/aeconnector. This needs to be entered twice, as there are two references to the connector.

8. Click Next. The deployment progress and completion of deployment is displayed in the browser.

BEA WebLogic Application Server 6.1 with SP1, SP2, or SP3To deploy the beans:

1. Click Start > Programs > BEA WebLogic E-Business Platform > WebLogic <verson_num>> Start Default Console to start the Administrator Console.

2. Select EJB under the Deployments section and then click Install a New EJB.

3. Choose the ExampleBeans.jar file from the adapter installation examples/lib subdirectory.

4. Click Upload. The jar will deploy.


To deploy the beans:

1. Start the application server by running the following commands in the <WebLogic Home>\server\bin directory:

— setWLSEnv.cmd

— startWLS.cmd

2. Click Start > Programs > BEA WebLogic Platform 7.0 > WebLogic Server 7.0 > Server Tour and Examples > Start Admin Console.

3. Enter your username and password.

4. Click EJB under the Domain Configuration section and then click Install a New EJB.


6. Click Browse to select the ExampleBeans.jar file from the <ADEJB_HOME>\examples\lib directory.

If the beans fail to deploy, it is likely that the startWebLogic.cmd or startWebLogic.sh (UNIX) file is missing one or more necessary jars in the classpath.



7. Click Upload to deploy the bean. The file will be listed in the browser.

8. Click Select for the bean.

9. Choose your application server from the Available Servers list and move it to the Target Servers list. The ExampleBeans.jar will be displayed in the Enter a name for this application field.

10. Click Configure and Deploy to deploy the beans.

BEA WebLogic Application Server 8.1 and BEA WebLogic Application Server 8.1 with SP1, SP2, SP3, SP4, SP5, and SP6

To deploy the beans:

1. To start the WebLogic server:

— Go to the <WebLogic_HOME>\server\bin directory on Microsoft Windows and run the following command:startWLS

— Go to <WebLogic_HOME>/server/bin directory on UNIX and run the following command:startWLS.sh

2. Start the Administrator Console. For example, on Microsoft Windows, click Start > Programs > BEA WebLogic Platform 8.1 > Examples > WebLogic Server Examples > Server Admin Console.

3. Type the username and password that will be used to start the WebLogic server.

4. Click EJB Modules under Deployments.

5. Click Deploy a new EJB Module.


7. Click Browse and select the ExampleBeans.jar file under the <ADEJB_HOME>\examples\lib directory.

8. Select the myserver folder and click Upload folder.

9. Select ExampleBeans.jar and click Target module.

10. Click Deploy. The Status of Last Action column will display a message informing you that the deployment was successful.

If the deployment fails, it is likely that the startWLS.cmd file is missing one or more necessary jars in the classpath.



BEA WebLogic Application Server 9.0, 9.1, and 9.2To deploy the beans:

1. To start the WebLogic server:

— Go to the <WebLogic_HOME>\server\bin directory on Microsoft Windows and run the following command:startWLS

— Go to <WebLogic_HOME>/server/bin directory on UNIX and run the following command:startWLS.sh

2. Start the Administrator Console. For example, on Microsoft Windows, click Start > Programs > BEA WebLogic Platform 9.0 > Examples > WebLogic Server Examples > Server Admin Console.

3. Type the username and password that will be used to start the WebLogic server.

4. Click EJB Modules under Deployments.

5. Click Deploy a new EJB Module.


7. Click Browse and select the ExampleBeans.jar file under the <ADEJB_HOME>\examples\lib directory.

8. Select the myserver folder and click Upload folder.

9. Select ExampleBeans.jar and click Target module.

Click Deploy. The Status of Last Action column will display a message informing you that the deployment was successful.

IBM WebSphere 5.1, 6.0, 6.0.2, and 6.1 Application ServersTo deploy the beans:



3. Click Browse to locate the ExampleBeans.jar file. This file is in the <ADEJB_HOME>/examples/lib directory.






7. Click Next and check the JNDI names of the connector reference in the Map resource references to resources page. Make sure that only two beans use the resource Reference Binding and that the JNDI name is tibco/aeconnector.



10. Select ExampleBeans.jar to deploy the beans.





15. Select ExampleBeans.jar.

16. Click Start. The status of ExampleBeans changes from red to green.

Sun Java System Application Server Platform Edition 7To deploy the beans:

1. Start the Sun Application Server Administrative Console.

2. Click EJB Modules under Applications for your application server instance. A page is displayed that lists all the installed applications.

3. Click Deploy. The Preparing for the Application Installation screen is displayed.

4. Click Browse to locate the ExampleBeans.jar file. This file is in the <ADEJB_HOME>\examples\lib directory.

5. Click OK to complete the deployment of the beans.

Sun Java System Application Server Platform Edition 8.1To deploy the beans:

1. Start the Sun Application Server Administrative Console.



2. Click EJB Modules under Applications for your application server instance. A page is displayed that lists all the installed applications.

3. Click Deploy.

4. Click Browse to locate the ExampleBeans.jar file. This file is in the <ADEJB_HOME>\examples\lib directory.

5. Click Next.

6. Under Advanced, select the option to generate the static RMI stubs in the client jar from.

7. Click OK to complete the deployment of the beans.

Oracle 9i Application ServerTo deploy the beans:

1. Create a subdirectory called EJBAdapter in the <ORACLE9IAS-ROOT>/j2ee/home/application-deployments/ directory.

2. Create a deployment descriptor (application.xml) to store the EJB Examples application and save the file into the <ORACLE9IAS-ROOT>/j2ee/home/application-deployments/EJBAdapter/META-INF directory.

The application.xml file is as follows:

<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EEApplication 1.3//EN""http://java.sun.com/dtd/application_1_3.dtd"><application>

<display-name>EJB Examples</display-name><description>TIBCO Adapter For EJB Examples</description>

<module><ejb>examples</ejb>

</module> </application>

3. Create another directory called examples in the <ORACLE9IAS-ROOT>/j2ee/home/application-deployments/EJBAdapter/ directory.

4. Extract the <ADEJB_HOME>/examples/lib/ExampleBeans.jar file to the <ORACLE9IAS-ROOT>/j2ee/home/application-deployments/EJBAdapter/examples directory.

EJBAdapter is the Application Name that you specified while configuring the application server.



5. Add the following line to the <ORACLE9IAS-ROOT>/j2ee/home/config/server.xml file:<application name="EJBAdapter" path="../application-deployments/EJBAdapter" />

6. Start the application server to deploy the beans.

Oracle 10g Application ServerTo deploy the beans:

1. Create a subdirectory called EJBAdapter in the <ORACLE10gAS-ROOT>/j2ee/home/application-deployments/ directory.

2. Create a deployment descriptor (application.xml) to store the EJB Examples application and save the file into the <ORACLE10gAS-ROOT>/j2ee/home/application-deployments/EJBAdapter/META-INF directory.

The application.xml file is as follows:

<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EEApplication 1.3//EN""http://java.sun.com/dtd/application_1_3.dtd"><application>

<display-name>EJB Examples</display-name><description>TIBCO Adapter For EJB Examples</description>

<module><ejb>examples</ejb>

</module> </application>

3. Create another directory called examples in the <ORACLE10gAS-ROOT>/j2ee/home/application-deployments/EJBAdapter/ directory.

4. Extract the <ADEJB_HOME>/examples/lib/ExampleBeans.jar file to the <ORACLE10gAS-ROOT>/j2ee/home/application-deployments/EJBAdapter/examples directory.

5. Add the following line to the <ORACLE10gAS-ROOT>/j2ee/home/config/server.xml file:<application name="EJBAdapter" path="../application-deployments/EJBAdapter" />

6. Start the application server to deploy the beans.

EJBAdapter is the Application Name that you specified while configuring the application server.



JBoss 3.2.3 Application ServerTo deploy the beans:

1. If the JBOSS server is not running, start the server in a new command-line console by running the <JBOSS_HOME>\bin\run.bat file.

2. Copy the <ADEJB_HOME>\examples\lib\ExampleBeans.jar to the <JBOSS_HOME>\server\default\deploy directory.

JBoss 4.0.0, 4.0.1, 4.0.2, 4.0.3, and 4.0.4 Application ServersTo deploy the beans:

1. If the JBOSS server is not running, start the server in a new command-line console by running the <JBOSS_HOME>\bin\run.bat file.

2. Copy the <ADEJB_HOME>\examples\lib\ExampleBeans.jar to the <JBOSS_HOME>\server\default\deploy directory.


| 125

Index

A

accessing examples 29

B

beansdeployment 117preparation 113

C

connectordeployment 99modifying repository, configuration URLs 60preparation 71

customer party business objectsync 49

customer support xi

D

deploying beans 117J2EE 117JBoss 3.2.3 124JBoss 4.0.0, 4.0.1, 4.0.2 124Oracle 10g 123Oracle 9i 122, 123Sun Java System Application Server Platform Edi-

tion 7 121Sun Java System Application Server Platform Edi-

tion 8.1 121WebLogic 6.1 118WebLogic 7.0 and BEA WebLogic Application

Server 7.0 with SP2, SP4, SP5 and SP6 118WebSphere 4.0.x Advanced Edition Single

Server 120WebSphere 5.0 120WebSphere 5.0 Advanced Edition Single Server 120WebSphere 5.0.2 120WebSphere 5.1 120

deploying connector 99JBoss 3.2.3 110Oracle 10g 109Oracle 9i 108Sun Java System Application Server Platform Edi-


tion 8.1 107WebLogic 6.1 99WebLogic 7.0 100WebSphere 5.0 103WebSphere 5.0.2 103WebSphere 5.1 103

deploying example beans 31, 38

E

employee business objectdelete 45get 45insert-update 44sync 44

TIBCO <Product> <DocTitle>

126 | Index

I

item master business objectdelete 56get 56insert-update 55sync 55

M

modifying URLsconfiguration 60JBoss 3.2.3 68Oracle 9i 65, 67repository 60Sun Java System Application Server Platform Edi-

tion 7 63, 64WebLogic 7.0 and BEA WebLogic Application

Server 7.0 with SP2, SP4, SP5 and SP6 60WebSphere 4.0.x Advanced Edition Single Server 63WebSphere 5.0 63WebSphere 5.0 Advanced Edition Single Server 63WebSphere 5.0.2 63WebSphere 5.1 63

P

preconfigured examplesaccessing 29customer party business object 49employee business object 43implementation matrix 28, 35item master business object 54prerequisites 29purchase order business object 46sales order business object 51software required 28

preparing beans 113J2EE 113JBoss 3.2.3 116JBoss 4.0.0, 4.0.1, 4.0.2 116Oracle 8.1 115Oracle 9i 115Sun Java System Application Server Platform Edi-

tion 7 114, 115Sun Java System Application Server Platform Edi-


Server 7.0 with SP2, SP4, SP5 and SP6 113WebSphere 4.0.x Advanced Edition Single

Server 114WebSphere 5.0 114WebSphere 5.0 Advanced Edition Single Server 114WebSphere 5.0.2 114WebSphere 5.1 114

preparing connector 715.0 Advanced Edition Single Server 85JBoss 3.2.3 94Oracle 10g 93Oracle 9i 92Sun Java System Application Server Platform Edi-



Server 7.0 with SP2, SP4, SP5 and SP6 74WebLogic 8.1 78WebLogic 8.1 with SP1 or SP2 78WebSphere 4.0.x Advanced Edition Single Server 85WebSphere 5.0 85WebSphere 5.0.2 85WebSphere 5.1 85

prerequisitespreconfigured examples 29starting repository server 59test programs 58

publication service test program 16


Index | 127

purchase order business objectdelete 48get 47insert-update 47

R

repository serverstarting 59

request-response invocation service test program 24request-response service test program 21

S

sales order business objectdelete 52get 52insert-update 52

starting repository server 59support, contacting xi

T

technical support xitest programs

prerequisites 58publication service 16request-response invocation service 24request-response service 21starting repository server 59

TIBCO BusinessWorks examplesdescription 36setting up environment 37starting using TIBCO Administrator 36starting using TIBCO Designer 36


tibco adapter™ for ejb · pdf filebea weblogic application server 7.0 and bea weblogic...

Documents