9
2.2 Summary of System Administration Tools and APIs
WebLogic Server includes several of its own standards-based, extensible utilities that you can use to create, manage, and monitor domains, or you can use WebLogic
Servers management APIs to create custom management utilities.
Table 2 describes the utilities that are included with WebLogic Server.
Monitor activity within applications
Determine which data points you want to monitor and then instrument one or more beans to expose this data through JMX. See Developing
Manageable Applications With JMX for Oracle WebLogic Server. Alternatively, use the WebLogic Server Diagnostics Service to insert
instrumentation code into a running application and monitor its methods or monitor transactions that involve the application. Use this
technology to discover the cause of problems that cannot otherwise be discovered by scanning the available monitoring metrics. If you
determine that the problem is within your application, you can prevent the problem from recurring by using JMX to expose attributes that
indicate the applications health state is degrading. See Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.
Optimize the performance of your
application and maintain service
level agreements. Work Managers configure how your application prioritizes the
execution of its work. Based on rules you define and by monitoring actual run-time performance, WebLogic Server can optimize the
performance of your application and maintain service level agreements.
See Using Work Managers to Optimize Scheduled Work in Configuring Server Environments for Oracle WebLogic Server.
Configure and secure
administration communications
You can separate administration traffic from application traffic in your domain by enabling the administration port. In production
environments, separating the two forms of traffic ensures that critical administration operations starting and stopping servers, changing a
servers configuration, and deploying applications do not compete with high-volume application traffic on the same network connection.
The administration port only accepts communications that use SSL, and therefore secures your administrative requests. See Administration Port
and Administrative Channel in Configuring Server Environments for Oracle WebLogic Server.
Configure logging and view log files
Many WebLogic Server operations generate logs of their activity. Each server has its own log as well as a standard HTTP access log. These log
files can be configured and used in a variety of ways to monitor the health and activity of your servers and applications.
By default, WebLogic Server uses the standard JDK logging APIs to filter and write the messages to log files. See Understanding WebLogic
Logging Services in Configuring Log Files and Filtering Log Messages for Oracle WebLogic Server.
Alternatively, you can configure WebLogic Server to use the Jakarta Project Log4j APIs to distribute log messages. See Log4j and the
Commons Logging API in Configuring Log Files and Filtering Log Messages.
Table 1 Cont. Choosing the Appropriate Management Technology
To do this... Use this technology...
10
Table 2 Management Utilities
Utility Description
Administration Console
The Administration Console is a Web application hosted by the Administration Server. Use it to manage and monitor an active domain.
The management capabilities include:
■
Configuring active domains
■
Stopping and starting servers
■
Monitoring server health and performance
■
Monitoring application performance
■
Viewing server logs Through the Administration Console, system administrators can easily
perform all WebLogic Server management tasks without having to learn the JMX API or the underlying management architecture. The
Administration Server persists changes to attributes in the config.xml file for the domain you are managing.
See:
■
Section 3.2, Starting the Administration Console
■
Administration Console Online Help The online help is also available from the Administration Console by clicking on the Help
link located in the tool bar at the top of the Console. WebLogic Scripting
Tool The WebLogic Scripting Tool WLST is a command-line scripting
interface that you use to manage and monitor active or inactive WebLogic Server domains. The WLST scripting environment is based
on the Java scripting interpreter Jython. In addition to WebLogic scripting functions, you can use common features of interpreted
languages, including local variables, conditional variables, and flow control statements. You can extend the WebLogic scripting language by
following the Jython language syntax. See
http:www.jython.org .
See Oracle WebLogic Scripting Tool. Configuration
Wizard The Configuration Wizard creates the appropriate directory structure
for a WebLogic Server domain, a config.xml file, and scripts you can use to start the servers in your domain. The wizard uses templates to
create domains, and you can customize these templates to duplicate your own domains.
You can also use the Configuration Wizard to add or remove services from an existing, inactive domain.
You can run the Configuration Wizard through a graphical user interface GUI or in a text-based command-line environment. This
command-line environment is called console mode—do not confuse this mode with the Administration Console. You can also create user-defined
domain configuration templates for use by the Configuration Wizard.
See Creating Domains Using the Configuration Wizard.
11
Table 3 describes APIs that you can use to create your own management utilities.
Configuration Template Builder
The Configuration Template Builder provides the capability to easily create your own domain templates, to enable, for example, the
definition and propagation of a standard domain across a development project, or to enable the distribution of a domain along with an
application that has been developed to run on that domain. The templates you create with the Configuration Template Builder are used
as input to the Configuration Wizard as the basis for creating a domain that is customized for your target environment. See Creating Domain
Templates Using the Domain Template Builder.
Apache Ant tasks You can use two Ant tasks provided with WebLogic Server to help you
perform common configuration tasks in a development environment. Ant is a Java-based build tool similar to Make. The configuration tasks
let you start and stop WebLogic Server instances as well as create and configure WebLogic Server domains. When combined with other
WebLogic Ant tasks, you can create powerful build scripts for demonstrating or testing your application with custom domains.
See Using Ant Tasks to Configure a WebLogic Server Domain in Developing Applications for Oracle WebLogic Server.
SNMP Agents WebLogic Server includes the ability to communicate with
enterprise-wide management systems using Simple Network Management Protocol SNMP. WebLogic Server SNMP agents let you
integrate management of WebLogic Servers into an SNMP-compliant management system that gives you a single view of the various
software and hardware resources of a complex, distributed system.
See SNMP Management Guide for Oracle WebLogic Server.
Table 2 Cont. Management Utilities
Utility Description
12
3 Overview of the Administration Console
For detailed information on using the Administration Console, see the Administration Console Online Help, or click Help from any Administration Console page.
The following sections provide an overview of the Administration Console:
■
Section 3.1, About the Administration Console
■
Section 3.2, Starting the Administration Console
■
Section 3.3, Elements of the Administration Console
Table 3 Management APIs
API Description
JMX Java Management Extensions JMX is the Java EE solution for
monitoring and managing resources on a network. Like SNMP and other management standards, JMX is a public specification and many
vendors of commonly used monitoring products support it.
The Administration Console, WebLogic Scripting Tool, and other WebLogic Server utilities use the JMX APIs.
See Developing Custom Management Utilities With JMX for Oracle WebLogic Server.
Java EE Management API
The Java EE Management APIs JSR-77 enable a software developer to create a single Java program that can discover and browse resources,
such as JDBC connection pools and deployed applications, on any Java EE Web application server. The APIs are part of the Java EE
Management Specification, which requires all Java EE Web application servers to describe their resources in a standard data model.
See Monitoring and Managing With the Java EE Management APIs for Oracle WebLogic Server.
Deployment API The WebLogic Server deployment API implements and extends the
JSR-88 deployment specification. All WebLogic Server deployment tools, such as the Administration Console and wldeploy Ant task, use
the deployment API to configure, deploy, and redeploy applications in a domain. You can use the deployment API to build your own WebLogic
Server deployment tools, or to integrate WebLogic Server configuration and deployment operations with an existing JSR-88-compliant tool.
See Programming Deployment for Oracle WebLogic Server. WebLogic
Diagnostic Service APIs
The WebLogic Diagnostic Service includes a set of standardized APIs that enable dynamic access and control of diagnostic data, as well as
improved monitoring that provides visibility into the server. The interfaces are standardized to facilitate future enhancement and
integration of third-party tools, while maintaining the integrity of the server code base. The service is well suited to the server and the servers
stack product components and targets operations and administrative staff as primary users.
See Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.
Logging APIs By default, WebLogic Server uses the standard JDK logging APIs to
filter and write the messages to log files. See Understanding WebLogic Logging Services in Configuring Log Files and Filtering Log Messages for
Oracle WebLogic Server.
Alternatively, you can configure WebLogic Server to use the Jakarta Project Log4j APIs to distribute log messages. For more information, see
Log4j and the Commons Logging API in Configuring Log Files and Filtering Log Messages for Oracle WebLogic Server.
13
■
Section 3.4, Using the Change Center
3.1 About the Administration Console
Kategori