Cloud Integration Hub

Back Next

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.
When you use a private publication repository,
Cloud Integration Hub
doesn't encrypt data. For more information about publication repository functionality, see Hosted and private publication repositories.

If the private repository resides on a MySQL database, and the MySQL server and the Secure Agent use different time zones, add the property
connectionTimeZone
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>?connectionTimezone=<AGENT_TIMEZONE>

where <AGENT_TIMEZONE> is the time zone of the node where the Secure Agent is installed.

The following table lists the databases that you can use to set up a private publication repository:

Database
Versions
Edition
System

Oracle
19c, 18c, 12cR2, 12c
Enterprise
64-bit

Microsoft SQL Server
2019, 2017, Azure SQL Database
Enterprise
-

MySQL
5.7
-
InnoDB
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: You can enable UTF-8 character encoding on Oracle Database. Configure the database to use the character set <
AMERICAN_AMERICA.AL32UTF8
>.
If you use a Linux operating system on the Secure Agent machine, configure it to use the character set <
EN_US.UTF8
>.