Developing Automation Scripts

Scripting is a non-graphical alternative that you can use to configure and manage the WebSphere® Application Server. The WebSphere administrative scripting tool (wsadmin) is a non-graphical command interpreter environment enabling you to run administrative operations on a server in a scripting language. The wsadmin tool is intended for production environments and unattended operations. You no longer need to switch out of the workbench to WebSphere Application Server command-line management tool, wsadmin, to run your administrative scripts.
There are five wsadmin objects available when you use scripts:
  • AdminControl: Use to run operational commands.
  • AdminConfig: Use to run configurational commands to create or modify WebSphere Application Server configurational elements.
  • AdminApp: Use to administer applications.
  • AdminTask: Use to run administrative commands.
  • Help: Use to obtain general help.
The scripts use these objects to communicate with managed beans (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.
The WebSphere Administrative (wsadmin) scripting program supports two scripting languages - Java Tcl (Jacl) and Java Python (Jython).

Deprecation of Jacl syntax in wsadmin

Deprecation of a product feature does not mean that the feature is being removed from the product immediately. Deprecation is a process of announcing intent to remove the feature eventually at some time in the future. The WebSphere deprecation procedure calls for a feature to remain in the product for two full release cycles before the feature can be removed.

With the Version 6.1 release of WebSphere Application Server, we are announcing the start of the deprecation process for the Jacl syntax associated with wsadmin. This means that Jacl syntax for wsadmin will continue to remain in the product and be supported for at least two major product releases. After that time period it is expected that the Jacl language support will be removed from wsadmin. However, the Jacl syntax support could be extended beyond the next two major product releases if circumstances warrant it.

The Jython syntax for wsadmin is the strategic direction for WebSphere administrative automation. With the Version 6.1 release, WebSphere is significantly enhancing administrative functions and tooling to support product automation in general and the use of the Jython syntax in particular. The following new Jython scripting related enhancements are provided in WebSpherev6.1:
  • WebSphere Automation Tools - an Eclipse-based, full function development environment for wsadmin scripts including Jython editor, color coded keyword highlighting, statement completion assistance, script execution and debugging support.
  • Administrative Console Command Assist - a new feature of the WebSphere administrative console that displays the wsadmin command that is equivalent to the action taken by the end user interacting with the console. The output from the Command Assist feature can be transferred directly to the Jython Editor, making development of Jython scripts based on console actions easy. The Command Assist output can also be saved in a plain text file for later use.
  • IBM® Jacl to Jython Conversion Assistant - a program that assists in the conversion of Jacl syntax wsadmin scripts into equivalent Jython syntax wsadmin scripts.
All future enhancements in the area of WebSphere scripting will focus on use of the Jython syntax. While Jacl will remain as a component shipped with WebSphere for at least two full releases, no new tooling or explicit enhancements will be created for Jacl syntax. Through the announcement of the end of Jacl scripting enhancements or tools, and the significant investment in runtime and tooling features supporting Jython, it is anticipated that a natural shift in WebSphere automation scripts from Jacl to Jython will occur over the time period of the next product releases.
Related tasks
Migrating administrative scripts to Jython V2.1
Related reference
Scripting: Resources for learning

Feedback