Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Integration Hub 10.4.1
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction to Data Integration Hub
  3. Security
  4. Events
  5. User Policies
  6. Operation Console Management
  7. System Properties
  8. Connections
  9. Connectivity to Informatica Intelligent Cloud Services
  10. Integration of Data Integration Hub with Enterprise Data Catalog
  11. Document Management
  12. Entity Management
  13. Export and Import
  14. Data Integration Hub Utilities
  15. Dashboard and Reports Management

Administrator Guide

Administrator Guide

Back Next

Repository Utility Command Syntax

Repository Utility Command Syntax

Use the repository utility syntax to define the actions that you want to perform on the
Data Integration Hub
 repository
, on the publication repository, or on the operational data store
.
The repository utility uses the following syntax: 
repoutil 
<-c|--command> command
<-t|contentType> contentType 

<-l|--url> “url” 

<-u|--user> user 
<-p|--password> password 

[--authmode mode]

[--sysadmin name] 
[--docStore docStore]
[--file file] 

[--forceDelete] 


[-Ddx.kerberos.initial.administrator]
[-Ddx.pwc.domain.gateway]
[-Ddx.kerberos.krb5.file]
[-Ddx.kerberos.console.keytab.file]
[-Ddx.kerberos.console.service.principal.name]
The following table describes the repository utility options and arguments:
Options
Argument
Description
- c
--command
command
Required. Command to run on the repository. Enter one of the following commands:
  • createContent. Initializes the repository. Use this command after you run the repository utility with the deleteContent command.
  • createSchema. Creates the tables and views in the repository.
  • deleteContent. Removes all content from the repository. If you use this command, you must run the repository utility with the createContent command before you can use the repository again.
  • deleteSchema. Deletes all tables and views in the repository.
  • disablePartitioning. Disables partitioning on the publication repository.
    The partitions state appears in the dih.staging.use.partitions.default system property.
  • enablePartitioning. Enables partitioning on the publication repository.
    Data Integration Hub
     creates a partitioning schema and a partitioning function, and manages all the tables in the publication repository within partitions. You must provide the access credentials of the
    Data Integration Hub
     repository in the command, and not the credentials of the
    Data Integration Hub
     publication repository.
    For example: 
    repoutil –c enablePartitioning –u DIH_USR –p DIH_USR –l ”jdbc:informatica:oracle://dih_rdbms:1521;SID=orcl” –t dih
    The partitions state appears in the dih.staging.use.partitions.default system property.
    When you enable or disable partitioning on the publication repository,
    Data Integration Hub
     re-generates the publication tables and erases all the publication data. The publications are no longer valid, and you must update them manually for validation.
  • loadProperties. Loads and sets
    Data Integration Hub
     system properties and event attributes in the
    Data Integration Hub
     repository.
  • migrateToISP. Switches the authentication mode to Informatica domain authentication and deletes all user information from the
    Data Integration Hub
     repository.
    For details see the section "Switching to Informatica Domain Authentication".
    You can synchronize
    Data Integration Hub
     with the Informatica security domain when you switch authentication modes. Create a
    .PROPERTIES
     file with the properties dx.authentication.groups, dx.pwc.domain.gateway, dx.pwc.user, and dx.pwc.password, and enter the file path in the
    --file
     command to load the properties from the file.
    You can also synchronize the users after you switch authentication modes on the
    Users
     page of the Operation Console.
  • migrateToISPKerberos. Switches the authentication mode to Informatica domain with Kerberos authentication. Deletes synchronized users from the
    Data Integration Hub
     repository and adds the system administrator that is defined by the command argument
    -Ddx.kerberos.initial.administrator
    .
    For details see the section "Switching to Informatica Domain with Kerberos Authentication".
  • migrateToNative. Switches the authentication mode to
    Data Integration Hub
     native authentication and deletes synchronized users from the
    Data Integration Hub
     repository.
    For details see the section "Switching to Native Authentication".
  • moveDocumentStore. Moves the document store directory to a different location. Enter the absolute file path of the location to which you want to move the document store in the
    --file
     command.
  • upgradeSchema. Upgrades the repository to the latest version.
  • verifyContents. Verifies the contents of the
    Data Integration Hub
     repository.
-t
--contentType
contentType
Required. Specifies on which repository the command runs. Specify one of the following options:
  • dih.
    Data Integration Hub
     repository.
  • dih_staging.
    Data Integration Hub
     publication repository.
  • dih_ods. Operational data store.
-l
-- url
"url"
Optional. JDBC URL for the
Data Integration Hub
 repository
or for the
Data Integration Hub
 publication repository
. You must enclose the URL in quotation marks. For example: 
repoutil -c createContent -l “jdbc:informatica:oracle://
//oracle_1:1521;SID=orcl”...
-u
--user
user
Optional. User name for the database account to use when the utility connects to the
Data Integration Hub
 repository or for the operational data store.
-p
--password
password
Optional. Password for the database account to use when the utility connects to the
Data Integration Hub
 repository or for the operational data store.
--authMode
mode
Optional for the createContent command. The argument determines the authentication mode to set. Specify one of the following options:
  • native. Native authentication.
  • isp. Informatica platform authentication.
--sysadmin
name
Required for the following commands:
  • migrateToNative
  • createContent if the --authMode parameter value is native
Creates an administrator user account that you use to log in to the Operation Console.
By default, the password for the administrator user account is the same as the user name. If --authMode has the value "isp", this option is ignored.
--docStore
docStore
Required for the moveDocumentStore command. Absolute path of the directory to which to move the document store. The directory must have the same access permissions as the current directory.
You cannot move the document store to a subdirectory of the current document store directory. For example, if current document store directory is
c:\DocStore
, you cannot move the document store to the following directory:
c:\DocStore\newstore
If the repository utility fails when you run the moveDocumentStore command, you can resume the move with the same value in the --docStore command.
On Windows operating systems, you must use forward double slashes (//) in the file path.
--file
file
Optional for the loadProperties, migrateToISPKerberos, migrateToISP, and verifyContents commands.
Enter the following file name in the command: 
<DIH_InstallationDir>/conf/dx-configuration.properties
The commands use the file to determine the connection properties of the publication repository. Each property must appear on a separate line in the following format: 
<propertyName>=<propertyValue>
--configFile
propertyFile
Optional for all the repository commands. Points to the location of the
Data Integration Hub
 configuration property file. If not specified,
Data Integration Hub
 loads the file from the following location: 
<
DIH
InstallationDir>/conf/dx-configuration.properties
--createVersion
version
Optional. If you run the createSchema command, you can use this option to specify the version of the product for which to create the repository. The product version consists of numbers separated by periods. For example:
9.6.0
. By default, the product version is set to the latest version.
--forceDelete
Optional for the deleteSchema command. Deletes the repository schema regardless of errors. By default, the deleteSchema command does not delete the repository schema if it encounters errors.
-Ddx.kerberos.initial.administrator
user
Required for the migrateToISPKerberos command. Kerberos user that exists in the Informatica security domain, in the following format: 
<username>@<SECURITY_DOMAIN>
You must enter
<SECURITY_DOMAIN>
 in uppercase letters. For example: 
Administrator@DEVELOPMENT.COM
-Ddx.pwc.domain.gateway
host
Required for the migrateToISPKerberos command. Gateway machine to the Informatica domain. For example: 
host:6005
-Ddx.kerberos.krb5.file
file
Required for the migrateToISPKerberos command. Location of the Kerberos configuration file. This file usually resided in the same location as the PowerCenter configuration file.
-Ddx.kerberos.console.keytab.file
file
Required for the migrateToISPKerberos command. Location of the keytab file.
If
Data Integration Hub
 is installed on the same machine as the PowerCenter Administrator Console, the keytab file is the same file that is used for the service principal
HTTP/<hostname>@<domain>
, the file
webapp_http.keytab
.
If
Data Integration Hub
 is installed on a different machine than the PowerCenter Administrator Console, the keytab file must contain the credentials for the service principal
HTTP/<
DIH
hostname>@<domain>
.
-Ddx.kerberos.console.service.principal.name
name
Required for the migrateToISPKerberos command. Service principal host name in the following format: 
HTTP/<FQDN>@<REALM NAME>
For exampe: 
 HTTP/webserver.development.com@DEVELOPMENT.COM

Repository Utility Command Examples

Create a new
Data Integration Hub
 repository: 
repoutil –c createSchema –u DIH_USR –p DIH_USR –l ”jdbc:informatica:oracle://dih_rdbms:1521;SID=orcl”  –t dih
repoutil –c createContent –u DIH_USR –p DIH_USR –l ”jdbc:informatica:oracle://dih_rdbms:1521;SID=orcl”  –t dih
Create a new
Data Integration Hub
 publication repository: 
repoutil –c createSchema –u DIH_STAGING_USR –p DIH_STAGING_USR –l ”jdbc:informatica:oracle://dih_rdbms:1521;SID=orcl”  –t dih_staging
repoutil –c createContent –u DIH_STAGING_USR –p DIH_STAGING_USR –l ”jdbc:informatica:oracle://dih_rdbms:1521;SID=orcl”  –t dih_staging
Create a new operational data store: 
repoutil –c createSchema –u DIH_USR –p DIH_ODS_PASSWORD –l ”jdbc:informatica:oracle://dih_rdbms:1521;SID=orcl”  –t dih_ods
repoutil –c createContent –u DIH_USR –p DIH_ODS_PASSWORD –l ”jdbc:informatica:oracle://dih_rdbms:1521;SID=orcl”  –t dih_ods
0 COMMENTS
We’d like to hear from you!