Appendix A - Uniform Resource Identifier : Connector Types That Support URI : Parameters
 
Share this page                  
Parameters
The following table provides the description for the URI parameters.
Parameter
Description
User
User name is an option in the URI. Some schemes (for example, FTP) allows the specification of a user name.
Password
Password is an option in the URI. If password is used, user name must also be used and password follows the user name separated from it by a colon.
The user name and password, if used, are followed by a commercial "at" sign "@". Within the user and password field, any ":", "@", or "/" must be escaped. Note that an empty user name or password is different from no user name or password. You can’t specify a password without specifying a user name.
Example
• ftp://@host.com/ - has an empty user name and no password
• ftp://host.com/ - has no user name
• ftp://user:@host.com/ - has a user name of "user" and an empty password.
Host
Fully qualified domain names take the form as described are a sequence of domain labels separated by decimals. each domain label starting and ending with an alphanumerical character and possibly also containing "-" characters. The rightmost domain label never starts with a digit, though, which syntactically distinguishes all domain names from the IP addresses.
Port
The port number to connect to. Most schemes use protocols that have a default port number. You can specify a different port in the URI. To do this, the port number follows host name and is separated from hostname by a colon.
Example
http://somedomain.com:110 - means "access this host on port 110" instead of the default HTTP port 80.
URL Path
The rest of the locator consists of data specific to the scheme and is known as the "URL path". It supplies the details of how the specified resource can be accessed. Note that the "/" between the host (or port) and the URL path is not part of the URL path. The URL path syntax and how it is interpreted depends on the scheme being used.
Example
http://somedomain.com/private/myweb/vacation/pix/index.html
In this example, the host server is somedomain.com. The balance of the URI is the URL path. This example takes the user to the index located in subdirectory pix, navigating through the directories private, myweb, and vacation.
Alternatives to Accessing Data from URLs
Currently, the extraction of data is limited to public WWW sites, where the navigation to the page is directly accessible with one URL hyperlink – for example, www.yahoo.com. Many URLs are not directly addressable. The following two solutions can help you get the data you are seeking:
• Manual Method
– Design time – Navigate to the desired web page and save it as text to a file. Next, access data by using the Extractor.
– Run time – Navigate to the desired web page and save it as text to a file. Next, access data through Integration Engine.
• Automated Method
– Run time – Program a preprocess "script" in advance with the SDK, Process Designer, or in a user batch file, to access the source. The script then performs Save As to a file and hands-off the saved file to the Integration Engine for processing.