Checking the setup of the federated server

Confirming the link-edit of the wrapper library files (UNIX)

On federated servers that run UNIX^®, some wrappers must be link-edited with the client software for the data source.

You must confirm that a wrapper library file exists on the federated server for each data source that you want to access.

About this task

This task applies to only the following data sources:

• Informix^®
• Microsoft^® SQL Server
• Oracle
• Sybase
• Teradata

Procedure

To check for the wrapper library files:

Check for the library files in the default directory path where WebSphere^® Federation Server is installed. If the library files are not in that directory, you must manually link the wrapper libraries to the data source client software.

The directory path for the wrapper library depends on the data source.

Oracle wrapper library files

The Oracle wrapper library files are added to the federated server when you install the wrapper.

When you install the Oracle wrapper, three library files are added to the default directory path. For example, if the federated server is running on AIX®, the wrapper library files that are added to the following directory path are libdb2net8.a, libdb2net8F.a, and libdb2net8U.a, The default wrapper library file is libdb2net8.a. The other wrapper library files are used internally by the Oracle wrapper.

The default directory paths and default wrapper library file names are listed in the following table.

Table 1. Oracle wrapper library locations and file names

Operating system	Directory path	Library file names
AIX	/usr/opt/install_path/lib32/ /usr/opt/install_path/lib64/	libdb2net8.a
Linux®	/opt/IBM/db2/install_path/lib32 /opt/IBM/db2/install_path/lib64	libdb2net8.so
Solaris	/opt/IBM/db2/install_path/lib32 /opt/IBM/db2/install_path/lib64	libdb2net8.so
Windows®	%DB2PATH%\bin	db2net8.dll

Manually linking the wrapper libraries to the data source client software

If the wrapper library files are not in the directory path, you must manually link the wrapper libraries.

Before you begin

You need root authorization to run the link scripts.

The client software for the data sources that you want to access must be installed and configured on the federated server.

For the djxlinkxxx scripts to issue their messages in your language, at least one database instance must exist on the federated server. If an instance does not exist on the federated server, the scripts will still work. However, the scripts will issue all messages in English.

Procedure

To link the wrapper libraries to the data source client software:

1. Decide which method you want to use to perform the link:

   Method

   Step

   Run the link-edit scripts.

   Open a UNIX® command prompt and run the link-edit script for each data source that you want to access. The names of the link-edit script are: djxlinkInformix djxlinkMssql djxlinkOracle djxlinkSybase djxlinkTeradata Issue the db2iupdt command on each federated database instance to enable federated access to the data sources. There is another script, the djxlink script, that attempts to create a wrapper library for every data source that is supported by WebSphere Federation Server. If you run djxlink script and have the client software for only some of the data sources installed, you will receive an error message for each of the data sources that you do not have installed.

2. After the link is performed, check the permissions on the wrapper libraries. Make sure that the libraries can be read and run by the database instance owners.

Checking the FEDERATED parameter

The FEDERATED parameter must be set to YES to enable the federated server to access to the data sources.

To check the FEDERATED parameter setting:

1. Issue the following DB2^® command to display all of the parameters and their current settings:

   GET DATABASE MANAGER CONFIGURATION

2. Determine if the concentrator is active based on the value of the max_connections parameter:
   • Off: max_connections is equal to max_coordagents.
   • On: max_connections is greater than max_coordagents.
   The max_connections parameter cannot be active when the FEDERATED parameter is configured to YES. If the concentrator is on, change the setting to off.
3. Check the FEDERATED parameter setting. If the FEDERATED parameter is set to NO, change the setting to YES. Issue the following DB2 command to change the setting:

   UPDATE DATABASE MANAGER CONFIGURATION USING FEDERATED YES

https://www-304.ibm.com/support/docview.wss?uid=swg21154462

http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp (Configuring - 페더레이티드 시스템 구성)