Use this procedure to dynamically add a new base entry to the specified
profile repository.
Before you begin
This base entry must have existed in the repository already.
About this task
Note: When this dynamic
call is made, only the configuration in memory is updated. The configuration
file is not updated.
- Event Type
- DYNA_CONFIG_EVENT_ADD_BASE_ENTRY
- Configuration Data
- DYNA_CONFIG_KEY_REPOS_ID (required) - [String]
- Specifies the ID of the repository that you want to add the base entry
to.
- DYNA_CONFIG_KEY_BASE_ENTRY (required) - [String]
- Specifies the base entry to be added to the specified repository.
- DYNA_CONFIG_KEY_BASE_ENTRY_IN_REPOS (optional) – [String]
- Specifies the corresponding base entry existing in the repository, if
it is different from the virtual member manager entry name.
The following is a sample task:
Procedure
- Ensure that virtual member manager is running.
- If the base entry is to be added to the database repository, insert
a new base entry into database directory Issue the sql command:
insert into dbentity (entity_id, entity_type, unique_id, unique_name, unique_name_key)
values (-1000, 'OrgContainer', 'cacf70b0-3f10-11da-9d8f-828d4353a4dc', 'o=new entry',
'o=new entry')
- Call the dynamicUpdateConfig API to add a new base entry to repository. For example:
Hashtable configData = new Hashtable();
configData.put(DynamicConfigConstants.DYNA_CONFIG_KEY_REPOS_ID, "DB1");
configData.put(DynamicConfigConstants.DYNA_CONFIG_KEY_BASE_ENTRY,"o=new entry");
- Call the dynamicUpdateConfig API to add a new participating base
entry into realm. For example:
service.dynamicUpdateConfig(DynamicConfigConstants.DYNA_CONFIG_EVENT_ADD_BASE_ENTRY, configData);