WebSphere Jython programming
Explanation will follow.
For now, some basic info, but more importantly, TABS to all the reference info.
Use it at your own risc
-
Within the console, follow the windows to the item you want to change and try to figure out which attributes in which MBean to change.
It is actually not as difficult as this may sound.
Explanation on how to do this will follow soon :-)
-
Start with the top-level Configuration items ("Contexts") and work your way down through "Document ID's"
Then Configuration Type and then through the type and its sub-types.
This is the most certain way of finding what to configure, the most complete way, but it is also the most complex, I guess.
This is explained below.
Contexts explanation
In the
"Contexts" section (see tab above), you find the starting points for configuring WebSphere Application Server.
The starting points are called "Contexts".
Contexts define all the configuration items for that context.
Opening a context item will list all the configration items (called "Documents") associated with that context.
Conetxts example
Suppose you want to configure an Application Server. The context for this is "Server Context".
Open the "Server Context" by clicking on the "+" in the tree on the left.
You then see all the items that may be configured for an Application Server.
Suppose you want to configure the Application Server itself. The item for this is "Server"
Then, above in the navigation, select Documents and lookup "Server".
Documents and Types explanation
Below, you find all the starting point for all the configuration items.
In the
"Contexts" window (See above) you can find out which item may be (or needs to be) configured for with top-level configuration item (called "Context").
For each configuration item, the right most column gives the Configuration Type (actually the MBean type) that defines the top-level configuration item type.
Click on the type you want to configure and you will see all the attributes and their types that needs to be configured.
Attributes themselves can be Types. You will see this after clicking on the type, by the fact that the attribute itself is again a hyperlink to a sub-type.
Documents and Types example
Suppose you want to configure an Application server. In the
"Contexts" section, you have found out that the document ID for this is "Server".
Look up "Server" in the left-most column in the table below and click on the "Configuration Type" (right-most column) corresponding to the "Server" document ID.
The "Configuration Type" for "Server" happens to be "Server" as well :-)
Clicking on the "Server" configuration item will list all the attributes for "Server".
Try it and you will see basic attributes like "name" (the name of the Application Server) and attributes that are themselves objects (types), like "WebContainer" (containing all the attributes for the "WebContainer" type that correspond to this Application Server.