Table of Contents

Search

  1. Introduction
  2. Samples and Examples
  3. Tools and Utilities
  4. SDK Resources

Automation Properties

Automation Properties

To automate configuration tasks, configure properties for the tasks that you need to automate in the
automation.properties
file.

MDM Hub Environment Properties

Before you automate any configuration task, set the MDM Hub environment properties.
The following table describes the properties to set for the MDM Hub environment:
Property
Description
appserver.type
Required. Type of application server, such as jboss, weblogic, or websphere.
appserver.version
Required. Version of the application server.
jboss.hostname
Required. Name of the machine that hosts JBoss.
jboss.remote_port
Required. The JBoss remote port number.
websphere.hostname
Required. Name of the machine that hosts WebSphere.
websphere.rmi_port
Required. The WebSphere RMI port number.
weblogic.hostname
Required. Name of the machine that hosts WebLogic.
weblogic.port
Required. Port number on which the WebLogic Server is listening.
weblogic.login
Required. Name of the user for the WebLogic installation.
weblogic.password
Required. Password that corresponds to the WebLogic user.
MDMAdminUsername
Required. User name of the MDM Hub administrative user.
MDMAdminPassword
Required. Clear text password that corresponds to the MDM Hub administrative user. Use either the
MDMAdminPassword
or the
MDMAdminEncryptedPassword
property.
MDMAdminEncryptedPassword
Required. Encrypted password that corresponds to the MDM Hub administrative user. Use either the
MDMAdminPassword
or the
MDMAdminEncryptedPassword
property.

User Configuration Properties

Set the user configuration properties to automate user configuration tasks.
The following table describes the properties that you need to configure to automate user configuration:
Property
Description
MDM.number.of.new.users
Required. Number of MDM Hub users that you want to create. You can create a maximum of 1000 users.
MDM.new.user.firstname<n>
Required. First name of the user that you want to create.
Define the
MDM.new.user.firstname<n>
property for each user. The value of
<n>
for the first user is 0. For each additional user, increment the value of
<n>
by 1.
MDM.new.user.middlename<n>
Optional. Middle name of the user that you want to create.
Define the
MDM.new.user.middlename<n>
property for each user. The value of
<n>
for the first user is 0. For each additional user, increment the value of
<n>
by 1.
MDM.new.user.lastname<n>
Required. Last name of the user that you want to create.
Define the
MDM.new.user.lastname<n>
property for each user. The value of
<n>
for the first user is 0. For each additional user, increment the value of
<n>
by 1.
MDM.new.user.email<n>
Required. Email address of the user that you want to create.
MDM.new.user.username<n>
Required. User name of the user that you want to create.
Define the
MDM.new.user.username<n>
property for each user. The value of
<n>
for the first user is 0. For each additional user, increment the value of
<n>
by 1.
MDM.new.user.password<n>
Required. Password to access the account of the user that you want to create.
Define the
MDM.new.user.password<n>
property for each user. The value of
<n>
for the first user is 0. For each additional user, increment the value of
<n>
by 1.
MDM.new.user.isExternalAuthentication<n>
Required. Specifies whether or not the user is externally authenticated.
Define the
MMDM.new.user.isExternalAuthentication<n>
property for each user. The value of
<n>
for the first user is 0. For each additional user, increment the value of
<n>
by 1.
You can configure the following values:
  • Y. Indicates that the user is externally authenticated.
  • N. Indicates that the user is internally authenticated in the
    MDM Hub
    .
If set to
N
, ensure that you set the
MDM.new.user.password<n>
property.
MDM.new.user.isAdministrator<n>
Required. Specifies whether or not the user is an administrator.
Define the
MDM.new.user.isAdministrator<n>
property for each user. The value of
<n>
for the first user is 0. For each additional user, increment the value of
<n>
by 1.
You can configure the following values:
  • Y. Indicates that the user is an administrator.
  • N. Indicates that the user is not an administrator.
MDM.new.user.defaultDatabaseId<n>
Required. ID of the default Operational Reference Store.
Define the
MDM.new.user.defaultDatabaseId<n>
property for each user. The value of
<n>
for the first user is 0. For each additional user, increment the value of
<n>
by 1.
If you do not set the
MDM.new.user.defaultDatabaseId<n>
property, the user is registered with the MDM Hub Master Database.
MDM.number.of.user_ors_relationships
Required. Number of relationships between users and Operational Reference Stores that you want to create.
You can create a maximum of 1000 relationships each time you run the command to register users with Operational Reference Stores.
MDM.user_ors_rel.username<n>
Required. User name of a user that you want to register with an Operational Reference Store.
Define the
MDM.user_ors_rel.username<n>
property for each user. The value of
<n>
for the first user is 0. For each additional user, increment the value of
<n>
by 1.
MDM.user_ors_rel.databaseIds<n>
Required. Operational Reference Store ID.
Define the
MDM.user_ors_rel.databaseIds<n>
property for each user. The value of
<n>
for the first user is 0. For each additional user, increment the value of
<n>
by 1.
If you want to register a user with multiple Operational Reference Stores, separate each Operational Reference Store ID with a comma.
MDM.number.of.user_roles_relationships
Required. Number of relationships between user and roles that you want to create.
You can create a maximum of 1000 relationships each time you run the command to assign roles to users.
MDM.user_roles_rel.username<n>
Required. User name of a user that you want to assign to a role.
Define the
MDM.user_roles_rel.username<n>
property for each user. The value of
<n>
for the first user is 0. For each additional user, increment the value of
<n>
by 1.
MDM.user_roles_rel.databaseIds<n>
Required. Operational Reference Store ID.
Define the
MDM.user_roles_rel.databaseId<n>
property for each user. The value of
<n>
for the first user is 0. For each additional user, increment the value of
<n>
by 1.
If you want to assign a user to multiple Operational Reference Stores, separate each Operational Reference Store ID with a comma.
MDM.user_roles_rel.roles<n>
Required. Name of a role that you want to assign to a user. Separate each role with a comma.
Define the
MDM.user_roles_rel.roles<n>
property for each user. The value of
<n>
for the first user is 0. For each additional user, increment the value of
<n>
by 1.
MDM.number.of.delete.users
Required. The total number of users that you want to delete.
You can delete a maximum of 1000 users each time you run the command to delete the MDM Hub users.
MDM.delete.user.username<n>
Required. User name of a user that you want to delete.
Define the
MDM.delete.user.username<n>
property for each user that you want to delete. The value of
<n>
for the first user is 0. For each additional user, increment the value of
<n>
by 1.

LDAP Server User Synchronization Properties

Set the LDAP Server user synchronization properties to configure to automate the synchronization of MDM Hub users between LDAP servers and the MDM Hub.
The following table describes the properties that you need to configure to automate the synchronization of MDM Hub users:
Property
Description
LDAP.Server
Required. URL to connect to the LDAP server.
LDAP.Username
Required. User name to access the LDAP server. If the LDAP server search is not secure, you do not need a user name.
LDAP.Password
Required. Password to access the LDAP server. If the LDAP server search is not secure, you do not need a password.
LDAP.SearchBase
Required. Specifies the starting point for the search in the LDAP directory tree.
For example, to query the entire directory, specify the root of the directory tree. To query a specific organizational unit in the directory, specify the root of the organizational unit in the directory tree.
A search base can include the following objects:
  • cn. common name
  • ou. organizational unit
  • o. organization
  • c. country
  • dc. domain
A search base consists of multiple objects separated by commas.
LDAP.attribute_name.for.user.firstname
Required. First name of a user in the LDAP server. Use the property if you want to synchronize the first name of a user from the LDAP server with the Operational Reference Store.
LDAP.attribute_name.for.user.middlename
Optional. Middle name of a user in the LDAP server. Use the property if you want to synchronize the middle name of a user from the LDAP server with the Operational Reference Store.
LDAP.attribute_name.for.user.lastname
Required. Last name of a user in the LDAP server. Use the property if you want to synchronize the last name of a user from the LDAP server with the Operational Reference Store.
LDAP.attribute_name.for.username
Required. An attribute of the user in the LDAP server, other than a common name or a user ID, such as Security Access Manager account name. Use the property to synchronize an attribute other than a common name or a user ID from the LDAP server with the Operational Reference Store.
LDAP.number.of.ldaproles
Required. Number of roles in the Operational Reference Stores for which you want to synchronize users.
LDAP.rolename.for.ldap.search<n>
Required. Name of a role in the LDAP server.
Define the
LDAP.rolename.for.ldap.search<n>
property for each role. The value of
<n>
for the first role is 0. For each additional role, increment the value of
<n>
by 1.
LDAP.attribute_name.for.user.email
Required. Email address of a user in the LDAP server. Use the property if you want to synchronize the email address of a user from the LDAP server with the Operational Reference Store.
LDAP.strip_slashes_from_usernames
Optional. Specifies whether to remove slashes from user names.
You can configure the following values:
  • no. Retains slashes in the user names.
  • yes. Removes slashes from the user names.
Default is
no
.
For example, when a user name such as
Boyd\
is part of a search filter expression such as
(&(CN=Boyd\)
, the following error might occur:
InvalidSearchFilterException: Unbalanced parenthesis
In a search expression, slashes might be treated as escape characters resulting in an unbalanced parenthesis error. To make the synchronization process work in such scenarios, you might need to remove slashes from the user names.
LDAP.cleanup.before.sync
Optional. Specifies whether to remove all the users that are assigned in an Operational Reference Store before synchronizing users with roles.
You can configure the following values:
  • true. Removes the users that are assigned in an Operational Reference Store, and then assigns the users to roles.
    If you run the command to synchronize users with the
    -u
    option, a single user assignment is removed. Otherwise, all user assignments are removed.
  • false. Retains the users that are assigned in an Operational Reference Store.
Default is
true
.
LDAP.role.attribute_name.for.userlist<n>
Required. Name of an attribute for a role in an LDAP server that is associated with a user in an Operational Reference Store.
Define the
LDAP.role.attribute_name.for.userlist<n>
property for each attribute. The value of
<n>
for the first attribute is 0. For each additional attribute, increment the value of
<n>
by 1.
LDAP.MDM.ORS.databaseId<n>
Required. ID of the Operational Reference Store that has a role associated with a user in the LDAP server.
Define the
LDAP.MDM.ORS.databaseId<n>
property for each Operational Reference Store. The value of
<n>
for the first Operational Reference Store is 0. For each additional Operational Reference Store, increment the value of
<n>
by 1.
LDAP.MDM.rolename<n>
Required. Name of a role in the Operational Reference Store that corresponds to a role in the LDAP server.
Define the
LDAP.MDM.rolename<n>
property for each role. The value of
<n>
for the first role is 0. For each additional role, increment the value of
<n>
by 1.
LDAP.number.of.ldapgroups
Required. Number of user groups in the Operational Reference Stores for which you want to synchronize users.
LDAP.groupname.for.ldap.search<n>
Required. Name of a user group in the LDAP server.
Define the
LDAP.groupname.for.ldap.search<n>
property for each user group. The value of
<n>
for the first user group is 0. For each additional user group, increment the value of
<n>
by 1.
LDAP.group.attribute_name.for.userlist<n>
Required. Name of an attribute for a user group in an LDAP server that is associated with a user in an Operational Reference Store.
Define the
LDAP.group.attribute_name.for.userlist<n>
property for each attribute. The value of
<n>
for the first attribute is 0. For each additional attribute, increment the value of
<n>
by 1.
LDAP.MDM.ORS.group.databaseId<n>
Required. ID of the Operational Reference Store that has a user group associated with a user in the LDAP server.
Define the
LDAP.MDM.ORS.databaseId<n>
property for each Operational Reference Store. The value of
<n>
for the first Operational Reference Store is 0. For each additional Operational Reference Store, increment the value of
<n>
by 1.
LDAP.MDM.groupname<n>
Required. Name of a user group in the Operational Reference Store that corresponds to a user group in the LDAP server.
Define the
LDAP.MDM.groupname<n>
property for each user group. The value of
<n>
for the first user group is 0. For each additional user group, increment the value of
<n>
by 1.

Security Provider Registration Properties

Set the security provider properties to automate the registration of security providers.
The following table describes the properties that you need to configure to automate the registration of security providers:
Property
Description
MDM.security_provider.login_module.template
Required. Name of the template that has the settings for the login module of the security provider.
Use one of the following security provider login templates:
  • MicrosoftActiveDirectory-template
  • OpenLDAP-template
  • Kerberos-template
MDM.security_provider.login_module.name
Required. Name of the login module.
MDM.security_provider.login_module.description
Optional. Description of the login module.
MDM.security_provider.login_module.enabled
Required. Specifies whether the login module is enabled or disabled.
You can configure the following values:
  • yes. Enables the login module.
  • no. Disables the login module.
Default is
no
.
MDM.security_provider.login_module.position
Required. Position of login module with respect to the existing login module.
You can configure the following values:
  • top. Indicates that the login module is the first login module.
  • bottom. Indicates that the login module is the last login module.
Default is
top
.
MDM.security_provider.login_module.no_of_properties
Required. Total number of login modules.
MDM.security_provider.login_module.properties_name<n>
Required. Name of the login module.
Define the
MDM.security_provider.login_module.properties_name<n>
property for each login module. The value of
<n>
for the first login module is 0. For each additional login module, increment the value of
<n>
by 1.
MDM.security_provider.login_module.properties_value<n>
Required. Value of the login module.
Define the
MDM.security_provider.login_module.properties_value<n>
property for each login module. The value of
<n>
for the first login module is 0. For each additional login module, increment the value of
<n>
by 1.
If any value has single slash ('\'), replace it with double slash ('\\').

Informatica Data Director Export and Import Properties

Set the Informatica Data Director application properties to automate the export or import of the Informatica Data Director application.
The following table describes the properties that you need to configure to automate the export or import of the Informatica Data Director application:
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
Applicable to Oracle only. Required. Name of the Oracle service if the selected Oracle connection type is SERVICE.
MDM.master_database.dbname
Applicable to IBM DB2 and Microsoft SQL Server. Required. 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
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.
You can configure the following values:
  • no. Retains files and directories in the temporary directory.
  • yes. Deletes files and directories in the temporary directory.
Default is
yes
.

0 COMMENTS

We’d like to hear from you!