27 Publishing Content from WebCenter Sites to Oracle Content and Experience

As an administrator, you can configure WebCenter Sites to reuse and publish content to Oracle Content and Experience. Once WebCenter Sites content is in Oracle Content and Experience, it can be delivered across other non-web channels such as Oracle Marketing Cloud, chatbots thereby fostering content reuse and consistent messaging.

To resuse WebCenter Sites content in Oracle Content and Experience:

1. You need to create an OCE mapping to include the asset types and sub types and then create a new destination and select the delivery type.
2. Approve the assets types and sub types that you have selected for publishing.
3. After publishing the assets into a zip file, upload it to Oracle Content and Experience.
4. Invoke a REST API to start importing asset types and dependencies to Oracle Content and Experience as content types and content items.

Content creators can reuse these assets in their website to deliver the content to multiple channels.

Topics:

• Configuring Assets Types

• Creating OCE Destination

• Approving Assets for Publishing

• Publishing Assets
• Downloading Published Assets
• Importing Published Assets to Oracle Content and Experience
• Limitations

Configuring Assets Types

Create an OCE mapping to include the asset types and sub types.

To configure assets types:

1. On the source WebCenter Sites system, log in to the Admin interface.
2. In the General Admin tree, expand the Content Cloud Admin node, expand the Export Mapping node, and double-click Configure.
3. Click the Add New OCE Mapping button.
4. Select Asset Types and Sub Types, and then click Add.

   Figure 27-1 Adding Assets and Assets Types

   
   Description of "Figure 27-1 Adding Assets and Assets Types"

Creating OCE Destination

You need to create a new OCE destination on WebCenter Sites and select the required delivery type.

To create a new destination:

1. In the General Admin tree, expand the Admin node, expand the Publishing node, and then expand the Destinations node.
2. Under the Destinations node, double-click Add New.
3. In the Add New Destination form, configure the fields on this form as follows:
   • Name: Enter a unique name for the destination.
   • Delivery Type: Select Export to OCE: Export to Oracle Content and Experience.
   • Send Email on Failure: If publishing fails and email notices to that effect are required, select the check box. Enter the recipient's email address in the Email Addresses field. (This field is available only when Send Email on Failure is selected.)
   • Verbose Output: Select this option to activate detailed error logging during the publishing process. When selected, messages in addition to error messages are written to the PubMessage table. Because additional information lengthens the publishing process, select this parameter only for troubleshooting.
   • More Arguments: This parameter is reserved for future use; no additional arguments can be specified at this time.
   • Sites: Select the sites whose assets can be approved for and published to this destination.
   • Roles (Approve for Publish): Select the roles to which you are assigning approval privileges. All users who are assigned these roles are allowed to approve assets.
   • Roles (Publish): Select the roles to which you are assigning publish privileges. All users assigned these roles can publish.
4. Click Add New Destination.

Approving Assets for Publishing

For publishing your assets, the assets and their dependencies need to be approved first. Each publishing destination has an option to approve multiple assets.

To approve a group of assets:

1. In the General Admin tree, expand the Admin node, expand the Publishing node, expand the Destinations node, and then expand the destination to approve assets for.
2. Under that destination, double-click the Approve Multiple Assets option.
3. In the Approve Assets form, from the Sample Queries list on the right, select a query. If the exact query that you require is not present, select the query that is most like the one wanted.
   WebCenter Sites creates a SQL query based on the items that you selected and displays it in the Query box.
4. (Optional) If necessary, edit the SQL query.
5. Click in the Approve in Batches of field and enter a numeric value. The default is set to 500.
6. Specify the Approve Previously Approved Assets option as follows:
   • If you want WebCenter Sites to ignore all previous approvals and approve again, select Yes. This is the option to use if previous approvals have become invalid such as a change in default templates for that destination.
   • If you want WebCenter Sites to approve only the assets that have not yet been approved, select No. This is the correct choice when you are sure that previously approved assets are still valid.
7. Click Approve for Publish.

Publishing Assets

After approving the assets, you need to publish them. The process for publishing assets for OCE destination is same as for any other destination.

To publish your approved assets:

1. In the button bar, click Publishing.
2. In the Publish Console, select your destination, for example, PublishToOCE of delivery type Export to OCE from the drop-down list and then click Select Destination.

   Review the assets that are ready to be published.

3. Click Publish. The approved assets are added to a .zip file.

   A confirmation message opens. Click OK to proceed.

   On publishing the assets, a zip file having approved assets is created.

4. On the Publish Console Active tab, you can observe that the session is running.
5. When the session completes, click the History tab to view the session summary for this session.
6. Mouse over the session information to view summary information; click Log to view the session log files.

Downloading Published Assets

Publishing to OCE destination creates a .zip file consisting of all the assets and its type. You can download the zip file on your local system.

To download published assets:

1. In the General Admin tree, expand the Content Cloud Admin node, expand the Export Mapping node, and double-click History.
2. The Oracle Content and Experience Publish History page shows the history of the published sessions.

   Figure 27-2 Publish History

   
   Description of "Figure 27-2 Publish History"
3. You can download the zip file of your destination. The zip file contains the published assets. These assets will be mapped to the content types of Oracle Content and Experience.

Importing Published Assets to Oracle Content and Experience

Importing the published assets to Oracle Content and Experience involves two steps:

• Upload the zip file to Oracle Content and Experience.
• Call a REST API to import the published asset into an asset repository.

To import published assets:

1. Log in to Oracle Content and Experience.
2. Select Documents from the left bar, and then click Upload to upload the zip file from your local system
3. After the upload, click on the zip file. In the address bar of the browser, the URL shows the Document ID.

   Figure 27-3 Document ID

   
   Description of "Figure 27-3 Document ID"
4. You need to create a new or use an existing repository to import content from WebCenter Sites. To create a repository, click Assets at the bottom of the left bar and then click Create.
   After the new repository is created, click on your repository. In the address bar of the browser, the URL shows the Repository ID.

   Figure 27-4 Repository ID

   
   Description of "Figure 27-4 Repository ID"

   Note:

   Note Document and Repository IDs because both are required to run the REST API.
5. Start the REST client to import the published assets from the zip file to Oracle Content and Experience as content types and content items. The POST request must have the following settings:
   1. Select the Authorization type as No Auth.
   2. To find the token value, enter the following URL in the address bar of your browser: https://example.com/documents/web?IdcService=GET_OAUTH_TOKEN&IsJson=true
   3. The POST command using the following URL:
      http://example.com:port/content/management/api/v1.1/content-templates/importjobs

      Note:

      The API returns the job id when you execute a POST command so that you can track the job.
   4. Enter the following key values in the Headers:

      Accept : application/json 

      X-Requested-With : XMLHttpRequest

      Content-Type : application/json

      Authorization : Bearer <token value>

   5. Enter the following code in the raw section of the Body:

      {

      "exportDocId": "<DOC_ID>",

      "repositoryId": "<REPO_ID>",

      "source" : "sites"

      }

6. When the import is successful, you can log in to Oracle Content and Experience.
7. To view the imported assets, click Assets in the middle of the left bar and select your repository from the drop-down menu. The imported assets show up as content items. They can be filtered by their type (Content Type).

   Figure 27-5 View Imported Assets

   
   Description of "Figure 27-5 View Imported Assets"

Limitations

The following are the limitations of this tool:

• Proxy assets are not published.
• Embedded assets are not published as is.
• Engage or recommendations are not published.
• All non-content assets such as Templates, CSElements, and Controllers are not published.