Wtc_admin Web Logic Tuxedo Connector Administration Guide

User Manual:

Open the PDF directly: View PDF PDF.
Page Count: 78

BETA
BEAWebLogic
Server®
WebLogic Tuxedo
Connector
Administration Guide
Version 9.0 BETA
Revised: December 15, 2004
BETA
BETA
Copyright
Copyright © 2004-2005 BEA Systems, Inc. All Rights Reserved.
Restricted Rights Legend
This software and documentation is subject to and made available only pursuant to the terms of the BEA Systems License
Agreement and may be used or copied only in accordance with the terms of that agreement. It is against the law to copy
the software except as specifically allowed in the agreement. This document may not, in whole or in part, be copied,
photocopied, reproduced, translated, or reduced to any electronic medium or machine readable form without prior
consent, in writing, from BEA Systems, Inc.
Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the BEA Systems License
Agreement and in subparagraph (c)(1) of the Commercial Computer Software-Restricted Rights Clause at FAR
52.227-19; subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS
252.227-7013, subparagraph (d) of the Commercial Computer Software--Licensing clause at NASA FAR supplement
16-52.227-86; or their equivalent.
Information in this document is subject to change without notice and does not represent a commitment on the part of BEA
Systems. THE SOFTWARE AND DOCUMENTATION ARE PROVIDED “AS IS” WITHOUT WARRANTY OF
ANY KIND INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. FURTHER, BEA Systems DOES NOT WARRANT, GUARANTEE, OR MAKE
ANY REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE SOFTWARE OR
WRITTEN MATERIAL IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE.
Trademarks or Service Marks
BEA, BEA WebLogic Server, Jolt, Tuxedo, and WebLogic are registered trademarks of BEA Systems, Inc. BEA Builder,
BEA Campaign Manager for WebLogic, BEA eLink, BEA Liquid Data for WebLogic, BEA Manager, BEA WebLogic
Commerce Server, BEA WebLogic Enterprise, BEA WebLogic Enterprise Platform, BEA WebLogic Enterprise
Security, BEA WebLogic Express, BEA WebLogic Integration, BEA WebLogic JRockit, BEA WebLogic
Personalization Server, BEA WebLogic Platform, BEA WebLogic Portal, BEA WebLogic Server Process Edition, BEA
WebLogic Workshop and How Business Becomes E-Business are trademarks of BEA Systems, Inc.
All other trademarks are the property of their respective companies.
BETA
BETA
WebLogic Tuxedo Connector Administration Guide v
Contents
About This Document
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii
e-docs Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii
How to Print the Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii
Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii
Contact Us! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Introduction to WebLogic Tuxedo Connector
WebLogic Tuxedo Connector Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Key Functionality and Administrative Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Known Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
How WebLogic Tuxedo Connector Differs from Jolt . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Platform Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Upgrading WebLogic Tuxedo Connector 6.x Applications . . . . . . . . . . . . . . . . . . . . . . . 1-4
Upgrading WebLogic Tuxedo Connector 7.0 Applications . . . . . . . . . . . . . . . . . . . . . . . 1-4
Configuring WebLogic Tuxedo Connector
Summary of Environment Changes and Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Tuxedo Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
WebLogic Server Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Administration and Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
BETA
vi WebLogic Tuxedo Connector Administration Guide
WebLogic Server Threads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Configuring WebLogic Tuxedo Connector for Your Applications . . . . . . . . . . . . . . . . . 2-2
WebLogic Tuxedo Connector MBean Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Configuring WebLogic Tuxedo Connector Using the Administration Console . . . . 2-5
Configuring WebLogic Tuxedo Connector Using the Command-Line Interface . . . 2-6
Set the WebLogic Server Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
How to Set WebLogic Tuxedo Connector Properties . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Set TraceLevel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Set PasswordKey . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Set encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
WebLogic Tuxedo Connector Configuration Guidelines. . . . . . . . . . . . . . . . . . . . . . 2-8
WebLogic Tuxedo Connector Administration
Configuring the Connections Between Access Points . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
How to Request a Connection at Boot Time (On Startup). . . . . . . . . . . . . . . . . . . . . 3-2
How to Configure RetryInterval. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
How to Configure MaxRetries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
How to Request Connections for Client Demands (On Demand) . . . . . . . . . . . . . . . 3-3
Accepting Incoming Connections (Incoming Only) . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
How to use LOCAL Connection Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
How ConnectionPolicy Affects Dynamic Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Configuring Failover and Failback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Prerequisite to Using Failover and Failback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
How to Configure Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
How to Configure Support Failback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Authentication of Remote Access Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Configuring a Password Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
BETA
WebLogic Tuxedo Connector Administration Guide vii
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Local Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Remote Passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
App Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
ACL Policy is LOCAL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
ACL Policy is GLobal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Credential Policy is Global . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
CredentialPolicy is Local . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
User Authenticaion for Tuxedo 6.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
How to Configure WebLogic Tuxedo Connector to Provide Security between Tuxedo and
WebLogic Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
TpUsrFile Plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Configuring the Local Tuxedo Access Point for the TpUsrFile Plug-in. . . . . . 3-11
Configure the Remote Tuxedo Access Point for the TpUsrFile Plug-in. . . . . . 3-11
LDAP Plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Implementing Single Point Security Administration . . . . . . . . . . . . . . . . . . . . 3-12
Configure the Local Tuxedo Access Point for the LDAP Plug-in . . . . . . . . . . 3-13
Configure the Remote Tuxedo Access Point for the LDAP Plug-in. . . . . . . . . 3-13
Custom Plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Configure the Local Tuxedo Access Point for the Custom Plug-in . . . . . . . . . 3-14
Configure the Remote Tuxedo Access Point for the Custom Plug-in. . . . . . . . 3-14
Anonymous Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Anonymous Users and CORBA Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Link-Level Encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Administration of CORBA Applications
How to Configure WebLogic Tuxedo Connector for CORBA Service Applications. . . . 4-1
BETA
viii WebLogic Tuxedo Connector Administration Guide
Example WTC Service and Tuxedo UBB Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
How to Administer and Configure WebLogic Tuxedo Connector for Inbound RMI-IIOP4-4
Configuring Your WTC Service for Inbound RMI-IIOP. . . . . . . . . . . . . . . . . . . . . . 4-4
Administering the Tuxedo Application Environment . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Guidelines About Using Your Server Name as an Object Reference. . . . . . . . . 4-6
How to Configure WebLogic Tuxedo Connector for Outbound RMI-IIOP. . . . . . . . . . . 4-7
Example Outbound RMI-IIOP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
How to Manage WebLogic Tuxedo Connector in a Clustered
Environment
WebLogic Tuxedo Connector Guidelines for Clustered Environments . . . . . . . . . . . . . . 5-1
How to Configure OutBound Requests to Tuxedo Domains . . . . . . . . . . . . . . . . . . . . . . 5-2
Example Clustered WebLogic Tuxedo Connector Configuration . . . . . . . . . . . . . . . 5-2
How to Configure Inbound Requests from Tuxedo Domains. . . . . . . . . . . . . . . . . . . . . . 5-4
Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Fail Over . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
How to Configure the Tuxedo Queuing Bridge
Overview of the Tuxedo Queuing Bridge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
How Tuxedo Queuing Bridge connects JMS with Tuxedo . . . . . . . . . . . . . . . . . . . . 6-2
How Tuxedo Queuing Bridge connects Tuxedo to JMS . . . . . . . . . . . . . . . . . . . . . . 6-3
Tuxedo Queuing Bridge Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Configuring the Tuxedo Queuing Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Starting the Tuxedo Queuing Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Error Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Tuxedo Queuing Bridge Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Example Connection Type Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Example JmsQ2TuxQ Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
BETA
WebLogic Tuxedo Connector Administration Guide ix
Example TuxQ2JmsQ Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Example JmsQ2TuxS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Priority Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Error Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
WLS Error Destination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Unsupported Message Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Tuxedo Error Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Connecting WebLogic Integration and Tuxedo Applications
Synchronous WebLogic Integration-to-Tuxedo Connectivity . . . . . . . . . . . . . . . . . . . . . 7-1
Defining Business Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Invoking an eLink Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Define Exception handlers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Synchronous Non-Blocking WebLogic Integration-to-Tuxedo Connectivity . . . . . . . . . 7-2
Asynchronous WebLogic Integration-to-Tuxedo Connectivity . . . . . . . . . . . . . . . . . . . . 7-3
Asynchronous Tuxedo /Q-to-WebLogic Integration Connectivity. . . . . . . . . . . . . . . . . . 7-3
Bi-directional Asynchronous Tuxedo-to-WebLogic Integration Connectivity. . . . . . . . . 7-3
Troubleshooting The WebLogic Tuxedo Connector
Monitoring the WebLogic Tuxedo Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Set Trace Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Enable Debug Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
What does this EJB Deployment Message Mean?. . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
How do I Start the Connector? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
How do I Start the Tuxedo Queuing Bridge?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
How do I Assign a WTC Service to a Server?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
BETA
xWebLogic Tuxedo Connector Administration Guide
How do I Resolve Connection Problems? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
How do I Migrate from Previous Releases? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
BETA
WebLogic Tuxedo Connector Administration Guide xi
About This Document
This document introduces the BEA WebLogic Tuxedo Connector™ application development
environment. This document provides information on how to configure and administer the
WebLogic Tuxedo Connector to interoperate between WebLogic Server and Tuxedo.
The document is organized as follows:
zChapter 1, “Introduction to WebLogic Tuxedo Connector,” is an overview of the WebLogic
Tuxedo Connector.
zChapter 2, “Configuring WebLogic Tuxedo Connector,” describes how to configure the
WebLogic Tuxedo Connector.
zChapter 3, “WebLogic Tuxedo Connector Administration,” provides configuration
information about the WebLogic Tuxedo Connector.
zChapter 4, “Administration of CORBA Applications,” provides information on how to
administer CORBA applications.
zChapter 5, “How to Manage WebLogic Tuxedo Connector in a Clustered Environment,”
provides information on how to use WebLogic Tuxedo Connector in a clustered
environment.
zChapter 6, “How to Configure the Tuxedo Queuing Bridge,” provides information on
tBridge functionality and configuration.
zChapter 7, “Using FML with WebLogic Tuxedo Connector,” discusses the Field
Manipulation Language (FML) and describes how the WebLogic Tuxedo Connector uses
FML.
BETA
About This Document
xii WebLogic Tuxedo Connector Administration Guide
zChapter 8, “Troubleshooting The WebLogic Tuxedo Connector,” provides WebLogic
Tuxedo Connector troubleshooting information.
Audience
This document is intended for system administrators and application developers who are
interested in building distributed Java applications that interoperate between WebLogic Server
and Tuxedo environments. It assumes a familiarity with the WebLogic Server, Tuxedo, and Java
programming.
e-docs Web Site
BEA product documentation is available on the BEA corporate Web site. From the BEA Home
page, click on Product Documentation or go directly to the WebLogic Server Product
Documentation page at http://e-docs.bea.com.
How to Print the Document
You can print a copy of this document from a Web browser, one main topic at a time, by using
the File→Print option on your Web browser.
A PDF version of this document is available on the WebLogic Server documentation Home page
on the e-docs Web site (and also on the documentation CD). You can open the PDF in Adobe
Acrobat Reader and print the entire document (or a portion of it) in book format. To access the
PDFs, open the WebLogic Server documentation Home page, click Download Documentation,
and select the document you want to print.
Adobe Acrobat Reader is available at no charge from the Adobe Web site at
http://www.adobe.com.
Related Information
The BEA corporate Web site provides all documentation for WebLogic Server and Tuxedo.
For more information about Java and Java CORBA applications, refer to the following sources:
zThe OMG Web Site at http://www.omg.org/
zThe Sun Microsystems, Inc. Java site at http://java.sun.com/
BETA
WebLogic Tuxedo Connector Administration Guide xiii
Contact Us!
Your feedback on BEA documentation is important to us. Send us e-mail at
docsupport@bea.com if you have questions or comments. Your comments will be reviewed
directly by the BEA professionals who create and update the documentation.
In your e-mail message, please indicate the software name and version you are using, as well as
the title and document date of your documentation. If you have any questions about this version
of BEA WebLogic Server, or if you have problems installing and running BEA WebLogic
Server, contact BEA Customer Support through BEA WebSupport at http://www.bea.com. You
can also contact Customer Support by using the contact information provided on the Customer
Support Card, which is included in the product package.
When contacting Customer Support, be prepared to provide the following information:
zYour name, e-mail address, phone number, and fax number
zYour company name and company address
zYour machine type and authorization codes
zThe name and version of the product you are using
zA description of the problem and the content of pertinent error messages
Documentation Conventions
The following documentation conventions are used throughout this document.
Convention Usage
Ctrl+Tab Keys you press simultaneously.
italics Emphasis and book titles.
BETA
About This Document
xiv WebLogic Tuxedo Connector Administration Guide
monospace
text
Code samples, commands and their options, Java classes, data types,
directories, and file names and their extensions. Monospace text also
indicates text that you enter from the keyboard.
Examples:
import java.util.Enumeration;
chmod u+w *
config/examples/applications
.java
config.xml
float
monospace
italic
text
Variables in code.
Example:
String CustomerName;
UPPERCASE
TEXT Device names, environment variables, and logical operators.
Examples:
LPT1
BEA_HOME
OR
{ } A set of choices in a syntax line.
[ ] Optional items in a syntax line. Example:
java utils.MulticastTest -n name -a address
[-p portnumber] [-t timeout] [-s send]
|Separates mutually exclusive choices in a syntax line. Example:
java weblogic.deploy [list|deploy|undeploy|update]
password {application} {source}
Convention Usage
BETA
WebLogic Tuxedo Connector Administration Guide xv
... Indicates one of the following in a command line:
• An argument can be repeated several times in the command line.
• The statement omits additional optional arguments.
• You can enter additional parameters, values, or other information
.
.
.
Indicates the omission of items from a code example or from a syntax line.
Convention Usage
BETA
About This Document
xvi WebLogic Tuxedo Connector Administration Guide
BETA
WebLogic Tuxedo Connector Administration Guide 1-1
CHAPTER 1
Introduction to WebLogic Tuxedo
Connector
The following sections summarize the concepts and functionality of WebLogic Tuxedo
Connector for this release of WebLogic Server:
zWebLogic Tuxedo Connector Overview
zKey Functionality and Administrative Features
zKnown Limitations
zHow WebLogic Tuxedo Connector Differs from Jolt
zPlatform Support
zLicensing
zUpgrading WebLogic Tuxedo Connector 6.x Applications
zUpgrading WebLogic Tuxedo Connector 7.0 Applications
WebLogic Tuxedo Connector Overview
The WebLogic Tuxedo Connector provides interoperability between WebLogic Server
applications and Tuxedo services. The connector allows WebLogic Server clients to invoke
Tuxedo services and Tuxedo clients to invoke WebLogic Server Enterprise Java Beans (EJBs) in
response to a service request.
BETA
1-2 WebLogic Tuxedo Connector Administration Guide
Key Functionality and Administrative Features
The WebLogic Tuxedo Connector enables you to develop and support applications interoperating
WebLogic Server and Tuxedo by using a Java Application-to-Transaction Monitor Interface
(JATMI) similar to the Tuxedo ATMI. The WebLogic Tuxedo Connector tBridge functionality
provides Tuxedo /Q and JMS advanced messaging services.
The WebLogic Tuxedo Connector provides the following bi-directional interoperability:
zAbility to call WebLogic Server applications from Tuxedo applications and vice versa.
zAbility to integrate WebLogic Server applications into existing Tuxedo environments.
zTransaction support.
zAbility to provide interoperability between CORBA Java and CORBA C++ server
applications.
zAbility to provide interoperability between Remote Method Invocation (RMI) over Internet
Inter-ORB Protocol (IIOP) applications and Tuxedo CORBA remote objects.
zAbility to use WebLogic Integration to manage workflow across Tuxedo ATMI services.
zAbility to define multiple connections between WebLogic Server and Tuxedo.
The WebLogic Tuxedo Connector includes the following key administration features:
zSimple implementation. The WebLogic Tuxedo Connector does not require modification of
existing Tuxedo application code.
– Existing Tuxedo clients call WebLogic Server EJBs through the WebLogic Tuxedo
Connector.
– New or modified WebLogic Server clients call Tuxedo services through WebLogic
Tuxedo Connector.
zBi-directional security propagation, including domain and ACL security.
zDomain-level failover and fallback.
zAdvanced messaging services provided by Tuxedo /Q and JMS.
zInteroperability with mainframes and other legacy applications using eLink.
Known Limitations
WebLogic Tuxedo Connector has the following limitations:
BETA
How WebLogic Tuxedo Connector Differs from Jolt
WebLogic Tuxedo Connector Administration Guide 1-3
zDoes not support dynamic configuration changes to the WebLogic Tuxedo Connector
gateway.
Note: When making changes to your WebLogic Tuxedo Connector service configuration,
you will need to remove the service from the server and target the service to the server
for these changes to take effect.
zDoes not support inbound TGIOP in clustered environments.
zDoes not support Tuxedo 8.1 multibyte string data typed buffer named MBSTRING for
transport of multibyte character user data.
zDoes not support Tuxedo 8.1 Domains keepalive functionality.
zWebLogic Tuxedo Connector does not support Tuxedo 6.5 running on VMS and OS/390
platforms.
How WebLogic Tuxedo Connector Differs from Jolt
The WebLogic Tuxedo Connector is not a replacement for Jolt. WebLogic Tuxedo Connector
differs from Jolt in the following ways:
zWebLogic Tuxedo Connector offers a similar but different API than Jolt.
zJolt enables the development of generic Java clients and other Web server applications that
the WebLogic Tuxedo Connector does not.
zJolt does not provide a mechanism for an integrated WebLogic Server-Tuxedo transaction.
Users should use Jolt as a solution instead of the WebLogic Tuxedo Connector when a generic
Java client or other Web server application is required and WebLogic Server is not part of the
solution.
Platform Support
See our Platforms Support page at
http://e-docs.bea.com/wls/certifications/certifications/overview.html for the most accurate and
current information regarding platform support.
Licensing
Note: For more information on WebLogic Server licensing information, see Installing a
WebLogic Server License at
http://e-docs.bea.com/wls/docs90/../../platform/docs90/install/prepare.html#1129187.
BETA
1-4 WebLogic Tuxedo Connector Administration Guide
This section provides licensing information for the WebLogic Tuxedo Connector:
zThere is no license requirement for using the connector without encryption.
zAn appropriate Tuxedo LLE license and an appropriate WebLogic Server SSL license is
required to use encryption.
Upgrading WebLogic Tuxedo Connector 6.x Applications
You must make some changes in your WebLogic Tuxedo Connector 6.x applications (including
WebLogic Tuxedo Connector 1.0) to use them with WebLogic Server 9.0. For detailed
information on the administration and programming changes required to upgrade to WebLogic
Tuxedo Connector in WebLogic Server 9.0, see Upgrade Planning Guide at
http://e-docs.bea.com/wls/docs90/../../platform/docs90/upgrade/index.html.
Upgrading WebLogic Tuxedo Connector 7.0 Applications
You may want to make some changes in your WebLogic Tuxedo Connector 7.0 RMI-IIOP
applications to use them with WebLogic Server 9.0. For detailed information, see Upgrade
Planning Guide at http://e-docs.bea.com/wls/docs90/../../platform/docs90/upgrade/index.html.
BETA
WebLogic Tuxedo Connector Administration Guide 2-1
CHAPTER 2
Configuring WebLogic Tuxedo
Connector
The following sections describe how to configure the WebLogic Tuxedo Connector.
zSummary of Environment Changes and Considerations
zConfiguring WebLogic Tuxedo Connector for Your Applications
Summary of Environment Changes and Considerations
This section provides an overview of the changes you must make to the Tuxedo and WebLogic
Server environments before you can start using the WebLogic Tuxedo Connector.
Tuxedo Changes
Note: For more information on Tuxedo domains, see the BEA TUXEDO Domains Guide.
Tuxedo users need to make the following environment changes:
zIf an existing Tuxedo application is already using Tuxedo /T DOMAINS, then a new
domain must be added to the domains configuration file for each connection to a
WebLogic Tuxedo Connector instantiation.
zIf the existing Tuxedo application does not use domains, then the domain servers must be
added to the TUXCONFIG of the application. A new DMCONFIG must be created with a
Tuxedo /T Domain entry corresponding to the WebLogic Tuxedo Connector instantiation.
zWebLogic Tuxedo Connector requires that the Tuxedo domain always have encoding
turned on. MTYPE should always be unset or set to NULL in the DMCONFIG file.
BETA
2-2 WebLogic Tuxedo Connector Administration Guide
WebLogic Server Changes
The following sections describe WebLogic Server changes required to use the WebLogic Tuxedo
Connector:
zAdministration and Programming
zWebLogic Server Threads
Administration and Programming
WebLogic Server users need to make the following environment changes:
zCreate Java clients or servers. For more information on creating WebLogic Tuxedo
Connector clients or servers, see the WebLogic Tuxedo Connector Programmer’s Guide.
zConfigure the WebLogic Tuxedo Connector using the WebLogic Server console or
command-line interface. For more information on how to configure the WebLogic Tuxedo
Connector, see “Configuring WebLogic Tuxedo Connector for Your Applications” on
page 2-2.
zIf the WebLogic Tuxedo Connector ACL Policy is set to Local, access to local services
does not depend on the CredentialPolicy. The Tuxedo remote domain DOMAINID must
be authenticated as a local WebLogic Server user. For more information, see “User
Authentication” on page 3-9.
WebLogic Server Threads
Note: For more information on WebLogic Server performance and tuning, see BEA WebLogic
Server Performance and Tuning at
http://e-docs.bea.com/wls/docs90/perform/index.html.
The number of client threads available when dispatching services from the gateway may limit the
number of concurrent services running. For this release of WebLogic Tuxedo Connector, there is
no WebLogic Tuxedo Connector attribute to increase the number of available threads. Use a
reasonable thread model when invoking service EJBs.You may need to increase the number of
WebLogic Server threads available to a larger value.
Configuring WebLogic Tuxedo Connector for Your Applications
Note: Deciding when to target a WTC Service is very important. Once a WTC Service is
targeted, the configuration deployed to the selected server is static. Although you can
continue to make changes in your WTC Service configuration, any changes made after
BETA
Configuring WebLogic Tuxedo Connector for Your Applications
WebLogic Tuxedo Connector Administration Guide 2-3
the configuration is deployed will not be reflected in the selected server. You will need
to remove the service from the server and target the service to the server for these changes
to take effect.
This section provides information on how to configure the WebLogic Tuxedo Connector to allow
WebLogic Server applications and Tuxedo applications to interoperate.
zWebLogic Tuxedo Connector MBean Classes
zConfiguring WebLogic Tuxedo Connector Using the Administration Console
zConfiguring WebLogic Tuxedo Connector Using the Command-Line Interface
zSet the WebLogic Server Environment
zHow to Set WebLogic Tuxedo Connector Properties
zWebLogic Tuxedo Connector Configuration Guidelines
WebLogic Tuxedo Connector MBean Classes
Note: For more information on the WebLogic Server management and the config.xml file,
see WebLogic Server Configuration Reference at
http://e-docs.bea.com/wls/docs90/wlsmbeanref/index.html.
The WebLogic Tuxedo Connector uses MBeans to describe connectivity information and
security protocols to process service requests between WebLogic Server and Tuxedo. These
configuration parameters are analogous to the interoperability attributes required for
communication between Tuxedo domains. The configuration parameters are stored in the
WebLogic Server config.xml file. The following table lists the MBean types used to
configure WebLogic Tuxedo Connector:
BETA
2-4 WebLogic Tuxedo Connector Administration Guide
MBean Type Description
WTCServer Parent MBean containing the interoperability attributes
required for a connection between WebLogic Server and
Tuxedo. Defines your WTC Service when configured using
the Administration Console.
WTCLocalTuxDom Provides configuration information to connect available
remote Tuxedo domains to a WTC Service. You must
configure at least one local Tuxedo access point. Defines
your Local Tuxedo Access Points when configured using the
Administration Console.
WTCRemoteTuxDom Provides configuration information to connect a WTC
Service to available remote Tuxedo domains. You may
configure multiple remote domains. Defines your Remote
Tuxedo Access Points when configured using the
Administration Console.
WTCExport Provides information on services exported by a local Tuxedo
access point. Defines your Exported Services when
configured using the Administration Console.
WTCImport Provides information on services imported and available on
remote domains. Defines your Imported Services when
configured using the Administration Console.
WTCResources Specifies global field table classes, view table classes, and
application passwords for domains. Defines your Resources
when configured using the Administration Console.
WTCPassword Specifies the configuration information for inter-domain
authentication. Defines your Passwords when configured
using the Administration Console.
Support for MBSTRING is provided using
RemoteMBEncoding and MBEncodingMapFile
attributes
BETA
Configuring WebLogic Tuxedo Connector for Your Applications
WebLogic Tuxedo Connector Administration Guide 2-5
Configuring WebLogic Tuxedo Connector Using the
Administration Console
The Administration Console allows you to configure, manage, and monitor WebLogic Tuxedo
Connector connectivity. To display the tabs that you use to perform these tasks, complete the
following procedure:
1. Start the Administration Console.
2. Locate the Interoperability node in the left pane, then expand the WTC Service.
3. Create or modify the WTC Server you want to configure.
4. Follow the instructions in the Online Help. For links to the Online Help, see Table 2-1.
The following table shows the connectivity tasks, listed in typical order in which you perform
them. You may change the order; just remember you must configure an object before associating
or assigning it.
WTCtBridgeGlobal Specifies global configuration information for the transfer of
messages between WebLogic Server and Tuxedo. Defines
your Tuxedo Queuing Bridge when configured using the
Administration Console.
WTCtBridgeRedirect Specifies the source, target, direction, and transport of
messages between WebLogic Server and Tuxedo. Defines
your Tuxedo Queuing Bridge Redirects when configured
using the Administration Console.
Table 2-1 WebLogic Tuxedo Connector Configuration Tasks
Task # Task Description
1Creating a WTC
Service On the General tab in the right pane, you set the attributes
for Name and Deployment Order.
2Creating a Local
Tuxedo Access Point Set the attributes that describe your local Tuxedo access
point in the General, Connections, and Security tabs. You
must configure at least one local Tuxedo access point.
MBean Type Description
BETA
2-6 WebLogic Tuxedo Connector Administration Guide
Configuring WebLogic Tuxedo Connector Using the
Command-Line Interface
The command-line interface provides a way to create and manage WebLogic Tuxedo Connector
connections. For information on how to use the command-line interface, see Commands for
Managing WebLogic Server MBeans at
http://e-docs.bea.com/wls/docs90/admin_ref/cli.html#Commands_Managing_WebLogic_Serve
r_MBeans.
Set the WebLogic Server Environment
You need to set the environment of your WebLogic Server application by running the
setExamplesEnv script located at WL_HOME\samples\domains\examples.
3Creating a Remote
Tuxedo Access Point Set the attributes that describe your remote Tuxedo
domains in the Local APs tab.
4Creating Exported
Services Set the attributes that describe your exported WebLogic
Server services in the Exported tab.
5Creating Imported
Services Set the attributes that describe your imported Tuxedo
services in the Imported tab.
6Creating a Password
Configuration Set the attributes that describe your passwords in the
Password tab.
7Creating a Resource Set the attributes that describe your WebLogic Tuxedo
Connector resources in the Resources tab.
8Creating a Tuxedo
Queuing Bridge
Connection
Set the global configuration information for the transfer of
messages between WebLogic Server and Tuxedo.
9Creating a tBridge
Redirection Sets the attributes used to specify the source, target,
direction, and transport of a message between WebLogic
Server and Tuxedo
10 Assign a WTC
Service to a Server Select a target server for your WTC Service.
Table 2-1 WebLogic Tuxedo Connector Configuration Tasks
Task # Task Description
BETA
Configuring WebLogic Tuxedo Connector for Your Applications
WebLogic Tuxedo Connector Administration Guide 2-7
- NT/2000 users: run setExamplesEnv.cmd
- UNIX users: run setExamplesEnv.sh
If you are setting the environment for the first time, you will need to review the settings in the
script. If necessary, use the following steps to modify the settings for your application
environment:
1. From the command line, change directories to the location of the WebLogic Server
application. Copy the setExamplesEnv script located at
WL_HOME\samples\domains\examples to your application directory.
2. Edit the setExamplesEnv script with a text editor, such as vi.
- NT/2000 users: edit setExamplesEnv.cmd
- UNIX users: edit setExamplesEnv.sh
3. Save the file.
How to Set WebLogic Tuxedo Connector Properties
TraceLevel, PasswordKey, and encoding are WebLogic Server Properties. If you need to set
these properties, update the JAVA_OPTIONS variable in your server start script. Example:
JAVA_OPTIONS=-Dweblogic.wtc.TraceLevel=100000
Set TraceLevel
Note: For more information on how to record log information, see “Monitoring the WebLogic
Tuxedo Connector” on page 8-1.
Use TraceLevel to specify the level of message tracing WebLogic Tuxedo Connector will send
to your log files:
JAVA_OPTIONS= -Dweblogic.wtc.TraceLevel=tracelevel
where tracelevel is a number between 10,000 and 100,000 that specifies the level of
WebLogic Tuxedo Connector tracing.
Set PasswordKey
Note: For more information on PasswordKey, see “Configuring a Password Configuration” on
page 3-7.
Use PasswordKey to specify the key used by the weblogic.wtc.gwt.genpassword utility to
encrypt passwords:
BETA
2-8 WebLogic Tuxedo Connector Administration Guide
JAVA_OPTIONS=-Dweblogic.wtc.PasswordKey=mykey
where mykey is the key value.
Set encoding
To transfer non-ascii (multibyte) strings between WebLogic Server and Tuxedo applications, you
must configure WebLogic Tuxedo Connector to provide characer set translation. WebLogic
Tuxedo Connector uses a WebLogic Server property to match the encoding used by all the
Tuxedo remote domains specified in a WebLogic Tuxedo Connector service. If you require more
than one coding set running simultaneously, you will require WebLogic Tuxedo Connector
services running in separate WebLogic Server instances.
To enable character set translation, update the JAVA_OPTIONS variable in your server start
script. Example:
JAVA_OPTIONS=-Dweblogic.wtc.encoding=codesetname
where codesetname is the name of a supported codeset used by a remote Tuxedo domain.
See Supported Encodings at http://java.sun.com/j2se/1.3/docs/guide/intl/encoding.doc.html
for list of supported supported base and extended coding sets.
You may not be able to select the exact encoding name to match the encoding used by the remote
domain. In this situation, you should select an encoding name that is equivalent to the remote
domain.
Example:
zThe Supported Encoding list includes EUC_JP
zThe remote domain is supported by a Solaris operating system using eucJP
Although the names don’t match exactly, EUC_JP and eucJP are equivalent encoding sets and
provide the correct string translation between WebLogic Server and your remote domain. You
should set the encoding property to EUC_JP:
JAVA_OPTIONS=-Dweblogic.wtc.encoding=EUC_JP
WebLogic Tuxedo Connector Configuration Guidelines
Use the following guidelines when configuring WebLogic Tuxedo Connector:
zYou must have at least one local Tuxedo access point in your configuration.
zYou may have more than one WTC Service in your configuration.
BETA
Configuring WebLogic Tuxedo Connector for Your Applications
WebLogic Tuxedo Connector Administration Guide 2-9
zYou can not target 2 or more WTC Services to the same server. A server can only be a
target for one WTC Service.
zAny configuration changes implemented in a WTC Service after a target server is selected
will not be updated in the target server instance. You must remove the WTC Service from
the server and then add the updated WTC Service add to the target server. For more
information on selecting a target server, see Assign a WTC Service to a Server.
BETA
2-10 WebLogic Tuxedo Connector Administration Guide
BETA
WebLogic Tuxedo Connector Administration Guide 3-1
CHAPTER 3
WebLogic Tuxedo Connector
Administration
Note: For more information on the WebLogic Server management, including the WebLogic
Tuxedo Connector, see the WebLogic Server Configuration Reference at
http://e-docs.bea.com/wls/docs90/wlsmbeanref/index.html.
The following sections describe how to establish connectivity and provide security between
WebLogic Server applications and Tuxedo environments. WebLogic Tuxedo Connector uses
attributes that are analogous to the interoperability attributes required for the communication
between Tuxedo access points.
The following sections provide WebLogic Tuxedo Connector configuration information:
zConfiguring the Connections Between Access Points
zHow ConnectionPolicy Affects Dynamic Status
zConfiguring Failover and Failback
zAuthentication of Remote Access Points
zUser Authentication
zHow to Configure WebLogic Tuxedo Connector to Provide Security between Tuxedo and
WebLogic Server
zLink-Level Encryption
BETA
3-2 WebLogic Tuxedo Connector Administration Guide
Configuring the Connections Between Access Points
Note: For more information on Dynamic Status, see “How ConnectionPolicy Affects Dynamic
Status” on page 3-4.
Several options can specify the conditions under which an access point tries to establish a
connection with a remote access point. Specify these conditions using the ConnectionPolicy
attribute in the Connections tab of the Local Tuxedo Access Points and Remote Tuxedo Access
Points configurations of your WTC Service. You can select any of the following connection
policies:
zHow to Request a Connection at Boot Time (On Startup)
zHow to Request Connections for Client Demands (On Demand)
zAccepting Incoming Connections (Incoming Only)
zHow to use LOCAL Connection Policy
For connection policies of On Startup and Incoming Only, Dynamic Status is invoked.
Dynamic Status checks and reports on the status of imported services associated with each remote
access point.
How to Request a Connection at Boot Time (On Startup)
A policy of On Startup means that an access point attempts to establish a connection with its
remote access points at gateway server initialization time. The connection policy retries failed
connections at regular intervals determined by the RetryInterval parameter and the
MaxRetries parameter. To request a connection at boot time, set the ConnectionPolicy
attribute in the Connections tab of your local Tuxedo access point to On Startup.
How to Configure RetryInterval
You can control the frequency of automatic connection attempts by specifying the interval (in
seconds) during which the access point should wait before trying to establish a connection again.
The minimum value is 0; the default value is 60, and maximum value is 2147483647.
How to Configure MaxRetries
Note: Use only when ConnectionPolicy is set to On Startup. For other connection policies,
retry processing is disabled.
BETA
Configuring the Connections Between Access Points
WebLogic Tuxedo Connector Administration Guide 3-3
You indicate the number of times an access point tries to establish connections to remote access
points before quitting by assigning a value to the MaxRetries parameter: the minimum value is
0; the default and maximum value is 2147483647.
zIf you set MaxRetries to 0, automatic connection retry processing is turned off. The server
does not attempt to connect to the remote access point automatically.
zIf you set MaxRetries to a number, the access point tries to establish a connection the
specified number of times before quitting.
zIf you set MaxRetries to 2147483647, retry processing is repeated indefinitely or until a
connection is established.
How to Request Connections for Client Demands (On Demand)
Note: If the ConnectionPolicy is not specified, the WebLogic Tuxedo Connector uses a
ConnectionPolicy of 0n Demand.
A connection policy of 0n Demand means that a connection is attempted only when requested by
either a client request to a remote service or an administrative connect command.
Accepting Incoming Connections (Incoming Only)
A connection policy of Incoming Only means that an access point does not establish a
connection to remote access points upon starting. The access point is available for incoming
Table 3-1 Example Settings of MaxRetries and RetryInterval Parameters
If you set ... Then ...
ConnectionPolicy: On Startup
RetryInterval: 30
MaxRetries: 3
The access point makes 3 attempts to
establish a connection, at 30 seconds
intervals, before quitting.
ConnectionPolicy: On Startup
MaxRetries: 0
The access point attempts to establish a
connection at initialization time but
does not retry if the first attempt fails.
ConnectionPolicy: On Startup
RetryInterval: 30
The access point attempts to establish a
connection every 30 seconds until a
connection is established.
BETA
3-4 WebLogic Tuxedo Connector Administration Guide
connections from remote access points and remote services are advertised when the access point
receives an incoming connection.
How to use LOCAL Connection Policy
Note: A ConnectionPolicy of LOCAL is not valid for local access points.
A connection policy of LOCAL indicates that a remote domain connection policy is explicitly
defaulted to the local domain ConnectionPolicy attribute value. If the remote access point
ConnectionPolicy is not defined, the system uses the setting specified by the associated local
access point.
How ConnectionPolicy Affects Dynamic Status
Dynamic Status determines the availability of remote services. The connection policy used
determines whether the Dynamic Status feature is available for a service. The following table
describes how ConnectionPolicy affects Dynamic Status capability.
Configuring Failover and Failback
Note: In the Tuxedo T/ Domain, there is a limit of two (2) backup remote access points. The
WebLogic Tuxedo Connector has no limit to the number of backup access points allowed
to be configured for a service.
WebLogic Tuxedo Connector provides a failover mechanism that transfers requests to alternate
remote access points when a failure is detected with a primary remote access point. It also
provides failback to the primary remote access point when that access point is restored. This level
On Startup Dynamic Status is on. Services imported from a remote
access point are advertised while a connection to that remote
access point exists.
0n Demand Dynamic Status is off. Services imported from remote access
points are always advertised.
Incoming Only Dynamic Status is on. Remote services are initially
suspended. The access point is available for incoming
connections from remote access points. Remote services are
advertised when the access point receives an incoming
connection.
BETA
Configuring Failover and Failback
WebLogic Tuxedo Connector Administration Guide 3-5
of failover/failback depends on Dynamic Status. The access point must be configured with a
connection policy of On Startup or Incoming Only to enable failover/failback.
Prerequisite to Using Failover and Failback
To use failback, you must specify On Startup or Incoming Only as the value of the
Connection Policy parameter.
A connection policy of 0n Demand is unsuitable for failback as it operates on the assumption that
the remote access point is always available. If you do not specify On Startup or Incoming Only
as your connection policy, your servers cannot fail over to the alternate remote access points that
you have specified with the Tuxedo RDOM parameter.
Note: A remote access point is available if a network connection to it exists; a remote access
point is unavailable if a network connection to it does not exist.
How to Configure Failover
To support failover, you must specify the remote access points responsible for executing a
particular service. You must specify the following in your WTC Service:
zCreate Remote Tuxedo Access Points configurations for each remote access point.
zCreate Imported Services configurations that specify the service provided by each remote
access point.
Suppose a service, TOUPPER, is available from two remote access points: TDOM1 and TDOM3.
Your WTC Service would include two Remote Tuxedo Access Point configuratons and two
Imported Services configurations in your WTC Service. The WTC Service defined in the
config.xml file would contain the following:
<WTCServer Name="WTCsimpapp"
<WTCExport EJBName="tuxedo.services.TOLOWERHome"
LocalAccessPoint="TDOM2" Name="myExportedResources"
ResourceName="TOLOWER"/>
<WTCImport LocalAccessPoint="TDOM2" Name="myImportedResources"
RemoteAccessPointList="TDOM1" ResourceName="TOUPPER"/>
<WTCImport LocalAccessPoint="TDOM2" Name="2ndImportedResources"
RemoteAccessPointList="TDOM3" ResourceName="TOUPPER"/>
<WTCLocalTuxDom AccessPoint="TDOM2" AccessPointId="TDOM2"
ConnectionPolicy="ON_DEMAND" Interoperate="no"
NWAddr="//123.123.123.123:5678" Name="myLoclTuxDom" Security="NONE"/>
<WTCRemoteTuxDom AccessPoint="TDOM1" AccessPointId="TDOM1"
LocalAccessPoint="TDOM2" NWAddr="//123.123.123.123:1234"
Name="myRTuxDom"/>
BETA
3-6 WebLogic Tuxedo Connector Administration Guide
<WTCRemoteTuxDom AccessPoint="TDOM3" AccessPointId="TDOM3"
LocalAccessPoint="TDOM2" NWAddr="//234.234.234.234:5555"
Name="2ndRemoteTuxDom"/>
</WTCServer>
How to Configure Support Failback
Failback occurs when a network connection to the primary remote access point is reestablished
for any of the following reasons:
zAutomatic retries (On Startup only)
zIncoming connections
Authentication of Remote Access Points
Note: Tuxedo 6.5 users should set the Interoperate parameter to Yes.
Domain gateways can be made to authenticate incoming connections requested by remote access
points and outgoing connections requested by local access points. Application administrators can
define when security should be enforced for incoming connections from remote access points.
You can specify the level of security used by a particular local access point by setting the
Security attribute in the Security tab of the local Tuxedo access point configuration of your
WTC Service. There are three levels of password security:
zNONE—incoming connections from remote access points are not authenticated.
zApplication Password— incoming connections from remote access points are
authenticated using the application password defined in the Password configuration of your
WTC Service. You use the weblogic.wtc.gwt.genpasswd utility to create encrypted
application passwords.
zDomain Password—this feature enforces security between two or more access points.
Connections between the local and remote access points are authenticated using password
pairs defined in the Password configuration of your WTC Service. You use the
weblogic.wtc.gwt.genpasswd utility to create encrypted local and remote passwords.
The Security attribute in the Security tab of the local Tuxedo access point of your WTC Service
must match the SECURITY attribute of the *DM_LOCAL_DOMAINS section of the Tuxedo
domain configuration file.
zIf authentication is required, it is done every time a connection is established between the
local access point and the remote access point.
BETA
Authentication of Remote Access Points
WebLogic Tuxedo Connector Administration Guide 3-7
zIf the security type of the local Tuxedo access point in your WTC Service does not match
the security type of the *DM_LOCAL_DOMAINS or if the passwords do not match, the
connection fails.
Configuring a Password Configuration
Note: For more information on how to assign a PasswordKey, see “How to Set WebLogic
Tuxedo Connector Properties” on page 2-7.
Use weblogic.wtc.gwt.genpasswd to generate encrypted passwords for Local Password,
Remote Password, and App Password attributes. The utility uses a key to encrypt a password that
is copied into the Password or Resources configuration of your WTC Service.
zThe Password configuration of your WTC Service does not store clear text passwords.
zThe key value is a WebLogic Server property.
–PasswordKey is the attribute used to assign the key.
-Dweblogic.wtc.PasswordKey=mykey
where: mykey is the key value
– The PasswordKey attribute can only be assigned one key value. This key value is used
for all Weblogic Tuxedo Connector passwords generated (local, remote, and application
passwords) for use with a specific WebLogic Server.
Usage
Call the utility without any arguments to display the command line options.
Example:
$ java weblogic.wtc.gwt.genpasswd
Usage: genpasswd Key <LocalPassword|RemotePassword|AppPassword>
<local|remote|application>
Call the utility with a key value, password to encrypt, and the type of password.
Example:
$ java weblogic.wtc.gwt.genpasswd Key1 LocalPassword1 local
The utility will respond with the encoded password and password IV. Cut and paste the results
into the appropriate fields in Password configuation of your WTC Service.
Local Password : my_password
BETA
3-8 WebLogic Tuxedo Connector Administration Guide
Local Password IV: my_passwordIV
where
zCut and paste the string of characters represented by my_password into the Password field.
zCut and paste the string of characters represented by my_passwordIV into the
PasswordIV field.
Examples
This section provides examples of each of the password element types.
Local Passwords
The following example uses key1 to encrypt “LocalPassword1” as the password of the local
access point.
$ java weblogic.wtc.gwt.genpasswd key1 LocalPassword1 local
Local Password : FMTCg5Vi1mTGFds1U4GKIQQj7s2uTlg/ldBfy6Kb+yY=
Local Password IV : NAGikshMiTE=
Your Password attributes are:
Local Password: FMTCg5Vi1mTGFds1U4GKIQQj7s2uTlg/ldBfy6Kb+yY=
Local Password IV: NAGikshMiTE=
Remote Passwords
The following example uses mykey to encrypt “RemotePassword1” as the password for the
remote access point.
$ java weblogic.wtc.gwt.genpasswd mykey RemotePassword1 remote
Remote Password : A/DgdJYOJunFUFJa62YmPgsHan8pC02zPT0T7EigaVg=
Remote Password IV : ohYHxzhYHP0=
Your Password attributes are:
Remote Password: A/DgdJYOJunFUFJa62YmPgsHan8pC02zPT0T7EigaVg=
Remote Password IV: ohYHxzhYHP0=
App Passwords
The following example uses mykey to encrypt “test123” as the application password.
BETA
User Authentication
WebLogic Tuxedo Connector Administration Guide 3-9
$ java weblogic.wtc.gwt.genpasswd mykey test123 application
App Password : uou2MALQEZgNqt8abNKiC9ADN5gHDLviqO+Xt/VjakE=
App Password IV : eQuKjOaPfCw=
Your Resources attributes are:
Application Password: uou2MALQEZgNqt8abNKiC9ADN5gHDLviqO+Xt/VjakE=
Application Password IV: eQuKjOaPfCw=
User Authentication
Access Control Lists (ACLs) limit the access to local services within a local access point by
restricting the remote Tuxedo access point that can execute these services. Inbound policy from
a remote Tuxedo access point is specified using the AclPolicy attribute. Outbound policy
towards a remote Tuxedo domain is specified using the CredentialPolicy attribute. This
allows WebLogic Server and Tuxedo applications to share the same set of users and the users are
able to propagate their credentials from one system to the other.
The valid values for AclPolicy and CredentialPolicy are:
zLOCAL
zGLOBAL
ACL Policy is LOCAL
If the WebLogic Tuxedo Connector ACL Policy is set to Local, access to local services does not
depend on the CredentialPolicy. The Tuxedo remote domain DOMAINID is authenticated as
a local WebLogic Server user. To allow WebLogic Tuxedo Connector to authenticate a
DOMAINID as a local user, use the WebLogic Server Console to complete the following steps:
1. Click on the Security node.
2. Click on Realms.
3. Select your default security Realm.
4. Click on Users.
5. Click the Configure a new User text link.
6. In the General tab, do the following:
a. Add the Tuxedo DOMAINID in the Name field.
BETA
3-10 WebLogic Tuxedo Connector Administration Guide
b. Enter and validate a password.
c. Click apply.
ACL Policy is GLobal
If the WebLogic Tuxedo Connector ACL Policy is GLOBAL, access to local services depends on
the CredentialPolicy.
Credential Policy is Global
If a remote domain is running with the CredentialPolicy set to GLOBAL, the request has the
credentials of the caller.
CredentialPolicy is Local
If a remote domain is running with the CredentialPolicy set to LOCAL, the result depends on
the user configuration that initiated the call.
User Authenticaion for Tuxedo 6.5
Tuxedo 6.5 users should set the Interoperate parameter to Yes. The AclPolicy and
CredentialPolicy elements are ignored and the Tuxedo remote domain DOMAINID is
authenticated as a local WebLogic Server user. If you require User Security features and use the
WebLogic Tuxedo Connector, you will need to upgrade to Tuxedo 7.1 or higher.
How to Configure WebLogic Tuxedo Connector to Provide
Security between Tuxedo and WebLogic Server
The following sections provide information on how to configure WebLogic Tuxedo provide user
security information to Tuxedo:
zTpUsrFile Plug-in
zLDAP Plug-in
zCustom Plug-in
zAnonymous Users
BETA
How to Configure WebLogic Tuxedo Connector to Provide Security between Tuxedo and WebLogic Server
WebLogic Tuxedo Connector Administration Guide 3-11
TpUsrFile Plug-in
The TpUsrFile plug-in provides traditional Tuxedo TpUserFile functionality for users who do not
need single point security administration or custom security authentication. Use the following
steps to configure WebLogic Tuxedo Connector to provide security between Tuxedo and
WebLogic Server applications using the TpUsrFile plug-in AppKey Generator:
zConfiguring the Local Tuxedo Access Point for the TpUsrFile Plug-in
zConfigure the Remote Tuxedo Access Point for the TpUsrFile Plug-in
Configuring the Local Tuxedo Access Point for the TpUsrFile Plug-in
Set the security attribute in the Security tab of the local Tuxedo access point of your WTC
Service to match the SECURITY parameter of the *DM_LOCAL_DOMAINS section of the
Tuxedo domain configuration file.
Configure the Remote Tuxedo Access Point for the TpUsrFile Plug-in
Configure the Security tab of the remote Tuxedo access point of your WTC Service to establish
an inbound and outbound Access Control List (ACL) policy.
Perform the following steps to prepare the WebLogic Server environment:
1. Set the AclPolicy attribute to GLOBAL.
2. Set the CredentialPolicy attribute to GLOBAL.
3. Set the Allow Anonymous attribute for your environment. If you select to allow anonymous
users to access Tuxedo, you must set the value of the Default AppKey to be used by
anonymous users. For more information on anonymous users, see “Anonymous Users” on
page 3-14.
4. Select TpUsrFile from the AppKey Generator dropdown box.
5. Set the value of the Tp Usr File attribute to the full path to the user password file.
You must have a copy of the Tuxedo tpusr file in your WebLogic Server environment.
Copy the tpusr file from TUXEDO to the WebLogic Server application environment or
generate your own tpusr file. For more information on how to create a Tuxedo tpusr file,
see How to Enable User-Level Authentication at
http://e-docs.bea.com/tuxedo/tux81/sec/secadm.htm#1239966.
BETA
3-12 WebLogic Tuxedo Connector Administration Guide
Using the Resources TpUsrFile attribute
The location of the TpUsrFile can be specified from your remote Tuxedo access point
configurations or from your Resources configuration. You may find it convenient assign the
value of the TpUsrFile attribute globally at the WTC Service level, rather than by assigning it
individually on all of your remote Tuxedo access point configurations. Use the following
guidelines to help you determine where to best configure the TpUsrFile attribute:
zAll TpUsrFile attribute values are ignored if the TpUsrFile Plug-in is not selected as the
AppKey Generator, regardless of location.
zIf the Resources configuation does not have TpUsrFile attribute values, the TpUsrFile
attribute value must be specified in the remote Tuxedo access point configurations. The
cached user record information is ignored.
zIf the Resources and remote Tuxedo access point configurations contain TpUsrFile
attribute values, the attribute values in the remote Tuxedo access points are used. The
cached user record information is ignored.
zIf the remote Tuxedo access point configuations do not have TpUsrFile attribute values, the
TpUsrFile attribute value must be specified in the Resources configuration. The cached
user record is used, which improves system performance. However, this restricts the user to
have the same identity in all remote Tuxedo access points.
LDAP Plug-in
The LDAP plug-in provides single point security administration that allows you to maintain user
security information in a WebLogic Server embedded LDAP server and use the WebLogic Server
Console to administer the security information from a single system. Requires Tuxedo 8.1 and
higher.Use the following steps to configure WebLogic Tuxedo Connector to provide security
between Tuxedo and WebLogic Server applications using the LDAP Plug-in AppKey Generator:
zImplementing Single Point Security Administration
zConfigure the Local Tuxedo Access Point for the LDAP Plug-in
zConfigure the Remote Tuxedo Access Point for the LDAP Plug-in
Implementing Single Point Security Administration
Detailed information on how to implement single point security administration, see
Implementing Single Point Security Administration located at
BETA
How to Configure WebLogic Tuxedo Connector to Provide Security between Tuxedo and WebLogic Server
WebLogic Tuxedo Connector Administration Guide 3-13
http://e-docs.bea.com/tuxedo/tux81/sec/sngleadm.htm. For information on WebLogic Security,
see Introduction to WebLogic Security at http://e-docs.bea.com/wls/docs90/secintro/index.html.
Configure the Local Tuxedo Access Point for the LDAP Plug-in
Set the security attribute in the Security tab of the local Tuxedo access point of your WTC
Service to match the SECURITY parameter of the *DM_LOCAL_DOMAINS section of the
Tuxedo domain configuration file.
Configure the Remote Tuxedo Access Point for the LDAP Plug-in
Configure the Security tab of the remote Tuxedo access point of your WTC Service to establish
an inbound and outbound Access Control List (ACL) policy.
Perform the following steps to prepare the WebLogic Server environment:
1. Set the AclPolicy attribute to GLOBAL.
2. Set the CredentialPolicy attribute to GLOBAL.
3. Set the Allow Anonymous attribute for your environment. If you select to allow anonymous
users to access Tuxedo, you must set the value of the Default AppKey to be used by
anonymous users. For more information on anonymous users, see “Anonymous Users” on
page 3-14.
4. Select LDAP from the AppKey Generator dropdown box.
5. If necessary, set the value of the Tuxedo UID Keyword attribute and Tuxedo GID attribute.
Default values are provided. These keywords for the Tuxedo user ID (UID) is used to
extract the Tuxedo UID and GID in the user record of the embedded LDAP database.
Custom Plug-in
Note: For information on how to create a Custom Plug-in, see How to Create a Custom AppKey
Plug-in athttp://e-docs.bea.com/wls/docs90/wtc_atmi/CustomAppKey.html.
The Custom plug-in provides the ability for you to create customized security authentication. Use
the following steps to configure WebLogic Tuxedo Connector to provide security between
Tuxedo and WebLogic Server applications using the Custom Plug-in AppKey Generator:
zConfigure the Local Tuxedo Access Point for the Custom Plug-in
zConfigure the Remote Tuxedo Access Point for the Custom Plug-in
BETA
3-14 WebLogic Tuxedo Connector Administration Guide
Configure the Local Tuxedo Access Point for the Custom Plug-in
Set the security attribute in the Security tab of the local Tuxedo access point of your WTC
Service to match the SECURITY parameter of the *DM_LOCAL_DOMAINS section of the
Tuxedo domain configuration file.
Configure the Remote Tuxedo Access Point for the Custom Plug-in
Configure the Security tab of the remote Tuxedo access point of your WTC Service to establish
an inbound and outbound Access Control List (ACL) policy.
Perform the following steps to prepare the WebLogic Server environment:
1. Set the AclPolicy attribute to GLOBAL.
2. Set the CredentialPolicy attribute to GLOBAL.
3. Set the Allow Anonymous attribute for your environment. If you select to allow anonymous
users to access Tuxedo, you must set the value of the Default AppKey to be used by
anonymous users. For more information on anonymous users, see “Anonymous Users” on
page 3-14.
4. Select Custom from the AppKey Generator dropdown box.
5. Set the value of the Custom AppKey Class attribute to the full pathname to your Custom
AppKey generator class. This class is loaded when the WTC Service is started.
6. Set the value of the Custom AppKey Param attribute to the optional parameters that you
may require to use your Custom AppKey class when it is initialized when the WTC Service
starts.
Anonymous Users
The Allow Anonymous attribute on the Security tab of a remote Tuxedo access point specifies
whether the anonymous user is allowed to access Tuxedo. If the anonymous user is allowed to
access Tuxedo, the value of the Default AppKey attribute is used for TpUsrFile and LDAP
AppKey plug-ins. The TpUsrFile and LDAP plug-ins do not allow users that are not defined in
user database to access Tuxedo unless the Allow Anonymous attribute is enabled. Interaction
with the Custom AppKey plug-in depends on the design of the Custom AppKey generator.
The default value of the Default AppKey is -1. If you wish to use this value, you must make sure
that your Tuxedo environment has a user assigned to that key value. You should avoid assigning
the Default AppKey value to 0. In some systems, this specifies the user as root.
BETA
Link-Level Encryption
WebLogic Tuxedo Connector Administration Guide 3-15
Anonymous Users and CORBA Services
It is important to understand the differences between how ATMI services and CORBA services
authenticate an anonymous user. ATMI services rely on the Default AppKey value sent with the
message. Corba services use the default WebLogic Server anonymous user name <anonymous>
to identify the user credential defined in the Tuxedo tpusr file. CORBA users must configure the
anonymous user using one of the following methods to become an authenticated user:
zAdd <anonymous> to the Tuxedo tpusr file.
zDefine anonymous as a user in the WebLogic Authentication provider. You do this by
setting the following argument when starting a WebLogic Server instance:
-Dweblogic.security.anonymousUserName=anonymous
Link-Level Encryption
You can use encryption to ensure data privacy. In this way, a network-based eavesdropper cannot
learn the content of messages or application-generated messages flowing from one domain
gateway to another. You configure this security mechanism by setting the MINENCRYPTBITS and
MAXENCRYPTBITS attributes of the Security tab in the local Tuxedo access points and remote
Tuxedo access points configurations of your WTC Service.
Note: Encryption requires appropriate licensing. For more information on license
requirements, see “Licensing” on page 1-3.
BETA
3-16 WebLogic Tuxedo Connector Administration Guide
BETA
WebLogic Tuxedo Connector Administration Guide 4-1
CHAPTER 4
Administration of CORBA Applications
Note: For more information on CORBA applications, see Tuxedo CORBA at
http://e-docs.bea.com/tuxedo/tux80/interm/corba.htm.
The following sections provide information on how to administer and configure the WebLogic
Tuxedo Connector to support Tuxedo CORBA clients and services.
zHow to Configure WebLogic Tuxedo Connector for CORBA Service Applications
zHow to Administer and Configure WebLogic Tuxedo Connector for Inbound RMI-IIOP
zHow to Configure WebLogic Tuxedo Connector for Outbound RMI-IIOP
How to Configure WebLogic Tuxedo Connector for CORBA
Service Applications
Note: For more information on how to configure your WTC Service, see “Configuring
WebLogic Tuxedo Connector for Your Applications” on page 2-2.
This section provides information on how to configure a WTC Service to support a call to a
Tuxedo CORBA server from a WebLogic Server EJB. Use the following steps to configure your
WTC Service:
1. Configure Local Tuxedo Access Points WebLogic Server applications.
2. Configure Remote Tuxedo Access Points for your Tuxedo CORBA domain.
3. Configure Imported Services.
BETA
4-2 WebLogic Tuxedo Connector Administration Guide
zSet Resource Name to “//domain_id” where domain_id is DOMAINID specified in the
Tuxedo UBBCONFIG file of the remote Tuxedo domain where the object is deployed. The
maximum length of this unique identifier for CORBA domains is 15 characters including
the //.
zSet Local Access Point to the value of the Local Access Point attribute of your
Remote Tuxedo Access Point.
zSet the Remote Access Point List to the value of the Access Point Id attribute of
the Remote Tuxedo Access Point.
For information on how to develop client applications that call a Tuxedo CORBA service using
a WebLogic Server EJB, see the WebLogic Tuxedo Connector Programmer’s Guide at
http://e-docs.bea.com/wls/docs90/wtc_atmi/index.html.
Example WTC Service and Tuxedo UBB Files
The following WTC Service (represented by the WTCServer MBean in the config.xml file)
provides an example of how to configure an Imported Services configuration for a TUXEDO
CORBA server.
Listing 4-1 Example WTCServer MBean for a CORBA Server Application
<WTCServer Name="WTCsimpappCNS"
<WTCImport LocalAccessPoint="examples"
Name="myImportedResources" RemoteAccessPointList="TUXDOM"
ResourceName="//simpapp"/>
<WTCLocalTuxDom AccessPoint="examples" AccessPointId="examples"
ConnectionPolicy="ON_DEMAND" NWAddr="//123.123.123.123:5678"
Name="myLoclTuxDom" Security="NONE"/>
<WTCRemoteTuxDom AccessPoint="TUXDOM" AccessPointId="TUXDOM"
LocalAccessPoint="examples" NWAddr="//123.123.123.123:1234"
Name="myRTuxDom"/>
</WTCServer>
The following example Tuxedo UBB configuration file has a DOMAINID name of simpapp. The
DOMAINID name is used in the Resource Name attribute of the Imported Services configuration
of your WTC Service.
BETA
How to Configure WebLogic Tuxedo Connector for CORBA Service Applications
WebLogic Tuxedo Connector Administration Guide 4-3
Listing 4-2 Example Tuxedo UBB File for a CORBA Server Application
*RESOURCES
IPCKEY 55432
DOMAINID simpapp
MASTER SITE1
MODEL SHM
LDBAL N
*MACHINES
"YODA"
LMID=SITE1
APPDIR="your APPDIR"
TUXCONFIG="APPDIR\tuxconfig"
TUXDIR="your TUXDIR"
MAXWSCLIENTS=10
*GROUPS
SYS_GRP
LMID=SITE1
GRPNO=1
APP_GRP
LMID=SITE1
GRPNO=2
*SERVERS
DEFAULT:
RESTART=Y
MAXGEN=5
TMSYSEVT
SRVGRP=SYS_GRP
SRVID=1
TMFFNAME
SRVGRP=SYS_GRP
SRVID=2
CLOPT="-A -- -N -M"
TMFFNAME
SRVGRP=SYS_GRP
SRVID=3
CLOPT= "-A -- -N"
TMFFNAME
BETA
4-4 WebLogic Tuxedo Connector Administration Guide
SRVGRP=SYS_GRP
SRVID=4
CLOPT="-A -- -F"
ISL
SRVGRP=SYS_GRP
SRVID=5
CLOPT="-A -- -n <//your tux machine:2468>"
cns
SRVGRP=SYS_GRP
SRVID=6
CLOPT="-A --"
DMADM SRVGRP=SYS_GRP SRVID=7
GWADM SRVGRP=SYS_GRP SRVID=8
GWTDOMAIN SRVGRP=SYS_GRP SRVID=9
simple_server
SRVGRP=APP_GRP
SRVID=1
RESTART = N
*SERVICES
How to Administer and Configure WebLogic Tuxedo Connector
for Inbound RMI-IIOP
This section provides information on how to administer your application environment and
configure your WTC Service to enable Tuxedo CORBA objects to invoke upon EJBs deployed
in WebLogic Server using the RMI-IIOP API.
zConfiguring Your WTC Service for Inbound RMI-IIOP
zAdministering the Tuxedo Application Environment
Configuring Your WTC Service for Inbound RMI-IIOP
Note: For more information on how to configure your WTC Service, see “Configuring
WebLogic Tuxedo Connector for Your Applications” on page 2-2.
BETA
How to Administer and Configure WebLogic Tuxedo Connector for Inbound RMI-IIOP
WebLogic Tuxedo Connector Administration Guide 4-5
Configure Local Tuxedo Access Points and Remote Tuxedo Access Points as needed for your
environment. No special administration steps are required to enable Tuxedo CORBA objects to
invoke upon EJBs deployed in WebLogic Server using the RMI-IIOP API.
Administering the Tuxedo Application Environment
Note: For more information on how to configure your Tuxedo application environment, see
Tuxedo Administration Topics at
http://e-docs.bea.com/tuxedo/tux80/interm/admin.htm.
You must perform some additional steps when configuring your Tuxedo application
environment.
1. Set the TOBJADDR for your environment.
Example: //<hostname>:2468
2. Register WebLogic Server (WLS) Naming Service in the Tuxedo domain’s CosNaming
namespace by entering the following command:
cnsbind -o ior.txt your_bind_name
where
your_bind_name is the CosNaming service object name from your Tuxedo
application.
The ior.txt file contains the URL of the WebLogic Server’s domain Naming Service.
Listing 4-3 ior.txt File for iiop.ejb.stateless.server.tux Tuxedo Client Example
corbaloc:tgiop:myServer/NameService
where
myServer is your server name.
3. Modify the *DM_REMOTE_SERVICES of your Tuxedo domain configuration file. Replace
your WebLogic Server service name, formerly the DOMAINID, with the name of your
WebLogic Server.
BETA
4-6 WebLogic Tuxedo Connector Administration Guide
Listing 4-4 Domain Configuration File
*DM_RESOURCES
VERSION=U22
*DM_LOCAL_DOMAINS
TDOM1 GWGRP=SYS_GRP
TYPE=TDOMAIN
DOMAINID="TDOM1"
BLOCKTIME=20
MAXDATALEN=56
MAXRDOM=89
*DM_REMOTE_DOMAINS
TDOM2 TYPE=TDOMAIN
DOMAINID="TDOM2"
*DM_TDOMAIN
TDOM1 NWADDR="//123.123.123.123:1234"
TDOM2 NWADDR="//234.234.234.234:5678"
*DM_REMOTE_SERVICES
"//myServer"
where
myServer is the server name that is running the WTC Service.
4. Load your modified domain configuration file using dmloadcf.
Guidelines About Using Your Server Name as an Object Reference
This section provides guidelines you need to remember when creating server names that are used
as object references.
zThe maximum field length Tuxedo accepts in the *DM_REMOTE_SERVICES section is 15
characters including the //. For example: If your server name is examplesServer, your
*DM_REMOTE_SERVICES object reference is //examplesServe.
BETA
How to Configure WebLogic Tuxedo Connector for Outbound RMI-IIOP
WebLogic Tuxedo Connector Administration Guide 4-7
zIf you require muliple servers, the server names must be unique in the first 13 charactcers.
zYou can use the complete name of your server name in the ior.txt file if it exceeds 13
characters. For example: corbaloc:tgiop:examplesServer/NameService
How to Configure WebLogic Tuxedo Connector for Outbound
RMI-IIOP
Note: For more information on how to configure your WTC Service, see “Configuring
WebLogic Tuxedo Connector for Your Applications” on page 2-2.
This section provides information on how to enable WebLogic Server EJBs to invoke upon
Tuxedo CORBA objects using the RMI-IIOP API. Use the following steps to modify your WTC
Service:
1. Configure a Local Tuxedo Access Point.
2. Configure Remote Tuxedo Access Point. Outbound RMI-IIOP requires two additional
elements: Federation URL and Federation Name.
zSet Federation URL to the URL for a foreign name service that is federated into the
JNDI. This must be the same URL used by the EJB to obtain the initial context used to
access the remote Tuxedo CORBA object.
zSet Federation Name to the symbolic name of the federation point.
3. Configure Imported Services.
zSet Resource Name to “//domain_id” where domain_id is DOMAINID specified in the
Tuxedo UBBCONFIG file of the remote Tuxedo domain where the object is deployed. The
maximum length of this unique identifier for CORBA domains is 15 characters including
the //.
zSet Local Access Point to the value of the Local Access Point attribute of your
Remote Tuxedo Access Point.
zSet Remote Access Point List to the value of the Access Point Id attribute of
your Remote Tuxedo Access Point.
For information on how to develop applications that use RMI-IIOP to call a Tuxedo service using
a WebLogic Server EJB, see the WebLogic Tuxedo Connector Programmer’s Guide at
http://e-docs.bea.com/wls/docs90/wtc_atmi/index.html.
BETA
4-8 WebLogic Tuxedo Connector Administration Guide
Example Outbound RMI-IIOP Configuration
The following WTCServer MBean in the config.xml file provides an example of a configured
WTC Service for outbound RMI-IIOP.
Listing 4-5 Example WTCServer MBean for Outbound RMI-IIOP
.
.
.
<WTCServer Name="WTCtrader">
<WTCImport LocalAccessPoint="TDOM2" Name="myImportedResources"
RemoteAccessPointList="TDOM1" ResourceName="//simpapp"/>
<WTCLocalTuxDom AccessPoint="TDOM2" AccessPointId="TDOM2"
ConnectionPolicy="ON_DEMAND" NWAddr="//123.123.123.123:5678"
Name="myLoclTuxDom" Security="NONE"/>
<WTCRemoteTuxDom AccessPoint="TDOM1" AccessPointId="TDOM1"
FederationName="tuxedo.corba.remote"
FederationURL="corbaloc:tgiop:simpapp/NameService"
LocalAccessPoint="TDOM2" NWAddr="//123.123.123.123:1234"
Name="myRTuxDom"/>
</WTCServer>
.
.
.
BETA
WebLogic Tuxedo Connector Administration Guide 5-1
CHAPTER 5
How to Manage WebLogic Tuxedo
Connector in a Clustered Environment
Note: For more information on WebLogic Server Clusters, see Using WebLogic Server
Clusters at http://e-docs.bea.com/wls/docs90/cluster/index.html.
The following sections provide information on how to administer and configure the WebLogic
Tuxedo Connector for use in a clustered environment:
zWebLogic Tuxedo Connector Guidelines for Clustered Environments
zHow to Configure OutBound Requests to Tuxedo Domains
zHow to Configure Inbound Requests from Tuxedo Domains
WebLogic Tuxedo Connector Guidelines for Clustered
Environments
Use the following guidelines when deploying WebLogic Tuxedo Connector in a clustered
environment:
zBecause the binding is not replicated in other servers in a cluster, all the WebLogic Servers
in the cluster must have a configured WebLogic Tuxedo Connector that includes an
Imported Services tab that defines any imported services required. If one server in the
cluster does not have a WebLogic Tuxedo Connector deployed, the Enterprise Java Bean
(EJB) or Message Driven Bean (MDB) won't be able to find a Tuxedo Connection Factory
for that connection.
BETA
5-2 WebLogic Tuxedo Connector Administration Guide
zThe administrator is responsible for the correct configuration of the TUXEDO
DMCONFIG to allow proper load balancing and fail over of inbound calls to clustered
nodes.
zWebLogic Tuxedo Connector does not support inbound TGIOP in clustered environments.
How to Configure OutBound Requests to Tuxedo Domains
Note: For more information on WebLogic Server Clusters, see Cluster Features and
Infrastructure at http://e-docs.bea.com/wls/docs90/cluster/features.html. WebLogic
Tuxedo Connector also provides domain-level failover and failback capabilities. For
more information, see “Configuring Failover and Failback” on page 3-4.
The load balancing and failover of the outbound requests from WebLogic Server depend on the
WebLogic Server EJB and MDB.
Example Clustered WebLogic Tuxedo Connector Configuration
The following configuration provides an example of WebLogic Tuxedo Connector in a clustered
environment. The cluster consists of an administration server (wtcAServer) and three managed
servers (wtcMServer1, wtcMServer2, wtcMServer3). Each managed server has a configured
WTC Service that contains the same service (TOUPPER) in as an imported service.
Listing 5-1 Example Clustered WebLogic Tuxedo Connector Configuration
<Domain Name="wtcDomain" >
<Security Name="wtcDomain" Realm="mysecurity"/>
<Realm Name="mysecurity" FileRealm="myrealm"/>
<FileRealm Name="myrealm"/>
<Cluster Name="wtcCluster" MulticastAddress="239.0.0.20"
MulticastPort="7700" MulticastTTL="1"/>
<Security GuestDisabled="false"/>
<Server Name="wtcAServer" NativeIOEnabled="true" ListenPort="3472"
ListenAddress="mymachine" TunnelingEnabled="true" >
<SystemDataStore ListenPort="7555" ListenAddress="mymachine" />
</Server>
<Server Name="wtcMServer1" Cluster="wtcCluster" NativeIOEnabled="true"
ListenPort="7701" ListenAddress="mymachine" TunnelingEnabled="true" >
BETA
How to Configure OutBound Requests to Tuxedo Domains
WebLogic Tuxedo Connector Administration Guide 5-3
</Server>
<Server Name="wtcMServer2" Cluster="wtcCluster" NativeIOEnabled="true"
ListenPort="7702" ListenAddress="mymachine" TunnelingEnabled="true" >
</Server>
<Server Name="wtcMServer3" Cluster="wtcCluster" NativeIOEnabled="true"
ListenPort="7703" ListenAddress="mymachine" TunnelingEnabled="true" >
</Server>
<WTCServer Name="WTCServer1" Targets="wtcMServer1">
<WTCExport EJBName="tuxedo.services.TOLOWERHome"
LocalAccessPoint="WDOM1" Name="exp0" ResourceName="TOLOWER"/>
<WTCImport LocalAccessPoint="WDOM1" Name="imp0"
RemoteAccessPointList="TDOM2,TDOM1" ResourceName="TOUPPER"/>
<WTCLocalTuxDom AccessPoint="WDOM1" AccessPointId="WDOM1"
BlockTime="30000" ConnectionPolicy="ON_DEMAND"
NWAddr="//mymachine:20401" Name="ltd0" Security="NONE"/>
<WTCRemoteTuxDom AccessPoint="TDOM1" AccessPointId="TDOM1"
LocalAccessPoint="WDOM1" NWAddr="//123.123.123.123:20301"
Name="rtd0"/>
<WTCRemoteTuxDom AccessPoint="TDOM2" AccessPointId="TDOM2"
LocalAccessPoint="WDOM1" NWAddr="//123.123.123.123:20302"
Name="rtd1"/>
</WTCServer>
<WTCServer Name="WTCServer2" Targets="wtcMServer2" >
<WTCExport EJBName="tuxedo.services.TOLOWERHome"
LocalAccessPoint="WDOM2" Name="exp1" ResourceName="TOLOWER"/>
<WTCImport LocalAccessPoint="WDOM2" Name="imp1"
RemoteAccessPointList="TDOM1,TDOM2" ResourceName="TOUPPER"/>
<WTCLocalTuxDom AccessPoint="WDOM2" AccessPointId="WDOM2"
BlockTime="30000" ConnectionPolicy="ON_DEMAND"
NWAddr="//mymachine:20402" Name="ltd1" Security="NONE"/>
<WTCRemoteTuxDom AccessPoint="TDOM1" AccessPointId="TDOM1"
LocalAccessPoint="WDOM2" NWAddr="//123.123.123.123:20301"
Name="rtd2"/>
<WTCRemoteTuxDom AccessPoint="TDOM2" AccessPointId="TDOM2"
LocalAccessPoint="WDOM2" NWAddr="//123.123.123.123:20302"
Name="rtd3"/>
</WTCServer>
<WTCServer Name="WTCServer3" Targets="wtcMServer3" >
<WTCExport EJBName="tuxedo.services.TOLOWERHome"
LocalAccessPoint="WDOM3" Name="exp2" ResourceName="TOLOWER"/>
<WTCImport LocalAccessPoint="WDOM3" Name="imp2"
BETA
5-4 WebLogic Tuxedo Connector Administration Guide
RemoteAccessPointList="TDOM1,TDOM2" ResourceName="TOUPPER"/>
<WTCLocalTuxDom AccessPoint="WDOM3" AccessPointId="WDOM3"
BlockTime="30000" ConnectionPolicy="ON_DEMAND"
NWAddr="//mymachine:20403" Name="ltd2" Security="NONE"/>
<WTCRemoteTuxDom AccessPoint="TDOM1" AccessPointId="TDOM1"
LocalAccessPoint="WDOM3" NWAddr="//123.123.123.123:20301"
Name="rtd4"/>
<WTCRemoteTuxDom AccessPoint="TDOM2" AccessPointId="TDOM2"
LocalAccessPoint="WDOM3" NWAddr="//123.123.123.123:20302"
Name="rtd5"/>
</WTCServer>
</Domain>
How to Configure Inbound Requests from Tuxedo Domains
Load balancing and failover of inbound requests from Tuxedo depend on the Tuxedo domain
DMCONFIG configuration.
Load Balancing
Note: For more information on Tuxedo Load Balancing
http://e-docs.bea.com/tuxedo/tux81/int/intatm.htm#1119040.
The following is a sample Tuxedo DMCONFIG that load balances from Tuxedo to clustered
WTC. This configuration has three nodes in a WebLogic Server cluster. Each node has a single
properly configured WebLogic Tuxedo Connector instance that provides an exported service that
is accessible to the Tuxedo client.
*DM_IMPORT
TOUPPER LDOM=tuxedo_dom RDOM=WDOM1 LOAD=50
TOUPPER LDOM=tuxedo_dom RDOM=WDOM2 LOAD=50
TOUPPER LDOM=tuxedo_dom RDOM=WDOM3 LOAD=50
BETA
How to Configure Inbound Requests from Tuxedo Domains
WebLogic Tuxedo Connector Administration Guide 5-5
Fail Over
Notes: For more information on Specifying Domains Failover and Failback on Tuxedo, see
http://e-docs.bea.com/tuxedo/tux81/add/addom.htm#1257878.
The following is a sample Tuxedo DMCONFIG that uses a more sophisticated configuration that
load balances between the WebLogic Server nodes as well as illustrate Tuxedo failover
capability. The Tuxedo domain must be configured with a Connection Policy of On Startup
or Incoming Only to enable Domains-level failover/failback.
*DM_IMPORT
TOUPPER LDOM=tuxedo_dom RDOM=WDOM1,WDOM2,WDOM3 LOAD=50
TOUPPER LDOM=tuxedo_dom RDOM=WDOM2,WDOM3,WDOM1 LOAD=50
TOUPPER LDOM=tuxedo_dom RDOM=WDOM3,WDOM1,WDOM2 LOAD=50
BETA
5-6 WebLogic Tuxedo Connector Administration Guide
BETA
WebLogic Tuxedo Connector Administration Guide 6-1
CHAPTER 6
How to Configure the Tuxedo Queuing
Bridge
The following sections provide information on the Tuxedo Queuing Bridge functionality and
configuration.
zOverview of the Tuxedo Queuing Bridge
zConfiguring the Tuxedo Queuing Bridge
zTuxedo Queuing Bridge Connectivity
zExample Connection Type Configurations
zPriority Mapping
zError Queues
Overview of the Tuxedo Queuing Bridge
The Tuxedo Queuing Bridge is a part of the WebLogic Tuxedo Connector that provides a
bi-directional JMS interface for your WebLogic Server applications communicate to Tuxedo
application environments. The transfer of messaging between the environments consists of JMS
based messages containing text, Byte, or XML data streams used to invoke services on behalf of
the client application.
BETA
6-2 WebLogic Tuxedo Connector Administration Guide
Figure 6-1 Interaction between WebLogic Server and Tuxedo with the Queing Bridge
The following features determine the functionality of the Tuxedo Queuing Bridge:
zConnectivity is determined by the configuration of the attributes in theTuxedo Queuing
Bridge and Redirections of your WTC Service.
zThe Tuxedo Queuing Bridge uses Java Messaging Service (JMS) to provide an interface to
a Tuxedo /Q or a Tuxedo service.
zThe Tuxedo Queuing Bridge provides simple translation between XML and FML32 to
provide connectivity to existing Tuxedo systems.
How Tuxedo Queuing Bridge connects JMS with Tuxedo
Note: All messages remain on the JMS queue until they have been acknowledged.
This section provides information on how JMS messages flow through the Tuxedo Queuing
Bridge to Tuxedo queues and services.
BETA
Overview of the Tuxedo Queuing Bridge
WebLogic Tuxedo Connector Administration Guide 6-3
1. A JMS client, such as a web enabled WLPI application, places a message to be processed by
Tuxedo on a JMS Queue. If this message was part of a transaction, the transaction commits.
2. The message is removed from the JMS queue to be processed by the Tuxedo Queuing
Bridge Converter.
3. The Tuxedo Queuing Bridge Converter checks the message type and converts supported
JMS types to JATMI buffer types.
zBytesMessage, TextMessage, XML are converted respectively to TypedCArray,
TypedString, and TypedFML32. XML/FML translation is performed according to the
TranslateFML attribute.
zTranslation errors are sent to the wlsServerErrorDestination queue and the message is
acknowledged in the JMS session.
zIf an unrecognized JMS message is received: an appropriate error message is logged, the
message is acknowledged, and then is discarded. This is considered a configuration error
and the Tuxedo Queuing Bridge does not redirect the message to the error queue.
4. The converted message is sent to Tuxedo using the T/Domain gateway.
zMessages with a redirect set to JmsQ2TuxQ use JATMI tpenqueue to deliver the message
to a Tuxedo queue.
zMessages with a redirect set to JmsQ2TuxS use JATMI tpcall to deliver the message to a
Tuxedo service.
5. The tpenqueue is successful or tpcall is successful and the return results are placed in the
replyQ. The message is acknowledged in the JMS session.
zIf the tpenqueue or tpcall fails, Tuxedo Queuing Bridge delivers the message to the
wlsServerErrorDestination queue and the message is acknowledged in the JMS
session. If a wlsServerErrorDestination queue is not configured, the message is
discarded and the Tuxedo Queuing Bridge processes the next available unacknowledged
message.
How Tuxedo Queuing Bridge connects Tuxedo to JMS
Note: Tuxedo Queuing Bridge uses a transaction to prevent the loss of messages while
transferring messages from Tuxedo /Q to a JMS queue.
This section provides information on how Tuxedo messages flow through the Tuxedo Queuing
Bridge to a JMS queue using the TuxQ2JmsQ redirect.
BETA
6-4 WebLogic Tuxedo Connector Administration Guide
1. Tuxedo Queuing Bridge polls the Tuxedo queue for available messages.
2. A Tuxedo service places a message on a Tuxedo queue.
3. Tuxedo Queuing Bridge uses JATMI tpdequeue to forward the message from Tuxedo and
places the message in the JMS queue.
zIf a message cannot be redirected to a JMS queue for any reason after the specified retries
have been exhausted, the message is put into the tuxErrorDestination queue within the
same queue space as the Tuxedo queue.
zIf the Tuxedo Queuing Bridge is not able to put the message into the
tuxErrorDestination queue for any reason, an error is logged and the message is lost.
zIf the tuxErrorDestination queue is not specified, the message is lost.
Tuxedo Queuing Bridge Limitations
The Tuxedo Queuing Bridge has the following limitations:
zTransactions are not used when retrieving messages from the JMS location and placing
them on the Tuxedo queue or invoking a Tuxedo service.
zTuxedo Queuing Bridge is thread intensive. A thread is used to transport each message
from JMS queue to Tuxedo. A polling thread is required to monitor the configured Tuxedo
queue.
zThe XML/FML translator is intended to construct simple message structures. For more
information on XML to FML conversion see, FML32 Considerations at
http://e-docs.bea.com/wls/docs90/wtc_atmi/XML_FML.html.
Configuring the Tuxedo Queuing Bridge
Tuxedo Queuing Bridge connectivity is determined by configuring the attributes in the Tuxedo
Queuing Bridge and Redirections of your WTC Service. These attributes contain the necessary
information to establish a connection to Tuxedo.
Starting the Tuxedo Queuing Bridge
The Tuxedo Queuing Bridge is started as part of the WebLogic Server application environment
if the Tuxedo Queuing Bridge and Redirections of your WTC Service are configured and the
WTC Service is is deployed to a target server. Any configuration condition that prevents the
Tuxedo Queuing Bridge from starting results in an error being logged.
BETA
Tuxedo Queuing Bridge Connectivity
WebLogic Tuxedo Connector Administration Guide 6-5
Error Logging
WebLogic Tuxedo Connector errors are logged to the WebLogic Server error log.
Tuxedo Queuing Bridge Connectivity
Note: JMS message types: MapMessage, ObjectMessage, StreamMessage are not valid in
WebLogic Tuxedo Connector. If one of these message types is received by the Tuxedo
Queuing Bridge, a log entry is generated indicating this is an unsupported type and the
message is discarded.
The Tuxedo Queuing Bridge establishes a one-way data connection between instances of a JMS
queue and a Tuxedo /Q or a JMS queue and a Tuxedo service. This connection is represented by
the Tuxedo Queuing Bridge and Redirections configurations of your WTC Service and provides
a one-to-one connection between the identified points. Three types of connections can be
configured. The following is a description of each of the connection types:
zJmsQ2TuxQ: Reads from a given JMS queue and transports the messages to the specified
Tuxedo /Q.
zTuxQ2JmsQ: Reads from a Tuxedo /Q and transports the messages to JMS.
zJmsQ2TuxS: Reads from a given JMS queue, synchronously calls the specified Tuxedo
service, and places the reply back onto a specified JMS queue.
Example Connection Type Configurations
The following sections provide example configurations for each connection type.
Example JmsQ2TuxQ Configuration
The following section provides an example configuration in the config.xml file for reading
from a JMS queue and sending to Tuxedo /Q.
<WTCtBridgeRedirect
Direction="JmsQ2TuxQ"
Name="redir0"
ReplyQ="RPLYQ"
SourceName="weblogic.jms.Jms2TuxQueue"
TargetAccessPoint="TDOM2"
TargetName="STRING"
BETA
6-6 WebLogic Tuxedo Connector Administration Guide
TargetQspace="QSPACE"
TranslateFML="NO"/>
The following section describes the components of the JmsQ2TuxQ configuration:
zThe Direction connection type is JmsQ2TuxQ.
zSource Name specifies the name of the JMS queue to read is
weblogic.jms.Jms2TuxQueue. The Tuxedo Queuing Bridge establishes a JMS client
session to this queue using CLIENT_ACKNOWLEDGE semantics.
zTarget Access Point specifies the name of the access point is TDOM2.
zTarget Qspace specifies the name of the Qspace is Qspace.
zTarget Name specifies the name of the queue is STRING.
zReplyQ specifies the name of a JMS reply queue is RPLYQ. Use of this queue causes
tpenqueue to provide TMFORWARD functionality.
zTranslateFML set to NO specifies that no data translation is provided by the Tuxedo
Queuing Bridge.
The following table provides information on JmsQtoTuxQ message mapping:
Example TuxQ2JmsQ Configuration
The following section provides an example configuration in the config.xml file for reading
from a Tuxedo /Q and sending to a JMS queue.
<WTCtBridgeRedirect
Direction="TuxQ2JmsQ"
Name="redir1"
SourceAccessPoint="TDOM2"
SourceName="STRING"
SourceQspace="QSPACE"
From: JMS Message Type To: WebLogic Tuxedo Connector JATMI (Tuxedo)
BytesMessage TypedCArray
TextMessage (translateFML = NONE) TypedString
TextMessage (translateFML = FLAT) TypedFML32
BETA
Example Connection Type Configurations
WebLogic Tuxedo Connector Administration Guide 6-7
TargetName="weblogic.jms.Tux2JmsQueue"
TranslateFML="NO"/>
The following section describes the components of the TuxQ2JmsQ configuration:
zThe Direction connection type is TuxQ2JmsQ.
zTarget Name specifies the name of the JMS queue to read is
weblogic.jms.Tux2JmsQueue.
zSource Access Point specifies the name of the access point is TDOM2.
zSource Qspace specifies the name of the Qspace is Qspace.
zSource Name specifies the name of the queue is STRING.
zTranslateFML set to NO specifies that no data translation is provided by the Tuxedo
Queuing Bridge.
zTranslateFML set to Flat specifies that the data is translated from FML to XML by the
Tuxedo Queuing Bridge.
The following table provides information on TuxQ2JmsQ message mapping:
Example JmsQ2TuxS Configuration
Note: For more information on XML/FML conversion, see Using FML with WebLogic
Tuxedo Connector at http://e-docs.bea.com/wls/docs90/wtc_atmi/XML_FML.html.
The following section provides an example configuration in the config.xml file for reading
from a JMS queue, calling a Tuxedo service, and then writing the results back to a JMS queue.
From: WebLogic Tuxedo Connector JATMI
(Tuxedo)
To: JMS Message Type
TypedCArray BytesMessage
TypedString (translateFML = NO) TextMessage
TypedFML32 (translateFML = FLAT) TextMessage
TypedFML (translateFML = FLAT) TextMessage
TypedXML TextMessage
BETA
6-8 WebLogic Tuxedo Connector Administration Guide
<WTCtBridgeRedirect
Direction="JmsQ2TuxS"
Name="redir0"
ReplyQ="weblogic.jms.Tux2JmsQueue"
SourceName="weblogic.jms.Jms2TuxQueue"
TargetAccessPoint="TDOM2"
TargetName="TOUPPER"
TranslateFML="FLAT"/>
The following section describes the components of the JmsQ2TuxS configuration:
zThe Direction connection type is JmsQ2TuxS.
zSource Name specifies the name of the JMS queue to read is
weblogic.jms.Jms2TuxQueue.
zTarget Access Point specifies the name of the access point is TDOM2.
zTarget Name specifies the name of the queue is TOUPPER.
zReplyQ specifies the name of the JMS reply queue is weblogic.jms.Tux2JmsQueue.
zTranslateFML set to FLAT specifies that when a JMS message is received, the message is
in XML format and is converted into the corresponding FML32 data buffer. The message
is then placed in a tpcall with arguments TDOM2 and TOUPPER. The resulting message is
then translated from FML32 into XML and placed on the weblogic.jms.Tux2JmsQueue.
The following table provides information on the JMSQ2TuxX message mapping:
JMS Message Type WebLogic Tuxedo Connector JATMI
(Tuxedo)
JMS Message Type
BytesMessage TypedCArray BytesMessage
TextMessage
(translateFML = NONE) TypedString TextMessage
TextMessage
(translateFML = FLAT) TypedFML32 TextMessage
BETA
Priority Mapping
WebLogic Tuxedo Connector Administration Guide 6-9
Priority Mapping
WebLogic Tuxedo Connector supports multiple Tuxedo Queuing Bridge redirect instances. In
many environments, using multiple redirect instances significantly improves application
scalability and performance. However, it does randomizes the order in which messages are
processed. Although priority mapping does not guarantee ordering, it does provides a mechanism
to react to messages based on an assigned importance. If the order of delivery must be guaranteed,
use a single Tuxedo Queuing Bridge redirect instance.
Use Priority Mapping to map priorities between the JMS and Tuxedo.
zJMS has ten priorities (0 - 9).
zTuxedo/Q has 100 priorities (1 - 100).
This section provides a mechanism to map the priorities between the Tuxedo and JMS
subsystems. There are two mapping directions:
zJmstoTux
zTuxtoJms
Defaults are provided for all values, shown below in pairs of value:range.
zThe value specifies the given input priority.
zThe range specifies a sequential group of resulting output priorities.
JmstoTux- 0:1 | 1:12 | 2:23 | 3:34 | 4:45 | 5:56 | 6:67 | 7:78 | 8:89 | 9:100
TuxtoJms- 1-10:0 | 11-20:1 | 21-30:2 | 31-40:3 | 41-50:4| 51-60:5 | 61-70:6 | 71-80:7 | 81-90:8 |
91-100:9
For this configuration, a JMS message of priority 7 is assigned a priority of 78 in the Tuxedo /Q.
A Tuxedo /Q with a priority of 47 is assigned a JMS priority of 4.
Error Queues
When Tuxedo Queuing Bridge encounters a problem retrieving messages from Tuxedo Queue or
JMS Queue after the retry interval:
zThe information is logged.
zThe message is saved in the error queue if it is configured.
BETA
6-10 WebLogic Tuxedo Connector Administration Guide
WLS Error Destination
The WLS Error Destination queue is used if a JMS message cannot be properly delivered due
to Tuxedo failure or a translation error.
Unsupported Message Types
If an unrecognized JMS message is received, an appropriate error message is logged and the
message is discarded. This is considered a configuration error and the Tuxedo Queuing Bridge
does not redirect the message to the error queue.
Tuxedo Error Queue
The Tuxedo Error Queue is the failure queue for the JATMI primitive tpdequeue during a
TuxQ2JmsQ redirect.
Limitations
The Tuxedo Queuing Bridge error queues have the following limitations:
zTuxedo Error Destination can be specified only once. Any error queue name
associated with the ErrorDestination implies that all the QSPACEs have the same error
queue name available.
zWhen there is an error, the message is put back in the source QSPACE. Assuming the
QSPACE is corrupted or full, subsequent messages would be lost.
zThere is no way to drop messages on error. All messages are received or none are received.
zInformation about the error is only available in the server log.
BETA
WebLogic Tuxedo Connector Administration Guide 7-1
CHAPTER 7
Connecting WebLogic Integration and
Tuxedo Applications
Note: For more information on how to integrate applications, see BEA WebLogic Integration
at http://e-docs.bea.com/more_wlpi.html.
The WebLogic Tuxedo Connector Tuxedo Queuing Bridge provides the necessary infrastructure
for WebLogic Integration users to integrate Tuxedo applications into their business workflows.
The following sections discuss WebLogic Integration - Tuxedo interoperability using the
WebLogic Tuxedo Connector.
zSynchronous WebLogic Integration-to-Tuxedo Connectivity
zSynchronous Non-Blocking WebLogic Integration-to-Tuxedo Connectivity
zAsynchronous WebLogic Integration-to-Tuxedo Connectivity
zAsynchronous Tuxedo /Q-to-WebLogic Integration Connectivity
zBi-directional Asynchronous Tuxedo-to-WebLogic Integration Connectivity
Synchronous WebLogic Integration-to-Tuxedo Connectivity
WebLogic Integration executes a blocking invocation against a Tuxedo service using a JATMI
EJB. This process consists of three parts:
zDefining WebLogic Integration Business Operations.
zInvoking an eLink Adapter.
zDefining WebLogic Integration Exception Handlers.
BETA
7-2 WebLogic Tuxedo Connector Administration Guide
Defining Business Operations
Define WebLogic Integration Business Operations for the JATMI methods to be used:
zTypedFML32 buffer manipulation methods.
zUse the JATMI tpcall() method.
Example: out_buffer = tpcall (service_name, in_buffer, flags)
Invoking an eLink Adapter
Invoke an eLink adapter from a WebLogic Integration process flow:
zBuild TypedFML32 request buffers using defined Business Operations.
zUsing the defined Business Operation invoke the JATMI tpcall() method specifying the
service name.
zProcess TypedFML32 response buffers using defined Business Operations.
Define Exception handlers
Define WebLogic Integration Exception handlers to process exceptions.
Synchronous Non-Blocking WebLogic Integration-to-Tuxedo
Connectivity
WebLogic Integration sends a message to synchronously invoke a Tuxedo service:
z1:1 relationship between JMS queue and the call to a Tuxedo service.
z1:1 relationship between the response from the Tuxedo service and a JMS queue.
zWebLogic Integration writes a message to JMS queue.
zOnce the message is on the JMS queue then Tuxedo Queuing Bridge moves the message to
the target Tuxedo service.
zThe message is translated from/to XML/FML32.
zThe response is written to the specified JMS reply queue.
zThe WebLogic Integration event node waits on the response queue for a response message.
BETA
Asynchronous WebLogic Integration-to-Tuxedo Connectivity
WebLogic Tuxedo Connector Administration Guide 7-3
Asynchronous WebLogic Integration-to-Tuxedo Connectivity
WebLogic Integration sends a guaranteed asynchronous message to a Tuxedo /Q:
z1:1 relationship between JMS queue and Tuxedo /Q.
zWebLogic Integration writes a message to JMS queue.
zOnce the message is on the JMS queue then Tuxedo Queuing Bridge moves the message to
the target Tuxedo /Q on a per message basis.
zMessages in error are forwarded to a specified JMS error queue:
– Infrastructure errors.
– XML/FML32 translation errors.
Asynchronous Tuxedo /Q-to-WebLogic Integration Connectivity
Tuxedo /Q sends a guaranteed asynchronous message to WebLogic Integration:
z1:1 relationship between JMS queue and Tuxedo /Q.
zTuxedo writes a message to Tuxedo /Q.
zOnce the message is committed on Tuxedo /Q, the message is forwarded via the Tuxedo /T
Domain Gateway to the WebLogic Tuxedo Connector Tuxedo Queuing Bridge and target
JMS queue.
zMessages which cannot be forwarded from Tuxedo are enqueued on a Tuxedo /Q error
queue.
zMessages in error are forwarded to a specified Tuxedo /Q error queue, including:
– Infrastructure errors.
– FML32/XML translation errors.
zA workflow is created that waits for the message on the JMS queue. It is defined in the
Start workflow node or in the Event node of an existing workflow instance.
Bi-directional Asynchronous Tuxedo-to-WebLogic Integration
Connectivity
Tuxedo executes a blocking invocation of a WebLogic Integration process flow. Use two
asynchronous instances to connect from JMS to Tuxedo /Q and from Tuxedo /Q back to JMS.
BETA
7-4 WebLogic Tuxedo Connector Administration Guide
BETA
WebLogic Tuxedo Connector Administration Guide 8-1
CHAPTER 8
Troubleshooting The WebLogic Tuxedo
Connector
The following sections provide WebLogic Tuxedo Connector troubleshooting information.
zMonitoring the WebLogic Tuxedo Connector
zFrequently Asked Questions
Monitoring the WebLogic Tuxedo Connector
The WebLogic Tuxedo Connector uses the WebLogic Server log file to record log information.
To record log information you must:
zSet Trace Levels
zEnable Debug Mode
Set Trace Levels
Note: For more information about setting WebLogic Server properties, see “How to Set
WebLogic Tuxedo Connector Properties” on page 2-7.
To enable tracing, update the JAVA_OPTIONS variable in your server start script to the to the
desired level.
Example:
JAVA_OPTIONS=-Dweblogic.wtc.TraceLevel=100000
Use the following values to set the TraceLevel:
BETA
8-2 WebLogic Tuxedo Connector Administration Guide
Enable Debug Mode
Use the following procedure to specify that trace information is written to the log file:
1. Click the Server node in the left pane.
2. Select your server in the left pane.
3. Select the Logging tab.
4. In the General tab:
a. Check Debug to Stdout
b. Set Stdout severity threshold to Info.
Frequently Asked Questions
This section provides solutions to common user questions.
Value Components Traced Description
10000 TBRIDGE_IO Tuxedo Queuing Bridge input and
output
15000 TBRIDGE_EX more Tuxedo Queuing Bridge
information
20000 GWT_IO Gateway input and output, including
the ATMI verbs
25000 GWT_EX more Gateway information
50000 JAMTI_IO JAMTI input and output, including
low-level JAMTI calls
55000 JAMTI_EX more JAMTI information
60000 CORBA_IO CORBA input and output
65000 CORBA_EX more CORBA information
100000 All Components information on all WebLogic Tuxedo
Connector components
BETA
Frequently Asked Questions
WebLogic Tuxedo Connector Administration Guide 8-3
What does this EJB Deployment Message Mean?
When I build the simpserv example, I get the following error:
<date> <Error> <EJB> <EJB Deployment: Tolower has a class
weblogic.wtc.jatmi.tpserviceHome which is in the classpath. This class should
only be located in the ejb-jar file.>
This error message can be ignored for this release of the WebLogic Tuxedo Connector. The EJB
wants all of the interfaces for an EJB call in the EJB jar file. However, some interfaces for the
WebLogic Tuxedo Connector are implemented through the CLASSPATH, and the compiler
throws an exception. When the EJB is deployed, the compiler complains that the EJB cannot be
redeployed because some of its classes are found in the CLASSPATH.
How do I Start the Connector?
Releases prior to WebLogic Server 7.0 used a WebLogic Server Startup class to start a WebLogic
Tuxedo Connector session and a WebLogic Server Shutdown class to end a session. In WebLogic
Server 8.1, WebLogic Tuxedo Connector sessions are managed using a WTC Service.
zA WebLogic Tuxedo Connector session is started when a configured WTC Service is
assigned to a selected server.
zA WebLogic Tuxedo Connector session is ended by removing a WTC Service from the
WebLogic server or when you shutdown the WebLogic server.
How do I Start the Tuxedo Queuing Bridge?
The Tuxedo Queuing Bridge is started if the Tuxedo Queuing Bridge and Redirections
configurations exist in your WTC Service and the WTC Service is assigned to a selected server
How do I Assign a WTC Service to a Server?
The console displays an exception when I try to assign my WTC Service to a server. What should
I do?
Make sure you have a valid WTC Service configured. Each WTC Service must have 1 or more
Local Tuxedo Access Points configured before it can be assigned to a server. Your server log will
display the following:
<Apr 22, 2002 4:21:35 PM EDT> <Error> <WTC> <180101> <At least one local
domain has to be defined.>
BETA
8-4 WebLogic Tuxedo Connector Administration Guide
How do I Resolve Connection Problems?
I'm having trouble getting a connection established between WebLogic Tuxedo Connector and
Tuxedo. What should I do?
zMake sure you have started your Tuxedo server.
zSet the TraceLevel and enable Debug mode. Repeat the connectivity test and check the
WebLogic Tuxedo Connector and Tuxedo log files for error messages.
zAvoid using machine names or localhost. Always use an IP address when specifying a
network location.
zCheck your AclPolicy and CredentialPolicy attributes. If your AclPolicy is LOCAL,
you must register the remote domain DOMAINID as a WebLogic Server user. For more
information, see “User Authentication” on page 3-9.
zIf you are migrating from WebLogic Server 6.x and your applications use security, you
need to set PasswordKey as a WebLogic Server property. For more information, see “How
to Set WebLogic Tuxedo Connector Properties” on page 2-7.
zCheck the WebLogic Tuxedo Connector configuration against the Tuxedo remote domain.
The remote domain must match the name of a remote domain configured in WebLogic
Tuxedo Connector.
For example: If the name simpapp is configured in the Tuxedo DMCONFIG
*DM_LOCAL_DOMAINS section, then this name must match the name in your
Remote Tuxedo Access Point Access Point Id attribute.
zRequest assistance from BEA Customer Support.
How do I Migrate from Previous Releases?
You must make some changes in your WebLogic Tuxedo Connector 6.x applications (including
WebLogic Tuxedo Connector 1.0) to use them with WebLogic Server 9.0. For more information,
see WebLogic Platform Upgrade Planning Guide at
http://e-docs.bea.com/wls/docs90/../../platform/docs90/upgrade/index.html.

Navigation menu