This chapter describes the typical tasks associated with managing Oracle WebLogic Server and WebLogic Server Domains:
This chapter includes the following sections:
Manage Oracle WebLogic Server with Fusion Middleware Control
Manage Oracle WebLogic Server with the Administration Console
Monitor Managed Servers and the Applications Deployed on Managed Servers
The following describes the steps you can take to manage the WebLogic Domain from Fusion Middleware Control:
View the Administration Server and the Managed Server instances in the domain. How?
Make any necessary configuration changes to the domain, using the Oracle WebLogic Server Administration Console. How?
Use the Change Center and set user preferences in Fusion Middleware Control. How?
Monitor the system components and applications deployed to the domain. How?
Deploy additional applications to the domain. How?
For more information about managing Oracle WebLogic Server, see:
Administering Oracle WebLogic Server with Fusion Middleware Control
"Overview of WebLogic Server System Administration" in Understanding Oracle WebLogic Server.
The following describes the steps you can take to manage the WebLogic Domain from the Oracle WebLogic Server Administration Console:
Learn how to view the Oracle WebLogic Server Administration Console. How?
Alternatively, you can access the Administration Console from Fusion Middleware Control by selecting the WebLogic Server Administration Console hyperlink or Dynamic Target menu choice.
Refer to the Oracle WebLogic Server online help for more information. More
For more information about managing Oracle WebLogic Server, see "Overview of WebLogic Server System Administration" in Understanding Oracle WebLogic Server.
An Oracle WebLogic Server administration domain is a logically related group of Oracle WebLogic Server resources. 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.
The following describes the steps you can take to manage Oracle WebLogic Server domains:
Understand WebLogic Server domains and domain configuration. More
Monitor WebLogic domains. How?
Control WebLogic domains. How?
Configure WebLogic domains. How?
For more information about creating and configuring Oracle WebLogic Server domains, see:
"Creating WebLogic Domains Using WLST Offline" in Understanding the WebLogic Scripting Tool
When you create a domain, you also create an Administration Server, which runs the WebLogic Server Administration Console and distributes configuration changes to other servers in the domain. In a typical production environment, you create one or more Managed Servers in the domain to host business applications and use the Administration Server only to configure and monitor the Managed Servers.
The following describes the steps you can take to manage WebLogic Server instances:
Understand WebLogic Server system administration. More
Monitor server instances. How?
Control server instances. How?
Configure server instances. How?
Configure server templates. How?
For more information on controlling and configuring Oracle WebLogic Server instances, see:
Administering Server Startup and Shutdown for Oracle WebLogic Server
"Using WLST and Node Manager to Manage Servers" in Understanding the WebLogic Scripting Tool
"Using Node Manager to Control Servers" in Administering Node Manager for Oracle WebLogic Server
Administering Server Environments for Oracle WebLogic Server
A WebLogic Server cluster consists of multiple WebLogic Server instances running simultaneously and working together to provide increased scalability and reliability. A cluster appears to clients to be a single WebLogic Server instance. The server instances that constitute a cluster can run on the same machine, or be located on different machines. You can increase a cluster's capacity by adding additional server instances to the cluster on an existing machine, or you can add machines to the cluster to host the incremental server instances.
The following describes the steps you can take to manage WebLogic Server clusters:
Understand WebLogic Server clusters and cluster configuration. More
Monitor WebLogic Server clusters. How?
Control server instances in a cluster. How?
Configure WebLogic Server clusters. How?
For more information, see these topics in Administering Clusters for Oracle WebLogic Server:
The following describes the steps to deploy your applications on Oracle WebLogic Server:
Understand the application deployment process. More
Understand the difference between deploying, redeploying, and undeploying your applications. More
Understand the types of applications you can deploy and the different administration tools you can use to deploy those applications. More
Based on the type of application you are deploying, refer to the appropriate procedure:
For more information on monitoring and controlling application and module deployments in a WebLogic Server domain, see:
"Application Deployments" in Administering Oracle WebLogic Server with Fusion Middleware Control
Before you redeploy an application, see Restrictions When Redeploying an Application with Fusion Middleware Control.
The following describes the steps to redeploy your applications on Oracle WebLogic Server:
Understand the application deployment process. More
Understand the difference between deploying, redeploying, and undeploying your applications. More
Based on the type of application you are redeploying, refer to the appropriate procedure for instructions on how to redeploy an application:
Restrictions When Redeploying an Application with Fusion Middleware Control
If you are redeploying an application, note the following:
The file name and path for the archive you are redeploying must be identical to the file name and path you used when you initially deployed the application.
For example, if the file name and path of the original application was /dua0/staging/myApp.ear
, then the revised application must be /dua0/staging/myApp.ear
.
If you initially deployed the application using another management tool, such as the Oracle WebLogic Server Administration Console or the WebLogic Scripting Tool (WLST), then you cannot redeploy the application using Fusion Middleware Control.
The following describes the steps to undeploy your applications on Oracle WebLogic Server:
The following describes the steps you can take to manage the applications deployed on your Oracle WebLogic Server domain:
Understand WebLogic Server application deployment. More
Monitor application deployments.
Control application deployments.
Configure application deployment.
For information about monitoring, controlling, and configuring application deployments, see "Application Deployments" in Administering Oracle WebLogic Server with Fusion Middleware Control.
For more information about developing and deploying applications for Oracle WebLogic Server, see:
The following describes how to monitor an Oracle WebLogic Server Managed Server and the applications deployed to the server:
Understand Oracle WebLogic Server Managed Servers and clusters. More
Monitor Managed Servers. How?
Determine the types of applications you have deployed. More
Depending upon the type of applications you have deployed, do one of the following:
For more information about monitoring Managed Servers, see "Monitor servers" in Administering Oracle WebLogic Server with Fusion Middleware Control.
For more information about monitoring application deployments, see "Application Deployments" in Administering Oracle WebLogic Server with Fusion Middleware Control.
The following describes how to monitor a cluster and the applications you deploy on the cluster:
Understand Oracle WebLogic Server Managed Servers and clusters. More
Monitor the cluster. How?
Monitor an application deployed to a cluster. How?
For more information about monitoring clusters, see "Monitor clusters" in Administering Oracle WebLogic Server with Fusion Middleware Control.
For more information about deploying to a cluster, see "Application Deployment for Clustered Configurations" in Administering Clusters for Oracle WebLogic Server.
Domain partitions are an administrative and runtime slice of a WebLogic domain and the building blocks of WebLogic Server Multi-Tenancy (WLS MT). Multi-tenancy permits multiple client organizations to share a domain, improving efficiency and reducing operation costs.
The following describes the steps you can take to manage domain partitions using Fusion Middleware Control:
Understand WebLogic Server MT. More
Configure WebLogic Server MT. How?
Manage domain partitions. How?
Configure Resource Managers. How?
To learn more about WebLogic Server MT, see Using WebLogic Server MT.
Java Database Connectivity (JDBC) enables you to configure database connectivity through JDBC data sources in your WebLogic domain. WebLogic JDBC data sources provide database access and database connection management.
The following describes how to create and manage JDBC data sources using Fusion Middleware Control:
Understand the purpose and types of Oracle Fusion Middleware JDBC data sources. More
Understand the capabilities of GridLink data sources. More
Create a generic data source. How?
OR
Create a GridLink data source. How?
OR
Create a multi data source. How?
Monitor a data source. How?
Control a data source. How?
Configure a data source. How?
For more information about creating and managing JDBC data sources, see:
"WebLogic JDBC Data Sources" in Administering Oracle WebLogic Server with Fusion Middleware Control.
The WebLogic Server implementation of JMS is an enterprise-class messaging system that is tightly integrated into WebLogic Server. It fully supports the JMS specification, and also provides numerous WebLogic JMS extensions that go beyond the standard JMS APIs.
The following describes the steps you can take to manage WebLogic Server messaging:
Monitor, control, and configure JMS servers. How?
Monitor and control Store-and-Forward agents. How?
Monitor and control JMS resources and modules. How?
Monitor path services. How?
Monitor and configure messaging bridges. How?
Monitor and configure JMS bridge destinations. How?
Monitor and configure persistent stores. How?
For more information on WebLogic JMS and other related WebLogic messaging components, refer to the following guides:
A security realm comprises mechanisms for protecting WebLogic resources. Each security realm consists of a set of configured security providers, users, groups, security roles, and security policies. A user must be defined in a security realm in order to access any WebLogic resources belonging to that realm.
The following describes the steps you can take to manage WebLogic Server users and groups:
For more information on WebLogic Server users and groups, refer to the following guides:
"Security Realms" in Understanding Security for Oracle WebLogic Server
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 toString Results entries.
The following describes the steps you can take to view the JNDI tree using Fusion Middleware Control:
View objects in the domain JNDI tree. How?
View objects in a server's JNDI tree. How?
View objects in a domain partition's JNDI tree. How?
To learn more about WebLogic JNDI, see "Understanding WebLogic JNDI" in Developing JNDI Applications for Oracle WebLogic Server.