Configuring a Default Persistence Store for Transaction Recovery Disabling Host Name Verification for the WLS_IPM Managed Servers
11. Click Save and Activate.
12. Repeat the steps and create IPMJMSServer2Store for IPMJMSServer2.
8.8 Configuring a Default Persistence Store for Transaction Recovery
Each server has a transaction log which stores information about committed transactions that are coordinated by the server that may not have been completed. The WebLogic Server uses this transaction log for recovery from system crashes or network failures. To leverage the migration capability of the Transaction Recovery Service for the servers within a cluster, store the transaction log in a location accessible to the server. Perform these steps to set the location for the default persistence store for WLS_IPM1: 1. Log in to the Oracle WebLogic Server Administration Console.2. In the Domain Structure window, expand the Environment node and then click
the Servers node. The Summary of Servers page opens. 3. Click WLS_IPM1 represented as a hyperlink in the Name column of the table. The settings page for the WLS_IPM1 server opens with the Configuration tab active.4. Click the Services tab.
5. Click Lock Edit.
6. In the Default Store section of the page, enter the path to the folder where the default persistent stores will store its data files. The directory structure of the path is as follows: ORACLE_BASE admindomain_nameipm_cluster_nametlogs7. Click Save and activate the changes.
8. Repeat the step for the WLS_IPM2 server.8.9 Disabling Host Name Verification for the WLS_IPM Managed Servers
This step is required if you have not set up the appropriate certificates to authenticate the different nodes with the Administration Server see Chapter 9, Setting Up Node Manager . If you have not configured the server certificates, you will receive errors when managing the different WebLogic Servers. To avoid these errors, disable host name verification while setting up and validating the topology, and enable it again once the EDG topology configuration is complete as described in Chapter 9, Setting Up Node Manager. Note: Preferably, this location should be a dual-ported SCSI disk or on a Storage Area Network SAN. Note: To enable migration of the Transaction Recovery Service, specify a location on a persistent storage solution that is available to other servers in the cluster. Both ECMHOST1 and ECMHOST2 must be able to access this directory. This directory must also exist before you restart the server. 8-10 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite Perform these steps to disable host name verification: 1. Log in to Oracle WebLogic Server Administration Console.2. In the Administration Console, select WLS_IPM1, then SSL, and then Advanced.
3. Click Lock Edit.
4. Set host name verification to None.5. In the Administration Console, select WLS_IPM2, then SSL, and then Advanced.
6. Set host name verification to None. 7. Save and activate the changes.8.10 Starting the Oracle IPM System
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