Programming Guides › Programming Guide for Java Connector Server › SDK Sample Connectors › Possible Clients

Possible Clients

The Provisioning Manager can serve as the main client to drive the DYN-based SDK sample connectors (SDKDYN, SDKFS, SDKSCRIPT, SDKCOMPOUND).The DYN User Interface plug-in built in to the Provisioning Manager is used for these sample connectors. To drive the SDK sample connector using the Provisioning Manager, you must install the Admin SDK Option as the SDK User Interface plug-in is required for the SDK sample connector.

To drive the SDK sample connector using the Provisioning Manager, install the Admin SDK Option.

Note: For more information about installing the Admin SDK Option, see the Java Connector Server Implementation Guide.

The CA Identity Manager Web GUI can also be used as the client to drive the following DYN-based SDK sample connectors: SDKDYN, SDKFS, and SDKSCRIPT. However, before the SDK samples can be appear in the CA Identity Manager UI, run the Role Definition Generator based on the SDK samples' metadata, and copy the Role Definition Generator output files to the specific folders.

Note: For more information about running the Role Definition Generator, see How you Generate CA Identity Manager User Console Account Screens in the Connector Xpress User Guide.

Some JMeter tests are included for communicating directly with the Java CS, in which case the Provisioning Manager need not be running, or even installed. Although we do not provide support for the JMeter library, other than some basic pointers, we strongly recommend that you write component tests concurrently with connector development, regardless of whether you use JMeter or another LDAP enabled testing framework. Informal manual testing can be useful in the early stages of connector development, but ultimately automated regression tests are required.

Unlike the C++ Connector Server, you can start the Java CS independently of the Provisioning Server. Connectors hosted by Java CS act much more like autonomous subtrees of a larger DIT, in particular supporting richer LDAP filter semantics. The components testing sequence is as follows:

• The top-level SDK build.xml starts the Java CS when ant jmeter.core is invoked.
• The set of tests for each connector implementation runs in turn. Each test must create an endpoint type, a connector within the endpoint type, and then put the connector through its paces by submitting various LDAP requests on target objects of various kinds.
• The Java CS spawned for the test run is automatically shut down when all tests are completed.

  Note: Verify that you do not have a development Java CS (listening on port 20412) already running before executing them.

The JXplorer utility can also be useful for adhoc one-off testing during connector development, particularly for running manual queries to verify the state of a connector during the early stages of development. The JXplorer utility is included as part of the Provisioning Manager installation.

Important! Be careful to include any important test steps in your JMeter test to help ensure that regressions do not go unnoticed during development.