Scripting is a non-graphical alternative that you can use to configure and manage WebSphere® Application Server.
Verify that user IDs that run WebSphere Application Server for z/OS® scripts, including server, administrator and client user IDs, run with the LANG and LC_ALL environment variables set to the same locale based on code page IBM-1047. Settings based on any other code page might cause the scripts to fail. See the "Changing the Locale in the Shell" topic in UNIX® System Services User's Guide for more information.
The WebSphere Application Server wsadmin tool provides the ability to run scripts. The wsadmin tool supports a full range of product administrative activities.
The following figure
illustrates the major components involved in a wsadmin scripting solution:
Figure 1: A WebSphere Application Server scripting solution
The wsadmin tool supports two scripting languages: Jacl and Jython. Five objects are available when you use scripts:
The scripts use these objects to communicate with MBeans that run in WebSphere Application Server processes. MBeans are Java objects that represent Java Management Extensions (JMX) resources. JMX is an optional package addition to Java 2 Platform Standard Edition (J2SE). JMX is a technology that provides a simple and standard way to manage Java objects.
To perform a task using scripting, you must first perform the following steps:
Before you perform any task using scripting, make sure that you are familiar with the following concepts:
Optionally, you can customize your scripting environment. For more information, see Administrative properties for using wsadmin scripting.
After you become familiar with the scripting concepts, choose a scripting language, and start the scripting client, you are ready to perform tasks using scripting.
In this information ...Subtopics
Related tasks
Related reference
| IBM Redbooks, demos, education, and more(Index) |