Table of Contents

Search

  1. Preface
  2. Introduction to Cloud Integration Hub
  3. Hub administration
  4. Project and Asset Management
  5. Applications
  6. Topics
  7. Data Integration tasks
  8. Publications
  9. Subscriptions
  10. Tracking and monitoring
  11. Cloud Integration Hub REST APIs
  12. Glossary

Cloud Integration Hub

Cloud Integration Hub

Set up a private publication repository

Set up a private publication repository

You can set up a private publication repository to store topic data on-premises or on your organization's private cloud. If you use a private publication repository, verify the following requirements:
Database
A private publication repository must reside on an Oracle, Microsoft SQL Server, or MySQL database. The repository must be accessible through the
Informatica Intelligent Cloud Services
Secure Agent. To optimize performance, set up the Secure Agent and the private repository on the same machine.
If the private repository resides on a MySQL database, and the MySQL server and the Secure Agent use different time zones, add the property
serverTimezone
to the connection string to define a common time zone.
For example, configure the connection string as follows:
jdbc:mysql://<HOST_NAME>:<port>/<DB_NAME>?serverTimezone=<AGENT_TIMEZONE>
where <AGENT_TIMEZONE> is the time zone of the node where the Secure Agent is installed.
Database user account
Verify that you have the user name and password for the required database user account that you create. The database user account must have privileges to perform the following actions:
  • Select data from tables and views.
  • Insert data into tables, delete data from tables, and update data in tables.
  • Create, change, and delete the following elements:
    • Tables
    • Views
    • Synonyms
    • Indexes
    • Custom data types
    • Triggers
  • Create, change, delete, and run stored procedures and functions.
If you use a Microsoft SQL Server database, consider granting database owner privileges to the database user account.
Language support
To support UTF-8 character encoding on Oracle Database, configure the database to use the following character set: <
AMERICAN_AMERICA.AL32UTF8
>.
Configure the following operating system settings of the Secure Agent machine:
  • Linux. Set the character set to
    EN_US.UTF8
  • Windows. Set the language to English (United States).