With the Administration Thin Client, you can run the wsadmin tool or a standalone administrative Java™ program with only a couple of Java archive (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.
You cannot use the Administration Thin Client to manage feature packs nor deploy application artifacts that are specific to feature packs.
The Administration Thin Client does not support the installation of store archive (SAR) files or editing applications that use an external Java Authorization Contract for Containers (JACC) provider, for example, Tivoli® Access Manager.
The Administrative Thin Client does not support passing the Kerberos token to a server. It only supports basic authentication, which passes the user ID and password.
The Administration Thin Client does not support co-existence with other thin clients.
The Administration Thin Client currently cannot be used to manage feature packs, nor deploy application artifacts specific to feature packs.
The Administration Thin Client on the z/OS® platform does not use localcomm.
For tracing and logging information for the Administration Thin Client, see Enabling trace on client and stand-alone applications.
In this information ...Subtopics
Related concepts
Related tasks
| IBM Redbooks, demos, education, and more(Index) |