Specifying URIs and URLs
Info*Engine parameters can require that you specify URIs or URLs as their values.
 |
The URIs and URLs use the forward slash as the separator (/) in paths even though the back slash (\) is the directory separator used on Windows systems. Info*Engine correctly identifies all system URIs and URLs when you specify the forward slash. You should only use a back slash in URIs where a back slash is being used outside of the context of use as a path separator.
|
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.
LDAP Search Base Entries
In other cases, including several tags in the directory tag library, you might be required to enter an LDAP URL that identifies a search base LDAP entry. Using the format listed above, this type of entry uses only the search_base attribute:
ldap://hostname:port/search_base
Example File Locations
Example URI locations of a task1.xml task file are as follows:
• Assume that the file resides in the C:\ptc\Windchill\tasks\infoengine\jdbc directory and that C:\ptc\Windchill\tasks is the root file directory of the local task processor. Then use the following relative URI to locate the file:
uri="infoengine/jdbc/task1.xml"
• Assume that the file resides on the local file system in the D:\ie\jdbc directory. Then use the following absolute URI to locate the file:
uri="file:///D:/ie/jdbc/task1.xml"
• Assume that the file resides in the opt/ptc/Windchill/infoengine/tasks/jdbc directory on the svr2 remote host. Then use the following absolute URI to locate the file:
uri="http://svr2/opt/ptc/Windchill/infoengine/tasks/jdbc/task1.xml"
• Assume that the task resides in an LDAP server on the cn=IEtasks node and that the name of the attribute where the task is stored is ptcCommandDelegateCode. Also assume that the server host name is srv3 and the dc attributes are myHost and com. Then use the following absolute URI to locate the task:
uri="ldap://srv3/cn=IEtasks,dc=myHost,dc=com?
ptc.CommandDelegateSource"
ptc.CommandDelegateSource"