1. Log in to Content Server as an administrator.
2. Click the Configuration for [Instance] link in the Content Server Administration tray.
3. In the Features And Components section, click Enabled Component Details.
4. From the details shown, verify that the following components are enabled. If a component is not listed, enable it.

   • CheckoutAndOpenInNative

   • ConfigMigrationUtility

   • CoreWebdav

   • YahooUserInterfaceLibrary

1. Log back in to Content Server as an administrator.
2. In Content Server, open the Config Migration Admin folder in the Content Server Administration tray, and click the Upload Bundle link.
3. On the Upload Configuration Bundle page, click Browse.
4. Select the SiebelAdapterCMUBundle.zip file, located in the following folder:

   ECM_ORACLE_HOME/ucm/Distribution/SiebelEcmIntegration

5. Select the Force overwrite field.
6. Click Upload.
7. On the Configuration Bundles page, select the SiebelIntegrationCmuBundle link. On the Configuration Migration Administration page, select the Overwrites Duplicates field. Select Preview from the item's Actions menu.
8. On the Import Preview page, select Import from the Actions field. (Note that you can ignore messages about skipped dependencies.)
9. Restart Content Server.

1. Log in to Content Server as an administrator.
2. Select Admin Server from the Administration menu. The Component Manager page is displayed.
3. Scroll to the Integration components section.
4. Select the SiebelEcmIntegration and SiebelIntegrationSearchDisplay components to enable them.
5. Optionally, select the SiebelSearchExtension and SiebelSearchExtraParams components. Note that you can disable these components at any time by deselecting them on this page.
6. Click Update.
7. Restart Content Server.

   Note:

   For information about restarting methods, see Starting and Stopping Content Server and Inbound Refinery in Administering Oracle WebCenter Content.

1. From the Administration tray in Content Server, click the Admin Server link.
2. In the side pane, click the General Configuration link.
3. Scroll to the Additional Configuration Variables section, and edit the following entries. (These entries were automatically created when you imported the Configuration Migration Utility Bundle.)

   Note:

   The default value for all true/false entries is TRUE, except for the AdapterAppDisplayLinks variable, whose default value is FALSE.

   Table 2-2 Configuration Variable Entries

   Entry	Description
   SiebelCssPath=http://siebel_host:port/main.css	Use to identify the Cascading Style Sheet (CSS) file to use for the IFrame. This entry links the Siebel CSS file with the adapter so that changes to the Siebel CSS also affect the IFrame. This is optional but recommended; if not specified, the IFrame uses the default CSS file. Example Siebel 7.8 URL: http://siebelserver:port/files/main.css Example Siebel 8.x URLs: http://siebelserver:port/callcenter_enu/files/main.css http://siebelserver:port/sales_enu/files/main.css
   ODDCURLPath	Use to enable document attachment scanning and importing using Oracle WebCenter Enterprise Capture or Oracle Distributed Document Capture. For configuration instructions, see Configuring Oracle WebCenter Enterprise Capture and Configuring Oracle Distributed Document Capture. For Oracle WebCenter Enterprise Capture (12c) integration This entry specifies the web address to Oracle WebCenter Enterprise Capture: Format: ODDCURLPath=oraclecapture://CaptureWorkspace=CaptureWorkspace&CaptureDriver=CAPTURE_IMPORT_DRIVER&CaptureSource=Import Source Example: ODDCURLPath=oraclecapture://CaptureWorkspace=SIEBEL&CaptureDriver=CAPTURE_IMPORT_DRIVER&CaptureSource=Import%20Source For Oracle WebCenter Enterprise Capture (11g) integration This entry specifies the web address to Oracle WebCenter Enterprise Capture: Format: ODDCURLPath=http://capture_host:port/dc-client Example: ODDCURLPath=http://capture1:16400/dc-client For Oracle Distributed Document Capture (10g) integration This entry specifies the web address to Oracle Distributed Document Capture: Format: ODDCURLPath=http://ODDC_host/ODDC_webcapture_address Example: ODDCURLPath=http://xyz/webcapture.asp
   ODDCScanAction=1 ODDCScanAction=2	Use to configure document attachment scanning and importing using Oracle WebCenter Enterprise Capture (as described in Configuring Oracle WebCenter Enterprise Capture) or Oracle Distributed Document Capture (as described in Configuring Oracle Distributed Document Capture). In this entry, specify the scan action to be performed, where 1 = Scan and 2 = Import.
   AdapterAppFrameLessWindowRequired=true	Specify if standard browser menu options are hidden in browser windows that open from the IFrame display (true) or displayed (false).
   AdapterAppCheckinNewBtnVisible=true	Specifies if the New button is displayed in the IFrame.
   AdapterAppDetachBtnVisible=true	Specifies if the Detach button is displayed in the IFrame.
   AdapterAppAdvSrchBtnVisible=true	Specifies if the Search button is displayed in the IFrame.
   AdapterAppConfigureBtnVisible=true	Specifies if the Configure button is displayed in the IFrame.
   AdapterAppScanBtnVisible=true	Specifies if the Scan button is displayed in the IFrame.
   AdapterAppRefreshBtnVisible=true	Specifies if the Refresh button is displayed in the IFrame.
   AdapterAppAdvSrchUCMUIVisible=true	Specifies if full Content Server user interface and search access is available when users click the Advanced Search button in the IFrame.
   AdapterAppDisplayLinks=false	If needed, use this variable to replace icons in the IFrame with links, by changing the variable's value to true.
   extraSiebelDocParams=parameter,parameter,parameter,...	Optionally specify additional parameters to be passed to the New button. See Passing Extra Metadata Parameters From Siebel to Content Server. Example entry: extraSiebelDocParams=dDocAccount,xsiebelOrder
   extraSiebelScanParams=parameter,parameter,parameter,...	Optionally specify additional parameters to be passed to the Scan button. See Passing Extra Metadata Parameters From Siebel to Content Server. Example entry: extraSiebelScanParams=dDocAccount

   Note:

   You can override the entries that determine if the New, Detach, Search, Configure, Scan, and Refresh buttons are displayed by specifying an alternate display mode, as described in Dynamically Change the Display Mode.

   Note:

   You can specify the default columns to be displayed to users in the IFrame. (When the user clicks Reset in the Configure Fields for Display screen, default columns are listed in the Main Information section of the screen.)

   Open the config.cfg file and set the value of the SiebelDefaultDisplayColumns configuration variable as a comma-delimited list containing the default fields.

   The additional column defaults are title, author, size, and date. To override these additional columns, populate this variable with comma-delimited Content Server metadata field names. For example, the list might include:

   dDocTitle,dDocType,dDocAuthor,dInDate

   Note:

   To avoid an issue with the Siebel Adapter for Content Server, in which the Content Server login page displays in the Siebel page instead of the IFrame, add the following entry to the Content Server config.cfg file:

   AllowContentServerInAnyDomains=1

   Be aware that setting the AllowContentServerInAnyDomains variable to 1 allows Content Server pages to be opened in IFrames, which could pose a potential security issue.

4. Restart Content Server.

1. Log in to Siebel Tools with User ID: SADMIN and Connect to: Local.

   Note:

   Ensure that you are modifying the correct .SRF repository file.

2. In the Object Explorer of Siebel Tools, select Project.
3. From the Query menu, select New Query (Ctrl+Q).
4. Submit the first query by entering the following text into the Name field and pressing Enter:

   Account OR Account ?SSE? OR Asset Management OR Contact OR Contact ?SSE? OR ERM Unified Help Desk OR FINS Call Reports OR FINS Call Reports ?SSE? OR FINS INS Claims OR FINS INS Claims Appraisals/Bills/Attachments OR Oppty OR Oppty ?SSE? OR Order Entry OR Quote OR Quote ?UI?

   Note:

   If you choose to copy and paste the text string, be sure to first paste the copied text into an ascii editor (such as Notepad) and remove any carriage returns before pasting into the Name field.

5. Select the Locked field for all objects.
6. Start another query by selecting New Query from the Query menu (Ctrl+Q). Enter the following text into the Name field and press Enter:

   Service OR Service ?SSV? OR VERT CUT Common OR PS Project Management OR PS Project Management ?SSE? OR Activity OR Activity ?SSE? OR PUB Case OR PUB Evidence OR PUB HLS Incident OR PUB HLS Physical Terrorism OR PUB Lead OR FINS Call Reports2

7. Select the Locked field for all objects.

   Note:

   Siebel Object Locking provides information about which objects are locked. This can be useful if you encounter issues when locking Siebel projects.

1. From the Tools menu, choose Import From Archive.
2. In the Select Archive To Import dialog box, select the appropriate .sif archive file, and click Import. Available SIF files include:

   • Siebel_SEA_7.x_UCM_Attachments_YYYYMMDD.sif

   • Siebel_SIA_8.x_UCM_Attachments_YYYYMMDD.sif

   • Siebel_SIA_7.x_UCM_Attachments_YYYYMMDD.sif

   • Siebel_SEA_8.x_UCM_Attachments_YYYYMMDD.sif

3. The SIF file's contents are displayed in the Import Wizard - Preview screen. Ensure that the Merge option (middle option) from the Conflict Resolution options is selected, and click Next. (This option merges the SIF file changes to existing Siebel Objects.)
4. The wizard displays any conflicting objects found. Click Next.
5. A dialog box lists the changes to be made to the repository, and prompts you to proceed. Click Yes.
6. A summary is displayed. Click Finish.

1. Select Options from the View menu.
2. In the Development Tools Options screen, select the Scripting tab.
3. In the Browser script compilation folder field, enter a path as follows:

   Client Install Folder/PUBLIC/ENU

   For example, on Windows Drive_letter:\Siebel_install_folder_path\client\PUBLIC\enu

4. Select Project in the Object Explorer, locate the Manage Attachments (UCM) project and lock it.
5. From the Tools menu, choose Compile Projects.

   Figure 2-1 Object Compiler

   
   Description of "Figure 2-1 Object Compiler"
6. In the Object Compiler screen, select Locked projects.
7. Verify that the correct repository is selected in the Siebel repository file field. This repository file must exist in the Web Client installation folder.
8. Click Compile. (Note that compiling may take a while.)

1. Launch the Web client, logging in with the User ID: SADMIN.
2. Choose Sitemap from the Navigate menu. The site map of the Siebel Web Client Application is displayed.
3. From the list of screens, click the Administration- Integration link, then the Symbolic URL Administration link.
4. From the Host Administration field, select Symbolic URL Administration.
5. Click New to create a new record.
6. Complete the following fields for the URL. With the new URL selected in the Symbolic URL table, a Symbolic URL Arguments pane becomes displayed.

   Field	Value to Enter
   Name	UcmServUrl
   URL	http://Content_Server_URL/_p/cc-embedded (example: http://content-server-name.domain:port-number/cs/idcplg/_p/cc-embedded)
   Fixup Name	InsideApplet
   SSO Disposition	IFrame

   Note:

   In certain demonstration environments, entering UcmServUrl in the Name field results in an error. If this occurs, enter the following:

   UcmServUrl_Demo

7. In the Symbolic URL Arguments pane, create new argument records by entering the following values. To create a new record, click New, select the new record, and specify its values. Be sure to navigate away from the last record entered to ensure it is saved to the database.

   An example of a Symbolic URL follows. (Note that this example URL is separated onto multiple lines for display purposes only, with argument names in bold for clarity.)

   http://content-server-name.domain:port-number/cs/idcplg/_p/cc-embedded?
   IdcService=GET_SEARCH_RESULTS_FORCELOGIN&
   siebelEntityField=xsiebelContact&
   siebelEntityValue=1LS-AF98&
   QueryText=xsiebelContact+%3cmatches%3e+%601LS-AF98%60&
   SearchQueryFormat=Universal&
   ResultTemplate=SIEBEL_SEARCH&
   coreContentOnly=1&
   SortField=dInDate&
   SortOrder=Desc&
   SearchEngineName=DATABASE.METADATA&
   ResultCount=20

   Name	Required Argument	Argument Type	Argument Value	Append as Argument	Substitute in Text	Sequence #
   IdcService	N	Constant	GET_SEARCH_RESULTS_FORCELOGIN	Y	N	1
   siebelEntityField	N	Field	SiebelEntityName	Y	N	2
   siebelEntityValue	N	Field	Id	Y	N	3
   QueryText	N	Field	QueryText	Y	N	4
   SearchQueryFormat	N	Constant	Universal	Y	N	5
   ResultTemplate	N	Constant	SIEBEL_SEARCH	Y	N	6
   coreContentOnly	N	Constant	1	Y	N	7
   SortField	N	Constant	dInDate	Y	N	8
   SortOrder	N	Constant	Desc	Y	N	9
   SearchEngineName	N	Constant	DATABASE.METADATA	Y	N	10
   ResultCount	N	Constant	6 (See Configure the IFrame Height).	Y	N	11
   IFrameSRC	N	Command	IFrame Height=280 Width=100% (See Configure the IFrame Height).	Y	N	12

   Figure 2-2 Symbolic URL Arguments Pane

   
   Description of "Figure 2-2 Symbolic URL Arguments Pane"

1. Log out of the Web client, then log in again to view the Managed Attachments IFrame embedded in the Attachments tab.

   Tip:

   To access Views, choose Sitemap from the Navigate menu in the Web client. This displays opportunities, orders, and other options with their child Views and attachment Views.

2. Test the changes locally. After testing is successful, ensure that the objects, including generated browser scripts, are synchronized with the Siebel server.

1. A Scan button is added to the Managed Attachments IFrame. The user clicks the button, and selects a Document Classification and Security Group, which are assigned to an Oracle WebCenter Enterprise Capture client profile. For example, the user might select a classification of Identity Documents to scan a photocopy of a driver's license or passport. (An Oracle WebCenter Enterprise Capture client profile specifies scanning, importing, and indexing settings.)
2. When the user clicks Scan Document, Oracle WebCenter Enterprise Capture's client launches in a new window and passes in parameters such as the client profile to be used and the Siebel entity value for later attachment.
3. Within the Oracle WebCenter Enterprise Capture client, the user reviews the document, makes changes as needed, completes any metadata fields configured in the client profile, and then releases the batch. Releasing the batch commits the new document to the Content Server using a Capture commit profile configured to commit to WebCenter Content. (A Capture commit profile configured for Content commit specifies connection information and field mappings between WebCenter Enterprise Capture and Content Server metadata fields.)
4. Upon successful batch release, the user returns to the Managed Attachments IFrame and refreshes the display to view the newly scanned document or imported file.

1. Refresh the Managed Attachments IFrame results page. You should see a Scan button beside the New button.
2. Click Scan. On the Scan Document page, select a document classification and security group, then click Scan Document. The Oracle WebCenter Enterprise Capture client launches.

   Notice that the URL reflects the settings you specified to run the client. It also passes the client profile, scan action (1 = Scan and 2 = Import), and metadata data consisting of the Siebel entity and its value (for example, xsiebelContact=1LS-AF98).

3. Within the Oracle WebCenter Enterprise Capture client, review, index, and release the document's batch.
4. Return to the Managed Attachments IFrame and click Refresh. The newly scanned document or imported scanned file should be displayed in the list. (It may take a few minutes to be displayed.)

1. A Scan button is added to the Managed Attachments IFrame. The user clicks the button, and selects a document classification, which is assigned to an Oracle Distributed Document Capture scan profile. For example, the user might select a classification of Identity Documents to scan a photocopy of a driver's license or passport. (An Oracle Distributed Document Capture scan profile specifies scanning, importing, and indexing settings.)
2. When the user clicks Scan Document, Oracle Distributed Document Capture's remote client launches in a new window, automatically authenticates and logs in the user, and passes in parameters such as the scan profile to be used and the Siebel entity value for later attachment.
3. Within the Oracle Distributed Document Capture client, the user reviews the document, makes changes as needed, completes any index fields configured in the scan profile, then sends the batch. Sending the batch commits the new document to Content Server using an Oracle 11g UCM commit profile specified for the scan profile. (A Capture UCM commit profile specifies connection information and field mappings between Capture and Content Server metadata fields.)
4. Upon successful sending, the user returns to the Managed Attachments IFrame and refreshes the display to view the newly scanned document or imported scanned image file.

1. Refresh the Managed Attachments IFrame results page. You should see a Scan button beside the New button.
2. Click Scan. In the Scan Document page, select a document classification and click Scan Document. The Oracle Distributed Document Capture client launches.

   Notice that the URL reflects the settings you specified to run the client. It also passes the scan profile, scan action (1 = Scan and 2 = Import), and index data consisting of the Siebel entity and its value (for example, xsiebelContact=1LS-AF98).

3. Within the Oracle Distributed Document Capture client, review, index, and send the document's batch.
4. Return to the Managed Attachments IFrame and click Refresh page. The newly scanned document or imported scanned image file should be displayed in the list. (It may take a few minutes to be displayed.)

1. Ensure that the SiebelSearchExtraParams component is enabled. See Enable the Siebel Adapter Content Server Components.
2. Set the extraSiebelDocParams and extraSiebelScanParams configuration variables.

   Specify the Content Server field or fields to populate. Define extraSiebelDocParams to pass values using the New button, and extraSiebelScanParams to pass values using the Scan button. For information about configuration variables, see Set the Configuration Variables.

   For example, to populate the Content Server Account metadata field for new and scanned documents, specify the following:

   • extraSiebelDocParams=dDocAccount

   • extraSiebelScanParams=dDocAccount

   Note:

   If specifying multiple Content Server fields for a variable, separate them with a comma. For example:

   extraSiebelDocParams=dDocAccount,xsiebelOrder

   extraSiebelScanParams=dDocAccount,dDocType

3. Update profiles as needed to accommodate the passed values (without the extra prefix).

   • If passing values using the New button, update the Content Server content profile to display the metadata field you specified, if needed.

   • If passing values using the Scan button, update the client profile to display the index field, if desired. (The index field must exist for the workspace being used.) In the commit profile, map the index field to the appropriate Content Server metadata field.

1. Add a Siebel field to hold the value to pass. For example, you might add a field called UcmAccount to the Contact business component, as shown in the following figure.

   Figure 2-12 Contact Business Component

   
   Description of "Figure 2-12 Contact Business Component"
2. On the symbolic URL, add an argument for the field you created in step 1, including the extra prefix (extradDocAccount in the following example, which is the Content Server metadata variable name of dDocAccount with the extra prefix).

   Figure 2-13 Symbolic URL Arguments Pane

   
   Description of "Figure 2-13 Symbolic URL Arguments Pane"
3. Compile the business component.

1. Using Component Manager, create a custom component. Create an include resource that overrides the following resource includes:

   • js_custom_siebel_functions

   • custom_configurable_btn_bar

   • js_custom_configurable_btn_bar

2. After applying these resource includes, enable the component in Content Server.

<@dynamichtml js_custom_siebel_functions@>
    <$include super.js_custom_siebel_functions$>
   
    <script type="text/javascript">
    //namespace definition
    YAHOO.namespace("YAHOO.oracle.ucm.adapter.extension");
   
       /**
         * Function for custom functionality added to the existing adapter.
         *
         */
        YAHOO.oracle.ucm.adapter.extension.customFunctionListener=function(){
            //custom code goes in here
            alert("You have your custom functionality running");
        };
        </script>
<@end@>

<@dynamichtml custom_configurable_btn_bar@>
       <$include super.custom_configurable_btn_bar$>
        <a id="customBtn"
href="http://hostname/pages/editpage.action#" >Custom Button</a>&nbsp;
<@end@>

<@dynamichtml js_custom_configurable_btn_bar@>
    <$include super.js_custom_configurable_btn_bar$>
   
YAHOO.util.Event.addListener("customBtn","click",YAHOO.oracle.ucm.adapter.extension.customFunctionListener);
<@end@>

As an option, you can configure a special display mode that dynamically overrides the default display configuration settings, hiding one or more buttons and disabling one or more icons. For example, when users are viewing a specific Siebel record type, such as Orders, you might hide the New and Scan buttons to prevent them from adding new attachments to orders, and disable the Edit icon so they can view but not edit order related attachments.

Here's how it works:

• By default, no dynamic display mode is configured. Under normal default settings, buttons in the IFrame are displayed according to their configuration variable settings (see Set the Configuration Variables). Columns are displayed according to the user's field configuration settings, and if columns are displayed, their icons are always functional.

• A parameter called SiebelDisplayMode sets the alternate display mode's combination of disabled buttons and icons. When set, this parameter overrides the other configuration variables (for example, AdapterAppCheckinBtn=true). The SiebelDisplayMode parameter is an integer that you calculate. During display, the integer is translated to dynamically determine the button and icon status.

• You activate the alternate dynamic display mode by configuring a secondary symbolic URL for the IFrame and specifying the SiebelDisplayMode parameter within it. Then, for business objects that require the alternate display mode, you change the symbolic URL to point to the secondary symbolic URL.

1. Log in to Content Server as an administrator.
2. Select Admin Server from the Administration menu.

   The Component Manager page is displayed.

3. Scroll to the Integration components section.
4. Deselect the Siebel adapter components to disable them.

   • SiebelEcmIntegration

   • SiebelIntegrationSearchDisplay

   • SiebelSearchExtension

   • SiebelSearchExtraParams

   • SiebelFilter

   (For details about these components, see Enable the Siebel Adapter Content Server Components)

5. Click Update.
6. Restart Content Server.

   Note:

   For information about restarting methods, see Starting and Stopping Content Server and Inbound Refinery in Administering Oracle WebCenter Content.