Package examples.wtc.atmi.convsimp

This example demonstrates the ability of WebLogic Tuxedo Connector to allow WebLogic Server to interoperate with Tuxedo using conversations.

See:
Description

Interface Summary

TuxedoConversation	The methods in this interface are the public face of the simpapp client.
TuxedoConversationHome	This interface is the home interface for the TraderBean.java, which in WebLogic is implemented by the code-generated container class TraderBeanC.

Class Summary

Client	This class illustrates calling a stateful SessionBean and performing the following exercises: Create a TuxedoConversation Buy some shares using the TuxedoConversation Sell some shares using the TuxedoConversation Remove the TuxedoConversation
TuxedoConversationBean	ToupperBean is a stateful SessionBean.

Package examples.wtc.atmi.convsimp Description

This example demonstrates the ability of WebLogic Tuxedo Connector to allow WebLogic Server to interoperate with Tuxedo using conversations.

Configure the example

You need to configure Tuxedo and WLS.

Tuxedo configuration

1. Your PATH environment variable needs to include the path of your C compiler. Use set PATH to check the status and add the path if necessary.
2. Create a working Tuxedo convsimp directory.
   Example:
   d:\my_apps\convsimp
3. Copy the following files from the WLS 6.1 examples.wtc.atmi.convsimp package to your working Tuxedo convsimp directory.
   • ubbdomain
   • dom1config
   • convcl.c
   • convsimp.c
4. Change directories to the working Tuxedo convsimp directory
5. Set environment variables. Update the following parameters:
   • TUXDIR - base directory of the TUXEDO Software
   • APPDIR - base directory of the sample program
   • PATH - must include %TUXDIR%\bin
   • TUXCONFIG - full pathname of binary tuxconfig file
   NT/2000 users modify setEnv.cmd located at %TUXDIR%. Unix users modify the tux.env file located at $TUXDIR.

   Build the clients:

   buildclient -o convcl -f convcl.c

   buildserver -o convsimp -f convsimp.c -s CTOUPPER

   Modify the ubbdomain for your Tuxedo environment. This includes setting the pathnames for APPDIR, TUXCONFIG, and TUXDIR and setting the machine name. Replace all <bracked> items with information for your environment.

   Example:

   APPDIR="d:\my_apps\convsimp"

   TUXCONFIG="d:\my_apps\convsimp\tuxconfig""

   TUXDIR="d:\bea\tuxedo"

   Load the ubbdomain file

   Example:

   tmloadcf -y ubbdomain

   Modify the dom1config for your Tuxedo environment. This includes creating log devices and updating the network addresses.

   • Logs

   Example:

   DMTLOGDEV="d:\my_apps\tlog"

   AUDITLOG="d:\my_apps\aud"

   DMTLOGNAME="DMTLOG_TDOM1"

   • NWADDR

   Example:

   TDOM1 NWADDR="//TuxedoMachine:1234"

   TDOM2 NWADDR="//WTCMachine:5678"

   Load the dom1config file

   Example:

   set BDMCONFIG=d:\my_apps\convsimp\bdmconfig

   dmloadcf -y dom1config

   Boot the Tuxedo domain

   tmboot -y

   Verify all processes have started using the tmadmin psc command.The following domain processes should have booted:

   • DMADM, GWADM, and GWTDOMAIN

   • The CTOUPPER service

WLS Configuration

1. Change directories to the WTC convsimp directory
2. Set environment variables. Update the following parameters:
   • Set the APPLICATIONS to the location of the applications directory in your WLS domain
   • Set the CLIENT_CLASSES to build
   NT/2000 users modify and run the setExamplesEnv.cmd. Unix users copy ./config/examples/setExamplesEnv.sh script to your WTC simpapp directory, then modify and run the setExamplesEnv.sh script.

   Build the wtc_tux_Conversations.jar file using ant.

   • Enter the following command: ant

   Modify the bdmconfig.xml file with information specific to your installation:

   • Update the NWAddr attributes of TDOM1 and TDOM2 domains for your environment

   • If you are using a Tuxedo 6.5 service, add Interoperate and set to Yes

   Use the following command to validate the bdmconfig.xml file using the WTCValidateCF utility:

   java weblogic.wtc.gwt.WTCValidateCF bdmconfig.xml

   Change directories to the simpconv directory

   Build the wtc_tux_server_Conversations.jar file using ant.

   • Enter the following command: ant

   Boot your WLS application server

   Check to see that the wtc_tux_Conversations.jar and wtc_tux_server_Conversations.jar are deployed. Use the WLS console or check the config.xml file. Manually deploy the EJBs if needed.

   Configure a WTC StartUp Class. You need to provide a classname and the fully qualified name of the bdmconfig.xml file you are using for the example.

   • Set the classname to: weblogic.wtc.gwt.WTCStartup

   • Set the arguments field to: BDMCONFIG=path_name_of_your_bdmconfig.xml_file

   Configure a WTC ShutDown Class

   • Set the classname to: weblogic.wtc.gwt.WTCShutdown

   Shutdown and restart your WLS application server.

Run the example

Start a WLS client.

1. Change directories to the WLS convsimp directory
2. Start a client
   • For NT/2000, use the following command: run.cmd asdf
   • For Unix, use the following command: run.sh asdf
   Example:

      run asdf

   The Tuxedo service replies to your WLS application with:

      Beginning statefulSession.Client...

      Creating TuxedoConversation

      datasize: 1 iterations: 1

      End statefulSession.Client...

Use TraceLevel

If you have a problem running the simpapp example, use the WTC tracing feature. Add the TraceLevel parameter to the StartUp Class Argument list.

Example:

   BDMCONFIG=path_to_my_bdmconfig.xml_file,TraceLevel=20000

A TraceLevel of 20000 traces all of the calls to the Tuxedo object in the client.

There's more...

You are ready to run the simpconv example.

For more information about WebLogic Server WebLogic Tuxedo Connector, see:

• WebLogic Tuxedo Connector Administration Guide
• WebLogic Tuxedo Connector Programmer's Guide
• WebLogic Tuxedo Connector Examples
• Javadocs for WebLogic Classes - weblogic.wtc.jatmi