user manual

Chapter 12: The VisiClient Container 121
Support of references and links
that is referencing the enterprise bean. This allows multiple enterprise
beans with the same ejb-name to be uniquely identified.
If the path is not specified, container picks first matching EJB-name that it
finds from list of EJB JARs inside EAR and throws an exception if doesn't
find a bean with same name in ejb-link element.>
Using the VisiClient Container
The following command line demonstrates the use of the VisiClient Container:
Prompt% appclient <client-archive> [-uri <uri>] [client-arg1 client-arg2
..]
The following table describes VisiClient container command line elements and
definitions
VisiClient Container usage example
The following command lines demonstrate usage of an application client. In
the example, the appclient launcher sets the classpath required to launch
VisiClient.
This example is also located in the Hello example in the install_dir/examples/
j2ee/hello directory. When your server (EJB container) is up, to run a client
embedded inside an EAR file, the command is:
appclient me install_dir\examples\j2ee\build\hello\hello.ear -uri
helloclient.jar
To run a client in a standalone JAR file, the command is:
appclient me install_dir\examples\j2ee\build\hello\client\helloclient.jar
Running a J2EE client application on machines not running
BES
To run a J2EE application client on a client machine that does not have
Borland Enterprise Server installed on it, make sure to copy the following
VisiClient files to your client machine and run the following processes.
Table 12.1 Elements in a VisiClient container command
Element Definition
<client-archive> A standalone client JAR or EAR
containing client JAR.
-uri The relative location of the client JAR
inside an EAR file. This is required for
EAR contained JAR files.
<client-args> Space separated list of arguments
passed to the client's main class.