Use Campaign Federated Data Access (FDA) option to process information stored in an external database. Follow the steps below to configure access to Vertica Analytics.
To configure Vertica Analytics on CentOS, follow the steps below:
Download the ODBC drivers for Vertica Analytics. Click here and download the latest Linux RPM.
You then need to install unixODBC with the following command:
yum search unixODBC
yum install unixODBC.x86_64
If you have previously installed the Vertica Analytics Server, an ODBC driver will already be installed. In this case, update the drive as follows:
#Switch to root
sudo su
#Install the package (add --force to update it)
rpm -Uvh vertica-client-x.x.x-x.x86_64.rpm [--force]
#Open odbcinst.ini
vi /etc/odbcinst.ini
#Add a section for Vertica Analytics and save
[VerVertica Analyticstica]
Description = Vertica Analytics ODBC Driver
Driver = /opt/vertica/lib64/libverticaodbc.so
#Open odbc.ini
vi /etc/odbc.ini
#Add your DSN in ODBC Data Sources section, for example:
[ODBC Data Sources]
VMart = "VMart database on Vertica Analytics"
#Add a DSN definition section below, for example:
[VMart]
Description = Vmart Database
Driver = Vertica Analytics
Database = VMart
Servername = # The name of the server where Vertica Analytics is installed. Use localhost if Vertica Analytics is installed on the same machine.
UID = dbadmin
PWD = <password>
Port = 5433
#Cleanup
#Remove the ODBC package
rm vertica-client-x.x.x-x.x86_64.rpm
In Adobe Campaign, you can then configure your Vertica Analytics external account. For more on how to configure your external account, refer to this section.
Download the ODBC driver for Windows. To install the driver for Windows, you will need to enable .NET Framework 3.5 or the installation wizard will try to automatically enable and download it.
Configure the ODBC driver in Windows. For more on this, refer to this page
In Adobe Campaign, you can then configure your Vertica Analytics external account. For more on how to configure your external account, refer to this section.
Download the ODBC drivers for Vertica Analytics. Click here start downloading.
You then need to install unixODBC with the following command:
apt-get install unixODBC
If you have previously installed the Vertica Analytics Server, an ODBC driver will already be installed. In this case, update the drive as follows:
#Switch to root
sudo su
#Move or copy the downloaded file and change to /root
mv vertica_9.3..xx_odbc_x86_64_linux.tar.gz /
cd /
#Uncompress the file you downloaded
tar vzxf vertica_9.3..xx_odbc_x86_64_linux.tar.gz
#Remove the tar.gz since it is not needed anymore
rm vertica_9.3..xx_odbc_x86_64_linux.tar.gz
#Open odbcinst.ini
vi /etc/odbcinst.ini
#Add a section for Vertica Analytics and save
[Vertica Analytics]
Description = Vertica Analytics ODBC Driver
Driver = /opt/vertica/lib64/libverticaodbc.so
#Open odbc.ini
vi /etc/odbc.ini
#Add your DSN in ODBC Data Sources section, for example:
[ODBC Data Sources]
VMart = "VMart database on Vertica Analytics"
#Add a DSN definition section below, for example:
[VMart]
Description = Vmart Database
Driver = Vertica Analytics
Database = VMart
Servername = # The name of the server where Vertica Analytics is installed. Use localhost if Vertica Analytics is installed on the same machine.
UID = dbadmin
PWD = <password>
Port = 5433
In Adobe Campaign, you can then configure your Vertica Analytics external account. For more on how to configure your external account, refer to this section.
You need to create a Vertica Analytics external account to connect your Campaign instance to your Vertica Analytics external database.
From Campaign Explorer, click Administration ‘>’ Platform ‘>’ External accounts.
Click New.
Select External database as your external account’s Type.
Configure the Vertica Analytics external account, you must specify:
Type: Vertica Analytics
Server: URL of the Vertica Analytics server
Account: Name of the user
Password: User account password
Database: Name of the database
The connector supports the following options:
Option | Description |
---|---|
TimeZoneName | By default empty, which means that the system time zone of the Campaign Classic app server is used. The option can be used to force the TIMEZONE session parameter. |