Planning the Oracle Fusion Middleware Infrastructure Installation

1 Planning the Oracle Fusion Middleware Infrastructure Installation

There are a few steps you must take to prepare for an Oracle Fusion Middleware Infrastructure installation.

Review this section thoroughly to ensure that you don't encounter any problems during or after product 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 Fusion Middleware Infrastructure. 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 is 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 to Extend an Existing Domain

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

If you do this, see 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 don't match instructions in the procedure, be sure to make your selections accordingly and see supporting documentation for additional details.

Using this Document in an Upgrade Scenario

If you are installing Oracle Fusion Middleware Infrastructure as part of an upgrade procedure, follow steps in this guide to install the software, but don't run the Configuration Wizard to create a WebLogic domain.

After you install the software, see Plan the Upgrade in Oracle Fusion Middleware Upgrading WebLogic Server.

About Installing a Development Environment

This guide describes how to use the Oracle Fusion Middleware Infrastructure distribution to install and configure a standard installation topology as a starting point for a development environment.

To install an Oracle Fusion Middleware Infrastructure development environment, Oracle recommends that you download and install Oracle JDeveloper, which provides an integrated development environment (IDE), preconfigured with the design-time software to develop Java and Oracle ADF applications.

With Oracle JDeveloper, you can test your applications from within JDeveloper, using the integrated Oracle WebLogic Server.

Alternatively, you can use this guide to configure an Oracle Fusion Middleware Infrastructure domain to use as a runtime environment for your Java and Oracle ADF applications. You can then deploy your applications directly from JDeveloper to the Infrastructure domain. See Installing Oracle JDeveloper.

About the Infrastructure Standard Installation Topology

The standard installation topology for Oracle Fusion Middleware Infrastructure has a standard WebLogic Server domain that contains an Administration Server and a cluster with Managed Servers.

Figure 1-1 Oracle Fusion Middleware Infrastructure Standard Installation Topology

Description of "Figure 1-1 Oracle Fusion Middleware Infrastructure Standard Installation Topology"

This topology also includes:

Libraries and other software required to deploy and manage Oracle ADF applications that are installed and available on the Managed Servers.
The domain is configured on one host. It requires the supported database where Fusion Middleware schemas are installed. See About Certified Oracle Database and the Standard Installation Topology.

Continue to these topics on the standard installation topology:

About Certified Oracle Database and the Standard Installation Topology

For 14c (14.1.2.0.0), you must use a certified Oracle database for the Oracle Fusion Middleware Infrastructure standard installation topology.

This database (in About the Infrastructure Standard Installation Topology) is the Infrastructure database, which Fusion Middleware products access. Do not confuse the Infrastructure database with the internal application database, which applications that you deploy in your environment use. For examples, see the "Additional DB" tab in the certification document for your release on the Oracle Fusion Middleware Supported System Configurations page.

Oracle Fusion Middleware Infrastructure Standard Installation Topology Elements

A standard installation topology includes a set of elements.

The table describes elements in the topology figure (Understanding the Infrastructure Standard Installation Topology). See Roadmap for Installing and Configuring the Standard Installation Topology for a roadmap describing steps to create this topology.

Table 1-1 Oracle Fusion Middleware Infrastructure Standard Installation Topology Elements

Element	Description and Links to Additional Documentation
APPHOST	Standard term in Oracle documentation for the machine that hosts the application tier.
DBHOST	Standard term in Oracle documentation that refers to the machine that hosts the database.
WebLogic Domain	A 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	Central control entity of a domain which maintains the domain's configuration objects and distributes configuration changes to Managed Servers. See What is the Administration Server? in Understanding Oracle Fusion Middleware.
Enterprise Manager	Oracle Enterprise Manager Fusion Middleware Control, the main tool that you can use to manage your domain. See Oracle Enterprise Manager Fusion Middleware Control 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 resources. See Understanding Managed Servers and Managed Server Clusters in Understanding Oracle Fusion Middleware.
Infrastructure	Collection of services that includes: Metadata repository (MDS) Contains metadata for Oracle Fusion Middleware components, such as Oracle Application Developer Framework. See What is the Metadata Repository in Understanding Oracle Fusion Middleware. Oracle Application Developer Framework (ADF) Oracle Web Services Manager (OWSM)

Options after You Have a Standard Installation Topology

Use the Standard Installation Topology (SIT) as a starting point for other documents.

The High Availability Guide uses the Oracle HTTP Server and Infrastructure as a starting point for configuring the SIT for high availability.
For more information about the documentation roadmap and related high availability topologies, see Planning for a Production Environment in Planning an Installation of Oracle Fusion Middleware.

Roadmap for Installing and Configuring the Standard Installation Topology

There are a series of steps to install and configure a standard Oracle Fusion Middleware Infrastructure installation topology.

This document has all steps you need to install and configure the product. Within the steps, this guide refers to additional information to create a modified version of this topology.

The following table shows steps required to install and configure the topology.

Table 1-2 Oracle Fusion Middleware Infrastructure Installation Roadmap

Task	Description	Documentation
Verify your system environment	Before you begin the installation, verify that the minimum system and network requirements are met.	See Roadmap for Verifying Your System Environment.
Obtain the appropriate distribution	To create the topology described in this guide, obtain the Oracle Fusion Middleware Infrastructure distribution.	See Obtaining the Infrastructure Distribution.
Determine your installation directories	Verify that the installer can create or access the installer directories that need to be created. Also, verify that the directories exist on systems that meet the minimum requirements.	See What are the Key Oracle Fusion Middleware Directories? in Understanding Oracle Fusion Middleware.
Install the software	Run the installation program to install the software. This transfers software to your system and creates the Oracle home directory.	See Installing the Infrastructure Software.
Create a WebLogic domain	Use the configuration wizard to create and configure the WebLogic domain.	See Configuring the Oracle Fusion Middleware Infrastructure Domain.
Administer and prepare your domain for high availability	Discover additional tools and resources to administer your domain and configure your domain to be highly available.	See Next Steps After Configuring the Infrastructure 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 to make sure that your environment is ready for installing and configuring Oracle Fusion Middleware Infrastructure.

Table 1-3 Roadmap for Verifying Your System Environment

Task	Description	Documentation
Verify certification and system requirements.	Verify that your operating system is certified and properly configured for Oracle Fusion Middleware Infrastructure installation and configuration.	See Verifying Certification and System Requirements 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 installation and configuration directories on your system.	Verify that you can create required 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 requires a certified JDK present on your system.	See About JDK Requirements for an Oracle Fusion Middleware Installation.
Install and configure an Oracle database.	To configure a WebLogic domain, you must have access to a certified database that is properly configured for schemas that Oracle Fusion Middleware Infrastructure requires. 14c (14.1.2.0.0) requires a certified Oracle database.	See Installing and Configuring a Certified Database in Planning an Installation of Oracle Fusion Middleware.

Obtaining the Infrastructure Distribution

Before you obtain product distributions and run installers, verify that you have a certified JDK installed on your system.

See About JDK Requirements for an Oracle Fusion Middleware Installation.

To obtain Oracle Fusion Middleware Infrastructure:

Go to http://www.oracle.com/technetwork/developer-tools/adf/downloads/index.html. In the Oracle ADF Downloads section, select 14.1.2.0.0 from the Application Development Runtime field. Click Download File.
When your browser asks if you want to download the file fmw_14.1.2.0.0_infrastructure_Disk1_1of1.zip, download this file onto your system.
Extract the .zip file contents onto your system. The extracted file fmw_14.1.2.0.0_infrastructure_generic.jar runs the product installer and installs the software onto your system. See Installing the Infrastructure Software

To obtain Oracle Fusion Middleware software, see Understanding and Obtaining Product Distributions in Planning an Installation of Oracle Fusion Middleware.

To locate and download Oracle Fusion Middleware products, see Oracle Fusion Middleware Download, Installation, and Configuration Readme Files on OTN.

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.