This chapter describes issues associated with Oracle WebCenter Content: Imaging. It includes the following topics:
This section describes general issues. It includes the following topics:
Section 35.1.1, "Imaging Session Time Out When Using OSSO Requires Browser Refresh"
Section 35.1.3, "Deleting More Than 100 Documents Can Cause Http 404 Errors"
Section 35.1.4, "Time Zone Based on Time Zone of Imaging Server"
Section 35.1.5, "Imaging Documents May Be Visible Natively Within WebCenter"
Section 35.1.6, "Removing Full-Text Search Capabilities From Defined Applications"
Section 35.1.7, "Application Field Limitations When Using Oracle Text Search"
Section 35.1.10, "Must Start NFS Locking Service When Input Agent Used with Linux Shares"
Section 35.1.12, "Input Mapping Error When Input Definition File Includes Blank Line"
Section 35.1.13, "Differing Behavior of Decimals When Ingested Into Number or Decimal Fields"
Section 35.1.14, "Using Browser Forward, Back, and Refresh Navigation Not Recommended"
Section 35.1.15, "Document Upload or Update Failure if Content Server English-US Locale Not Enabled"
Section 35.1.16, "Document Move Failure if Content Server Not Started with English-US Locale"
Section 35.1.17, "Clearing Java Temporary Files of Cached Files"
Section 35.1.18, "Solution Editor Enabled Only On Imaging Systems Using an Oracle Database"
Section 35.1.20, "Viewer Cache Does Not Work After Upgrading or Patching"
When using Oracle Single Sign On and an Imaging session expires, WebLogic Server will return an internal server error. Refreshing the page returns to the Imaging log in page for reauthentication to start a new session.
Oracle products support 10 standard languages for administrative tasks and 27 standard languages for user tasks. This means that in instances when a selected language is supported for user tasks and an administrative task is performed, multiple languages may be displayed in the user interface.
There is a known issue with Microsoft Internet Explorer if attempting to delete more than 100 documents using a search results table. Doing so can cause Internet Explorer to return a 404 Page Not Found error or potentially lock. This is due to Internet Explorer limiting URL strings to a maximum of 2083 characters. If it is necessary to delete over 100 documents using a search results table, Mozilla Firefox supports URLs up to 65,000 characters.
All time information is now based on the time zone of the Imaging server. This means that any date metadata generated by the Imaging system, such as document creation date, modify date, or other audit events, is governed by the time zone of the Imaging server, and not the user time zone. This can cause date data to be displayed differently to what may be expected on some documents because the time zone may cross midnight.
For example, if the Imaging server is in the Greenwich Mean Time (GMT) time zone and a document is created in the GMT+6 time zone on January 10th at 2:00 AM local time, the creation date that will be displayed in the user interface will be January 9th at 8:00 PM. This can have implications when searching for content based on creation and modification dates of documents.
If an Imaging document is viewed through WebCenter, then the document is cached in WebCenter. This means that if a document is viewed in WebCenter prior to being annotated, the non-annotated document is viewable until such time as the WebCenter cache is refreshed. Redacting a document after it has been cached in WebCenter does not cause the original document to be purged from the WebCenter cache, and so redacted content may be compromised. To help protect redacted content when Imaging is integrated with WebCenter, use the Viewer on the Upload page to redact documents prior to uploading to Imaging.
Removing full-text search capabilities from a defined application can cause an error in any defined search against that application if the Document Content condition is not also removed from the search. When modifying an existing application to remove full-text indexing capabilities, ensure that you also remove all Document Content conditions from any defined searches against that application.
When Imaging is configured to use OracleTextSearch and an application is defined to do full-text indexing, a maximum limit of 20 SDATA fields for the Content Server repository is imposed on Imaging. SDATA fields are defined as optimized fields by the Oracle Text Search component and are typically non-text, non-memo fields, although other criteria can exist to define text fields as optimized SDATA fields.
When defining an application, Imaging queries the repository DOCMETA table for the number of available SDATA fields and does not allow the creation of any non-text fields within the application beyond the available number. However, additional components installed on the Content Server repository, such as Folders or Discussions, may reduce the total number of available SDATA fields. Because other configurations may consume SDATA outside of the DOCMETA table, you may be able to add fields to an application but get an error when trying to rebuild the search index in Content Server. If this occurs, you must redefine the application using a different Content Server connection with available SDATA fields. If no additional Content Server connection is defined, you can install and configure an additional Content Server and create a new connection to it in Imaging. Alternately, you can redefine the application using the original Content Server connection but with fewer non-text fields until you are able to successfully rebuild the search index.
Care should be taken when integrating Imaging with Oracle WebCenter Content: Records. If a document is uploaded into an Imaging application that has been configured to use a Records-only Retention Category and the user who uploaded the document does not have rights on the Content Server repository to see records, they will not be able to see any of the uploaded documents in an Imaging search. Rights to retention categories are determined in Records. If integrating Imaging and Records, ensure that all users needing rights to view records have the correct security, that Retention Categories are set correctly in all Imaging applications, and that users understand what can happen if the Records-only Retention Categories are used.
If leveraging AXF functionality with Imaging, the Listen Address base domain configured in the WebLogic Server console must match how the domain is specified in the URL used to access AXF. Otherwise content may not load properly and users may not have access to AXF. To configure the Listen address in AXF, do the following:
Log in to the WebLogic Server administration console.
Under the Environment section of the ecm_domain, select Servers. The Summary of Servers page is displayed with the Configuration tab active.
Click imaging_server<number>. The Setting for imaging_server<number> page is displayed for the selected Imaging server with the Configuration and General tabs active.
Set the Listen Address to the preferred URL. The Listen Address specified should be the base domain without the protocol.
Note:
The Listen Address base domain and the URL base domain used to access AXF must be identical. If the fully qualified domain name is used for the Listen Address setting, then it must also be used for the access URL, even when inside the domain. For example, if the base domain server_name.domain.com is used in the Listen Address configuration setting, the access URL would be http://server_name.domain.com:<port>/.
When Input Agent is being used with Linux and NFS shares, the NFS locking service must be started in addition to the other NFS services. If the NFS locking service is not running, Input Agent fails to acquire file locks and displays an error message stating that no locks are available. If this happens, Input Agent cannot function until the NFS locking service is started.
The functionality of the DefaultSecurityGroup MBean has been augmented. In addition to being the default security group to use for document security when creating an application, this setting can also be used during security initialization to assign full administrative permissions to a specified group. If a value is specified in the DefaultSecurityGroup MBean prior to Imaging security being initialized, then when the first user logs in, the specified group is given full administrative permissions as well as the user logging in.
Note that when mapping an input definition file, the input field mapping page may display an error if it encounters a line with no data in the definition file. Should this occur, map the fields using a line in the definition file that contains data. You can move to a different line in the definition file using the Show Previous Line and Show Next Line icons in the Sample Data column of the input field mapping page.
When ingesting a decimal representation of a whole number into a number field, the decimal is stripped. For example, "1.0" is ingested as "1." When ingesting a decimal that is not whole, the ingestor does not round the value and an error occurs. For example, "1.1" is not ingested into a number field and causes an error.
When ingesting a decimal value into a decimal field, the decimal value must not exceed the precision specified in the application, even if the represented value is the same. For example, if the application specifies a scale of 2, then "123.45" is ingested correctly, where "123.450" would cause an error. This is because "123.450" exceeds the number of decimal places allowed by the application. This behavior is consistent with the conversion routines available in Java.
Using browser navigation such as Forward, Back, and Refresh does not provide navigation within a document, a document's panels, or between document tabs open in the Viewer. Instead, browser controls navigate outside of the Imaging Viewer. When viewing a document, it is recommended that all navigation within the Viewer be done using the navigation controls in the Viewer toolbar.
The Content Server locale English-US must be enabled on the Content Server. Imaging documents will fail to upload or update if the English-US locale in the Content Server is disabled. It does not need to be set as the active locale, but it must be enabled.
The Content Server must be initially started with the active locale set to English-US or moving Imaging documents from one application to another fails. Once started, the active locale can be changed and documents can be successfully moved as necessary.
When viewing files in advanced mode, some files are cached on the local client computer. If storage space is a concern on the client computer, manually delete any cached files in the client temp directory.
The Solution Editor is enabled in the Tools menu of the Navigator Pane provided that Imaging is using an Oracle database. If Imaging is using a database other than Oracle, access to the Solution Editor is not available.
The following configuration MBeans are read only and not included in Section 3.6, "Configuring MBeans" of the Oracle WebCenter Content Administrator's Guide for Imaging. They are part of Oracle's implementation of the Java Management Extension (JMX) standard and are visible in the Enterprise Manager System MBean browser but cannot be altered.
| MBean | Description |
|---|---|
|
ConfigMBean |
Indicates if this MBean is a Config MBean. Default: false |
|
eventProvider |
Indicates that this MBean is an event provider as defined by JSR-77. Default: true |
|
eventTypes |
All the event's types emitted by this MBean. Default: jmx.attribute.change |
|
objectName |
The MBean's unique JMX name . Default: oracle.imaging:type=config |
|
ReadOnly |
If true, it indicates that this MBean is a read only MBean. Default: false |
|
RestartNeeded |
Indicates whether a restart is needed. Default: false |
|
stateManageable |
Indicates that this MBean provides State Management capabilities as defined by JSR-77. Default: false |
|
statisticsProvider |
Indicates that this MBean is a statistic provider as defined by JSR-77. Default: false |
|
SystemMBean |
It indicates that this MBean is a System MBean. Default: false |
Beginning with the 11g Release 1 (11.1.1.7.0) patch set, follow these steps to enable the Viewer Cache in Imaging or to preserve it if upgrading. In order to enable the Viewer Cache, you will need to extend the Imaging domain with a new separately packaged Viewer Cache component. In previous releases, the Imaging domain was extended using a manually run script that produced the domain extension. However, the 11g Release 1 (11.1.1.7.0) patch set leverages a user friendly configuration wizard to provide the domain extension.
Note:
If you are upgrading from 11g Release 1 (11.1.1.4.0), 11g Release 1 (11.1.1.5.0), or 11g Release 1 (11.1.1.6.0) and you are already using the Viewer Cache feature, then you must complete the steps in this section to extend the domain to enable Viewer Cache in the 11g Release 1 (11.1.1.7.0) patch set.
To extend the Imaging domain:
Navigate to the following directory:
cd $ORACLE_HOME/common/bin
Run the following script to start the domain configuration wizard:
./config.sh
Select Extend an existing WebLogic domain and click Next. The Select a WebLogic Domain Directory screen is displayed.
Select the domain in which Imaging is currently configured. By default, the domain name of the ECM install is base_domain.
Click Next. The Select Extension Source screen is displayed.
Select Oracle WebCenter Content: Imaging Viewer Cache - 11.1.1.0 [wcc] and click Next.
If you are applying the patch set to upgrade from a previous release which already had the Viewer Cache enabled, the Conflict Detected dialog box is displayed indicating that the component Viewer JMS ConnectionFactory is already defined. Select the Replace existing component option and click OK. The Configure JDBC Component Schema screen is displayed.
Click Next. The Configure GridLink RAC Data Sources screen is displayed.
Click Next. The Test JDBC Component Schema screen is displayed.
Click Next and then click Extend.
Restart the system's Weblogic Managed servers.
Upgraded systems with previously configured Viewer Caches will operate as before. To take advantage of the new feature for the first time, use the steps listed in "Configuring the Imaging Viewer Cache" in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter Content.
This section describes browser compatibility issues. It includes the following topics:
Section 35.2.1, "IE: Non-ASCII Characters Not Supported in Internet Explorer for ExecuteSearch"
Section 35.2.2, "Firefox: Version and Download Dialog Boxes Appear Behind Viewer in Advanced Mode"
The Search URL Tool (ExecuteSearch) does not work in Microsoft Internet Explorer if non-ascii characters are used in the search name. If it is necessary for your search name to have non-ascii characters, you must use Mozilla Firefox version 3.5 or higher and set the following parameters:
prefs.converted-to-utf8=true
network.standard-url.escape-utf8=true
network.standard-url.encode-utf8=true
network.standard-url.encode-query-utf8=true
There is a problem with how Firefox 3.6, 5.0 and higher handles layer order of page items in the advanced mode of the Viewer. This causes the main page region where documents are displayed to hide the Version and Download dialog boxes when a document is viewed using Firefox. To work around this issue, expand the Properties, History, or Sticky Notes panel into the main page region enough to allow the obscured items to be displayed prior to accessing dialog boxes. This is not an issue when using Microsoft Internet Explorer or Firefox 3.5.x and a workaround would be to use either of these browsers to view documents when using the advanced Viewer mode.
The Viewer requires a Java SE Runtime Environment (JRE) plug-in to be installed to view documents in advanced mode. If a JRE is not installed, the Viewer will prompt you to install the plug-in the first time it is used in advanced mode. If using Internet Explorer 9, the link to install the JRE plug-in fails. If using Internet Explorer 9, you must obtain and install the JRE plug-in manually to use the Viewer in advanced mode.
This section describes accessibility issues. It includes the following topics:
Section 35.3.1, "Button Activation Behavior Different Depending on Viewer Mode"
Section 35.3.3, "Skip to Content Link Added for Keyboard Navigation"
Section 35.3.4, "Firefox: Skip to Applet Link Added for Keyboard Navigation in Advanced Viewer Mode"
Section 35.3.5, "Internet Explorer 7: Focus Issue on Upload Document and Preferences Pages"
Section 35.3.6, "Name of File Selected For Import Not Displayed in Screen Reader Mode"
Section 35.3.7, "Issues Selecting From Calendar Using Keyboard"
Section 35.3.8, "Focus Issue in Create Searches Wizard Using Keyboard"
Section 35.3.10, "Date Selected From Calendar Lost Using Keyboard"
Section 35.3.11, "Some Annotation Buttons Incorrectly Read by JAWS"
Section 35.3.12, "Internet Explorer: Long Panels Not Visible In Screen Reader"
The keyboard command to activate a button that has focus is different between basic and advanced Viewer modes. The enter key is used to activate a focused button when using the basic Viewer mode. The space key is used to activate a focused button when using the advanced Viewer mode.
The contents of sticky notes are not downloaded or printed with the document, nor are they viewable through the REST Viewer. The contents of a sticky note can be printed, with limitations, by expanding the sticky note in the Sticky Notes Panel and printing the web page.
The first link encountered on a page when using keyboard navigation in the Imaging user interface is a Skip to Content link at the top of the page. Selecting this link and pressing Enter takes the focus to the first item in the content region of the page. For example, if on the home page, the first content item is the help links. If a search has been executed and the results are displayed in the content region, then the Skip to Content link takes you to the first search tab.
When viewing a document in the advanced Viewer mode, keyboard focus starts in the Viewer toolbar. However, in Firefox, if focus moves out of the toolbar, it will not return when cycling through the elements using the keyboard. To work around this, a Skip to Applet link is at the top of the page. To return keyboard focus to the Viewer toolbar, tab to the Skip to Applet link and press Enter.
When using Internet Explorer 7, the keyboard appears not to focus on any command buttons on the Upload Document page (Open Viewer, Create, Reset, Close) or Preferences page (Apply, Revert, Close). Focus is achieved, however there is no indication which button is active. This issue does not occur in Internet Explorer 8.
When in screen reader mode and selecting a file to import, the file is loaded and the Next button becomes available, but the name of the file to be imported is not displayed.
In Internet Explorer 7, when selecting dates from a calendar using the keyboard, you cannot select a day. This is not an issue in Firefox, Safari and later versions of Internet Explorer. In addition, the following buttons are skipped when tabbing: Previous month, Previous year, Month increase/decrease, and Year increase/decrease. An alternative to selecting the date with the keyboard is to manually enter the date with the number keys.
After completing fields in the Create New Search Wizard, the keyboard focus changes to the browser URL and you must tab through the banner and navigation before you can edit the current page.
When viewing a document with annotations while running JAWS, you can tab to an annotation, but no description is read by JAWS.
When using the keyboard to select a date from a calendar control, the selected date is not retained. The workaround is to enter the date into the date field using the number keys on the keyboard.
When you first open a document in Advanced Viewer mode using screen reader mode, JAWS incorrectly adds the phrase Insert F1 Help Text after each button name.
When using Microsoft Internet Explorer and I use a screen reader is enabled on the user preferences page, some panels in the Navigation pane may not display, although the text of the panel title is still read. This is caused when the panel name is too long. Depending on the user interface language, this could happen to one or multiple panels. If you expand the panel above the hidden panel, the hidden panel is then displayed.
Documentation Errata: Currently, there are no documentation issues to note.