Table of Contents

Search

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

Cloud Integration Hub

Cloud Integration Hub

Setting up the organization in Informatica Cloud Integration Hub

Setting up the organization in Informatica Cloud Integration Hub

Set up the organization in
Cloud Integration Hub
to create and manage Cloud Integration Hub assets. You must define the settings required by the organization.
  1. Access
    Cloud Integration Hub
    and accept the license agreement.
    The
    Organization Cloud Setup
    dialog box appears.
  2. Define the following settings:
    Property
    Description
    Organization Name
    Name of the organization in
    Informatica Intelligent Cloud Services
    . Appears in view only mode.
    Organization ID
    ID of the organization in
    Informatica Intelligent Cloud Services
    . Appears in view only mode.
    Informatica Cloud User
    Name of the
    Informatica Intelligent Cloud Services
    user to use at run time. The user must have an Admin user role in
    Informatica Intelligent Cloud Services
    . The user must also have Update and Execute permissions for the Data Integration assets associated with publications and subscriptions.
    Informatica Cloud Password
    Password for the
    Informatica Intelligent Cloud Services
    user to use at run time.
    Runtime Environment
    Informatica Intelligent Cloud Services
    Secure Agent runtime environment to use at run time.
    Rotate Key
    Click
    Rotate Key
    to rotate the encryption key used for data encryption.
  3. To use a private publication repository, define the following settings:
    Property
    Description
    Repository Type
    Select
    Private
    .
    Repository Database Type
    Choose Oracle, Microsoft SQL Server, or a MySQL database. If you use an SQL Server database, the collation is case-insensitive.
    Repository URL
    JDBC URL of the repository, based on the database type:
    • Oracle:
      jdbc:informatica:oracle://<ip>:<port>;sid=<sid>;
    • Microsoft SQL Server:
      jdbc:informatica:sqlserver://<ip>:<port>; DatabaseName=<DatabaseName>;
    • MySQL:
      jdbc:mysql://<ip>:<port>/<DatabaseName>;
    To prevent failure while establishing a connection to the proxy service, add the following string to the repository URL:
    useSystemProxyOptions=false;
    User
    Name of the user to access the repository.
    User Role
    Role granted to the user to access the repository, based on the database type:
    • On an Oracle database, the user must be granted
      CONNECT
      and
      RESOURCE
      roles.
    • On a Microsoft SQL Server database, the user must be granted
      db_datareader
      ,
      db_datawriter
      , and
      db_ddladmin
      roles.
    Password
    Password of the user.
    Repository Schema
    Schema used with the repository. For more information, see Bypass the Publication Repository Service in a private publication repository.
  4. Optionally, define the following file store publication repository settings:
    Property
    Description
    Enable File Store
    If you use an on-premises Secure Agent, select to enable the hub to store published files as-is in a file store publication repository.
    File Store Repository Location
    File directory path of the file store publication repository. The Informatica Cloud Secure Agent must be able to access the location.
  5. Click
    Save
    .

0 COMMENTS

We’d like to hear from you!