The SDKDYN takes its Java implementation from the SDK connector, and differs only in that it uses the DYN schema instead of the SDK schema. Consequently, it uses the DYN User Interface plug-in built in to the Provisioning Manager.
This makes it possible to demonstrate some capabilities like automatic reverse associations which are not catered for in the SDK schema and the Provisioning Server User Interface plug-in. This connector defines virtual containers in metadata (the new preferred approach) instead of in connector.xml. Look for the <class name="eTDYNAccountContainer"> in cs-sdk-home/connectors/sdkdyn/conf/sdkdyn_metadata.xml.
The SDKDYN sample connector is an example of how to implement a custom connector. The SDK sample connector uses the java.util.Properties API for persisting account and group objects to a series of Java properties flat-files beneath a specified file system directory, local to the computer running CA IAM CS. Like all connectors, it has an attribute-style processor that implements the following mandatory LDAP operations:
It also implements the optional operation doModifyRn(), and supports direct associations between object types. It does not support doMove() and its variants.
The SDKDYN sample connector is a typical DYN connector (with developer-maintained metadata). That is, it is a flat connector with no hierarchy except for the virtual containers SDK Accounts and SDK Groups. However, its use of flat files makes its connection manager a contrived example.
As recommended, it makes extensive use of metadata and sample validator and converter plug-ins. The SDK sample connector is also bundled with fully functional JMeter component tests.
The build.xml ant file is included for compiling the SDK sample connector and associated code. This file is in the following location:
cs-sdk-home/connectors/sdkdyn
Note: The sample SDK static connector is located in jcs-sdk-deprecated.zip in the SDK distribution. The new DYN-based SDK connectors (SDKDYN, SDKFS, SDKSCRIPT, SDKCOMPOUND) supersede the static SDK sample.
The SDKDYN Connector contains examples of all core elements involved in implementation of a CA IAM CS hosted connector, such as:
Important: Connectors have their own methods, such as add() and modify(), which they inherit from the MetaConnector base class, the primary engine of CA IAM CS connectors. Connector developers should rarely (if ever) override these methods. However, if you do override these methods, it is imperative that you invoke the matching super.*() method. For example, an overridden add() method must call super.add().
|
Copyright © 2013 CA.
All rights reserved.
|
|