WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize the table of contents and search results
             New or updated topic for this feature pack

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.

Before you begin

You must install WebSphere Application Server before performing this task.

Procedure

  1. Set up the Thin application client environment.
    [Windows] Use the setupCmdLine shell.
    app_server_root\bin\setupCmdLine.bat
    
    [AIX] [Linux] [HP-UX] [Solaris] [z/OS] Use the setupCmdLine shell.
    app_server_root/bin/setupCmdLine.sh
    [i5/OS] Use the setupClient script.
    1. Start the Qshell environment. On the CL command line, run the STRQSH command.
    2. On the Qshell command line, run the following command using the dot (.) operator:
      . app_server_root/bin/setupClient [-profileName profileName]
      
  2. 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
    [AIX] [Linux] [HP-UX] [Solaris] [z/OS]
    $JAVA_HOME/bin/javac -classpath "$WAS_CLASSPATH: 
    <list_of_your_application_jars_and_classes>" -extdirs $WAS_EXT_DIRS 
    <your_application_class>.java
    [i5/OS] Run the following command on the Qshell command line.
    javac -J-Djava.version=1.5 -classpath "$WAS_CLASSPATH:jars_and_classes" -extdirs $WAS_EXT_DIRS app_class.java
  3. 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="%USER_INSTALL_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 WebSphere Application Server launcher.
      "%JAVA_HOME%\bin\java" %WAS_LOGGING%
      -Djava.security.auth.login.config="%USER_INSTALL_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] [z/OS] 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="$USER_INSTALL_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 WebSphere Application Server launcher.
      "$JAVA_HOME/bin/java" $WAS_LOGGING
      -Djava.security.auth.login.config="$USER_INSTALL_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>
    [i5/OS] Run the following command on a Qshell command line.
    java ${JAVA_FLAGS_EXT} -classpath "$WAS_CLASSPATH:jars_and_classes" -Djava.naming.provider.url=URL class_name app_parm
    
    When using the WebSphere Application Server launcher, run the following command on a Qshell command line:
    java ${JAVA_FLAGS_EXT} -classpath "$WAS_CLASSPATH:jars_and_classes" -Djava.naming.provider.url=URL com.ibm.ws.bootstrap.WSLauncher class_name app_parm
    
  4. Launch the administrative program. The com.ibm.ws.admin.client_6.1.0.jar JAR file, which is in the WAS_HOME/runtimes directory and the com.ibm.ws.security.crypto.jar JAR file, which is in the WAS_HOME/plugins directory should be in your classpath. You can use java -classpath to have the JAR files in your classpath when launching your program.

Example

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




In this information ...


Related concepts

IBM Redbooks, demos, education, and more


Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

IBM Suggests
Task topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/tcli_developthinserver.html