Load Ingest Data
Results 1 to 1 of 1

Thread: ADO Connect String Disam

  1. #1
    Jeanne Wiegelmann is offline Documentation
    Join Date
    Aug 2006
    Posts
    86
    Rep Power
    14

    ADO Connect String Disam

    ADO Connect String Parameters to Connect to DISAM


    The ADO connect string parameters can be one or more of the following:

    • Binding=name|XML_format: Specifies the data source connection information.


    Where:
    name: The name of the binding configuration in the local repository. This provides access to all data sources defined in this binding configuration.
    XML format: The binding configuration in XML format. This parameter defines specific data sources and eliminates the need to define a local binding configuration in the repository. Only the data sources specified for the binding are accessed. If you want to access the data sources in all the binding configurations on a remote machine, use the BindURL parameter.

    The settings include the following:
    • name: The name of a data source. For more information, see Bindings.
    • type: The driver used to access the data source if it resides on the client machine, or the value REMOTE if the data resides on a remote machine. If the value is REMOTE, the binding on the remote machine is updated with the values of name, data source type and configuration properties.
    • connect: If the type value is a driver, this value is the connection information to the data source. If the type value is REMOTE, this value is the address of the remote machine where the data source resides and the workspace on that machine (if the default workspace is not used).
    • Configuration properties: Properties specific to the data source driver. For details, see the specific data source driver.

    Sample Connections

    The following shows a connection to a local demo DISAM data source, via ADO:
    connection.Open "provider=AttunityConnect;
    Binding="<?xml version=’1.0’ encoding=’iso-8859-1’?>
    <navobj><datasources><datasource name=’demo’ type=’add-disam’ readOnly=’true’><config newFileLocation=’D:\disam’ audit=’true’/>
    </datasource></datasources></navobj>""


    The following shows a connection to a remote demo data source:
    connection.Open "provider=AttunityConnect;
    Extended Properties="BindFile=NAV;DEFAULTTDP=mysql;OPERATIN G_MODE=0;";
    Binding="<?xml version=’1.0’ encoding=’iso-8859-1’?><navobj>
    <datasources><datasource name=’demo’ connect=’develop/acme.com’
    type=’remote’/></datasources></navobj>""

    • BindURL=[attconnect://][username:password@]host[:port][/workspa ce][&...][|...]: Specifies an AIS Server and which data sources, defined in a binding configuration on this server, are available. This parameter eliminates the need to define a local binding with entries for data sources on a server.


    If you want to access only a subset of the data sources on the server, use the Binding parameter. The settings include the following:

    • attconnect://: An optional prefix to make the URL unique when the context is ambiguous.
    • username:password@: An optional user ID/password pair for accessing the AIS Server.
    • host: The TCP/IP host where the daemon resides. Both numeric form and symbolic form are accepted.
    • port: An optional daemon port number. This item is required when the daemon does not use the Sun RPC portmapper facility.
    • workspace: An optional workspace to use. If omitted, the default workspace (“Navigator”) is used.
    • &…: Multiple BindURLs may be specified, using an ampersand (&) as separator. Spaces between the BindURLs are not allowed. If one of the machines listed is not accessible, the connect string fails.
    • |…: Multiple BindURLs may be specified, using an OR symbol (|) as separator. Spaces between the BindURLs are not allowed. The connect string succeeds as long as one of the machines listed is accessible.

    Note the following:
    • A data source name may appear more than once. AIS resolves this ambiguity by using the first definition of any DSN and disregarding any subsequent definitions. Thus, if a DSN called SALES appears in the local binding and via the BindURL parameter, then the local definition is used.
    • When using BindURL, AIS Server binds upon initialization to all of the DSNs defined for the binding – regardless of which DSNs are actually used. (Note that this may result in decreased performance.)
    • For each server specified in the BindURL connect string item, AIS Server automatically adds a remote machine (dynamically in memory) called BindURLn with n=1,2,…, according to the order of the elements in the BindURL value.


    For multiple BindURLs, use the following syntax to specify a remote Query Processor to use:

    BindURLn=[attconnect://]… where n is the number of the BindURL specifying the remote machine whose Query Processor you want to use.

    Connection to remote machines

    • The following string shows an AIS Server running on nt.acme.com using the default workspace (Navigator), the portmapper and an anonymous login.

      ADO
      connection.Open
      "provider=AttunityConnect;BindURL=nt.acme.com"

    • The following string shows an AIS Server running on nt.acme.com using the Prod workspace and logging on as ’minny’ (password ’mouse’).

      BindURL=minny:mouse@nt.acme.com/prod
    • The following string shows an AIS Server running on nt.acme.com using the default workspace (Navigator), using the port 8888 and an anonymous login.

      BindURL=nt.acme.com:8888

    • Database: The name of a virtual database that this connection accesses. The virtual database presents a limited view to the user of the available data such that only selected tables from either one or more data sources are available, as if from a single data source.

      For more information, see Using a Virtual Database. If set, only the virtual database can be accessed using this connect string.
    • defaulttdp=data source: The name of the single data source you want to access as the default using this connection. Tables specified in SQL statements are assumed to be from this data source. If this parameter is not specified, SYS is the default; for tables from any other data source, you must prefix each table name with the name of the data source, using the format data source:tablename.

      Specifying defaulttdp is equivalent to setting the DefaultDatabase property in ADO or the Default Data Source option in a UDL connecting to AIS Server.
    • DSNPasswords=data_source|machine_ alias=username/password[&data_source|machine_ alias=username/password[&…]]: User profile information (username and password) granting access to a data source or remote machine via this connection.

      As an alternative to storing usernames and passwords in the user profile, this parameter allows you to dynamically supply one or more pairs of username and password values, with each pair assigned to a particular data source or remote machine.

      where:
      • data_source: A data source name defined in the binding configuration For more information, see Bindings.
      • machine_alias: A machine alias defined in the binding configurationFor more information, see Bindings.
      • username/password: A pair of user ID and password values needed in order to access the indicated data source.

    • Env-prop=value[,Env-prop=value[,Env-prop=value]...]: Environment values that override the values in the binding environment on the client.
    • where Env-prop is the name of the environment property. For information on these parameters see Environment Properties.


    Setting a parameter to True

    The following string sets the value of the noHashJoin parameter to true, disabling the hash join mechanism during query optimization.
    <optimizer noHashJoin="true"/>

    • Operating_Mode=1|0: Specifies whether all SQL statements that do not return rowsets during this connection will pass directly to the native RDBMS data source parameter, without any parsing normally performed by the Query Processor. Specifying 1 enables passthru mode and causes AIS to open the connection in single data source mode. This parameter can be used only if the backend data source is an SQL-based driver.

      SQL executed in passthru mode behave the same as individual passthru queries specified with the TEXT={{…}} syntax; however, there is no way to override passthru mode for a particular query. Use passthru mode to issue queries that perform special processing not supported in AIS, such as alter table and drop index.

      Note: Oracle Application Server Release Notes does not recommend using this option, since it impacts on every DDL SQL statement, even if only some statements were intended.

      Also see For all SQL During a Session.

      Specifying operating_mode is equivalent to setting the passthru option in a UDL used to connect to AIS Server.

      Also refer to Passthru SQL.
    • Password=password: Specifies the password required in order to access the user profile. For more information, see Editing a User Profile..

      When using ADO, to prompt the user for the correct password via a dialog box, use the ADO adPromptAlways attribute of the Properties method, as follows:

      connection.Properties("Prompt")=adPromptAlways

      Specify this line before the Open method. When the user tries to connect, a dialog box requesting the password is always displayed.
    • SecFile=filespec: The name of an user profile other than the default (NAV).

      The SecFile entry is supported for backwards compatibility only. As of AIS version 3.x, the User ID parameter is used instead of SecFile.
    • User ID=userID: Specifies the name of a user profile in the repository. If the user profile is not specified, the default user profile (NAV) is used.
    Last edited by Admin_attu; 09-28-2006 at 10:57 AM.
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •