Naming the Adapter in INSTANCE Parameters

To provide the ability to connect to other adapters if a specific adapter is not available, the INSTANCE parameter can be multi-valued. Info*Engine attempts to connect to the adapters in the order given. If the first adapter specified is not available, the next adapter listed is tried, and so on, until a connection is made. If a connection cannot be established with any listed adapter, an error is returned.

In conjunction with this parameter, you can include two other parameters that enable fail-over and load balancing: CONNECTION_ATTEMPTS and CONNECTION_ATTEMPT_INTERVAL.

Defines the maximum number of times to attempt establishing a connection to an adapter before returning an error. The default value is 1. This parameter is optional.

If multiple INSTANCE parameter values are specified, the value of CONNECTION_ATTEMPTS defines the maximum number of times to iterate through the list of adapter instances.

Defines the amount of time, in seconds, to delay between connection attempts. The default value is 60 seconds. This parameter is optional.

If multiple INSTANCE parameter values are specified, the value of CONNECTION_ATTEMPT_INTERVAL defines the number of seconds to wait between the attempts to iterate through the entire list of adapter instances.

You define the adapter name to use in the INSTANCE parameter when you configure the adapter through the Info*Engine Property Administration utility.

An adapter name can be one of the following forms:

This is defined in the Service Name field on the Info*Engine Property Administration LDAP form.

Simple names are stored in the ptcServiceName attribute of the adapter LDAP entry. To use a simple name, the adapter LDAP entry must reside within the Naming Service search path.

For example, assume that “com.myCompany.myHost.sapAdapter” is the ptcServiceName attribute of the adapter LDAP entry in the Naming Service search path. Then, the following INSTANCE parameter can be used:

When configuring the adapter, you specify the distinguished name in the Info*Engine Property Administration form. This name consists of the ptcServiceName attribute and the other attributes that define the location of the LDAP entry.

For example, assume that the “com.myCompany.myHost.sapAdapter” entry is located on “host1” at “dc=IeProps,dc=myHost,dc=myCompany, dc=com,ou=Applications,o=myCompany.” Then, the following INSTANCE parameter can be used:

<ie:param name="INSTANCE" data="ldap://host1/
ptcServiceName=com.myCompany.myHost.sapAdapter,
dc=IeProps,dc=myHost,dc=myCompany,dc=com,
ou=Applications,o=myCompany"/>

This is just another way of identifying the distinguished name. An Info*Engine domain-based reference name uses the following format:

◦ dc_attributes are the dc attributes that make up the domain location of the LDAP entry. Each attribute is separated from the next attribute using a period.

◦ When constructing the LDAP directory in which the Info*Engine entries are located, you use dc=com as a root-level entry and other dc attributes for subtree entries

◦ The Naming Service .serviceDomainBase property is set to include those attributes beyond the domain that are used in the distinguished name of the entry.

For example, assume that the ptcServiceName attribute value is “com.myCompany.myHost.sapAdapter” and that the entry is located in the “dc=myHost,dc=myCompany,dc=com,ou=Applications, o=myCompany” branch, then the following domain-based reference name could only be used in the INSTANCE parameter if the .serviceDomainBase property is set to “ou=Applications,o=myCompany”:

<ie:param name="INSTANCE" data="com.myCompany.myHost.
sapAdapter@myHost.myCompany.com"/>

Use the Info*Engine Property Administration utility to set the .serviceDomainBase property.