|
|
| 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
- 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.
-
Copy the simpFML32.c example to your Tuxedo installation and create
a working Tuxedo simpFML32 directory
-
Change directories to the working Tuxedo simpFML32 directory
-
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 simpFML32 server:
buildserver -o simpFML32 -f simpFML32.c -s REVERSE_STRING
-
Copy the ubbdomain and dom1config files from the WebLogic Tuxedo Connector
simpFML32
directory to your Tuxedo simpFML32 directory
-
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.
APPDIR="/home/me/simpapp"
TUXCONFIG="/home/me/simpapp/tuxconfig""
-
Modify the dom1config for your Tuxedo environment. This includes
creating log devices and updating the network addresses.
DMTLOGDEV="d:\my_apps\tlog"
AUDITLOG="d:\my_apps\aud"
DMTLOGNAME="DMTLOG_TDOM1"
TDOM1 NWADDR="//TuxedoMachine:1234"
TDOM2 NWADDR="//WTCMachine:5678"
-
Load the ubbdomain file
-
Load the dom1config file
set BDMCONFIG=d:\mydomain\simpFML32\bdmconfig
-
Boot the Tuxedo domain
-
Verify all processes have started using the tmadmin psc command.The
following domain processes should have booted:
-
DMADM, GWADM, and GWTDOMAIN
-
The REVERSE_STRING service offered by the simpFML32 server
WebLogic Server Configuration
- Boot your WebLogic Examples Server
- Make sure that no other WTCServer Mbeans are targeted to the examplesServer
-
Change directories to the WebLogic Tuxedo Connector examples simpFML32 directory
-
Set environment variables. Update the following parameters:
-
Set the APPLICATIONS to the location of the applications directory
in your WebLogic Server 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 qsample directory, then modify and run the setExamplesEnv.sh script.
- Build the
wtc_rstring.jar file using ant.
- Enter the following command:
ant
- Modify the
setWTCMbeans file with information specific to your installation.
- NT/2000 users modify the
setWTCMbeans.cmd file. Unix users modify the setWTCMbeans.sh file.
- 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
- Set the
user and passwd for your environment
- Run the
setWTCMbeans file to configure your installation.
- NT/2000 users run the
setWTCMbeans.cmd file.
- Unix users run the
setWTCMbeans.sh file.
-
Shutdown and restart your WebLogic Server application server.
- 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.
-
Change directories to the WebLogic Server simpFML32 directory
-
Start a client
-
For NT/2000, use the following command: run.cmd abcdef
-
For Unix, use the following command: run.sh abcdef
-
Example:
run abcdef
The Tuxedo service replies to your WebLogic Server application with:
Returned string is: fedcba
- 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:
Copyright © 2002 BEA Systems, Inc. All Rights Reserved.