Contents

Title and Copyright Information

Preface

• Audience
• Documentation Accessibility
• Related Documents
• Conventions

What's New in the Oracle Application Server Release Notes?

• Chapter 2, "Installation Issues"
• Chapter 3, "General Management and Security Issues"
• Chapter 4, "Oracle HTTP Server"
• Chapter 9, "Oracle Containers for J2EE"

1 Introduction

• 1.1 Latest Release Information
• 1.2 Purpose of this Document
• 1.3 Operating System Requirements
• 1.4 Certification Information
• 1.5 Licensing Information

2 Installation Issues

• 2.1 Installation Issues
  • 2.1.1 Installer Hangs When It Tries to Restart OPMN on Vista
  • 2.1.2 Response Files Created through the Record Mode Are Not Supported
  • 2.1.3 IPv6 Not Supported
  • 2.1.4 Port Conflict When Oracle WebCenter Framework and Oracle Content DB are Installed on the Same Machine
  • 2.1.5 Installation Failure for Turkish Locale
  • 2.1.6 Set db_create_file_dest Before Installing Against a File System Database
• 2.2 Documentation Errata
  • 2.2.1 Length Restrictions on Content Database Schema Password is Incorrect in the Oracle Universal Installer Online Help
  • 2.2.2 Incorrect DVD-ROM File Structure Mentioned in Oracle Application Server Installation Guide
  • 2.2.3 Clarification of VIRTUAL_HOST_NAME Environment Variable Setting

3 General Management and Security Issues

• 3.1 General Issues and Workarounds
  • 3.1.1 Deploying an Application Hangs During File Upload
  • 3.1.2 Limited Management Support for Multiple-JVM OC4J Instances
  • 3.1.3 Problem Removing a Property from a Native Data Source
  • 3.1.4 Use the Command-Line to Restart Standalone OC4J Instances
  • 3.1.5 TopLink Sessions Not Available in Application Server Control Console
  • 3.1.6 Unable to Receive MBean Notification Using OPMN to Start or Stop OC4J
  • 3.1.7 Using the Java Server Pages Standard Tag Libraries
  • 3.1.8 RMD Conditional Does Not Fully Evaluate
  • 3.1.9 Cannot Browse System MBeans If Application Server and OC4J Instance Share the Same Name
  • 3.1.10 Application Server Control Does Not Check for Multibyte Characters in Routing ID Text Fields
  • 3.1.11 Application Server Control Does Not Check for All Invalid Characters in the Context Root Field When Deploying an Application
• 3.2 Clustering and Replication Issues
  • 3.2.1 Using Oracle Universal Installer Provided Sample Cluster Discovery Address May Inadvertently Cluster Servers
• 3.3 Documentation Errata
  • 3.3.1 Default Ping Timeout Value in OPMN Is 30 Seconds, Not 20
  • 3.3.2 Incorrect Gateway Example in Oracle Process Manager and Notification Server Administrator's Guide
  • 3.3.3 Valid Range of Multicast Addresses is Incorrect in the Application Server Control Online Help
  • 3.3.4 Additional Information About Cloning
  • 3.3.5 Enabling and Disabling Components Is Supported
  • 3.3.6 Incorrect request Attribute Description
  • 3.3.7 Incorrect Title

4 Oracle HTTP Server

• 4.1 Issues and Workarounds
  • 4.1.1 Configuring Weighted Routing for AJP13 Destinations
  • 4.1.2 Routing Requests to Different Middle Tiers Based on the URL of the Request
• 4.2 Documentation Errata
  • 4.2.1 Oracle HTTP Server Apache Version Number
  • 4.2.2 Log Level Choices for Configuring IIS Listener for Single Sign-On are Incorrect
  • 4.2.3 Correction to SSLCARevocationFile Directive Description
  • 4.2.4 Correction to SSLCARevocationPath Directive Description
  • 4.2.5 Incorrect Tags Listed for 40-Bit and 56-Bit Export Ciphers
  • 4.2.6 Incorrect Web Address for mod_php Extensions Information
  • 4.2.7 Clarification for the Name of the Oracle Application Server Proxy Plug-In Definition File

5 Oracle Content Database

• 5.1 Documentation Errata
  • 5.1.1 Additional Information for Content Database Administration Guide

6 Oracle WebCenter Suite

• 6.1 Oracle WebCenter Suite Issues and Workarounds
  • 6.1.1 Installing Oracle WebCenter Suite 10g (10.1.3.2) on the Same Host as Oracle Database 10.1.x or 10.2.x Will Cause Performance Issues
  • 6.1.2 Cloning the Oracle Home that Contains the OC4J_WebCenter Instance Does Not Clone the Java Object Cache Configuration
  • 6.1.3 Standalone OC4J Requires Configuration to Run Java Object Cache
  • 6.1.4 Use of Portal Adapter Requires Patch Update
  • 6.1.5 JAZN Migration Tool Incorrectly Prefixes ADFRolePrincipal
  • 6.1.6 Rich Text Portlet Customization Not Supported in Safari
  • 6.1.7 Portlets with ADF Data Binding on the Same Page Cannot Be Customized
  • 6.1.8 Issue with SES Securely Crawling Content in Oracle ContentDB
  • 6.1.9 Language Setting Issue with the Federated Portal Adapter
  • 6.1.10 Using the Search Feature with the File System Adapter
  • 6.1.11 Using the Search Feature with the Federated Portal Adapter or Oracle ContentDB in Turkish
  • 6.1.12 Use of Oracle WebCenter Adapters for Microsoft SharePoint, EMC Documentum, and IBM Lotus Domino Requires Patch Update
  • 6.1.13 Using the Search Feature with Oracle WebCenter Adapters for Microsoft SharePoint, EMC Documentum, and IBM Lotus Domino
  • 6.1.14 Reexecuting a Page that Uses Oracle WebCenter Adapters for Microsoft SharePoint, EMC Documentum, and IBM Lotus Domino
  • 6.1.15 Incorrect Query Execution in Oracle WebCenter Adapter for IBM Lotus Domino
  • 6.1.16 Supplying a Domain Name as Part of Administrator Credentials for Oracle WebCenter Adapter for EMC Documentum
  • 6.1.17 Testing a JCR SharePoint Repository Connection
  • 6.1.18 Running the Predeployment Tool in Scripts
  • 6.1.19 Log Messages While Starting Preconfigured OC4J
  • 6.1.20 Error When Compiling JSP with PDK Struts Components
• 6.2 Documentation Errors
  • 6.2.1 Help for WebCenter Application Metrics Incorrect in All Languages
  • 6.2.2 Error in the Manually Creating and Editing the orion-application.xml File section of Oracle WebCenter Framework Developer's Guide

7 Oracle JDeveloper

• 7.1 Introduction
• 7.2 General IDE Issues and Workarounds
  • 7.2.1 Incompatibility Between Internal CVS Client and CVSNT Server
• 7.3 Deployment Issues and Workarounds
  • 7.3.1 EJB Web Service Fails to Deploy to JDeveloper's Embedded Server
  • 7.3.2 ADF Web Application with Ejb3 Model Project Dependency Fails to Deploy
  • 7.3.3 Deploying JDeveloper Deployment Profiles to Archive Files on the File System
• 7.4 Database Issues and Workarounds
  • 7.4.1 Entity Created Only for First Table in Entity Beans from Tables in Oracle Lite
• 7.5 Modeling Issues and Workarounds
  • 7.5.1 Refactoring Context Menu and UML
  • 7.5.2 Java Modeler Accessibility
• 7.6 Toplink Issues and Workarounds
  • 7.6.1 Importing Tables with Multibyte Characters
• 7.7 EJB Issues and Workarounds
  • 7.7.1 EJB 3.0 Application Migration Issue (10.1.3 to 10.1.3.1)
  • 7.7.2 Running EJB 3.0 Applications
• 7.8 Web Services Issues and Workarounds
  • 7.8.1 Top-Down SOAP 1.2 Services Changed to SOAP 1.1 after Editing
  • 7.8.2 Top-Down Service with One-Way Operations Changed to Two-Way Methods after Editing
  • 7.8.3 Top-down Web Services Generated with Enumerated Types Fail Validation
  • 7.8.4 Deleting InitParam or Header in a Web Service Handler Causes an Error
  • 7.8.5 Web Service Proxy Fails when Running with Reliability Settings
  • 7.8.6 'Invoke' Button Not Present in Enterprise Manager for Testing EJB3.0 Web Service on External OC4J
  • 7.8.7 Invalid Web Service Endpoint in Generated Proxy for Multi-Port WSDLs
  • 7.8.8 Runtime Exception when More than One Web Service Exists in a Project
• 7.9 JavaServer Faces (JSF) Issues
  • 7.9.1 In JSF 1.1_02 Pages under /WEB-INF Fail to Load
• 7.10 Miscellaneous Issues and Workarounds
  • 7.10.1 Using JAZNMigrationTool with JDeveloper
  • 7.10.2 Running ADF Installer against Application Server 10.1.2 Instance
  • 7.10.3 Restore Option Does Not Restore bc4j.ear

8 Oracle Sensor Edge Server

• 8.1 Installation and Configuration Issues
  • 8.1.1 OC4J 10.1.2 Must be Stopped if Installing Against It
  • 8.1.2 Default Database Tablespaces
  • 8.1.3 DBMS Lock Problem
  • 8.1.4 Unable to Create a JMX Connection
  • 8.1.5 Restart Server for Changes to Take Effect
  • 8.1.6 Oracle Sensor Edge Server Installation Fails
  • 8.1.7 Resolving the Reboot Issue for XML Configuration
• 8.2 General Issues
  • 8.2.1 Using UTL_EDG.REMOVE_RULE Displays an Error
  • 8.2.2 Adding a Rule Displays an Error
  • 8.2.3 Localization -- Navigation Tree in the SES Console Renders as the Server Locale-Defined Character Set
  • 8.2.4 Reassignment of Audio Event Type (207)
• 8.3 Documentation Issues
  • 8.3.1 Documentation for Oracle Sensor Edge Server Extensions
  • 8.3.2 Manually Deploying Sensor Data Streams Against an Existing Sensor Data Repository

9 Oracle Containers for J2EE

• 9.1 Configuration, Deployment, and Administration Issues and Workarounds
  • 9.1.1 Remove the Tomcat Examples
  • 9.1.2 Deprecated Environment Variables KeepWrapperCode, WrapperCodeDir, and DoNotReGenerateWrapperCode
  • 9.1.3 Deprecated System Property ejb.batch.compile
  • 9.1.4 Desupported orion-ejb-jar.xml Attributes
  • 9.1.5 System Property for File Information Cache Size
  • 9.1.6 Use of '/' for Context Root
  • 9.1.7 Allowed Format for Version Numbers in MANIFEST.MF File
  • 9.1.8 Having the AJP Listener Use the Loopback Interface Only
  • 9.1.9 Determining JVM, OC4J Instance, or Application Server Instance
  • 9.1.10 Invocation by Servlet Name without Mapping Is Disabled by Default
  • 9.1.11 Warning Regarding Maximum Concurrent Timers
  • 9.1.12 Use of the http.file.allowAlias Property
  • 9.1.13 Starting OC4J Using JDK 1.4.2 for a Headless Console
  • 9.1.14 New Wait Option for Sequential Redeployment to a Cluster
  • 9.1.15 Job Scheduler Redeployment
  • 9.1.16 Incompatible ONS Versions
  • 9.1.17 Incorporating Ant Tasks Using Ant 1.6.5 Outside OC4J with the OC4J Administrative Client
  • 9.1.18 Specifying the Mapping Attribute
  • 9.1.19 Using opmn Settings for OC4J home Instance As Template for New Instance
  • 9.1.20 How to Specify Ports for State Replication in OPMN
  • 9.1.21 OC4J Instances in a Group Must Have Same Version
  • 9.1.22 Same Destination for Trace Output from Two OC4J Instances Not Supported
• 9.2 Servlet Issues and Workarounds
  • 9.2.1 Servlet Invocation by Classname Disabled by Default
  • 9.2.2 Enabling Access Logging for Web Applications
  • 9.2.3 OC4J 10.1.3.1.0 Honors Session id Value Differently
  • 9.2.4 Exception and Stack Trace No Longer Displayed in HTML Error Page
  • 9.2.5 Disabling Servlet Reloading
• 9.3 JavaServer Pages (JSP) Issues and Workarounds
  • 9.3.1 Workaround to View JSP Demo Files
  • 9.3.2 Deprecated JSP Configuration Parameters
  • 9.3.3 ojsp Tag Libraries Deprecated
  • 9.3.4 Specifying justrun for Production Environment Efficiency
  • 9.3.5 Using a Tag Library with the ojspc Utility
• 9.4 EJB Issues and Workarounds
  • 9.4.1 EJB 3.0 Support
  • 9.4.2 EJB 3.0 Interceptors Supported in JDK 1.5 Only
  • 9.4.3 Remote EJB 3.0 Stateful Session Bean Does Not Failover When Using Extended Persistence
  • 9.4.4 Orion CMP Is Deprecated
  • 9.4.5 ejb-module Attribute remote Deprecated
  • 9.4.6 Default IP Address Stack
  • 9.4.7 Set Managed Datasource Attribute manage-local-transactions To False When Using Oracle JMS Connector
• 9.5 Web Services Issues and Workarounds
  • 9.5.1 Configuration Issues
    • 9.5.1.1 Installation Fails in Web Services Inspection Language (WSIL) Configuration
  • 9.5.2 WebServicesAssembler Issues
    • 9.5.2.1 Multiple Service Elements in Top Down Web Service Assembly
    • 9.5.2.2 Relative Path Names Are Not Supported in WSDL or XSD Imports
    • 9.5.2.3 WebServicesAssembler Requires Schema Imports in the WSDL to Be Qualified by the schemaLocation Attribute
    • 9.5.2.4 The assemble Ant Task Raises an Exception when Java Files Contain J2SE 5.0 Annotations
  • 9.5.3 WSDL-Related Issues
    • 9.5.3.1 Support for Globalization Support (NLS) Characters in the WSDL
    • 9.5.3.2 Services that use Multiple Message Formats Cannot be Deployed in a Single Web Application
    • 9.5.3.3 genWsdl Command Does not Preserve Order of Variables
  • 9.5.4 Schema Features Limitations
    • 9.5.4.1 RPC Encoded Does Not Support Complex Types With Attributes
    • 9.5.4.2 XML Types xsd:choice and xsd:group Are Not Supported for Proxy or Top Down Web Service Assembly
  • 9.5.5 Test Page Issues
    • 9.5.5.1 Recursive Schema Definitions Are Not Supported in the Web Services Test Page
    • 9.5.5.2 Formatted XML Content Returned from a Service Invocation on the Web Services Test Page May Be Shown Incorrectly
    • 9.5.5.3 Test Page May Not Show Errors Originating from an Invalid Web Service WSDL
    • 9.5.5.4 Invalid Values in a Web Services Test Page Form Field May Result in an "Unable to get header stream in saveChanges" Error
    • 9.5.5.5 Web Services Test Page Does Not Support Globalization Support (NLS) Characters in User Name or Password
    • 9.5.5.6 Web Services Test Page Does Not Support the Schema Features: group, choice, union, or Derived Simple Types as Attributes
    • 9.5.5.7 Test Page Stress Test Report May Be Displayed Incorrectly Under Firefox or Mozilla
  • 9.5.6 Deployment Issues
    • 9.5.6.1 EJB 2.1 Web Services Deployed with an Invalid oracle-webservices.xml File
  • 9.5.7 Other Issues
    • 9.5.7.1 Get NodeLists by Using getFirstChild and getNextSibling Instead of getChildNode
    • 9.5.7.2 Using the 'class' Attribute in Ant Build Scripts to Specify JAX-RPC Web Service Handlers
    • 9.5.7.3 BEA Clients are Unable to Deserialize Responses from OC4J Web Services
    • 9.5.7.4 Mapping Issue with Simple Types (with Restrictions) on the .NET Platform
    • 9.5.7.5 genValueType Command Does Not Validate Restrictions
    • 9.5.7.6 XML Serialization Does Not Accept the Array Java Data Type for Document-Literal-Bare Message Format
• 9.6 OC4J Services Issues and Workarounds
  • 9.6.1 JNDI
    • 9.6.1.1 Spaces in Application Names
    • 9.6.1.2 Wrong Provider URL in the jndi.properties File
    • 9.6.1.3 Deprecated JNDI Environment Variables
    • 9.6.1.4 Local Host Not Supported
  • 9.6.2 Oracle Enterprise Messaging Service (OEMS)
    • 9.6.2.1 Error Starting OC4J after OracleASjms is Undeployed
    • 9.6.2.2 OC4J May Fail to Restart after Abnormal OC4J Shutdown
    • 9.6.2.3 XA-styled JMS Connections Not Supported Between OC4J Versions
    • 9.6.2.4 JMS Auto-Enlisting in Global Transactions is Desupported
    • 9.6.2.5 Changes in JMS Client Properties Require Restart
    • 9.6.2.6 New JMS Provider
    • 9.6.2.7 Poor Performance When Persisting Messages to a Database
  • 9.6.3 Data Sources
    • 9.6.3.1 The oracleFatalError method is no Longer Available
    • 9.6.3.2 OracleConnectionCacheImpl Deprecated
    • 9.6.3.3 Orion CMP Fails Due to JDBC Driver Clash
    • 9.6.3.4 Upgrading the Oracle THIN JDBC Driver
  • 9.6.4 OC4J Transaction Support
    • 9.6.4.1 The In-DB Coordinator Is Deprecated
    • 9.6.4.2 Support for Recoverable Last Resource Commit
    • 9.6.4.3 New Transaction Manager Extensions
  • 9.6.5 RMI
    • 9.6.5.1 RMI Recommendations
    • 9.6.5.2 Incorrect "Provider URL..." Error Message
  • 9.6.6 XQS
    • 9.6.6.1 Updated XQS Client API
    • 9.6.6.2 SQL Usage has Changed
    • 9.6.6.3 Incorrect XQS Type-Checking Example
    • 9.6.6.4 XQS Schema Import Support
  • 9.6.7 Application Client Container
    • 9.6.7.1 Custom Security Callback Handler Fails
• 9.7 J2EE Connector Architecture (J2CA) Issues and Workarounds
  • 9.7.1 New Class Loader Architecture for Standalone Resource Adapters
  • 9.7.2 Deployment Dependencies between Standalone Resource Adapters
  • 9.7.3 Class Not Found Exceptions
  • 9.7.4 Restart of Default Application Required After Redeploying or Undeploying Internal Resource Adapters
• 9.8 OracleAS JAAS Provider and Security
  • 9.8.1 Correct JAZNMigrationTool Syntax
  • 9.8.2 Use of JAAS Permissions and JAZNMigrationTool with External LDAP Provider
  • 9.8.3 Proper Specification of osso.conf File Name for SSO Configuration
  • 9.8.4 User and Role APIs Replace OracleAS JAAS Provider Realm API Functions
  • 9.8.5 OutOfMemoryError on Multiple Restarts of Standalone OC4J through Application Server Control
  • 9.8.6 Controlling Caching of JNDI Contexts for LDAP Connections
  • 9.8.7 JAZN Tool No Longer Includes -clustersupport
  • 9.8.8 AJP13 Protocol Vulnerable to Bypass User Authentication
• 9.9 General OC4J Issues and Workarounds
  • 9.9.1 OutOfMemoryError on Multiple Restarts of Standalone OC4J through Application Server Control
• 9.10 Documentation Errata
  • 9.10.1 Web Services Guide
    • 9.10.1.1 Incorrect Link Provided for wsclient_extended.zip File
    • 9.10.1.2 Typos in XML Type Names in Advanced Web Services Developer's Guide
    • 9.10.1.3 ServerConstants Properties Cannot be used to Access the HTTP Layer from the Client
  • 9.10.2 Oracle Application Server Advanced Web Services Developer's Guide
    • 9.10.2.1 Incorrect XML in Examples in the "Using Web Service Providers" Chapter
  • 9.10.3 Oracle Containers for J2EE Deployment Guide
    • 9.10.3.1 Incorrect Attribute Name in Example of Ant Task
    • 9.10.3.2 File Name oracle-ant.jar Should Be ant-oracle.jar
    • 9.10.3.3 The version Property of the removeSharedLibrary Ant Task Should Be libraryVersion
    • 9.10.3.4 Checking for Updates by Comparing Directory and EAR or WAR Timestamps
    • 9.10.3.5 Incorrect Subswitch Names for admin_client.jar Commands
    • 9.10.3.6 Information Missing from Description of admin_client.jar -redeploy Command Subswitches
    • 9.10.3.7 deploymentPlan Property Not Valid in Ant Task for WAR Deployment
    • 9.10.3.8 Incremental Redeployment of EJB Modules Not Supported by Application Server Control
  • 9.10.4 Oracle Containers for J2EE Services Guide
    • 9.10.4.1 Wrong Data Source Element Name
    • 9.10.4.2 Wrong Defaults Listed for Connection Pool Attributes
    • 9.10.4.3 Invalid Attribute
    • 9.10.4.4 Revised Description for max-connections Attribute
  • 9.10.5 OracleAS JAAS Provider and Security
    • 9.10.5.1 Incorrect Notes on 'Mixed Usage' between Identity Store and Policy Store
    • 9.10.5.2 Incorrect Note on Automatic Creation of Indirect User Accounts
    • 9.10.5.3 Obsolete <data-source> Element Cited
    • 9.10.5.4 Invalid Reference to x509cert.mapping.attribute Property
    • 9.10.5.5 Form Authentication Method Supported with Custom Login Modules
  • 9.10.6 Oracle Containers for J2EE Developer's Guide
    • 9.10.6.1 Missing Character in Service URL Strings
    • 9.10.6.2 Incorrect Setting for Client Module in orion-application.xml
    • 9.10.6.3 Correction to Example: Replacing the Oracle XML Parser with the Xerces Parser
  • 9.10.7 Oracle Containers for J2EE Configuration and Administration Guide
    • 9.10.7.1 Incorrect Example for Disabling Text File Logging
    • 9.10.7.2 Incorrect Subswitch Names for admin_client.jar Commands
    • 9.10.7.3 Information Missing from Description of admin_client.jar -redeploy Command Subswitches
    • 9.10.7.4 Format for Variables That Configure Text Logging for Web Sites
    • 9.10.7.5 Incorrect Description of Queue Attribute for Thread Pools
    • 9.10.7.6 Configuration of OPMN Gateway Element Shows Incorrect Order
    • 9.10.7.7 Starting Order Incorrect for Static Peer-to-Peer Replication
  • 9.10.8 Oracle Containers for J2EE Servlet Developers Guide
    • 9.10.8.1 Do Not Specify a Host for the <host-access> domain Attribute
  • 9.10.9 Oracle Containers for J2EE Enterprise JavaBeans Developer's Guide
    • 9.10.9.1 Do Not Edit the boot.xml File As Documented

10 High Availability

• 10.1 Configuration Issues and Workarounds
  • 10.1.1 Compatible ASG Releases for OracleAS Instances from Different Oracle Application Server Releases
  • 10.1.2 Compatible ASG Releases in an OracleAS Disaster Recovery Topology
  • 10.1.3 Configuring Portlet Producers and WebCenter Applications in an OracleAS Cluster Topology
  • 10.1.4 Supported Java Object Types for Session Attributes in Distributed Applications
  • 10.1.5 The create standby Command Fails with Standby Control File Errors
  • 10.1.6 ASG to Catch Array Overflow Exceptions in Queries to Primary
  • 10.1.7 The create standby Command Fails if the Redo Log Files Directories do not Exist at the Standby
  • 10.1.8 Corrupt Index Blocks in Metadata Repository Databases
  • 10.1.9 Database SIDs Must be the Same for Database Peers at Primary and Standby Sites
  • 10.1.10 Use All Uppercase Characters for Database Initialization Parameters to Avoid Instantiate and Sync Problems
  • 10.1.11 Workaround for ASG_DUF-3800 "Failed trying to connect to the OPMN Manager" Error
  • 10.1.12 Use the Same Port for ASG on the Production and Standby Sites to Avoid clone instance Operation Problems
  • 10.1.13 Install sc.exe Version 5.0.2134.1 or Higher on Windows Systems to Avoid Cloning Problems
  • 10.1.14 Use Fully Qualified Path Names with the add instance Command
  • 10.1.15 ASG Cloning is Not Supported when the Number of Oracle Homes is Different at the Primary and Standby Hosts
  • 10.1.16 Steps to Add a Database with OMF or ASM to ASG Topology
• 10.2 Documentation Errata
  • 10.2.1 Additional Site Switchover Information for RAC Deployments
  • 10.2.2 Correction to Configuration Instructions for a Primary Site with RAC Database and Standby Site with Non-RAC Database

11 Oracle Business Rules

• 11.1 Standalone OC4J Rule Author Installation
• 11.2 RL serviceDateValidation Error: Fact Class Should Be Declared Earlier

12 Oracle Secure Enterprise Search

• 12.1 Oracle Secure Enterprise Search
  • 12.1.1 Overview of Oracle Secure Enterprise Search
  • 12.1.2 Oracle SES in WebCenter

13 Oracle Communication and Mobility Server

• 13.1 Installation, Configuration, and Upgrade Issues
  • 13.1.1 Use Only Lowercase Usernames
  • 13.1.2 OutOfMemoryException
  • 13.1.3 Installation Accessibility Issue
  • 13.1.4 Oracle Communicator Accessibility Issue
    • 13.1.4.1 Account Settings
    • 13.1.4.2 Presence Settings
    • 13.1.4.3 Appearance Settings
    • 13.1.4.4 Security
    • 13.1.4.5 Network
    • 13.1.4.6 Audio
    • 13.1.4.7 Video
    • 13.1.4.8 Other
• 13.2 Other Known Issues
  • 13.2.1 OCMS Server Does Not Start After IP Address Change
  • 13.2.2 XSLT Stylesheet Error