WAS v5.1 System Administration
- J2EE Applications
- Cell-wide settings
GUI-menu system for configuration of most aspects of WebSphere Application Server.
Command interpreter that allows you to execute administrative operations using jacl or jython.
- Miscellaneous commands
Various command line tools are available that will perform specific tasks, such as starting and stoping appservers, checking server status, adding/removing nodes, etc...
- Java programs
Perform administrative tasks using Java programs by using the JMX specification.
- XML data files
Modify functionality by tweaking product configuration XML data files.
- Administrative agents
Includes node and deployment manager agents.
- Configure appservers.
Within appservers, configure:
- Configure clusters of appservers
- Deploy J2EE applications
- Manage nodes
- Implement security and create end-user accounts
- Establish database connectivity
- Administer Web services
- Administer JMS
- Tune the Web container
- Configure Cell-wide and server-wide settings
Refers to XML-based configuration data stored under...$WAS_HOME/config/cell...and includes information about virtual hosts, shared libraries, and variables.
- Configure Load Balancers and Web servers
Appservers can work with load balancers and Web servers to handle requests for webapps. If you use a Web server to serve requests, configure an HTTP plug-in.
WAS can host applications developed using J2EE 1.3 specifications and containing the following components:
Assembling is when you package code components into "modules" that comply with the J2EE specification, using XML documents known as deployment descriptors to describe the contents of the modules. After assembly, modules are archived into an EAR file and deployed into WebSphere Application Server.
EAR files can contain the following modules:
*.war web application (.war) archives *.RAR Resource adapter archives *.JAR Enterprise beans EJB *.jar Application client archives
You can update and uninstall deployed applications, sometimes with hot deployment and dynamic reloading, where you do not need to restart the appserver.
When deploying, verify class loading relationships are correct.
You can use Apache Ant and Apache Struts to help build applications.
Configuration data is stored in XML files under $WAS_HOME/config. Files in an individual server directory apply to that specific server only. Files in a node level directory apply to every server on that node. And files in the cell directory apply to every server on every node within the entire cell.
Cell-wide configuration data is replicated to every node in the cell.