Package examples.iiop.ejb.entity.cppclient

This directory contains a c++ client which can be used to call an entity session bean from WebLogic server. You must have Visibroker 4.1 or 5.0 installed on your machine in order to get the example running. You set the location of visibroker by modifying the iiop.properties located in the WL_HOME/samples/server/src/examples/iiop folder (for example, it would likely be set to INPRISE_HOME=c:/Inprise/vbroker). You also need a C++ compiler; this example used Microsoft Visual C++. Make sure that your PATH is set so that the compiler can be run.

Before you run the client applications in this directory, be sure to build the full example. This includes configuring the WebLogic Server and deploying the entity bean. Do this first.

iiop.entity.server.wls

Also, be sure to also take a look at the C++ client code.

Visibroker

There are many bugs in Visibroker that make configuring your files and environment correctly a difficult process (Note how we must force GIOP version with visibroker 4.5). This example demonstrates using Visibroker with an EJB, but it also simultaneously demonstrates how difficult this process can be.

Visibroker 5.0

You may now also build this example with visibroker 5.0. to do so, you must make the following changes from the instructions below:

1. You need to specify utf-16/iso-8859-1 as the default native codesets. Change your config.xml within the Server mbean to include the following:

   <Server> <IIOP DefaultCharCodeset="iso-8859-1" DefaultWideCharCodeset="utf-16" Name="myserver"/> </Server>

2. Do not use GIOP 1.1, and do not use the DefaultMinorVersion entry in your config.xml, this gets specified in the step below.

3. When running the client you need to use a full corbaloc url (Note the '1.2', which specifies GIOP version. Change:

   Client -ORBInitRef NameService=iioploc://localhost:7001/NameService

   to:

   Client -ORBInitRef NameService=corbaloc:iiop:1.2@localhost:7001/NameService

Configure WebLogic

Due to a Visibroker bug in GIOP 1.2 you must force Visibroker to use GIOP 1.1. You can do this by adding the DefaultMinorVersion element to your Server MBean in the config.xml contained in the WL_HOME/samples/server/config/examples directory. For example:

<Server AcceptBacklog="50" COMEnabled="true" ClusterWeight="1"
        ConsoleInputEnabled="false" DGCIdlePeriodsUntilTimeout="2"
        DefaultProtocol="t3" DefaultSecureProtocol="t3s"
        HttpdEnabled="true" JavaCompiler="C:/bea/jdk131_02/bin/javac"
        ListenPort="7001" Name="examplesServer" NativeIOEnabled="true"
        ServerVersion="7.0.0.0" SocketReaderTimeoutMaxMillis="10"
        TunnelingClientPingSecs="45" TunnelingClientTimeoutSecs="40">
<IIOP Name="examplesServer" DefaultMinorVersion="1"/>
</Server>

Build the example

1. Set up your development shell as described in Setting up your environment.

2. Execute the build script provided for this example in the samples\examples\iiop\ejb\entity\cppclient directory of your WebLogic Server installation.

Run the Example

1. Open a separate command-line window in which you will run the client.

2. Set up the environment for your client as described in Setting up your environment for building and running the examples. Make sure you have specified your Visibroker home in the iiop.properties file (WL_HOME/samples/server/src/examples/iiop/iiop.properties) as well as include any necessary directories in your PATH.

3. You can run the client by executing the ant run command included in the build xml: ant run

   Edit the build.xml file for your particular ip address and port ant, it will run the following command:

   
    Client -ORBInitRef NameService=iioploc://localhost:7001/NameService 
   

   Enter the correct hostname and port for your particular configuration

4. You should see output like the following:

   Getting name service reference
   Narrowing to a naming context
   Resolving the naming context
   Narrowing to the AccountHome
   Creating accounts ....
    Finding account 0 ...failed, creating ...done
    Finding account 1 ...failed, creating ...done
    Finding account 2 ...failed, creating ...done
    Finding account 3 ...failed, creating ...done
    Finding account 4 ...failed, creating ...done
    Finding account 5 ...failed, creating ...done
    Finding account 6 ...failed, creating ...done
   Account: :0x00905C88 has a balance of 0
   Account: :0x00905EF8 has a balance of 1000
   Account: :0x00906620 has a balance of 2000
   Account: :0x00906CA0 has a balance of 3000
   Account: :0x00907340 has a balance of 4000
   Account: :0x009079C0 has a balance of 5000
   Account: :0x00908040 has a balance of 6000
   Creating and marshalling a Vector
   Finding big accounts ...
   Account 0x009086C0; balance is $6000
   Removing beans...

There's more...

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.