Tuxedo Configuration with WebLogic Connect by WTC
(Author: Xu Chun Kim)
BEA's Tuxedo, WebLogic as the best middleware products, widely used in banks, telecommunications, finance and other industries, usually using Tuxedo's core business, using WebLogic to extend to the Internet platform, realize e-commerce, by WebLogic calls the service on Tuxedo, so the interconnection between Tuxedo and WebLogic is often encountered.
The following is a configuration method for connecting Tuxedo and WebLogic through the WTC by an example.
WebLogic and Tuxedo interconnects have two mode, through jolt or through the WTC (WebLogic Tuxedo Connector). They are BEA products, WTC not only makes WebLogic call service in Tuxedo, but also allows Tuxedo to call EJB in WebLogic; and Jolt can only call Tuxedo. But Jolt can make Tuxedo and Webspere and other applications
The server is connected, while the WTC can only be used between WebLogic and Tuxedo.
First, WTC description
(1) WebLoigic5.1 cannot be connected to the Tuxedo via the WTC.
(2) WebLogic 6.0 When connecting to Tuxedo, install the WTC package.
(3) The WTC is integrated in eblogic 6.1, as long as you configure it, you can install the WTC package separately.
(4) The current WTC only supports two versions of Tuxedo6.5, Tuxedo8.0, and does not support Tuxedo7.1.
(5) There are two versions of the WTC, and the Windows version supports 2000 / NT, UNIX is a unified version.
(6) WTC can be downloaded from http://commerce.bea.com/downloads/tuxedo.jsp, current version is 1.0.
Second, the WTC installation process
(1) WebLogic and Tuxedo must be installed first.
(2) WTC requires installation in a Java environment, can run under command line, config / example / setENV.SH (NT / 2000 under STENV.CMD) to configure the Java environment under the command line.
(3) Perform the installer WTC_10_Win.exe on the DOS command line. You can follow the prompt operation.
Note: If you install it under Window, it will not be executed when you go to a COPY file, but prompts to install success, actually fake. So install it in the DOS command.
Third, WTC configuration instructions
Tuxedo and WebLogic are mutually called by Domain, in which two Domain: Tuxedo's Domain is named TDOM1, the domain name where WebLogic is located is TDOM2. TDOM1 has TouPper it is a Tuxedo Serveice, TDOM2 has TOLOWER it is an EJB,
The following is the configuration process: SIMPAPP (under Examples / WTC / ATMI / SIMPAPP of the WTC Installation Directory) in the WTC installation:
TUXEO version: tuxedo65
WebLogic version: WebLogic6.0
TUXEO installation directory: D: / tuxedo65
WebLogic installation directory: D: / WebLogic
Operating system: Win2000
Example Directory: D: / SimPApp (EXAMPLES / WTC / ATMI / SIMPAPPAPP) for WTC Installation Directory Copy to D: / SimPApp)
Server name: DEMOSERVER
WTC installation directory: d: /weblogic/wtc1.0
Fourth, Tuxedo must do
(1) Modify d: /simpapp/setenv.cmd as:
Set tuxdir = d: / tuxedo65
Set wsnaddr = // DemoServer: 8888
SET AppDir = D: / SimPApp
Set path =% tuxdir% / bin;% appdir%;% PATH%
SET TUXCONFIG =% AppDir% / Tuxconfig
Set bdmconfig =% AppDir% / DBMConfig
(2) Modify D: / SimPApp / ubbdomain as:
* Resources
IPCKey 123456
Domainid Simpapp
Master SIMPLE
Maxaccessers 10
MaxServers 5
MaxServices 10
Model SHM
LDBAL N
* Machines
DemoServer Lmid = Simple
Appdir = "d: / simpapp"
Tuxconfig = "d: / simpApp / tuxconfig"
Tuxdir = "d: / tuxedo65"
* Groups
Group1
Lmid = Simple Grpno = 1 openInfo = NONE
* Servers
DEFAULT:
Clopt = "- a"
SIMPSERV SRVGRP = Group1 SRVID = 1
* SERVICES
TouPper
(3) Modify D: / SimPApp / Dom1config:
Modify DOM1CONFIG, add TLOG path and AuditLog's path. Then modify the NWADDR = "IP: port" of TDOM1 for tuxedo's IP and port, TDOM2
NWADDR = "IP: port" is WebLogic IP and port.
* DM_RESOURCES
Version = U22
* DM_LOCAL_DOMAINSSSS
TDOM1 GWGRP = group2
Type = TDOMain
DomainId = "TDOM1"
BlockTime = 20
MaxDatalen = 56
MaxRDom = 89
TLOG = "D: / Simpapp / Tlog"
Auditlog = "D: / Simpapp / Auditlog"
* DM_REMOTE_DOMAINS
TDOM2 TYPE = TDOMAIN
DomainID = "TDOM2"
* DM_TDOMAIN
TDOM1 NWADDR = "// DemoServer: 9998"
TDOM2 NWADDR = "// DemoServer: 9999"
* DM_REMOTE_SERVICES
TOLOWER RDOM = "TDOM2"
(4) TMLOADCF -Y Ubbdomain
(5) MLOADCF -Y DOM1CONFIG
(6) BuildServer -O Simpserv -f Simpserv.c -s Toupper
(7) Copy the TOLOWER.C under Examples / WTC / ATMI / SIMPAP / SIMPSERV to D: / SimPApp, and execute buildclinet -v -f tolower.c -o toLower
V. WebLogic's configuration
(1) Modify the WebLogic Directory in Config / Examples / SeexampleSenv.cmd and StartexamplesServer.cmd, add:
D: /weblogic/wtc1.0/lib/jatmi.jar. Perform setxamplesenv.cmd
(2) Modify BDMConfig.xml
Modify: [WTC Installation Directory] /weblogic/wtc/gwt/wtc_config_1_0.dtd (WLS60) Modify the consistency in the NWADDR and Tuxedo in TDOM1 and TDOM2
If t_dm_local_tdomain accesspoint = "t_local_tdomain accesspoint =" t_local_tdomain accesspoint = "t_local_tdomain accesspoint =" t_local_tdomain accesspoint = "TDOM2"> is not needed if tuxeod8.0 is required.
(3) The contents of the modified BDMConfig.xml are as follows:
LocalaccessPoint = "TDOM2"> ResourceName = "TouPper" LocalaccessPoint = "TDOM2" RemoteAccessPointList = "TDOM1"> (4) Execute Java WebLogic.wtc.gwt.wtcvalidatecf bdmconfig.xml to monitor whether XML is correct. (5) Execute the build command under D: / SIMPAPP, then execute the build command at D: /WebLogic/wtc1.0/examples/simpserv. (6) Start Welogic (7) See if wtc_tolower.jar, wtc_toupper.jar is successful (8) Create a WebLogic Startup Class: ClassName is a weblogic.wtc.gwt.wtcstartup parameter is bdmconfig = d: /simpapp/bdmconfig.xml, and set its target to ExampleServer (9) Create a WebLogic SHUTDOWN CLASS: Classname is WebLogic.wtc.gwt.wtcshutdown, and set its target to ExampleServer (10) Restart WebLogic, and pay attention to WebLogic's launch log to see if the Startup Class startup process is successful, failure will report error, no prompt information If the failure does not check if config.xml is 6. Start Tuxedo Seven, operation example Under D: / SimPApp, execute run.cmd, which is WebLogic to do a Client side call TouPper EJB, called Tuxedo's service: TouPper Perform run.cmd under D: / SimPApp, this is Tuxedo to make a Client side calling WebLogic's TOLOWER EJB, Eight, if it is WebLogic 6.1 Tuxedo's configuration is constant WEBLOGIC is configured from (2). Where: DMConfig.xml is not found in WebLogic 6.1, you can copy one to WebLogic 6.1 installation directory from WebLogic 6.1: Such as D: /WebLogic 6.1, specify its path in DMConfig.xml Nine, failure If you fail, you can set the tracking options for WebLogic.wtc.gwt.wtcstartup, that is, set it to: bdmconfig = d: /simpapp/BDMConfig.xml ,tractelevel=20000 And please check the log of WebLogic, Tuxedo. Do the appropriate processing.
