Configuring the Java Object Cache for Oracle Web Services Manager
6.11 Configuring the Java Object Cache for Oracle Web Services Manager
The Java Object Cache JOC should be configured among all the servers running Oracle Web Services Manager WSM. This local cache is provided to increase the performance of Oracle WSM. The Java Object Cache can be configured using the MW_ HOMEoracle_commonbinconfigure-joc.py script. This is a Python script which can be used to configure JOC in the managed servers. The script runs in WLST online mode and expects the Administration Server to be up and running. When configuring JOC ports for Oracle products, Oracle recommends using ports in the 9988 to 9998 range. Perform these steps to configure the Java Object Cache for Oracle WSM: 1. Connect to the Administration Server using the command-line Oracle WebLogic Scripting Tool WLST, for example: MW_HOME oracle_commoncommonbinwlst.sh connect Enter the server URL, Oracle Weblogic Administration user name and password when prompted. 2. After connecting to the Administration Server using wlst, start the script using the execfile command, for example: wls:mydomainserverConfigexecfileMW_HOMEoracle_commonbin configure-joc.py Specifically, for EDG environments, the first cluster option in step 2 should be used. Here is a walkthrough for using configure-joc.py for EDG environments see below for the script input parameters: ExecfileMW_HOMEoracle_commonbinconfigure-joc.py. Enter Hostnames eg host1,host2 : SOAHOST1VHN1, SOAHOST2VHN1 . Do you want to specify a cluster name yn yy . Enter Cluster Name : SOA_Cluster . Enter Discover Port : 9991 . Enter Distribute Mode true|false true : true . Do you want to exclude any servers from JOC configuration yn n n You can also configure the Java Object Cache JOC using the HA Power Tools tab in the Oracle WebLogic Administration Console as described in the Oracle Fusion Middleware High Availability Guide. Note: After configuring the Java Object Cache using the wlst commands or configure-joc.py script, all affected managed servers should be restarted for the configurations to take effect. Extending the Domain with SOA Components 6-15 Script Input Parameters The input parameters are prompted by the script. The script can be used to perform the following JOC configurations: ■ Configure JOC for all specified managed servers for a given cluster. Enter y when the script prompts whether you want to specify a cluster name, and also specify the cluster name and discover port, when prompted. This discovers all the managed servers for the given cluster and configures the JOC. The discover port is common for the entire JOC configuration across the cluster. For example: Do you want to specify a cluster name yn y Enter Cluster Name : SOA_Cluster Enter Discover Port : 9991 ■ Configure JOC for all specified managed servers. Enter n when the script prompts whether you want to specify a cluster name, and also specify the managed server and discover port, when prompted. For example: Do you want to specify a cluster name yn yn Enter Managed Server and Discover Port eg WLS_SOA1:9991, WLS_SOA21:9991 : WLS_SOA1:9999,WLS_SOA2:9999 This example configures JOC only for the specified managed servers that is, WLS_SOA1 and WLS_SOA2. The discover port is specified with the managed server for example, WLS_SOA1:2222. ■ Exclude JOC configuration for some managed servers. The script allows you to specify the list of managed servers for which the JOC configuration DistributeMode will be set to false. Enter y when the script prompts whether you want to exclude any servers from JOC configuration, and enter the managed server names to be excluded, when prompted. For example: Do you want to exclude any servers from JOC configuration yn ny Exclude Managed Server List eg Server1,Server2 : WLS_SOA1,WLS_SOA2 ■ Disable the distribution mode for all managed servers. The script allows you to disable the distribution to all the managed servers for a specified cluster. Specify false when the script prompts for the distribution mode. By default, the distribution mode is set to true.6.12 Configuring Oracle HTTP Server for the WLS_SOA Managed Servers
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