Connector Xpress lets you create projects that specify how connectors are configured and deployed to the Provisioning Server.
A project represents a connector in Connector Xpress. A project includes:
You can save, edit, and reopen projects for later use.
You can also create projects based on existing metadata, then modify the class mappings and operation bindings and then redeploy the connector back to the endpoint.
You can create a project using the following methods:
This lets you create projects that specify how connectors are configured and deployed to the Provisioning Server.
This allows you to use Connector Xpress as a generic metadata editor and create new attributes.
This lets you use templates as starting points for mapping common endpoint schemas.
The wizard helps you start a new project based on a template, and steps you through the basic process of mapping an account and group class.
You can use a template as a starting point for mapping common endpoint schemas. For example, starting a project with a template is useful for LDAP, where standards such as RFCs define widely used schemas, and purely custom schemas are less common. Templates also include information that CA Identity Manager uses to render account management screens.
The following table highlights some of the more commonly used templates. For a full list of all templates, select Project, Create New from Template in Connector Xpress, then click on each template for a brief description.
Important! To help ensure correct performance, we recommend that you use the vendor-specific template supplied with Connector Xpress as a starting point when you create a mapping for a specific vendor.
|
Project Name Setting |
Endpoint type |
Description |
Metadata File Name |
|---|---|---|---|
|
JNDI NIS NetGroup |
JNDI |
For use with LDAP endpoints supporting NIS Netgroup Schema. This template demonstrates advanced association handling. |
jndi_assoc_nisnetgroup_metadata |
|
JNDI inetOrgPerson (Common) |
JNDI |
LDAP inetOrgPerson. This template should be used when no vendor-specific template is required. |
jndi_inetorgperson_common_metadata |
|
Lotus Notes Domino |
JNDI |
Lotus Notes Domino Server. This template allows easy mapping of eTLNDCustomAttribute* and eTLNDCustomCapabilityAttribute* attributes (the latter set are relevant for account template synchronization). |
lnd_metadata |
|
SDK DYN Compound |
Any |
Like SDKDYN but demonstrates use of Compound Values. This template uses compound values which allow complex data to be represented as a single string in JSON syntax, for instance '{"attr1": 42, "attr2": [ "a", "b" ], attr3: { "objName" : "jack" } }' represents a top level object with three attributes, the first is an integer (42), the next is an array of strings and the last a nested object. |
sdkcompound_metadata |
|
SDK DYN |
Any |
Software Development Kit demo connector. This template is a flat (i.e. non-hierarchical) case-sensitive connector that uses the recommended eTDYN* schema to save provisioning information to local files on the CA IAM Connector Server host computer. Because it is flat, its containers are Virtual Containers not actually stored on the endpoint. |
sdkdyn_metadata |
|
SDK DYN Script |
Any |
Like SDKDYN but implemented in Java Script. This template demonstrates how to implement an entire connector (all operation bindings) in JavaScript, as well as configuration information usually found in a connector.xml file, using the connectorXML metadata setting on the top-level namespace. |
sdkscript_metadata |
|
SDK DYN UPO Script |
Any |
Like SDK DYN Script but sends emails rather than writing to local files. This connector has similar functionality to the deprecated C++ UPO connector except that it sends emails rather than writing information to local files. |
sdkuposcript_metadata |
All template files are stored in the Connector Xpress install directory/conf/templates.
Connector Xpress searches this directory recursively to find all applicable templates.
To create a connector, you can create projects that specify how connectors are configured and deployed to the Provisioning Server.
Follow these steps:
The Select Data Source for new Project dialog appears.
The Source Types dialog appears.
The Edit Source dialog appears, specific to the type of data source you are adding.
The Select Data Source for new Project dialog appears and the data source you added appears in the list.
The Enter Password for Data Source Dialog appears.
Connector Xpress does the following:
The Save Project As dialog appears.
Connector Xpress saves the project.
Note: We recommend that you use the default file extension (.con) and that you keep a copy of the project. You cannot view the stored procedure bindings after you deploy a connector, unless you open the Connector Xpress project file where your bindings are stored.
You can start a new project using a template as a starting point for mapping common endpoint schemas.
Follow these steps:
The Select Template dialog appears.
The Select Data Source for a new project dialog appears.
The Endpoint Type Details dialog appears.
You can also start a project by opening a template in wizard mode. When you start a project using the wizard, the wizard steps you through the basic process of mapping an account class, or an account class and group class, depending on the template you selected. You can use the wizard to start a project, and then use the other dialogs to complete your mappings.
The wizard prompts you to complete the following mapping details:
You can use the wizard to complete the basic details of a mapping, such as mappings for account and group attributes. You can use the wizard to start a project, and then use the other dialogs to complete your mappings.
Follow these steps:
The Select template dialog appears.
The Select Data Source for a new project dialog appears.
The Endpoint Type Details dialog appears.
Note: While the wizard is active, the mapping tree is read-only. As you step through the wizard, the relevant node in the mapping tree is expanded and highlighted.
You can create a project based on the contents of eTMetadata and eToperation binding set for both dynamic and static connectors. Creating a project based on existing metadata allows you to:
Creating a project based on existing metadata is useful when:
To review or modify the class mappings and operation bindings for a static or dynamic connector where the original project for the connector does not exist, you can create a project based on existing metadata.
Follow these steps:
The progress dialog appears. If you selected a dynamic connector, Connector Xpress displays the Select Data Source for New project dialog.
Connector Xpress creates the project and populates the mapping tree with the metadata.
To open an existing project, click Project, Open, and double-click the file you want to open from the Open Project dialog.
Connector Xpress opens the project and displays the mappings in your project in the Mapping Tree of the Connector Xpress window.
To reopen a recent project, click Project, Open Recent, and select the project you want to open.
Connector Xpress opens the project and displays the mappings in your project in the Mapping Tree of the Connector Xpress window.
To change the details of a project, you can open a saved project and edit the metadata as required.
Follow these steps:
The Select Data Source for new project dialog appears.
Connector Xpress opens the project, and displays the metadata in the mapping tree of the Connector Xpress window.
The Enter Password for Data Source dialog appears.
After you have created a new dynamic connector, you can save the connector project for future deployment.
Follow these steps:
The Save Project As dialog appears.
Connector Xpress saves the project.
Note: We recommend that you use the default file extension (.con) and that you keep a copy of the project. You cannot view the stored procedure bindings after you deploy a connector, unless you open the Connector Xpress project file where your bindings are stored.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|