Programming Guides › Connector Programming Guide › Configuration Files › Connector Jar Files

Connector Jar Files

The -dist target packages the connector in its build.xml file as a single file named jcs-connector-*.jar which can depend on separate external third-party libraries .jar files. This JAR file is then used by the bundle builder to create the OSGI version JAR File.

When ant inst is invoked from cs-sdk-home, a connectors’ build.xml file is asked to execute its -inst task which must create a single consolidated jcs-connector-*.zip file in cs-home/build/inst/.

The zip file includes every file it deploys to a production CA IAM CS. For example, its jcs-connector-*.jar file, any third-party libraries, and all sources of configurations settings.

A connector can be installed in these two ways:

• Before installing CA IAM CS, create a bundle for the connector and copy it to the directory that contains the install files. When you install CA IAM CS, the new connector will be installed too.
• Log in to CA IAM CS and add the new connector. For instructions, see Add a Connector in the Connectors Guide.

The contents of a jcs-connector-*.jar file are:

• /conf/connector.xml—This file is converted into a com.ca.jcs.ImplBundle JavaBean using the Spring Framework XML support. This file is the major descriptor for the connector in the same way that the /WEB-INF/web.xml is for a .war file used to deploy a J2EE web application.
• /conf/*_openldap.schema— Connectors that make their own connector-specific schemas known to the ApacheDS server hosting CA IAM CS use this optional file. Verify that this file is in the format dictated by the OpenLDAP standard.
• /conf/*_metadata.xml—Connectors that have static metadata or metadata maintained by developers rather than users can use this optional file. Such connectors are referred to as static connectors, as opposed to dynamic connectors where metadata is generated dynamically in Connector Xpress by users.