Missing Documents in Imaging while commiting from ODC/OFR

ISSUE:

Documents which were uploaded into WebCenter Content: Imaging and used to create BPEL instances are no longer seen in WebCenter Content: Imaging or WebCenter Content: interfaces.  The following error is on the WebCenter Content logs


Failed to find indexable webviewable for content item


CAUSE:

1)FIRST CHECK ucm logs ,

if logs contains

[FMWGEN][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 83) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. java.sql.SQLTransactionRollbackException: [FMWGEN][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 83) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction

THEN,

SOLUTION:


The SQL Server database admin must execute these statements. Once these complete, restart the WebCenter Content managed server.

ALTER DATABASE <dbname> SET ALLOW_SNAPSHOT_ISOLATION ON
ALTER DATABASE <dbname> SET READ_COMMITTED_SNAPSHOT ON



Example statements, where the database name is DEV_OCS:

ALTER DATABASE DEV_OCS SET ALLOW_SNAPSHOT_ISOLATION ON
ALTER DATABASE DEV_OCS SET READ_COMMITTED_SNAPSHOT ON


If UCM LOGS does not contains above error,then perform below steps:




2)This issue is caused because the WebCenter Content server's DefaultFileStore is setup to create the web viewable images along with the vault, which causes a delay in the release of the documents. This delay means that the BPEL process is trying to update the document's index before it was released, causing the document to be in a failed release state because the revision was in an incorrect state.

Disabling the Repository Weblayout Directory

Content Server traditionally uses a weblayout directory on a file system to store content in a format for viewing in a web browser, even though the main storage volume may be set up in a database. This can allow for faster retrieval of content when content server is being used to manage a web site, or can be used to store a secondary file used to describe the primary content item, but it doesn't have much use in an I/PM solution. Retaining a web layout directory for an exclusively I/PM solution would copy files to a web layout directory that would never get used, taking up unnecessary storage space. It is recommended that any file store provider configured for use as an I/PM volume should have the weblayout functionality disabled.

SOLUTION:

To resolve this issue, and to disable the use of the weblayout directory, perform the following steps:

Actions on the WebCenter Content system:

1. Log in to WebCenter Content as the WebCenter Content Administrator (http://servername:16200/cs).
2. Expand the Administration pane and select Providers.
3. In the Providers page, find DefaultFileStore.  Select Info under Action.
4. In the DefaultFileStore page, select Edit.
5. In the Edit page, select Add New Rule from the drop down menu, and then Edit Rule (WebCenter Content Support suggests creating a new rule over editing the default rule).
6. In the new window, type in a name for the new rule and check the box for 'Is Webless File Store', and then OK.
7. Hit OK again and then Update.
8. This will bring you back to the Provider page. Notice that for the DefaultFileStore under Connection State it will say 'Requires a restart'.
9. Restart the WebCenter Content Managed server.

Actions on WebCenter Content: Imaging System:

1. Log into WebCenter Content: Imaging (http://servername:16000/imaging).
2. Select Manage Applications on the left pane.
3. Select an application, then Modify.
4. Go to the Storage Policy section, and then change the Document Storage and Supporting Content Storage to the new rule that was created (note the name will be displayed File rule name).
5. Submit the changes.

You also need to resubmit the images on the Content Sever so they can be release and view able in IPM. 

How to resubmit the images in the Content sever:

1. Log into the Content server as an Administrator.
2. In the Administration Menu, select Admin Applets and then Repository Manager.
3. On the Repository Manager page, select the Define Filter button.
4. Within the filter, check the box next to "Revision Status" to make it active, and then in the drop down menu, select GenWWW, then OK.
5. Back on the Repository Manager page, check the box for Use Filter and uncheck the box for Release Date.  
6. This will return a list of images that are not released in Content Server.  Select them and right click and choose Resubmit.

Once you have created the new storage rule, you can move any images in the old rule to the new rule by using the following steps.

How to use Archiver to move content from one storage rule to another:

1. Log into WebCenter Content as the WebCenter Content Administrator (http://servername:16200/cs).
2. Go to Administration -- Admin Applets and open Archiver.
3. Select Edit -- Add.
4. Enter an Archive name.
5. Select the Export Data tab.
6. In the Export Query pane, click the Edit button.
7. In the Field drop down menu, select Storage Rule.
8. In the Value field, select the FSP rule to move content.
9. Click the Add button.
10. Click the OK button.
11. Optionally, click the Preview tab to verify that there is content to be exported.
12. Select Actions -- Export.
13. When the export is complete, select the Import Maps tab.
14. In the Value Maps pane, click the Edit button.
15. Check the All box.
16. In the Field drop down menu, select Storage Rule.
17. In the Output Value field, enter the FSP rule to move content to. 
18. Click the Add button.
19. Click the OK button.
20. Select Actions -- Import.