1. Locate the script corresponding to the implementation in the folder specified below.

   MW_HOME/wccontent/axf/adapters/ebs/R11/

   MW_HOME/wccontent/axf/adapters/ebs/R12/

2. In the AXF_EBS_ATTACHMENTS_CONFIG.sql script, change the host name and port to match your Imaging server.
   If you are using UCM web service implementation and the value of the webkey is anything other than cs, add the following in AXF_EBS_ATTACHMENTS_CONFIG.sql :

   Insert into AXF_COMMAND_PARAMETERS (PARAMETERID,EVENTID,PARAMETERNAME,DATASOURCENAME,DATABLOCKNAME,FIELDNAME,CONSTANTVALUE,CREATED_BY,CREATION_DATE,LAST_UPDATE_DATE,LAST_UPDATED_BY,LAST_UPDATE_LOGIN) values (AXF_COMMAND_PARAMETERS_SEQ.NEXTVAL,v_eventId,'CS_WEBKEY','CONSTANT',null,null,’<WEBKEY_VALUE>’,0,sysdate,sysdate,0,0);

3. Log in to the Oracle E-Business Suite database as the Oracle E-Business Suite plug-in schema user (AXF) and run the appropriate script.

   To execute the script, enter:

   @AXF_EBS_ATTACHMENTS_CONFIG.sql

4. Open the AXF_FND_MAP table and delete unneeded rows.

   See AXF_FND_MAP Table (Oracle E-Business Suite Forms). The script inserts multiple rows, allowing you to keep the rows that apply to your particular configuration.

1. Locate the AXF_PSFT_ATTACHMENTS_CONFIG.sql sample script in this folder:

   MW_HOME/wccontent/axf/adapters/psft/

2. Log in to the Oracle PeopleSoft database as a user with administrative privileges.
   If you are using UCM web service implementation and the value of the webkey is anything other than cs, add the following in AXF_PSFT_ATTACHMENTS_CONFIG.sql:

   Insert into PS_AXF_CMD_PARAMS (AXF_CMD_PARAMS_ID,AXF_CMDS_ID,AXF_PARAM_NAME,AXF_DATASOURCE,AXF_RECORD_NAME,AXF_FIELD_NAME,AXF_CONSTANT_VALUE) values (111,101,'CS_WEBKEY','CONSTANT',' ',' ','<WEBKEY_VALUE>');

3. Modify the sample script to include the values you identified for your Oracle PeopleSoft entities in Placing AXF Components on Oracle PeopleSoft Pages, then run the script.

   To execute the script, enter:

   @AXF_PSFT_ATTACHMENTS_CONFIG.sql

4. Specify an Oracle PeopleSoft role in the PS_AXF_COMMANDS Table to grant users permission to use a specified user interface item. For example, you might change the Employee value to PeopleSoft User or an appropriate Oracle PeopleSoft user role.

1. If upgrading from an earlier installation of the adapter, back up previous customizations, as described in Backing Up Customizations Before Upgrading.
2. Log in to Content Server as an administrator.
3. Choose Admin Server from the Administration menu.

   The Component Manager page displays.

4. Choose Integration.

   The Content Server components described in Table 6-5 are listed as Integration options.

5. Select the AppAdapterCore component to enable it.
6. Select any one of the appropriate business application component:

   • AppAdapterEBS.zip for Oracle E-Business Suite

   • AppAdapterPSFT.zip for Oracle PeopleSoft

   • AppAdapterUniversal.zip for other business applications, as described in Configuring the Enterprise Application Adapter Framework.

7. Click Update.
8. Restart Content Server.
9. Check the Content Server and database logs to ensure that no application adapter install errors occurred.

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, install and enable it according to its installation documentation.

   The following components must be at or above the version level included with the installed Content Server:

   • YahooUserInterfaceLibrary

   • CheckoutAndOpenInNative

   • CoreWebdav

   • NativeOsUtils

   • ContentFolios

5. In the User Admin applet, ensure that the roles below have the correct access level to the corresponding security groups.

   In Content Server, choose the Administration option from the main menu, choose Admin Applets, then User Admin. Select Security, then Permissions by Role.

   • AFAdmin: AFDocuments (RWDA) and no permissions on any other groups

   • AFDelete: AFDocuments (RWD) and no permissions on any other groups

   • AFWrite: AFDocuments (RW) and no permissions on any other groups

   • AFRead: AFDocuments (R) and no permissions on any other groups

1. Configure the business application to provide an application entity context link, button, or menu item to call AXF via the SOAP service and to pass the Managed Attachments attributes listed in Table 6-6.

   • Example provides a sample SOAP XML file for calling AXF and Table 6-7 describes fields in the AXFRequest.

   • Example provides a sample AXFResponse and Table 6-8 describes fields in the AXFResponse.

     The SOAP response contains the Managed Attachments page's URL. If an error occurs during the grant call, an AXF Error Page URL is returned.

   For UCM web service implementation, the WSDL URL is:

   http://CS Hostname:CS Port/idcws/AfGrantAccess?wsdl

   For IPM web service implementation, the WSDL URL is:

   http://Imaging Hostname:Imaging Port/axf-ws/AxfSolutionMediatorService?wsdl

   Table 6-6 Attributes to Pass Via SOAP Call to AXF

   Managed Attachments Attribute Key	Description	Example Value
   application (required)	Specifies the business application instance name, providing a unique identifier to differentiate between instances.	BIZAPP_instanceA
   businessObjectType (required)	Specifies the business application's object type, typically the name of the record where the business object data is stored.	REQ_HEADERS
   businessObjectKey1...businessObjectKey5 (one pair required)	Specifies the ObjectKey portion of key-value pairs that uniquely map business application record fields to Content Server. One key-value pair is required, and up to 5 pairs are supported.	REQUISITION_HEADER_ID
   businessObjectValue1...businessObjectValue5 (one pair required)	Specifies the ObjectValue portion of key-value pairs that uniquely map business application record fields to Content Server. One key-value pair is required, and up to 5 pairs are supported.	1234
   labelValue1...labelValue5 (optional)	Specifies labels to be displayed in the Managed Attachments page's title. Use these labelValue fields to pass text constants and record data that will allow the end user to see, via the user interface, the specific application entity record to which the Managed Attachments apply. Labels are optional, and up to 5 label values are supported.	Business Unit US001 Requisition ID 1234
   extraParamName (optional; for example, extraxReqNum)	Extra parameter to be passed as metadata from the business application to Content Server in check-in or scan forms. (For details, see Passing Values Via Enterprise Application Adapter Framework.)	1234

   Following is an example of Sample SOAP XML File for Calling AXF:

   <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://service.axf.imaging.oracle/">
         <soapenv:Header>
               <Security xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
               <UsernameToken>
                     <Username>weblogic</Username>
                     <Password>welcome1</Password>
               </UsernameToken>
               </Security>
         </soapenv:Header>
         <soapenv:Body>
               <ser:execute>
                     <request>
                           <solutionNamespace>UCM_Managed_Attachments</solutionNamespace>
                           <commandNamespace>UCM_Managed_Attachments</commandNamespace>
                           <conversationId></conversationId>
                           <systemName></systemName> <!-- future use -->
                           <role></role> <!-- future use -->
                           <userContext></userContext> <!-- future user -->
                           <username>jcooper</username>
                           <requestParameters>
                                 <entry>
                                       <key>application</key>
                                       <value>BIZAPP_instanceA</value>
                                 </entry>
                                 <entry>
                                       <key>businessObjectType</key>
                                       <value>REQ_HEADERS</value>
                                 </entry>
                                 <entry>
                                       <key>businessObjectKey1</key>
                                       <value>BUSINESS_UNIT</value>
                                 </entry>
                                 <entry>
                                       <key>businessObjectValue1</key>
                                       <value>US001</value>
                                 </entry>
                                 <entry>
                                       <key>businessObjectKey2</key>
                                       <value>REQUISITION_HEADER_ID</value>
                                 </entry>
                                 <entry>
                                       <key>businessObjectValue2</key>
                                       <value>1234</value>
                                 </entry>
                                 <entry>
                                       <key>extraxReqNum</key>
                                       <value>1234</value>
                                 </entry>
                           </requestParameters>
                     </request>
               </ser:execute>
         </soapenv:Body>
   </soapenv:Envelope>

   Table 6-7 AXFRequest Attributes

   AXFRequest Attributes	Description	Example
   solutionNamespace	SolutionNamespace in which to execute the command.	UCM_Managed_Attachments
   commandNamespace	Command to execute within the specified SolutionNamespace.	UCM_Managed_Attachments
   conversationID	Currently opened conversation created by AXF. This attribute is blank if it is the first call and is not used by the Managed Attachments solution.
   systemName	Reserved for future use.
   role	Reserved for future use.
   userContext	Reserved for future use.
   userName	Business application user name. (Note that for the Managed Attachments solution, the USERNAME_PASS_THROUGH parameter must be set to TRUE if used with AXF for BPEL. For more information about USERNAME_PASS_THROUGH, see Restoring Business Application User Pass Through for Managed Attachments.)	jcooper
   requestParameters	A collection of key/value pairs providing the command parameters.	<entry> <key>application</key> <value>BIZAPP_instanceA</value> </entry>

   Following is an example of AXFResponse:

   <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
         <S:Body>
               <ns2:executeResponse xmlns:ns2="http://service.axf.imaging.oracle/">
                     <response>
                           <conversationId>b80ce79b-6b46-4302-ab59-ddb91e30692b</conversationId>
                           <responseCommands>
                                 <command>OPEN_BROWSER</command>
                                 <value>http://imaging.example.com:16200/cs/idcplg/-UniversalProfile?IdcService=GET_SEARCH_RESULTS_FORCELOGIN&ResultTemplate=Universal_LIST&afGuid=00000132-b540-810e-63f4-00e94577f990</value>
                           </responseCommands>
                     </response>
               </ns2:executeResponse>
         </S:Body>
   </S:Envelope>

   Table 6-8 AXFResponse Attributes

   AXFResponse Attributes	Description
   conversationId	Current conversation created by AXF to help maintain state/context for the transaction.
   responseCommands	A collection of key/value pairs providing a command for the business application to execute with a single parameter. In most cases, it is the OPEN_BROWSER command, which provides a URL that the business application must open.

2. Display the URL returned by the AXF SOAP call in a new browser window or iFrame.
3. Optionally, configure SOAP over SSL security for the call, as described in Securing Communications Through SSL (Other Business Applications).

1. Open the preferences.hda file in the following directory:

   UCM_Instance/data/appadapter

   This file provides Managed Attachments configuration options in the ResultSet sections described in the following table:

   Table 6-13 ResultSet Sections in Preferences.hda File

   Section	Description
   AFEnvironmentConfiguration	Use to configure Content Server environment variables for the adapter. For more information, see Table 6-9 and Customizing the Managed Attachments Solution.
   AFRelationshipAttributes	Use to configure custom relationships between attached documents and business entities. For more information, see Configuring Attachment Relationship Attributes.
   AFRevisionSpecificEntities	Use to enable users to access the document version that was attached, even if the document was later updated. For more information, see Configuring Revision-Specific Mode.

2. Scroll to the AFEnvironmentConfiguration ResultSet section, and edit the entries described in Working With Global Configuration Variables as needed. For more information about customizing the Managed Attachments solution using these variables, see Customizing the Managed Attachments Solution.

1. On Content Server, choose Managed Attachments from the Administration menu.

   The Configure Managed Attachments page displays.

2. Scroll to the Role Specific Configuration settings in the lower portion of the page and click Add.
3. In the Add Role Specific Configuration page shown in Figure 6-6, enter fields to customize a Managed Attachments variable based on user role and click Update. This example specifies the following settings:

   • Configuration Name: AppAdapterGrantPrivilege

   • Value: R

   • Role: readRole

   The AppAdapterGrantPrivilege variable specifies the access level to grant to users. This example assumes that you have configured and assigned the user role (readRole, in this example) using User Admin functions in Content Server.

   Figure 6-6 Example Role Specific Configuration

   
   Description of "Figure 6-6 Example Role Specific Configuration"

1. On Content Server, choose Managed Attachments from the Administration menu.

   The Configure Managed Attachments page displays.

2. Scroll to the Business Context Specific Configuration settings in the lower portion of the page and click Add.
3. In the Business Context Specific Configuration page shown in Figure 6-7, enter fields to customize a Managed Attachments variable based on business context, and click Update.

   The example shown in Figure 6-7 configures the Scan button to display when the businessObjectContext passed from the business application equals ScanContext. This example specifies the following settings:

   • Configuration Name: AppAdapterScanBtnVisible

   • Value: true

   • Role: ScanContext

   Figure 6-7 Example Business Context Specific Configuration

   
   Description of "Figure 6-7 Example Business Context Specific Configuration"
4. Configure the business application table to pass in the ScanContext value from the business application, just as you would configure key labels/values (labelValues).

   • For each Oracle PeopleSoft page to be configured, insert a row in the PS_AXF_CMD_PARAMS table that passes ScanContext. In PS_AXF_CMD_PARAMS Table, see the row in which AXF_PARAM_NAME=businessObjectContext and AXF_CONSTANT_VALUE=ScanContext.

   • For each Oracle E-Business Suite OAF page, insert a row in the OAF_AXF_CMD_PARAMS table that passes ScanContext. In OAF_AXF_CMD_PARAMS Table (Oracle E-Business Suite OAF), see the row in which AXF_PARAM_NAME=businessObjectContext and AXF_CONSTANT_VALUE=ScanContext.

   • For each Oracle E-Business Suite Forms page, insert a row in the AXF_COMMAND_PARAMETERS table that passes a context value. In AXF_COMMAND_PARAMETERS Table (Oracle E-Business Suite Forms), see the example row in which PARAMETERNAME=businessObjectContext and CONSTANTVALUE=ScanContext. Note that you can specify a value using a constant value or a data block/fieldname.

1. On Content Server, choose Managed Attachments from the Administration menu.

   The Configure Managed Attachments page displays. Currently selected global settings are displayed under the Global Configuration heading.

2. Scroll to the Entity Specific Configuration settings in the lower portion of the page and click Add.
3. In the Add Entity Specific Configuration page shown in Figure 6-8, enter fields to override the global setting for an entity or application.

   • To override at the business entity level, complete all fields. The example values below configure the From Repository button to display for the ExpenseClaims business entity only, regardless of the global setting.

   • To override at the application level, leave the Object Name field blank. Doing so in the example below would display the From Repository button for all business entities of the EBS_Instance application, regardless of the global setting.

   Field	Description	Example
   Application Name	Identifies the business application	EBS_Instance
   Object Name	Identifies the business entity	ExpenseClaims
   Configuration Name	Global configuration variable to set for business entity	AppAdapterRepoAttachButtonVisible
   Configuration Value	Variable value to set for business entity	true

   Figure 6-8 Example Entity Specific Configuration

   
   Description of "Figure 6-8 Example Entity Specific Configuration"

   Note:

   You must complete either the Application Name or Object Type field. Entering an object type without an application name applies the setting to the business entity of all applications with that object type.

1. On Content Server, create or modify a document type.

   For more information about document types, see the Content Server documentation.

2. In the preferences.hda file, add a new row in the AFEnvironmentConfiguration resultset. For general information, see Alternatively Editing Settings in the Preferences.hda File.
3. Insert an entry that identifies the document type to use as the default type for a specified business entity, where:

   • name: dDocType

   • value: document type key

   • dAFApplication: Application to which you assign this document type

   • dAFBusinessObjectType: Business entity within application to which you assign document type

   Example (7-3) sets the document type ExpenseClaimsType as the default type when users attach documents to the ExpenseClaims business entity (within the PSFT_Instance application).

   Following is an example of Custom Default Document Type For Expenses Business Entity:

   dDocType
   ExpenseClaimsType
   PSFT_Instance
   ExpenseClaims
   

4. Restart the Content Server.

1. On Content Server, choose Managed Attachments from the Administration menu.
2. Under Global Configuration, change a button's global setting to false to hide it, or true to display it.
3. To configure a button's display at a business entity level, create an entity-specific configuration by clicking Add under Entity Specific Configurations and completing fields as described in Customizing Settings at Business Entity or Application Levels.

Following are the methods to customize scanning functionality using Oracle Distributed Document Capture 10g or using Oracle WebCenter Enterprise Capture 12c and higher. Note that the profiles are named as scan profile in Oracle Distributed Document Capture 10g and client profile in Oracle WebCenter Enterprise Capture 12c (and higher). This section includes the following topics:

• Enabling or Disabling Scanning

• Configuring an Alternate Scan Profile For a Business Entity

• Modifying the Document Classification Used

1. On Content Server, open Configuration Manager and navigate to the Application Fields tab.
2. Add one or more application fields.
3. Navigate to the Rules tab.
4. Edit the AFRelationshipAttributes rule. Add the application fields you added in step 2 to this rule.
5. On Content Server, choose Managed Attachments from the Administration menu.
6. On the Configure Managed Attachments page, scroll to the Attachment Relationship Attributes settings in the lower portion of the page, and click Add.

   The Add Attachment Relationship Attribute page displays.

   Figure 6-9 Add Attachment Relationship Attribute Page

   
   Description of "Figure 6-9 Add Attachment Relationship Attribute Page"
7. Complete fields for the attribute and click Update. The example in Figure 6-9 shows a relationship attribute (Print) configured for an WO1 business object for an Oracle PeopleSoft application.

   Element	Description	Example
   Application Name	Business application for which the relationship attribute is configured.	PSFT_Instance
   Object Type	Business object for which to enable the relationship attribute	WO1
   Attribute Name	Relationship attribute	Print
   Attribute Type	Attribute's type. Available types include: Text, Long Text, Date, Memo, Integer, and TrueFalse.	TrueFalse

1. Open the preferences.hda file, and add a new row in the AFRevisionSpecificEntities resultset. (For general information, see Alternatively Editing Settings in the Preferences.hda File.)

   Each row in the resultset represents one business entity for which to enable revision specific attachments, where:

   • dAFApplication refers to the business application for which to enable the revision feature.

   • dAFBusinessObjectType refers to the business object for which to enable the revision feature.

   Following example shows revision-specific mode configured for a CallRecords business object for an Oracle E-Business Suite application.

   Following is an example of AFRevisionSpecificEntities Customization:

   @ResultSet AFRevisionSpecificEntities
   2
   dAFApplication
   dAFBusinessObjectType
   EBS_Instance
   CallRecords
   @end

1. Create a copy of the appropriate default result template and register the template with a new name, preferably in a new component.

   • The Oracle E-Business Suite template is located at:

     UCM_HOME/custom/AppAdapterEBS/adapter_list_results_template.htm

   • The Oracle PeopleSoft template is located at:

     UCM_HOME/custom/AppAdapterPSFT/ps_adapter_list_results_template.htm

   • The Enterprise Application Adapter Framework template is located at:

     UCM_HOME/custom/AppAdapterUniversal/universal_adapter_list_results_template.htm

2. In the preferences.hda file, add an entry in the AFEnvironmentConfiguration section as follows:

   ResultTemplate
   Template Reference
   Application Name
   Business Entity
   

   In the following example, all requests to Managed Attachments for the WorkOrder business entity would use the EBS_WORK_ORDER_LIST custom result template instead of the default Oracle E-Business Suite template.

   Following is an example of Preferences.hda Entry For Specifying a Custom Result Template:

   ResultTemplate
   EBS_WORK_ORDER_LIST
   EBS_Instance
   WorkOrder

1. In the preferences.hda file, add an entry in the AFEnvironmentConfiguration section.
2. Set the value of the AppAdapterDefaultDisplayColumns configuration variable as a comma-delimited list containing Content Server metadata field names.

   In the following example, the first entry sets document title, type, author, and date as the default columns for the EBS_Instance application. The second entry overrides this setting for the CallRecords business entity by adding the revision column (dRevision) as a default column.

AppAdapterDefaultDisplayColumns
dDocTitle,dDocType,dDocAuthor,dInDate
EBS_Instance

AppAdapterDefaultDisplayColumns
dDocTitle,dDocType,dDocAuthor,dInDate,dRevision
EBS_Instance
CallRecords

1. Add the following row to the AXF_PROPERTIES table:

   Table 6-16 AXF_PROPERTIES Values For PaperClip Use

   PROPNAME	PROPVALUE
   AXF_PAPERCLIP	Set to TRUE to enable the paperclip option, or FALSE (default) to disable it. (The value must be in uppercase characters.)

   For more information, see AXF_PROPERTIES Table (Oracle E-Business Suite Forms).

1. From Content Server, choose Managed Attachments from the Administration menu.
2. Under Global Configuration, enter one or more field names to pass, using a comma to separate multiple names.

   • Enter field names in the AppAdapterExtraCheckinMetadata field to pass their values directly to the Content Check In page.

   • Enter field names in the AppAdapterExtraScanMetadata field to pass their values directly to the Scan Document page.

3. Access the command parameters table for your business application.

   • For an Oracle E-Business Suite Forms configuration, access the AXF_COMMAND_PARAMETERS Table (Oracle E-Business Suite Forms) and the AXF_MA_PARAMETERS Table (Oracle E-Business Suite Forms) to pass additional parameters.

   • For an Oracle E-Business Suite OAF configuration, access the OAF_AXF_CMD_PARAMS Table (Oracle E-Business Suite OAF).

   • For a PeopleSoft configuration, access the PS_AXF_CMD_PARAMS Table.

   • For an Enterprise Application Adapter Framework configuration, see Passing Values Via Enterprise Application Adapter Framework.

4. Add entries in the table for the extra values to be passed to Content Server, similar to adding labelValue rows. See the example command shown in the following example and the example table shown in Table 6-17.

   Add a row for each metadata value, prepending the Content Server field name with extra. For example, xReqNum becomes extraxReqNum and dDocTitle becomes extradDocTitle.

   Note:

   Typically, Content Server extra information fields have an x character in front of them and standard ones have a d character in front of them. For more information, see Standard Metadata Fields in the Managing Oracle WebCenter Content.

   Following is an example of Inserting Extra Metadata Field into OAF Command Parameters Table:

   Insert into OAF_AXF_CMD_PARAMS (AXF_CMD_PARAMS_ID, AXF_CMDS_ID, AXF_PARAM_NAME, AXF_DATASOURCE,AXF_VIEW_OBJ_NAME, AXF_ATTRIBUTE_NAME,AXF_CONSTANT_VALUE) values (OAF_AXF_CMD_PARAMS_SEQ.NEXTVAL,v_cmdId,'extraxReqNum','DATA','ReqHeaderVO', 'ReqNum',null);

   Table 6-17 Example OAF_AXF_CMD_PARAMS Table With Extra Metadata Field Specified

   AXF_CMD_PARAMS_ID	AXF_CMDS_ID	AXF_PARAM_NAME	AXF_DATASOURCE	AXF_VIEW_OBJ_NAME	AXF_ATTRIBUTE_NAME	AXF_CONSTANT_VALUE
   1	1	application	CONSTANT			EBS_instanceA
   2	1	businessObjectType	CONSTANT			REQ_HEADERS
   3	1	businessObjectKey1	CONSTANT			REQUISITION_HEADER_ID
   4	1	businessObjectValue1	DATA	ReqHeaderVO	RequisitionHeaderId
   5	1	labelValue1	DATA	ReqHeaderVO	PreparerName
   6	1	labelValue2	DATA	ReqHeaderVO	ReqNum
   7	1	extraxReqNum	DATA	ReqHeaderVO	ReqNum

5. For an Oracle E-Business Suite Forms configuration, populate the AXF_MA_PARAMETERS Table (Oracle E-Business Suite Forms) table using a script similar to the following:

   BEGIN
     FOR x1 IN
     (SELECT fndid, block_name FROM axf.axf_fnd_map WHERE FORM_NAME =
   'APXINWKB')
     LOOP
     INSERT
     INTO AXF.AXF_MA_PARAMETERS VALUES
     (
     AXF.AXF_MA_PARAMETERS_SEQ.nextval,
     x1.fndid,
     'extraxIDNumber',
     'DATA',
     x1.block_name,
     'INVOICE_NUM',
     NULL,
     '0',
     SYSDATE,
     SYSDATE,
     '0',
     '0'
     );
     END LOOP;
   END;

   This script creates many new rows in the AXF_MA_PARAMETERS table. You can use the script for other forms by changing the form_name parameter (APXINWKB) to another form_name parameter (FAXASSET or PERWSHRG). You can also change the metadata field (xIDNumber) to another field. Replace INVOICE_NUM in the script depending on the value that you want to pull from a form. For example, in FAXASSET Form you must replace INVOICE_NUM in the script with ASSET_NUMBER.

1. On Content Server, choose Managed Attachments from the Administration menu.
2. On the Configure Managed Attachments page, scroll to the Entity Specific Configuration settings in the lower portion of the page, and click Add.

   The Add Entity Specific Configuration page displays.

   Figure 6-11 Configuring Entity Level Private Attachments Security Group

   
   Description of "Figure 6-11 Configuring Entity Level Private Attachments Security Group"
3. In the Add Entity Specific Configuration page shown in Figure 6-11, complete the fields, identifying the AppAdapterPrivateSecGroup variable and the alternate security group to use for a specified business entity, where:

   • Application Name: Application for which to assign alternate security group

   • Object Type: Business entity for which to assign alternate security group

   • Configuration Name: AppAdapterPrivateSecGroup

   • Configuration Value: Alternate security group

   The example values shown in Figure 6-11 set ClaimsSecurity as the security group when users attach private documents to the ExpenseClaims business entity (within the PSFT_Instance application).

4. Assign the following roles to the specified security group (must be the same as those assigned to the AFDocuments security group): AFRead, AFWrite, AFDelete, and AFAdmin.
5. In the config.cfg file, add the alternate security group to the SpecialAuthGroups configuration variable if you have configured Access Control List (ACLs) and want to use Entity Security for Managed Attachments.

1. Open the ManagedAttachmentButtonRN.xml file, which was imported into the MDS repository on the Oracle E-Business Suite OAF side during setup.
2. Locate the following line and replace Managed Attachments with a localized name.

   <oa:button id="MAButton" prompt="Managed Attachments"/>
   

3. Using the import command, reimport the file into MDS.

Business application users must have a Content Server account to display the Managed Attachments page within the supported business application entity. In addition, the authentication model configured for Content Server and the business application determines how users are authenticated the first time they activate managed attachments from a business application record:

• Content Server configured for single sign-on: If the business application is not configured for single sign-on, the Content Server single sign-on login prompt displays. (If the business application is configured for single sign-on, the user has been authenticated so no login prompt displays.)

• Content Server not configured for single sign-on: The Content Server login prompt displays, regardless of the selected business application authentication model.

  Note:

  No user authentication is needed for AXF if security checks are properly configured, as described in Configuring Authentication and Security.

When checking documents into Content Server through the Managed Attachments user interface, users specify their access by choosing one of two modes:

• private (not shared): Users can access these documents only through their associated business application entity screens through the Managed Attachments user interface. Users (including the user who checks in a document) cannot search for or access a private document using any other standard Content Server user interface. This is the default security mode when checking in a new document through the Managed Attachments user interface.

  Note:

  The AppAdapterCheckinPrivate global configuration variable determines if the Share Document field on the Content Check-In page is deselected by default (set for private check-in). For more information, see Working With Global Configuration Variables.

  Note:

  Private (not shared) documents are automatically assigned to a special security group called AFDocuments, and users who have access to the business application entity are granted temporary access to the documents when they invoke the Managed Attachments user interface. The AppAdapterPrivateSecGroup variable enables you to override on a per entity level the security group to use for private attachments, and assign them to an alternate group. For more information, see Configuring an Entity's Private Attachments Security Group.

  In certain exceptional cases, an administrator might grant special users direct access to the AFDocuments security group by permanently assigning the AFRead, AFWrite, AFDelete, or AFAdmin roles for the AFDocuments security group, in which case the user could access a private document through any standard Content Server user interface.

• shared: These documents are more easily accessed than private documents, because their security is managed by Content Server. In addition to access through their associated business application entity screens through the Managed Attachments user interface, any Content Server user with a document's assigned security group access can search for and access the document using any standard Content Server user interface.

  Note:

  Users can view shared documents only in AutoVue (if configured). They cannot view private documents. For details, see Configuring Oracle AutoVue Document Viewing.

The default document viewing option for the Managed Attachments page is the standard web rendition provided by Content Server. For enhanced viewing options, the adapter also supports Oracle AutoVue through VueLink for Content Server, where non-private attachments of virtually any document type are available for viewing, printing, collaboration, annotation, and mark up, delivered securely using Web technologies.

Important Points About the AutoVue/Adapter Integration

• If configured, users can view all non-private attachments through AutoVue. For details on shared versus private documents, see Configuring User Authentication.

• The VueLink integration serves as a bridge that securely streams documents from the Content Server repository to AutoVue for viewing, digital markup and collaboration. Digital markups are saved in the Content Server repository and associated with the attached document.

• By default, AutoVue is turned off in the Managed Attachments solution. You activate it on the Configure Managed Attachments page, by displaying the AutoVue icon and identifying the URL to the AutoVue servlet to launch when the user clicks the View in AutoVue icon.

• As with other preferences settings, you can enable the AutoVue integration at the global, application, and business entity levels.

• AutoVue trusts the user authentication against Content Server. Once authenticated to Content Server, no further authentication to AutoVue is required for users to view attached documents using AutoVue.

• Viewing or annotating a document in AutoVue does not check it out or prevent it from being edited by others. Annotations are contained in a separate layer from their corresponding document.

1. Configure the Content Server/AutoVue integration.

   Follow the procedures outlined in the Oracle VueLink 20 for Oracle UCM System Administrator Manual

2. On Content Server, choose Managed Attachments from the Administration menu.
3. On the Configure Managed Attachments page, enable display globally of the AutoVue icon by setting the AppAdapterAutoVueIconVisible variable to True. For general information, see Configuring Managed Attachments Settings.
4. In the AutoVueURLPath field, specify the AutoVue servlet to run, using the following format:

   http://ucm_host name:port/web_root/idcplg?IdcService=VIEW_IN_AUTOVUE
   

   For example:

   http://ucm1.example.com/cs/idcplg?IdcService=VIEW_IN_AUTOVUE
   

5. Optionally specify application or business entity settings by adding new rows in the AFEnvironmentConfiguration resultset for the AppAdapterAutoVueIconVisible and AutoVueURLPath variables, where:

   • dAFApplication: Application in which to display or hide button

   • dAFBusinessObjectType: Business entity within application in which to display or hide button

   Figure 6-12 contains several AutoVue settings. It assumes that the View in AutoVue icon is set to false globally. The first two entries enable and display the icon for the PSFT_Instance_A application. The last two entries enable and display the icon for the PSFT_Instance_B application, but only within its PIM business entity.

   Figure 6-12 Example AutoVue Document Viewing

   
   Description of "Figure 6-12 Example AutoVue Document Viewing"

The Oracle WebCenter Enterprise Capture application enables an application such as the adapter to direct it to scan a document and pass in document metadata values. This allows users to scan a document or import a file (image or non-image file such as PDF or Microsoft Word file) from the Managed Attachments page and attach it to the selected business application record.

When configured for the adapter, document scanning works as follows:

• A Scan button is added to the Managed Attachments page. The user clicks the button, and selects options such as 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.) The user also specifies whether the document should be shared, and if so the user specifies a security group for the shared document from those to which the user has access.

• When the user clicks the Scan Document button, Oracle WebCenter Enterprise Capture's client launches in a new window and passes in parameters such as the client profile to use and business application entity values for later attachment.

• 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 Content Server using a Capture commit profile configured to output to WebCenter Content. (A Capture commit profile configured for Content output specifies connection information and field mappings between WebCenter Enterprise Capture and Content Server metadata fields.)

• Upon successful batch release, the user returns to the Managed Attachments page and refreshes the display to view the newly scanned document or imported file.

1. Refresh the Managed Attachments 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, and click Scan Document. A popup window opens where in you can specify the username, password, and the Oracle WebCenter Enterprise Capture Server details. Enter the following in the Server field: http://<capture_host>:<capture-port>.

   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 containing the Oracle E-Business Suite or Oracle PeopleSoft entity values.

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

The Oracle Distributed Document Capture application enables an application such as the adapter to direct it to scan a document and pass in document index values. This allows users to scan documents or import scanned image files from the Managed Attachments page and attach them to the selected business application record.

When configured for the adapter, document scanning works as follows:

• A Scan button is added to the Managed Attachments page. The user clicks the button, and selects options such as 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.) The user also specifies whether the document should be shared, and if so the user specifies a security group for the shared document from those to which the user has access.

• When the user clicks the Scan Document button, Oracle Distributed Document Capture's remote client launches in a new window, automatically authenticates and logs in the user (if configured), and passes in parameters such as the scan profile to use and business application entity values for later attachment.

• 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 a commit profile specified for the scan profile. (A Capture/Content Server commit profile specifies connection information and field mappings between Capture and Content Server metadata fields.)

• Upon successful sending, the user returns to the Managed Attachments page and refreshes the display to view the newly scanned document or imported scanned image file.

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

   Note:

   You can attach one document only via scanning or importing at a time.

   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 containing the Oracle E-Business Suite or Oracle PeopleSoft entity values.

3. Within the Oracle Distributed Document Capture client, review, index, and send the document.

   Note:

   If you decide to cancel a document scan or import, you must close the Oracle Distributed Document Capture window and return to the Managed Attachments page and perform a new scan or import. This ensures that index values are properly set for attachments.

4. Return to the Managed Attachments page and click Refresh. The newly scanned document or imported scanned image file should be displayed in the list. (It may take a few minutes to display.)