DB2 10.5 for Linux, UNIX, and Windows

Instance merge modules (Windows)

There are two types of merge modules: instance merge modules and non-instance merge modules.

It is recommended that you use non-instance merge modules. Instance merge modules require additional overhead and maintenance, but can be used when:
  • an application requires a instance environment, or,
  • an application requires function that only exists in a instance merge module. (The instance merge modules are listed later in this section.)

Using Windows Installer for instance merge modules, you can easily add IBM® Data Server Runtime Client function to any product that uses the Windows Installer.

When you merge the modules, you will be prompted to supply the data server copy name. Multiple copies of data server products can be installed on the same machine; so each copy is known by its unique name. This name will be used when the installation is performed on each target machine. Choose a name that is unlikely to be already used for another data server copy. Suitable names include the name of your application, for example, myapp_db2copy_1. If the name is not unique, the installation will fail.

For more information on merge module technology, see the documentation included with your installation authoring product or at http://msdn.microsoft.com.

The following merge modules are available for your use:

Base Client Merge Module.msm
This module provides the function required for database connection, SQL, and command function. This module allows you to use the Named Pipes communication protocol to transfer data in a client-server environment, contains the system bind files which are used for such tasks as creating databases or accessing remote host databases, and, provides various tools used to administer local and remote databases. This module also allows you to create a response file which can be used to configure the data server copy within your installation. The configurable option specifies the location of a response file used to configure the data server copy. Types of configuration include creating instances, setting database manager configuration parameters or profile registry variables. You can also use the Command Line Processor (CLP) with this module.

For information about the sequence of various custom actions and the proposed sequences, view the merge module with a tool such as Orca.

JDBC and SQLJ Support.msm
This module contains JDBC and SQLJ support allowing Java™ samples to be built and run using the JDBC driver.
LDAP Exploitation Merge Module.msm
This module allows the data server copy to use an LDAP directory to store database directory and configuration information.
ODBC Support Merge Module.msm
This module provides support for applications that use Open Database Connectivity (ODBC) to access data.
OLE DB Support Merge Module.msm
This module provides a set of interfaces that allows applications to uniformly access data stored in different data sources.
IBM Data Server Provider for .NET Merge Module.msm
This module enables your application to use the IBM Data Server Provider for .NET. The IBM Data Server Provider for .NET is an extension of the ADO.NET interface that enables your .NET applications to quickly and securely access data from databases.
The following Microsoft re-distributable merge modules are included with the IBM Data Server Runtime Client merge modules. You must include these Microsoft merge modules when merging Data Server Runtime Client merge modules.

Microsoft NT32:
Microsoft_VC80_CRT_x86.msm
Microsoft_VC80_MFC_x86.msm
policy_8_0_Microsoft_VC80_CRT_x86.msm
policy_8_0_Microsoft_VC80_MFC_x86.msm

Microsoft NT64:
Microsoft_VC80_CRT_x86_x64.msm
Microsoft_VC80_MFC_x86_x64.msm
policy_8_0_Microsoft_VC80_CRT_x86_x64.msm
policy_8_0_Microsoft_VC80_MFC_x86_x64.msm

You can find the Microsoft merge modules on the IBM Data Server Runtime Client DVD under the merge module directory.
The following merge modules contain IBM data server client messages used by the data server copy. Depending on the languages of your product, include and install the components in the appropriate merge module.

IBM data server client Messages - Arabic.msm
IBM data server client Messages - Bulgarian.msm
IBM data server client Messages - Chinese(Simplified).msm
IBM data server client Messages - Chinese(Traditional).msm
IBM data server client Messages - Croatian.msm
IBM data server client Messages - Czech.msm
IBM data server client Messages - Danish.msm
IBM data server client Messages - Dutch.msm
IBM data server client Messages - English.msm
IBM data server client Messages - Finnish.msm
IBM data server client Messages - French.msm
IBM data server client Messages - German.msm
IBM data server client Messages - Greek.msm
IBM data server client Messages - Hebrew.msm
IBM data server client Messages - Hungarian.msm
IBM data server client Messages - Italian.msm
IBM data server client Messages - Japanese.msm
IBM data server client Messages - Korean.msm
IBM data server client Messages - Norwegian.msm
IBM data server client Messages - Polish.msm
IBM data server client Messages - Portuguese(Brazilian).msm
IBM data server client Messages - Portuguese(Standard).msm
IBM data server client Messages - Romanian.msm
IBM data server client Messages - Russian.msm
IBM data server client Messages - Slovak.msm
IBM data server client Messages - Slovenian.msm
IBM data server client Messages - Spanish.msm
IBM data server client Messages - Swedish.msm
IBM data server client Messages - Turkish.msm