As a user of an ETL tool I can send bulk upload requests to Web Content

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: 6.2.0 CE M2
• Fix Version/s: 6.2.0 CE M4
• Component/s: WCM, WCM > Web Content Administration
• Labels:
  • JSON
  • QA-PORTAL
  • WebContent
• Epic/Theme:
  • LPRE
• Similar Issues: Show 4 results ; ;

  LPS-31952	As a user of an ETL tool I can send bulk upload requests to Documents & Media
  LPS-29936	As a web content publisher, I can publish the latest approved version of web content without sending previous approved versions
  LPS-25794	As content administrator I can manage web contents in folders
  LPS-25352	I can not preview the content in web content.

The goal of this requirement is to provide out of the box integration with an ETL (Extract-Transform-Load) tool to simplify the process of bulk uploading to Liferay. An ETL tool allows extracting data from a source, transforming it as needed and load it into a target system.

Some example Open Source ETL tools are:

• Talend: http://uk.talend.com/index.php
• Penhaho Kettle: http://kettle.pentaho.com/

In order to remain tool agnostic, Liferay will be modified to allow an standard way to input bulk data. In particular Liferay will provide a web service URL for each of the items that are allowed to be bulk uploaded. The ETL tool will just have to make a POST HTTP Request to that URL with an specifically formatted body with the data to be imported. It is common for ETL tools to support this type of operation out of the box, so no specific extensions for Liferay will be necessary.

Liferay will provide a URL to which the ETL tool will be able to send a body with JSON format to specify all the fields for the web content. All valid metadata for the content will be allowed, included the generic information (title, description, tags, ...) as well as the web content structure and any fields specific to that structure. If the Web Content structure has image fields, the actual image files will be attached by making the request a multi-part request which allows attaching the files. Only one web content can be imported per request.

[Juan Fernández]

There's nothing to test here. No changes were done in the product

[Lawrence Lee]

Closing as cannot be tested by QA.