Programming Guides › Programming Guide for Java Connector Server › 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.

When ant inst is invoked from jcs-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 jcs-home/build/inst/.

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

The .zip file is directly extracted under a jcs-home directory. Folder names must exactly match the standard names used by the Java CS on which it depends. For example, lib/, extlib/, conf/override/<connector>/ .

All connector jar files are collected in the Java CS lib directory: jcs-home/lib

Note: Restart the Java CS for it to notice new connector .jar files added to its lib/ directory.

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 the Java 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.