When first run, ProductWriter's (PW) main executable 'PWNavigator.exe' will attempt to create a database. Even if the account you're using has administrative privileges, this will fail. You need to shake some bones at DB2 first.
You need to set the database configuration accordingly. I have used the property DB2PATH to represent the path where the DB2 executables live:
[DB2PATH]db2cmd -c -w db2 UPDATE DBM CFG USING CATALOG_NOAUTH YES
[DB2PATH]db2cmd -c -w db2 UPDATE DBM CFG USING SYSADM_GROUP DB2ADMNS
Note that these instructions apply ONLY if using local groups. Since this product seems blissfully unaware of the fact that DB2 was designed as a server-based product and requires a local DB2 instance, I can't really see the point in using domain groups. Equally, the vendor doesn't support any configuration other than a local instance. Indeed, my use of DB2ADMNS instead of ADMINISTRATORS in the d/b config means my client (which forbids all but 4 accounts from local admins) is running unsupported. However, since the vendor was unable to help us with ANY of the above (nor the setting up of DB2 to install silently - see my 'DB2 Express Edition 9.x' entry) to get to a working state, the value of such support has to be questioned.