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, MySQL database, or Aurora MySQL database. The private publication 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.
Note: 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:
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, 8.x
Enterprise
INNODB
Aurora MySQL
3
MySQL 8.0.23 Community
INNODB
You can use Aurora MySQL to set up both private and hosted repositories. You can use Oracle RDS to set up a private repository.
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>.
Recommendations for setting up MySQL 8.x and Aurora MySQL private publication repositories
Consider the following rules and guidelines when you set up a MySQL 8.x or an Aurora MySQL private publication database:
- Initialise the MySQL database with the lower_case_table_names configuration set to 1.
- Use the utf8mb3 character set.
Bypass the Publication Repository Service in a private publication repository
If you use a private publication repository, you can configure Cloud Integration Hub to bypass the Publication Repository Service (PRS) to improve system performance.
When you use a private publication repository, by default, Cloud Integration Hub writes published data to the publication repository and reads data from the publication repository through the PRS.
To configure Cloud Integration Hub to bypass the PRS in publication and subscription flows, select Use JDBC for Private Publication Repository in the Cloud Integration Hub connection. In the Repository Schema field of the Organization Cloud Setup dialog box, you can enter either a custom repository schema name or the default repository schema name to connect to the repository.
Changing the port number of the publication repository service
When you select to use a private publication repository, Cloud Integration Hub communicates with the repository via the publication repository service on the Secure Agent.
By default, the port number of the publication repository service is 19443. You can change the port number.
1In Administrator, select Runtime Environments, and then, on the Runtime Environments page, click the name of the Secure Agent that Cloud Integration Hub uses at run time.
Note: You might have to expand the Secure Agent group to see the list of Secure Agents within the group.
2On the Details tab, in the upper right corner, click Edit.
3In the System Configuration Details area, select CIH Processor.
4Click the Edit Agent Configuration icon next to api-port and enter the port number.
5Click Save.
Using a customized Java KeyStore with a private publication repository
When you select to use a private publication repository, Cloud Integration Hub assigns a default Java KeyStore (JKS) as the repository of security certificates.
You can assign a different keystore to use with the publication repository.
1Place the customized keystore in the following location:
2In Administrator, select Runtime Environments, and then, on the Runtime Environments page, click the name of the Secure Agent that Cloud Integration Hub uses at run time.
Note: You might have to expand the Secure Agent group to see the list of Secure Agents within the group.
3On the Details tab, in the upper right corner, click Edit.
4In the System Configuration Details area, select CIH Processor.
5Click the Edit Agent Configuration icon next to keystore-filename and enter the name of the keystore.
6Click the Edit Agent Configuration icon next to keystore-password and enter the password to the keystore.