1. Install DB2 client
2. Set DB2 envoirnment variables
3. Catalog remote host and database

After above these steps, add a new DB2 data source in Cognos Configurations. Navigate to IBM Cognos Connection > Launch > IBM Cognos Administration > Configuration and click New Data Source.

I set following environment variables in /etc/profile.

 JAVA_HOME=/usr/java6_64/jre
 PATH=$JAVA_HOME/bin:$PATH:/u01/ibm_cognos/cognos/c10_64/bin:/u01/IBM/db2/V9.7/bin
 LIBPATH=/u01/ibm_cognos/cognos/c10_64/bin:/home/db2inst1/sqllib/lib32
 export JAVA_HOME
 export PATH
 export LIBPATH

DB2DIR=/u01/IBM/db2/V9.7
 export DB2DIR

INSTHOME=/home/db2inst1
 export INSTHOME

DB2INSTANCE=db2inst1
 export DB2INSTANCE

1. Adding remote host in host file
2. Switch user to DB2 user (e.g. db2inst1)
3. Catalog remote node
4. Catalog remote database

Adding remote host in host file

Open /etc/hosts file and add your remote host with it’s IP address. You can vi this file and make changes. You must have root privileges to do this operation.

Switch to DB2 user

Switch to DB2 user by following command in shell.

su - db2inst1

Catalog remote node

Since now you have added you remote host in the host file (suppose your hostname is lpar0). Execute following command in the shell:

catalog tcpip node lpar0 remote lpar0 server 50000

50000 is the port of DB2 database.

Cataloging remote database

Now execute following command.

. DB2_INST_HOME/sqllib/db2profile

catalog database mysampledb as mysampledb at node lpar0 authentication server

Check your connectivity

connect to mysampledb user ctginst1 using admin

Where ctginst1 and admin are user name and password of mysampledb on host lpar0.

References

1. CATALOG TCPIP/TCPIP4/TCPIP6 NODE command
2. Cataloging a database from a DB2 client using the CLP

Exception in thread "main" com.sun.xml.internal.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions
Class has two properties of the same name "bookList"
	this problem is related to the following location:
		at public java.util.ArrayList com.xmlservice.jaxb.model.Bookstore.getBookList()
		at com.xmlservice.jaxb.model.Bookstore
	this problem is related to the following location:
		at private java.util.ArrayList com.xmlservice.jaxb.model.Bookstore.bookList
		at com.xmlservice.jaxb.model.Bookstore

	at com.sun.xml.internal.bind.v2.runtime.IllegalAnnotationsException$Builder.check(Unknown Source)
	at com.sun.xml.internal.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(Unknown Source)
	at com.sun.xml.internal.bind.v2.runtime.JAXBContextImpl.<init>(Unknown Source)
	at com.sun.xml.internal.bind.v2.runtime.JAXBContextImpl$JAXBContextBuilder.build(Unknown Source)
	at com.sun.xml.internal.bind.v2.ContextFactory.createContext(Unknown Source)
	at com.sun.xml.internal.bind.v2.ContextFactory.createContext(Unknown Source)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at javax.xml.bind.ContextFinder.newInstance(Unknown Source)
	at javax.xml.bind.ContextFinder.find(Unknown Source)
	at javax.xml.bind.JAXBContext.newInstance(Unknown Source)
	at javax.xml.bind.JAXBContext.newInstance(Unknown Source)
	at com.xmlservice.jaxb.model.BookMain.main(BookMain.java:43)

Solution: After some googling I figured out, that I have to move annotation to the getter method. That solves above exception.

The Bookstore.java will be look like this:

package com.xmlservice.jaxb.model;

import java.util.ArrayList;

import javax.xml.bind.annotation.XmlElement;
import javax.xml.bind.annotation.XmlElementWrapper;
import javax.xml.bind.annotation.XmlRootElement;

@XmlRootElement(namespace = "com.xmlservice.jaxb.model")
public class Bookstore {

	private ArrayList<Book> bookList;
	private String name;
	private String location;

	@XmlElementWrapper(name = "bookList")
	@XmlElement(name = "book")
	public ArrayList<Book> getBookList() {
		return bookList;
	}
	public void setBookList(ArrayList<Book> bookList) {
		this.bookList = bookList;
	}
	public String getName() {
		return name;
	}
	public void setName(String name) {
		this.name = name;
	}
	public String getLocation() {
		return location;
	}
	public void setLocation(String location) {
		this.location = location;
	}
}

Could not start the IBM Unica Campaign Listener service on Local Computer.

Error 183: Cannot create a file when that file already exists.

To resolve this issue you have to do following steps.
1. Make sure database is up and running. I was have Oracle database and checked it while connecting Sqlplus.
2. Start IBM WebSphere Application Server. Make sure Campaign, unica and dashboard applications are up and running in Enterprise Application section.

3. Navigate to <You Installation DIR>\Unica\Campaign\conf and delete unica_aclsnr.pid file. This is the file which is already there and listener is throwing error about it. We will delete it so that when we will start the Listener service, it will create a new file.
4. Right click on IBM Unica Campaign Listener service and click Start. It will work.

I come up with Toothpaste theme which is freely available on WordPress themes repository.

I am loving it’s customization and simplicity. And it’s what I was looking for.

We will install Netezza client on the machine where we are running IBM Unica Campaign. And will configure ODBC on this machine.

Installing Netezza client

1. Extract nz-aixclient-v6.0.5.p7.tar somewhare in your directory
2. Run unpack script and install Netezza client on /usr/local/nz

Installing ODBC Data Direct

This application will help to test our connectivity with Netezza using above installed client. For IBM Unica Campaign, we will add odbc.so file in our LIBPATH.
1. Extract datadirect.package.tar to /opt/
2. It will be extracted as /opt/odbc64v51

ODBC.ini file

If it does not exist in your envoirnment, create it.
1. Create a file with name odbc.ini
2. Add following entry of your Netezza server

[NZSQL]
Driver                = /usr/local/nz/lib64/libnzodbc.so
Description           = NetezzaSQL ODBC
Servername            =
Port                  = 5480
Database              =
Username              =
Password              =
ReadOnly              = false
ShowSystemTables      = false
LegacySQLTables       = false
LoginTimeout          = 0
QueryTimeout          = 0
DateFormat            = 1
NumericAsChar         = false
SQLBitOneZero         = false
StripCRLF             = false
CancelAsFreeSmt       = false
CommLog               = false
Ksqo                  = false
Lie                   = false
Optimizer             = false
Parse                 = false
PreFetch              = 256
Protocol              = 7.0
Socket                = 16384
DateFormat            = 1
TranslationDLL        =
TranslationName       =
TranslationOption     =

3. You will add this file name with path in ODBC environment variable in next step
4. Make sure you have libnzodbc.so in /usr/local/nz/lib64 (if you don’t have, get it from here)

Setting environment variables

To run Netezza client you have to set following environment variables. I have set these variables in /etc/profile because I want them for root user.

ODBCINI=/u01/CONFIG/odbc.ini
NZ_ODBC_INI_PATH=/u01/CONFIG
NETEZZA=/usr/local/nz
LIBPATH=$NETEZZA/lib64:$NETEZZA/lib
PATH=$PATH:$NETEZZA/bin64:$NETEZZA/bin
LANG=en_US

export ODBCINI
export NETEZZA
export NZ_ODBC_INI_PATH
export PATH
export LANG

Testing connectivity with Netezza

1. Navigate to /opt/odbc64v51/example
2. Run example script
3. It will ask data source, username and password
4. Give those values to verify if you have successfully setup every thing

Important: Must read Netezza ODBC JDBC Configuration Guide for more understanding.

Add Netezza environment variables in setenv.sh for Unica listener

1. Add following environment variables in setenv.sh present in /u01/IBM/Unica/Campaign/bin

NETEZZA=/usr/local/nz
export NETEZZA
NZ_ODBC_INI_PATH=/u01/CONFIG
export NZ_ODBC_INI_PATH
ODBCINI=/u01/CONFIG/odbc.ini
export ODBCINI

2. Update LIBPATH in setenv.sh and it will look like this:

LIBPATH=$CAMPAIGN_HOME/bin:/usr/lib:$ORACLE_HOME/lib:$NETEZZA/lib64:$NETEZZA/lib:/opt/odbc64v51/lib

3. Commit your changes and restart Unica listener

Import Netezza data source template in IBM Unica Campaign

Since you have set up the Netezza client. Now you have to add it as a data source in IBM Unica Campaign. For that first, you have to import Netezza data source template in IBM Unica Campaign.
1. Navigate to /u01/IBM/Unica/Platform/tools/bin
2. Run following command

./configTool.sh -i -p "Affinium|Campaign|partitions|partition1|dataSources" -f /u01/IBM/Unica/Campaign/conf/NetezzaTemplate.xml

Add Netezza data source in IBM Unica Campaign

1. Open IBM Unica Platform and navigate to Settings > Configuration.
2. Navigate to data source in Campaign > partitions > partion1 > dataSources > NetezzaTemplate

3. Configure following properties
4. Now you are good to import tables from Netezza data warehouse

Create a shell script with following contents. Your every statement will be run with su to db2inst1.

#!/bin/sh
su - db2inst1 -c 'db2 connect to customerdb user db2inst1 using admin'
su - db2inst1 -c 'db2 -tvsf /u01/IBM/workspace/addcustomer.sql'

Write any thing in your SQL file. I am calling a DB2 store procedure that will insert a row in a table.

call ADDCUSTOMER();

Running being a root user.

bash-3.2# ./addcustomer.sh

   Database Connection Information

 Database server        = DB2/AIX64 9.7.0
 SQL authorization ID   = DB2INST1
 Local database alias   = CUSTOMERDB

call ADDCUSTOMER()

  Return Status = 0

Following are table of contents extracted from guide.

• Preparing AIX Platform
• Setting up DB2 Server
• Installing DB2
• Creating Users, Buffer pool & Table Spaces
• Create DB Users of IBM Unica Platform and Campaign on AIX
• Installing IBM WebSphere Application Server
• Create IBM WebSphere Server Profile
• Configuring IBM WebSphere Application Server for Unica Deployment
• Adding Application Server Custom Property
• Creating JDBC Provider for DB2
• Creating Data Source for IBM Unica Platform
• Create Data Source for IBM Unica Campaign
• Setting Heap Size of WebSphere
• Installing IBM Unica Platform
• Deploying IBM Unica Platform on WebSphere
• Installing IBM Unica Campaign
• Deploying IBM Unica Campaign on WebSphere
• Configuring Campaign Server on AIX
• Configuring Campaign after Deployment
• Set up Campaign System User
• Settings for Configuration page of Unica
• Map System Tables in Campaign
• Configuring Reports in IBM Unica Platform
• Installing Oracle Client 11g for Oracle Data Sources in IBM Unica Campaign
• Creating Group and User for Oracle Client Installation
• Create Oracle Base Directory
• Login Oracle User and Configure Environment
• Install Oracle Client
• Creating Oracle Data Source in IBM WebSphere Application Server
• Creating Oracle Data Source in IBM Unica Platform
• Installing DB2 Runtime Client for DB2 Data Sources in IBM Unica Campaign
• Adding DB2 Data Source in db2cli.ini
• Installing IBM Cognos BI 10.2
• Prerequisites and Checklist
• Installing Java 6 on AIX
• Installing HTTP Server & Configuring for Cognos
• Setting up IBM Cognos BI 10.2 System
• Configuring Cognos Server
• Installing Unica Integration Components & Report Model on Cognos System
• Installation checklist: IBM Cognos Integration
• Obtain the JDBC Driver for the Marketing Platform System Tables
• Install Reporting Models on the Cognos System
• Create Cognos Data Source for Unica Database
• Import Reports Folder to Cognos Connection
• Configure & Publish Data Model
• Configure the Reporting Properties in IBM Unica Marketing
• Test Your Configuration without Authentication Enabled

But while I gave credentials of my host to attach a project I recieved following error:

Problem

Failed to authenticate the current user against the selected Services Tier

The URL [iiop://lpar5:2825] that is used to connect to the host [172.21.2.176] on the port [9080] is incorrect or is not trusted. To trust the connection, import the signer certificate into the local truststore, by running the following UpdateSignerCerts command: UpdateSignerCerts{.sh|.bat} -host 172.21.2.176 -port 9080

Exception stack trace:

com.ascential.acs.security.auth.JNDILoginException: The URL [iiop://lpar5:2825] that is used to connect to the host [172.21.2.176] on the port [9080] is incorrect or is not trusted. To trust the connection, import the signer certificate into the local truststore, by running the following UpdateSignerCerts command: UpdateSignerCerts{.sh|.bat} -host 172.21.2.176 -port 9080
	at com.ascential.acs.security.auth.JAASAuthenticationService.loginImpl(JAASAuthenticationService.java:345)
	at com.ascential.acs.security.auth.JAASAuthenticationService.login(JAASAuthenticationService.java:148)
	at com.ascential.acs.security.auth.client.AuthenticationService.doLoginImpl(AuthenticationService.java:866)
	at com.ascential.acs.security.auth.client.AuthenticationService.doLogin(AuthenticationService.java:350)
Caused by: com.ibm.is.isf.j2ee.J2EEClientException: A communication failure occurred while attempting to obtain an initial context with the provider URL: "iiop://lpar5:2825".  Make sure that any bootstrap address information in the URL is correct and that the target name server is running.  A bootstrap address with no port specification defaults to port 2809.  Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration.
	at com.ibm.is.isf.j2ee.impl.was.WASJ2EEClient.initRuntime(WASJ2EEClient.java:99)
	at com.ascential.acs.security.auth.JAASAuthenticationService.loginImpl(JAASAuthenticationService.java:311)
	... 3 more
Caused by: java.net.UnknownHostException: lpar5
	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:227)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:377)
	at java.net.Socket.connect(Socket.java:539)
	at java.net.Socket.connect(Socket.java:488)
	at java.net.Socket.(Socket.java:385)
	at java.net.Socket.(Socket.java:199)
	at com.ibm.ws.orbimpl.transport.WSTCPTransportConnection.createSocket(WSTCPTransportConnection.java:270)
	at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:354)
	... 25 more

Solution

It’s quite clear from the exception but it took time to figure out. We have to add a entry in the hosts file of Windows (present at: C:\Windows\System32\drivers\etc).

Open notepad or any of your favorite editor with administrator privileges (Run As Administrator) and open hosts file and edit.

Save this file and open Designer Client again. This time it will fetch projects.

There is a way for that. You can set envoirnment variable in /etc/profile. This will override all those envoirnment variables mentioned in .profile.

Setting variables in /etc/profile

For setting JAVA_HOME in /etc/profile enter following statements:

JAVA_HOME=/usr/java6_64/jre
export JAVA_HOME

PATH=$JAVA_HOME/bin:$PATH
export PATH

You have to login again to see the changes. I am using putty, so will re-open it and login with root user.

Verifying variables

To verify your changes you can echo JAVA_HOME and PATH variables.

# echo $JAVA_HOME
/usr/java6_64/jre

# echo $PATH
/usr/java6_64/jre/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin

# which java
/usr/java6_64/jre/bin/java

I am using Korn Shell. To know which shell you are using, you can echo SHELL.

# echo $SHELL
/usr/bin/ksh