Running Thin application client code on a server machine

This topic provides the steps necessary to run Thin application client code on a server machine. Install WAS before performing this task.

Procedure

Set up the Thin application client environment. On Windows use the setupCmdLine shell.
```
app_server_root\bin\setupCmdLine.bat
```
Use the setupCmdLine shell.
```
app_server_root/bin/setupCmdLine.sh
```

Run the Java compilation command to compile your client application.

[Windows]

"%JAVA_HOME%\bin\javac" -classpath "%WAS_CLASSPATH%; 
<list_of_your_application_jars_and_classes> " -extdirs %WAS_EXT_DIRS% 
<your_application_class>.java

$JAVA_HOME/bin/javac -classpath "$WAS_CLASSPATH: 
<list_of_your_application_jars_and_classes>" -extdirs $WAS_EXT_DIRS 
<your_application_class>.java

Run the application client.

[Windows] Perform one of the following methods:

Run a Java command to call your main class directly.

"%JAVA_HOME%\bin\java" %WAS_LOGGING%" 
-Djava.security.auth.login.config="%app_server_root%\properties\wsjaas_client.conf" 
-Djava.ext.dirs="%JAVA_HOME%\jre\lib\ext;%WAS_EXT_DIRS%;%WAS_HOME%\plugins;%WAS_HOME%\lib\WMQ\java\lib" 
-Djava.naming.provider.url=<an_IIOP_URL_or_a_corbaloc_URL_to_your  application_server_machine_name>
-Djava.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory 
-Dserver.root="%WAS_HOME%" "%CLIENTSAS%" "%CLIENTSSL%" %USER_INSTALL_PROP% 
-classpath "%WAS_CLASSPATH%;<list_of_your_application_jars_and_classes>" 
<fully_qualified_class_name_to_run> <your_application_parameters>

For more information on IIOP and corbaloc URLs, see Developing applications that use JNDI.

Enter a command to use the WAS launcher.

"%JAVA_HOME%\bin\java" %WAS_LOGGING%
-Djava.security.auth.login.config="%app_server_root%\properties\wsjaas_client.conf"
-classpath "%WAS_CLASSPATH%;<list_of_your_application_jars_and_classes>
-Djava.ext.dirs="%WAS_EXT_DIRS%;%WAS_HOME%\plugins"
-Djava.endorsed.dirs="%WAS_ENDORSED_DIRS%
-Djava.naming.provider.url=iiop://<your_application_server_machine_name>
-Djava.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory  
%SERVER_ROOT% %CLIENTSAS% %CLISENTSSL% <fully_qualified_class_name_to_run>

[AIX] [Linux] [HP-UX] [Solaris] Perform one of the following methods:

Run a Java command to call your main class directly.

"$JAVA_HOME/bin/java" "WAS_LOGGING"
-Djava.security.auth.login.config="$app_server_root/properties/wsjaas_client.conf"
-Djava.ext.dirs="$JAVA_HOME/jre/lib/ext:$WAS_EXT_DIRS:$WAS_HOME/plugins: $WAS_HOME/lib/WMQ/java/lib" 
-Djava.naming.provider.url=<an_IIOP_URL_or_a_corbaloc_URL_to_your  application_server_machine_name>
-Djava.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory
-Dserver.root="$WAS_HOME" $USER_INSTALL_PROP "$CLIENTSAS" "%CLIENTSSL%"
-classpath "$WAS_CLASSPATH;<list_of_your_application_jars_and_classes>"
<fully_qualified_class_name_to_run> <your_application_parameters>

For more information on IIOP and corbaloc URLs, see Developing applications that use JNDI.

Enter a command to use the WAS launcher.

"$JAVA_HOME/bin/java" "WAS_LOGGING"
-Djava.security.auth.login.config="$app_server_root/properties/wsjaas_client.conf"
 "-Dws.ext.dirs=<list_of_your_application_jars_and_classes>
$WAS_EXT_DIRS;$WAS_USER_DIRS" 
-Djava.naming.provider.url=<an_IIOP_URL_or_a_corbaloc_URL_to_your  application_server_machine_name>
-Djava.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory  
"-Dserver.root=$WAS_HOME" 
"$CLIENTSAS" "$CLIENTSSL" $USER_INSTALL_PROP -classpath "$WAS_CLASSPATH"  com.ibm.ws.bootstrap.WSLauncher 
<fully_qualified_class_name_to_run> <your_application_parameters>

Example

View the Samples gallery for more information about the Application Client.

Thin application clients