Integrating the Agent with Content Management Systems

The general agent can integrate SAS Customer Intelligence 360 with a third-party CMS. This type of integration enables the selection of one or more HTML assets from a third-party CMS and adds them as creatives in SAS Customer Intelligence 360.

The cms_configuration.json file in the doc folder of the agent has five attributes:

• id
• local_cms
• name
• className
• supportSearch
• supportFolders

Modify the code as necessary:

1. For multiple systems, give each system a unique name.
2. Set the supportSearch property to true to enable users to search the CMS within SAS Customer Intelligence 360.
3. Set the supportFolders property to true enables the folder structure of the CMS to be viewed within SAS Customer Intelligence 360.

   Here is some example code:

   { "id":"aem", "name":"AEM Content Management System", "className":"AEMCmsProcessor", "supportSearch":false, "supportFolders":true }

   {
     "id":"aem", 
     "name":"AEM Content Management System",
     "className":"AEMCmsProcessor",
     "supportSearch":false,
     "supportFolders":true
   }

4. After modifying the code, save and move the file to the config folder.
5. Restart the agent. The general agent uploads the CMS to SAS Customer Intelligence 360 and the CMS content becomes available.

If you want to use your own CMS, you must get your data from that CMS to the system and then convert the data to a SAS format. The LocalCMSProcessor.java file is included in the doc folder of the general agent. You can use this file as a template to create your own file.

Here is an example SAS format file:

id: null, 
path: null, name: "bear",
lastModifiedDate: null, 
action: null,
originalURL: "<data
                data-context-url="http://cmsURL/mycms/content/bear.html">/data",
width: 440,
height: 400,
size: 0, 
type: null,
thumbnailURL: "http://cmsURL/mycms/images/thumbnail/bear.jpg",
previewURL:"http://cmsURL/mycms/images/preview/bear.jpg", 
folder: false

Compile the file and add it to the JAR file in the libThirdParty folder.