Wtc_admin Web Logic Tuxedo Connector Administration Guide
User Manual:
Open the PDF directly: View PDF 
.
Page Count: 78
| Download | |
| Open PDF In Browser | View PDF |
BEA WebLogic
A
Server
ET
®
B
WebLogic Tuxedo
Connector
Administration Guide
Version 9.0 BETA
Revised: December 15, 2004
A
ET
B
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.
A
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.
ET
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
B
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.
A
ET
B
Contents
About This Document
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii
e-docs Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii
How to Print the Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii
A
Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii
Contact Us! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
ET
Introduction to WebLogic Tuxedo Connector
WebLogic Tuxedo Connector Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Key Functionality and Administrative Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Known Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
B
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
WebLogic Tuxedo Connector Administration Guide
v
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
A
WebLogic Tuxedo Connector Configuration Guidelines. . . . . . . . . . . . . . . . . . . . . . 2-8
WebLogic Tuxedo Connector Administration
ET
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
B
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
vi
WebLogic Tuxedo Connector Administration Guide
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
A
How to Configure WebLogic Tuxedo Connector to Provide Security between Tuxedo and
WebLogic Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
ET
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
B
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
WebLogic Tuxedo Connector Administration Guide
vii
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
A
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
ET
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
B
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
viii
WebLogic Tuxedo Connector Administration Guide
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
A
Synchronous WebLogic Integration-to-Tuxedo Connectivity . . . . . . . . . . . . . . . . . . . . . 7-1
Defining Business Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Invoking an eLink Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
ET
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
B
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
WebLogic Tuxedo Connector Administration Guide
ix
How do I Resolve Connection Problems? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
B
ET
A
How do I Migrate from Previous Releases? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
x
WebLogic Tuxedo Connector Administration Guide
A
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.
ET
The document is organized as follows:
Chapter 1, “Introduction to WebLogic Tuxedo Connector,” is an overview of the WebLogic
Tuxedo Connector.
z
Chapter 2, “Configuring WebLogic Tuxedo Connector,” describes how to configure the
WebLogic Tuxedo Connector.
z
Chapter 3, “WebLogic Tuxedo Connector Administration,” provides configuration
information about the WebLogic Tuxedo Connector.
z
Chapter 4, “Administration of CORBA Applications,” provides information on how to
administer CORBA applications.
z
Chapter 5, “How to Manage WebLogic Tuxedo Connector in a Clustered Environment,”
provides information on how to use WebLogic Tuxedo Connector in a clustered
environment.
z
Chapter 6, “How to Configure the Tuxedo Queuing Bridge,” provides information on
tBridge functionality and configuration.
z
Chapter 7, “Using FML with WebLogic Tuxedo Connector,” discusses the Field
Manipulation Language (FML) and describes how the WebLogic Tuxedo Connector uses
FML.
B
z
WebLogic Tuxedo Connector Administration Guide
xi
About This Do cume nt
z
Chapter 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
How to Print the Document
A
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.
ET
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.
B
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:
xii
z
The OMG Web Site at http://www.omg.org/
z
The Sun Microsystems, Inc. Java site at http://java.sun.com/
WebLogic Tuxedo Connector Administration Guide
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:
Your name, e-mail address, phone number, and fax number
z
Your company name and company address
z
Your machine type and authorization codes
z
The name and version of the product you are using
z
A description of the problem and the content of pertinent error messages
ET
A
z
Documentation Conventions
B
The following documentation conventions are used throughout this document.
Convention
Usage
Ctrl+Tab
Keys you press simultaneously.
italics
Emphasis and book titles.
WebLogic Tuxedo Connector Administration Guide
xiii
About This Do cume nt
Convention
Usage
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
Variables in code.
Example:
String CustomerName;
Device names, environment variables, and logical operators.
Examples:
LPT1
ET
UPPERCASE
TEXT
A
monospace
italic
text
BEA_HOME
OR
A set of choices in a syntax line.
[ ]
Optional items in a syntax line. Example:
B
{ }
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}
xiv
WebLogic Tuxedo Connector Administration Guide
Convention
Usage
...
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
ET
A
Indicates the omission of items from a code example or from a syntax line.
B
.
.
.
•
WebLogic Tuxedo Connector Administration Guide
xv
B
ET
A
About This Do cume nt
xvi
WebLogic Tuxedo Connector Administration Guide
CHAPTER
1
A
Introduction to WebLogic Tuxedo
Connector
The following sections summarize the concepts and functionality of WebLogic Tuxedo
Connector for this release of WebLogic Server:
WebLogic Tuxedo Connector Overview
z
Key Functionality and Administrative Features
z
Known Limitations
z
How WebLogic Tuxedo Connector Differs from Jolt
z
Platform Support
z
Licensing
z
Upgrading WebLogic Tuxedo Connector 6.x Applications
z
Upgrading WebLogic Tuxedo Connector 7.0 Applications
B
ET
z
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.
WebLogic Tuxedo Connector Administration Guide
1-1
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:
Ability to call WebLogic Server applications from Tuxedo applications and vice versa.
z
Ability to integrate WebLogic Server applications into existing Tuxedo environments.
z
Transaction support.
z
Ability to provide interoperability between CORBA Java and CORBA C++ server
applications.
z
Ability to provide interoperability between Remote Method Invocation (RMI) over Internet
Inter-ORB Protocol (IIOP) applications and Tuxedo CORBA remote objects.
z
Ability to use WebLogic Integration to manage workflow across Tuxedo ATMI services.
z
Ability to define multiple connections between WebLogic Server and Tuxedo.
ET
A
z
The WebLogic Tuxedo Connector includes the following key administration features:
z
Simple implementation. The WebLogic Tuxedo Connector does not require modification of
existing Tuxedo application code.
B
– 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.
z
Bi-directional security propagation, including domain and ACL security.
z
Domain-level failover and fallback.
z
Advanced messaging services provided by Tuxedo /Q and JMS.
z
Interoperability with mainframes and other legacy applications using eLink.
Known Limitations
WebLogic Tuxedo Connector has the following limitations:
1-2
WebLogic Tuxedo Connector Administration Guide
How WebL ogi c Tuxedo Conne cto r Differs from Jolt
z
Does 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.
Does not support inbound TGIOP in clustered environments.
z
Does not support Tuxedo 8.1 multibyte string data typed buffer named MBSTRING for
transport of multibyte character user data.
z
Does not support Tuxedo 8.1 Domains keepalive functionality.
z
WebLogic Tuxedo Connector does not support Tuxedo 6.5 running on VMS and OS/390
platforms.
A
z
How WebLogic Tuxedo Connector Differs from Jolt
ET
The WebLogic Tuxedo Connector is not a replacement for Jolt. WebLogic Tuxedo Connector
differs from Jolt in the following ways:
z
WebLogic Tuxedo Connector offers a similar but different API than Jolt.
z
Jolt enables the development of generic Java clients and other Web server applications that
the WebLogic Tuxedo Connector does not.
z
Jolt does not provide a mechanism for an integrated WebLogic Server-Tuxedo transaction.
B
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.
WebLogic Tuxedo Connector Administration Guide
1-3
This section provides licensing information for the WebLogic Tuxedo Connector:
z
There is no license requirement for using the connector without encryption.
z
An 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.
A
Upgrading WebLogic Tuxedo Connector 7.0 Applications
B
ET
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.
1-4
WebLogic Tuxedo Connector Administration Guide
CHAPTER
2
A
Configuring WebLogic Tuxedo
Connector
The following sections describe how to configure the WebLogic Tuxedo Connector.
Summary of Environment Changes and Considerations
z
Configuring WebLogic Tuxedo Connector for Your Applications
ET
z
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.
B
Tuxedo Changes
Note: For more information on Tuxedo domains, see the BEA TUXEDO Domains Guide.
Tuxedo users need to make the following environment changes:
z
If 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.
z
If 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.
z
WebLogic 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.
WebLogic Tuxedo Connector Administration Guide
2-1
WebLogic Server Changes
The following sections describe WebLogic Server changes required to use the WebLogic Tuxedo
Connector:
z
Administration and Programming
z
WebLogic Server Threads
Administration and Programming
WebLogic Server users need to make the following environment changes:
Create Java clients or servers. For more information on creating WebLogic Tuxedo
Connector clients or servers, see the WebLogic Tuxedo Connector Programmer’s Guide.
z
Configure 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.
z
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 must
be authenticated as a local WebLogic Server user. For more information, see “User
Authentication” on page 3-9.
ET
A
z
WebLogic Server Threads
B
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
2-2
WebLogic Tuxedo Connector Administration Guide
C o n fi g u ri n g Web L o gi c T u xe do C onnector for Your Applic ations
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.
WebLogic Tuxedo Connector MBean Classes
z
Configuring WebLogic Tuxedo Connector Using the Administration Console
z
Configuring WebLogic Tuxedo Connector Using the Command-Line Interface
z
Set the WebLogic Server Environment
z
How to Set WebLogic Tuxedo Connector Properties
z
WebLogic Tuxedo Connector Configuration Guidelines
A
z
WebLogic Tuxedo Connector MBean Classes
ET
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.
B
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:
WebLogic Tuxedo Connector Administration Guide
2-3
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.
WTCPassword
ET
WTCResources
Provides information on services imported and available on
remote domains. Defines your Imported Services when
configured using the Administration Console.
Specifies global field table classes, view table classes, and
application passwords for domains. Defines your Resources
when configured using the Administration Console.
B
WTCImport
A
MBean Type
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
2-4
WebLogic Tuxedo Connector Administration Guide
C o n fi g u ri n g Web L o gi c T u xe do C onnector for Your Applic ations
MBean Type
Description
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.
A
Configuring WebLogic Tuxedo Connector Using the
Administration Console
ET
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.
B
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.
Table 2-1 WebLogic Tuxedo Connector Configuration Tasks
Task #
Task
Description
1
Creating a WTC
Service
On the General tab in the right pane, you set the attributes
for Name and Deployment Order.
2
Creating 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.
WebLogic Tuxedo Connector Administration Guide
2-5
Table 2-1 WebLogic Tuxedo Connector Configuration Tasks
Task
Description
3
Creating a Remote
Tuxedo Access Point
Set the attributes that describe your remote Tuxedo
domains in the Local APs tab.
4
Creating Exported
Services
Set the attributes that describe your exported WebLogic
Server services in the Exported tab.
5
Creating Imported
Services
Set the attributes that describe your imported Tuxedo
services in the Imported tab.
6
Creating a Password
Configuration
Set the attributes that describe your passwords in the
Password tab.
7
Creating a Resource
Set the attributes that describe your WebLogic Tuxedo
Connector resources in the Resources tab.
8
Creating a Tuxedo
Queuing Bridge
Connection
Set the global configuration information for the transfer of
messages between WebLogic Server and Tuxedo.
9
Creating a tBridge
Redirection
10
Assign a WTC
Service to a Server
ET
A
Task #
Sets the attributes used to specify the source, target,
direction, and transport of a message between WebLogic
Server and Tuxedo
B
Select a target server for your WTC Service.
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.
2-6
WebLogic Tuxedo Connector Administration Guide
C o n fi g u ri n g Web L o gi c T u xe do C onnector for Your Applic ations
- 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
A
- UNIX users: edit setExamplesEnv.sh
3. Save the file.
ET
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
B
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:
WebLogic Tuxedo Connector Administration Guide
2-7
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.
A
To enable character set translation, update the JAVA_OPTIONS variable in your server start
script. Example:
JAVA_OPTIONS=-Dweblogic.wtc.encoding=codesetname
ET
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:
The Supported Encoding list includes EUC_JP
z
The remote domain is supported by a Solaris operating system using eucJP
B
z
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:
2-8
z
You must have at least one local Tuxedo access point in your configuration.
z
You may have more than one WTC Service in your configuration.
WebLogic Tuxedo Connector Administration Guide
C o n fi g u ri n g Web L o gi c T u xe do C onnector for Your Applic ations
You can not target 2 or more WTC Services to the same server. A server can only be a
target for one WTC Service.
z
Any 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.
B
ET
A
z
WebLogic Tuxedo Connector Administration Guide
2-9
A
ET
B
2-10
WebLogic Tuxedo Connector Administration Guide
CHAPTER
3
A
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.
ET
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:
Configuring the Connections Between Access Points
z
How ConnectionPolicy Affects Dynamic Status
z
Configuring Failover and Failback
z
Authentication of Remote Access Points
z
User Authentication
z
How to Configure WebLogic Tuxedo Connector to Provide Security between Tuxedo and
WebLogic Server
z
Link-Level Encryption
B
z
WebLogic Tuxedo Connector Administration Guide
3-1
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:
How to Request a Connection at Boot Time (On Startup)
z
How to Request Connections for Client Demands (On Demand)
z
Accepting Incoming Connections (Incoming Only)
z
How to use LOCAL Connection Policy
A
z
ET
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)
B
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.
3-2
WebLogic Tuxedo Connector Administration Guide
Configuring the Conne cti ons Betwee n Acc ess Poi nts
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.
z
If 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.
z
If you set MaxRetries to a number, the access point tries to establish a connection the
specified number of times before quitting.
z
If you set MaxRetries to 2147483647, retry processing is repeated indefinitely or until a
connection is established.
Table 3-1 Example Settings of MaxRetries and RetryInterval Parameters
Then ...
ConnectionPolicy: On Startup
RetryInterval: 30
ConnectionPolicy: On Startup
MaxRetries: 0
ConnectionPolicy: On Startup
The access point attempts to establish a
connection at initialization time but
does not retry if the first attempt fails.
The access point attempts to establish a
connection every 30 seconds until a
connection is established.
B
RetryInterval: 30
The access point makes 3 attempts to
establish a connection, at 30 seconds
intervals, before quitting.
ET
MaxRetries: 3
A
If you set ...
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
WebLogic Tuxedo Connector Administration Guide
3-3
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
0n Demand
Dynamic Status is off. Services imported from remote access
points are always advertised.
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.
B
Incoming Only
Dynamic Status is on. Services imported from a remote
access point are advertised while a connection to that remote
access point exists.
ET
On Startup
A
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
3-4
WebLogic Tuxedo Connector Administration Guide
Conf ig ur in g F ail ove r and Fail back
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.
How to Configure Failover
A
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.
ET
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:
z
Create Remote Tuxedo Access Points configurations for each remote access point.
z
Create Imported Services configurations that specify the service provided by each remote
access point.
B
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:
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
WebLogic Tuxedo Connector Administration Guide
3-7
Local Password IV: my_passwordIV
where
z
Cut and paste the string of characters represented by my_password into the Password field.
z
Cut 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
A
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=
ET
Local Password IV : NAGikshMiTE=
Your Password attributes are:
Local Password: FMTCg5Vi1mTGFds1U4GKIQQj7s2uTlg/ldBfy6Kb+yY=
Local Password IV: NAGikshMiTE=
B
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.
3-8
WebLogic Tuxedo Connector Administration Guide
Us er Authenti catio n
$ 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
A
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.
z
LOCAL
z
GLOBAL
ET
The valid values for AclPolicy and CredentialPolicy are:
ACL Policy is LOCAL
B
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.
WebLogic Tuxedo Connector Administration Guide
3-9
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.
A
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.
ET
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.
B
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:
3-10
z
TpUsrFile Plug-in
z
LDAP Plug-in
z
Custom Plug-in
z
Anonymous Users
WebLogic Tuxedo Connector Administration Guide
How to Configure Web Logic Tuxe do Connector to Provide Security betwe en Tu xe do an d W eb Log ic S er ver
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:
z
Configuring the Local Tuxedo Access Point for the TpUsrFile Plug-in
z
Configure the Remote Tuxedo Access Point for the TpUsrFile Plug-in
Configuring the Local Tuxedo Access Point for the TpUsrFile Plug-in
A
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
ET
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.
B
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.
WebLogic Tuxedo Connector Administration Guide
3-11
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:
All TpUsrFile attribute values are ignored if the TpUsrFile Plug-in is not selected as the
AppKey Generator, regardless of location.
z
If 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.
z
If 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.
z
If 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
ET
A
z
B
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:
z
Implementing Single Point Security Administration
z
Configure the Local Tuxedo Access Point for the LDAP Plug-in
z
Configure 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
3-12
WebLogic Tuxedo Connector Administration Guide
How to Configure Web Logic Tuxe do Connector to Provide Security betwe en Tu xe do an d W eb Log ic S er ver
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.
1. Set the AclPolicy attribute to GLOBAL.
A
Perform the following steps to prepare the WebLogic Server environment:
2. Set the CredentialPolicy attribute to GLOBAL.
ET
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.
B
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:
z
Configure the Local Tuxedo Access Point for the Custom Plug-in
z
Configure the Remote Tuxedo Access Point for the Custom Plug-in
WebLogic Tuxedo Connector Administration Guide
3-13
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.
A
2. Set the CredentialPolicy attribute to GLOBAL.
ET
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.
B
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.
3-14
WebLogic Tuxedo Connector Administration Guide
L ink -L eve l Encryptio n
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
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:
z
Add to the Tuxedo tpusr file.
z
Define anonymous as a user in the WebLogic Authentication provider. You do this by
setting the following argument when starting a WebLogic Server instance:
Link-Level Encryption
A
-Dweblogic.security.anonymousUserName=anonymous
ET
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.
B
Note: Encryption requires appropriate licensing. For more information on license
requirements, see “Licensing” on page 1-3.
WebLogic Tuxedo Connector Administration Guide
3-15
A
ET
B
3-16
WebLogic Tuxedo Connector Administration Guide
CHAPTER
4
A
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.
ET
The following sections provide information on how to administer and configure the WebLogic
Tuxedo Connector to support Tuxedo CORBA clients and services.
z
How to Configure WebLogic Tuxedo Connector for CORBA Service Applications
z
How to Administer and Configure WebLogic Tuxedo Connector for Inbound RMI-IIOP
z
How to Configure WebLogic Tuxedo Connector for Outbound RMI-IIOP
B
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.
WebLogic Tuxedo Connector Administration Guide
4-1
z
Set 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 //.
z
Set Local Access Point to the value of the Local Access Point attribute of your
Remote Tuxedo Access Point.
z
Set 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.
A
Example WTC Service and Tuxedo UBB Files
ET
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
B
:2468
2. Register WebLogic Server (WLS) Naming Service in the Tuxedo domain’s CosNaming
namespace by entering the following command:
where
ET
cnsbind -o ior.txt your_bind_name
your_bind_name is the CosNaming service object name from your Tuxedo
application.
B
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.
WebLogic Tuxedo Connector Administration Guide
4-5
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
TDOM2 TYPE=TDOMAIN
*DM_TDOMAIN
ET
DOMAINID="TDOM2"
A
*DM_REMOTE_DOMAINS
TDOM1 NWADDR="//123.123.123.123:1234"
TDOM2 NWADDR="//234.234.234.234:5678"
"//myServer"
where
B
*DM_REMOTE_SERVICES
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.
z
4-6
The 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.
WebLogic Tuxedo Connector Administration Guide
How to Configure WebLog ic Tuxe do Connector for Outbound RMI-II OP
z
If you require muliple servers, the server names must be unique in the first 13 charactcers.
z
You 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.
1. Configure a Local Tuxedo Access Point.
A
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:
2. Configure Remote Tuxedo Access Point. Outbound RMI-IIOP requires two additional
elements: Federation URL and Federation Name.
Set 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.
z
Set Federation Name to the symbolic name of the federation point.
ET
z
3. Configure Imported Services.
Set 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 //.
z
Set Local Access Point to the value of the Local Access Point attribute of your
Remote Tuxedo Access Point.
z
Set Remote Access Point List to the value of the Access Point Id attribute of
your Remote Tuxedo Access Point.
B
z
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.
WebLogic Tuxedo Connector Administration Guide
4-7
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
.
.
.
WebLogic Tuxedo Connector Administration Guide
CHAPTER
5
A
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.
ET
The following sections provide information on how to administer and configure the WebLogic
Tuxedo Connector for use in a clustered environment:
z
WebLogic Tuxedo Connector Guidelines for Clustered Environments
z
How to Configure OutBound Requests to Tuxedo Domains
z
How to Configure Inbound Requests from Tuxedo Domains
B
WebLogic Tuxedo Connector Guidelines for Clustered
Environments
Use the following guidelines when deploying WebLogic Tuxedo Connector in a clustered
environment:
z
Because 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.
WebLogic Tuxedo Connector Administration Guide
5-1
z
The 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.
z
WebLogic 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.
A
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
ET
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
B
5-2
WebLogic Tuxedo Connector Administration Guide
How to Configure OutBound Re quests to T uxedo Do mains
ET
A
B
A
How to Configure Inbound Requests from Tuxedo Domains
Load Balancing
ET
Load balancing and failover of inbound requests from Tuxedo depend on the Tuxedo domain
DMCONFIG configuration.
Note: For more information on Tuxedo Load Balancing
http://e-docs.bea.com/tuxedo/tux81/int/intatm.htm#1119040.
*DM_IMPORT
B
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.
TOUPPER LDOM=tuxedo_dom RDOM=WDOM1 LOAD=50
TOUPPER LDOM=tuxedo_dom RDOM=WDOM2 LOAD=50
TOUPPER LDOM=tuxedo_dom RDOM=WDOM3 LOAD=50
5-4
WebLogic Tuxedo Connector Administration Guide
H o w to C o nf i g ur e I nb o u nd R e q ue s ts fr o m T ux e d o D o m ai n s
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
B
ET
A
TOUPPER LDOM=tuxedo_dom RDOM=WDOM3,WDOM1,WDOM2 LOAD=50
WebLogic Tuxedo Connector Administration Guide
5-5
A
ET
B
5-6
WebLogic Tuxedo Connector Administration Guide
CHAPTER
6
A
How to Configure the Tuxedo Queuing
Bridge
The following sections provide information on the Tuxedo Queuing Bridge functionality and
configuration.
Overview of the Tuxedo Queuing Bridge
z
Configuring the Tuxedo Queuing Bridge
z
Tuxedo Queuing Bridge Connectivity
z
Example Connection Type Configurations
z
Priority Mapping
z
Error Queues
B
ET
z
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.
WebLogic Tuxedo Connector Administration Guide
6-1
ET
A
Figure 6-1 Interaction between WebLogic Server and Tuxedo with the Queing Bridge
The following features determine the functionality of the Tuxedo Queuing Bridge:
Connectivity is determined by the configuration of the attributes in theTuxedo Queuing
Bridge and Redirections of your WTC Service.
z
The Tuxedo Queuing Bridge uses Java Messaging Service (JMS) to provide an interface to
a Tuxedo /Q or a Tuxedo service.
z
The Tuxedo Queuing Bridge provides simple translation between XML and FML32 to
provide connectivity to existing Tuxedo systems.
B
z
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.
6-2
WebLogic Tuxedo Connector Administration Guide
Overvi ew o f the T uxedo Queui ng Bridge
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.
BytesMessage, TextMessage, XML are converted respectively to TypedCArray,
TypedString, and TypedFML32. XML/FML translation is performed according to the
TranslateFML attribute.
z
Translation errors are sent to the wlsServerErrorDestination queue and the message is
acknowledged in the JMS session.
z
If 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.
A
z
ET
4. The converted message is sent to Tuxedo using the T/Domain gateway.
z
Messages with a redirect set to JmsQ2TuxQ use JATMI tpenqueue to deliver the message
to a Tuxedo queue.
z
Messages with a redirect set to JmsQ2TuxS use JATMI tpcall to deliver the message to a
Tuxedo service.
z
B
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.
If 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.
WebLogic Tuxedo Connector Administration Guide
6-3
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.
z
If 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.
z
If 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.
z
If the tuxErrorDestination queue is not specified, the message is lost.
A
Tuxedo Queuing Bridge Limitations
The Tuxedo Queuing Bridge has the following limitations:
Transactions are not used when retrieving messages from the JMS location and placing
them on the Tuxedo queue or invoking a Tuxedo service.
z
Tuxedo 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.
z
The 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.
B
ET
z
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.
6-4
WebLogic Tuxedo Connector Administration Guide
T uxedo Queuing Bridge Co nnectivi ty
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.
z
A
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:
JmsQ2TuxQ: Reads from a given JMS queue and transports the messages to the specified
ET
Tuxedo /Q.
z
TuxQ2JmsQ: Reads from a Tuxedo /Q and transports the messages to JMS.
z
JmsQ2TuxS: 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
B
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.
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.
A
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.
A WebLogic Tuxedo Connector session is started when a configured WTC Service is
assigned to a selected server.
z
A WebLogic Tuxedo Connector session is ended by removing a WTC Service from the
WebLogic server or when you shutdown the WebLogic server.
ET
z
B
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:
<180101>
WebLogic Tuxedo Connector Administration Guide
8-3
How do I Resolve Connection Problems?
I'm having trouble getting a connection established between WebLogic Tuxedo Connector and
Tuxedo. What should I do?
Make sure you have started your Tuxedo server.
z
Set the TraceLevel and enable Debug mode. Repeat the connectivity test and check the
WebLogic Tuxedo Connector and Tuxedo log files for error messages.
z
Avoid using machine names or localhost. Always use an IP address when specifying a
network location.
z
Check 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.
z
If 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.
z
Check 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.
ET
A
z
z
B
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.
Request 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.
8-4
WebLogic Tuxedo Connector Administration Guide
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.4 Linearized : Yes Page Count : 78 Page Mode : UseOutlines XMP Toolkit : XMP toolkit 2.9.1-13, framework 1.6 About : uuid:be1088b2-7b45-462e-8f3c-b61aba6737cb Producer : Acrobat Distiller 6.0 (Windows) Creator Tool : FrameMaker 6.0 Modify Date : 2004:12:14 07:53:21Z Create Date : 2004:12:14 07:53:16Z Document ID : uuid:2c9b581f-61bc-421d-989a-4085ebf7688d Format : application/pdf Title : wtc_admin.book Creator : webadmin Author : webadminEXIF Metadata provided by EXIF.tools