Planning the Oracle WebLogic Server Installation

1 Planning the Oracle WebLogic Server Installation

This section prepares you to install Oracle WebLogic Server and Coherence. Review this section thoroughly to ensure that you do not encounter any problems during or after installation and domain configuration.

Using this Document

There are certain scenarios that you want to use this guide for, and other sources of information.

This section contains the following topics:

Using the Standard Installation Topology as a Starting Point

This guide helps you create the standard installation topology for Oracle WebLogic Server and Coherence. You can extend this topology to make it highly available and secure so that it is suitable for a production system.

The standard installation topology represents a sample topology for this product; it is not the only topology that Oracle supports. See Understanding the Standard Installation Topology in Planning an Installation of Oracle Fusion Middleware.

Using this Document in an Upgrade Scenario

If you are installing Oracle WebLogic Server and Coherence as part of an upgrade procedure, follow procedures in this guide to install the software, but do not run the Configuration Wizard to create a WebLogic domain.

After you install the software, go to Overview of the Upgrade Process in Upgrading Oracle WebLogic Server.

Using this Document to Extend a Domain

Procedures in this document describe how to create a new domain; you can use the same procedures to extend an existing domain.

If you do this, be sure to read Installing Multiple Products in the Same Domain in Planning an Installation of Oracle Fusion Middleware for important information.

If you are creating a new domain but your needs do not match the steps in a procedure, be sure to make your selections accordingly and see the supporting documentation for more details.

Oracle WebLogic Server Installers

This guide describes how to use the Oracle WebLogic Server and Coherence distribution to install and configure runtime development, test, or production environments for Oracle WebLogic Server.

To set up a development environment, see:

Obtaining the Oracle WebLogic Server and Coherence Distribution to find the installers.
Overview of WebLogic Server Application Development in Developing Applications for Oracle WebLogic Server for a complete list of what to keep in mind when you set up a development environment for Oracle WebLogic Server.

About the WebLogic Server and Coherence Standard Installation Topology

The standard installation topology has a standard WebLogic Server domain.

The following figure shows the standard installation topology for Oracle WebLogic Server and Coherence:

Figure 1-1 Oracle WebLogic Server and Coherence Topology

Description of "Figure 1-1 Oracle WebLogic Server and Coherence Topology"

This topology has a standard WebLogic Server domain that contains two Managed Servers in a cluster and an Administration Server, all configured on one host.

See these topics:

WebLogic Server and Coherence Standard Installation Topology Elements

This section describes the standard installation topology elements.

Oracle WebLogic Server and Coherence Standard Installation Topology Elements

See Roadmap for Installing and Configuring the Installation Topology for a roadmap that describes steps to create this topology.

Element	Description and Links to Additional Documentation
APPHOST	Standard term in Oracle documentation for the machine that hosts the application tier.
WebLogic Domain	Logically related group of Java components. In this case, the Administration Server, Managed Servers, and other related software components. See What is an Oracle WebLogic Server Domain? in Understanding Oracle Fusion Middleware.
Administration Server	Domain central control entity. Maintains domain configuration objects and distributes configuration changes to Managed Servers. See What is the Administration Server in Understanding Oracle Fusion Middleware.
Cluster	A collection of multiple WebLogic Server instances running simultaneously and working together. See Understanding Managed Servers and Managed Server Clusters in Understanding Oracle Fusion Middleware.
Machine	Logical representation of the computer that hosts one or more WebLogic Server instances (servers). Machines are also the logical glue between Managed Servers and Node Manager; to start or stop a Managed Server with Node Manager, the Managed Server must be associated with a machine.
Managed Server	Host for your applications, application components, Web services, and their associated resources. See Understanding Managed Servers and Managed Server Clusters in Understanding Oracle Fusion Middleware.

Running the Installer in Silent Mode

You can install using the -silent flag on the command line when you start the installer.

See the following topics in Installing Software with the Oracle Universal Installer for details on silent mode and the steps to run it.

Roadmap for Installing and Configuring the Installation Topology

This document has all the procedures you need to install and configure WebLogic Server. Within the procedures, this document refers to additional information you can use if you want to create a modified version of this topology.

Oracle WebLogic Server and Coherence Installation Procedure

The following table shows steps required to install and configure Oracle WebLogic Server:

Task	Description	Documentation
Verify your system environment	Before starting the installation, verify that your system meets minimum system and network requirements.	Roadmap for Verifying Your System Environment
Obtain the appropriate distribution	To create the topology this section describes, obtain the Oracle WebLogic Server and Coherence distribution.	Obtaining the Oracle WebLogic Server and Coherence Distribution.
Determine your installation directories	Verify that the installer can create or access installer directories that it needs to create. Also, verify that the directories exist on systems that meet the minimum requirements.	What are the Key Oracle Fusion Middleware Directories? in Understanding Oracle Fusion Middleware.
Install the software	Run the installation program to install the software.	Installing the Oracle WebLogic Server and Coherence Software
Create a WebLogic domain	Use the Configuration Wizard to create a WebLogic domain.	Creating and Configuring the WebLogic Domain
Perform post-installation tasks	Start to manage components in the domain or continue to modify your environment for high availability.	Next Steps After Configuring the WebLogic Server Domain

Roadmap for Verifying Your System Environment

This topic has important information that you must read and understand before you begin installation and configuration steps. It identifies important tasks and checks that verify your environment is properly prepared to install and configure Oracle WebLogic Server and Coherence.

Roadmap to Verify Your System Environment

Task	Description	Documentation
Verify certification and system requirements.	Verify that your operating system is certified and properly configured for WebLogic Server and Coherence installation and configuration.	See Verifying Certification, System Requirements and Interoperability in Planning an Installation of Oracle Fusion Middleware.
Identify a proper installation user.	Verify that the installation user has the proper permissions to install and configure the software.	See Selecting an Installation User in Planning an Installation of Oracle Fusion Middleware.
Select the installation and configuration directories on your system.	Verify that you can create the necessary directories for installation and configuration, according to the recommended directory structure.	See Selecting Directories for Installation and Configuration in Planning an Installation of Oracle Fusion Middleware.
Install a certified JDK.	The installation program for the distribution requires that your system have a certified JDK.	See Installing a JDK in Planning an Installation of Oracle Fusion Middleware. Note: Oracle WebLogic Server 15c (15.1.1.0.0) supports JDK version 17.0.16 or later, and JDK 21.0.8 or later.

Obtaining the Oracle WebLogic Server and Coherence Distribution

To download Oracle WebLogic Server and Coherence software for development or evaluation, go to the Software Downloads page.

Note:

As of Oracle WebLogic Server 14c (14.1.2.0.0), the WebLogic Server and Coherence examples are provided in a separate examples JAR file, which you install in the same ORACLE_HOME as your WebLogic Server installation. For more information about obtaining and installing WebLogic Server examples, see Installing the WebLogic Server Code Examples .

To obtain Oracle WebLogic Server and Coherence, follow these steps:

Download the generic installer fmw_15.1.1.0.0_wls_generic.jar .
(Optional) Download the WebLogic Server and Coherence examples installer fmw_15.1.1.0.0_wls_examples_generic.jar.
Extract the contents onto your system.
The extracted files run the product installer and install the software onto your system (Installing the Oracle WebLogic Server and Coherence Software).

Verifying Digital Signature and Integrity of Installation Archive Files

Oracle digitally signs the installation archive files with Oracle certificates to ensure the integrity of the packages before you deploy them in your environments.

Use the Java utility jarsigner to verify the integrity of your installation archive files. You can verify the integrity of the installation archive files before you extract the installation files.

Quick Verification

To quickly verify the installation archive files, use the jarsigner command with the -verify option:

Go to the directory where you have downloaded the installation archive files.

Run this command to check your installation archive file:

jarsigner -verify installation_archive_file

Detailed Certificate Information

If you want detailed certificate information, then use the -verbose:summary and -certs along with the -verify option.

Go to the directory where you have downloaded the installation archive files.

Run this command to check your installation archive file:

jarsigner -verify -verbose:summary -certs installation_archive_file

The output is similar to the following:

 204040 Thu Oct 02 14:32:24 UTC 2025 META-INF/MANIFEST.MF   >>> Signer
   X.509, CN="Oracle America, Inc.", O="Oracle America, Inc.", L=Redwood City, ST=California, C=US
   Signature algorithm: SHA256withRSA, 3072-bit key
   [certificate is valid from 1/10/25, 12:00 AM to 1/11/28, 11:59 PM]
   X.509, CN=DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1, O="DigiCert, Inc.", C=US
   Signature algorithm: SHA384withRSA, 4096-bit key
   [certificate is valid from 4/29/21, 12:00 AM to 4/28/36, 11:59 PM]
   X.509, CN=DigiCert Trusted Root G4, OU=www.digicert.com, O=DigiCert Inc, C=US
   Signature algorithm: SHA384withRSA, 4096-bit key
   [trusted certificate]
   >>> TSA
   X.509, CN=DigiCert SHA256 RSA4096 Timestamp Responder 2025 1, O="DigiCert, Inc.", C=US
   Signature algorithm: SHA256withRSA, 4096-bit key
   [certificate is valid from 6/4/25, 12:00 AM to 9/3/36, 11:59 PM]
   X.509, CN=DigiCert Trusted G4 TimeStamping RSA4096 SHA256 2025 CA1, O="DigiCert, Inc.", C=US
   Signature algorithm: SHA256withRSA, 4096-bit key
   [certificate is valid from 5/7/25, 12:00 AM to 1/14/38, 11:59 PM]
   X.509, CN=DigiCert Trusted Root G4, OU=www.digicert.com, O=DigiCert Inc, C=US
   Signature algorithm: SHA384withRSA, 4096-bit key
   [certificate is valid from 8/1/22, 12:00 AM to 11/9/31, 11:59 PM]   203521 Thu Oct 02 14:32:26 UTC 2025 META-INF/ORACLE_C.SF (and 1 more)   (Signature related entries)      0 Thu Oct 02 12:40:26 UTC 2025 META-INF/ (and 637 more)   (Directory entries)sm    298 Wed Oct 01 23:48:56 UTC 2025 META-INF/com/oracle/cie/common/dao/jaxb/jaxb-packages.properties (and 1492 more)   [entry was signed on 10/2/25, 2:32 PM]
   >>> Signer
   X.509, CN="Oracle America, Inc.", O="Oracle America, Inc.", L=Redwood City, ST=California, C=US
   Signature algorithm: SHA256withRSA, 3072-bit key
   [certificate is valid from 1/10/25, 12:00 AM to 1/11/28, 11:59 PM]
   X.509, CN=DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1, O="DigiCert, Inc.", C=US
   Signature algorithm: SHA384withRSA, 4096-bit key
   [certificate is valid from 4/29/21, 12:00 AM to 4/28/36, 11:59 PM]
   X.509, CN=DigiCert Trusted Root G4, OU=www.digicert.com, O=DigiCert Inc, C=US
   Signature algorithm: SHA384withRSA, 4096-bit key
   [trusted certificate]
   >>> TSA
   X.509, CN=DigiCert SHA256 RSA4096 Timestamp Responder 2025 1, O="DigiCert, Inc.", C=US
   Signature algorithm: SHA256withRSA, 4096-bit key
   [certificate is valid from 6/4/25, 12:00 AM to 9/3/36, 11:59 PM]
   X.509, CN=DigiCert Trusted G4 TimeStamping RSA4096 SHA256 2025 CA1, O="DigiCert, Inc.", C=US
   Signature algorithm: SHA256withRSA, 4096-bit key
   [certificate is valid from 5/7/25, 12:00 AM to 1/14/38, 11:59 PM]
   X.509, CN=DigiCert Trusted Root G4, OU=www.digicert.com, O=DigiCert Inc, C=US
   Signature algorithm: SHA384withRSA, 4096-bit key
   [certificate is valid from 8/1/22, 12:00 AM to 11/9/31, 11:59 PM] s = signature was verified
 m = entry is listed in manifest
 k = at least one certificate was found in keystore- Signed by "CN="Oracle America, Inc.", O="Oracle America, Inc.", L=Redwood City, ST=California, C=US"
  Digest algorithm: SHA-256
  Signature algorithm: SHA256withRSA, 3072-bit key
 Timestamped by "CN=DigiCert SHA256 RSA4096 Timestamp Responder 2025 1, O="DigiCert, Inc.", C=US" on Thu Oct 02 14:32:26 UTC 2025
  Timestamp digest algorithm: SHA-256
  Timestamp signature algorithm: SHA256withRSA, 4096-bit key
  Warning: nonexistent signed entries: [ora-launcher]jar verified.Warning:
POSIX file permission and/or symlink attributes detected. These attributes are ignored when signing and are not protected by the signature.
This jar contains signed entries for files that do not exist. See the -verbose output for more details.The signer certificate will expire on 2028-01-11.
The timestamp will expire on 2031-11-09.