Federation: Registering the server definitions for a Microsoft SQL Server data source
IBM InfoSphere Federation Server, Version 10.5

Registering the server definitions for a Microsoft SQL Server data source

You must register each Microsoft SQL Server remote server that you want to access in the federated database.

Procedure

  1. Locate the node name for the Microsoft SQL Server.
    • On federated servers that run Windows, the node name is the System DSN name that you specified for the Microsoft SQL Server remote server that you are accessing.
    • On federated servers that run UNIX, the node name is defined in the .odbc.ini file.

    At the top of the .odbc.ini file, there is a section labeled ODBC Data Sources, which lists the nodes. Each of the nodes has a section in the .odbc.ini file that describes the node.

    The following example is a .odbc.ini file on AIX®. The node names are [rawilson] and [medusa].
    [ODBC Data Sources]
    rawilson=MS SQL Server 2000
    medusa=MS SQL Server 2000 
    [rawilson]
    Driver=/opt/odbc/lib/ddmsss20.so  
    Description=MS SQL Server Driver for AIX
      Address=9.112.30.39,1433
    [medusa] 
    Driver=/opt/odbc/lib/ddmsss20.so 
    Description=MS SQL Server Driver for AIX
    Address=9.112.98.123,1433
    [ODBC]
    InstallDir=/opt/odbc
  2. Issue the CREATE SERVER statement from the command line to create the server definition.
    For example:
    CREATE SERVER server_definition_name 
    TYPE MSSQLSERVER 
    VERSION version_number 
    WRAPPER wrapper_name
    OPTIONS (NODE 'node_name', 
    DBNAME 'database_name');

    Although the 'node_name' and 'db_name' variables are specified as options in the CREATE SERVER statement, these options are required for Microsoft SQL Server data sources.

    After the server definition is registered, use the ALTER SERVER statement to add or drop server options.

What to do next

After you complete this task, you can create user mappings.