2 Oracle WebCenter Sites

This chapter describes issues associated with Oracle WebCenter Sites. It includes the following topics:

2.1 What's New in This Release

WebCenter Sites introduces new features focused on ease-of-use for marketing personnel and includes integration with other Oracle products that are part of the digital marketing ecosystem. The new features are:

2.1.1 Support for Mobile-Optimized Websites

Many new capabilities extend WebCenter Sites for use in building mobile-optimized websites:

  • Detection and identification of mobile devices making requests.

  • Device group management, which includes definition of groups with similar characteristics (such as screen size, tablet devices, non-touch devices) to aid with mobile site management.

  • Site plan updates that allow creation of multiple site plans to support delivery of different site navigations to mobile devices.

  • Drag-and-drop assembly of mobile pages.

  • Preview of websites for different mobile devices.

  • In-context editing of mobile pages.

  • Ability to run variations of the website using the same URLs (for example, one website for desktops, one for tablets, and one for smartphones, as opposed to creating a separate 'm.' variation of the site).

  • Ability to manage mobile templates from WebCenter Sites: Developer Tools.

2.1.2 Updates to Content Targeting (Engage Component)

The following new features are included for content targeting:

  • Content Tagging and Content Queries: In the Contributor interface, tags consisting of single words or short phrases can be attached to content. These tags can be placed across different assets types. Content queries can then be written using the tags and other metadata for use in search and in targeted recommendations.

  • New Segment and Recommendation Interface: The Engage Segment and Recommendation interface has been enhanced with an entirely new interface for specifying filtering criteria and allowing for more intuitive creation of site visitor segments. Recommendations can also now be created by use of drag-and-drop functionality.

  • Preview by Segment: After the creation of segments and recommendations within the Engage interface, the website can be previewed in the context of different segments.

  • REST API Updates: The WebCenter Sites REST API has been updated to include APIs to access recommendations.

2.1.3 Marketing-Friendly URL Management (Vanity URLs)

URLs to any asset in WebCenter Sites can now be easily created and managed. Content authors and marketers can do the following:

  • Create short, human readable, easy-to-control URLs that are SEO friendly for any web content. These can be either pattern-based for similar content or contributor defined. URLs could point to any host name, desktop version of the site or a mobile device, specific template and wrapper.

  • Control redirection with specific HTTP status.

  • Auto-generate URLs according to user-defined patterns.


    A utility is shipped in the \misc folder of the WebCenter Sites distribution to allow you to apply these changes to existing assets.
  • Generate reports on all URLs managed in the system. Administrators can run queries against these URLs and manage URL cache from System Tools for bulk URL management.

2.1.4 New Integrations

WebCenter Sites includes the following new integrations and features to incorporate assets and capabilities from other products in the digital marketing ecosystem:

  • Proxy Assets Framework: New APIs are included that allow for access to external content from the Contributor interface. External content can therefore be referenced from WebCenter Sites without duplicating or copying the content into WebCenter Sites. Contributors can access that content by using content trees, preview, and search, and then drag and drop the content into slots. A reference integration with YouTube is included to demonstrate access to video content inside the Contributor interface.

  • WebCenter Content Integration: Content items stored in WebCenter Content can be migrated to WebCenter Sites according to a configured attribute mapping. A simple Sync to Sites check box can be selected in WebCenter Content to select which content to copy and to keep it synchronized with WebCenter Sites when the connector runs. Administration tools are included in WebCenter Sites to configure the connector, manage the connector configuration, and monitor the synchronization process.

  • Real-Time Decisions (RTD) Integration: Users can now automate and optimize targeting by combining WebCenter Sites managed segments with the RTD-automated predictive content recommendations engine. This release includes an API to invoke Real-Time Decisions from WebCenter Sites to get recommendations.

2.1.5 AviSports Sample Site Updates

The avisports demonstration website has been updated to include examples of targeting, mobile websites, and workflow.

2.1.6 Platform Updates

Platform updates include support for Oracle HTTP Server (OHS), updated browser support, an update to the CKEditor version (we are now shipping version, and a new operating system and application server support for Community-Gadgets. Refer to the Oracle WebCenter Sites Certification Matrix for more information.

2.2 Deprecated Functionality

  • The following functionality is deprecated, starting with the release:

    • Mirror publishing. Use RealTime publishing, instead.

    • SOAP-based web services. Use the public REST API.

    • Page Debugger. Use IDE integration for JSP debug capabilities. DebugServlet is not deployed.

  • The following functionality is deprecated, starting with the release:

    • Static Publishing

    • Sites Desktop

    • Sites DocLink

2.3 Limitations

2.3.1 Asset Type Name Restrictions

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

  • The following tables display the asset type names used by WebCenter Sites:

    Table 2-1 lists asset types that are created by default:

    Table 2-1 Default Asset Types

    Default Asset Type Default Asset Type Default Asset Type




    Content Query



    Device Group
















    Site Plan





    Table 2-2 lists asset types that are installed by the avisports sample site:

    Table 2-2 Asset Types in the Avisports Sample Site

    Avisports Asset Types Avisports Asset Types Avisports Asset Types










    Table 2-3 lists asset types that are installed by the FirstSite II sample site:

    Table 2-3 Asset Types in the FirstSite II Sample Site

    FirstSite II Asset Types FirstSite II Asset Types FirstSite II Asset Types































    Table 2-4 lists names (in alphabetical order) that are reserved for use by WebCenter Sites and must not be assigned to custom asset types:

    Table 2-4 Restricted Names for Asset Types

    Restricted Names Restricted Names Restricted Names Restricted Names
































































































































































































































    Any name that starts with VMz


















    WorkflowGrp Actions
















  • 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.

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

2.3.2 API

  • Dynamic loading of 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 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)

2.3.3 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 must be set to true.

  • CKEditor is not currently supported for Internet Explorer 11.

  • For information about browser support for Community and Gadgets interfaces, see Section 3.2.1, "Browser Support" in Chapter 3, "Oracle WebCenter Sites: Community-Gadgets."

2.3.4 BulkLoader and BulkApprover

  • Without validation, the utility ignores versioning of content. With validation, if the content type is under versioning, it 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, as it 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 it is performing the same operations for example, all insert or all update and multiple source tables do not refer to the same asset. Doing so will cause data corruption.

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

2.3.5 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 username "2," that user cannot log in.

2.3.6 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.

2.3.7 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.

2.3.8 Content Tags

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

2.3.9 Contributor Interface

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

  • Approval and Delete listing screens shows 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 multi-selection of items in docked search mode.

  • Use of Internet Explorer in Compatibility Mode is not supported.

2.3.10 Developer Tools

  • Developer Tools export created from Content Server 7.6 patch 2:

    Import will not succeed if it contains Page Assets. The recommendation is to upgrade to WebCenter Sites 11gR1 and then re-export by using the Developer Tools Plug-in for this version before the next import.

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

2.3.11 Database

WebCenter Sites 11gR1 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.

2.3.12 Installing 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.

  • If your installation of WebCenter Sites fails, take the following steps before re-executing the installation:

    • Drop the database tables.

    • Undeploy the .ear/.war file.

    • Delete the WebCenter Sites installation folder.

    • Restart the application servers and web servers.

  • 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

  • If you enable J2EE security on WebSphere 8.0, you will need to add additional classes to the security policy in the .ear file. Two of these are:

    • java.lang.reflect.ReflectPermission.suppressAccessChecks

    • java.lang.RuntimePermission.modifyThreadGroup

  • For security reasons, we recommend providing only internal access for the following servlets:

    • Install

    • HelloCS

    • CatalogManager

    • TreeManager

    • CacheServer

    • Inventory

  • WebCenter Sites is not supported on OHS Webcache with WebLogic domain. Currently this is supported on OHS in standalone mode.

2.3.13 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

2.3.14 OAM Integration

2.3.15 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.

2.3.16 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 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.

2.3.17 REST API

  • The INPUTFORM tag support is limited in the Asset API when 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 Sites Explorer).

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

  • It is possible to create duplicate fw_uid if you perform a GET operation and use PUT on the resulting bean when using the REST API. In this scenario, a new asset with a different asset id will be created, but it will still have the same fw_uid. The workaround is to clear the fw_uid in the bean before performing the PUT operation.

  • When using the REST API, you will 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.

2.3.18 Satellite Server

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

2.3.19 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 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.

2.3.20 Sites Explorer

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

2.3.21 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.

2.3.22 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 using LDAP.

2.3.23 Sites DocLink (Deprecated)

  • If Windows is configured using the "Show All Folders" option, if your session times out and you are using Sites DocLink, the login window will appear when Explorer loads the shortcuts.

  • Revision tracking of DocLink assets is not supported in this release.

2.3.24 Sites Desktop (Deprecated)

Revision tracking and workflow are not supported from Sites Desktop in this release.

2.3.25 Tags

  • Choice of values entered for variant attribute used in insite:calltemplate must be applicable to all types valid for clegal argument.

  • Change of behavior for render:callelement from FatWire Content Server 7.x to WebCenter Sites 11g Release 1:

    In earlier versions of WebCenter Sites, <render:callelement scoped="local"> would copy all variables from the calling element to the called element, which was a bug. In 11gR1+, the behavior has been corrected to match the documentation in the Oracle WebCenter Sites Tag Reference and it will now only copy over those variables that are passed to the called element as arguments. To retain the incorrect behavior, you can add -DuserLegacyLocalScoping=true to the JAVA_OPTS of the application server.

2.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, as they may be used as default templates in other assets. Deletion will result in failure to render those pages.

2.3.27 Vanity URL

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

2.3.28 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.

2.4 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topic:

2.4.1 API

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

  • JSP processing adds whitespace.

  • When using asset:export / asset.export tags on an asset that isn't a page or collection, the output XML doesn't contain info about the unnamed associations.

  • The Asset API Tutorial contains example byte d = fileObj.getBinary(); However getBinary() no longer exist. It has been changed to getBinaryStream() which returns an InputStream. Instead of byte d = fileObj.getBinary() , the example should be changed to: byte d = newbyte[fileObj.getBinaryStream().available()];

  • 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.4.2 Admin Interface

  • In the Admin interface, the tree applet will not reflect changes when Start Menu name is edited.

  • Downloading thread dumps from the System Tools is not supported for WebSphere.

  • 500 error is thrown if you browse directly to the WebCenter Sites-Cache status page when AssetCache is not started or enabled.

  • Pasting text using Ctrl+V into the query box of the Log Viewer triggers the View Logs function. The correct shortcut for log viewer functionality is Ctrl+Shift+V.

  • Downloaded log files from System Tools do not include information from cas.log.

  • Right-clicking REFRESH does not 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 is not displayed in graph form in Internet Explorer. To view this graph, use Firefox.

  • When creating a new AssetMaker asset type, using the tab key to move through the fields will result in the Browse button disappearing from view. Clicking in the area where the button originally appeared will allow browse to continue.

  • Setting the xcelerate.showSiteTree property to false does not turn the applet off in the Admin interface.

  • When WebCenter Sites is configured to use hierarchical LDAP, if the user only has access 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.3 Analytics Integration

Assets deleted in the Contributor interface are not reflected in the Analytics data.txt file.

2.4.4 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.4.5 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 5MB 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 un-linked cache. If there is an un-recognized 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.4.6 Browser Support

  • Selecting Delete from the top menu in the Contributor interface will throw a JavaScript error when Internet Explorer 9 is used. To avoid this issue, delete by using the Delete button.

  • The Site Plan tab in the Contributor interface may not display properly on initial login when Internet Explorer 10 is used. Refresh the page to correct this.

  • When using Chrome, unable to upload user avatar.

  • The Admin interface tree applet fails to load in Chrome when the browser is run on Linux.

  • In Internet Explorer 9, the Web Experience Management (WEM) Framework site selector drop-down list is not populated with sites when the user name contains non-ASCII characters.

  • In Web Mode, the upload icon does not appear in Internet Explorer 10. Switch to form mode to upload files or images.

  • In Internet Explorer 9, the selected date is shown in UTC format in Web Mode.

  • The Contributor interface is best viewed at 100% zoom. Changing this to a higher zoom results in unexpected behavior such as:

    • All drag-and-drop fields may not appear in Web Mode.

    • Additional horizontal and vertical lines appear.

  • In Site Capture, the Archive ID fails to show when sort by ID is selected on the Archive page.

2.4.7 Caching: inCache

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

2.4.8 Caching: Satellite Server

  • Any blob which 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.


    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.4.9 CKEditor

  • Anchor name is added before the selected text when using Internet Explorer 9.

  • Upgraded assets may have an extra <p> <span> added when viewed in Form Mode post upgrade. This can be resolved by changing the attribute to use the updated CKEditor.

  • For assets created prior to Content Server 7.5 Patch 1 - If the first piece of data in the FCKEditor window is an embedded link or included asset, you must switch to source view to add additional content prior to the embedded link or included asset. Similarly, if the last asset is an embedded link or included asset, source view must also be used to add additional content immediately following the link or included asset.

  • Frame shows "Loading" message if target is set to "not set", "frame" or "Same Window (_self)" while creating the external link in CKEditor.

2.4.10 Cluster

For a WebSphere cluster, user session replication for the management interfaces will not properly failover in all scenarios when one cluster member fails.

2.4.11 Content Query

Content Query throws errors when selecting an assettype which contains a subtype.

2.4.12 Contributor Interface

  • If there is a failure due to template compatibility reasons while swapping a slot, 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 Admin.

  • When 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 result in 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.

  • Progress bar is not displayed accurately for large file uploads (>64MB) for Basic Assets.

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

  • Setting bs.security=true results in a failure of the 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.

2.4.13 Developer Tools

  • Importing a Developer Tools export from version or to will fail if the export includes fw_attributeeditor or fw_uiconfiguration assettypes, users should remove these types from the datastore prior to the import.

  • Developer Tools import from version 7.6.x will not be successful if the DatePicker attribute editor is included in the datastore, as the calendar is different between this version and 11gR1+. Remove the attribute to import this data.

  • 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 filename length of exported file exceeds the operating system filename limitation, the file cannot be exported. This is likely to happen if the filename of uploaded blob is too long.

  • Deleting a site does not update information about the exported assets. The workaround is to first unshare the assets from the site which you wish to delete, and then delete the site.

  • Deleting of non-asset resources should be done manually on each destination. This is currently no sync for deleted non-asset resources.

  • User 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 which include slashes or commas cannot be exported.

  • The Sync and FW workspace views in Eclipse do not properly display UTF-8 characters on Windows.

  • The locale hierarchy information is not preserved for 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.

  • The Developer Tools Eclipse Plug-in auto complete will add double quotes if your application server does not support this. The double quotes must be changed to single quotes manually.

  • Import fails to import segment assets when the segment criteria contains history definition with string value.

  • When connecting to a remote instance, the project WEB-INF folder points to a non-existent 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.

  • In some Linux systems, the WebCenter Sites interface and log sections are not appearing.

  • Site Entry creation fails via Developer Tools.

2.4.14 Engage

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

2.4.15 Flex Assets

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

  • Parent asset cannot be deselected when using Select Box attribute editor for an optional parent attribute. The workaround is to use Pick from Tree.

2.4.16 Installation / Upgrade

  • Going back or restarting the installation process after entering passwords requires that the passwords be re-entered, or the system defaults will be used.

  • During upgrade, the following ERROR may appear in the sites log and can be safely ignored:

    [com.fatwire.logging.cs] Exception loading properties from file list futuretense.ini java.lang.Exception: Required key not found: cs.pgCacheTimeout"

  • Installation should not be initiated to a path that includes multibyte characters.

  • "Exception loading applications assetcom.fatwire.assetapi.common.AssetAccessException: asset type FW_Application cannot be found in Content Server" may appear in sites.log when installing avisports sample site, or when a new site is created. This exception can be safely ignored.

  • Occasionally, the midpoint installation tests will fail for WebSphere secondary cluster member. If this occurs, try again. The same issue may occur on login after a restart.

  • Download patch 14847089 if installing on WebSphere to avoid the following exception after starting the server during installation:

    JPAPUnitInfo  E   CWWJP0015E: An error occurred in the org.eclipse.persistence.jpa.PersistenceProvider persistence 
    @ provider when it attempted to create the container entity manager factory for the JpsDBDataManagerV3 persistence unit. The following error occurred: 
    at java.net.URLClassLoader.findClass(URLClassLoader.java:434) 
    at java.lang.ClassLoader.loadClass(ClassLoader.java:646)

2.4.17 Mobility

  • 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.

  • Entering more than 31 characters in the device name field will result in the name appearing outside the device area in multi-device preview.

2.4.18 Performance

The tree applet in the Admin interface takes 2 to 4 minutes to release memory used when switching sites. This is a JRE limitation.

2.4.19 Proxy Assets

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

2.4.20 Publish Console

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

2.4.21 Publishing

  • 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 only publishing 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 via REST and Developer Tools import / export.

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

2.4.22 REST API

  • When you use an invalid multi-ticket in a REST call to Satellite Server, instead of redirecting to the login screen, it throws the following exception: javax.servlet.ServletException: Failed to parse assertion for multi ticket xxx

  • When you use an invalid multi-ticket in a REST call to Satellite Server, it does redirect to the login screen. However, instead of generating a ticket and displaying the requested information, the redirect fails, and an error is shown.

  • Initiating a REST call 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 is not returned with the ordinal value.

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

  • When under load, the following exception may occur when using 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

  • Content-type header must be set to allow delete operations.

  • When creating asset types in REST, Plural Form is not reflected/honored in the Admin interface.

  • Invoking the Delete method on a non-existent object returns a 200 status code.

  • Update is not working for 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 will fail with a 500 error.

  • The Navigation service will return a 500 instead of 200 error if there are no Page assets.

  • Although description is a required attribute for a Site, the WebCenter Sites REST service doesn't validate for a Site description during create/edit.

  • When roles are deleted via REST, the corresponding entry for Site and Users is not deleted. Use WEM Admin interface to delete a role or manually clean up the UserPublication table to remove the dependencies.

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

  • 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.4.23 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 on 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.4.24 Satellite Server

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.4.25 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.

2.4.26 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. It is recommended to create 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.

2.4.27 Site Launcher

Sites Desktop information in the replicated site does not set the description field for Sites Desktop to enabled in the copied site.

2.4.28 Site Plan

  • If a page is moved to a different site plan while another user is editing or viewing the page in the Contributor interface, the multi-device 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.4.29 Sites Desktop (Deprecated)

  • The following error may appear in the sites.log file when assets are created using Word 2010:

    [ERROR] [WebContainer : 6] [docx4j.openpackaging.contenttype.ContentTypeManager] No subclass found for /word/stylesWithEffects.xml.

    This error can be safely ignored.

  • Locale selected during creating an asset from Sites Desktop does not appear in Sites Desktop before save even though it is saved correctly.

  • Unable to upload multiple images to a multivalued attribute.

  • Unable to reorder multivalued attributes in Sites Desktop.

2.4.30 Sites DocLink (Deprecated)

  • Unable to create translated assets using 'copy' option.

  • After the Document Type is changed in WebCenter Sites, refreshing DocLink does not make this change active. The user must log out and log back in for the change to take effect.

  • Required fields are not marked as "Required" in the DocLink Edit Configuration screen.

2.4.31 Sites Explorer

Login via Sites Explorer on Windows 2008R2 over https fails to authenticate. It is recommended to use Sites Explorer on Windows XP or Windows 7 if configured using https.

2.4.32 Start Menu

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

2.4.33 System Tools

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

  • Setting fatwire.logging.cs.xml logger to DEBUG level will cause the Admin interface to fail to load properly until the server is restarted.

2.4.34 Tags

  • The POST tag works incorrectly when USERNAME, PASSWORD or LOGOUT attributes are passed to it. Login and logout requests are sent to the URL being posted to, instead of CatalogManager. One workaround is to perform login 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.

  • Unable to delete page and basic assets using 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.4.35 WebLogic Server

Exception is thrown when WebLogic Server starts. This can be safely ignored:

java.net.ConnectException: Tried all: '1' addresses , but could not connect over HTTP to server

2.4.36 WEM Admin

  • Case sensitivity for sorting is inconsistent.

  • Site names with special characters or symbols are not getting deleted. Delete the site by using the Admin interface.

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

  • 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.4.37 WEM Framework

  • The SiteAdmin role is not added to the user for WEM Admin 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 application, if required.

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

  • If an incorrect old password is entered when changing the password in the WEM Admin interface, selecting Save and Close will fail to display a warning that the old password is incorrect. The password will not be changed in this case.

2.4.38 Workflow

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

  • The DashUser role is listed in the list of Workflow Participants if the user was part of the group before upgrade. This user role should be removed and replaced with SitesUser.

2.4.39 UI Customization

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

2.4.40 Upgrade

  • The upgrade utility will not apply indexes to the tables listed below if the assets were created prior to version 7.6 Patch 2 and a previous upgrade was done to an earlier version of WebCenter Sites 11gR1. To take advantage of performance enhancements, apply indexes to these tables manually:

    • AssetType_Dim

    • AssetType_DimP

    • AssetType_Amap

    • AssetType_Group

  • After upgrade, the Content Query start menu is not present even though the asset type is enabled for sites. The start menu must be created manually.

  • The timezone utility does not update previously exported data that contains a user-defined attribute of type date. The serialized data needs to be manually updated to UTC before import.

  • For information about upgrading the Community Blogs module, see Section 3.4, "Upgrading the Community Blogs Module" in Chapter 3, "Oracle WebCenter Sites: Community-Gadgets."

2.4.41 XMLPost

  • XML namespaces are stripped from XML elements during evaluation.

  • XMLPost created as recursive dependency on the asset when modifying a parent asset.

2.5 Demonstration Purposes Only

Areas of documentation that reference the shopping cart functionality are for demonstration purposes only. These topics are in Oracle Fusion Middleware Using Oracle WebCenter Sites and Oracle Fusion Middleware Developing with Oracle WebCenter Sites.