This service deploys application client JARs and runs their class with the main method in a separate Java virtual machine. Appclient Service is a container used by the Deploy Service in EAR component deployment, if there is an application client JAR in it.
|
Server |
|
Property |
Description |
Default Value |
|
|
|
java.naming.factory.initial |
Specifies implementation class for InitialContextFactory. The administrator can change the InitialContextFactory and pass additional properties that correspond to the specified context factory. Note : For information about initial context factory, refer to JNDI Context Specification .
|
com.inqmy.services.jndi.InitialContextFactoryImpl |
com.inqmy.services.appclient.classpathNumber |
The classpath, which is used when launching the application client, is also passed to the application client. It specifies the number of classpath tokens to be added to application client classpath. |
23 |
classpathToken_1 … classpathToken_N |
N is the number specified as a value of the com.inqmy.services.appclient.classpathNumber property. These properties specify paths to a single directory or a JAR file that is added to the application client classpath. |
|
|
|
|
Note: If a reference to another service or library is added in Appclient Service, the classpath to it must be added as classpathToken_N . This is done at runtime, and the service does not need restarting. In this way, various applications that are deployed on SAP J2EE Engine 6.20 can use the same resource. If the JAR is changed, applications must not be redeployed. Since they have reference to it and it is present in their classpaths, they cam still use the resource.
Appclient Service can be administered using Shell commands from the
APPCLIENT
command group.
Note: For information on Appclient shell commands, refer to the Shell Commands Reference section.
../cluster/server/services/appclient/properties
Appclient Service properties specified in the
Visual Administrator
section can be set from this property file as well.