6.5和8.0可以混用吗 - Tuxedo (Chinese)

我想后台用8.0,前台用6.5可以吗?
我自己在sco openserver 5上用tuxedo 6.5做client
winxp上用tuxedo 8.0做server
没有成功啊, tpinit的时候返回9,协议错.
我怎么听说有人能够混用? 

你的client端有应用么?有其他服务还是单纯的workstation client? 是一个domain么? 

没有应用,就是一个纯粹的Client,
这有关系吗? 如果是基于Domain的又有什么不同吗? 

我在tuxedo overview中找到一段:While BEA Tuxedo 8.0 clients or servers cannot interoperate or coexist with BEA Tuxedo 6.3 servers, BEA Tuxedo 6.3 clients can interoperate with BEA Tuxedo 8.0 servers. 

可以应用的.
1.低联高(6.5--->8.0) : 在WSL中加入-t即可
如:CLOPT="-A -t -- -n //vt8000:3345
2.高联低(8.0--->6.5),除了设置环境变量WSNADDR=//host:port外,还应设WSINTOPPRE71 = yes 

测试通过, 谢谢 

6.5Domain和8.0Domain可以通过对等域互联吗?
从8.0调用6.5服务时报GP_CAT:1069和LIBTUX_CAT:322错可能是什么原因?
此文被nepho在2003/10/28 23:02:09修改!

Related

WLS 6.1 and 8.1 on same machine?

Can two different versions of Weblogic (6.1 and 8.1) be installed on the same Unix
machine at the same time? If yes, how?
Thanks,
Krish
"Krish" <krishd#yahoo.com> wrote in message news:3fa9208b$1#newsgroups.bea.com...
Can two different versions of Weblogic (6.1 and 8.1) be installed on the same Unix
machine at the same time? If yes, how?you can have them both on the same machine provided thay point to
different directories for domains deployments.
Regards,
Slava Imeshev

WebServices with WL 6 SP2

Hi
Does Weblogic 6 SP2 support Webservices? Can we tweak the configuration
in any way to get this to work?
Is there any workaround for this situation other than migrating to
Weblogic 6.1?
Thanks
Madhu
Hi Madhusudan,
To my knowledge, "built-in" support for Web Services is only available in WebLogic
Server 6.1, not WebLogic Server 6.0. You can, of course, use other Java-based
SOAP/WSDL/UDDI implementations (i.e. Apache SOAP, GLUE, Idoox WASP, IONA XMLBus,
etc.) with WLS 6.0 or WLS 6.1, but you must use WLS 6.1 to create WebLogic Web
Services. Note that WLS 6.0, like any other Java and non-Java environment, can
be a consumer (or "client", if you prefer that term) of a WLS 6.1 hosted WebLogic
Web Service.
Regards,
Mike Wooten
Madhusudan R Chaganthi <mvc9#cdc.gov> wrote:
Hi
Does Weblogic 6 SP2 support Webservices? Can we tweak the configuration
in any way to get this to work?
Is there any workaround for this situation other than migrating to
Weblogic 6.1?
Thanks
Madhu

How to configure Weblogic Tuxedo Connector ?

Hi:
I have 2 machines. One machine "A" installed with BEA TUXEDO 8.0 software.
The other machine "B" doesn't have BEA TUXEDO 8.0 software but it has BEA WebLogic
Server 6.1
installed.
My desire is to be able to make a successful application using WebLogic Tuxedo
Connector from the machine "B" to machine "A".
I have tried to follow the instruction for the WebLogic Tuxedo Connector example.
However, I wasn't able to make the application work. I am suspecting that
I must have BEA TUXEDO 8.0 software installed into machine "B" in order to make
it work. Am I right or wrong?
Khanh,
You don't need Tuxedo installed on the same machine as WLS to use WTC.
Your problem must be caused by some error in your configuration, either
in the dmconfig on the Tuxedo side, or the xml config on the WTC side.
I think you will need to post more detail to get any further help.
Regards,
Peter.
Khanh Mai wrote:
Hi:
I have 2 machines. One machine "A" installed with BEA TUXEDO 8.0 software.
The other machine "B" doesn't have BEA TUXEDO 8.0 software but it has BEA WebLogic
Server 6.1
installed.
My desire is to be able to make a successful application using WebLogic Tuxedo
Connector from the machine "B" to machine "A".
I have tried to follow the instruction for the WebLogic Tuxedo Connector example.
However, I wasn't able to make the application work. I am suspecting that
I must have BEA TUXEDO 8.0 software installed into machine "B" in order to make
it work. Am I right or wrong?

Thanks BEA!

We have successfully implemented global transactions into WLS 6.1 SP1 and
Oracle 8.1.7 which were started from a mainframe application using eLink for
OSI-TP to Tuxedo 7.1 and WTC. With just a few configuration file entries,
the mainframe application is able to make a transactional call to a WLS EJB
as a remote Tuxedo service.
WLS 6.1 with WTC has made the XA implementation so much cleaner than what we
formerly had to do with WLE 5.1, which was to deploy intermediate Tuxedo
Servers which became CORBA clients calling Java CORBA servers which in turn
called EJBs in WLE.
Thanks for your efforts.
Carl Lawstuen
Unisys
Great news.
By the way, the check is in the mail...
Just kidding ;-)
--
John Wells (Aziz)
john.wells#bea.com
jwells3#home.com
"Carl Lawstuen" <carl.lawstuen#unisys.com> wrote in message
news:3be1b70a$1#newsgroups.bea.com...
We have successfully implemented global transactions into WLS 6.1 SP1 and
Oracle 8.1.7 which were started from a mainframe application using eLinkfor
OSI-TP to Tuxedo 7.1 and WTC. With just a few configuration fileentries,
the mainframe application is able to make a transactional call to a WLSEJB
as a remote Tuxedo service.
WLS 6.1 with WTC has made the XA implementation so much cleaner than whatwe
formerly had to do with WLE 5.1, which was to deploy intermediate Tuxedo
Servers which became CORBA clients calling Java CORBA servers which inturn
called EJBs in WLE.
Thanks for your efforts.
Carl Lawstuen
Unisys

Bad message error (WLS 6.0 - Tuxedo 7.1)

Hi Everyone,
Using WLS 6.0 and Tuxedo 7.1 comunication, I 've got the following error:
LIBGWT:1313
ERROR: Bad message from val. Closing file descriptor
Description
The gateway received a poorly formatted message from the specified remote domain
and is unable to recognize it.
Action
Check the ULOG of the remote domain for further diagnosis.
I am using FML32 buffer type. Everything is working the same way using WLS 6.0
and Tuxedo 6.5.
Any clue
Thanks,
Claudio
Claudio,
Did you install the patch for 7.1, as per the FAQ:
Q8. What versions of Tuxedo are supported?
A8. WTC 1.0 will support Tuxedo 6.5 and Tuxedo 8.0. WTC 1.1 (which
adds
CORBA support) will support Tuxedo 6.5 and Tuxedo 8.0. Soon after the
release of both of these products we will certify WTC with Tuxedo 7.1.
However, the version of Tuxedo 7.1 you will need to have will be Tuxedo
7.1
after RP 89.
     Scott Orshan
     BEA Systems
Claudio Lazo wrote:
>
Hi Everyone,
Using WLS 6.0 and Tuxedo 7.1 comunication, I 've got the following error:
LIBGWT:1313
ERROR: Bad message from val. Closing file descriptor
Description
The gateway received a poorly formatted message from the specified remote domain
and is unable to recognize it.
Action
Check the ULOG of the remote domain for further diagnosis.
I am using FML32 buffer type. Everything is working the same way using WLS 6.0
and Tuxedo 6.5.
Any clue
Thanks,
Claudio
Scott Orshan <sdo#bea.com> wrote:
Claudio,
Did you install the patch for 7.1, as per the FAQ:
Q8. What versions of Tuxedo are supported?
A8. WTC 1.0 will support Tuxedo 6.5 and Tuxedo 8.0. WTC 1.1 (which
adds
CORBA support) will support Tuxedo 6.5 and Tuxedo 8.0. Soon after the
release of both of these products we will certify WTC with Tuxedo 7.1.
However, the version of Tuxedo 7.1 you will need to have will be Tuxedo
7.1
after RP 89.Thanks.
We moved the tuxedo service to Tuxedo 8 running on the same machine where WTC
and WLS60 is.
Can this tux-wtc domain live in the same machine? (Solaris 8). It works with
SIMPAPP on Linux Tuxedo 6.5 WLS 6.0.
Thank you
Claudio
Claudio Lazo wrote:
Hi Everyone,
Using WLS 6.0 and Tuxedo 7.1 comunication, I 've got the followingerror:
LIBGWT:1313
ERROR: Bad message from val. Closing file descriptor
Description
The gateway received a poorly formatted message from the specifiedremote domain
and is unable to recognize it.
Action
Check the ULOG of the remote domain for further diagnosis.
I am using FML32 buffer type. Everything is working the same way usingWLS 6.0
and Tuxedo 6.5.
Any clue
Thanks,
Claudio
Yes, the WLS and Tuxedo processes can run on the same machine. As Scott
pointed out, Tuxedo 7.1 must be post rolling patch 89. Other than that (and
making sure that loopback mode of your machine works properly (try telnet to
127.0.0.1)) everything should work properly.
Is WTC getting connected to the GWTDOMAIN process properly? Can you send us
the logs from both WLS and Tuxedo? That would help us to diagnose the
problem...
--
John Wells (Aziz)
john.wells#bea.com
jwells3#home.com
"Claudio Lazo" <clazo#omegacl.cl> wrote in message
news:3bafa858$1#newsgroups.bea.com...
>
Scott Orshan <sdo#bea.com> wrote:
Claudio,
Did you install the patch for 7.1, as per the FAQ:
Q8. What versions of Tuxedo are supported?
A8. WTC 1.0 will support Tuxedo 6.5 and Tuxedo 8.0. WTC 1.1 (which
adds
CORBA support) will support Tuxedo 6.5 and Tuxedo 8.0. Soon after the
release of both of these products we will certify WTC with Tuxedo 7.1.
However, the version of Tuxedo 7.1 you will need to have will be Tuxedo
7.1
after RP 89.Thanks.
We moved the tuxedo service to Tuxedo 8 running on the same machine whereWTC
and WLS60 is.
Can this tux-wtc domain live in the same machine? (Solaris 8). It workswith
SIMPAPP on Linux Tuxedo 6.5 WLS 6.0.
Thank you
Claudio
Claudio Lazo wrote:
Hi Everyone,
Using WLS 6.0 and Tuxedo 7.1 comunication, I 've got the followingerror:
LIBGWT:1313
ERROR: Bad message from val. Closing file descriptor
Description
The gateway received a poorly formatted message from the specifiedremote domain
and is unable to recognize it.
Action
Check the ULOG of the remote domain for further diagnosis.
I am using FML32 buffer type. Everything is working the same way usingWLS 6.0
and Tuxedo 6.5.
Any clue
Thanks,
Claudio

Categories

Resources