Preparing applications for SMA use with driver manager

SMA and LLA Guide : Creating and running SMA applications : Creating SMA applications - overview : Preparing applications for SMA use with driver manager

When using SMA with a driver manager, you connect to a SMA data source in a similar way as when connecting to a regular solidDB^® ODBC data source.

About this task

The SMA driver library file is installed during the solidDB^® server installation. The table below lists the file names and their default installation locations for the most common platforms.

xx is the version number of the driver library, for example, ssolidsma70.so.

Platform	SMA driver library	Default installation location
Windows	ssolidsmaxx.dll Note If you link to the SMA driver directly (without driver manager), you link to the solidsma.lib import library file that gives you access to the actual .dll library file.	Library: <solidDB^® installation directory>\bin Import library: <solidDB^® installation directory>\lib
Linux	ssolidsmaxx.so	<solidDB^® installation directory>/bin
Solaris	ssolidsmaxx.so	<solidDB^® installation directory>/bin
HP-UX	ssolidsmaxx.so	<solidDB^® installation directory>/bin
AIX	ssolidsmaxx.so	<solidDB^® installation directory>/bin

Procedure

1 Configure the SMA data source according to the instructions provided with your driver manager.

2 Connect to the SMA data source.

Use the SMA-specific connect string when defining the data source connection information.

The connect string syntax for a SMA connection is:

sma <protocol name> <port number or pipe name>

For example:

sma tcp 2315

3 Check the use of signal handlers.

Signal handlers are used to report the occurrence of an exceptional event to the application. The SMA driver installs by default its own signal handler that can help the SMA system to survive the most common application failures, such as killing or interrupting the applications from outside. Upon the capture of certain signals, the signal handler closes the SMA connections safely and exits the SMA application. This means that in most cases, the SMA server continues to run despite abnormal application exits.

By default, the SMA driver handles the following signals that can cause the SMA connection to break:

▪Linux and UNIX: SIGINT, SIGTERM

▪Windows: SIGINT

You can modify the set of signals that the SMA driver handles with the client-side parameter SharedMemoryAccess.Signals. You can also disable the SMA driver signal handler by setting the client-side parameter SharedMemoryAccess.SignalHandler to no.

If the SharedMemoryAccess.SignalHandler parameter is set to “yes” (default), do not set signal handlers in your application for those signals that are handled by the SMA driver; the application setting will override the SMA driver settings.

Related reference:

Shared memory access parameters