Traditionally, IBM WebSphere used Jacl (port of Tcl to the JVM) for scripting its administration. However, in later releases, Jython (Java-based Python) was introduced as an alternative, and now Jacl is deprecated. WebSphere has now branched into two different code lines, the legacy "Traditional" and re-architected "Liberty" – "Traditional" still supports Jacl, but it is deprecated; in "Liberty" Jacl has been removed entirely.
This is a big story.
WebSphere is the "flagship" "application server" [L1 ] from COMPANY: IBM. What that means in the year 2001 is a Web server, with a method for active content, plus convenience functions for database access, and at least lip service to load-leveling, security, and so on. In fact, as of 2002, it's evident IBM is promoting "WebSphere" as one of its top two or three brands; that means, among other things, that the rubric has lost almost all technical content.
Because it's IBM, WebSphere uses Java for as much as possible, and prefixes all descriptions with "e-commerce". The technical basis is
As one too-wise correspondent justly noted, "You need to be a DBA, Apache Administrator and a JAVA guru to do a clean install."
[Explain Tcl connection and controversy.]
Tcl enters through WSCP.
Other WebSphere acronyms of possible pertinence:
WAS 5 APPLICATION SERVER UPDATE.
The WebSphere Application Server wsadmin tool provides the ability to execute scripts. You can use the wsadmin tool to manage a WebSphere Application Server V5.0 installation. This tool uses the Bean Scripting Framework (BSF), which supports a variety of scripting languages to configure and control your WebSphere Application Server installation. The WebSphere Application Server only supports the Jacl and Jython scripting languages. The wsadmin launcher makes Java objects available through language-specific interfaces. Scripts use these objects for application management, configuration, operational control, and for communication with MBeans running in WebSphere server processes.
Patrick Finnegan 05/04/2005.