Configuring In-Process Adapters and Gateways

When a native adapter or gateway runs exclusively in the same Java Virtual Machine (JVM) as the SAK, the adapter or gateway does not need its own port for communication. Examples of in-process adapters and gateways include a servlet running within a JSP application or a task processor. In these instances, the SAK must be able to locate the class files that are associated with the adapter or gateway.

To provide the required information, you must include the following attributes in the LDAP entry for the adapter or gateway:

• A service name for the adapter or gateway. This is usually the name that users enter on the webject INSTANCE parameter to access the adapter or gateway.

The name you enter should be unique within the Naming Service search base (unless you are providing redundant services for load balancing or failures). To name your adapter or gateway service, use the LDAP naming convention set up by your site. The convention that is used by default is described in Info*Engine LDAP Directories.

• The distinguished name of the LDAP entry. By default, the Info*Engine Property Administration utility suggests a distinguished name that is based on the base URI you entered when you started the administrator and the service name.

As you enter a value in the Service Name field, the ptcServiceName attribute in the distinguished name is updated to include the service name changes. To ensure that the correct LDAP entry is created for the service, you should not manually modify the ptcServiceName attribute. If you want the entry to reside at a LDAP directory location that is different from the default location, you can modify the other attributes in the distinguished name.

Initially, the Property Administration utility populates the Runtime Service Name field with the same name it enters in the Service Name field. If you delete the runtime service name, the service name you enter becomes the runtime service name. The runtime service name is prepended to the properties that are set. The properties starting with this name are used when the adapter or gateway is instantiated.

• The service class. This attribute identifies the class files used for the adapter or gateway.

• Adapter or gateway properties as described in the corresponding adapter guide or the help that is available from the Property Administration utility.

To configure an Info*Engine server to support in-process adapters, you must include the adapter class files in the codebase of the server. If the adapter class files are contained in the lib or classes directory within the codebase/WEB-INF directory, no changes are required.