You can use the wsadmin tool to configure and administer
application servers, application deployment, and server run-time operations.
About this task
The wsadmin tool provides the ability to automate configuration
tasks for your environment by running scripts. However, there are
some limitations for using the wsadmin tool, including:
- The wsadmin tool only supports the Jython and Jacl scripting languages. The Version 6.1 release of WebSphere Application
Server represented the start of the deprecation process for the Jacl
syntax that is associated with the wsadmin tool. The Jacl syntax for
the wsadmin tool continues to remain in the product and is supported
for at least two major product releases. After that time, the Jacl
language support might be removed from the wsadmin tool. The Jython
syntax for the wsadmin tool is the strategic direction for WebSphere
Application Server administrative automation. The application server
provides significantly enhanced administrative functions and tooling
that support product automation and the use of the Jython syntax.
- The wsadmin tool manages
the installation, configuration, deployment, and runtime operations
for application servers, deployment managers, administrative agents,
and job managers that run the same version or a higher version of
the product. The wsadmin tool cannot connect to an application server,
deployment manager, administrative agent, or job manager that runs
a product version which is older than the version of the wsadmin tool.
For example, a Version 6.x wsadmin client cannot connect to a Version
5.x application server. However, a Version 5.x wsadmin client can
connect to a Version 6.x application server. This limitation exists
because new functionality is added to the wsadmin tool in each product
release. You cannot use new command functionality on application servers
running previous product versions.
- The wsadmin tool operates
at the deployment manager node level in a mixed-cell environment.
Do not run wsadmin at the application server node level to ensure
that all command functionality is available.
The wsadmin launcher supports several
scripting objects, including the AdminConfig, AdminControl, AdminApp,
AdminTask, and Help objects. Scripts use these objects for application
management, configuration, operational control, and for communication
with MBeans that run in product processes. You must start the wsadmin
scripting client before you perform any other task using scripting.
In a flexible
management environment, you can connect the wsadmin tool to a base
application server, deployment manager, administrative agent, or job
manager process. If you do not specify the port of the base application
server or the profile name assigned to the job manager, the wsadmin
tool automatically connects to the administrative agent.
Results
The wsadmin returns the following output when it establishes
a connection to the server processs:
Jthon example output:
WASX7209I: Connected to process server1
on node myhost using SOAP connector;
The type of process is: UnManagedProcess
WASX7029I: For help, enter: "$Help help"
wsadmin>
Jacl example output:
WASX7209I: Connected to process server1
on node myhost using SOAP connector;
The type of process is: UnManagedProcess
WASX7029I: For help, enter: "$Help help"
wsadmin>