Basic tBridge configuration

Question

Hi,
I need some help in configuring tBridge. we have WLS 8.1 in one machine and Tuxedo 8.1 server in other machine. We connect to Tuxido server from Weblogic through Jolt connection. We are planning to use tBridge with WTC for one of our requirements. Basically We want to pass messages from Tuxedo Q to JMS Q through tBridge(TuxQt2JmsQ) asynchronosly.
My first query is can we use WTC and JOLT connector both from the same Weblogic server to connect to Tuxedo?.
When I was trying config WTC from WLS Admin console it is asking for Local access point and Remote accee point where my remote accee point is Tuxedo listener port that I use for our jolt connection?? and My Local access point is t3://localhost:8001 ??. When I check at Tuxedo server side I can not fint any DMCONFIG or BDMCONFIG files(those are the main confiruble files I assume), where should I look for thease files exactly?
Any help would be greatly appriciated.
Thanks in advance
Madhav

Answer 1

Hi Madhav,
You can use WTC and Jolt at the same time, although they will obviously be different connections. Jolt clients connect to the JSL, whereas WTC connects to the Tuxedo Domain Gateway. So to use tBridge (a component of WTC) you will need to configure a domain gateware on your Tuxedo system. As well you will need to configure WTC. For detailed information on WTC and the meaning local local access points, etc., please consult the WLS and Tuxedo documentation. In particular, read a bit about setting up domains in the Tuxedo documentation to get some background.
If you want to try a canned set up to see how domains communication and WTC is configured, you could try the Tuxedo Control Jumpstart Kit located at:
http://dev2dev.bea.com/pub/a/2004/02/tuxedo_jumpstart.html
I believe it has some ant scripts that will automatically configure your WTC configuration and a simple Tuxedo application, at least on a single machine. You can then use that as a model for setting up your real environment.
Briefly, a domain in Tuxedo terms can have local access points and remote access points. A local access point basically describes a listening point. A given Tuxedo application can have multiple local access points, although only one is required. Remote access points then describe the remote Tuxedo domain this domain should connect to. So the simplest case is on your Tuxedo system:
Local Access Point: TUXDOM
Local Access Point ID: TUXDOM (it doesn't have to be the same, just for convenience)
Local Access Point Network address: //tuxhost:6010
Remote Access Point: WLSDOM
Remote Access Point ID: WLSDOM
Remote Access Point Network address: //wlshost:6030
And then basically the reverse on the WLS system in the WTC configuration:
Local Access Point: WLSDOM
Local Access Point ID: WLSDOM
Local Access Point Network address: //wlshost:6030
Remote Access Point: TUXDOM
Remote Acess Point ID: TUXDOM
Remote Access Point Network address: //tuxhost:6010
That's just a start, but it should get you going.
Regards,
Todd Little
BEA Tuxedo Engineering