Domains include a special Oracle WebLogic Server instance called the Administration Server, which is the central point from which you configure and manage all resources in the domain. Usually, you configure a domain to include additional Oracle WebLogic Server instances called Managed Servers. You deploy Web applications, EJBs, Web services, and other resources onto the Managed Servers and use the Administration Server for configuration and management purposes only.
For more information on WebLogic Server domains, see Understanding Domain Configuration for Oracle WebLogic Server.
Note:
If you are logged into a domain partition, navigate from the Domain Partition menu.
This chapter includes the following sections:
This section describes how to monitor your domain. This section includes the following tasks:
A server is an instance of WebLogic Server that runs its own Java Virtual Machine (JVM) and has its own configuration.
To monitor the runtime status of all server instances configured in a domain:
To monitor the status of all JDBC data sources created in a domain:
From the WebLogic Domain menu, select Monitoring, then select JDBC Data Sources.
The JDBC Data Sources (Monitoring) table lists the JDBC data sources that have been created in the domain and displays related status information, such as:
Name
Type
Resource
Scope
Server Name
State
For more information about these fields, see Configuration Options.
Optionally, select View to access the following table options:
Columns: add or remove the columns displayed in the table
Detach: detach the table (viewing option)
Sort: sort the columns in ascending or descending order
Reorder: change the order of the columns displayed
Query by Example
To test a data source:
In the JDBC Data Sources table, select the row of the JDBC data source instance you want to test. The Test Data Source option is displayed above the table.
Click Test Data Source.
To monitor the completion status of all tasks in a domain:
To view status information of a specific server life cycle task:
This section includes the following tasks:
Before you begin:
Control operations on Managed Servers require starting the Node Manager. Starting Managed Servers in STANDBY
mode requires the domain-wide administration port.
You can start, resume, suspend, or shut down the server instances configured in a domain. For information on how the server instances transition from STANDBY
or ADMIN
to the RUNNING
state, see Understanding Server Life Cycle in Managing Server Startup and Shutdown for Oracle WebLogic Server.
To change the state of server instances in a domain:
This section describes how to configure your domain. This section includes the following tasks:
To configure general settings for a domain:
Before you begin:
The administration port accepts only secure, SSL traffic, and all connections via the port require authentication by a server administrator. Because of these features, enabling the administration port imposes the following restrictions on your domain:
The Administration Server and all Managed Servers in your domain must be configured with support for the SSL protocol.
All server instances in the domain, including the Administration Server, enable or disable the administration port at the same time.
Note:
The administration port cannot be dynamically enabled on a Managed Server. You must shut down each Managed Server, enable the administration port, then restart.
WebLogic Server provides the option to enable an SSL administration port for use with all server instances in the domain. Using the administration port is strongly recommended. It provides three capabilities:
Since communication uses SSL, administration traffic (which includes such things as administrator passwords) is more secure.
It enables you to start a server instance in the STANDBY
state.
It enables you to separate administration traffic from application traffic in your domain.
To enable the administration port for a domain:
After you finish:
Start all Managed Server instances in the domain. You do not need to restart the Administration Server.
To configure how many archive files are retained:
All server instances in a domain run either in development mode or production mode. In general, production mode requires you to configure additional security features.
To configure all server instances in a domain to run in production mode:
startWebLogic
script. The Administration Server starts in the new mode.You can specify which Java Persistence API (JPA) persistence provider to use for each persistence entity in the persistence.xml
file. However, if no persistence provider is specified, the domain-wide default provider is used.
Changing the default provider does not affect applications that are already deployed. The setting takes effect when the server instance is restarted or the application is manually redeployed.
To specify the default JPA provider in a domain:
The JNDI browser is a central location where you can find the JNDI names of all the WebLogic Server resources. Typically, while writing WLS client programs, you would search the JNDI browser for JNDI names. The JNDI browser displays a tree of resources in the domain, a server, or a partition. Selecting a node or an object in the tree, displays JNDI information including Binding Name, Object Class, Object Hash Code, and Object to String Results entries.
To view objects in the domain JNDI tree:
For more information about JNDI, see Understanding WebLogic JNDI in Developing JNDI Applications for Oracle WebLogic Server.