Skip Headers
Oracle® Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite
11
g
Release 1 (11.1.1)
Part Number E12036-07
Home
Book List
Index
Master Index
Contact Us
Next
View PDF
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 Oracle RAC Database
2.1.3
Configuring SOA Schemas for Transactional Recovery Privileges
2.1.4
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
2.4
LDAP as Credential and Policy Store
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 VIP1 in SOAHOST1
4.4
Running the Configuration Wizard on SOAHOST1 to Create a Domain
4.5
Creating boot.properties for the Administration Server on SOAHOST1
4.6
Starting Node Manager on SOAHOST1
4.7
Starting the Administration Server on SOAHOST1
4.8
Validating the Administration Server
4.9
Creating a Separate Domain Directory for Managed Servers in the Same Node as the Administration Server
4.10
Applying the Java Required Files (JRF) Template to the WSM-PM_Cluster
4.11
Disabling Host Name Verification for the Oracle WebLogic Administration Server and the WLS_WSM1 Managed Server
4.12
Starting and Validating the WLS_WSM1 Managed Server
4.13
Propagating the Domain Configuration to SOAHOST2 Using the unpack Utility
4.14
Disabling Host Name Verification for the WLS_WSM2 Managed Server
4.15
Starting Node Manager on SOAHOST2
4.16
Starting and Validating the WLS_WSM2 Managed Server
4.17
Configuring the Java Object Cache for Oracle WSM
4.18
Configuring Oracle HTTP Server for the Administration Server and the WLS_WSM-PM
n
Managed Servers
4.19
Registering Oracle HTTP Server With WebLogic Server
4.20
Setting the Frontend URL for the Administration Console and Setting Redirection Preferences
4.21
Validating Access Through Oracle HTTP Server
4.22
Manually Failing Over the Administration Server to SOAHOST2
4.23
Validating Access to SOAHOST2 Through Oracle HTTP Server
4.24
Failing the Administration Server Back to SOAHOST1
4.25
Backing Up the Installation
5
Extending the Domain for SOA Components
5.1
Enabling VIP2 on SOAHOST1 and VIP3 on SOAHOST2
5.2
Extending the Domain for SOA Components
5.3
Restarting the Administration Server
5.4
Configuring Oracle Coherence for Deploying Composites
5.5
Setting Connection Destination Identifiers for B2B Queues
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 Managed Server
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
Setting the WLS Cluster address for Direct Binding/RMI invocations to composites
5.19
Configuring a Shared JMS Persistence Store
5.20
Configuring a Default Persistence Store for Transaction Recovery
5.21
Enabling High Availability for Oracle File and FTP Adapters
5.21.1
Using the Database Mutex Locking Operation
5.22
Update the B2B Instance Identifier for transports
5.23
Scaling the Oracle Database Adapter
5.24
Backing Up the Installation
6
Extending the Domain to Include Oracle BPM
6.1
Option 1: Extending a Domain to Include SOA and BPM
6.1.1
Backing Up the Existing Installation
6.1.2
Enabling VIP2 on SOAHOST1 and VIP3 on SOAHOST2
6.1.3
Running the Configuration Wizard on SOAHOST1 to Extend the Current Domain
6.1.4
Configuring Oracle Coherence for Deploying Composites
6.1.5
Setting Connection Destination Identifiers for B2B Queues
6.1.6
Disabling Host Name Verification for the WLS_SOA1, WLS_SOA2, Managed Servers
6.1.7
Propagating the Domain Changes to the Managed Server Domain Directory
6.1.8
Starting and Validating the WLS_SOA1 Managed Server
6.1.9
Propagating the Domain Configuration to SOAHOST2 Using the Unpack Utility
6.1.10
Extracting the XEngine Files in SOAHOST2
6.1.11
Starting and Validating the WLS_SOA2 Managed Server
6.1.12
Configuring Oracle HTTP Server for WLS_SOA
n
Managed Servers
6.1.13
Validating Access Through Oracle HTTP Server
6.1.14
Setting the Frontend HTTP Host and Port
6.1.15
Setting the WLS Cluster address for Direct Binding/RMI invocations to composites
6.1.16
Configuring a Shared JMS Persistence Store
6.1.17
Configuring a Default Persistence Store for Transaction Recovery
6.1.18
Enabling High Availability for Oracle File and FTP Adapters
6.1.18.1
Using the Database Mutex Locking Operation
6.1.19
Scaling the Oracle Database Adapter
6.1.20
Backing Up the Installation
6.2
Option 2: Extending a SOA Domain to Include Oracle BPM
6.2.1
Backing Up the Existing Installation
6.2.2
Running the Configuration Wizard on SOAHOST1 to Extend a SOA Domain to Include BPM
6.2.3
Configuring a JMS Persistence Store for BPM JMS
6.2.4
Propagating the Domain Configuration to the managed server directory in SOAHOST1 and to SOAHOST2
6.2.5
Starting the BPM Suite Components
6.2.6
Validating the BPM Suite Components in WLS_SOA1 and WLS_SOA2
6.2.7
Configuring Oracle HTTP Server for the WLS_SOA
n
Managed Servers
6.2.8
Validating Access Through Oracle HTTP Server
6.2.9
Backing Up the Installation
7
Extending the Domain to Include BAM
7.1
Overview of Adding BAM to a Domain
7.2
Enabling VIP4 in BAMHOST1
7.3
Extending the Domain to Include BAM
7.3.1
Restarting the Administration Server
7.4
Configuring a JMS Persistence Store for BAM UMS
7.5
Configuring a Default Persistence Store for Transaction Recovery
7.6
Untargeting the BAM Server System from WLS_BAM2
7.7
Propagating the Domain Configuration to BAMHOST1 and BAMHOST2 Using the pack/unpack Utility
7.8
Disabling Host Name Verification for the WLS_BAM
n
Managed Servers
7.9
Starting Node Manager on BAMHOST1 and BAMHOST2
7.10
Starting the BAM System
7.11
Configuring the BAM Web Applications to Use the BAM Server in BAMHOST1
7.12
Configuring Oracle HTTP Server for the WLS_BAM
n
Managed Servers
7.13
Validating Access Through Oracle HTTP Server
7.14
Configuring Server Migration for the WLS_BAM1 Server
7.14.1
Setting Up the User and Tablespace for the Server Migration Leasing Table
7.14.2
Creating a Multi-Data Source from the WebLogic Server Administration Console
7.14.3
Editing the Node Manager's Properties File
7.14.4
Set Environment and Superuser Privileges for the wlsifconfig.sh Script
7.14.5
Enabling Host Name Verification Certificates Between Node Manager in the BAMHOST
n
Nodes and the Administration Server
7.14.6
Configure Server Migration Targets
7.14.7
Test Server Migration
7.15
Configuration Changes Applied to BAM components in an Enterprise Deployment Topology
7.16
Accessing an Oracle BAM Server Using the BAM Adapter
7.17
Backing Up the Installation
8
Setting Up Node Manager
8.1
About the Node Manager
8.2
Changing the Location of Node Manager Log
8.3
Enabling Host Name Verification Certificates for Node Manager in SOAHOST1
8.3.1
Generating Self-Signed Certificates Using the utils.CertGen Utility
8.3.2
Creating an Identity Keystore Using the utils.ImportPrivateKey Utility
8.3.3
Creating a Trust Keystore Using the Keytool Utility
8.3.4
Configuring Node Manager to Use the Custom Keystores
8.4
Starting the Node Manager on SOAHOST1
8.5
Enabling Host Name Verification Certificates for the Node Manager in SOAHOST2
8.5.1
Generating Self-Signed Certificates Using the utils.CertGen Utility
8.5.2
Importing Identities in SOAHOST2 using the "utils.ImportPrivateKey" Utility
8.5.3
Configuring Node Manager to Use the Custom Keystores
8.6
Starting the Node Manager on SOAHOST2
8.7
Configuring WebLogic Servers to Use the Custom Keystores
9
Server Migration
9.1
Setting Up a User and Tablespace for the Server Migration Leasing Table
9.2
Creating a Multi-Data Source Using the Oracle WebLogic Server Administration Console
9.3
Enabling Host Name Verification Certificates between SOAHOST1 and SOAHOST2 and the Administration Server
9.4
Editing the Node Manager's Properties File
9.5
Setting Environment and Superuser Privileges for the wlsifconfig.sh Script
9.6
Configuring Server Migration Targets
9.7
Testing the Server Migration
10
Managing the Topology
10.1
Monitoring the Topology
10.2
Deploying Composites and Artifacts in SOA Enterprise Deployment Topology
10.3
Managing Space in the SOA Infrastructure Database
10.4
Configuring UMS Drivers
10.5
Scaling the Topology
10.5.1
Scaling Up the Topology (Adding Managed Servers to Existing Nodes)
10.5.2
Scaling Out the Topology (Adding Managed Servers to New Nodes)
10.6
Performing Backups and Recoveries
10.7
Troubleshooting
10.7.1
Access to BAM Results in HTTP Error 404
10.7.2
Page Not Found When Accessing soa-infra Application Through Load Balancer
10.7.3
Error While Retrieving Oracle B2B Document Definitions
10.7.4
Soa-infra Application Fails to Start Due to Deployment Framework Issues (Coherence)
10.7.5
Incomplete Policy Migration After Failed Restart of SOA Server
10.7.6
SOA, BAM, or WMS Servers Fail to Start Due to Maximum Number of Processes Available in Database
10.7.7
Administration Server Fails to Start After a Manual Failover
10.7.8
Error While Activating Changes in Administration Console
10.7.9
SOA/BAM Server Not Failed Over After Server Migration
10.7.10
SOA/BAM Server Not Reachable From Browser After Server Migration
10.7.11
SOA Server Stops Responding after Being Active and Stressed for a Period of Time
10.7.12
Exceptions While Performing Deploy/Purge/Import Operations in the B2B Console
10.7.13
OAM Configuration Tool Does Not Remove URLs
10.7.14
Redirecting of Users to Login Screen After Activating Changes in Administration Console
10.7.15
Redirecting of Users to Administration Console's Home Page After Activating Changes to OAM
10.7.16
Configured JOC Port Already in Use
10.7.17
SOA or BAM Server Fails to Start
10.8
Best Practices
10.8.1
Preventing Timeouts for SQLNet Connections
10.8.2
Auditing
11
Integration With Oracle Identity Management
11.1
Credential and Policy Store Configuration
11.1.1
Overview of Credential and Policy Store Configuration
11.1.2
Credential Store Configuration
11.1.2.1
Creating the LDAP Authenticator
11.1.2.2
Moving the WebLogic Administrator to LDAP
11.1.2.3
Reassociating the Domain Credential Store
11.1.3
Policy Store Configuration
11.1.3.1
Prerequisites to Using an LDAP-Based Policy Store
11.1.3.2
Reassociating the Domain Policy Store
11.1.4
Reassociation of Credentials and Policies
11.1.4.1
Cataloging Oracle Internet Directory Attributes
11.2
Oracle Access Manager 10g Integration
11.2.1
Overview of Oracle Access Manager Integration
11.2.2
Prerequisites for Oracle Access Manager
11.2.3
Using the OAM Configuration Tool
11.2.3.1
Collecting the Information for the OAM Configuration Tool
11.2.3.2
Running the OAM Configuration Tool
11.2.3.3
SOA Composite Applications and Oracle Access Manager Logout Guidelines
11.2.3.4
Verifying Successful Creation of the Policy Domain and AccessGate
11.2.3.5
Updating the Host Identifier
11.2.3.6
Updating the WebGate Profile
11.2.3.7
Adding Additional Access Servers
11.2.3.8
Configuring Delegated Form Authentication
11.2.4
Installing and Configuring WebGate
11.2.5
Changing the CacheControl Headers in the SOA_EDG_AG for Oracle BAM
11.2.6
Configuring IP Validation for the Webgate
11.2.7
Setting Up WebLogic Authenticators
11.2.7.1
Back Up Configuration Files
11.2.7.2
Setting Up the OAM ID Asserter
11.2.7.3
Setting the Order of Providers
11.3
Oracle Access Manager 11g Integration
11.3.1
Overview of Oracle Access Manager Integration
11.3.2
Prerequisites for Oracle Access Manager
11.3.3
Install WebGate
11.3.3.1
Installing GCC Libraries
11.3.3.2
Installing WebGate
11.3.3.3
Post-Installation Steps
11.3.4
Register the WebGate Agent
11.3.4.1
The RREG Tool
11.3.4.2
Updating the OAM11gRequest file
11.3.4.3
Running the oamreg tool
11.3.4.4
Copy Access files to WEBHOSTs
11.3.5
Set Role Members for BPMWorkflowAdmin Application Role in soa-infra
11.3.6
Setting Up the WebLogic Authenticators
11.3.6.1
Back Up Configuration Files
11.3.6.2
Setting Up the OAM ID Asserter
11.3.6.3
Setting the Order of Providers
11.4
Backing Up the Installation
12
Miscellaneous
12.1
Recovering Failed BPEL and Mediator Instances
12.2
Configuring Web Services to Prevent Denial of Service and Recursive Node Attacks
12.3
Running the SOA Fusion Order Demo Application in an Enterprise Deployment Environment
12.4
Oracle Business Activity Monitoring (BAM) Configuration Properties
12.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.