4 Next Steps After Configuring the WebLogic Server Domain
This section includes the following topics:
- Performing Basic Administrative Tasks
Review the administrative tasks you will likely want to perform on a new domain. - Performing Additional Domain Configuration Tasks
Review additional configuration tasks you will likely want to perform on a new domain. - Preparing Your Environment for High Availability
Scaling out for high availability requires additional steps. - Enabling Edition-based Redefinition for Standalone WebLogic Server Installations (Optional)
Edition-based redefinition (EBR) provides standalone Oracle WebLogic Server users with online upgrade support with uninterrupted availability.
Performing Basic Administrative Tasks
Review the administrative tasks you will likely want to perform on a new domain.
Table 4-1 Basic Administration Tasks for a New Domain
Task | Description | More Information |
---|---|---|
Getting familiar with WebLogic Server administration tools |
Get familiar with various tools that you can use to manage your environment. |
See System Administration in Understanding Oracle WebLogic Server. |
Starting and stopping products and servers |
Learn how to start and stop Administration Server, Managed Servers, and components. |
See Starting and Stopping Servers in Administering Server Startup and Shutdown for Oracle WebLogic Server. |
Configuring Secure Sockets Layer (SSL) |
Learn how to set up secure communications for Oracle WebLogic Server using SSL. |
See Configuring SSL for Oracle WebLogic Server in Administering Oracle Fusion Middleware. |
Monitoring Oracle WebLogic Server |
Learn how to keep track of the status of Oracle WebLogic Server. |
See Monitoring, Diagnosing, and Troubleshooting in Understanding Oracle WebLogic Server. |
Understanding Backup and Recovery Procedures |
Learn the recommended backup and recovery procedures for OracleWebLogic Server. |
See Recovering Oracle WebLogic Server with Whole Server Migration and Backup and Recovery Considerations for Oracle WebLogic Server JMS in Administering Oracle Fusion Middleware. |
Parent topic: Next Steps After Configuring the WebLogic Server Domain
Performing Additional Domain Configuration Tasks
Review additional configuration tasks you will likely want to perform on a new domain.
Table 4-2 Additional Domain Configuration Tasks
Task | Description | More Information |
---|---|---|
Deploying Applications |
Learn how to deploy your applications to Oracle Fusion Middleware. |
See Deploying Applications in Administering Oracle Fusion Middleware. |
Adding a Web Tier front-end to your domain |
Oracle Web Tier hosts Web pages (static and dynamic), provides security and high performance along with built-in clustering, load balancing, and failover features. In particular, the Web Tier contains Oracle HTTP Server. |
To install and configure Oracle HTTP Server in the WebLogic Server domain, see Configuring Oracle HTTP Server in a WebLogic Server Domain in Installing and Configuring Oracle HTTP Server. |
Tuning and configuring Coherence for your topology |
The standard installation topology includes a Coherence cluster that contains storage-enabled Managed Coherence Servers. This configuration is a good starting point for using Coherence, but depending upon your specific requirements, consider tuning and reconfiguring Coherence to improve performance in a production environment. |
For more about Coherence clusters, see Configuring and Managing Coherence Clusters in Administering Clusters for Oracle WebLogic Server. For information on tuning Coherence, see Performance Tuning in Administering Oracle Coherence. For information on storing HTTP session data in Coherence, see Using Coherence*Web with WebLogic Server in Administering HTTP Session Management with Oracle Coherence*Web. For more about creating and deploying Coherence applications, see Getting Started in Developing Oracle Coherence Applications for Oracle WebLogic Server. |
Parent topic: Next Steps After Configuring the WebLogic Server Domain
Preparing Your Environment for High Availability
Scaling out for high availability requires additional steps.
Table 4-3 provides a list of tasks to perform if you want to scale out your standard installation environment for high availability.
Table 4-3 Tasks Required to Prepare Your Environment for High Availability
Task | Description | More Information |
---|---|---|
Scaling out to multiple host computers |
To enable high availability, it is important to provide failover capabilities to another host computer. That way, if one computer goes down, your environment can continue to serve the consumers of your deployed applications. |
See Scaling Out a Topology (Machine Scale Out) in the High Availability Guide. |
Configuring high availability for your Web Tier components. |
If you have added a Web tier front-end, then you must configure the Web Tier for high availability, as well as the WebLogic Server software. |
See Configuring High Availability for Web Tier Components in High Availability Guide. |
Setting up a front-end load balancer |
A load balancer can be used to distribute requests across servers more evenly. |
See Server Load Balancing in a High Availability Environment and Configuring Load Balancer Virtual Server Names and Ports in High Availability Guide. |
Configuring Node Manager |
Node Manager enables you to start, shut down, and restart the Administration Server and Managed Server instances from a remote location. This document assumes you have configured a per-domain Node Manager. Review the Node Manager documentation, for information on advanced Node Manager configuration options and features. |
See Advanced Node Manager Configuration in Administering Node Manager for Oracle WebLogic Server. |
Parent topic: Next Steps After Configuring the WebLogic Server Domain
Enabling Edition-based Redefinition for Standalone WebLogic Server Installations (Optional)
Edition-based redefinition (EBR) provides standalone Oracle WebLogic Server users with online upgrade support with uninterrupted availability.
If you want to perform a zero downtime upgrade when upgrading to a future standalone release of Oracle WebLogic Server, you must perform the following tasks after installing and configuring the WebLogic domain.
Note:
For information about using EBR to perform an online application upgrade, see Using EBR to Upgrade an Application.Before you begin, review the following prerequisites and pertinent information:
- Oracle database is the only EBR-supported database.
- In order to EBR-enable Weblogic Server for zero downtime upgrades, you must use the following database tables for storing system schemas: diagnostic logs, timers, leasing tables, servlet sessions, persistent stores, WAN persistent stores, LLR tables, and batch data tables.
- The steps in this guide apply to Oracle WebLogic Server standalone installations.
- In cases where the Oracle WebLogic Server administrator is not able to perform privileged database operations, a database administrator must execute SQL statements or provide an environment for the Oracle WebLogic Server administrator to use.
- The Oracle WebLogic Server administrator or database administrator must create all editions.
- Enabling EBR requires downtime during the initial setup, but once the environment is EBR-enabled, additional downtime is unlikely.
- Stop the WebLogic Server Domain
Before you begin EBR-enabling your environment, you must first stop the WebLogic Server domain. - Create an Edition-enabled User and the Edition
Create an edition-enabled user before creating the edition on the database. - Run the Create Table Scripts
Use SQL*Plus to run the packaged EBR scripts from the WebLogic Services directory. These scripts will create the required tables and EBR-enable them automatically. - Enable EBR Support for System Tables
Use SQL*Plus to execute the scripts that will EBR-enable each existing system table to be defined. - Set the New Edition as the Default
Once you have verified that all of the tables have been created and the new edition is working as expected, set it as the default edition. - Restart the WebLogic Server Domain
After you have created the system tables, restart the WebLogic domain.
Parent topic: Next Steps After Configuring the WebLogic Server Domain
Stop the WebLogic Server Domain
Before you begin EBR-enabling your environment, you must first stop the WebLogic Server domain.
Create an Edition-enabled User and the Edition
Create an edition-enabled user before creating the edition on the database.
Run the Create Table Scripts
Use SQL*Plus to run the packaged EBR scripts from the WebLogic Services directory. These scripts will create the required tables and EBR-enable them automatically.
Enable EBR Support for System Tables
Use SQL*Plus to execute the scripts that will EBR-enable each existing system table to be defined.
Set the New Edition as the Default
Once you have verified that all of the tables have been created and the new edition is working as expected, set it as the default edition.
Restart the WebLogic Server Domain
After you have created the system tables, restart the WebLogic domain.