This topic highlights what is new or changed, for users who are going to customize, administer, monitor, and tune production server environments using the wsadmin tool.
New in Version 6.1! indicates new features or changes implemented at the Version 6.1 level. Unmarked items are Version 6.0 improvements that apply also to Version 6.1, which should interest anyone migrating to Version 6.1 from Version 5.x. |
Growing set of administrative commands | Automation of administrative tasks is made easier through the AdminTask scripting object of wsadmin. Many of the more involved tasks for administration have been implemented using this new feature which supports interactive execution and combines many individual scripting commands into a single task oriented command. Various AdminTask commands are implemented for important administrative scenarios such as server management, cluster management and resource management. AdminTask commands provide various user friendly and task oriented wsadmin commands. AdminTask commands may have multiple steps for some complicated administrative tasks similar to the wizard in the console. AdminTask commands are grouped based on their function areas. The AdminApp, AdminConfig, and AdminControl objects have also been enhanced with new functionality. For more information about the scripting
objects for the wsadmin tool, see the following topics:
.
|
Additional administrative roles | New in Version 6.1! For security specialists, even more administrative roles are defined to provide degrees of authority that are needed to perform certain administrative functions with the wsadmin tool. The newest roles are deployer and adminsecuritymanager. |
Improved help with administrative commands | Detailed help information for AdminTask commands and command groups is available through various AdminTask help commands. All AdminTask commands can be executed in interactive mode, which leads users step by step, interactively. At the end of execution, the corresponding AdminTask command is generated to help you learn the AdminTask command syntax. |
Improved wsadmin tracing configuration | New in Version 6.1! You can configure the wsadmin client side log file and audit each wsadmin session. The wsadmin.properties file includes new properties for specifying to append to a trace file and to name a default scripting interface. See Tracing operations with the wsadmin tool and Administrative properties for scripting. |
wsadmin no longer case sensitive | New in Version 6.1! Commands and parameters for the wsadmin tool are not case sensitive. That is, wsadmin will an accept any of these arguments: –-tracefile, -traceFile, -traceFile, or tRaCEFile. wsadmin also infers the scripting language by looking at the suffix of the script file you specified on the command line. |
Simplified administration | New in Version 6.1! Command assistance in the administrative console maps your administrative activities to wsadmin scripting commands, so that you can capture your console knowledge and apply it to wsadmin. Using command assistance, you can view wsadmin scripting commands in the Jython language for the last action run in the administrative console. See Accessing command assistance from the administrative console. |
Scripting enhancements for configuring applications | New in Version 6.1! Scripting
enhancements for application configuration include:
|
Local and connected mode | New in Version 6.1! The administrative commands can be available in connected or local mode. The set of available administrative commands is determined when you start a scripting client in connected or local mode. See the documentation for each scripting object, available from Using the wsadmin scripting objects. |