1 Planning the Oracle WebLogic Server Installation
- Using this Document
There are certain scenarios that you want to use this guide for, and other sources of information. - About the WebLogic Server and Coherence Standard Installation Topology
The standard installation topology has a standard WebLogic Server domain. - Running the Installer in Silent Mode
You can install using the-silent
flag on the command line when you start the installer. - 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. - 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. - Obtaining the Oracle WebLogic Server and Coherence Distribution
To download Oracle WebLogic Server and Coherence software for development or evaluation, go to theSoftware Downloads
page. - 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.
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. - 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. - 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. - 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.
Parent topic: Planning the Oracle WebLogic Server Installation
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.
Parent topic: Using this Document
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.
Parent topic: Using this Document
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.
Parent topic: Using this Document
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.
-
Installing the Oracle JDeveloper Software in Oracle Fusion Middleware Installing JDeveloper to install Oracle JDeveloper, an integrated development environment (IDE) for building applications using the latest Java, XML, Web services, and SQL standards.
Parent topic: Using this Document
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.
Parent topic: Planning the Oracle WebLogic Server Installation
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.
Parent topic: Planning the Oracle WebLogic Server Installation
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. |
|
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. |
|
Perform post-installation tasks |
Start to manage components in the domain or continue to modify your environment for high availability. |
Parent topic: Planning the Oracle WebLogic Server Installation
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 Fusion Middleware 14c (14.1.2.0.0) supports JDK version 17.0 or later, and JDK 21.0 or later. |
Parent topic: Planning the Oracle WebLogic Server Installation
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, fmw_14.1.2.0.0_wls_examples.jar
, which you install in the same ORACLE_HOME
as your WebLogic Server installation. For more information about obtaining and installing WebLogic Server see Installing the WebLogic Server Code Examples .
To obtain Oracle WebLogic Server and Coherence, follow these steps:
Parent topic: Planning the Oracle WebLogic Server Installation
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
For example, to check the Oracle Fusion Middleware Infrastructure archive:
jarsigner -verify fmw_14.1.2.0.0_infrastructure.jar
jar verified.
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
For example, to check the Oracle Fusion Middleware Infrastructure image:
jarsigner -verify -verbose:summary -certs fmw_14.1.2.0.0_infrastructure.jar
The output is similar to the following:
2237119 Fri Dec 6 07:02:30 UTC 2023 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 12/19/24 12:00 AM to 12/19/25 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/24 12:00 AM to 4/28/36 11:59 PM] X.509, CN=DigiCert Trusted Root G4, O=DigiCert Inc, C=US [ Signature algorithm: SHA384withRSA, 4096-bit key [trusted certificate] >>> TSA X.509, CN=DigiCert Timestamp 2024 - 2, O=DigiCert, C=US [ Signature algorithm: SHA256withRSA, 4096-bit key [certificate is valid from 9/21/24 12:00 AM to 11/21/33 11:59 PM] X.509, CN=DigiCert Trusted G4 RSA4096 SHA256 TimeStamping CA, O="DigiCert, Inc.", C=US [ Signature algorithm: SHA256withRSA, 4096-bit key [certificate is valid from 3/23/24 12:00 AM to 3/22/37 11:59 PM] X.509, CN=DigiCert Trusted Root G4, O=DigiCert Inc, C=US [ Signature algorithm: SHA384withRSA, 4096-bit key [certificate is valid from 8/1/24 12:00 AM to 11/9/31 11:59 PM] 2237281 Fri Feb 17 07:02:32 UTC 2024 META-INF/ORACLE_C.SF (and 1 more) (Signature related entries) 0 Fri Feb 17 05:41:24 UTC 2023 OPatch/ (and 1897 more) (Directory entries) 2977 Tue Dec 20 08:02:16 UTC 2024 OPatch/README.txt (and 20199 more) [entry was signed on 2/17/24 7:02 AM] >>> 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 8/19/24 12:00 AM to 8/19/25 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/24 12:00 AM to 4/28/36 11:59 PM] X.509, CN=DigiCert Trusted Root G4, O=DigiCert Inc, C=US [ Signature algorithm: SHA384withRSA, 4096-bit key [trusted certificate] >>> TSA X.509, CN=DigiCert Timestamp 2024 - 2, O=DigiCert, C=US [ Signature algorithm: SHA256withRSA, 4096-bit key [certificate is valid from 9/21/24 12:00 AM to 11/21/33 11:59 PM] X.509, CN=DigiCert Trusted G4 RSA4096 SHA256 TimeStamping CA, O="DigiCert, Inc.", C=US [ Signature algorithm: SHA256withRSA, 4096-bit key [certificate is valid from 3/23/24 12:00 AM to 3/22/37 11:59 PM] X.509, CN=DigiCert Trusted Root G4, O=DigiCert Inc, C=US [ Signature algorithm: SHA384withRSA, 4096-bit key [certificate is valid from 8/1/24 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 i = at least one certificate was found in identity scope - 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 Timestamp 2024 - 2, O=DigiCert, C=US" on Fri Feb 17 07:02:33 UTC 2024 Timestamp digest algorithm: SHA-256 Timestamp signature algorithm: SHA256withRSA, 4096-bit key jar verified. The signer certificate will expire on 2025-12-19. The timestamp will expire on 2031-11-09.
Parent topic: Planning the Oracle WebLogic Server Installation