This article provides various ways to access information about administering
the product and your applications being hosted by the product. Find information
based on:
Click a check mark in the table to go to the instructions for the
task.
|
Application Assembly Tool |
AEs administrative console |
Application client resource configuration tool |
Configuring client resources |
|
|
 |
Creating an application client |
 |
|
|
Starting and stopping resources |
|
 |
|
Pinging resources |
|
 |
|
Validate administrative configuration |
|
 |
|
Removing objects from EAR files |
 |
|
 |
Configuring enterprise applications |
 |
 |
|
Creating the EAR.WAR and JAR files in an application |
 |
|
|
Installing enterprise applications |
|
 |
|
Starting, stopping, and restarting applications and modules |
|
 |
|
Uninstalling applications |
|
 |
|
Updating application configurations |
 |
 |
|
Exporting application configurations |
|
 |
|
Viewing deployment descriptor information for enterprise applications (read-only) |
|
 |
|
Showing the status of enterprise applications |
|
 |
|
Exporting enterprise applications |
|
 |
|
Updating nodes |
|
 |
|
Regenerating WebSphere plug-in configurations |
|
 |
|
Configuring tracing on administrative nodes |
|
 |
|
Starting and stopping application servers |
|
 |
|
Updating application servers |
|
 |
|
Updating EJB containers |
|
 |
|
Creating an EJB module |
 |
|
|
Installing EJB modules |
|
 |
|
Viewing deployment descriptor information for EJB modules |
|
 |
|
Updating EJB module configurations |
|
 |
|
Exporting table DDLs of EJB modules |
|
 |
|
Updating Web container configurations |
|
 |
|
Creating a Web module |
 |
|
|
Installing Web modules |
|
 |
|
Precompiling JSP files for Web modules |
|
 |
|
Viewing deployment descriptor information for Web modules |
|
 |
|
Updating Web module configurations |
|
 |
|
Updating session management settings |
|
 |
|
Configuring new HTTP transports |
|
 |
|
Removing HTTP transport configurations |
|
 |
|
Updating transport configurations |
|
 |
|
Configuring new data source providers |
|
 |
 |
Configuring new data sources |
|
 |
 |
Removing data source providers (JDBC providers) and data sources |
|
 |
 |
Updating data source and data source provider configurations |
|
 |
 |
Configuring new custom services |
|
 |
|
Removing custom services |
|
 |
|
Updating custom service configurations |
|
 |
|
Administering virtual hosts |
|
 |
|
Configuring security |
 |
 |
|
Administering server traces |
|
 |
|
Administering the transaction service |
|
 |
|
Configuring application server process definitions |
|
 |
|
Updating process definition configurations |
|
 |
|
Administering path maps |
|
 |
|
Configuring OLT and Debugger |
|
 |
|
Configuring the Location Service Daemon |
|
 |
|
Configuring Object Request Brokers (ORBs) |
|
 |
|
Configuring JVM settings |
|
 |
|
Configuring new mail sessions |
|
 |
 |
Updating mail session configurations |
|
 |
 |
Removing mail session configurations |
|
 |
 |
Configuring new URL providers |
|
 |
 |
Updating URL provider configurations |
|
 |
 |
Removing URL provider configurations |
|
 |
 |
Removing URL configurations |
|
 |
 |
Configuring new JMS providers |
|
 |
 |
Configuring new JMS connection factories |
|
 |
 |
Configuring new JMS destinations |
|
 |
 |
Updating JMS provider, connection factory, and destination configurations |
|
 |
 |
Removing JMS providers, connection factories, and destinations |
|
 |
 |
Updating JMS provider, connection factory, and destination configurations |
|
 |
 |
Administering WebSphere administrative domains |
|
 |
|
Regenerating the Web server plug-in configuration |
|
 |
|
The following tables provide quick entry points into descriptions,
tasks, and settings of various objects that you can administer.
Use the following information to compare, select among, and learn how to use the features of
the various product interfaces.
The table summarizes the available product interfaces (with the
exception of the installation program and the
problem determination tools).
Interface |
Purpose |
Script for starting the product |
Perhaps the most important interface you will use is the script for
starting the product, which you need to do prior to starting the administrative
console or the application server runtime. |
Administrative console (Web based) |
Graphical interface for configuring and operating application servers and other resources
that support applications in a runtime environment |
Application assembly tool |
Graphical interface for assembling applications from application components and modifying their
J2EE deployment descriptors |
Configuration using property files |
Ability to manually edit various property files in the product directory structure
for miscellaneous configuration purposes |
Application installer (SEAppInstall) |
Command line interface for installing an application into a server configuration file,
preparing it to run within an application server. You can also use it to uninstall an
application from a server and to export an installed application containing configuration
information.
|
Client launcher (launchClient) |
Command line interface for starting a client application. |
EAR expander |
Command line interface for expanding .ear files into the directory structure typical
for use in the runtime of this product. Should not need to use this tool on an ordinary
basis. |
Application client resource configuration tool |
Graphical interface for configuring resources that support client applications
in a runtime environment. (See also information on developing
a Java client.) |
SOAP EAR Enabler |
Command line interface for enabling a set of SOAP services within an
Enterprise Application Archive (EAR) file. |
XML-SOAP Admin tool |
A modified version of the Apache SOAP XML-Admin interface for managing
each SOAP-enabled EAR file. |
Deployment tool |
Interface for generating code for deployment. Useful for more complicated or custom
scenarios. For simple scenarios, the use of this tool is hidden from the administrator. It is invoked
by other consoles and tools. (See
also the article about generating code
for deployment). |
Administrators that have access to an administrative client can
use the full capabilities of the client. At this time, it is not
possible to allow administrators to perform some operations (such as starting and
stopping servers) but deny them the ability to perform other operations
(such as creating and configuring resources).