Configuring the VMM repository and realm | HCL Digital Experience
Run the wp-create-cur, wp-create-cur-custom-property, and wp-update-group-repository-relationship commands to configure the VMM repository and realm.
Procedure
- Open a command prompt and change to the wp_profile_root/ConfigEngine directory.
-
Run the following task to add the repository configuration to VMM. For information, read the
related links section.
- AIX® HP-UX Linux™ Solarisz/OS®: ./ConfigEngine.sh wp-create-cur -DWasPassword=yourpassword -Dfederated.cur.id=SoftGroups -Dfederated.cur.adapterClassName=com.ibm.wps.vmm.adapter.softgroups.SoftgroupsAdapter -Dfederated.cur.baseDN=o=softgroups
- IBM® i: ConfigEngine.sh wp-create-cur -DWasPassword=yourpassword -Dfederated.cur.id=SoftGroups -Dfederated.cur.adapterClassName=com.ibm.wps.vmm.adapter.softgroups.SoftgroupsAdapter -Dfederated.cur.baseDN=o=softgroups
- Windows™: ConfigEngine.bat wp-create-cur -DWasPassword=yourpassword -Dfederated.cur.id=SoftGroups -Dfederated.cur.adapterClassName=com.ibm.wps.vmm.adapter.softgroups.SoftgroupsAdapter -Dfederated.cur.baseDN=o=softgroups
- Run the following command to update the repository configuration
with custom properties:Specify the following attributes on the command line:
dataSource
- The attribute must point to the correct JNDI name of the previously configured data source for the rule-based groups database.
dbSchema
- The attribute must declare the database schema that holds the rule-based groups table.
dbType
- If your database server type is SQLServer, you must declare the
attribute
dbType
by specifyingSQLServer
as the value. For all other database server types, you can omit the value. - Base entry specification
- You can set the base entry specification that defines the base distinguished name and suffix for rule-based groups to a different value.
name
- The
name
and thenameInRepository
must be the same.
- AIX®
HP-UX
Linux™
Solarisz/OS®:
./ConfigEngine.sh wp-create-cur-custom-property -DWasPassword=yourpassword -Dcur.id=SoftGroups -Dcur.name=dataSource -Dcur.value=nameofdatasource ./ConfigEngine.sh wp-create-cur-custom-property -DWasPassword=yourpassword -Dcur.id=SoftGroups -Dcur.name=dbSchema -Dcur.value=yourschema ./ConfigEngine.sh wp-create-cur-custom-property -DWasPassword=yourpassword -Dcur.id=SoftGroups -Dcur.name=dbType -Dcur.value=yourDBType
- IBM® i:
ConfigEngine.sh wp-create-cur-custom-property -DWasPassword=yourpassword -Dcur.id=SoftGroups -Dcur.name=dataSource -Dcur.value=nameofdatasource ConfigEngine.sh wp-create-cur-custom-property -DWasPassword=yourpassword -Dcur.id=SoftGroups -Dcur.name=dbSchema -Dcur.value=yourschema ConfigEngine.sh wp-create-cur-custom-property -DWasPassword=yourpassword -Dcur.id=SoftGroups -Dcur.name=dbType -Dcur.value=yourDBType
- Windows™:
ConfigEngine.bat wp-create-cur-custom-property -DWasPassword=yourpassword -Dcur.id=SoftGroups -Dcur.name=dataSource -Dcur.value=nameofdatasource ConfigEngine.bat wp-create-cur-custom-property -DWasPassword=yourpassword -Dcur.id=SoftGroups -Dcur.name=dbSchema -Dcur.value=yourschema ConfigEngine.bat wp-create-cur-custom-property -DWasPassword=yourpassword -Dcur.id=SoftGroups -Dcur.name=dbType -Dcur.value=yourDBType
- You must enable the cross repository group lookup for the
repositories you want to use. To find Groups Entities in the SoftGroups
Repository, run the following task:
- AIX® HP-UX Linux™ Solarisz/OS®: ./ConfigEngine.sh wp-update-group-repository-relationship -DWasPassword=password -Drepository.id=ldapid -Drepository.forgroups=SoftGroups
- IBM® i: ConfigEngine.sh wp-update-group-repository-relationship -DWasPassword=password -Drepository.id=ldapid -Drepository.forgroups=SoftGroups
- Windows™: ConfigEngine.bat wp-update-group-repository-relationship -DWasPassword=password -Drepository.id=ldapid -Drepository.forgroups=SoftGroups
- Optional:
You can enable a dynacache on the Portal softgroups to help improve performance under high
load.
The dynacache offers improved performance at the tradeoff of stale data that is potentially retrieved from the cache. For example, if groups in the Portal softgroups database are updated then the cache might contain outdated data relative to updated data in the database. Consider the tradeoff of performance versus the need for live data before you implement the following steps.