Required. Type of application server, such as jboss, weblogic, or websphere.

Required. Version of the application server.

Required. Name of the machine that hosts JBoss.

Required. The JBoss remote port number.

Required. Name of the machine that hosts WebSphere.

Required. The WebSphere RMI port number.

Required. Name of the machine that hosts WebLogic.

Required. Port number on which the WebLogic Server is listening.

Required. Name of the user for the WebLogic installation.

Required. Password that corresponds to the WebLogic user.

Required. User name of the MDM Hub administrative user.

Required. Clear text password that corresponds to the MDM Hub administrative user. Use either the

MDMAdminPassword

or the

MDMAdminEncryptedPassword

property.

Required. Encrypted password that corresponds to the MDM Hub administrative user. Use either the

MDMAdminPassword

or the

MDMAdminEncryptedPassword

property.

Required. Number of MDM Hub users that you want to create. You can create a maximum of 1000 users.

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.

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.

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.

Required. Email address of the user that you want to create.

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.

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.

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.

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.

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.

You can create a maximum of 1000 relationships each time you run the command to register users with Operational Reference Stores.

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.

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.

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.

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.

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.

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.

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.

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.

Required. URL to connect to the LDAP server.

Required. User name to access the LDAP server. If the LDAP server search is not secure, you do not need a user name.

Required. Password to access the LDAP server. If the LDAP server search is not secure, you do not need a password.

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.

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.

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.

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.

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.

Required. Number of roles in the Operational Reference Stores for which you want to synchronize users.

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.

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.

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.

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

.

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.

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.

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.

Required. Number of user groups in the Operational Reference Stores for which you want to synchronize users.

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.

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.

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.

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.

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:

Required. Name of the login module.

Optional. Description of the login module.

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

.

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

.

Required. Total number of login modules.

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.

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 ('\\').

Required. Type of database that you use.

Based on the database that you use, set to one of the following values:

Required. Name of the machine that hosts the MDM Hub Master Database.

Required. Port number of the MDM Hub Master Database.

Applicable to Oracle only. Required. Name of the Oracle service if the selected Oracle connection type is SERVICE.

Applicable to IBM DB2 and Microsoft SQL Server. Required. Name of the database instance.

Required. User name to access the MDM Hub Master Database.

Required. Password to access the MDM Hub Master Database.

Required. Name of the temporary 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

.