Oracle® Fusion Middleware

Release Notes for Oracle WebCenter Sites

12c (12.2.1.2.0)

E77467-02

November 2016

Describes the general issues and limitations that may be encountered while using WebCenter Sites. For few of the issues, workarounds are listed. Additionally, the document provides information about new features, deprecated features, oracle support, and product documentation.

Oracle Fusion Middleware Release Notes for Oracle WebCenter Sites, 12c (12.2.1.2.0)

E77467-02

Copyright © 2012, 2016, Oracle and/or its affiliates. All rights reserved.

Primary Author: Debosri Brahma

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

Part I Introduction

1 New Features and Certifications

- 1.1 New Features

- 1.2 Purpose of this Document

- 1.3 System Requirements and Specifications

- 1.4 Deprecated Features

- 1.5 Certification Information

- 1.6 Product Documentation

- 1.7 Oracle Support

- 1.8 Downloading and Applying Required Patches

- 1.9 Licensing Information

Part II Issues Related to Oracle WebCenter Sites Components

2 General Issues and Workarounds

- 2.1 A/B Testing

- 2.2 Accessibility

- 2.3 Admin Interface

- 2.4 APIs

- 2.5 Approval

- 2.6 AssetCache

- 2.7 Authentication

- 2.8 Bulk Approver Utility

- 2.9 Caching: inCache

- 2.10 Caching: Satellite Server

- 2.11 CKEditor

- 2.12 Cluster

- 2.13 Contributor Interface

- 2.14 Developer Tools

- 2.15 Edge Browser

- 2.16 Engage

- 2.17 Flex Assets

- 2.18 Image Optimization

- 2.19 Installation

- 2.20 Logging

- 2.21 Mobility

- 2.22 Proxy Assets

- 2.23 Publishing

- 2.24 REST APIs

- 2.25 Revision Tracking

- 2.26 Satellite Server

- 2.27 Search

- 2.28 Shared File System (NIO)

- 2.29 Site Capture

- 2.30 Site Navigation

- 2.31 Sites Explorer

- 2.32 Start Menu

- 2.33 System Tools

- 2.34 Tags

- 2.35 User Interface Customization

- 2.36 Vanity URLs

- 2.37 Visitor Services

- 2.38 WEM Admin Interface

- 2.39 WEM Framework

- 2.40 Workflow

- 2.41 XMLPost

3 Limitations

- 3.1 A/B Testing

- 3.2 APIs

- 3.3 Asset Type Name Restrictions

- 3.4 Browser Support

- 3.5 BulkLoader and BulkApprover

- 3.6 CatalogManager

- 3.7 CatalogMover

- 3.8 CKEditor

- 3.9 Collection

- 3.10 Content Tags

- 3.11 Contributor Interface

- 3.12 Database

- 3.13 Developer Tools

- 3.14 Engage

- 3.15 Installation of WebCenter Sites

- 3.16 Localization

- 3.17 Page Cache: inCache

- 3.18 Publishing

- 3.19 REST APIs

- 3.20 Satellite Server

- 3.21 Search

- 3.22 Site Capture

- 3.23 Sites Explorer

- 3.24 Site Management

- 3.25 Tags

- 3.26 Template, Site Entry, and CS-Element

- 3.27 Upgrade

- 3.28 Vanity URL

- 3.29 WebCenter Content Integration

- 3.30 XMLPost

4 Configuration Issues and Workarounds

5 Demonstration Purposes Only

6 Documentation Errata

- 6.1 Cache Tool Resources Missing from Java API Reference for Oracle WebCenter Sites: Visitor Services

- 6.2 Updated Parameter in the getAggregatedProfile API Methods

- 6.3 Visitor Services Sample Code

Preface

This document describes all known issues and workarounds for Oracle WebCenter Sites 12.2.1.2.0.

Audience

This document is intended for all users of Oracle WebCenter Sites 12.2.1.2.0.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see these Oracle resources:

- Oracle Fusion Middleware Documentation Library 12c (12.2.1.2.0)

- Oracle Technology Network at
http://www.oracle.com/technetwork/index.html

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

Part I Introduction

This part introduces the Oracle Fusion Middleware Release Notes for Oracle WebCenter Sites, Release 12.2.1.2.0. It includes the chapter on New Features and Certifications.

1 New Features and Certifications

This chapter discusses new features, deprecated features, as well as certification and support information.

Topics

- New Features

- Purpose of this Document

- System Requirements and Specifications

- Certification Information

- Deprecated Features

- Product Documentation

- Oracle Support

- Downloading and Applying Required Patches

- Licensing Information

1.1 New Features

For information on the new features added in Release 12.2.1.2.0 see What’s New for Oracle WebCenter Sites.

1.2 Purpose of this Document

This document contains the release information for Oracle WebCenter Sites Release 12.2.1.2.0. It describes differences between Oracle WebCenter Sites and its documented functionality.

Oracle recommends that you review its contents before installing or working with the product.

1.3 System Requirements and Specifications

Oracle WebCenter Sites installation and configuration will not complete successfully unless users meet the hardware and software prerequisite requirements before installation.

For more information, see Oracle Fusion Middleware System Requirements and Specifications.

1.4 Deprecated Features

The following features have been deprecated since 12.2.1 release:

- Legacy Sites such as Hello Asset World, Burlington Financials, and GE Lightings

- Page Debugger

- SOAP-based web services

- WebCenter Sites Analytics 2.5

- WebCenter Sites Gadgets and Gadget Server

- WebCenter Sites Content Integration Platform - EMC Documentum

- WebCenter Sites Content Integration Platform Filesystem

- WebCenter Sites Content Integration Platform Sharepoint

- WebCenter Sites Integration with Endeca

- WebCenter Sites Janrain Integration

- WebCenter Sites Native authentication in Community/Gadgets

- WebCenter Sites Netomat Mobility Server

1.5 Certification Information

The latest certification information for Oracle WebCenter Sites 12c (12.2.1.2.0) is available at the Oracle Fusion Middleware Supported System Configurations page.

1.6 Product Documentation

For developer information, see Introduction to Developing with WebCenter Sites in Developing with Oracle WebCenter Sites.

For administrator information, see Introduction to Oracle WebCenter Sites in Administering Oracle WebCenter Sites.

For user information, see Introduction to Oracle WebCenter Sites in Using Oracle WebCenter Sites.

For properties information, see Oracle WebCenter Sites JSON Property File in Property Files Reference for Oracle WebCenter Sites.

1.7 Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support at https://support.oracle.com.

1.8 Downloading and Applying Required Patches

After you install and configure Oracle WebCenter Sites Release 12.2.1.2.0, there might be cases where additional patches are required to address specific known issues.

Complete the following steps to obtain a patch:

1. Log in to the My Oracle Support web site at https://myoraclesupport.com/.

2. Click the Patches & Updates tab.

3. Use the Patch Search area to locate patches.

4. On the Patch Search Results page, select a patch and click Download to download the patch.

5. Install the patch by following the instructions in the README file that is included with the patch.

1.9 Licensing Information

Licensing information for Oracle Fusion Middleware is available at:

Oracle® Fusion Middleware Licensing Information User Manual

Part II Issues Related to Oracle WebCenter Sites Components

This part describes issues associated with Oracle WebCenter Sites components. It includes the following chapters:

- General Issues and Workarounds

- Limitations

- Configuration Issues and Workarounds

- Documentation Errata

2 General Issues and Workarounds

This chapter describes general issues and workarounds for this release.

Topics

For the general issues and workarounds of 12.2.1.1 release, see Release Notes of 12.2.1.1.

- A/B Testing

- Accessibility

- Admin Interface

- APIs

- Approval

- AssetCache

- Authentication

- Bulk Approver Utility

- Caching: inCache

- Caching: Satellite Server

- CKEditor

- Cluster

- Contributor Interface

- Developer Tools

- Edge Browser

- Engage

- Flex Assets

- Image Optimization

- Installation

- Logging

- Mobility

- Proxy Assets

- Publishing

- REST APIs

- Revision Tracking

- Satellite Server

- Search

- Shared File System (NIO)

- Site Capture

- Site Navigation

- Sites Explorer

- Start Menu

- System Tools

- Tags

- User Interface Customization

- Vanity URLs

- Visitor Services

- WEM Admin Interface

- WEM Framework

- Workflow

- XMLPost

2.1 A/B Testing

- If a page on which an A/B test is running is changed and republished, then the A/B test shows correct new data for variant A. If the page is changed in such a way that the differentials for the variant pages no longer apply, then the variants aren’t shown correctly as expected.

- Template assets that are used in A/B testing but aren’t used elsewhere can also be deleted. However, deleting a template used in a differential of an A/B test prevents the A/B test from displaying the intended content to the site visitors.

- When an A/B test is running, it is possible to modify and publish the base page. These changes may prevent the test variants from being delivered correctly and invalidate the test results without warning. Therefore, it is recommended to not change a page while it is taking part in an A/B test.

2.2 Accessibility

In the Contributor interface, the JAWS accessibility reader doesn’t read the field names for flex assets that use the Pulldown, Uploader, and typeAhead attribute editors. In addition, the reader doesn’t read all field names on the Workflow Status screen. Lastly, the reader doesn’t read the field name for multiple-value date fields that use the date picker attribute editor.

2.3 Admin Interface

- Downloaded log files from System Tools don’t include information from cas.log.

- Right-clicking REFRESH doesn’t refresh the page for Thread Info, Sites Info, and DB Info.

- The message "An error has occurred" appears when attempts are made to view logs in Log Viewer, but the logs are empty.

- "No access allowed" messages appear multiple times when permissions are insufficient for viewing table information in DB Info.

- Unable to run the File System test multiple times without changing the type of test to run.

- System Tools, File System Test information isn’t displayed in graph form in Internet Explorer. To view this graph, use Firefox.

- When WebCenter Sites is configured to use a hierarchical LDAP, if the user has access only to the Management Site and you log in to the Admin interface, the tree tab loads and shows the tabs, but all the tabs are empty.

2.4 APIs

- ics.CommitBatchedCommands() does not return the correct status or set the errno variable properly in every situation.

- JSP processing adds white space.

- When asset:export / asset.export tags are used on an asset that is not a page or collection, the output XML does not contain information about the unnamed associations.

- The XML tag ASSET.DELETEREVISION, which deletes a specific revision of the asset, fails to execute. The JSP variant asset:deleterevision should be used.

- For case-sensitive databases, setting the case sensitivity to false does not disable the case sensitivity of the search query.

2.5 Approval

- Approving a site plan using the right-click in the Contributor interface will not include any slot assets in the approval. Pages with slots will need to be approved separately.

- When a recommendation or promotion is approved, it does not show segment as a dependency.

2.6 AssetCache

- When a revision-tracked asset is deleted, on the initial inspection of the asset, AssetCache shows this asset with updated time and valid dependency, which is incorrect.

- Uploading a blob larger than 5 MB will result in an exception, which can be safely ignored:
"Error met serializing / deserializing <Assettype ID> for copying purpose in AssetCache"

- <render:LogDep> could cause unlinked cache. If there is an unrecognized rendermode passed, the system will cache the page and not log the dependencies. This will cause the page to not be flushed in any way since their dependencies are not there.

- A warning message in the log is sometimes seen: "Creating a new instance of CacheManager using the diskStorePath". The message can be safely ignored.

2.7 Authentication

Integrating WebCenter Sites with the WebLogic Server embedded LDAP may affect the listing of users previously assigned to the site on the Manage Sites Users page in the WEM Admin interface. This display issue does not affect functionality; previously assigned users can log in to the site successfully.

2.8 Bulk Approver Utility

Running the Bulk Approver utility no longer requires login credentials as plain text in the bulkapprove.ini file. The utility now accepts the credentials as arguments in the command line, as follows:

BulkApprover <config=...> <action=initialize,notify,approve,mark_publish> <output_file=xxx> <target_list=...> <username=...> <password=...>

target_list=<...>[optional, overrides approvalTargetList

2.9 Caching: inCache

The disk store size keeps growing as the cache gets more usage, even if the actual number of items in cache remains the same.

2.10 Caching: Satellite Server

- Any blob that is not supposed to be cached by the Satellite Server will be added under sscachedir/uncachedblob. This directory can grow if blobs are not being cached on the Satellite Server. The content of this directory can be safely deleted at any time. It can be deleted manually or by using the FlushServer reset call.

Note:
The FlushServer reset call will clear all the cache from the Satellite Server.

- Pages based on a template variant are not cached on Remote Satellite Server on the first request.

2.11 CKEditor

A frame shows a "Loading" message if the target is set to "not set", "frame", or "Same Window (_self)" during creation of the external link in CKEditor.

2.12 Cluster

After a successful user log in to a WebCenter Sites cluster environment, an error message displays in the sites.log file indicating that the ticket is either invalid or already expired. This message does not affect functionality and can be ignored.

2.13 Contributor Interface

- When a page is previewed in a new window in the Contributor interface, it first checks the wrapper element in the request. If this element is not available, the page uses the default wrapper configured for the site in the Admin interface.

- If there is a failure due to template compatibility reasons while a slot is swapped, the original slot content is cleared. Refresh or cancel the save to revert back to the previously saved state.

- Bookmarks are not appearing in the tree for sites that are imported using Developer Tools. To resolve this, edit and save the bookmark tree tab in the Admin interface.

- During dragging and dropping from the docked search, the avatar window (showing the asset name in blue) tends to hide behind the search.

- Drag-and-drop of pages to the Site Plan Tree is not supported. Doing so may cause the tree node indicator to spin and not return results. Other operations are able to continue during this time except action initiated from the node of the Site Plan Tree that is no longer responding.

- The progress bar is not displayed accurately for large file uploads (greater than 64 MB) for Basic Assets.

- Setting bs.security=true results in blobs failing to render in Web Mode or Preview.

- Setting bs.security=true results in the failure of a blob to render correctly on create screen; inspect will display properly.

- The select layout template appears behind videos added as part of a proxy asset in the Contributor interface.

- Date picker does not work in Web Mode if the value is empty.

- In Web Mode, the selected layout in the Change Layout option is retained in the browser even when the asset is not saved.

- Changes to the presentation of a slot are not copied during an asset copy operation in Web Mode.

- When Right-to-Left (RTL) orientation is used in the Contributor interface, the context menu and submenu may overlap in the navigation pane tree. In addition, the Content menu’s submenu options may not display fully.

- The New menu option from Placed Pages node under the Site Tree in Contributor interface is removed.

- In the Web mode, image upload fails in the first attempt, but is successful in the second attempt. Image upload works fine in the Form mode of the Contributor interface.

- If you try to delete an asset, dependent assets are shown in the Delete page, but are not shown under the 'Referenced By' column in metadata tab of the asset.

2.14 Developer Tools

- When creating templates using the existing element option, if the specified element does not exist, an empty template will be created in WebCenter Sites, but cannot be exported.

- If the file name length of an exported file exceeds the operating system file name limitation, the file cannot be exported. This is likely to happen if the file name of an uploaded blob is too long.

- You must be cautious of the order in which resources are imported. Consider the situation in which all developers have "A points to B" in their system. Then one developer changes A to point to C and deletes B. If other developers were to sync B before A, the import would fail, since an asset that is being referenced cannot be deleted.

- During import, you may experience some indexing data exceptions. This will affect only the search index and not the actual data import. Re-index the affected asset types after the import, if necessary.

- Resources that contain fw_uids that include slashes or commas cannot be exported.

- The locale hierarchy information is not preserved for an exported hierarchical DimensionSet. The workaround is to manually configure the hierarchal information after import.

- SiteCatalog resources do not contain a dependency on the ElementCatalog resource. These currently need to be exported/imported manually.

- Import fails to import segment assets when the segment criteria contain a history definition with a string value.

- During a connection to a remote instance, the project WEB-INF folder points to a nonexistent location. As a result, code completion will not work. To work around this issue, map to local jars / tlds when working with remote connections.

- If an ElementCatalog entry is created with the name of an existing ElementCatalog entry, the JSP will be overridden with a new empty JSP.

2.15 Edge Browser

- If you are unable to login to Sites in the Edge browser, refresh the Edge browser or access the Site through other browsers, and then login to the Site through the Edge browser.

- While switching sites in the Edge browser, click on the Browser Refresh icon to enable switching of the sites in the Edge browser.

2.16 Engage

- To add segments in Recommendation assets, Oracle recommends using forms in the Contributor interface instead of enabling the Asset Forms functionality provided in the Admin interface. In the Contributor interface, the asset creation forms can be created using the Content > New menu, and these forms are accessible through Search/Tree tabs.

- Due to an issue with the Add Selected Segment option accessible through Recommendation Asset Creation in the Admin interface, after enabling Asset Forms you may not be able to add segments. (The Add Selected Segment option is available after setting the advancedUI.enableAssetForms property to true through Property Management in the Admin interface and enabling the Recommendation asset type for the site.)

- Setting an asset that is part of a recommendation to a rating of 100 results in only that asset being returned.

2.17 Flex Assets

If you are using multiple parents, they should all use the same Parent Select Style.

2.18 Image Optimization

The default Image Optimization filter does not optimize GIF images. This is a JDK limitation. Custom image optimization APIs may need to be implemented if you need optimized GIF images.

2.19 Installation

- During and after installation, an exception related to the jersey-container-servlet-core-2.9.jar library may display when the WebCenter Sites server is shut down. This exception does not interrupt the shutdown process and can be ignored.

- During a WebCenter Sites Managed Server and Administration Server shutdown, an exception may display in the Managed Server or Administration Server log files. These exceptions do not affect functionality and can be ignored.

- During the configuration of WebCenter Sites with Apache on HTTPS protocol, use Apache 2.4.0 or higher version. There are known issues with configuration of WebCenter Sites with Apache versions lower than 2.4.0  for Transport Layer Security version 1 (TLSv1) protocol. The product installation may fail.

2.20 Logging

The Sites.log and cas.log files are not displayed in the Fusion Middleware Control console.

2.21 Mobility

- Zooming in on more than 150 percent does not render the mobility preview page correctly.

- The devices.xml file provides a sample that works best using user-agent identification to identify by device name. Modify this file for greater granularity.

2.22 Proxy Assets

Creating a Content Query that contains proxy assets will show only dots (…) in the search results.

2.23 Publishing

- During publishing to a cluster, the progress bars in the publish status screen show progress out of order from the actual steps.

- Export to Disk: Changing display template results in multiple assets in pub list. Contact technical support for a utility to resolve this.

- Removing a published child page from the site plan and later publishing only the parent will leave the child page on the destination, but the page will not appear in the site plan.

- Temp files created during publishing remain in the file system after publication.

- Dependent asset relation for promotion is lost after publishing. This also occurs through REST and Developer Tools import / export.

- Error -3100 when publishing blobs may occur. This can be safely ignored.

- In the Admin interface’s Publish console, deleting a publish session that failed does not remove the session. The deleted session continues to display on the History tab.

- When a user with the Publisher role publishes a page, the Publish screen does not list the page’s dependent (children) assets. This behavior differs from the Approval screen, which lists a page’s dependent (children) assets for approving the page.

2.24 REST APIs

- To make a REST call, the user first gets the multi-ticket from CAS. Once the multi-ticket is received, the user should send the POST request to the URL http://<host:port>/sites/wem/service/encrypttoken. This POST request should contain the ContentType header value as applications/x-www-form-urlencoded. The user will get the encryptedtoken value as a response to this call. All calls to REST URLs must include this encryptedtoken value as the value of the X-CSRF-Token header in the request. This change applies to all REST calls except AGGREGATED REST APIs.

- When you use an invalid X-CSRF-Token header value in a REST call to Satellite Server, it does redirect to the log in screen. However, instead of generating a ticket and displaying the requested information, the redirect fails, and an error is shown.

- Initiating a REST call to sites using an invalid ticket or multi-ticket via the browser while you are logged into WebCenter Sites will be successful, as it will use the session ticket.

- Multivalued association for an asset is returned in the same order when it is saved.

- Deleted groups are not deleted from the Security Configuration. The group can be manually deleted by removing the entries from the FW_CSSecurityConfig table.

- Under load, the following exception may occur during use of Buffered Writes. This can be safely ignored, as the data is properly returned:
com.sun.jersey.server.impl.application.WebApplicationImpl onException SEVERE: Internal server error javax.ws.rs.WebApplicationException: javax.xml.bind.MarshalException

- During creation of asset types in REST, Plural Form is not reflected/honored in the Admin interface.

- Update is not working for an Application object type if Delete permission is not also granted.

- If the first request after a restart of WebCenter Sites is a PUT, the create may fail with a 500 error.

- The Navigation service will return a 400 error if Page assets type is not enabled for the site.

- When roles that are assigned to a user in a site are deleted via REST APIs, it results in 403 error.

- Access to the navigation service requires the user to be part of the RESTAdmin Group.

- A REST API for asset data sometimes returns an empty string when the attribute data is null.

- REST API calls to Remote Satellite Server through Central Authentication Service (CAS) must be made after acquiring a multi-ticket and using that multi-ticket in each REST call.

2.25 Revision Tracking

- Viewing the version of a revision-tracked asset where the parent has been deleted will display a blank screen.

- If access to Checkout is denied, clicking the Checkout button in the Contributor interface will result in no response.

- Deleting an asset that was associated to a revision-tracked asset removes all associations on rollback.

2.26 Satellite Server

- On a Remote Satellite Server instance that runs on Apache Web Server, one or more operations related to uncached templates may get blocked because of another ongoing operation. This blocking of operations or threads occurs due to a bug in Apache, and it results in decreased throughput. This issue is exacerbated by an increased number of uncached templates.

- A content-type header is lost when a wrapper page is called using Co-resident Satellite Server. WebCenter Sites logs "Unable to set header (header name) because the header has already been committed".
The workaround is to increase the application server response buffer size.

2.27 Search

- When assets in the Contributor interface are assigned multiple tags, an advanced search does not return the correct results. For example, if an asset is assigned three tags and an advanced search looks for the asset based on one of its tags, no search results display for the asset.

- When an attribute-specific advanced search in Contributor begins with an uppercase character, advanced search displays no results.

2.28 Shared File System (NIO)

- When an NIO (Nonblocking I/O) shared file system is used in which the shared file system is stored on a separate database, a delay of 2-5 minutes on the first log in to WebCenter Sites is expected.

- When the shared file system is managed in the database, the download option available under System Information tools is not working.

2.29 Site Capture

- Download Archives action may time out if the archive size is large.

- Multiple Jobs and Archives get created if schedules overlap for the same crawler. Oracle recommends creating only one schedule for each crawler to avoid creation of duplicate jobs and archives.

- In some cases, when the installation is performed on Solaris, if the start URI is not configured correctly, errors will be reported as HTTP instead of network errors. Ensure that the start URI is configured correctly.

- Site Capture shares two caches with WebCenter Sites: linked-cache.xml and cas-cache.xml. The default values are the same for Site Capture and WebCenter Sites.
For cache configuration, Site Capture should be treated as a cluster member of WebCenter Sites. If the WebCenter Sites ports change, the Site Capture ports must be updated to match. If WebCenter Sites is changed to unicast, then Site Capture must also be changed to unicast.

If Site Capture and WebCenter Sites reside on different machines, the timeToLive (ttl) value needs to be adjusted, as if they were members of the same cluster.

2.30 Site Navigation

- The site navigation in avisports shows only the unplaced pages when an updated page is republished. The site navigation works as expected in the newly created sites.

- If a page is moved to a different site navigation while another user is editing or viewing the page in the Contributor interface, the multidevice preview may not accurately reflect the correct device group.

- Setting showparentnodes=false will result in related assets of the last node in the tree appearing as children of the root node.

2.31 Sites Explorer

Oracle recommends using Oracle WebCenter Sites Explorer on Windows 7 if it is configured using HTTPS.

2.32 Start Menu

Start menus that contain more than 21 characters are not displayed properly in the search box in the Contributor interface.

2.33 System Tools

The ResultSet Summary screen refresh does not always refresh properly. Use the individual screen for each cache for more accurate reporting.

2.34 Tags

- The POST tag works incorrectly when a USERNAME, PASSWORD, or LOGOUT attribute are is passed to it. Log in and log out requests are sent to the URL being posted to, instead of CatalogManager. One workaround is to perform log in before this tag is executed. Alternatively, the FormPoster API can be directly used to perform the post operation.

- SEARCHSTATE.ADDRICHTEXTCONSTRAINT fails when the ResultSet returns more than 1000 rows.

- You cannot delete page and basic assets using the asset:void tag if a valid pubid is not present in the session. The workaround is to set the pubid in the session to "0", then remove it again after voiding.

2.35 User Interface Customization

If the left navigation and right navigation panels in LayoutConfig are swapped, the Contributor interface throws errors and does not load.

2.36 Vanity URLs

Prior to release 12.2.1, administrators configured a URL rewriter filter to resolve Vanity URLs by modifying the web.xml file. In release 12.2.1, administrators now configure the rewriter filter by modifying the site.prefix property in the wcs_properties.json file using the Property Management Tool, as described in Managing JSON File Properties in the Oracle Fusion Middleware Property Files Reference for Oracle WebCenter Sites. The site.prefix property provides a comma-separated list of unique site prefixes required for resolving vanity URLs using the rewriter filter.

2.37 Visitor Services

Configuring Visitor Services requires profile, identity, and access provider (optional) JAR files. You can create these files in the following ways:

- Create new implementations. For information, see Developing WebCenter Sites: Visitor Services in Oracle Fusion Middleware Developing with Oracle WebCenter Sites.

- Modify the sample source and Java files shipped with the distribution. These sample JAR and source files are available in the samples folder when Visitor Services is installed with the With Samples option selected in the Configuration Wizard. If you installed Visitor Services without the samples, contact Oracle Support for these JARs and source files.

2.38 WEM Admin Interface

- When you add a new site in the WEM Admin interface, a message may occur indicating that an error has occurred. This error message can be ignored.

- Case sensitivity for sorting is inconsistent.

- Deleting a site does not clean up the applications assigned to the site. To resolve this, manually remove the site entries from the urlaccessroles column in the FW_Applications table, using Oracle WebCenter Sites Explorer.

- You cannot assign roles to a user who has stale group membership data. The workaround for this is to edit and save the user in the WEM Admin interface.

2.39 WEM Framework

- The SiteAdmin role is not added to the user for the WEM Admin interface by default when the user has been assigned the SiteAdmin role in another site. The user should be manually assigned access to the WEM Admin interface application, if required.

- If the last accessed application or asset no longer exists, a subsequent log in to WebCenter Sites will result in a blank screen.

2.40 Workflow

Shared roles need to be reselected if a workflow report is edited after the initial save.

2.41 XMLPost

- When invoking the XMLPost utility, as described in Importing Assets of Any Type in Developing with Oracle WebCenter Sites, developers should include the ESAPI.properties file in the class path to avoid security warnings.

- XML namespaces are stripped from XML elements during evaluation.

- XMLPost is created as a recursive dependency on the asset during modification of a parent asset.

3 Limitations

This section describes limitations that you may encounter using WebCenter Sites.

Topics

- A/B Testing

- APIs

- Asset Type Name Restrictions

- Browser Support

- BulkLoader and BulkApprover

- CatalogManager

- CatalogMover

- CKEditor

- Collection

- Content Tags

- Contributor Interface

- Database

- Developer Tools

- Engage

- Installation of WebCenter Sites

- Localization

- Page Cache: inCache

- Publishing

- REST APIs

- Satellite Server

- Search

- Sites Explorer

- Site Capture

- Site Management

- Tags

- Template, Site Entry, and CS-Element

- Upgrade

- Vanity URL

- WebCenter Content Integration

- XMLPost

3.1 A/B Testing

- When you create customized goals for A/B testing of an asset, the Goals dialog box may load slowly.

- When you search for A/B tests because test summary data needs to be retrieved from Google, the Search results panel may load slowly.

- The data for A/B tests is only updated after every 24 hours. Therefore, there will be no data to review during the first day the test is running. The data that you review for every consecutive day after the first day will be approximately one day behind.

- If you use a free Google Analytics account, you can create a maximum of 20 A/B test goals.

3.2 APIs

- Dynamic loading of a new DataSource using the loadproperty tag is not supported.

- When the Asset API is used in a standalone application and called from the main method, it does not automatically terminate after the Asset API call is complete (unlike other Java applications). The reason is that the Asset API behaves like another cluster member of WebCenter Sites and boots up all the events in the background. To terminate, code should call System.exit(0).

3.3 Asset Type Name Restrictions

- All the administrative database tables created by WebCenter Sites are prefixed with FW_ and WCS_ (the tables were added after the 7.5 release of FatWire Content Server and 12.2.1 release of Oracle WebCenter Sites respectively). Asset types should not be created with a prefix of FW_ or WCS_.

- Do not use the names of any existing database tables while creating a new asset type. To see the list of existing database tables, from the Admin Interface, expand System Tools under the General Admin tree tab, and then double-click Sites Database. On the Sites Database form, specify % in the Enter Table Name field, select Modify Table, and then click OK to list all the database tables.

- For a given database, the name of a flex asset type must have ten characters less than the maximum number of characters that are allowed for database table names.

- For a given database, the name of a basic asset type must have five characters less than the maximum number of characters that are allowed for database table names.

- The attributes "Start Date" and "End Date" are reserved because WebCenter Sites uses them for out-of-the-box asset types. They should not be used in user-created AssetMaker assets.

- Do not create attributes for assets or assets with the names such as "name", "createdby", "createddate", "updatedby", "updateddate", "startdate", "enddate" and "description" because these attributes are default attributes for every asset that you create.

- If an asset name has multibyte long text, connector admin rules cannot be created.

3.4 Browser Support

- If Apache Web Server is not configured to use HTTP 1.1, pages will be cached by Internet Explorer.

- In Internet Explorer, the Tools > Internet Options > Settings > Every Visit to the page option must be set to true.

3.5 BulkLoader and BulkApprover

- Without validation, the utility ignores versioning of content. With validation, if the content type is under versioning, the utility will not update the content.

- Page cache is not flushed by BulkLoader. Because page cache is persistent, the cache should be cleared prior to running BulkApprover.

- Using BulkApprover requires running WebCenter Sites because BulkApprover is implemented via WebCenter Sites tags.

- Flex filters are not fired (for example, FieldCopier).

- BulkLoader does not support blobs. For this, you should use XMLPost.

- Start and end date cannot be specified nor configured for bulk transferred assets using BulkLoader.

- BulkLoader should not be executed while WebCenter Sites is running.

- When assets are added using BulkLoader, the assets will not be indexed in Lucene. You will need to re-index after import.

- Running multiple BulkLoader instances is not recommended unless they are performing the same operations; for example, all insert or all update, and multiple source tables do not refer to the same asset. Doing so would cause data corruption.

- BulkApprover will not update the PubAsset table to reflect the publish status after running Approve and Mark Publish.

3.6 CatalogManager

- If revision tracking is enabled for an object table, and you delete the table using CatalogManager, WebCenter Sites continues to treat the table as revision tracked.

- WebCenter Sites allows the value in the tablename column in the SystemSQL table to be null. However, for ResultSet caching to work properly, this value must be specified.

- You cannot log in to WebCenter Sites if your user name has the "id" value of an existing user in the SystemUsers table. For example, DefaultReader has an ID value of 2. If you create a user with the user name "2," that user cannot log in.

3.7 CatalogMover

CatalogMover does not export from columns that hold blobs. For example, a table is created with a column using the data type specified by the property cc.blob. An image is uploaded to the table. When CatalogMover exports the row, the image is not written to the export data.

3.8 CKEditor

In Windows environments, import of Flex assets with CKEditor and TextArea attribute editors fails.

3.9 Collection

Modifying the rank of assets in a collection that has been previously approved does not put the collection into the approval queue, even after rebuilding.

3.10 Content Tags

Newly added tags appear in search results only after a refresh.

3.11 Contributor Interface

- Use of the browser back button is not supported in this release.

- Approval and Delete listing screens show references based on evaluation of the layout template. If the layout template execution fails for any reason, the assets presented in the tables may not be correct.

- Page Layout allows for multiple levels of nested slots. However, the slot properties are only for the first two levels. The tool allows drag-and-drop to multiple levels.

- Drag-and-drop in the Contributor interface will not work if the page uses an iFrame.

- Clarkii Image Editor is not supported in Web Mode.

- Changing device views in Web Mode will not retain unsaved changes.

- The Contributor interface does not support multiselection of items in docked search mode.

- The use of Internet Explorer in Compatibility Mode is not supported.

- If you edit a site in the Web mode, Float values for Flex asset attributes get rounded off.

- After a session expires, if you click in the Search drop-down in the Contributor interface, an error message is displayed instead of getting redirected to Session Timeout screen.

- During Site preview, the calendar widget in the Contributor interface does not display time as per the user time zone.

- If you provide invalid values (values of different data types together, for example, date and money types ) for pull-down attribute editors, Contributor interface alignment gets distorted.

- Refresh does not work in Delete assets form of an asset.

3.12 Database

WebCenter Sites 12c uses the length specification for strings to specify the underlying database column sizes in bytes. When specifying the maximum length of a text field, keep in mind that multibyte characters will need more bytes per character. The maximum length is limited to 64 bytes for the Name field and 128 bytes for the Description field respectively.

3.13 Developer Tools

- Developer Tools does not support assets enabled for revision tracking.

- Importing assets into the SQLServer database from Oracle database, using CSDT Eclipse or CSDT Command Line Interface(CLI) utility fails.

3.14 Engage

On HTTPS servers, visitor segments are not retrieved.

3.15 Installation of WebCenter Sites

- When cs.use.short.jsp.names=false (the new default value, which used to be true by default), JSP elements that contain dots (such as www.xyz.com/common/flexLinkButton) will not be deployed properly. They will be deployed without the .jsp extension. As a result, the application server will not be able to run them. To work around this, if you use dots in your JSP element names, set cs.use.short.jsp.names=true.

- When installing a web server in between Remote Satellite Server and WebCenter Sites, you must set the cookie header property http.protocol.single-cookie-header=true in the httpaccess.properties file and place it in the remote_satellite_server install folder/WEB-INF/classes folder.

- For security reasons, Oracle recommends providing only internal access for the following servlets:

- CacheServer

- CatalogManager

- ContentServer (if you are using Satellite Server only)

- DebugServer

- DispatchManager

- FlushServer

- HelloCS

- Install

- Inventory

- PageDispatcherServer

- REST (unless you want to allow REST requests to your delivery server; they are password-protected)

- SeedDispatchServer

- SyncSeedDispatchServer

- TreeManager

- Sites installation (with sample sites) integrated with Oracle Traffic Director (OTD) fails in Bootstrap process due to timeout issues.

3.16 Localization

- Non-ASCII characters should not be used in the following Form Name Fields:

- Site

- Template

- Site Entry

- CS-Element

- Attribute

- Recommendation

- Segment

- Use only alphanumeric characters for the following:

- AssetTypes

- Asset Definitions

- Asset Subtypes

- Legal Arguments

3.17 Page Cache: inCache

- Persisting cache to disk clears the Last Access Time and hit count on Remote Satellite Server.

- The recommendation is to initialize inCache by accessing one page of the site from each of the WebCenter Sites cluster members.

3.18 Publishing

- Ensure that the maximum number of open file handles for your publishing destination operating system is set to 65000. The source system should be set to at least 32000. These numbers are only a guideline and may need to be adjusted based on the type of data and size of publishing operations.

- Export to Disk: Exported page is effectively rendered with wrong template when using SIMPLENAME. Contact technical support for a utility to remove the duplicate pub keys.

- Publishing is not supported from multiple development WebCenter Sites instances to a single delivery WebCenter Sites instance.

3.19 REST APIs

- The INPUTFORM tag support is limited in the Asset API when you are creating basic asset types via REST. As a result, unsupported INPUTFORM TYPES are interpreted as <INPUTFORM TYPE="TEXT" WIDTH="48" REQUIRED="YES"/>. For users to see proper asset type attributes in WebCenter Sites interfaces, the INPUTFORM tags need to be updated in the asset descriptor file through the database (AssetType table in Oracle WebCenter Sites Explorer).

- Setting BufferingConfig.xml to use multiple threads is not supported.

- When using the REST APIs, you may see the following message displayed on the server side. The message can be safely ignored:

com.sun.jersey.core.impl.provider.xml.SAXParserContextProvider getInstance
WARNING: JAXP feature XMLConstants.FEATURE_SECURE_PROCESSING cannot be set on a SAXParserFactory. External general entity processing is disabled but other potential security related features will not be enabled.
org.xml.sax.SAXNotRecognizedException:http://javax.xml.XMLConstants/feature/secure-processingSAXParserFactory.

3.20 Satellite Server

WebCenter Sites and Satellite Server must be configured to be in the same time zone.

3.21 Search

- Lucene fails to index text that comes after dashes, underscores, and other special characters.

- If indexing takes longer than the cs.timeout setting, exceptions will be thrown and indexing may be in an unstable state. The timeout should be adjusted based on the size of the index.

- SQL Server only stores milliseconds up to 3.33 millisecond precision with the data type DATETIME.

- WebCenter Sites does not support indexing of legacy Word 95 documents and throws exceptions in the logs.

- Lucene standard analyzer treats words differently if they contain a hyphen (-). For example:
ABC-DEF-HIJ is sometimes indexed as one word and sometimes indexed separately as "ABC" and "DEF-HIJ"; when this occurs, searching for "ABC-DEF-HIJ" will not always return the proper results.

- Searching for text within XML or HTML tags is not supported.

3.22 Site Capture

- Status messages are not shown in the application user interface. Check the crawler.log file for log messages.

- Site Capture session failover is not supported in this release.

3.23 Sites Explorer

Oracle WebCenter Sites Explorer fails to start on some Windows 2008 R2 servers.

3.24 Site Management

- Creating a site without a Preview asset assigned results in errors in the log, which can be safely ignored.
CS.XCELERATE.ASSET][ERROR] error: unable to load asset type information for Variables.previewAssetType, in tag asset.load pagename:OpenMarket/Xcelerate/Admin/SiteFront" and "[CS.XML][ERROR] object.get no object named previewAsset"

- Site names that include a hyphen ('-') are not supported if you are using LDAP.

3.25 Tags

The choice of values entered for a variant attribute used in insite:calltemplate must be applicable to all types valid for the clegal argument.

3.26 Template, Site Entry, and CS-Element

- Wrapper pages with "." in the name will not execute. Templates and Site Entry assets should not have a dot (.) in their names.

- Do not use the tag <throwexception> in the code of a template asset. The <throwexception> tag effectively terminates execution in WebCenter Sites for itself and any nested or parent WebCenter Sites engine. This breaks template execution and streaming of data to the client. In addition, when a user approves a template for export publish, a <throwexception> terminates the execution of the approval page and the user gets no feedback.

- No warning is given regarding the potential for broken pages when templates are deleted. Users should delete templates with care because they may be used as default templates in other assets. Deletion will result in failure to render those pages.

3.27 Upgrade

In upgraded environments, sample sites’ pages of Default, Touch, and Non-Touch site navigations may not be accessed at all times.

3.28 Vanity URL

- Removing a URL pattern does not remove the URLs based on that pattern.

- When there are multiple vanity URLs for the same asset, all having the same URL arguments (Template, DeviceGroup, Wrapper), the LinkBuilder API returns the vanity URL  based on its date of creation. The oldest vanity URL is returned instead of returning the vanity URL designated as the default URL by the user.

3.29 WebCenter Content Integration

When importing assets into WebCenter Sites, the WebCenter Content connector does not check asset permissions and will take action regardless of asset-level restrictions (for example, if the asset is revision tracked). This is an Asset API limitation.

3.30 XMLPost

When web server exists in a different machine, importing assets with XMLPost fails.

4 Configuration Issues and Workarounds

There are no known configuration issues at this time.

5 Demonstration Purposes Only

Areas of documentation that reference the shopping cart functionality are for demonstration purposes only. These topics are in the following documents:

- See What You May Need to Know About Shopping Carts and Engage in Developing with Oracle WebCenter Sites.

- See The Shopping Cart Criterion in Using Oracle WebCenter Sites.

- See Oracle Fusion Middleware Tag Reference for Oracle WebCenter Sites.

6 Documentation Errata

This section describes documentation errata for Oracle Fusion Middleware Java API Reference for Oracle WebCenter Sites: Visitor Services.

Topics

- Cache Tool Resources Missing from Java API Reference for Oracle WebCenter Sites: Visitor Services

- Updated Parameter in the getAggregatedProfile API Methods

- Visitor Services Sample Code

6.1 Cache Tool Resources Missing from Java API Reference for Oracle WebCenter Sites: Visitor Services

Cache Tool Resources:
GET

http://<host>:<port>/<context>/rest/v1/cachetool/{region}/list
The resource endpoint can be used to fetch the list of all the providers currently installed in Visitor Services.

REQUEST:

Path Parameters: Name Description Format

Region: Accepts the values common and shared_cache. Common returns the list of all the installed providers, and Shared_cache returns the list of all the installed providers with the date of install/update String.

RESPONSE:

Supported Media Types: application/json

200 Response: The list of installed providers.

Example 6-1 Example 1: Fetch the list of currently installed providers

curl -i -H "Accept: application/json" -X GET
http://<host>:<port>/<context>/rest/v1/cachetool/common/list
Response:
Content-Length:1111
Content-Type:application/json

{
"type": "cacheToolResponse",
"status": "success",
"entry": {
"entry": [
{
"key": "profileProviderConfig.pr1",
"value": "profileProviderConfig.pr1"
},
{
"key": "profileProviderConfig.pr2",
"value": "profileProviderConfig.pr2"
},
{
"key": "profileProvider.pr1",
"value": "profileProvider.pr1"
},
{
"key": "profileProvider.pr2",
"value": "profileProvider.pr2"
},
{
"key": "identityProviderConfig.identityProvider1",
"value": "identityProviderConfig.identityProvider1"
},
{
"key": "identityProvider.identityProvider1",
"value": "identityProvider.identityProvider1"
}
]
}
}

Example 6-2 Example 2: Fetch the installed/updated time of currently installed providers

curl -i -H "Accept: application/json" -X GET
http://<host>:<port>/<context>/<rest>v1/cachetool/shared_cache/tool
Response:

Content-Type:application/json
{
"type": "cacheToolResponse",
"status": "success",
"entry": {
"entry": [
{
"key": "profileProviderConfig.pr1",
"value": "Fri Sep 04 12:03:41 IST 2015"
},
{
"key": "profileProviderConfig.pr2",
"value": "Fri Sep 04 12:03:41 IST 2015"
},
{
"key": "profileProvider.pr1",
"value": "Fri Sep 04 12:03:41 IST 2015"
},
{
"key": "profileProvider.pr2",
"value": "Fri Sep 04 12:03:41 IST 2015"
},
{
"key": "identityProviderConfig.identityProvider1",
"value": "Fri Sep 04 12:03:41 IST 2015"
},
{
"key": "identityProvider.identityProvider1",
"value": "Fri Sep 04 12:03:41 IST 2015"
}
]
}
}

6.2 Updated Parameter in the getAggregatedProfile API Methods

The public String getAggregatedProfile(String visitorId, String rule, boolean updated) and public String getAggregatedProfile(String visitorId, String rule) methods use the same REST point:

http://host:port/context/rest/v1/visitor/id/visitorId/profile/aggregated/rule

The method to use depends on the query parameter updated in the REST URL; for example, the URL http://host:port/context/rest/v1/visitor/id/visitorId/profile/aggregated/rule ?updated=true will use public String getAggregatedProfile(String visitorId,String rule, boolean updated). However, if you do not provide the query parameter updated, then the public String getAggregatedProfile(String visitorId, String rule) is called, which ultimately calls the first method with 3 parameters only, passing the value of the updated parameter as false. These two methods simplify the APIs for those who do not want to provide any value for the updated parameter so that they can call visitorClient.getAggregatedProfile(visitorId, rule) instead of having to specify the value false: visitorClient.getAggregatedProfile(visitorId, rule, false).

6.3 Visitor Services Sample Code

If the With Samples option is selected, the distribution includes the samples folder. The samples folder contains the source code and JAR for the default provider bundles available in WebCenter Sites. This sample code can be used for modifying the code in the default provider bundles, or it can be used as a starting tool for creating custom provider bundles.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2018, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.