Use the Administration Thin Client

 

With the Administration Thin Client, you can run the wsadmin tool or a standalone administrative Java program with only a couple of JAR files. This leads to a reduction in the amount of time that it takes for the wsadmin tool to start and improved performance.

 

Overview

The Administration Thin Client does not support the installation of SAR files or editing applications that use an external JACC provider, for example, Tivoli Access Manager.

For tracing and logging information for the Administration Thin Client, see the Enabling trace on client and standalone applications article.

 

Procedure

1. Make the Administration Thin Client JAR files available by copying them from a WAS environment to an environment outside of WAS, for example, c:\MyThinClient . The Administration Thin Client JAR files are located in one of the following locations:

   • The AppServer/runtimes directory.

   • The AppClient/runtimes directory, if you optionally selected the Administration Thin Client when you installed the application client.

   You must have a special license agreement to download these JAR files.

2. Use the Administration Thin Client JAR files to compile and test administration client programs. For Java applications, you can compile and run the JAR files within a standard Java 2 Platform, Standard Edition environment. For more information see the the Compiling an application in a non-OSGi environment using scripting topic.

3. If security is turned on, you will also need the following required files:

   • Copy the com.ibm.ws.security.crypto_6.1.0.jar file from either the AppServer/plugins directory or the AppClient/plugins directory and put it in the C:\MyThinClient directory.

   • Copy the soap.client.props file from the AppServer\profiles\profileName\properties directory and put it in the C:\MyThinClient\properties directory.

   • Copy the sas.client.props file from the AppServer/profiles/profileName/properties directory and put it to C:\MyThinClient\properties directory

   • Copy the ssl.client.props file from either the AppServer\profiles\profileName/properties directory or the AppClient/properties directory and put it in the C:\MyThinClient\properties directory. Note that this file contains the user.root property. You must modify the value to your thin client directory, for example, C:\MyThinClient .

   • Copy the key.p12 file from AppServer\profiles\profileName\etc directory and put it to \MyThinClient\etc directory. To do this, copy the file to your thin client directory or run a script to generate the file. For more information, see the following articles:

     • ssl.client.props client configuration file

     • Interoperating with previous product versions

     • retrieveSigners command

     • Secure installation for client signer retrieval

4. Launch the Administration Thin Client client or run the wsadmin tool remotely in a Java 2 Platform, Standard Edition environment.

5. Deploy the stand alone JAR files and the administrative client applications and start the applications outside of a WebSphere Application Server environment.

---

Compiling an application in a non-OSGi environment using scripting

Running the wsadmin tool remotely in a Java 2 Platform, Standard Edition environment

Auditing invocations of the wsadmin tool

 

Related Reference

Application client functions

 

Related information

Use scripting (wsadmin)
Enabling trace on client and standalone applications
Start the wsadmin scripting client