Connector Xpress

Contents
imgc10-in-progress
 
Contents
 
 
 
Connector Xpress Overview
Connector Xpress is a CA Identity Manager utility for managing dynamic connectors, mapping dynamic connectors to endpoints, and establishing routing rules for endpoints. You can use it to configure dynamic connectors to allow provisioning and management of SQL databases and LDAP directories.
Connector Xpress lets you create and deploy custom connectors without extensive technical expertise.
You can also set up, edit, and remove a connector server configuration using Connector Xpress.
The primary input into Connector Xpress is the native schema of an endpoint system. For example, you can use Connector Xpress to connect to an RDBMS and retrieve the SQL schema of the database. You can then use Connector Xpress to construct mappings from those parts of the native schema that are relevant to identity management and provisioning. A mapping describes how the provisioning layer represents an element of the native schema.
Connector Xpress generates metadata that describes, to a dynamic connector, the runtime mappings to a target system.
The output of Connector Xpress is a metadata document produced when you complete your mappings. The metadata is an XML file that describes the structure of your connector to the CA IAM Connector Server.
The output describes the provisioning server classes and attributes and how they are mapped to the native schema.
The metadata is used to create dynamic endpoint types that you can manage with CA Identity Manager.
Communication with Other Components
The following diagram shows the direct and indirect communications between Connector Xpress and other components in the distributed system:
 Communication with other Components 
 The dashed red lines indicate that the direct communications between Connector Xpress and endpoints are read-only. These direct communications occur when setting up data sources.
Supported Databases and Directories
To see the list of directories and databases that Connector Xpress supports, see the Platform Support Matrix. Look for the table named CERTIFIED CONNECTOR XPRESS ENDPOINT TYPES.
Data Sources
A data source is a reference to a server or other source of schema information that Connector Xpress can construct a connector for.
Connector Xpress supports the following data sources from supported vendors:
  •  
    JDBC
     -- Any service accessible through the JDBC API, typically a relational database server.
  •  
    JNDI
     -- Any service accessible through the JNDI API, typically an LDAP server.
Set Up Data Sources
A data source is a reference to a server or other source of schema information that Connector Xpress can construct a connector for.
Connector Xpress supports the following data sources from supported vendors:
  •  
    JDBC
     -- Any service accessible through the JDBC API, typically a relational database server.
  •  
    JNDI
     -- Any service accessible through the JNDI API, typically an LDAP server.
You can connect to a data source to read its schema and then use Connector Xpress to map the schema to a new endpoint type. Connector Xpress maintains a list of data sources that you configure. You can set up JNDI or JDBC data sources.
 When you create a Connector Xpress project, Connector Xpress prompts you to set up your data sources.
 
Follow these steps:
 
  1. Click Tools, Data Sources.
    The Select Data Source for new Project dialog appears.
  2. Click Add.
    The Source Types dialog appears.
  3. Select an available data source type from the list, then click OK.
    The Edit Source dialog appears, specific to the type of data source you are adding.
  4. Complete the fields on the dialog, then click Test to verify your settings and authentication details.
    Depending on the authentication method chosen, a subsequent authentication dialog can appear.
    Complete the fields on this dialog to continue the test.
  5. When the test has completed successfully, click OK.
    You have successfully configured the data source type you selected.
Password Caching
Connector Xpress caches the passwords used with each Provisioning Server only when the application is open. When the application is closed, Connector Xpress does not permanently record passwords. When Connector Xpress needs a password, and the password is not cached, or the cached password causes a failed authentication attempt, Connector Xpress prompts you to enter the password.
Connector Xpress Window
The Connector Xpress window contains the following three panes:
  •  
    Mapping tree
    Displays an overview of the mappings you made for your endpoint. Each node and child node represents an aspect of your endpoint mapping. For example, attributes you have mapped, associations between classes, and operation bindings for your endpoint. Clicking a node displays a dialog that allows you to edit the parameters of the node.
  •  
    Editor panel
    Displays a dialog that lets you edit the parameters for the node you have selected.
  •  
    Provisioning Servers tree
    Displays the endpoints and connectors of multiple Provisioning Servers.
Mapping Tree
The Mapping Tree lets you define the mappings, associations, and operation bindings for your connector. The mapping tree contains the following nodes:
  •  
    Endpoint type node
    Lets you create a description of your endpoint.
  •  
    Classes parent node
    Lets you map a new class and view a read-only list of the classes that you have mapped and the native classes they are mapped to.
  •  
    Class node
    Lets you specify the JDBC database tables or the JNDI native object classes that you want map a class to.
  •  
    Attributes parent node
    Lets you map provisioning attributes to the JDBC database table columns or JNDI object class attributes of the endpoint.
  •  
    Attributes node
    Lets you configure extended details of the selected attribute.
  •  
    Account screens node
    Lets you arrange the attributes you have mapped into the groups and subgroups that you want to appear as tabs and pages in the CA Identity Manager User Console account screens.
  •  
    Associations parent node
    Lets you specify the classes you want to create direct and indirect associations between.
  •  
    Containers parent node
    Lets you specify which object classes you want to use as containers in your connector.
  •  
    Custom Types
    Lets you define arbitrary strings (flexi-strings) you want to use as metadata types in attribute mappings.
  •  
    Operation Bindings
    Lets you specify operation binding information and display a summary of existing operation bindings.
  •  
    Scripts parent node
    Lets you name the script you want to bind to the operation bindings you have mapped.
  •  
    Scripts node
    Lets you specify the parameters of the script you want to bind to the operation bindings you have mapped.
Provisioning Servers Tree
The Provisioning Servers tree (in the lower left pane) lets you manage the endpoints and connectors of multiple Provisioning Servers. The Provisioning Servers tree contains the following fields:
  •  Refresh button
    Refreshes the currently selected node in the Provisioning Tree.
     The Refresh button is only available when you select a tree node that has a changeable list of child nodes. For example, the button is not available for a particular endpoint, as this type of node always has Policies and Endpoint child nodes only. For the endpoints node of a particular endpoint, the button is available.
  •  Action
    Displays the actions you can perform on the currently selected object in the Provisioning Tree. Clicking this button is equivalent to right-clicking the currently selected object in the Provisioning Tree.
  •  
    Provisioning Servers node 
    Lets you add and configure Provisioning Server connection details. When you add a Provisioning Server, Connector Xpress maintains the details of the Provisioning Server so that you can access it each time you run Connector Xpress.
  •  
    Servers Object node
    Displays each registered Provisioning Server on the network. You can use this node to edit or remove the Provisioning Server connection details.
  •  
    Domains Node
    Displays the domain configured for the Provisioning Server.
  •  
    Endpoint Types node
    Displays a list of endpoint types. You can use this node to create an endpoint type.
  •  
    Endpoints Object node
    Lets you do the following:
    • Deploy and edit metadata
    • Delete an endpoint type
    • Clean an endpoint type for DYN endpoint types
    • Set the managing connector server for non-DYN endpoint types only
  •  
    Endpoints node
    Groups endpoints of a particular endpoint type.
  •  
    Endpoints Name node
    Displays an endpoint that you have acquired on the Provisioning Server. You can use this node to:
    • Perform an explore or correlate of the endpoint for DYN endpoints
    • Delete an endpoint
    • Set the managing connector server only for non-DYN endpoints
  •  
    Policies node
    Displays groups of policies of a particular endpoint type.
     A default policy is provided for all endpoint types.
  •  
    CS Config Object node
    Displays a list of CS configurations.
    You can use this node to:
    • Edit the existing configuration for the server's branch DN routing rules
    • Delete a configuration entry
    • Set the managing connector server password
  •  
    CS Configs node
    Displays logical groupings of CA IAM Connector Server configurations. These configurations contain the DSFConfig style routing rules for managing branch DNs. You can use this node to add a new routing rules configuration object for a C++ Connector Server or CA IAM Connector Server service.
  •  
    Connector Servers Node
    Displays the endpoint types, endpoints, and the dynamic endpoint types that the selected Connector Server manages.
Where Connector Xpress Stores User Preferences
Connector Xpress stores user preferences through the Java Preferences API.
On Windows, this stores data in the following registry key:
HKEY_CURRENT_USER\Software\JavaSoft\Prefs
On UNIX, this stores data in the user's home directory under the .java/.userPrefs folder.
The uninstaller does not remove this data, so subsequent installs preserve user preferences.