Data Sources

Data Source Names (kourier_datasource_def.aspx)

Purpose

Create Data Source Names (DSNs) that Kourier Integrator uses to transfer data between U2 and other applications. A DSN comprises a name, class, address and the associated credentials.

Refer to the Kourier DSN Guide for more information on the use of DSNs.

Available Toolbar Commands

	Click the New icon in the toolbar to save the current Data Source Name and then clear the page making it ready for a new item.
	Click the Save icon in the toolbar to save the current Data Source Name and return to the Define Data Sources listing.
	Click the Delete icon in the toolbar to delete the current Data Source Name . You will be prompted with a "Are you sure you want to delete?" dialog. Clicking Yes will permanently delete the Data Source and then return to the Data Sources listing. Click Cancel to return to the existing export without deleting.
	Click the Help balloon to open the help for this page.

File/Key Field

KT_QUEUES/DSN ID

Prerequisites

If an address contains user-defined literals, they should be entered using Substitution Literals

Cautions

None

Fields

Name	Enter the name of the DSN record. By convention, it includes a prefix that associates it to an application and a general purpose. It can also describe its location and direction.
Description	Enter the description for the DSN. This should provide enough information to explain how the DSN is used.
Class	Select a pre-defined DSN class to designate how Kourier will transfer data using this DSN. The class also specifies how the address field is interpreted in order to perform the transfer. IMPORTANT: An improperly configured DSN can result in database corruption. When defining a DSN for access to a local OS files, using the DATA-class DSN provides the greatest amount of protection against such corruption. Only those classes that are delivered with Kourier can be used. For information on the different classes and how they work, refer to the Kourier DSN Guide.
Address	Enter the address that defines this DSN. The syntax for addresses depends on the DSN Class. For information on specifying addresses and how they work, refer to the Kourier DSN Guide. WARNING: It is possible to accidentally specify an address that can corrupt your database. It is important to specify addresses using the syntax that is consistent with the class. Make sure that you use the proper syntax as documented. Addresses can contain substitution tags that can specify dynamic values when the message is transferred. Use these tags when the address cannot be fully specified at design time or if you want to have the flexibility of changing certain values that are shared between DSNs.
Username	If this DSN has restricted access, enter the username portion of the user's credentials when connecting to the remote system. TIP: If you need to include the domain name in a Username make sure to enter two backslashes since the backslash character is the escape character in java applications (which Kourier uses to support FTP type DSNs). Credentials are only supported in certain DSN classes. For information on the different classes and how they work, refer to the Kourier DSN Guide.
Password	If this DSN has restricted access, enter the password portion of the user's credentials when connecting to the remote system. Credentials are only supported in certain classes. For information on the different classes and how they work, refer to the Kourier DSN Guide.
Use Binary Control	This option is valid only when using the FTP Class. Select this checkbox if you want to transfer data using binary FTP. This capability will prevent the system from adding an additional CR (carriage return) to the end of each line when it is moved from UNIX to Microsoft Windows.
Use Concurrency Control	This option is valid only when using the FTP Class. Select this checkbox to cause the system to send the file with an alternate name and then when the file transfer is complete the file will be renamed to the actual file name. This capability will aid in reducing potential file concurrency issues, which can occur when polling for files with a specific name or extension.