Bea Tuxedo development discipline -- DoNet

This middleware, which has been acquired by Oracle, is available in the latest version. However, its development in DoNet is poor, the configuration of the environment also cost me a lot of money.

Because the project needs to be connected to the power recording charging interface, and the Tuxedo for power use is still version 8.1, my development platform here is DoNet. fortunately, the latest Tuxedo version 10 comes with the DoNet ghost library. however, it is not passed in IIS directly referenced in the Web. I don't know why. find another method through some searches...

[Brief introduction to Tuxedo]

TRansactionUNIXHas beenEXtendedDIstributedOPeration: UNIX transaction system extended by distributed operations

Tuxedo was developed in the Bell lab AT & T in 1984, but distributed processing was not as successful as it was today in commercial applications, for a long period of time, Tuxedo was only a laboratory product. later it was acquired by Novell. after the unsuccessful commercial promotion of Novell, it was acquired by BEA in 1995. Although the concept of middleware has been created for a long time, it has been widely used in the past 10 years. BEA became a real Middleware vendor after its acquisition of Tuxedo in 1995. IBM's middleware MQSeries was also a product in 1990s, and many other middleware Products have matured in recent years. Let me briefly introduce tongdong TongLINK and TONGEASY.

BEA Tuxedo is the preferred platform for today's C, C ++ and COBOL solutions. It runs some of the largest key task transaction processing systems, such as wired transmission, ATM, and telecommunications. It is the pillar of many of the world's leading companies.

See: http://soft.zdnet.com.cn/software_zone/2007/1004/535422.shtml

[Download & Install]

Since it was acquired by Oracle, you can go to the Oracle official page to find and download the Tuxedo10.1 client to download for DoNet

<Install the client>

...

<Environment variable>

TUXDIR = <path of Tuxedo software>

APPDIR = <Application Path>

PATH = <must contain PATH % TUXDIR % \ BIN>

TUXCONFIG = <full path of the configuration file tuxconfig>

WSNADDR = <server address, used by the client>

LD_LIBRARY_PATH = % LD_LIBRARY_PATH %; % TUXDIR % \ LIB

In actual development, I didn't use all the variables. But you must understand them.

[DoNet Development]

As mentioned above, Tuxedo10.1 now comes with the DoNet repository --Libwd8net. dll.
However, this does not mean that you can use it directly, because the slave database requires other call libraries, and other call libraries are not the DoNet slave database and cannot be referenced.

Set<TUX installation directory> \ binCopy all *. dll files to the reference directory under the project (the Web is the bin directory, and CS is the program directory ).<TUX installation directory> \ libAnd<TUX installation directory> \ localeThese two directories.

Create a new user environment variableTUXDIREnvironment Variables point to our reference directory, system environment variablesPATHAdd % TUXDIR %

C #

// Env = "WSNADDR = // IP: Port ";

// Env = "WSINTOPPRE71 = yes"; // backward compatible

Bea. Tuxedo. ATMI. Utils. tuxputenv (string env); // configure the Parameter

AppContext ac = AppContext. tpinit (null); // initialize the context

TypedBuffer its = new TypedString (string Param); // send
TypedBuffer rts = new TypedString (""); // receives

Ac. tpcall (ServiceName, its, ref rts, 0 );

String Output = (rts as TypedString). GetString ();

Ac. tpterm ();

Let's take a look at this article.

Http://www.cnblogs.com/andyhai/archive/2007/07/12/815536.html