Network Deployment (Distributed operating systems), v8.0 > Scripting the application serving environment (wsadmin)


Get started with wsadmin scripting

The WAS 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 WAS 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 WAS processes. MBeans are Java objects that represent 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.

Some wsadmin scripts, including the AdminApp install, AdminApp update, and some AdminTask commands, require that the user ID under which the server is running must have read permission to the files that are created by the user that is running wsadmin scripting. For example, if the application server is running under user1, but you are running wsadmin scripting under user2, you might encounter exceptions involving a temporary directory. When user2 runs wsadmin scripting to deploy an application, a temporary directory for the enterprise application archive (EAR) file is created. However, when the application server attempts to read and unzip the EAR file as user1, the process fails. It is not recommended that you set the umask value of the user that is running wsadmin scripting to 022 or 023 to work around this issue. This approach makes all of the files that are created by the user readable by other users.

To resolve this issue, consider the following approaches based on your administrative policies:

To perform a task using scripting, first perform the following steps:


Procedure

  1. Choose a scripting language. The wsadmin tool only supports Jacl and Jython scripting languages. Jacl is the language specified by default. To use Jython, use the -lang option or specify it in the wsadmin.properties file.

  2. Start the wsadmin scripting client interactively, as an individual command, in a script, or in a profile.


What to do next

Before you perform any task using scripting, make sure that you are familiar with the following concepts:

Optionally, you can customize your scripting environment. See Administrative properties for using wsadmin.sh.

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.


Related


What is new for scripted administration (wsadmin)
Overview and new features for scripting the application serving environment
Use wsadmin scripting with JMX
WAS configuration model using wsadmin.sh
Use wsadmin scripting with Jacl
Use wsadmin scripting with Jython
Use the wsadmin scripting objects
Start the wsadmin scripting client using wsadmin.sh
Restricting remote access using scripting
Use wsadmin scripting


Related


wsadmin scripting tool
Administrative properties for using wsadmin.sh
Scripting and command line reference material using wsadmin.sh
IBM Jacl to Jython Conversion Assistant
WAS Administration Using Jython

+

Search Tips   |   Advanced Search