25 Administering Eloqua Cloud Marketing Service in WebCenter Sites

WebCenter Sites can use Eloqua visitor profile data to target specific content to the visitor by personalizing their visit to all those pages where they navigate around on your website. By sharing both content and visitor profile data across Eloqua and WebCenter Sites, the visitor gets a consistent personalized experience that leads to higher conversions. Read further to find out how you can integrate the Eloqua Cloud Marketing Service (Eloqua) with Oracle WebCenter Sites.

25.1 Eloqua Integration Overview

Integrating Eloqua with WebCenter Sites provides marketers with the ability to converge the visitor's online experience with their marketing campaigns, as well as more effectively manage the visitor journey. The integration promotes content reuse and streamlines content targeting across channels.

This is achieved through the following functionality enabled by the integration:
  • Embedding WebCenter Sites content into Eloqua forms and landing pages. Drag-and-drop placement of existing WebCenter Sites content ensures consistency of the marketing message and a seamless visitor experience across channels. Specific content can be targeted at specific visitors or campaign contacts.

  • Embedding Eloqua forms into WebCenter Sites pages. Drag-and-drop placement of Eloqua forms into WebCenter Sites pages eliminates the involvement of the site administrator or developer in the lead generation process.

Existing visitor segment and contact data can be automatically passed from Eloqua to WebCenter Sites for targeted content delivery.

25.2 Configuring Eloqua Instances in WebCenter Sites

You can configure multiple Eloqua instances with WebCenter Sites. You can use these instances for different business units of your organization. Different business units of an organisation may have their own subscriptions with Eloqua that can be used with the sites they own in WebCenter Sites. With the ability to configure multiple Eloqua instances with WebCenter Sites, it's possible for the business units to use their Eloqua subscription with their sites alone.

To add an Eloqua instance:
  1. In the General Admin tree, expand the External Integrations node, expand the Configurations node, and then double-click Add New.
  2. In the New Configuration form, enter the Name of the new Eloqua instance that you want to configure, select the Type as ELOQUA, and then click Continue.
  3. In the Configuration form, enter eloqua.companyname, eloqua.username, eloqua.password, eloqua.loginurl, eloqua.baseurl, and eloqua.apiprefix.


    • The login parameters eloqua.companyname, eloqua.username, and eloqua.password are the ones that you use to log in to the Eloqua website.

    • In the field eloqua.loginurl, enter the login URL of the Eloqua website and in the field eloqua.baseurl, you can enter the URL that you get after logging into the Eloqua website.

    • The value of eloqua.apiprefix field should always be /API/REST/2.0.

  4. Click Save.
Your Eloqua instance is configured with WebCenter Sites and you can find it listed under the EloquaForm node in the Content Tree tab of the Contributor interface.

25.3 Accessing WebCenter Sites Content in Eloqua

To embed WebCenter Sites content in Eloqua e-mails and landing pages, you need to configure your Eloqua instance with the WebCenter Sites content service, ensure that only the authorized Eloqua instance can access content within the target WebCenter Sites instance, and determine which WebCenter Sites asset types and associated templates are available to Eloqua marketers.

See these topics:

25.3.1 Configuring Eloqua for Access to the WebCenter Sites Content Service

Before marketers can embed existing WebCenter Sites content into Eloqua e-mails and landing pages, you must configure your Eloqua instance to communicate with the WebCenter Sites content service. The example URLs below assume the default servlet path of /cs/ContentServer - adjust your URLs as appropriate for your environment. Also, if you have not already done so, create a new provider in Eloqua to separate the WebCenter Sites content service from other services and applications.


Your WebCenter Sites instance must be configured to accept HTTPS connections. Only ports 443 and 8443 are supported. All URLs, property names, and their values are case-sensitive.

To configure Eloqua for accessing the WebCenter Sites Content Service, you must do the following:
  1. Log into the target Eloqua site as its administrator.
  2. In the top bar, click Settings and select AppCloud Developer.
  3. Click Create New App and fill in the form that appears as follows:


    If you have created an Eloqua instance in the WebCenter Sites with the name My_Eloqua, the value of the eloquaname parameter will be My_Eloqua.

    Table 25-1 Create New App Fields

    Field Value
    Icon URL https://wcs-instance.company.com/cs/images/eloqua/AppIcon.png
    Enable URL https://wcs-instance.company.com/cs/ContentServer?pagename= EloquaIntegration/Enable&eloquaname=My_Eloqua&installId={InstallId}&appId={AppId}& callbackUrl={CallbackUrl}
    Status URL https://wcs-instance.company.com/cs/ContentServer?pagename= EloquaIntegration/SitesStatus
    Callback URL https://wcs-instance.company.com/cs/ContentServer?pagename= EloquaIntegration/Enable&eloquaname=My_Eloqua
  4. Click Save App to save your changes.
  5. In the App Details page that appears, click Show Secret in the OAuth section, copy the client secret value displayed in the pop-up, and save it to a text file. The client secret value of the application should be mapped to the Eloqua instance in the WebCenter Sites (you need this value to configure the authentication of Eloqua requests within WebCenter Sites later in this guide).
  6. In the Services section, click Add Service and then click Content in the pop-up that appears.
  7. Fill in the fields in the Content Service Details form as follows:

    Table 25-2 Content Service Details Fields

    Field Value
    Icon URL https://wcs-instance.company.com/cs/images/eloqua/ ContentServiceIcon.png
    Create URL https://wcs-instance.company.com/cs/ContentServer?pagename= EloquaIntegration/Instances/Add&eloquaname=My_Eloqua&instanceId={InstanceId}
    Configure URL https://wcs-instance.company.com/cs/ContentServer?pagename= EloquaIntegration/ContentSearch&eloquaname=My_Eloqua&instanceId={InstanceId}& installId={InstallId}
    Delete URL https://wcs-instance.company.com/cs/ContentServer?pagename= EloquaIntegration/Instances/Delete&eloquaname=My_Eloqua&instanceId={InstanceId}
    Copy URL https://wcs-instance.company.com/cs/ContentServer?pagename= EloquaIntegration/Instances/Copy&eloquaname=My_Eloqua&instanceId={InstanceId}& originalInstanceId={OriginalInstanceId}


    Flow layout mode allows the embedded content to be dynamically resized.


    The maximum number of rendered assets passed from WebCenter Sites to Eloqua in a single call. Oracle recommends a value below 5000; however, if you experience issues with passing very large pieces of content, lower this value. For more information, consult Eloqua documentation.



    Landing Page

    Notification URL

    (Optional) To make WebCenter Sites content available in Eloqua landing pages:

    https://wcs-instance.company.com/cs/ContentServer?pagename= EloquaIntegration/Processor/LandingPageNotification&eloquaname=My_Eloqua&instanceId= {InstanceId}&installId={InstallId}&executionId={ExecutionId}

    E-mail Page

    Notification URL

    (Optional) To make WebCenter Sites content available in Eloqua e-mails:

    https://wcs-instance.company.com/cs/ContentServer?pagename= EloquaIntegration/Processor/EmailNotification&eloquaname=My_Eloqua&instanceId= {InstanceId}

    Fill in the remaining fields as appropriate for your environment, then click Save to commit your changes.
  8. Save your changes and return to the WebCenter Sites content service properties page.
  9. Click the link in the Catalog section to add the WebCenter Sites content service to your cloud service catalog. When prompted, click Accept.
  10. Install the WebCenter Sites cloud service into your Eloqua instance.
    This makes it available within the Eloqua marketer interface for the target Eloqua instance only.
    1. In the Eloqua interface, click Settings, and then select Setup.
    2. Click AppCloud Catalog.
    3. Select the Catalog tab to display the list of available (but not installed) services.
    4. Locate your target application and click Install.


    To maintain security within your Eloqua instance, do not publish the WebCenter Sites content service.

25.3.2 Configuring OAuth Authentication

Secure HTTP calls from Eloqua to the WebCenter Sites content service are authenticated via OAuth 1.0 to ensure that only the authorized Eloqua instance can access content within the target WebCenter Sites instance.

To facilitate this authentication process, you must provide the Eloqua client secret value to the WebCenter Sites content service as follows:
  1. Open the Property Management Tool and in the Search by section, do one of the following:
    • In the Name field, enter the name of the property you want to modify.
    • In the Category drop-down menu, select EloquaIntegration.
  2. Click Search.
  3. In the Key column, select the name of the property.
  4. In the Value field, enter the new value.
  5. Click Save.
  6. Repeat steps 2 through 6 for all the properties you want to change.
  7. Stop and restart the application server to apply the changes.

25.3.3 Making WebCenter Sites Assets Available within Eloqua

You need to decide which WebCenter Sites asset types and associated templates should be available to Eloqua marketers. Rendering templates must be created specifically for rendering WebCenter Sites content within Eloqua e-mails and landing pages according to the best practices listed in the next section.

25.4 Registering the Eloqua Firehose Service

The Eloqua Firehose service notifies you whenever a form that has been embedded into a WebCenter Sites page has been deleted from Eloqua. This minimizes the chance of delivering pages that are missing content.

  1. Log in to the target Eloqua instance as the administrator.
  2. In the top bar, click Settings, and then select AppCloud Developer.
  3. In the list of services, click the WebCenter Sites content service you have created.
  4. In the Services section click Add Service, and then select Firehose from the pop-up dialog.
  5. In the form that appears, fill in the fields as follows:
    Field Value

    Icon URL



    WebCenter Sites Firehose


    WebCenter Sites Firehose Notification Service



    Notification URL

    https://wcs-instance.company.com/cs/ContentServer?pagename= EloquaIntegration/Processor/FirehoseNotification

  6. Click Save to store your changes.
  7. Add the following line to the protectedPageslist in the web.xml file on your WebCenter Sites instance:
Once an Eloqua form has been embedded into a WebCenter Sites page, a rendered copy of that page, including the Eloqua form, is stored in the WebCenter Sites cache. If an Eloqua marketer deletes the embedded form within Eloqua, that cached page copy is no longer valid.

When notified by the Firehose service, the WebCenter Sites contributor responsible for the affected page must manually remove the deleted Eloqua form from the page and republish it; otherwise, the page is delivered to the visitor's browser incomplete.

25.5 Creating the Rendering Template for the EloquaForm Assets

To create the template that renders the EloquaForm proxy assets within WebCenter Sites pages, do the following:

  1. Log in to the Admin interface on target WebCenter Sites site as the administrator.
  2. Create a new template with the following parameters:
    Field Value



    For AssetType



    Element is used within an HTML page

    Create Template Element


    Element Logic

    paste the contents of the EloquaForm/Detail.jsp element


    If you upgrade from release to Bundle patch 2, update the Element Logic of the existing EloquaForm Assets with the updated code of the EloquaForm/Detail.jsp element file. This will ensure accurate rendering of the templates in the Web mode.
  3. Save the new template.