Notes for Oracle

For a self-signed binary distribution/zip file of Instant Client, we recommend that the zip file contents are copied to a folder in your $HOME directory, for example: ~/InstantClient_23
You can then create a symbolic link in the /usr/local/lib folder that points to the target library, i.e.

cd /usr/local/lib
ln -s ~/InstantClient_23/libclntsh.dylib.23.1 libclntsh.dylib

For unsigned binaries- extracted from a zip file for example, these should be placed either:

• inside the Omnis.app/Contents/Frameworks folder, or the DAM's Contents/Frameworks folder.
  These can then be signed as part of the Omnis executable.
• inside the /usr/local/lib folder. This option requires that you apply an adhoc code signature to each client library dependency.

Notes:
• The Omnis.app/Contents/MacOS folder should not be used for client libraries, since this folder is reserved for the main Omnis executable.
• It is not necessary to copy all files from the Instant Client distribution. Please refer to technote TNSQ0010c for further details.

Notes for Sybase

When building the freetds client library for use with the Sybase DAM, this gets signed and installed into the /usr/local/lib folder by default, and should load correctly from this location.

It should be possible to bundle the client library inside Omnis.app/Contents/Frameworks or inside the DAM's Contents/Frameworks folder, provided that the client library's dependencies can be located. The RPATHs used by the client library can be modified using the install_name_tool command if required.

Using Homebrew

It may be preferable to install FreeTDS client using the Homebrew package manager. You can install FreeTDS client using the command:

arch -arm64 brew install freetds

Then, navigate to the Omnis Frameworks folder, or to /usr/local/lib and create the symbolic link. For example:

cd /usr/local/lib
ln -s /opt/homebrew/Cellar/freetds/1.5.18/lib/libct.4.dylib libct.dylib

Note: you can find the location of your target library using the command:   brew list freetds

Notes for PostgreSQL

On installing the PostgreSQL admin & command line tools- from https://www.postgresql.org/download/,
the following symlink can be used to point at the installed lib folder:

ln -s /Library/PostgreSQL/16/lib /usr/local/pgsql/lib

This will allow the DAM to load the SSL-enabled version of libpq.dylib.

Alternatively, it is possible to copy the dylibs from /Library/PostgreSQL/16/lib to /usr/local/lib.

The SSL client can also be bundled with the DAM if part of a custom deployment. However, this is subject to the license terms and will require dependency paths to be modified using the install_path_tool. No custom folders should be created in the Studio tree, (e.g. lib).

Using Homebrew

It may be preferable to install PostgreSQL client libraries using the Homebrew package manager, particularly where there may be several inter-dependent library files. You can install the client libraries using the command:

arch -arm64 brew install libpq@17
or
brew install libpq    (to use default architecture and client version)

Then, navigate to /usr/local/lib and create the symbolic link. For example:

ln -s /opt/homebrew/Cellar/libpq/18.4/lib/libpq.5.dylib libpq.dylib

Note: you can find the location of your target library using the command:   brew list libpq@17

Notes for MySQL

Standard installation of the MySQL client places a symlink from /usr/local/mysql, for example:

/usr/local/mysql -> mysql-9.0.1-macos14-arm64

This means that the DAM can pick the client up along that path. If bundling the client with Studio, the dependencies will likely need changing to be load from Omnis.app/Frameworks or /PlugIns/dammysql.u_xcomp/Contents/Frameworks.

Using Homebrew

It may be preferable to install MySQL client libraries using the Homebrew package manager, particularly where there may be several inter-dependent library files. You can install the client libraries using the command:

arch -arm64 brew install mysql-client@9.7
or
brew install mysql-client    (to use default architecture and client version)

Then, create the symbolic link. For example:

sudo ln -s /opt/homebrew/Cellar/mysql-client/9.7.1/lib/libmysqclient.24.dylib /usr/local/lib/libmysqlclient.dylib

Note: you can find the location of your target library using the command:   brew list mysql-client@9.7

Notes for ODBC

Please note that Omnis Studio ODBC DAM supports different ODBC driver managers via it's $mode property, notably; iODBC and unixODBC.

For unixODBC/Microsoft ODBC drivers, refer to technote: TNSQ0038
For iODBC/Openlink/Actual Technologies ODBC drivers, refer to technote: TNSQ0038a

Using Homebrew

• To install the unixODBC driver manager, open a terminal window and run the following commands:

brew install unixodbc
sudo ln -s /opt/homebrew/Cellar/unixodbc/2.3.14/lib/libodbc.2.dylib /usr/local/lib/libodbc.dylib

• To install the iODBC driver manager, open a terminal window and run the following commands:

brew install libiodbc
sudo ln -s /opt/homebrew/Cellar/libiodbc/3.52.16/lib/libiodbc.2.dylib /usr/local/lib/libiodbc.dylib

You can find the exact path (and version) of the installed library using the brew list <packge_name> command, for example: brew list libiodbc.
Subsequently, Omnis Studio will be able to locate the signed driver manager from its location on the standard library search path (/usr/local/lib).