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
  • Multidomain MDM 10.3 HotFix 1
  • All Products

Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Samples and Examples
  4. Part 3: Tools and Utilities
  5. Part 4: SDK Resources

Resource Kit Guide

Resource Kit Guide

Back Next

Importing and Deploying Informatica Data Director to an Existing Application

Importing and Deploying Informatica Data Director to an Existing Application

If an Informatica Data Director (IDD) property file or a configuration file is updated, you can import the changes to the application through the command line. The command imports one type of change each time you run it. If an application has multiple changes, such as changes in the configuration and changes in the
BDDHelp
 file, run the command for each type of change.
  1. Edit the
    automation.properties
     file.
    The following table describes the properties in the
    automation.properties
     file that you need to configure:
    Property
    Description
    MDM.master_database.type
    Required. Type of database that you use.
    Based on the database that you use, set to one of the following values:
    • oracle
    • db2
    • sqlserver
    MDM.master_database.server
    Required. Name of the machine that hosts the MDM Hub Master Database.
    MDM.master_database.portnumber
    Required. Port number of the MDM Hub Master Database.
    MDM.master_database.servicename
    Required. Applicable to Oracle only. Name of the Oracle service if the selected Oracle connection type is SERVICE.
    MDM.master_database.dbname
    Required. Applicable to IBM DB2 and Microsoft SQL Server. Name of the database instance.
    MDM.master_database.username
    Required. User name to access the MDM Hub Master Database.
    MDM.master_database.password
    Required. Password to access the MDM Hub Master Database.
    MDM.temp_directory_name
    Required. Name of the temporary directory.
    MDM.delete_temp_directory_name
    Optional. Specifies whether you want to delete or retain files and directories in the temporary directory. You might want to retain files and directories in the temporary directory for troubleshooting issues.
    Set to
    no
     to retain files and directories in the temporary directory. If you set the value to any value other than
    no
    , all the files and directories in the temporary directory are deleted.
  2. To import and deploy IDD to an existing application, run the following command:
    On Windows.
    IddImportToExistingApp.cmd <IDD application name> -<Configuration change type> <file name of the file with configuration changes>
    On UNIX.
    IddImportToExistingApp.sh <IDD application name> -<Configuration change type> <File with configuration changes>
    The following table describes the types of configuration changes and the associated files:
    Configuration Change Type
    Description
    BDDConfiguration
    Changes to the IDD configuration. The changes are made to the
    BDDConfig.xml
     file.
    BDDBundle
    Changes to the IDD bundle. The changes are made to the
    BDDBundle[_locale].properties
     file.
    MetadataBundle
    Changes to the metadata bundle. The changes are made to the
    MetadataBundle[_locale].properties
     file.
    MessagesBundle
    Changes to the message bundle. The changes are made to the
    MessagesBundle[_locale].properties
     file.
    ErrorCodeBundle
    Changes to the error code bundle. The changes are made to the
    ErrorCodeBundle[_locale].properties
     file.
    BDDHelp
    Changes to the IDD online help. The changes are made to the
    BDDHelp[_locale].zip
     file.
    CustomBDDHelp
    Changes to the custom IDD online help. The changes are made to the
    CustomBDDHelp[_locale].zip
     file.
    ApplicationLogo
    Changes to the IDD application logo. The changes are made to the
    logo.gif|logo.jpg|logo.jpeg|logo.png
     file.
    DataImportTemplate
    Changes to the IDD data import template. The changes are made to the
    data-import-template-config.xml
     file.
  3. Restart the application server.
    The IDD application is validated and is moved to one of the following application states in which it was before changes were imported:
    • Full Deployment
    • Limited Deployment
    • Not Deployed
  4. If validation errors appear during the application server restart, manually fix the validation errors and restart the import process.
0 COMMENTS
We’d like to hear from you!