WebLogic Server 7.0 Code Examples, BEA Systems, Inc.

Package examples.wtc.atmi.simpFML32

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

See:
          Description

Interface Summary
Rstring The methods in this interface are the public face of the simpapp client.
RstringHome 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 Rstring Buy some shares using the Rstring Sell some shares using the Rstring Remove the Rstring
MyFieldTable  
RstringBean RstringBean is a stateful SessionBean.
 

Package examples.wtc.atmi.simpFML32 Description

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

The Tuxedo simpFML32 application is extended to run over domains. This allows WebLogic Server clients using FML32 buffers to reference the Tuxedo REVERSE_STRING service.   This example consists of a Tuxedo service, simpFML32 that export the service REVERSE_STRING, that expects and returns a FML32 string, in reverse order.  A WebLogic Server client invokes the REVERSE_STRING EJB that connects to the Tuxedo service to perform the operation and return the results.

Configure the simpFML32 example:

You need to configure Tuxedo and WebLogic Server.

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. Copy the simpFML32.c example to your Tuxedo installation and create a working Tuxedo simpFML32 directory
  3. Change directories to the working Tuxedo simpFML32 directory
  4. Set environment variables. Update the following parameters:
  5. NT/2000 users modify setEnv.cmd located at %TUXDIR%. Unix users modify the tux.env file located at $TUXDIR.
  6. Build the simpFML32 server:
  7. Copy the ubbdomain and dom1config files from the WebLogic Tuxedo Connector simpFML32 directory to your Tuxedo simpFML32 directory
  8. 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.
  9. Modify the dom1config for your Tuxedo environment. This includes creating log devices and updating the network addresses.
  10. Load the ubbdomain file
  11. Load the dom1config file
  12. Boot the Tuxedo domain
  13. Verify all processes have started using the tmadmin psc command.The following domain processes should have booted:

WebLogic Server Configuration

  1. Boot your WebLogic Examples Server
  2. Change directories to the WebLogic Tuxedo Connector examples simpFML32 directory
  3. Set environment variables. Update the following parameters:
  4. NT/2000 users modify and run the setExamplesEnv.cmd. Unix users copy ./config/examples/setExamplesEnv.sh script to your WTC qsample directory, then modify and run the setExamplesEnv.sh script.
  5. Build the wtc_rstring.jar file using ant.
  6. Modify the setWTCMbeans file with information specific to your installation.
  7. Run the setWTCMbeans file to configure your installation.
  8. Shutdown and restart your WebLogic Server application server.
  9. Check to see that the wtc_rstring.jar is deployed. Use the WLS console or check the config.xml file. Manually deploy the EJB if needed.

Run the example

Start a WebLogic Server client to invoke the Rstring EJB and connect to the Tuxedo REVERSE_STRING service.
  1. Change directories to the WebLogic Server simpFML32 directory
  2. Start a client
  3. Example:
       run abcdef
    The Tuxedo service replies to your WebLogic Server application with:
       Returned string is: fedcba

  4. Untarget the WTCsimpfml Mbean from the examplesServer.

Use TraceLevel

If you have a problem running the simpapp example, use the WebLogic Tuxedo Connector tracing feature. Add the TraceLevel attribute to your startWebLogic script.
Example:
   -Dweblogic.wtc.TraceLevel=20000
A TraceLevel of 20000 traces all of the calls to the Tuxedo object in the client.

There's more....

There are additional features provided by WebLogic Tuxedo Connector to support the FML application program interface (API).  For more information about WebLogic Tuxedo Connector FML API implementation, see the Javadocs for the WebLogic Tuxedo Connector.

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


Documentation is available at
http://e-docs.bea.com/wls/docs70

Copyright © 2002 BEA Systems, Inc. All Rights Reserved.