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 dp Command Reference
  16. infacmd idp Command Reference
  17. infacmd edp Command Reference
  18. Infacmd es Command Reference
  19. infacmd ihs Command Reference
  20. infacmd ipc Command Reference
  21. infacmd isp Command Reference
  22. infacmd ldm Command Reference
  23. infacmd mas Command Reference
  24. infacmd mi Command Reference
  25. infacmd mrs Command Reference
  26. infacmd ms Command Reference
  27. infacmd oie Command Reference
  28. infacmd ps Command Reference
  29. infacmd pwx Command Reference
  30. infacmd roh Command Reference
  31. infacmd rms Command Reference
  32. infacmd rtm Command Reference
  33. infacmd sch Command Reference
  34. infacmd search Command Reference
  35. infacmd sql Command Reference
  36. infacmd tdm Command Reference
  37. infacmd tools Command Reference
  38. infacmd wfs Command Reference
  39. infacmd ws Command Reference
  40. infacmd xrf Command Reference
  41. infacmd Control Files
  42. infasetup Command Reference
  43. pmcmd Command Reference
  44. pmrep Command Reference
  45. Working with pmrep Files

Command Reference

Command Reference

Metadata Manager Service Options

Metadata Manager Service Options

Enter Metadata Manager Service options in the following format:
infacmd isp CreateMMService ... -so option_name=value option_name=value ...
To enter multiple options, separate them with a space. To enter a value that contains a space or other non-alphanumeric character, enclose the value in quotation marks.
The following table describes the Metadata Manager Service options:
Option
Description
AgentPort
Required. Port number for the Metadata Manager Agent. The agent uses this port to communicate with metadata source repositories. Default is 10251.
CodePage
Required. Code page description for the Metadata Manager repository. To enter a code page description that contains a space or other non-alphanumeric character, enclose the name in quotation marks.
ConnectString
Required. Native connect string for the Metadata Manager repository database.
DBUser
Required. User account for the Metadata Manager repository database.
DBPassword
Required. Password for the Metadata Manager repository database user. User password. You can set a password with the -so option or the environment variable INFA_DEFAULT_DATABASE_PASSWORD. If you set a password with both methods, the password set with the -so option takes precedence.
DatabaseHostname
Required. Host name for the Metadata Manager repository database.
DatabaseName
Required. Full service name or SID for Oracle databases. Service name for IBM DB2 databases. Database name for Microsoft SQL Server database.
DatabasePort
Required. Port number for the Metadata Manager repository database.
DatabaseType
Required. Type of database for the Metadata Manager repository.
ErrorSeverityLevel
Optional. Level of error messages written to the Metadata Manager Service log. Default is ERROR.
FileLocation
Required. Location of the files used by the Metadata Manager application.
JdbcOptions
Optional. Additional JDBC options.
You can use this property to specify the following information:
  • Backup server location
  • Oracle Advanced Security Option (ASO) parameters
  • Microsoft SQL Server authentication parameters
  • Additional JDBC parameters when secure communication is enabled for the Metadata Manager repository database
For more information about these parameters, see the
Informatica Application Service Guide
.
MaxConcurrentRequests
Optional. Maximum number of request processing threads available, which determines the maximum number of client requests that Metadata Manager can handle simultaneously. Default is 100.
MaxHeapSize
Optional. Amount of RAM in megabytes allocated to the Java Virtual Manager (JVM) that runs Metadata Manager. Default is 512.
MaxQueueLength
Optional. Maximum queue length for incoming connection requests when all possible request processing threads are in use by the Metadata Manager application. Default is 500.
MaximumActiveConnections
Optional. Number of active connections to the Metadata Manager repository database available. The Metadata Manager application maintains a connection pool for connections to the repository database. Default is 20.
MaximumWaitTime
Optional. Amount of time in seconds that Metadata Manager holds database connection requests in the connection pool. Default is 180.
MetadataTreeMaxFolderChilds
Optional. Number of child objects that appear in the Metadata Manager metadata catalog for any parent object. Default is 100.
ODBCConnectionMode
Connection mode the Integration Service uses to connect to metadata sources and the Metadata Manager repository when loading resources. Value can be true or false.
You must set this property to True if the Integration Service runs on a UNIX machine and you want to load metadata from a Microsoft SQL Server database or if you use a Microsoft SQL Server database for the Metadata Manager repository.
OracleConnType
Required if you select Oracle for the DatabaseType. Oracle connection type. You can enter one of the following options:
  • OracleSID
  • OracleServiceName
PortNumber
Required. Port number the Metadata Manager application runs on. Default is 10250.
StagePoolSize
Optional. Maximum number of resources that Metadata Manager can load simultaneously. Default is 3.
TablespaceName
Tablespace name for the Metadata Manager repository on IBM DB2.
TimeoutInterval
Optional. Amount of time in minutes that Metadata Manager holds a failed resource load in the load queue. Default is 30.
URLScheme
Required. Indicates the security protocol that you configure for the Metadata Manager application: HTTP or HTTPS.
keystoreFile
Required if you use HTTPS. Keystore file that contains the keys and certificates required if you use the SSL security protocol with the Metadata Manager application.

0 COMMENTS

We’d like to hear from you!