1/15
Contents
Title and Copyright Information
Preface
Audience
Documentation Accessibility
Related Documents
Conventions
1
Enterprise Deployment Overview
1.1
What is an Enterprise Deployment?
1.2
Terminology
1.3
Benefits of Oracle Recommendations
1.3.1
Built-in Security
1.3.2
High Availability
1.4
Hardware Requirements
1.5
Enterprise Deployment Reference Topology
1.5.1
Oracle Identity Management
1.5.2
Web Tier
1.5.2.1
Load Balancer Requirements
1.5.3
Application Tier
1.5.4
Data Tier
1.5.5
What to Install
1.5.6
Unicast Requirement
1.6
How to Use This Guide
1.6.1
Installation and Configuration Procedure
1.6.2
Overview of Installation Strategies
2
Database and Environment Preconfiguration
2.1
Database
2.1.1
Setting Up the Database
2.1.1.1
Database Host Requirements
2.1.1.2
Supported Database Versions
2.1.1.3
Initialization Parameters
2.1.1.4
Database Services
2.1.2
Loading the Oracle Fusion Metadata Repository in the RAC Database
2.1.3
Backing Up the Database
2.2
Network
2.2.1
Virtual Server Names
2.2.1.1
soa.mycompany.com
2.2.1.2
admin.mycompany.com
2.2.1.3
soainternal.mycompany.com
2.2.2
Load Balancers
2.2.2.1
Configuring the Load Balancer
2.2.3
IPs and Virtual IPs
2.2.4
Firewalls and Ports
2.3
Shared Storage and Recommended Directory Structure
2.3.1
Terminology for Directories and Directory Environment Variables
2.3.2
Recommended Locations for the Different Directories
2.3.3
Shared Storage Configuration
3
Installing Oracle HTTP Server
3.1
Installing Oracle HTTP Server on WEBHOST1 and WEBHOST2
3.2
Validating Oracle HTTP Server Through the Load Balancer
3.3
Backing Up Oracle HTTP Server
4
Creating a Domain
4.1
Installing Oracle Fusion Middleware Home
4.1.1
Installing Oracle WebLogic Server
4.1.2
Installing Oracle Fusion Middleware for SOA
4.2
Backing Up the Installation
4.3
Enabling SOAHOST1VHN1 on SOAHOST1
4.4
Running the Configuration Wizard on SOAHOST1 to Create a Domain
4.5
Creating a Separate Domain Directory for Managed Servers in the Same Node as the Administration Server
4.6
Creating boot.properties for the Administration Server on SOAHOST1
4.7
Starting the Administration Server on SOAHOST1
4.8
Validating the Administration Server
4.9
Disabling Host Name Verification for the Oracle WebLogic Administration Server and the WLS_WSM1 Managed Server
4.10
Starting Node Manager on SOAHOST1
4.11
Starting and Validating the WLS_WSM1 Managed Server
4.12
Propagating the Domain Configuration to SOAHOST2 Using the unpack Utility
4.13
Disabling Host Name Verification for the WLS_WSM2 Managed Server
4.14
Starting Node Manager on SOAHOST2
4.15
Starting and Validating the WLS_WSM2 Managed Server
4.16
Configuring Oracle HTTP Server for the Administration Server and the WLS_WSM-PM
n
Managed Servers
4.17
Registering Oracle HTTP Server With WebLogic Server
4.18
Setting the Frontend URL for the Administration Console
4.19
Validating Access Through Oracle HTTP Server
4.20
Manually Failing Over the Administration Server to SOAHOST2
4.21
Validating Access to SOAHOST2 Through Oracle HTTP Server
4.22
Failing the Administration Server Back to SOAHOST1
4.23
Backing Up the Installation
5
Extending the Domain for SOA Components
5.1
Enabling SOAHOST1VHN2 and SOAHOST2VHN1
5.2
Extending the Domain for SOA Components
5.3
Restarting the Administration Server
5.4
Configuring Oracle Coherence for Deploying Composites
5.5
Running the soa-createUDD.py Script
5.6
Disabling Host Name Verification for the WLS_SOA
n
Managed Server
5.7
Restarting the Node Manager on SOAHOST1
5.8
Propagating the Domain Changes to the Managed Server Domain Directory
5.9
Starting the WLS_SOA1 Managed Server on SOAHOST1
5.10
Validating the WLS_SOA1 and WLS_WSM1 Managed Servers
5.11
Propagating the Domain Configuration to SOAHOST2 Using the unpack Utility
5.12
Extracting the XEngine Files in SOAHOST2
5.13
Restarting Node Manager on SOAHOST2
5.14
Starting and Validating the WLS_SOA2 Managed Server
5.15
Configuring Oracle HTTP Server for the WLS_SOA
n
Managed Servers
5.16
Validating Access Through Oracle HTTP Server
5.17
Setting the Frontend HTTP Host and Port
5.18
Configuring a Shared JMS Persistence Store
5.19
Configuring a Default Persistence Store for Transaction Recovery
5.20
Enabling High Availability for Oracle File and FTP Adapters
5.20.1
Using the Database Mutex Locking Operation
5.21
Scaling the Oracle Database Adapter
5.22
Backing Up the Installation
6
Extending the Domain to Include BAM
6.1
Overview of Adding BAM to a Domain
6.2
Extending the Domain to Include BAM
6.2.1
Restarting the Administration Server
6.2.2
Configuring the Cache Size for BAM JDBC Data Sources
6.3
Running the soa-createUDD.py Script
6.4
Configuring a JMS Persistence Store for BAM UMS
6.5
Configuring a Default Persistence Store for Transaction Recovery
6.6
Untargeting the BAM Server System from WLS_BAM2
6.7
Propagating the Domain Configuration to BAMHOST1 and BAMHOST2 Using the pack/unpack Utility
6.8
Disabling Host Name Verification for the WLS_BAM
n
Managed Servers
6.9
Starting Node Manager on BAMHOST1 and BAMHOST2
6.10
Starting the BAM System
6.11
Configuring the BAM Web Applications to Use the BAM Server in BAMHOST1
6.12
Configuring the ADCServer to Use the Appropriate BAMServer Address
6.13
Configuring Oracle HTTP Server for the WLS_BAM
n
Managed Servers
6.14
Validating Access Through Oracle HTTP Server
6.15
Configuring Server Migration for the WLS_BAM Servers
6.15.1
Setting Up the User and Tablespace for the Server Migration Leasing Table
6.15.2
Creating a Multi-Data Source from the WebLogic Server Administration Console
6.15.3
Enabling Host Name Verification Certificates Between Node Manager in the BAMHOST
n
Nodes and the Administration Server
6.15.4
Editing the Node Manager's Properties File
6.15.5
Set Environment and Superuser Privileges for the wlsifconfig.sh Script
6.15.6
Configure Server Migration Targets
6.15.7
Test Server Migration
6.16
Backing Up the Installation
7
Setting Up Node Manager
7.1
About the Node Manager
7.2
Enabling Host Name Verification Certificates for Node Manager in SOAHOST1
7.2.1
Generating Self-Signed Certificates Using the utils.CertGen Utility
7.2.2
Creating an Identity Keystore Using the utils.ImportPrivateKey Utility
7.2.3
Creating a Trust Keystore Using the keytool Utility
7.2.4
Configuring Node Manager to Use the Custom Keystores
7.3
Starting the Node Manager on SOAHOST1
7.4
Enabling Host Name Verification Certificates for the Node Manager in SOAHOST2
7.4.1
Generating Self-Signed Certificates Using the utils.CertGen Utility
7.4.2
Creating an Identity Keystore Using the "utils.ImportPrivateKey" Utility
7.4.3
Creating a Trust Keystore Using the keytool Utility
7.4.4
Configuring Node Manager to Use the Custom Keystores
7.5
Starting the Node Manager on SOAHOST2
8
Server Migration
8.1
Setting Up a User and Tablespace for the Server Migration Leasing Table
8.2
Creating a Multi-Data Source Using the Oracle WebLogic Server Administration Console
8.3
Enabling Host Name Verification Certificates between SOAHOST1 and SOAHOST2 and the Administration Server
8.4
Editing the Node Manager's Properties File
8.5
Setting Environment and Superuser Privileges for the wlsifconfig.sh Script
8.6
Configuring Server Migration Targets
8.7
Testing the Server Migration
9
Integration With Oracle Identity Management
9.1
Overview of Oracle Access Manager Integration
9.2
Prerequisites for Oracle Access Manager
9.3
Using the OAM Configuration Tool
9.3.1
Collecting the Information for the OAM Configuration Tool
9.3.2
Running the OAM Configuration Tool
9.3.3
Verifying Successful Creation of the Policy Domain and Access Gate
9.3.4
Updating the Host Identifier
9.3.5
Updating the WebGate Profile
9.3.6
Configuring Delegated Form Authentication
9.4
Installing and Configuring WebGate
9.5
Setting Up the WebLogic Authenticators
9.5.1
Setting Up the OID Authenticator
9.5.1.1
Back Up Configuration Files
9.5.1.2
Identity Store
9.5.2
Setting Up the OAM ID Asserter
9.5.3
Setting the Order of Providers
9.6
Changing the Login Form for the Administration Console Application
9.7
Moving the WebLogic Administrator to LDAP
9.8
Backing Up the Installation
10
Managing the Topology
10.1
Monitoring the Topology
10.2
Deploying Composites and Artifacts in SOA Enterprise Deployment Topology
10.3
Configuring UMS Drivers
10.4
Scaling the Topology
10.4.1
Scaling Up the Topology (Adding Managed Servers to Existing Nodes)
10.4.2
Scaling Out the Topology (Adding Managed Servers to New Nodes)
10.5
Performing Backups and Recoveries
10.6
Troubleshooting
10.6.1
Access to BAM Results in HTTP Error 404
10.6.2
Page Not Found When Accessing soa-infra Application Through Load Balancer
10.6.3
Error While Retrieving Oracle B2B Document Definitions
10.6.4
Soa-infra Application Fails to Start Due to Deployment Framework Issues (Coherence)
10.6.5
Incomplete Policy Migration After Failed Restart of SOA Server
10.6.6
SOA, BAM, or WMS Servers Fail to Start Due to Maximum Number of Processes Available in Database
10.6.7
Admin Server Fails to Start After a Manual Failover
10.6.8
Error While Activating Changes in Administration Console
10.6.9
SOA/BAM Server Not Failed Over After Server Migration
10.6.10
SOA/BAM Server Not Reachable From Browser After Server Migration
10.6.11
SOA Server Stops Responding after Being Active and Stressed for a Period of Time
10.6.12
Exceptions While Performing Deploy/Purge/Import Operations in the B2B Console
10.6.13
OAM Configuration Tool Does Not Remove URLs
10.6.14
Redirecting of Users to Login Screen After Activating Changes in Administration Console
10.6.15
Redirecting of Users to Administration Console's Home Page After Activating Changes to OAM
10.7
Best Practices
10.7.1
Preventing Timeouts for SQLNet Connections
10.7.2
Setting AUTOEXTEND for Tablespaces for Processing More Than 30,000 Files
10.7.3
Auditing
11
Miscellaneous
11.1
Recovering Failed BPEL and Mediator Instances
11.2
Configuring Security in Web Services
11.3
Running the SOA Fusion Order Demo Application in an EDG Environment
11.4
Oracle Business Activity Monitoring (BAM) Configuration Properties
11.5
Using Shared Storage for Deployment Plans and SOA Infrastructure Applications Updates
Index
Scripting on this page enhances content navigation, but does not change the content in any way.