Right Java tools for J2EE, Web Service, Grid and more

Universal Envoy is for any EJB/J2EE server, which is EJB specification 1.1 (or later) compliant. See Envoy for more information.

The only functionality  from Universal Envoy is the connection to EJB server. There is no support for deploy/undeploy and JNDI name listing for now.

You can use EasyEJB and SuperLogging with Universal Envoy. But, you must type in JNDI names for PeekPoking, you must do some manual work to deploy/undeploy entourage EJBs..

When Super starts, Universal Envoy tries to read a properties file "_jndi.properties" (without double quotes, case sensitive)  under the current working directory (AceletSuper as default). If Universal Envoy finds this file, all the properties, which are specified in this file, will be used to construct InitialContext. If Universal Envoy can not find this file, or anything goes wrong, Universal Envoy will ignore this file and use the default InitialContext constructor (the one without argument list) to get initial context for connecting to EJB server.
 

Set your environment

You need to modify the following file to set your environment variables:
    setEnvironment.bat   (for Windows)
    setEnvironment.sh     (for Unix)
The files are on the installed directory.
 

How to deploy entourage EJBs?

The basic files are provided under beanbox directory of AceletSuper (your installed directory):
     universalSuperLoggingEJB.jar
     universalExample.jar
     

All of them have ejb-jar.xml in the jar files. You need to:

1. Provide the vendor specific xml file with above jar files.
2. Use the vendor provided tools to generate stub and skeleton files.
3. Make a new jar file by adding generated stub and skeleton files.
4. Use the vendor provided tools to deploy above jar files.
5. Install generated client jar files as foreign beans.

J2EE RI and WebLogic 5.1 have been used as Universal servers.

We run J2EE RI server, then:

• Install Super using Universal Envoy.
• Set correct CLASSPATH for J2EE RI on the client machine.
• Run Super.
• Install the client jar files onto Super.
• Restart Super.

We did the same thing with WebLogic 5.1. WebLogic uses special protocol (t3), so we provided a jndi.properties file like this:

    ####### example for Weblogic
    # Context.INITIAL_CONTEXT_FACTORY
    java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
    # Context.PROVIDER_URL
    java.naming.provider.url=t3://localhost:7001
    # Context.SECURITY_PRINCIPAL
    java.naming.security.principal=system
    # Context.SECURITY_CREDENTIALS
    java.naming.security.credentials=weblogic1

This jndi.properties should work for WebLogic 4.5 as well.