For connecting to HCP

This data connection uses HCP's RESTful HTTP protocol to read and write data to an HCP namespace or folder within a namespace.

For HCP namespaces that have versioning enabled, this data connection reads only the latest version of each object.

This data connection is best suited for use with:

• Small namespaces.
• Namespaces whose contents never or rarely change.
• Namespaces that you intend to read only one time.
• Namespaces that have versioning disabled or namespaces for which you are interested in reading only the latest version of each object.

You need to include every document in the database when using this data connection in order to track changes. This leads to extra database usage and impacts performance when re-crawling.

For more information on this connector, see HCP (Hitachi Content Platform) data connection.

Parent Topic

• For connecting to HCP

This data connection uses HCP's metadata query engine (MQE) to ask HCP for lists of changed files. This data connection is better suited than the regular HCP data connection for use with very large namespaces or namespaces whose contents change regularly.

This data connection also lets you read data from an entire HCP tenant or system, which the regular HCP data connection does not.

For HCP namespaces that have versioning enabled, this data connection reads all versions of an HCP object. However, only the latest version of each object can be indexed.

For more information, see HCP MQE (Hitachi Content Platform Metadata Query Engine) data connection

Parent Topic

• For connecting to HCP

Use this data connection to connect to an HCP system using the Hitachi API for Amazon S3 protocol. This data connection is especially useful for migrating data from Amazon S3 to HCP.

For more information:

• On this data connection, see S3 Compatible data connection.
• On migrating data from Amazon S3 to HCP, see Copying data from Amazon S3 to HCP.

Parent Topic

• For connecting to HCP