Deploying and managing using scripting

Before you begin

Make sure that all WebSphere Application Server for z/OS server, administrator and client user IDs (any user IDs that run WebSphere Application Server for z/OS scripts) are run with environment variables LANG and LC_ALL both set to the same locale based on code page IBM-1047. Settings based on any other code page may cause the scripts to fail. See "Changing the Locale in the Shell" in UNIX System Services User's Guide for more information.

Why and when to perform this task

Scripting is a non-graphical alternative that you can use to configure and manage the WebSphere Application Server. The WebSphere Application Server wsadmin tool provides the ability to execute scripts. The wsadmin tool supports a full range of product administrative activities.

To configure and manage WebSphere Application Server, you can also use the administrative console, which runs in the deployment manager for the cell. For more information about using the administrative console, see Deploying and managing with the GUI. There are also several command-line tools that you can use to start, stop, and monitor WebSphere Application Server processes and nodes. These tools only work on local servers and nodes. They cannot operate on a remote server or node. See Managing using command-line tools for more information.

Steps for this task

  1. Launch a scripting client interactively, as an individual command, in a script, or in a profile.
  2. Perform one of the following options:

Related concepts
Migrating from Systems Management Scripting API (SMAPI) V4 to wsadmin V5
Scripting objects
ObjectName, Attribute, and AttributeList
Related reference
wsadmin scripting environment



Searchable topic ID:   txml_script
Last updated: Jun 21, 2007 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/txml_script.html

Library | Support | Terms of Use | Feedback