Shared Storage Configuration Shared Storage and Recommended Directory Structure
2.3.3 Shared Storage Configuration
The following steps show to create and mount shared storage locations so that SOAHOST1 and SOAHOST2 can see the same location for binary installation in two separate volumes. nasfiler is the shared storage filer. From SOAHOST1: SOAHOST1 mount nasfiler:volvol1u01apporacleproductfmw u01apporacle productfmw -t nfs Table 2–5 Contents of Shared Storage Server Type of Data Volume in Shared Storage Directory Files WLS_SOA1 Tx Logs VOL1 ORACLE_BASEadmindomain_ namesoa_cluster_nametlogs The transaction directory is common decided by WebLogic Server, but the files are separate. WLS_SOA2 Tx Logs VOL1 ORACLE_BASEadmindomain_ namesoa_cluster_nametlogs The transaction directory is common decided by WebLogic Server, but the files are separate. WLS_SOA1 JMS Stores VOL1 ORACLE_BASEadmindomain_ namesoa_cluster_namejms The transaction directory is common decided by WebLogic Server, but the files are separate; for example: SOAJMSStore1, UMSJMSStore1, and so on. WLS_SOA2 JMS Stores VOL1 ORACLE_BASEadmindomain_ namesoa_cluster_namejms The transaction directory is common decided by WebLogic Server, but the files are separate; for example: SOAJMSStore2, UMSJMSStore2, etc. WLS_SOA1 WLS Install VOL1 MW_HOME Individual in each volume, but both servers see same directory structure. WLS_SOA2 WLS Install VOL2 MW_HOME Individual in each volume, but both servers see same directory structure. WLS_SOA1 SOA Install VOL1 MW_HOMEsoa Individual in each volume, but both servers see same directory structure. WLS_SOA2 SOA Install VOL2 MW_HOMEsoa Individual in each volume, but both servers see same directory structure. WLS_SOA1 Domain Config VOL1 ORACLE_BASEadmindomain_ namemserverdomain_name Individual in each volume, but both servers see same directory structure. WLS_SOA2 Domain Config VOL2 ORACLE_BASEadmindomain_ namemserverdomain_name Individual in each volume, but both servers see same directory structure. Database and Environment Preconfiguration 2-21 From SOAHOST2: SOAHOST2 mount nasfiler:volvol2u01apporacleproductfmw u01apporacle productfmw -t nfs If only one volume is available, users can provide redundancy for the binaries by using two different directories in the shared storage and mounting them to the same dir in the SOA Servers: From SOAHOST1: SOAHOST1 mount nasfiler:volvol1u01apporacleproductfmw1 u01apporacle productfmw -t nfs From SOAHOST2: SOAHOST2 mount nasfiler:volvol2u01apporacleproductfmw2 u01apporacle productfmw -t nfs The following commands show how to share the SOA TX logs location across different nodes: SOAHOST1 mount nasfiler:volvol1u01apporaclestoressoadomainsoa_cluster tlogs u01apporaclestoressoadomainsoa_clustertlogs -t nfs SOAHOST2 mount nasfiler:volvol1u01apporaclestoressoadomainsoa_cluster tlogs u01apporaclestoressoadomainsoa_clustertlogs -t nfs2.4 LDAP as Credential and Policy Store
Parts
» Oracle Fusion Middleware Online Documentation Library
» What Is an Enterprise Deployment? About Oracle Enterprise Content Management Suite
» Built-In Security High Availability
» Terminology Oracle Fusion Middleware Online Documentation Library
» Oracle Identity Management Web Tier
» Abbreviations Hardware Requirements What to Install
» Installation Procedure Oracle Fusion Middleware Online Documentation Library
» Database Host Requirements Supported Database Versions Initialization Parameters
» Loading the Oracle Fusion Middleware Metadata Repository in the Oracle RAC Database
» ecm.mycompany.com admin.mycompany.com soainternal.mycompany.com ecminternal.mycompany.com
» IPs and Virtual IPs Firewalls and Ports
» Terminology for Directories and Directory Environment Variables
» Recommended Locations for the Different Directories
» Shared Storage Configuration Shared Storage and Recommended Directory Structure
» LDAP as Credential and Policy Store
» Configuring the Oracle Web Tier
» Enabling ADMINVHN on SOAHOST1 Running the Configuration Wizard on SOAHOST1 to Create a Domain
» Configuring Oracle HTTP Server for the Administration Server
» Assumptions and Procedure Manually Failing Over the Administration Server to SOAHOST2
» Validating Access Through Oracle HTTP Server Backing Up the Installation
» Configuring Oracle Coherence for Deploying Composites
» Configuring the Java Object Cache for Oracle Web Services Manager
» Configuring Oracle HTTP Server for the WLS_SOA Managed Servers
» Setting the Frontend HTTP Host and Port Validating Access Through Oracle HTTP Server
» Enabling High Availability for Oracle File and FTP Adapters
» About Adding Oracle UCM to a Domain Extending the Domain to Include Oracle UCM
» Restarting the Administration Server Configuring a JMS Persistence Store for Oracle IPM JMS
» Configuring BPEL CSF Credentials
» About Setting Up Node Manager
» Generating Self-Signed Certificates Using the utils.CertGen Utility
» Configuring Node Manager to Use the Custom Keystores
» Configuring Managed WLS Servers to Use the Custom Keystores
» Testing the Server Migration
» Create an LDIF file assumed to be jpstestnode.ldif in this example
» Cataloging Oracle Internet Directory Attributes
» Overview of Oracle Access Manager Integration Prerequisites for Oracle Access Manager
» Running the OAM Configuration Tool
» Installing and Configuring WebGate
» Back Up Configuration Files Setting the Order of Providers
» Move to the following directory under your Oracle Home for Webgate:
» Updating the OAM11gRequest File
» Monitoring the Topology Defining an Optimal Input File Strategy for Oracle IPM
» Configuring UMS Drivers Oracle Fusion Middleware Online Documentation Library
» Choose the Automatic Server Migration Enabled option. This enables Node Click Save.
» Performing Backups and Recoveries
» Page Not Found When Accessing soa-infra Application Through Load Balancer
Show more