Access Enterprise Java Beans in Macromedia JRun4 from .NET Using J-Integra® for .NET

 Java/J2EE .NET Interoperability Products Page

This example demonstrates how to access Enterprise Java Beans in Macromedia JRun4 from .NET client. J-Integra® for .NET is a Java interoperability component that bridges Java/J2EE and Microsoft .NET. It provides bi-directional access of Java objects and .NET components.

Synopsis

Use this example as a guideline to show you how to access your Enterprise JavaBeans (EJB) from a .NET client, using J-Integra® for .NET. This example will be deployed on Macromedia JRun4 Application Server.

The Steps to Follow will show you how to deploy J-Integra® for .NET as a Java Servlet in JRun4 to interpret the HTTP requests from a .NET client. Refer to the diagram below for an overview of the scenario:

Access Enterprise Java Beans in Macromedia JRun4 from .NET Using J-Integra® for .NET

Note: $USER_INSTALL_DIR$ is the directory where J-Integra® for .NET has been installed. If this location contains whitespace characters (e.g. C:\Program Files\...), you may need to include it within "" when referencing it at the command-line. JRUN4_HOME is the directory where JRun4 has been installed.

Prerequisites

  1. A platform with Microsoft Visual Studio .NET 2003 (7.1.3088 or higher) installed, or at least the .NET Framework 1.0.3705 or higher. This will be known throughout the example as the .NET platform.

  2. A platform with JRun4 and J-Integra® for .NET 1.5.1265 (or higher) installed. This will be known throughout the example as the Java platform.

  3. Verify that GenService is installed correctly on the .NET platform.

Steps to Follow

  1. Run Janetor to Configure J-Integra® for .NET

  2. Generate a Web Application aRchive (WAR file)

  3. Deploy the EJB and WAR file on JRun4

  4. Run GenNet and Compile the Proxies

  5. Compile and Run the .NET Client

Run Janetor to Configure J-Integra® for .NET

Perform this step on the Java platform.

You will need to configure J-Integra® for .NET to act as a Servlet. This is done through the Janetor tool.

  1. Windows

    Launch Janetor from the Start Menu.

    Command-Line 
    java -jar $USER_INSTALL_DIR$\lib\janetor.jar

  2. Go to File - Open and open janet.xml located in $USER_INSTALL_DIR$\examples\jrun4_http\java_server.

  3. Install your J-Integra® for .NET product license. See Installing the J-Integra® for .NET license for further information.

  4. Select default under Local Objects. Here you see that the J-Integra® for .NET Servlet can be accessed with a URI that will be constructed from the configuration details shown. Any Java classes will also be accessed as the specified Assembly name from the .NET client. If required, change the details to point to the JRun4 host name/port number.

    Setup local objects in Janetor configuration tool

    Do not exit Janetor yet as you'll need it for the next step.

Generate a Web Application aRchive (WAR file)

Perform this step on the Java platform.

In this step, you will use Janetor to generate a WAR file. This WAR file will include the J-Integra® for .NET runtime acting as a Java Servlet along with the EJB proxies required to access the EJB.

  1. Back in Janetor, go to File - Export web application archive.

  2. The screenshot below shows the Export web application archive window. See the documentation for Janetor for a description of all the fields. Change Output file as necessary. Finally, notice that the Use version 2.2 deployment descriptor is checked.

    Export WAR file using Janetor configuration tool

    To generate the WAR file click OK.

  3. Before you exit Janetor, save the configuration by going to File - Save.

Deploy the EJB and WAR file on JRun4

Perform this step on the Java platform.

In this step, you will deploy both the EJB and the WAR file from Janetor on JRun4. The EJB represents a basic Entity Bean that returns orders from the order database. This EJB already comes deployed in JRun4 and you will not need to re-deploy it.

  1. Launch JRun Launcher and start both samples and admin server:

    Launch JRun Launcher and start both samples and admin server

  2. Use the Management Console to deploy the WAR file, janetexample.war located in $USER_INSTALL_DIR$\examples\jrun4_http\java_server.

Run GenNet and Compile the Proxies

Perform this step on the Java platform.

In this step, you will use the GenNet tool to generate .NET proxies for the EJB, along with the JNDI Context required to instanciate the Home object.

 
Note: GenNet saves configuration details to an XML file. For your convenience, the settings described below have already been saved to the file gennet.xml in the directory $USER_INSTALL_DIR$\examples\jrun4_http\java_server. If you'd prefer not to manually enter the settings as instructed below, simply copy this file over to $USER_INSTALL_DIR$ before starting GenNet.
  1. Windows

    Launch GenNet from the Start Menu.

    Command-Line

    Change directory to $USER_INSTALL_DIR$ and then enter:

    java -jar lib\gennet.jar

  2. The first screen of GenNet shows a list of machines that have GenService running (screenshot not shown). Select the appropriate one and click Next.

  3. The next screen prompts for the components (JAR files or directories) to be added to the CLASSPATH. Each of these components are required in order for the Java runtime to resolve references to Java classes when generating .NET proxies. You'll need to add the following components:

    - $USER_INSTALL_DIR$\examples\jrun4_http\java_server\order.jar
    - JRUN4_HOME\lib\jrun.jar

    Using GenNet generate .NET assemblies for Java objects

    Move on to the next step by clicking Next.

  4. The next screen prompts for the specific Java classes that will have .NET proxies generated for them. Click on Browse... to add the following classes (use the CTRL key to select multiple classes):

    - compass.OrderHomeRemote
    - com.intrinsyc.janet.JNDIContext
    - compass.OrderRemote

    Select Java classes to be exported to .NET in GenNet

    Click on the Filter button and choose not to generate any proxies for the referenced classes as shown below. This will eliminate the number of .NET proxies created.

    Filter Referenced classes in GenNet

    Move on to the next step by clicking Next.

  5. The next screen prompts you to specify the .NET Assembly name along with the output directory. The screenshot may show a different output directory than what Output Directory is, but it should be pointing to $USER_INSTALL_DIR$\examples\jrun4_http\vbnet_client\bin\Debug.

    Setup .NET assembly name and output directory in GenNET

  6. You should see a message that the proxy generation was successful. Click Exit to exit GenNet.

    GenNet proxy generation successful

Compile and Run the .NET Client

Perform this step on the .NET platform.

In this final step, you will configure the .NET client using a configuration file, then compile and run it.

Along with .NET proxies, the GenNet tool generates .NET configuration files to be used as templates - one for the HTTP channel and one for the TCP channel. As the .NET client will be using HTTP to connect to the EJB, we will modify remoting_http.config. You can find this in the same directory that the proxies were generated in.

Note: In the .NET code, notice that a call is made to RemotingConfiguration.Configure("remoting_http.config");

  1. Modify remoting_http.config to look like:

    <configuration>
  <system.runtime.remoting> 
    <application>
      <client url="http://localhost:8200/janetexample">
        <activated type="com.intrinsyc.janet.JNDIContext, JanetExample"/>
      </client>
      <channels>
        <channel ref="http">
          <clientProviders>
            <formatter ref="binary"/>
          </clientProviders>
        </channel>
      </channels>
    </application>
  </system.runtime.remoting>
</configuration>

    Notice that http://localhost:8200/janetexample matches what was entered under Local Objects in Janetor. Change accordingly if necessary.

  2. Load JRun4OrderClient.sln located in $USER_INSTALL_DIR$\examples\jrun4_http\csharp_client and press F5 to run, or simply run the executable in the bin\Debug directory.

    Note: If you happen to have an older version of Visual Studio .NET, it is still possible to compile the example, but you will not be able to open the solution file. See build.bat in $USER_INSTALL_DIR$\examples\jrun4_http\vbnet_client.

  3. You should see the JRun 4 Order Example form:

    Access Enterprise Java Beans in Macromedia JRun4 from .NET Client

    This form uses the EJB locate and display orders.

  4. Enter 1 for the Order Id field and press Find Order to see the results:

    Access Enterprise Java Beans in Macromedia JRun4 from .NET Client

© 2007 Intrinsyc Software International, Inc. All rights reserved. Legal