DesktopTag Component Operation Using the DesktopTag Component

13-2 Oracle Fusion Middleware Developers Guide for Oracle Universal Content Management

13.2 System Requirements

The DesktopTag component is included with Oracle Content Server 11gR1. It must be enabled on Oracle Content Server because it is not enabled by default. The DesktopTag component requires that the OracleCleanContent component is enabled as well. The OracleCleanContent component is enabled with typical Oracle Content Server installations. You can enable components using Component Manager, which is launched from the Content Admin Server page. For more information about enabling components, see Enabling and Disabling a Component in the Oracle Fusion Middleware System Administrators Guide for Oracle Content Server. DesktopTag can add custom properties to the following Microsoft Office applications: ■ Microsoft Word 2002 XP and later versions ■ Microsoft Excel 2002 XP and later versions ■ Microsoft PowerPoint 2002 XP and later versions

13.3 DesktopTag Component Operation

The DesktopTag component modifies the check-out file get and check-in operations for Oracle Content Server.

13.3.1 File Get Operation

The DesktopTag component installs a service handler override for the createFileName method, which should be called for all file get operations that go through the server native URL requests do not call this method. If the file type is supported by the configuration, a set of custom properties are added to the file. These custom properties are used in various ways by the DesktopIntegrationSuite component and are made available to other components.

13.3.2 File Check-In Operation

The DesktopTag component installs an extension filter that hooks the validateCheckinData filter, which is part of the DesktopIntegrationSuite component. It removes the custom properties that were added by a file get operation before the data is checked in to the server. The result set returned for this operation includes the properties that would be added to the Microsoft Office file in a subsequent file get operation. This is provided to allow the client to modify the file rather than having to get a new copy. This method calls the desktopTagGetFilter extension filter, just like the file get operation.

13.4 Using the DesktopTag Component

The functionality offered by the DesktopTag component is provided entirely in the background. There is no direct user interaction. It is typically used for content tracking purposes, although the information can be exposed to users. Figure 13–1 shows an example of a Word 2003 document without custom properties added by DesktopTag, and Figure 13–2 shows a number of custom properties added. Customizing DesktopTag 13-3 The properties that are added to the Microsoft Office files depend on the settings in the DesktopTag configuration file see Section 13.5, Configuring the DesktopTag Component . In Figure 13–2 , the content ID dDocName, user name dUser, and unique content item identifier dID are added to the Word document. The DISProperties custom property is always added. It lists all custom properties added by DesktopTag as specified in the configuration file, and is used to ensure that the correct custom properties are deleted when a file is checked into Oracle Content Server again. Figure 13–1 Word 2003 Document Without Custom Properties Added by DesktopTag 13-4 Oracle Fusion Middleware Developers Guide for Oracle Universal Content Management Figure 13–2 Word 2003 Document with Custom Properties Added by DesktopTag

13.4.1 Viewing Custom Properties

Users can view the custom properties of a Microsoft Office file as follows: ■ Microsoft Office XP 2002 and 2003: Choose File, then Properties, and then click the Custom tab. ■ Microsoft Office 2007: Click the Office button in the application, then choose Prepare , then Properties, then Document Properties, then Advanced Properties, and then click the Custom tab. ■ Microsoft Office 2010: Open the File panel, then click Info, then Properties, then Advanced Properties , and then click the Custom tab. Customizing DesktopTag 13-5 Figure 13–3 Custom Document Properties Microsoft Word 2003

13.4.2 Checking in Documents from Outside Oracle Content Server

These custom document properties allow Desktop Integration Suite to keep track of where a managed file resides in an Oracle Content Server instance. This, in turn, enables users to check a Microsoft Office document back in to Oracle Content Server even from outside a content management integration context. This feature can be useful in a number of situations; for example: ■ A user receives a managed Word document from someone else, as an attachment to an e-mail. ■ A user copies a managed Word document from a server in the integration hierarchy to a folder outside that hierarchy. In either case, users can open the file in Microsoft Word, make changes, and then check the file back in to the server using the Oracle UCM menu or ribbon in Word. Desktop Integration Suite checks the custom properties embedded in the Word document to find out where to upload the file to. 13-6 Oracle Fusion Middleware Developers Guide for Oracle Universal Content Management

13.5 Configuring the DesktopTag Component