This chapter describes issues associated with Oracle WebCenter application adapters. It includes the following topics:
This section describes configuration issues and their workarounds. It includes the following topics:
When implementing an AXF solution using MS LDAP as a user repository, the credential user must be the administrator belonging to the Administrators group within the Builtin CN in MS LDAP. The AXF uses this credential user when making certain calls (for example, when retrieving a task list from SOA). In addition, you must configure the Group Base DN (in WLS Console, Provider Specific) to import CN=Builtin.
This section describes an alternative command line method for compiling Oracle E-Business Suite Forms for adapter use. It applies only to Oracle E-Business Suite 12 Forms use only, and does not apply to Oracle E-Business Suite 11.
Follow these steps to copy the AXF_CUSTOM.pld file, convert it to an AXF_CUSTOM.pll file, make modifications, and then compile it to an AXF_CUSTOM.plx file. Then follow the administrator's guide to modify the other file, CUSTOM.pll, and complete the Forms configuration.
Copy the AXF_CUSTOM.pld file to a UNIX system and run the dos2unix command to convert the file to UNIX format.
As an alternative, open the file in vi editor and manually remove the ^M characters from the file.
Enter the following command line to convert AXF_CUSTOM.pld to AXF_CUSTOM.pll:
$APPL_TOP>/au/12.0.0/resource frmcmp_batch.sh module=AXF_CUSTOM.pld userid=apps/apps output_file=AXF_CUSTOM.pll module_type=library parse=yes
Enter the following command line to convert AXF_CUSTOM.pll to AXF_CUSTOM.plx:
$APPL_TOP>/au/12.0.0/resource frmcmp_batch.sh module=AXF_CUSTOM.pll userid=apps/apps output_file=AXF_CUSTOM.plx module_type=library compile_all=special
Modify the CUSTOM.pll file by following the steps, starting with step 6, in the section "Compiling Oracle E-Business Suite Forms" in Oracle Fusion Middleware Administrator's Guide for Oracle Application Adapters for Oracle Enterprise Content Management.
Complete the remaining steps in this section.
The base URL for AutoVue configuration has changed for VueLink 20.1. When enabling AutoVue for the adapter, you set this URL in the AutoVueURLPath variable on the Configure Managed Attachments screen, as described in "Enabling AutoVue For the Adapter" in Oracle Fusion Middleware Administrator's Guide for Oracle Application Adapters for Oracle Enterprise Content Management.
Below are the old and new URLs for the AutoVueURLPath variable:
The Siebel identifier metadata fields (named xsiebel<entity>, as in xsiebelContact and xsiebelAcct) store Siebel entity values used for linking attachments to Siebel entities. Because they are not stored as regular metadata fields, they are not searchable and administrators configuring profiles should not treat them as regular metadata fields. (By default, these identifier fields are not visible to users in WebCenter Content. While users can enter search values into the fields if displayed, matching documents will not be found by the Content Server search engine.)
Note that users can attach documents to entities by entering entity row IDs into the Siebel identifier fields as a comma-separated list. In this case, Managed Attachments stores the values in a separate database table.
The Siebel adapter Siebel SIF files can be found at the following location after an 184.108.40.206 install:
This section describes documentation errata. It includes the following topics:
In the section "Working With Global Configuration Variables" in Oracle Fusion Middleware Administrator's Guide for Oracle Application Adapters for Oracle Enterprise Content Management, the documentation incorrectly indicates the format of variable assignment. Instead of the variable =value format in the preferences.hda file, the variable should be on one line and the value on the line below it. For example:
In the section "Configuring Oracle Distributed Document Capture For the Adapter" in Oracle Fusion Middleware Administrator's Guide for Oracle Application Adapters for Oracle Enterprise Content Management, the illustration of the Capture Administration, Add/Edit Custom Fields dialog box shows the dAFApplication, dAFBusinessObjectType, and dAFBusinessObject custom fields incorrectly named.