$(function() { $('a[name]').remove(); $('#ic-homepage__footer').before('
'); $('#tabs').tabs({ selected: 0 }); $('#ic-homepage__ic-tips').append( quickTipHTML() ); unhideOneProductTip(); $('#ic-homepage__product-tips').wrapInner('
'); $('#ic-homepage__feed-tips').wrapInner('
'); }); -->
WAS v8.5 > New features > New features overview: AdministeringIntroduction: System administration
We can administer your WebSphere Application Server product through scripts, command line tools, the dmgr console, or the Java programming interface. You administer server processes, topological units referenced as nodes and cells, and the configuration repository where configuration information is stored in XML files.
If we would prefer to browse PDF versions of this documentation using your Adobe Reader, see the System Administration PDF files available from www.ibm.com/software/webservers/appserv/infocenter.html.
A variety of tools, processes, and configuration files are provided for administering the product:
- Console
The dmgr console is a graphical interface that provides many features to guide you through deployment and systems administration tasks. Use it to explore available management options.
For more information, refer to Introduction: Administrative console.
- Scripting
The WebSphere administrative (wsadmin) scripting program is a powerful, non-graphical command interpreter environment enabling you to run administrative operations in a scripting language. We can also submit scripting language programs to run in batch mode. The wsadmin tool is intended for production environments and unattended operations.
For more information, refer to Introduction: Administrative scripting (wsadmin).
- Command line tools
Command-line tools are simple programs that you run from an operating system command-line prompt to perform specific tasks, as opposed to general purpose administration. Using the tools, we can start and stop application servers, check server status, add or remove nodes, and complete similar tasks.
For more information, refer to Introduction: Administrative commands.
- Programming
WAS v8.5 supports a Java programming interface for developing administrative programs. All of the administrative tools supplied with the product are written according to the API, which is based on the industry standard JMX specification.
For more information, refer to Introduction: Administrative programs.
- Data
Product configuration data resides in XML files that are manipulated by the previously-mentioned administrative tools.
For more information, refer to Introduction: Administrative configuration data.
Subtopics
- Introduction: Administrative console
The dmgr console is a graphical interface that allows you to manage the applications and perform system administration tasks for the WAS environment. The dmgr console runs in the web browser.- Introduction: Administrative scripting (wsadmin)
The WebSphere administrative (wsadmin) scripting program is a powerful, non-graphical command interpreter environment enabling you to run administrative operations in a scripting language.- Introduction: Administrative commands
- Introduction: Administrative programs
The JMX specification allows you to write Java programs to administer WAS.- Introduction: Administrative configuration data
WAS configuration data is kept in files. All administrative actions that you perform involve changes to these files.- Introduction: Administrative console
The dmgr console is a graphical interface that allows you to manage the applications and perform system administration tasks for the WAS environment. The dmgr console runs in the web browser.- Introduction: Administrative scripting (wsadmin)
The WebSphere administrative (wsadmin) scripting program is a powerful, non-graphical command interpreter environment enabling you to run administrative operations in a scripting language.- Introduction: Administrative commands
- Introduction: Administrative programs
The JMX specification allows you to write Java programs to administer WAS.- Introduction: Administrative configuration data
WAS configuration data is kept in files. All administrative actions that you perform involve changes to these files.