| 
 | WebLogic Server 6.1 Code Examples, BEA Systems, Inc. | |||||
This example illustrates connectivity between a variety of clients, Tuxedo and WebLogic Server using a simple Ping program. To build the C++ client you will need Inprise Visibroker 4.1 for C++ and a C++ compiler. It is also necessary that you have Tuxedo 8.0 or later if you wish to run the clients through Tuxedo or make outbound calls to Tuxedo. To get the most out of this example, first read through the source code files to see what is happening. Start with the XML build files to find the general structure of the example, i.e. which classes are used for the different objects and interfaces, then examine the other files to see how the applications work.
Pay close attention to setting up your Tuxedo environment as there are many pitfalls when attempting to run Tuxedo and WebLogic in conjunction. There are three different clients that can be executed; examine the XML build file carefully for each one. Take special note to see how the idl files are created for the C++ and Tuxedo clients as well as the Tuxedo server. This example also presumes familiarity with BEA Tuxedo. For further information on Tuxedo and especially how to administer and configure a Tuxedo Server, it is highly recommended that you view their online documentation
If you run into problems, make sure to check your environment; check especially your PATH and CLASSPATH as well as the BDMCONFIG, 
TOBJADDR
, and TUXCONFIG variables that are used by Tuxedo. Make sure you have the proper 
  settings that include the necessary Tuxedo directories in your PATH; make sure you have TUXDIR set to your installation of Tuxedo 8.0 and that 
  you have included the tuxedo8.0/bin and tuxedo8.0/lib directories in your PATH. It is recommended to get these examples first working with WebLogic Server before 
attempting to introduce the Tuxedo Server  
The following section describes how to build and run the example:
config.xml or use the console to make sure you have included PingImpl as a startup class:
    <StartupClass
      Arguments="tuxedo.corba.remote"
      ClassName="examples.iiop.rmi.server.wls.PingImpl"
      FailureIsFatal="false"
      Name="Pinger"
      Targets="examplesServer"
    />
bdmconfig.xml file has been provided in the WL_HOME/samples/examples/iiop/ejb/stateless/server/tux directory. This file 
provides configuration information for connectivity between WebLogic and Tuxedo. Edit it for your particular installation (change all instances 
of 127.0.0.1 to your own ip address) and add it to
as an argument to the WTC (WebLogic Tuxedo Connector) startup class in your config.xml file located at 
WL_HOME/config/examples. 
For example:
    <StartupClass
      Arguments="BDMCONFIG=BEA_HOME\samples\examples\iiop\rmi\server\tux\bdmconfig.xml"
      ClassName="weblogic.wtc.gwt.WTCStartup"
      Name="WTC"
      Targets="examplesServer"
     />
<TUXDIR>/samples/corba/cnssimpapp directory and run
runme.cmd, this will verify that you Tuxedo installation is correct and
builds an example. For more information on this example and setting up your Tuxedo environment, 
see the Tuxedo documentation.
You will have to edit your environment to include a BDMCONFIG
entry.  This path should lead to a blank unformatted file as it will contain domain information stored in binary format.  
For example: set BDMCONFIG=C:\BEA_HOME\tuxedo8.0\samples\corba\cnssimpapp\results\my_bdm. The my_bdm 
file should begin as blank unformatted file.  Do not get this confused with the bdmconfig.xml file that configures the WebLogic side of 
communication.  
ping_server.exe, ior.txt ubbdomain, and dom1config from 
the WL_HOME/samples/examples/iiop/rmi/server/tux directory. 
Paste them into the <TUXDIR>/samples/corba/cnssimpapp directory.
<TUXDIR>/samples/corba/cnssimpapp/ubbdomain and
dom1config files for your particular setup.  The ubbdomain file configures your Tuxedo Server and applications in a Tuxedo domain. 
You will have to change the MACHINES and ISL sections to contain your own machine name, i.p. address and port information. 
The dom1config file 
configures connectivity for remote domains (In this case WebLogic Server) and gets turned into binary format, replacing the my_bdm 
file you have already created. Please change any instance of 127.0.0.1 in this file to match your own ip address.
For more information on setting up your Tuxedo environment, 
see the Tuxedo documentation. 
ubbdomain using tmloadcf -y ubbdomain. Load the dom1config
using dmloadcf -y dom1config and boot the Tuxedo system using tmboot -y.
//<hostname>:2468
CosNaming namespace by doing:
	cnsbind -o ior.txt WLS
The ior.txt is included in the WL_HOME\samples\examples\iiop\rmi\server\tux directory, and should be appropriately edited for
the domain you are using for your WebLogic server (examples if you are following the example explicitly).
C++ Client (requires visibroker 4.1)
Tuxedo Client (requires Tuxedo 8.0)
Read more about WebLogic RMI over IIOP in the Developer Guide, Using WebLogic RMI over IIOP.
Read more about WebLogic EJB in the Developer Guide, BEA WebLogic Server Enterprise JavaBeans.
Read more about WebLogic RMI in the Developer Guide, Using WebLogic RMI.
For more information about WebLogic Server WebLogic Tuxedo Connector, see:
| 
 | Documentation is available at http://e-docs.bea.com/wls/docs61/ | |||||