This chapter describes issues associated with Oracle Imaging and Process Management. It includes the following topics:
This section describes general issues. It includes the following topics:
When using Oracle Single Sign On and an I/PM session expires, WebLogic Server will return an internal server error. Refreshing the page returns to the I/PM 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 but not administrative 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 I/PM server. This means that any date metadata generated by the Oracle I/PM system, such as document creation date, modify date, or other audit events, is governed by the time zone of the I/PM 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 I/PM 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 I/PM 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 I/PM is integrated with WebCenter, use the Viewer on the Upload page to redact documents prior to uploading to I/PM.
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 Oracle I/PM 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 I/PM. 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, Oracle I/PM 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 Oracle Content Server connection with available SDATA fields. If no additional Content Server connection is defined, you can install and configure an additional Oracle Content Server and create a new connection to it in Oracle I/PM. 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 Oracle I/PM with Oracle Universal Records Management. If a document is uploaded into an Oracle I/PM 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 Oracle Content Server repository to see records, they will not be able to see any of the uploaded documents in an I/PM search. Rights to retention categories are determined in Oracle URM. If integrating Oracle I/PM and Oracle URM, ensure that all users needing rights to view records have the correct security, that Retention Categories are set correctly in all Oracle I/PM applications, and that users understand what can happen if the Records-only Retention Categories are used.
If leveraging AXF functionality with Oracle I/PM, 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 IPM_server<number>. The Setting for IPM_server<number> page is displayed for the selected Oracle I/PM 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 using WLST commands importIPMSearch, importIPMInput, importIPMApplication, the first parameter is the file path to the export file. WebLogic Scripting Tool does not recognize multibyte characters in the file path, and so multibyte characters should not be used in the path.
If an invalid value is set in the DefaultColorSet MBean, or if a user has specified a UI skin in their preferences that has been deprecated when Oracle I/PM is upgraded, then a generic user interface is displayed when the user logs in. The generic interface has a larger font and does not display a logo. Correcting the invalid value of the DefaultColorSet MBean or applying a current skin from the User Preference page corrects the problem.
There is a known issue with the Oracle Outside In Technology libraries that causes a memory error when attempting to display the second page of a Microsoft PowerPoint 2007 .pptx file. If such an error occurs when attempting to view a PowerPoint file, download the original document to view the file. Note that if the file has been redacted and you do not have rights to view content under the redactions, you will not be able to download the file.
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 Oracle I/PM 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.
Note that work managers used to manage JMS threads are only compatible with WebLogic Server Java Message Service (WLS JMS). They do not work with Advanced Queueing JMS (AQ JMS). Section 9.4.3, "Changing Oracle WebLogic Server Work Manager Settings" and section 10.2.4 "Changing WebLogic Server Work Manager Settings" of the Oracle Fusion Middleware Adminstrator's Guide For Imaging and Process Management are not applicable if using AQ JMS.
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.
Two additional MBean configuration settings have been added that can be set to clean up the image directory used for Input Agent filings.
|CleanupExpireDays||Sets the number of days after which images are deleted. Acceptable values are 0 through 30. The default is 0, which disables purging of the images directory. Modification requires a server restart.|
|CleanupFileExclusionList||String value specifies a list of file names excluded from being purged. This allows files to be reused in filings like annotations, without being deleted after filing.
Specified file names must be exact, without wildcards. Entered values are concatenated into a single semicolon delimited string that must not exceed 250 characters, including delimiters. Modification requires a server restart.
These configuration settings provide the ability to manage the images directory used for Input Agent filings by deleting images after they have been successfully ingested into the repository. If enabled, any successfully processed file, including annotation and supporting content files, are placed in a batch folder in the input directory's holding folder. The images remain there until the number of days specified in the CleanupExpireDays setting elapses. After that point the files and the batch folder are deleted. Specify any files that should not be deleted in the CleanupFileExclusionList setting with exact file names.
An additional MBean configuration setting has been added that returns the length of time an I/PM server has been running.
|Uptime||Returns the duration the I/PM server has been running since the last startup. The value is returned in the format: HH:MM:SS. This is a read-only MBean.|
When using Oracle Access Manager (OAM) 11g WebGate 11g single sign-on (SSO), you must set the WebGate 11g Agent user-defined parameter, filterOAMAuthnCookie=false. Failure to do so causes an error when using the viewer in advanced mode. For more information on setting the Agent user-defined parameters using the OAM console or when registering partners remotely, refer to the Oracle Fusion Middleware Administrator's Guide for Oracle Access Manager with Oracle Security Token Service.
When using the viewer in advanced mode for the first time, Oracle I/PM downloads and caches files from Oracle Outside In Technology to the client system. After upgrading to Oracle I/PM 184.108.40.206.0 from earlier versions, ensure the updated files are downloaded to each client computer by deleting the oracle directory in the system temporary directory. This allows the viewer to download the correct files the first time it is used in advanced mode. The location of the temporary directory is specific to each system depending on the operating system used.
The ability to export search results to a Microsoft Excel format has been temporarily disabled in this release. The option to export a search result to Excel will be made available in a subsequent patch set.
When previewing and testing a newly created search, the following Search Results Toolbar and menu commands have been temporarily disabled in this release:
Note that these commands are only disabled on the Preview and Test page when creating or modifying a search. The commands are functional on a search results page after the search is created and the search is run.
The procedure for selecting a page to go to in a multi-page document has changed slightly from previous releases. The desired page is selected from a menu in the viewer toolbar. Total number of pages available in a document is listed next to the page selection control.
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 Oracle I/PM viewer. When viewing a document, it is recommended that all navigation within the viewer be done using the navigation controls in the viewer toolbar.
This section describes browser compatibility issues. It includes the following topics:
When using the keyboard tab button to select functions on the Toolbar of a Search results page, the expected behavior is to focus on the first option (View) and then move to the next (Email). Instead, the tab button causes focus to move through the hidden View submenus before moving the focus to Email. Similarly, when using the tab button to select menus on the Viewer, the expected behavior is to move focus from the first Viewer menu (File) to the next (View). Instead, the tab button causes the focus to move through the hidden submenus of each top-level menu before moving focus to the next menu.
Downloading either the original or TIFF versions of a document from the viewer is not supported when using Safari. To download a document in its original native format or as a TIFF when using Safari you must access the document from a search result page.
When using the keyboard tab button to select items on the Viewer, none of the panels (History, Sticky Notes, or Properties) can be selected. This is a known issue with Safari. If you need to use the keyboard to select a panel in the Viewer, you must use either Microsoft Internet Explorer or Mozilla Firefox to view documents.
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:
There is a problem with how Firefox 3.6 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 3.6. 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.
There is a problem with how Chrome 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 Chrome. 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.
Downloading either the original or TIFF versions of a document from the viewer is not supported when using Chrome. To download a document in its original native format or as a TIFF when using Chrome you must access the document from a search result page.
This section describes accessibility issues. It includes the following topics:
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 I/PM 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, Internet Explorer 8 or Safari 4. 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 viewing a document using screen reader mode and Advanced Viewer mode, JAWS reaches the Close Tab options in the Viewer and reads a collapse pane link that is not visible after More options. If you click when JAWS reads link, a 403 Forbidden Page error is returned.
When searching using Internet Explorer, expanding and collapsing the instructions tree using the keyboard incorrectly changes the focus to the Skip to Content link instead of the next row.
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.
When a document contains multiple sticky notes, the following keys are used to navigate and control the sticky notes in the sticky note panel:
|Up Arrow||Moves focus to the previous sticky note.|
|Down Arrow||Moves focus to the next sticky note|
|Right Arrow||Expands a sticky note|
|Left Arrow||Collapses a sticky note|
There is a known issue with keyboard navigation in the sticky note panel. When a sticky note is expanded, the up and down arrow keys do not change focus to a different note. The left arrow key must first collapse the expanded sticky note, then the up and down arrow keys can be used to navigate from one note to another.
The following keys are used to control search tabs in the Oracle I/PM content areal:
|Shift+F10||Opens a contextual menu when the search tab has focus.|
|Ctl+Alt+F4||Closes the tab that has focus.|
There are known issues with these keyboard commands in the following browsers:
Firefox 3.6: Ctr+Alt+F4 does not close the focused search tab.
Internet Explorer 8: Ctr+Alt+F4 does not close the focused search tab and Shift+F10 causes menus to display for both the search tab contextual menu and the browser file menu. Pressing the Esc key closes the browser file menu and puts focus on the search tab contextual menu.
Safari 4: Shift+F10 does not open a contextual menu.
There is a known issue in all browsers that after checking the Disable UI Animations on the Preferences page, the busy indicator in the top banner continues to spin when performing a task that keeps the system busy.
When using JAWS and viewing a multipage document in the Viewer basic mode on screen resolutions less than 1280 pixels wide, focusing on the toolbar expansion arrows and pressing Enter causes an error. This prevents access to tools necessary to navigate to the document. To workaround this issue, view the multi-page document in the Viewer advanced mode. Alternately, set your screen resolution to 1280 x 1024 pixels if your monitor supports it. The higher resolution setting allows for access to all buttons in the Viewer basic mode except the Go to Next Page, Go to Last Page, and Help buttons. However, the functionality these buttons provide is accessible by other means.
This section lists any know errors in the Oracle I/PM released documentation.
The Oracle® Fusion Middleware Developer's Guide for Oracle Imaging and Process Management incorrectly states that only basic authentication is supported when Oracle I/PM is first installed and configured with no Oracle Web Service Manager security policies applied. In fact, both basic and username token authentication is supported by default.