File Entries
Some custom tags require that you enter specific parameter values as valid URIs to files. Some webjects also require that you enter specific parameter values as valid URLs to files. In both cases, you are entering the location of a file to execute as defined by the tag or webject. The URI or URL can be relative or absolute:
• Relative URIs and URLs reference files that reside under the root file system directory that is defined for the local Info*Engine task processor.
• Absolute URIs and URLs reference files that reside in the local file system, on a remote HTTP server, or are referenced through an accessible LDAP directory.
Absolute file references can be grouped as follows:
• References starting with file:/// are to the local file system. When specifying drive letters, it is good practice to use all uppercase or all lowercase drive letters. Info*Engine distinguishes between upper and lower case. As a result, if two file references are the same except for the case of the drive letter, then Info*Engine treats those references as two distinct paths.
• References starting with http:// identify files on a remote system.
• References starting with ldap:// identify tasks that are stored in attributes of LDAP entries.
The general format of an LDAP URL is:
ldap://hostname:port/search_base?attribute_names?scope?filter
To specify an LDAP URL, replace each part of the URL with the appropriate value:
◦ hostname:port locates the LDAP directory server. The port can be omitted when the server answers on the default LDAP port, which is port 389.
◦ search_base is the distinguished name identifying the entry that is the root of the subtree that is to be searched.
◦ attribute_names is a comma-separated list of the attributes to be returned from the selected directory entries. By default, all attributes are returned.
◦ scope determines the scope of the search. Valid scope values are:
SUB — for a subtree search.
ONE — for a single-level search.
BASE — to search only the entry identified by the distinguished name.
By default, the scope is set to BASE.
◦ filter defines the search filter. By default, all entries are selected.
To locate an LDAP entry containing a task, you can omit the scope and filter attributes from the format. You specify the distinguished name of LDAP entry containing the task and the attribute name of the attribute in which the task source is stored.