The following Provisioning Server SDKs and interfaces are deprecated in CA Identity Manager r12.5 SP1; however, they continue to function as documented.
To use the C++ Connector SDK and the JIAM SDK, download and install the CA Identity Manager Legacy Components package. It includes the Programming Guide for Provisioning, which describes these SDKs.
This SDK allows you to write custom static C++ Connectors. Existing C++ Connectors will continue to work with CA Identity Manager r12.5 SP8.
Note: New connectors should be developed using the Java Connector SDK, which is described in the Programming Guide for Java Connector Server.
The JIAM SDK provided the following functionality in previous versions of CA Identity Manager:
This API is being deprecated because it only provides access to a subset of CA Identity Manager functionality.
This functionality is replaced by the following CA Identity Manager 12.5 functionality:
You can use admin tasks to manipulate most of the objects that Identity Manager manages.
The CA Identity Manager Task Execution Web Service (TEWS) is a web service interface that allows third-party client applications to submit remote tasks to CA Identity Manager for execution. This interface implements the open standards of WSDL and SOAP to provide remote access to CA Identity Manager.
CA Identity Manager provides interfaces for managed objects, which are accessible through CA Identity Manager APIs.
For more information about admin tasks, see the Administration Guide. For more information about TEWS and managed object interfaces, see the Programming Guide for Java.
You use the etautil batch utility to perform the same tasks as you do with the Provisioning Manager, but from a command line interface. It is described in the Provisioning Reference Guide.
This functionality is replaced by the Task Execution Web Services (TEWS), which is described in the Programming Guide for Java.
The UPC provides a mechanism for Identity Manager to invoke user-specified external programs when user provisioning requests are received. It uses program exits to send alerts regarding non-managed systems (non-managed mode) so that administrators can manually carry out the request and update the account request status. It also uses exits in a synchronous mode (managed mode) to provide a direct management interface to remote endpoint types.
Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |