Database Connection Properties

This section describes the connection properties you can specify for databases supported by DataDirect XQuery.

See Specifying Connection URIs for information about the format of connection URLs and specifying connection properties in connection URLs.

This section provides information for the following supported databases:

DB2

DB2

This section describes the connection properties you can specify for DB2 and provides information about how DataDirect XQuery creates DB2 packages.

Table E-9 lists the connection properties supported for DB2 by DataDirect XQuery.

Table E-9. DB2 Connection Properties
DB2 Property	Description
AuthenticationMethod	{kerberos \| encryptedUIDPassword \| encryptedPassword \| clearText \| client}. Determines which authentication method DataDirect XQuery uses when establishing a connection. If set to kerberos, DataDirect XQuery uses Kerberos authentication. DataDirect XQuery ignores any user ID or password specified. See Using Kerberos Authentication for more information about using Kerberos. If set to encryptedUIDPassword, DataDirect XQuery uses user ID/password authentication. DataDirect XQuery sends an encrypted user ID and password to the DB2 server for authentication. If a user ID and password are not specified, an exception is thrown. If set to encryptedPassword, DataDirect XQuery uses user ID/password authentication. DataDirect XQuery sends a user ID in clear text and an encrypted password to the DB2 server for authentication. If a user ID and password are not specified, an exception is thrown. If set to clearText (the default), DataDirect XQuery uses user ID/password authentication. DataDirect XQuery sends the user ID and password in clear text to the DB2 server for authentication. If a user ID and password are not specified, an exception is thrown. If set to client, DataDirect XQuery uses client authentication. The DB2 server relies on the client to authenticate the user and does not provide additional authentication. DataDirect XQuery ignores any user ID or password specified. The User property provides the user ID. The Password property provides the password. If the specified authentication method is not supported by the DB2 server, the connection fails and an exception is thrown.
CreateDefaultPackage	{true \| false}. If set to true, the required DB2 packages are automatically created even if they already exist. Existing DB2 packages are replaced by the new packages. If set to false (the default), the required DB2 packages are created automatically only if they do not already exist. For DB2 for Linux/UNIX/Windows, this property must be used in conjunction with the ReplacePackage property. For DB2 for z/OS and DB2 for iSeries, DB2 packages are created in the collection or library specified by the PackageCollection property. See Creating DB2 Packages for more information about creating DB2 packages.
DatabaseName Required for Linux/UNIX/Windows	The name (DB2 for Linux/UNIX/Windows) or location name (DB2 for z/OS and DB2 for iSeries) of the database you want to connect to.
DynamicSections	The maximum number of prepared statements that can be open at any time. This value must be a positive integer. The default is 200.
Grantee	The name of the schema to which you want to grant EXECUTE privileges for DB2 packages. The value must be a valid DB2 schema. This property is ignored if the GrantExecute property is set to false. The default is PUBLIC. See Creating DB2 Packages for more information about creating DB2 packages.
GrantExecute	{true \| false}. Determines which DB2 schema is granted EXECUTE privileges for DB2 packages. If set to true (the default), EXECUTE privileges are granted to the schema specified by the Grantee property. If set to false, EXECUTE privileges are granted to the schema that created the DB2 packages. See Creating DB2 Packages for more information about creating DB2 packages.
InitializationString	Specifies one or multiple SQL commands to be executed by DataDirect XQuery after it has established the connection to the database and has performed all initialization for the connection. Multiple commands must be separated by semicolons. In addition, if this property is specified in a connection URL, the entire value must be enclosed in parentheses when multiple commands are specified. The following example adds USER2 to the CURRENT PATH special register and sets the CURRENT PRECISION special register to DEC31. `jdbc:xquery:db2://server1:50000; InitializationString=(SET CURRENT PATH=current_path, USER2;SET CURRENT PRECISION='DEC31')` NOTE: Setting the CURRENT PRECISION special register is only valid for DB2 for z/OS. If the execution of a SQL command fails, the connection attempt also fails and DataDirect XQuery raises an exception indicating which SQL command or commands failed.
LocationName Required for z/OS and iSeries if DatabaseName is not specified	The name of the DB2 location that you want to access. For DB2 for z/OS, your system administrator can determine the name of your DB2 location using the following command: `DISPLAY DDF` For DB2 for iSeries, your system administrator can determine the name of your DB2 location using the following command. The name of the database that is listed as *LOCAL is the value you should use for this property. `WRKRDBDIRE` This property is supported only for DB2 for z/OS and DB2 for iSeries.
PackageCollection	The name of the collection or library (group of packages) to which DB2 packages are bound. The default is NULLID. This property is ignored for DB2 for Linux/UNIX/Windows.
PackageOwner	The owner to be used for any DB2 packages that are created. The default is null. See Creating DB2 Packages for more information about creating DB2 packages.
Password	A case-sensitive password used to connect to your DB2 database. A password is required only if user ID/password authentication is enabled on your database. Contact your system administrator to obtain your password.
ReplacePackage	{true \| false}. Specifies whether the current bind process will replace the existing DB2 packages. If set to true, the current bind process will replace the existing DB2 packages. If set to false (the default), the current bind process will not replace the existing DB2 packages. For DB2 for Linux/UNIX/Windows, this property must be used in conjunction with the CreateDefaultPackage property. See Creating DB2 Packages for more information about creating DB2 packages.
SecurityMechanism DEPRECATED	This property is recognized for backward compatibility, but we recommend that you use the AuthenticationMethod property to set the authentication method used by DataDirect XQuery.
User	The case-sensitive user name used to connect to the DB2 database.

Creating DB2 Packages

DataDirect XQuery automatically creates all required DB2 packages at connection time, which, by default, contain 200 dynamic sections and are created in the NULLID collection (or library). You can override the default number of dynamic sections by setting the DynamicSections property. Similarly, you can override the collection in which packages are created by setting the PackageCollection property.

NOTE: The initial connection may take a few minutes because of the number and size of the packages that must be created for the connection. Subsequent connections do not incur this delay.

In most cases, you do not need to create DB2 packages because they are automatically created at connection time. If, for some reason, you need to explicitly create them, you can create them using the following sets of connection properties.

NOTE: The user ID creating the DB2 packages must have BINDADD privileges on the database. Consult with your database administrator to ensure that you have the correct privileges.

For DB2 for Linux/UNIX/Windows

CreateDefaultPackage=true

ReplacePackage=true

DynamicSections=x (where x is a positive integer)

NOTE: To create new DB2 packages, you must use ReplacePackage=true in conjunction with CreateDefaultPackage=true. If a DB2 package already exists, it is replaced when ReplacePackage=true.

The following URL creates DB2 packages with 400 dynamic sections. If any DB2 packages already exist, they are replaced by the new ones being created.

jdbc:xquery:db2://server1:50000;databaseName=SAMPLE;
createDefaultPackage=TRUE;replacePackage=TRUE;dynamicSections=400

For DB2 for z/OS and iSeries

PackageCollection=collection_name (where collection_name is the name of the collection or library to which DB2 packages are bound)

CreateDefaultPackage=true

DynamicSections=x (where x is a positive integer)

The following URL creates DB2 packages with 400 dynamic sections.

jdbc:xquery:db2://server1:50000;locationName=SAMPLE;
packageCollection=DEFAULT;createDefaultPackage=TRUE;dynamicSections=400

Informix

This section describes the connection properties you can specify for Informix.

Table E-10 lists the connection properties supported for Informix by DataDirect XQuery.

Table E-10. Informix Connection Properties
Informix Property	Description
DatabaseName	The name of the database you want to which you want to connect. If this property is not specified, a connection is established to the specified server without connecting to a particular database.
InformixServer Required	The name of the Informix database server to which you want to connect.
InitializationString	Specifies one or multiple SQL commands to be executed by DataDirect XQuery after it has established the connection to the database and has performed all initialization for the connection. For example: `InitializationString=command` Multiple commands must be separated by semicolons. In addition, if this property is specified in a connection URL, the entire value must be enclosed in parentheses when multiple commands are specified. For example: `jdbc:xquery:informix://server1:2003;informixServer=test_server;databaseName=test;initializationString=(command1;command2)` If the execution of a SQL command fails, the connection attempt also fails and DataDirect XQuery raises an exception indicating which SQL command or commands failed.
Password	A case-insensitive password used to connect to your Informix database. A password is required only if user ID/password authentication is enabled on your database. If so, contact your system administrator to obtain your password.
User	The case-insensitive default user name used to connect to your Informix database. A user name is required only if user ID/password authentication is enabled on your database. If so, contact your system administrator to obtain your user name.

Microsoft SQL Server

This section describes the connection properties you can specify for Microsoft SQL Server.

Table E-11 lists the connection properties supported for Microsoft SQL Server by DataDirect XQuery.

Table E-11. Microsoft SQL Server Connection Properties
SQL Server Property	Description
AuthenticationMethod	{auto \| kerberos \| ntlm \| userIdPassword}. Determines which authentication method DataDirect XQuery uses when establishing a connection. If set to auto (the default), DataDirect XQuery uses SQL Server authentication, Kerberos authentication, or NTLM authentication when establishing a connection. DataDirect XQuery selects an authentication method based on a combination of criteria such as whether the application provides a user ID, DataDirect XQuery is running on a Windows platform, and DataDirect XQuery can load the DLL required for NTLM authentication. If set to kerberos, DataDirect XQuery uses Kerberos authentication. DataDirect XQuery ignores any user ID or password specified. See Using Kerberos Authentication for more information about using Kerberos. If set to ntlm, DataDirect XQuery uses NTLM authentication if the DLL required for NTLM authentication can be loaded. If DataDirect XQuery cannot load the DLL, DataDirect XQuery raises an error. DataDirect XQuery ignores any user ID or password specified. See Using NTLM Authentication for more information about NTLM authentication. If set to userIdPassword, DataDirect XQuery uses SQL Server authentication when establishing a connection. If a user ID is not specified, an exception is thrown. The User property provides the user ID. The Password property provides the password.
DatabaseName	The name of the database to which you want to connect.
InitializationString	Specifies one or multiple SQL commands to be executed by DataDirect XQuery after it has established the connection to the database and has performed all initialization for the connection. For example: `InitializationString=command` Multiple commands must be separated by semicolons. In addition, if this property is specified in a connection URL, the entire value must be enclosed in parentheses when multiple commands are specified. For example: `jdbc:xquery:sqlserver://server1:1433;databaseName=test;initializationString=(command1;command2)` If the execution of a SQL command fails, the connection attempt also fails and DataDirect XQuery raises an exception indicating which SQL command or commands failed.
LoadLibraryPath	Specifies the directory DataDirect XQuery looks in for the DLL used for NTLM authentication. The value is the fully qualified path of the directory that contains the DLL. When you install DataDirect XQuery, the NTLM DLLs are placed in the install_dir/lib subdirectory, where install_dir is the DataDirect XQuery installation directory. By default, DataDirect XQuery looks for the NTLM authentication DLLs in a directory on the Windows system path defined by the PATH environment variable. If you install DataDirect XQuery in a directory that is not on the Windows system path, you can set this property to specify the location of the NTLM authentication DLLs. For example, if you install DataDirect XQuery in a directory named "DataDirect" that is not on the Windows system path, you can use this property to specify the directory containing the NTLM authentication DLLs. jdbc:xquery`:sqlserver://server3:1433; databaseName=test;loadLibraryPath=C:\DataDirect\lib; User=test;Password=secret` See Using NTLM Authentication for more information about NTLM authentication.
Password	A case-insensitive password used to connect to your Microsoft SQL Server database. A password is required only if user ID/password authentication is enabled on your database. If so, contact your system administrator to obtain your password.
User	The case-insensitive user name used to connect to your Microsoft SQL Server database. A user name is required only if user ID/password authentication is enabled on your database. If so, contact your system administrator to obtain your user name.

MySQL Enterprise

This section describes the connection properties you can specify for MySQL Enterprise.

NOTE: You must purchase commercially licensed MySQL database software or a MySQL Enterprise subscription in order to use DataDirect XQuery with MySQL software.

Table E-12 lists the connection properties supported for MySQL Enterprise by DataDirect XQuery.

Table E-12. MySQL Enterprise Connection Properties
MySQL Enterprise Property	Description
DatabaseName	The name of the database you want to connect to.
InitializationString	Specifies one or multiple SQL commands to be executed by DataDirect XQuery after it has established the connection to the database and has performed all initialization for the connection. For example: `InitializationString=command` Multiple commands must be separated by semicolons. In addition, if this property is specified in a connection URL, the entire value must be enclosed in parentheses when multiple commands are specified. For example: `jdbc:xquery:mysql://server1:3306;databaseName=test;initializationString=(command1;command2)` If the execution of a SQL command fails, the connection attempt also fails and DataDirect XQuery raises an exception indicating which SQL command or commands failed.
Password	A case-insensitive password used to connect to your MySQL Enterprise database. A password is required only if user ID/password authentication is enabled on your database. If so, contact your system administrator to obtain your password.
User	The case-insensitive default user name used to connect to your MySQL Enterprise database. A user name is required only if user ID/password authentication is enabled on your database. If so, contact your system administrator to obtain your user name.

Oracle

This section describes the connection properties you can specify for Oracle and provides information about using tnsnames.ora files to specify connection information to an Oracle database.

Table E-13 lists the connection properties supported for Oracle by DataDirect XQuery.

Table E-13. Oracle Connection Properties
Oracle Property	Description
AuthenticationMethod	{auto \| kerberos \| kerberosUIDPassword \| ntlm \| client \| userIDPassword}. Determines which authentication method DataDirect XQuery uses when establishing a connection. If set to auto (the default), DataDirect XQuery uses user ID/password, Kerberos, or NTLM authentication when establishing a connection. DataDirect XQuery selects an authentication method based on a combination of criteria, such as whether the application provides a user ID, DataDirect XQuery is running on a Windows platform, and DataDirect XQuery can load the DLL required for NTLM authentication. If set to kerberos, DataDirect XQuery uses Kerberos authentication. DataDirect XQuery ignores any user ID or password specified. If set to kerberosUIDPassword, DataDirect XQuery first uses Kerberos to authenticate the user. Next, DataDirect XQuery reauthenticates the user using user ID/password authentication. If a user ID and password are not specified, DataDirect XQuery throws an exception. If either Kerberos or user ID/password authentication fails, the connection attempt fails and DataDirect XQuery throws an exception. If set to ntlm, DataDirect XQuery uses NTLM authentication if the DLL required for NTLM authentication can be loaded. If DataDirect XQuery cannot load the DLL, it throws an exception. DataDirect XQuery ignores any user ID or password specified. This value is supported for Windows clients only. See Using NTLM Authentication for more information about NTLM authentication. If set to client, DataDirect XQuery uses client authentication. The Oracle database server relies on the client to authenticate the user and does not provide additional authentication. DataDirect XQuery ignores any user ID or password specified. If set to userIdPassword, DataDirect XQuery uses user ID/password authentication. If a user ID and password are not specified, an exception is thrown. The User property provides the user ID. The Password property provides the password.
InitializationString	Specifies one or multiple SQL commands to be executed by DataDirect XQuery after it has established the connection to the database and has performed all initialization for the connection. For example: `initializationString=command` Multiple commands must be separated by semicolons. In addition, if this property is specified in a connection URL, the entire value must be enclosed in parentheses when multiple commands are specified. For example: `jdbc:xquery:oracle://server1:1521;ServiceName=ORCL;iInitializationString=(command1;command2)` If the execution of a SQL command fails, the connection attempt also fails and DataDirect XQuery raises an error indicating which SQL command or commands failed.
LoadLibraryPath	Specifies the directory DataDirect XQuery looks in for the DLL used for NTLM authentication. The value is the fully qualified path of the directory that contains the DLL. When you install DataDirect XQuery, the NTLM DLLs are placed in the install_dir/lib subdirectory, where install_dir is the DataDirect XQuery installation directory. By default, DataDirect XQuery looks for the NTLM authentication DLLs in a directory on the Windows system path defined by the PATH environment variable. If you install DataDirect XQuery in a directory that is not on the Windows system path, you can set this property to specify the location of the NTLM authentication DLLs. For example, if you install DataDirect XQuery in a directory named "DataDirect" that is not on the Windows system path, you can use this property to specify the directory containing the NTLM authentication DLLs. `jdbc:xquery:oracle://server3:1521;serviceName=ORCL;loadLibraryPath=C:\DataDirect\lib;User=test;Password=secret` See Using NTLM Authentication for more information about NTLM authentication.
Password	A case-insensitive password used to connect to your Oracle database. A password is required only if user ID/password authentication is enabled on your database. If so, contact your system administrator to obtain your password.
ServiceName	The database service name that specifies the database used for the connection. This property is mutually exclusive with the SID property. The service name is a string that is the global database name—a name that typically comprises the database name and domain name. For example: `sales.us.acme.com` This property is useful to specify connections to an Oracle Real Application Clusters (RAC) system rather than a specific Oracle instance because the nodes in a RAC system share a common service name. If using a tnsnames.ora file to provide connection information, do not specify this property. See Using Oracle tnsnames.ora Files for information about specifying the database service name using a tnsnames.ora file.
SID	The Oracle System Identifier that refers to the instance of the Oracle database running on the server. The default is ORCL, which is the default SID that is configured when installing your Oracle database. If using a tnsnames.ora file to provide connection information, do not specify this property. See Using Oracle tnsnames.ora Files for information about specifying an Oracle SID using a tnsnames.ora file.
TNSNamesFile	The path and filename to the tnsnames.ora file from which connection information is retrieved. The tnsnames.ora file contains connection information that is mapped to Oracle net service names. Using a tnsnames.ora file to centralize connection information simplifies maintenance when changes occur. The value of this property must be a valid path and filename to a tnsnames.ora file. If you specify this property is specified, then: Also specify the TNSServerName property. Do not specify any of following: PortNumber (in URL), ServerName (in URL), or SID (connection property). If any of this connection information is specified in addition to this property, an error is generated. See Using Oracle tnsnames.ora Files for information about using tnsnames.ora files to connect.
TNSServerName	The Oracle net service name used to reference the connection information in a tnsnames.ora file. The value of this property must be a valid net service name entry in the tnsnames.ora file specified by the TNSNamesFile property. If this property is specified, you also must specify the TNSNamesFile property. If this property is specified, do not specify any of the following connection information to prevent conflicts: PortNumber (in URL) ServerName (in URL) SID (connection property) If any of this connection information is specified in addition to this property, an error is generated. See Using Oracle tnsnames.ora Files for information about using tnsnames.ora files to connect.
User	The case-insensitive user name used to connect to your Oracle database. A user name is required only if user ID/password authentication is enabled on your database. If so, contact your system administrator to obtain your user name.

Using Oracle tnsnames.ora Files

The tnsnames.ora file is used to map connection information for each Oracle service to a logical alias. DataDirect XQuery can retrieve basic connection information from a tnsnames.ora file, including:

Oracle server name and port

Oracle System Identifier (SID) or Oracle service name

In a tnsnames.ora file, connection information for an Oracle service is associated with an alias, or Oracle net service name. Each net service name entry contains connect descriptors that define listener and service information. The following example in Figure E-1 shows connection information in a tnsnames.ora file configured for the net service name entry, FITZGERALD.SALES.

Figure E-1. tnsnames.ora Example

FITZGERALD.SALES = 
  (DESCRIPTION =  
    (ADDRESS = (PROTOCOL = TCP)(HOST = server1)(PORT = 1521)) 
       (CONNECT_DATA = 
          (SID = ORCL) 
       ) 
  )

Using this example, if the Oracle net service name entry FITZGERALD.SALES is referenced, DataDirect XQuery would connect to the Oracle database instance identified by the Oracle SID ORCL (SID=ORCL).

Typically, a tnsnames.ora file is installed when you install an Oracle database. By default, the tnsnames.ora file is located in the ORACLE_HOME\network\admin directory on Windows and the $ORACLE_HOME/network/admin directory on UNIX and Linux.

Connecting to the Database

To retrieve connection information from an Oracle tnsnames.ora file, you must inform DataDirect XQuery which tnsnames.ora file (using the TNSNamesFile property) and Oracle service name entry (using the TNSServerName property) to use so that the correct connection information is referenced. For example, the following connection URL:

jdbc:xquery:oracle:TNSNamesFile=c:\oracle92\NETWORK\ADMIN\tnsnames.ora;
TNSServerName=FITZGERALD.SALES

specifies the path and filename of the tnsnames.ora file (TNSNamesFile=c:\oracle92\NETWORK\ADMIN\tnsnames.ora) and the net service name entry (TNSServerName=FITZGERALD.SALES) to use for the connection.

NOTE: The connection URL does not specify the server name and port of the database server; that information is specified in the tnsnames.ora file referenced by the TNSNamesFile property.

If using tnsnames.ora files with a Security Manager on a Java 2 Platform, read permission must be granted to the tnsnames.ora file. For example:

grant codeBase "file:/install_dir/lib/-" { 
   permission java.io.FilePermission "C:\\oracle\\ora92\\network\\admin\\
      tnsnames.ora", "read"; 
};

where install_dir is the DataDirect XQuery installation directory.

Configuring the tnsnames.ora File

If using a tnsnames.ora file to retrieve connection information, do not specify any of the following connection information in a connection URL or property to prevent conflicts:

PortNumber (in URL)

ServerName (in URL)

ServiceName (connection property)

SID (connection property)

Table E-14 lists the Oracle connection properties that correspond to tnsnames.ora connect descriptor parameters.

Table E-14. Oracle Connection Property Mappings to tnsnames.ora Connect Descriptor Parameters
Oracle Connection Property	tnsnames.ora Parameter
PortNumber = port	PORT = port The ADDRESS_LIST parameter contains connection information for one or multiple servers, using the ADDRESS parameter to specify the primary and alternate servers. The PORT parameter is used within the ADDRESS parameter to specify the port number for each server entry. For example: `(ADDRESS_LIST=` `(ADDRESS= (PROTOCOL = TCP)(HOST = server1) (PORT = 1521))` `...` ) A port of 1521, the default port number when installing an Oracle database, is specified for server1.
ServerName = server_name	HOST = server_name The ADDRESS_LIST parameter contains connection information for one or multiple servers, using the ADDRESS parameter to specify the primary and alternate servers. The HOST parameter is used within the ADDRESS parameter to specify the server name for each server entry. The server entry can be an IP address or a server name. For example: `(ADDRESS_LIST=` `(ADDRESS= (PROTOCOL = TCP)(HOST = server1) (PORT = 1521))` `...` ) The server name server1 is specified in the first server entry.
ServiceName = service_name	SERVICE_NAME = service_name The database service name that specifies the database used for the connection. The service name is a string that is the global database name—a name that typically comprises the database name and domain name. For example: `sales.us.acme.com` The service name is specified in the CONNECT_DATA parameter. For example: `(CONNECT_DATA= (SERVICE_NAME=sales.us.acme.com)` ) This parameter is mutually exclusive with the SID attribute and is useful to specify connections to an Oracle Real Application Clusters (RAC) system rather than a specific Oracle instance.
SID = SID	SID = SID The Oracle System Identifier (SID) that refers to the instance of the Oracle database running on the server. The default Oracle SID that is configured when installing your Oracle database software is ORCL. The SID is specified in the CONNECT_DATA parameter. For example: `(CONNECT_DATA= (SID=ORCL) )` This parameter is mutually exclusive with the SERVICE_NAME attribute.

For more information about configuring tnsnames.ora files, refer to your Oracle documentation.

PostgreSQL

Refer to your PostgreSQL JDBC driver documentation for information about connection properties supported by the PostgreSQL JDBC driver.

Sybase

This section describes the connection properties you can specify for Sybase.

Table E-15 lists the connection properties supported for Sybase by DataDirect XQuery.

Table E-15. Sybase Connection Properties
Sybase Property	Description
AuthenticationMethod	{kerberos \| userIdPassword}. Determines which authentication method DataDirect XQuery uses when establishing a connection. If set to kerberos, DataDirect XQuery uses Kerberos authentication. DataDirect XQuery ignores any user ID or password specified. If you set this value, you also must set the ServicePrincipalName property. See Using Kerberos Authentication for more information about using Kerberos. If set to userIdPassword (the default), DataDirect XQuery uses user ID/password authentication. If a user ID and password are not specified, an exception is thrown. The User property provides the user ID. The Password property provides the password.
InitializationString	Specifies one or multiple SQL commands to be executed by DataDirect XQuery after it has established the connection to the database and has performed all initialization for the connection. For example: `InitializationString=command` Multiple commands must be separated by semicolons. In addition, if this property is specified in a connection URL, the entire value must be enclosed in parentheses when multiple commands are specified. For example: `jdbc:xquery:sybase://server1:5000;DatabaseName=test; InitializationString=(command1;command2)` If the execution of a SQL command fails, the connection attempt also fails and DataDirect XQuery raises an exception indicating which SQL command or commands failed.
Password	A case-insensitive password used to connect to your Sybase database. A password is required only if user ID/password authentication is enabled on your database. If so, contact your system administrator to obtain your password.
ServicePrincipalName	Specifies the case-sensitive service principal name to be used by DataDirect XQuery for Kerberos authentication. For Sybase, the service principal name is the name of a server configured in your Sybase interfaces file. If you set this property, you also must set the value of the AuthenticationMethod property to Kerberos. The value of this property can include the Kerberos realm name, but it is optional. If you do not specify the Kerberos realm name, the default Kerberos realm is used. For example, if the service principal name, including Kerberos realm name, is server/sybase125ase1@XYZ.COM and the default realm is XYZ.COM, valid values for this property are: `server/sybase125ase1@XYZ.COM` and `server/sybase125ase1` When Kerberos authentication is not used, this property is ignored.
User	The case-insensitive user name used to connect to your Sybase database. A user name is required only if user ID/password authentication is enabled on your database. If so, contact your system administrator to obtain your user name.