Skip navigation

In the post Cloud Components: Making marketers more productive, I introduced Cloud Components and how they are used in Eloqua landing pages. 

 

So, what exactly is involved in building a Cloud Component?  I'm glad you asked!

 

The first step is developing and hosting a Cloud Component Provider that:

  • Is developed in the language of your choice, and hosted in the *Cloud*, external to the Eloqua application.
  • Contains one or more Cloud Components that can be used on Eloqua Landing Pages.
  • Exposes a set of service Endpoints for each component, which the Eloqua Cloud Components Framework will call out to. 
  • Publishes a Service Definition, in JSON format, that will be used to register the Provider within Eloqua.


CCPframework.png

Details on the structure of a Cloud Component Provider can be found in the following posts:

  1. Building Cloud Components: The Endpoints
  2. Building Cloud Components: The Service Definition

 

Now that we've described the things from a high-level, check out Building Cloud Components:  Hello World, My First Provider to get more technical.

When using the Eloqua SOAP API with an E10 instance, there are a few things to keep in mind.  While much of the functionality continues to work without issue, there are a few areas that warrant clarification.

 

The following table lists each Eloqua WSDL, along with details and limitations when used with E10.

 

 

WSDLUsage with E10
EloquaService

Functions work the same in E10, with the exception of Prospects. (Prospects do not exist in E10, and therefore cannot be manipulated through the SOAP API)

 

Note: the names and locations of certain features differ between E9 and E10.  For example, a Contact Group is  called a Contact List in E10.  The SOAP API still uses the E9 naming conventions.

EloquaDataTransferService

The Data Transfer Service is not supported in E10.  Although the ability to Import and Export data does exist in E10, the UI for configuring the type of Import or Export that can be accessed through the DTS does not.

Note: Customers who have set up Imports and Exports in E9, then update to E10, can still access these through the DTS.

 

For E9 or E10, use the new RESTful Bulk API that will offer this functionality and more.

Eloqua Bulk API 1.0: Importing and Exporting Data

EloquaEmailService

The E-mail Service WSDL is not supported with E10.

 

For E10, you can now use the RESTful API that will offer this functionality.

See the Email section under RESTful API HERE for examples of usage.

ExternalActionService

The External Action Service API (also known as the Cloud Connector API) continues to function in E10.

 

See Using Cloud Connectors with E10 for additional details.

TJ Fields-Oracle

Eloqua SDK

Posted by TJ Fields-Oracle Jan 3, 2012

In working with developers wanting to integrate with Eloqua, I am often asked if there is an official Eloqua SDK.

 

While there is not an official implementation of a SDK, we do have an ever-growing set of resources to assist in developing on the Eloqua platform.

 

There is a guide located here Building On The Eloqua Platform - A Resource Guide which contains links to code samples, How-Tos, and other useful information.  As more resources become available, they will be added to the guide.

 

There is also a newly developed Eloqua PHP Client, that should help those using PHP, and the Eloqua SOAP API documentation can be found here.

 

Also, the Topliners community in general is a great resource for developers.  In the Eloqua API group for example, there are many valuable discussions about API development issues and best practices.