|
WebLogic Server 6.1 Code Examples, BEA Systems, Inc. | |||||
See:
Description
| Interface Summary | |
| Toupper | The methods in this interface are the public face of the simpapp client. |
| ToupperHome | 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 Toupper Buy some shares using the Toupper Sell some shares using the Toupper Remove the Toupper |
| ToupperBean | ToupperBean is a stateful SessionBean. |
This example demonstrates the ability of WTC to allow WLS to interoperate with Tuxedo.
The Tuxedo simpapp application is extended to run over domains. This allowsclients of the TOUPPER service to run on either Tuxedo or WLS. It consists of a Tuxedo service, TOUPPER, which converts a string to upper case. A WLS client invokes the TOUPPER EJB and connects to the Tuxedo TOUPPER service.
set PATH to check the status and add the path if necessary.simpapp example from your Tuxedo installation and create a working Tuxedo simpapp directorysimpapp directory%TUXDIR%\bin setEnv.cmd located at %TUXDIR%. Unix users modify the tux.env file located at $TUXDIR.buildclient -o simpcl -f simpcl.cbuildserver -o simpserv -f simpserv.c -s TOUPPERubbdomain and dom1config files from the WTC simpapp directory to your Tuxedo simpapp directorytolower.c file from the WTC simpserv directory to your Tuxedo simpapp directoryubbdomain 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"ubbdomain file tmloadcf -y ubbdomaindom1config for your Tuxedo environment. This includes creating log devices and updating the network addresses.DMTLOGDEV="d:\my_apps\tlog"TDOM1 NWADDR="//TuxedoMachine:1234"dom1config file set BDMCONFIG=d:\mydomain\simpapp\bdmconfigdmloadcf -y dom1configtolower client buildclient -v -f tolower.c -o tolowertmboot -ytmadmin psc command.The following domain processes should have booted: DMADM, GWADM, and GWTDOMAINTOUPPER service offered by the simpserv serverTOLOWER service is offered by the GWTDOMAIN serversimpapp directoryapplications directory in your WLS domain build setExamplesEnv.cmd. Unix users copy ./config/examples/setExamplesEnv.sh script to your WTC simpapp directory, then modify and run the setExamplesEnv.sh script. wtc_toupper.jar file using ant. antbdmconfig.xml file with information specific to your installation: bdmconfig.xml file using the WTCValidateCF utility:java weblogic.wtc.gwt.WTCValidateCF bdmconfig.xmlsimpserv directorywtc_tolower.jar file using ant. antwtc_tolower.jar and wtc_toupper.jar are deployed. Use the WLS console or check the config.xml file. Manually deploy the EJBs if needed.bdmconfig.xml file you are using for the example. weblogic.wtc.gwt.WTCStartupBDMCONFIG=path_name_of_your_bdmconfig.xml_fileweblogic.wtc.gwt.WTCShutdownTOUPPER and Tolower EJBs are deployed in your WLS application serversimpapp directoryrun.cmd allcapsrun.sh allcapsrun allcapsThe Tuxedo service replies to your WLS application with:
Returned string is: ALLCAPS
simpapp example, use the WTC tracing feature. Add the TraceLevel parameter to the StartUp Class Argument list. BDMCONFIG=path_to_my_bdmconfig.xml_file,TraceLevel=20000A TraceLevel of 20000 traces all of the calls to the Tuxedo object in the client.
You are ready to run the simpserv example.
For more information about WebLogic Server WebLogic Tuxedo Connector, see:
|
Documentation is available at http://e-docs.bea.com/wls/docs61 |
|||||