You should write connectors using a specialized data model based on the generic DYN schema (eta_dyn_openldap.schema) and metadata.
For example, like the JDBC and JNDI DYN metadata output from Connector Xpress. This approach requires a metadata-aware client to interact with your connector, for example, the GUI client DYN Provisioning Manager plug-in.
This approach means that, rather than displaying the LDAP attribute id eTDYN-str-01 to the user, its mapped name Description is displayed instead.
We recommend this approach for all connector development as doing so means it is not necessary to write a custom parser table and/or Provisioning Manager C++ User Interface plug-in. Using a DYN schema also simplifies enhancing released connectors as it is only necessary to change metadata mappings. That is, there is no impact on the Provisioning Server.
In this release, is it now possible to include POP scripts for DYN-based connectors, as demonstrated for the SDKDYN connector by cs-sdk-home/connectors/sdkdyn/conf/_uninst/ sdkdynpop.ldif.
POP scripts are required for DYN endpoint types because the custom mapping chosen are important when defining default account templates.
Note: Connector Xpress does the work of a POP script for endpoint types created within it.
If the DYN plug-in does not meet your requirements, you can write your own custom Provisioning Manager plug-in for the DYN schema.
|
Copyright © 2013 CA.
All rights reserved.
|
|