C Completing Installation of Oracle WebCenter Content Service for Oracle Universal Content Management

If you installed Oracle WebCenter Content Service for Oracle Universal Content Management, perform the following tasks to complete the installation:

• Verifying Installation

• Creating a Content Source

• Creating a Content Crawler

• Creating a Job

• Configuring Security for Document Discovery

• Configuring Security for Document Access

• Troubleshooting

Verifying Installation

Complete the steps on the Content Service for UCM Installation Verification page. This page is located on your Oracle WebCenter Content Service for Oracle Universal Content Management host computer, at http://RemoteServer:port/ptucmcws/web/install/index.html.

Creating a Content Source

Create a content source to define the area of Oracle Universal Content Management from which you want to import content. To create a content source, perform the following steps in the Oracle WebCenter Content Service for UCM folder in the portal's Administrative Object Directory:

1. Log in to the portal as an administrator.

2. Click Administration.

3. Open the Oracle WebCenter Content Service for UCM folder.

4. From the Create Object menu, select Content Source - Remote.

5. In the Choose Web Service dialog box, choose the Oracle WebCenter Content Service for UCM Web service.

6. Configure the content source as described in the online help.

Stay logged in to the portal with the Oracle WebCenter Content Service for UCM folder open for the next procedure.

Creating a Content Crawler

Create a content crawler to import content from the content source. To create a content crawler, perform the following steps in the Oracle WebCenter Content Service for UCM folder of the portal's Administrative Object Directory:

1. From the Create Object menu, select Content Crawler - Remote.

2. In the Choose Content Source dialog box, choose the content source that you created in the previous procedure.

3. On the Main Settings page of the Content Crawler Editor, select Import security with each document. Configure the rest of the content crawler as described in the online help.

Stay logged in to the portal with the Oracle WebCenter Content Service for UCM folder open for the next procedure.

Creating a Job

To import content, you must associate the content crawler with a job and run the job. To create and run a job, perform the following steps in the Oracle WebCenter Content Service for UCM folder of the portal's Administrative Object Directory:

1. From the Create Object menu, select Job.

2. Click Add Operation.

3. Choose the content crawler that you created in the previous procedure.

4. Choose the scheduling values for the job and click Finish.

5. Name the job and click OK.

6. When you are finished creating the job, ensure that the Oracle WebCenter Content Service for UCM folder is associated with an automation service. For assistance, see the online help under Select Utilities, then Automation Service.

Configuring Security for Document Discovery

Portal users discover documents by browsing the Knowledge Directory and using portal search tools. In the portal, you manage document discovery with access control lists (ACLs) that are associated with portal directories.

If you want Oracle Universal Content Management users to be able to browse records for crawled Oracle Universal Content Management records in the portal with a similar level of privilege they experience in the Oracle Universal Content Management environment, you map the configuration for Oracle Universal Content Management user privileges to the portal ACL Read privilege and ensure that their credentials are used for document access.

Note:

You manage document discovery (display a record) as described in the following procedure. You manage document access (open a file) with click-through security, described in Configuring Security for Document Access.

To configure security settings for the Oracle WebCenter Content Service for Oracle Universal Content Management:

1. Deploy an authentication source (for example, LDAP) to manage Oracle Universal Content Management users. For details, refer to Oracle Universal Content Management documentation.

2. Create a remote authentication source in the portal to import the Oracle Universal Content Management users. For details, refer to the portal's online help or the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Interaction.

3. Configure the Global ACL Sync Map to associate the Oracle Universal Content Management domain name with the authentication source:

   1. Log in to the portal as an administrator.

   2. Click Administration.

   3. From the Select Utility menu, select Global ACL Sync Map.

   4. Click Add Mapping and choose the authentication source you created in step 2.

   5. In the Domain Name column, click the edit icon and type the domain name of the Oracle Universal Content Management users, usually the Lotus Domino Server name.

   6. Click Finish.

Stay logged in to the portal for the next procedure.

Configuring Security for Document Access

To enable portal users to open files imported into the portal, you configure click-through security. The following table describes click-through security methods.

Table C-1 Click-Through Security Methods

Click-Through Security Method	Description and Procedure
User Preferences	User Preferences is the default click-through security method for Oracle WebCenter Content Service for Oracle Universal Content Management. The User Preferences method uses stored values for the Oracle Universal Content Management user to enable access to the Oracle Universal Content Management file. To implement the User Preferences method, in the Oracle WebCenter Content Service for Oracle Universal Content Management config.xml file (located by default in C:\Oracle\Middleware\wci\ptucmcws\10.3.3\settings\config), set clickthroughAuthType as follows: <clickthroughAuthType>1</clickthroughAuthType> When users click through to a Oracle Universal Content Management file for the first time, they are prompted for their Oracle Universal Content Management credentials. The portal stores the credentials as user preferences, so the user does not have to enter them again. Users can modify the values of these credentials by clicking My Account, then Oracle WebCenter Content Service for UCM.
Basic Authentication	Basic Authentication is one of two SSO click-through security methods you can implement for Oracle WebCenter Content Service for Oracle Universal Content Management. It uses the authentication information for the user portal session to enable access to the Oracle WebCenter Content Service for Oracle Universal Content Management file. The portal user name must match the Oracle Universal Content Management user name; so the portal and Oracle Universal Content Management users must be synchronized from a common source, such as LDAP. Note: If you deploy this method, users must log in to the portal with both their user name and password. They cannot choose the Remember My Password option To enable Basic Authentication click-through: Disable User Preference click-through in the portal: In the portal's Administrative Object Directory, open the Oracle WebCenter Content Service for UCM folder. Expand the Web Service section and click the Oracle WebCenter Content Service for UCM Web service. On the left, under Edit Object Settings, click Advanced URL Settings. Remove the entry from the User Configuration URL box. On the left, under Edit Object Settings, click Preferences. Delete all User Preferences and click Finish. Stay logged in to the portal with the Oracle WebCenter Content Service for UCM folder open for the next procedure. Enable Basic Authentication in the portal: In the portal PTConfig.xml file, set the CaptureBasicAuthenticationForPortlets parameter to 1. In the Oracle WebCenter Content Service for UCM folder of the portal's Administrative Object Directory, click the Oracle WebCenter Content Service for UCM Web service. On the left, under Edit Object Settings, click Authentication Settings. Select User's Basic Authentication Information. Restart the portal application server. Enable Basic Authentication click-through on the Oracle WebCenter Content Service for Oracle Universal Content Management host computer: In the Oracle WebCenter Content Service for Oracle Universal Content Management config.xml file (located by default in C:\Oracle\Middleware\wci\ptucmcws\10.3.3\settings\config), set clickthroughAuthType as follows: <clickthroughAuthType>2</clickthroughAuthType>
Trusted Authentication	Trusted Authentication is one of two SSO click-through security methods you can implement for Oracle WebCenter Content Service for Oracle Universal Content Management. It uses the authentication information from an SSO partner to enable access to the Oracle Universal Content Management file. The portal user name must match the Oracle Universal Content Management user name; so the portal and Oracle Universal Content Management users must be synchronized from a common source, such as LDAP. To enable Trusted Authentication click-through: Disable User Preference click-through in the portal: In the portal's Administrative Object Directory, open the Oracle WebCenter Content Service for UCM folder. Expand the Web Service section and click the Oracle WebCenter Content Service for UCM Web service. On the left, under Edit Object Settings, click Advanced URL Settings. Remove the entry from the User Configuration URL box. On the left, under Edit Object Settings, click Preferences. Delete all User Preferences and click Finish. Stay logged in to the portal with the Oracle WebCenter Content Service for UCM folder open for the next procedure. Enable Trusted Authentication click-through on the Oracle WebCenter Content Service for Oracle Universal Content Management host computer: In the Oracle WebCenter Content Service for Oracle Universal Content Management config.xml file (located by default in C:\Oracle\Middleware\wci\ptucmcws\10.3.3\settings\config), set clickthroughAuthType as follows: <clickthroughAuthType>3</clickthroughAuthType> In config.xml file, specify the following parameters for the SSO partner: <trustedUserName></trustedUserName> <trustedPassword></trustedPassword> <trustedDomain></trustedDomain> Note: The value for the <trustedPassword> parameter must be encrypted. Use the Encrypt Password link located at: http://RemoteServer:port/ptdctmcws/web/install/index.html
Admin Preference/Content Source Credential	If you prefer, you can set all click-through requests to use the credentials configured in the content source to retrieve documents upon click-through. This is referred to as the Super User click-through method. To enable Super User click-through: Disable User Preference click-through in the portal: In the portal's Administrative Object Directory, open the Oracle WebCenter Content Service for UCM folder. Expand the Web Service section and click the Oracle WebCenter Content Service for UCM Web service. On the left, under Edit Object Settings, click Advanced URL Settings. Remove the entry from the User Configuration URL box. On the left, under Edit Object Settings, click Preferences. Delete all User Preferences and click Finish. Stay logged in to the portal with the Oracle WebCenter Content Service for UCM folder open for the next procedure. Enable content source credential click-through on the Oracle WebCenter Content Service for Oracle Universal Content Management host computer: In the Oracle WebCenter Content Service for Oracle Universal Content Management config.xml file (located by default in C:\Oracle\Middleware\wci\ptucmcws\10.3.3\settings\config), set clickthroughAuthType as follows: <clickthroughAuthType>4</clickthroughAuthType>

Troubleshooting

This section provides reference information for troubleshooting problems you might encounter when you use the Oracle WebCenter Content Service for Oracle Universal Content Management. It includes the following topics:

• Reviewing Log Files

• Modifying Configuration Files

• Diagnosing Unexpected Results

Reviewing Log Files

If you encounter problems with crawl jobs, you can review the job logs provided through the portal's Automation Service Utility. For details, refer to the portal's online help or to the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Interaction.

If you encounter problems with the Oracle WebCenter Content Service for Oracle Universal Content Management, you can use Logging Spy to analyze portal communication.

The Oracle WebCenter Content Service for Oracle Universal Content Management also logs communication on the Oracle WebCenter Content Service for Oracle Universal Content Management host computer. To analyze logs specific to the Oracle WebCenter Content Service for Oracle Universal Content Management processes, review the logs in install_dir\ptucmcws\10.3.3\settings\logs.

Modifying Configuration Files

If you encounter error messages or logs that indicate misconfiguration in the Oracle WebCenter Content Service for Oracle Universal Content Management config.xml file, you can modify the config.xml file to correct syntax or mismatched values.

The following table describes the syntax and values for config.xml configuration parameters.

Table C-2 Configuration Parameters

Configuration (sample value in bold)	Value Description
baseURL	The URL for the Oracle WebCenter Content Service for Oracle Universal Content Management application on the Oracle WebCenter Content Service for Oracle Universal Content Management host computer. When you configure Oracle WebCenter Interaction applications, always specify the fully qualified domain name for hosts to avoid host and domain name resolution mismatches.
<clickthroughAuthType>1</clickthroughAuthType> <trustedUserName></trustedUserName> <trustedPassword></trustedPassword> <trustedDomain></trustedDomain>	The clickthroughAuth type parameter determines what type of authentication to use during click-through. The following values are valid: 1 = User Preferences 2 = Basic Authentication 3 = Trusted Authentication 4 = Admin Preferences We recommend you set the accessLevelMapping value to 3 (read) if the clickThroughAuthType is either 4 or 5. See Configuring Security for Document Discovery, for details on accessLevelMapping. For Trusted authentication (option #3), credentials must be supplied below. The password must be encrypted. Follow the instructions on http://RemoteServer/ptucmcws/web/install/index.html to generate an encrypted password.
<accessLevelMapping>2</accessLevelMapping>	The accessLevelMapping maps the Oracle Universal Content Management access level setting to the portal's access privilege setting. Oracle Universal Content Management users who have an access level setting that is equal to or higher than the value configured here will receive Read access in the portal. The default setting is 2 which means that Oracle Universal Content Management users with Browse access or higher will receive Read access in the portal. Browse users will not, however, be able to click through and read the file contents because the Oracle WebCenter Content Service for Oracle Universal Content Management verifies their credentials upon click-through and will not return the document unless they have Read access in Oracle Universal Content Management. This is how the portal mimics the Oracle Universal Content Management Browse-level security. An important dependency of this functionality is that userCredentialClickThrough must be set to true (see note above regarding setting this parameter to 3 if userCredentialClickThrough is set to false). Valid values for this parameter are: 2 = Browse 3 = Read
<preferredRenditionFormat>default</preferredRenditionFormat>	Set the preferredRenditionFormat to the desired format for the document to be returned during click-through. The portal supports the following formats: default (or blank): The document's native format pdf: Acrobat PDF msw8: Microsoft Word 97/2000 crtext: Text (Windows) The setting is “preferred” because the Oracle WebCenter Content Service for Oracle Universal Content Management will return the native format for documents if pdf/msw8/crtext is not available. This option only applies if userCredentialClickThrough is set to true.

Diagnosing Unexpected Results

The following table summarizes cases in which users encountered unexpected results with the Oracle WebCenter Content Service for Oracle Universal Content Management. You can use this table as a reference for particular issues you might encounter or as a guide for troubleshooting any similar problems you might encounter.

Table C-3 Troubleshooting

Symptom	Solution
HTTP 500 Error on Clickthrough Users have reported that the URL property in a document's Properties page is clickable, but the link returns an error. The URL property is unique as it is clickable in the Document Properties page (accessed by clicking Properties for a document crawled into the portal). This is potentially confusing to users because the value is technical and clicking it results in an HTTP 500 error.	To avoid potential confusion, map the URL property in a content type to an Override Value, such as a space, which will prevent the technical URL from appearing in the Properties page.
Port conflict, port in use, BindException	Port numbers for HTTP and HTTPS are configured in install_dir\ptdctmcws\10.3.3\settings\config\application.conf. Edit the http and https settings in application.conf to set the value to an available port. The service must be restarted to pick up changes made in the configuration file. Note that changes to a service port number require corresponding changes to any Web service or remote server settings that may reference that port number.
Memory consumption, Out of Memory Errors	The maximum amount of memory, in megabytes, that the service JVM will be allowed to use is controlled by the wrapper.java.maxmemory property, configured in the file install_dir\ucmcws\10.3.3\settings\config\wrapper.conf. For example, the following line shows a maximum memory setting of 1 GB: wrapper.java.maxmemory=1024 The setting corresponds directly to the -Xmx parameter used by the java executable. The default value of this setting in the config file will be adequate for most configurations. For large production configurations, especially those in which the service is installed on a dedicated host computer, this value should be set as high as possible (for example, 1024 or 1536) but should always remain below the amount of physical RAM on the host computer.