56 Publishing

This chapter contains information about publishing to WebCenter Sites from file systems and Microsoft SharePoint systems.

This chapter contains the following sections:

56.1 Overview

Once the source system schema is mapped to WebCenter Sites, any object that is based on the schema can be published to WebCenter Sites.

This section contains the following topics:

56.1.1 Synchronization

Manual publishing is unnecessary after the initial session, because the synchronization engine takes over. The engine monitors published folders (on the source system) and mirrors the changes it detects:

  • Modification to published objects

  • Deletion of published objects

  • Addition of objects to the monitored folder(s), as long as their object types are mapped

  • Attributes require special treatment, as explained in Chapter 58, "Remapping,"

The synchronization interval can be configured in the publish command (see Section 56.2, "Publishing to WebCenter Sites").

Event notification for the synchronization process can be enabled by installing CIP-related default workflows, or specially creating custom workflows. For more information, see Chapter 57, "Configuring Event Notification."

56.1.2 Unpublishing

The unpublish command is used to clear catalog.xml of all entries that are associated with published objects. Including the -delete parameter removes the same entries from the WebCenter Sites database. For more information, see Section 56.6, "Unpublish Command."

56.2 Publishing to WebCenter Sites

If the source system schema is mapped to WebCenter Sites, you can successfully publish objects that are based on the schema. (Otherwise, you will need to remap the schema. Instructions are available in Chapter 58, "Remapping").

To publish to WebCenter Sites

  1. Make sure Content Integration Agent is running.

    Note:

    If you changed the port in the section "Restart the Content Integration Agent Executable" in the Oracle Fusion Middleware WebCenter Sites Installation Guide, make sure that the new port is set in facilities.xml , and add -p <port> to the command in the following step (which starts CIPCommander).

  2. Run the CIPCommander executable (located in the bin folder of the system where Content Integration Agent is installed):

    cipcommander
publish <source_providerid> <target_providerid>
-source_repname <source_repname>
-source_path <source_path>
-target_repname <target_repname>
-mapping <mapping_id>
-replic_mode <full | ingestion>
-bulk_resynch_interval <seconds>

    where:

    • <source_providerid> is the provider ID for the source system:

      File System:

      2023b849-688e-4009-af1f-903fe62d85b7

      Microsoft SharePoint:

      7137dd5d-9ed7-4327-b4fd-8caeebd5889a

    • <target_providerid> is the WebCenter Sites provider ID:

      70b1e307-26a1-499c-9295-cf0b6bd01342

    Parameters and values for the publish command are defined in Table 56-1, "Publishing Parameters". Examples on the usage of the publish command are available in Section 56.3, "Examples." Information about an object's publication data is available in Section 56.4, "When an Object is Published."

    Table 56-1 Publishing Parameters

    Publishing Parameter Value

    -source_repname

    <source_repname> : Name of the source repository from which content will be published. Enter the name exactly as it appears in the URL.

    Legal values:

    File System: Empty string ("" ).

    SharePoint: Name of the document library or picture library that contains the folder to be published.

    Examples: See Section 56.3, "Examples."

    -source_path

    <source_path>: Path to the object you want to publish.

    Legal values:

    File System: /<folder>/<folder>/ .../<folder>/(to publish the last folder in the path)

    SharePoint: / (to publish a library [document or picture] and its contents)

    /<folder>/<folder> .../<folder>/(to publish the last folder in the path)

    -target_repname

    <target_repname>: Name of the content management site (in WebCenter Sites) in which the flex family is enabled for this source system.

    -mapping

    <mapping_id> : Value of the mapping id in mappings.xml . If you are using the default mappings.xml , enter one of the following values:

    • sharepoint2cs

    • filesystem2cs

    -replic_mode

    full | ingestion

    • full means that a full replication will be performed (by default).

    • ingestion means that only item creation events will be propagated. Modifications and deletions on the source side will not be reflected on the target.

    -bulk_resynch_interval

    <seconds>: Number of seconds between two successive synchronization events.

    An optional publishing parameter. For more information, see Section 56.5, "Synchronization."

56.3 Examples

This section contains the following topics:

56.3.1 Publishing from a File System

To publish the C:\publish folder to the CIPDemo content management site, using filesystem2cs default mapping:

cipcommander publish 2023b849-688e-4009-af1f-903fe62d85b7 70b1e307-26a1-499c-9295-cf0b6bd01342
-source_repname ""
-source_path c:\publish-mapping filesystem2cs-target_repname CIPDemo

56.3.2 Publishing from Microsoft SharePoint

  • To publish the Images picture library to the CIPDemo content management site using, sharepoint2cs default mapping:

    cipcommander publish 7137dd5d-9ed7-4327-b4fd-8caeebd5889a70b1e307-26a1-499c-9295-cf0b6bd01342-source_repname Images-source_path /-mapping sharepoint2cs-target_repname CIPDemo

  • To publish the Cool/Bright folder in the Images picture library to the CIPDemo content management site, using sharepoint2cs default mapping:

    cipcommander publish 7137dd5d-9ed7-4327-b4fd-8caeebd5889a70b1e307-26a1-499c-9295-cf0b6bd01342-source_repname Images-source_path /Cool/Bright-mapping sharepoint2cs-target_repname CIPDemo

56.4 When an Object is Published

When an object is published, catalog.xml (located in integration_agent/conf/) is updated with an entry that identifies both the source system and the WebCenter Sites system (within the <workspace> tags), and specifies replication data for the published object (within the <replication> tag). The code below is an example of a publication entry for an object that was published from a file system:

<workspace id="8a55488d-97c9-4290-92e1-d7bb9e476dc7">
  <provider-ref refid="2023b849-688e-4009-af1f-903fe62d85b7" />
    <init-params>
      <param name="repname" />
      <param name="path">c:/temp/CIP_xml/test1/test3</param><param name="repid" />
  </init-params>
</workspace>
<workspace id="f917ddcb-1cbb-46c5-8840-fb194b693629">
  <provider-ref refid="70b1e307-26a1-499c-9295-cf0b6bd01342" />
    <init-params>
      <param name="repname">CIPTest</param>
      <param name="repid">39e1e988-f1a6-4913-a16d-45a1c5ad9976</param>
    </init-params>
</workspace>
<replication>
  <link id="04e4f0f2-8535-492b-8590-691a510884d4">
  <source-ref refid="8a55488d-97c9-4290-92e1-d7bb9e476dc7" />
  <target-ref refid="f917ddcb-1cbb-46c5-8840-fb194b693629" />
  <mapping-ref refid="filesystem2cs" />
    <init-params>
      <param name="BulkResynchInterval">600</param>
      <param name="ReplicMode">full</param>
    </init-params></link>
</replication>

56.5 Synchronization

Once objects are published, the synchronization engine monitors the status of the folder(s) from which the objects were published and mirrors the changes it detects. For optimal performance, set the synchronization interval to a value that agrees with the frequency of updates to the source system. To set the synchronization interval, include the bulk_resynch_interval parameter in the publish command (Section 56.2, "Publishing to WebCenter Sites").

56.6 Unpublish Command

You can unpublish objects from catalog.xml alone (and additionally, from WebCenter Sites) by executing the cipcommander unpublish command with parameters that suit your requirements.

Note:

The unpublish command clears catalog.xml of all entries that are associated with published objects (for a sample publication entry, see the code in Section 56.4, "When an Object is Published"). To remove the same entries from the WebCenter Sites database, you must include the -delete parameter.

The unpublish command takes the following form and parameters:

cipcommander unpublish <parameters>

Table 56-2 Unpublish Parameters

Unpublish Parameter Description

-all

Use this parameter to clear catalog.xml of all publication entries.

-linkid

Use this parameter to clear catalog.xml of selected publication entries.

linkid specifies the published object's link to the WebCenter Sites system. Use the value in the published object's <link > tag, which is nested within the object's <replication> tag (for sample code, see Section 56.4, "When an Object is Published.")

For example:To unpublish a single object from catalog.xml, obtain its <linkid> and issue the following command:

cipcommander unpublish linkid 04e4f0f2-8535-492b-8590-691a510884d4

To unpublish multiple objects, add their linkid 's to the unpublish command.

-delete

Use this parameter to remove, from the WebCenter Sites database, the same objects that you are unpublishing from catalog.xml.

Legal values: <true | false>

Default value: true