Table of Contents

Search

  1. Preface
  2. Command Line Programs and Utilities
  3. Installing and Configuring Command Line Utilities
  4. Using the Command Line Programs
  5. Environment Variables for Command Line Programs
  6. Using infacmd
  7. infacmd as Command Reference
  8. infacmd aud Command Reference
  9. infacmd autotune Command Reference
  10. Infacmd bg Command Reference
  11. infacmd ccps Command Reference
  12. infacmd cluster Command Reference
  13. infacmd cms Command Reference
  14. infacmd dis Command Reference
  15. infacmd idp Command Reference
  16. infacmd edp Command Reference
  17. Infacmd es Command Reference
  18. infacmd ihs Command Reference
  19. infacmd ipc Command Reference
  20. infacmd isp Command Reference
  21. infacmd ldm Command Reference
  22. infacmd mas Command Reference
  23. infacmd mi Command Reference
  24. infacmd mrs Command Reference
  25. infacmd ms Command Reference
  26. infacmd oie Command Reference
  27. infacmd ps Command Reference
  28. infacmd pwx Command Reference
  29. infacmd roh Command Reference
  30. infacmd rms Command Reference
  31. infacmd rtm Command Reference
  32. infacmd sch Command Reference
  33. infacmd search Command Reference
  34. infacmd sql Command Reference
  35. infacmd tdm Command Reference
  36. infacmd tools Command Reference
  37. infacmd wfs Command Reference
  38. infacmd ws Command Reference
  39. infacmd xrf Command Reference
  40. infacmd Control Files
  41. infasetup Command Reference
  42. pmcmd Command Reference
  43. pmrep Command Reference
  44. Working with pmrep Files

Configure the Metadata Manager Utilities

Configure the Metadata Manager Utilities

To configure the Metadata Manager utilities, configure environment variables that specify the location of the Java Virtual Machine and the Informatica root directory. You must also verify the shared library location for Solaris.
If the domain uses Kerberos authentication, create the domains.infa file. Metadata Manager command line programs use the domains.infa file to get gateway connectivity information for the domain.
Configure the following environment variables:
JAVA_HOME
Specifies the location of the Java Virtual Machine. Set JAVA_HOME to the PowerCenter Java directory in the command line utilities installation. For example:
<Utilities installation directory>\PowerCenter\java
Set this environment variable in each Metadata Manager command line program as follows:
  1. Open the batch file or shell script with a text editor.
  2. Find the line that sets JAVA_HOME to
    @INFA_JDK_HOME@
    .
  3. Replace the string
    @INFA_JDK_HOME@
    with the PowerCenter Java directory. For example:
    set JAVA_HOME=C:\InfaUtilities\PowerCenter\java
  4. Save and close the batch file or shell script.
INFA_HOME
Specifies the Informatica root directory so that any Informatica application or service can find the other Informatica components that it needs to run. Set INFA_HOME to the PowerCenter directory in the command line utilities installation. For example:
<Utilities installation directory>\PowerCenter
Set this environment variable on each machine where you installed the Informatica utilities.
LD_LIBRARY_PATH
Required for Solaris. Specifies the shared library location. Verify that the LD_LIBRARY_PATH environment variable contains the following directories:
${JAVA_HOME}/jre/lib/sparcv9/server:${JAVA_HOME}/jre/lib/sparcv9/jli
Set this environment variable on each machine where you installed the Informatica utilities.
Restart the machine after you configure the INFA_HOME or LD_LIBRARY_PATH environment variable.


Updated August 15, 2019