OpenEJB at SourceForge     OpenEJB at Exolab     
 

Main
   Welcome!
   Download
   Mailing Lists
   The Team
Users
   Quickstart
   Hello World!
   Deploy
   Startup
   Support
   Request Feature
Servers
   Local Server
   Remote Server
Adapters
   Tomcat
Integrators
   Why OpenEJB
   Overview
   Design
   Specification
   Presentation
Developers
   Release Plan
   Source Code
   SourceForge


SourceForge Logo
  



OpenEJB Remote Server
Command-line Guide


NAME

openejb start - OpenEJB Remote Server

SYNOPSIS

openejb start [options]

NOTE

The OpenEJB Remote Server must be executed from the OPENEJB_HOME directory. This is the directory where OpenEJB was installed or unpacked. For the remainder of this document we will assume you unpacked OpenEJB into the directory C:\openejb.

In Windows, the remote server can be executed as follows:

C:\openejb> openejb start -help

In UNIX, Linux, or Mac OS X, the deploy tool can be executed as follows:

[user@host openejb]# ./openejb.sh start -help

Depending on your OpenEJB version, you may need to change execution bits to make the scripts executable. You can do this with the following command.

[user@host openejb]# chmod 755 openejb.sh bin/*.sh

From here on out, it will be assumed that you know how to execute the right openejb script for your operating system and commands will appear in shorthand as show below.

openejb start -help

DESCRIPTION

Starts OpenEJB as an EJB Server that can be accessed by remote clients via the OpenEJB Remote Server.

ALWAYS check your openejb.log file for warnings immediately after starting the Remote Server.

OpenEJB issues warnings when it works around a potential problem, encounters something it didn't expect, or when OpenEJB wants to let you know something may not work as you expected it.

The OpenEJB Remote Server is the default implementation of OpenEJB's ApplicationServer interface. It allows remote clients to access beans in OpenEJB over a network.

The JNDI names clients use to lookup beans from the Remote Server depends on the Deployment ID you gave the beans when you deployed them with the Deploy Tool.

OpenEJB itself is configured with the OpenEJB configuration file, which is extremely simple and self-documenting. This file is located at c:\openejb\conf\openejb.conf.

OPTIONS

 -hhostBinds the Remote Server to the specified host address. Default host address is 127.0.0.1.
 -pport Binds the Remote Server to the specified port. Default port is 4201.
 -tint Sets the number of concurrent threads the Remote server should use to service requests from clients. Default number of threads is 20.
 -ddirSets the OPENEJB_HOME to the specified directory.
 -lfileSets the log4j configuration to the specified file.
 -conffileSets the OpenEJB configuration to the specified file.
 -version Print the version.
 -help Print this help message.
 -examples Show examples of how to use the options.

EXAMPLES

Simplest scenario

openejb start

That's it. The server will start up and bind to IP 127.0.0.1 and port 4201.

The following properties would then be used to get an InitialContext from the Remote Server.

   java.naming.factory.initial      = org.openejb.client.JNDIContext
   java.naming.provider.url         = 127.0.0.1:4201
   java.naming.security.principal   = myuser
   java.naming.security.credentials = mypass
   

Using -h

openejb start -h 10.45.67.8

This is the most common way to use the OpenEJB Remote Server. The server will start up and bind to IP 10.45.67.8 and port 4201.

The following properties would then be used to get an InitialContext from the Remote Server.

   java.naming.factory.initial      = org.openejb.client.JNDIContext
   java.naming.provider.url         = 10.45.67.8:4201
   java.naming.security.principal   = myuser
   java.naming.security.credentials = mypass
   

DNS names can also be used.

openejb start -h myhost.foo.com

The following properties would then be used to get an InitialContext from the Remote Server.

   java.naming.factory.initial      = org.openejb.client.JNDIContext
   java.naming.provider.url         = myhost.foo.com:4201
   java.naming.security.principal   = myuser
   java.naming.security.credentials = mypass
   

Using -p

openejb start -p 8765

The server will start up and bind to IP 127.0.0.1 and port 8765.

The following properties would then be used to get an InitialContext from the Remote Server.

   java.naming.factory.initial      = org.openejb.client.JNDIContext
   java.naming.provider.url         = 127.0.0.1:8765
   java.naming.security.principal   = myuser
   java.naming.security.credentials = mypass
   

Using -conf file

openejb start -conf C:\openejb\conf\mytest.conf

Sets the openejb.configuration system variable to the file C:\openejb\conf\mytest.conf. When the server starts up and the initializes OpenEJB, this configuration will be used to assemble the container system and load beans.

 
     
   
   
 


Java, EJB, JDBC, JNDI, JTA, Sun, Sun Microsystems are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and in other countries. XML, XML Schema, XSLT and related standards are trademarks or registered trademarks of MIT, INRIA, Keio or others, and a product of the World Wide Web Consortium. All other product names mentioned herein are trademarks of their respective owners.