UCM: Migration of content files from one instance to another

Refer the link below in order to understand the entire process:
http://www.ateam-oracle.com/migrating-folders-and-content-together-in-webcenter-content/

Points:
1. Just set AllowArchiveNoneFolderItem=false in general Configuration Screen
2. Create an outgoing provider in the source instance, providing details of the target UCM instance.

3. This entire process works only for Folders_g component. If frameworkfolders component is enabled, and you try to access the Folder Archive Configuration page, then you get a !csJdbcGenericError error.


Setup Auto-Transfer
Auto-Replication should only be turned on once the initial Export, Transfer and Import steps have been completed.

On the Source archive
1. Click the Replication tab and in the Registered Exporters section click the Edit button. Check the box for Enable Automated Export. Click the Register button to register the Source instance as an exporter.
2. Select the Transfer To tab. Under Transfer Options, click the Edit button. Select the Is Transfer Automated option.

On the Target archive
1. Click the Replication tab in the Registered Importer section click the Register Self button.

Webcenter Sites: Asset, Asset Type, Asset definition

An asset represents a piece of content, such as an article or an image, that is managed in WebCenter Sites. It consists of a set of properties that helps distinguish it from other assets of the same type.

An asset type is a schema for distinguishing content types from one another. It is made up of a set of attributes, which can also be described as a set of fields on an asset creation form.

An asset type is a set of attribute names, while an asset is a set of attribute values.
An asset is an instance of an asset type.

When you create a new asset type for your CM site, a table in the database is also created, named for the asset type, that will store its instances (the assets). The columns in the database table correspond to the attribute names, while the rows correspond to its asset instances.

Asset definition controls the asset creation form. In particular, one can determine what attribute fields appear on the form and what order they appear in, as well as which attribute fields are mandatory versus optional.


Core asset types ship with WebCenter Sites by default. These are asset types that are typically used to support the structure of your CM site and website. Core asset types can be categorized as follows:
1. Container Assets: They "contain" lists of assets. Collection, Recommendation
2. Developer Assets: Query, Template, CSElement, Site Entry, Attribute Editor

Core "content" asset types does not ship with WebCenter Sites, such as articles, images, and media types.

All assets can be divided into two loosely defined categories: 
1. Content assets are items that visitors read and examine on your site.
2. Design assets are items that organize and format the content assets. Templates, CSElements, SiteEntry assets

The assets available to a site depend on the content applications and sample sites that are installed. As a general rule, the applications deliver design assets, and the sample sites deliver content assets.

WebCenter Sites: Product Architecture

WebCenter Sites	The base application for web experience and content management
WebCenter Sites: Community	Management of user-generated content, such as comments, ratings, and polling
WebCenter Sites: Gadgets	Management of gadgets for use on websites such as iGoogle
WebCenter Sites: Engage	Management of segments and strategic marketing tools
Content Connectors	For integration with other source repository systems, such as WebCenter Content, Documentum, Sharepoint, or file systems
WebCenter Sites: Analytics	Reporting of website content usage
Remote Satellite Server	Edge caching application for larger-scale deployments

Add attachments without using the Managed Attachments window

SCENARIO: When using the WebCenter Content Application Adapters for PeopleSoft or E-Business Suite, attachments are typically added by logging into PSFT or EBS and opening the Managed Attachments popup window. Another method of adding attachments can be done with direct checkins to the content server, as long as certain parameters are added to the checkin data.

To add attachments without using the Managed Attachments window, the following three parameters must be added to a checkin service call. This may be useful in migrating content from one system to another, or initial batchloading. To understand how these parameters work, look at the AFObjects table in the WebCenter Content schema. This table stores these values on checkin.

1. dAFApplication - This is the name of the EBS instance that is set as the application in the AXF_COMMAND_PARAMETERS table. If using the OAF pages in EBS, the application parameter is set in the OAF_AXF_CMD_PARAMS table.  If using PeopleSoft, this value is set in the PS_AXF_CMD_PARAMS table.  This parameter is usually the simplest one to determine, since many content items will be using the same value for this.
2. dAFBusinessObjectType - This setting must match what is setup in PSFT or EBS to pass as the business object type. For EBS forms, this is determined using the AXF schema table AXF_FND_MAP. The AXF_FND_MAP.ENTITY_NAME column is used for EBS forms. For example, when using the Oracle form Invoices, the dAFBusinessObjectType is AP_INVOICES. If using the "Requisition" page on iProcurement, this value will be what is set in the OAF_AXF_CMD_PARAMS for that OAF page (e.g. Requisition, or REQ_HEADER, depending on how the page was setup initially in this table). When using PeopleSoft, the value will be set in the PS_AXF_CMD_PARAMS table.  If performing checkins outside of the Managed Attachments window, this value must match exactly. If the match is not exact, content items checked in outside of the Managed Attachments window will not show up when the business user logs into EBS and opens the attachments popup.
3. dAFBusinessObject - This is the key value for the page or form. An example of the key value on the AP_INVOICES form is the invoice number. This value is typically an integer representing an ID for a invoice, requisition, purchase order, work order, etc. This must match exactly what is being used when the Managed Attachments windows is used for checkins. If the value used in direct checkins to the content server do not match, the attachments will not show up on the Managed Attachments page, and will be orphaned in the AFObjects table.

Understand that these fields are not WCC metadata fields, but data used in the AFObjects table. But like metadata field values, these can be set in local data for the checkin call to the content server. If using RIDC for a call the CHECKIN_NEW or CHECKIN_UNIVERSAL, these three settings can be added in the following manner, just like common metadata fields are added (dSecurityGroup or xCommencts are added in the same manner).

//Managed Attachments parameters - these 3 trip the AppAdpater filter so that the content item is attached via insert to the AFObjects table. 
dataBinder.putLocal("dAFApplication", "EBS_instanceA");
dataBinder.putLocal("dAFBusinessObjectType", "REQ_HEADERS"); 
dataBinder.putLocal("dAFBusinessObject", "181152");

If using a SOAP request for the checkin service call, the following example shows the fields that can be added when calling a checkin service using GenericSoapService (a.k.a GenericSoapPort).

<ns1:Field name="dAFApplication">EBS_instanceA</ns1:Field>
<ns1:Field name="dAFBusinessObjectType">AP_INVOICES</ns1:Field>
<ns1:Field name="dAFBusinessObject">1234</ns1:Field>

Again, to help understand how these values are stored on the WebCenter Content side, use SQL Developer or SQLPlus to review the AFObjects table.  To understand where these values come from on the application side, review each form or page and investigate the AXF schema to see how the form is configured to pass in the page name. For OAF pages, the table of most interest is OAF_AXF_CMD_PARAMS (and related OAF* tables). If using PSFT, the PS_AXF_CMD_PARAMS table contains the values. If using EBS forms, the AXF_FND_MAP and AXF_COMMAND_PARAMETERS table contain the values. 

Execute Enterprise Capture WLST Commands

Option 1:

1. Open a CMD prompt on your WLS server, and change to the "<ECM_HOME>\common\bin" directory (e.g. "C:\Oracle\Middleware\Oracle_ECM1\common\bin").
2. Run the wlst script ("wlst.cmd" on Windows or "wlst.sh" on Linux).
3. Connect to the server using the WLST command "connect(<userID>, <password>, <url>)". An example would be: connect('weblogic','welcome1','t3://localhost:7001')
4. Execute the domainRuntime() command.
5. At this point, any capture WLST command can be executed. To list the Capture commands, execute the help('capture') command to display a list of capture commands. You can then execute the help on each of the commands returned to get the syntax that is to be used.  e.g. help('listWorkspaces').

Option 2:

1. Open the EM console.
2. Navigate to the System Mean Browser (right click on capture_server1 and select from menu).
3. In the left pane, expand the tree "Application Defined MBeans".
4. Expand the folder oracle.capture.
5. Drill down to Server: capture_server1 / Application: capture / config / Config.
6. In the right pane, select the operations tab.
7. Select the desired operation.  The operation page will be displayed.
8. On the Operation pages, supply (if needed) the parameters and click "Invoke".

For the list of the commands, check the link below:
http://docs.oracle.com/cd/E29542_01/doc.1111/e37898/advd_functions.htm

Batch Content to Later Show as EBS Managed Attachments for Certain Business Entities

SCENARIO: You have numerous content items that you need to batch/bulk load into Universal Content Management (UCM) without using the EBS interface, and those items need to be tied/related to certain EBS entities.

Below is an example of using UCM IdcCommand to batch/bulkload the content items:

1. Gain a better understanding of what the EBS Managed Attachments code sends to UCM for a "New" check-in via enabling verbose system audit trace section "requestaudit" and adding an attachment to a specific business entity via the Managed Attachments EBS Zoom link. Example parameters sent to UCM are below:

requestaudit/6 10.26 17:09:44.854 IdcServer-7165:

CHECKIN_NEW [dID=8512][dDocName=UCM008514][dDocTitle=test][dUser=sysadmin][dSecurityGroup=AFDocuments][QueryText=dAFBusinessObjectType<matches>`PER_PEOPLE_F` <AND> dAFBusinessObject<matches>`6429` <AND> dAFApplication<matches>`EBS_instanceA`][xCollectionID=0][StatusCode=0][StatusMessage=Successfully checked in content item 'UCM008514'.] 0.16578499972820282(secs)

2. Using the values from the example UCM trace above, you can create a serialized hda file to use with IdcCommand. For your environment, you will need to change the values to meet your needs/trace results.

Example IdcCommand file name = <ucm install root>/bin/EBSCheckin.hda

<?hda version="10.1.3.3.2 (071031)" jcharset=UTF8 encoding=utf-8?>
doFileCopy=1
IdcService=CHECKIN_NEW
dSecurityGroup=AFDocuments
dDocType=EBSAttachment
dDocTitle=test
dDocAuthor=sysadmin
dDocAccount=
dRevLabel=1
dInDate=12/15/2010
dAFApplication=EBS_instanceA
dAFBusinessObjectType=PER_PEOPLE_F
dAFBusinessObject=6429
primaryFile=/home/oracle/Desktop/Hello.txt


3. Run IdcCommand to batch/bulk load the content item(s) from the <ucm install root>/bin directory:

IdcCommand -u sysadmin -f EBSCheckin.hda

4. IdcCommand should output "successful".

5. Log-into that same EBS entity (a Person's record).

6. Log into UCM's prompt for the Managed Attachments Zoom for that EBS entity as the same user specified in the serialized hda as the value of  "dDocAuthor".

7. Check that the batch/bulk loaded content item(s) is available via EBS.

Enable Managed Attachments for Oracle EBS Forms don't have FND Attachments configured at form level

For EBS forms that have FND Attachments enabled at the "Form" level one can configure Managed Attachments by populating the AXF_FND_MAP table (either using the AXF_MANAGED_ATTACHMENT_DATA.sql script or manually) and additional parameters can be added by populating the AXF_MA_PARAMETERS table.

For EBS forms and/or custom forms that have FND Attachments enabled at "Form Function" level only, you will need to use an alternate approach and manually add entries to the AXF_CONFIGS / AXF_COMMANDS / AXF_COMMAND_PARAMETERS tables.

You will need to collect the following values:

• Entity (businessObjectType): the EBS entity/module (for example: AP_INVOICES)
• Primary Key (businessObjectKey1) and Data Block Object (businessObjectValue1); the forms data block and attribute that holds the primary key value for the record (for example: INV_SUM_FOLDER.INVOICE_ID)
• Formfunction name for the EBS form (for example: AP_APXINWKB)

DECLARE
my_entity VARCHAR2(255) := 'your_ebsentity'; --example: AP_INVOICES
my_formfunction VARCHAR2(255) := 'your_formfunction'; --example: AP_APXINWKB
my_datablockname VARCHAR2(255) := 'your_forms_datablock_name'; --example: INV_SUM_FOLDER
my_fieldname VARCHAR2(255) := 'your_datablock_fieldname'; --example: INVOICE_ID

v_formId AXF_CONFIGS.FORMID%TYPE;
v_eventId AXF_COMMANDS.EVENTID%TYPE;
v_solutionendpoint AXF_CONFIGS.SOLUTIONENDPOINT%TYPE;

BEGIN
select AXF_CONFIGS_SEQ.NEXTVAL into v_formId from dual;
select SOLUTIONENDPOINT into v_solutionendpoint from AXF_CONFIGS where formfunction='AXF_MANAGED_ATTACHMENTS';

Insert into AXF_CONFIGS (FORMID,FORMFUNCTION,SOLUTIONENDPOINT,ENTITYNAME,LOGENABLED,DATABLOCKNAME,CREATED_BY,CREATION_DATE,LAST_UPDATE_DATE,LAST_UPDATED_BY,LAST_UPDATE_LOGIN) values (v_formId,my_formfunction,v_solutionendpoint,null,'YES','AXF_DEFAULT',0,sysdate,sysdate,0,0);

select AXF_COMMANDS_SEQ.NEXTVAL into v_eventId from dual;
Insert into AXF_COMMANDS (EVENTID,FORMID,EVENTNAME,DISPLAYMENU,COMMANDNAMESPACE,REQUIRESCONVERSATION,SORTBY,SOLUTIONNAMESPACE,MENUTYPE,SPECIAL,RESPONSIBILITY,CREATED_BY,CREATION_DATE,LAST_UPDATE_DATE,LAST_UPDATED_BY,LAST_UPDATE_LOGIN) values (v_eventId,v_formId,'ZOOM','Managed Attachments','UCM_Managed_Attachments','NO',3,'UCM_Managed_Attachments','ZOOM',null,null,0,sysdate,sysdate,0,0);

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,'application','CONSTANT',null,null,'EBS_instanceA',0,sysdate,sysdate,0,0);

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,'businessObjectType','CONSTANT',null,null,my_entity,0,sysdate,sysdate,0,0);

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,'businessObjectKey1','CONSTANT',null,null,my_datablockname||'.'||my_fieldname,0,sysdate,sysdate,0,0);

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,'businessObjectValue1','DATA',my_datablockname,my_fieldname,null,0,sysdate,sysdate,0,0);

END;
/

The following screenshot displays the entries for transactions in Receivables.