Auditing Bug

Well, the problem with auditing was a little more complex than I had first thought. 

Turns out that during the install, the auditing connection had been set to the same as the CMS database connection, and for some reason the wrong Activity universe had been installed (MS SQL instead of Oracle).

This would be fine, just change the auditing connection to the correct auditing database, but sadly not. The ./cmsdbsetup.sh script on Solaris is bugged and will not effect any changes when you run the script.

Setting up Auditing in XI 3.0

I set up our DEV environment over a week ago, and enabled auditing. Was a bit miffed when I came to look at the audit activity today, to find nothing in the audit database. 

After a bit of digging, I discovered that this was due to the 'Events per file' setting in the Audit Properties of the services, the default is 500, and because there are currently only a couple of people using that server, it hadn't hit that limit and started copying the audit data from the log files into the audit database!

QaaWS XI 3.0

Query As A Web Service does not function on a default XI 3.0 install, if you have a named user license.

You can check if this is the problem by navigating to http://<server>:<port>/dswsbobje/services/session .

If it's complaining about no more concurrent access licenses, you need to change the user account QAAWSServletPrincipal from Concurrent  to Named user in the CMC. Job done.

Introduction

I'm going to use this blog to track various hurdles I come across in the implementation of XI 3.0 and Xcelsius 2008, in a mixed Windows and Solaris clustered deployment, utilising Windows AD silent single sign-on.....hopefully :)