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 reduces the amount of time that it takes for the
wsadmin tool to start and improved performance. This information should
be used to set up JMX client programs.
Before you begin
Verify that the Java™ Development Kit (JDK) is installed
on the Administration Thin Client. Use the same IBM JDK as the server
that it will connect to in the administrative Thin Client environment.
Important: The Administration Thin Client does not support using
a non-IBM JDK.
About this task
The Administration Thin Client does not
support the installation of SIP Application Archive (SAR) files or
editing applications that use an external Java Authorization Contract for Containers (JACC)
provider, such as the Tivoli® Access
Manager. ![[Updated in December 2011]](../../deltaend.gif)
dec2011
For tracing and logging information for the Administration
Thin Client, see the Enabling trace on client and stand-alone applications article.
Procedure
- Make the Administration Thin Client JAR files available
by copying com.ibm.ws.admin.clientXXX.jar from a WebSphere Application
Server environment to an environment outside of WebSphere Application
Server, for example, c:\MyThinClient \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.
- 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 Compiling an application in a non-OSGi environment using scripting topic.
- Copy the messages directory from the app_server_root//properties directory
to the C:\MyThinClient\properties directory.
- 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 \MyThinClient directory.
- Copy the soap.client.props file from the AppServer\profiles\profileName\properties directory
and put it in the C:\MyThinClient\properties \MyThinClient\properties directory.
- Copy the sas.client.props file from the AppServer/profiles/profileName/properties directory
and put it to C:\MyThinClient\properties \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 \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 \MyThinClient.
- Copy the key.p12 file from AppServer\profiles\profileName\etc directory
and put it to C:\MyThinClient\etc \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:
- Launch the Administration Thin Client client or run the wsadmin tool remotely in a Java 2 Platform,
Standard Edition environment.
- Deploy the stand alone JAR files and the administrative
client applications and start the applications outside of a WebSphere
Application Server environment.