COGNOiSe.com - The IBM Cognos Community

IBM Cognos 10 Platform => Cognos 10 BI => Cognos Administration => Topic started by: mattbartos on 16 Mar 2015 11:56:11 AM

Title: cognosisapi.dll
Post by: mattbartos on 16 Mar 2015 11:56:11 AM
Anyone had any issues getting this to work properly.  I can only get the cgi module to work as advertised.
Title: Re: cognosisapi.dll
Post by: mattbartos on 16 Mar 2015 11:58:44 AM
BTW this is 10.2.2
Title: Re: cognosisapi.dll
Post by: redstang on 16 Mar 2015 05:26:58 PM
Yes, we use ISAPI.  What web server are you using?  If IIS, you must configure the handler mappings in the cgi-bin app directory to allow it to run.  You also must change the default.htm to load the cognosisapi.dll instead of the .cgi. 
Title: Re: cognosisapi.dll
Post by: MFGF on 17 Mar 2015 05:03:21 AM
I tested it in 10.2.2 and it worked fine for me too. I use cognos.cgi but have IIS configured to allow both cgi modules and dlls.

MF.
Title: Re: cognosisapi.dll
Post by: mattbartos on 17 Mar 2015 02:22:30 PM
We are using IIS 7.5 and I have the handler mappings taken care of for the cgi-bin directory.  As I said CGI works fine...but the ISAPI module takes up one full processor of CPU, runs about 6 minutes and drops off...but w3wp continues to hold onto the CPU.  If I refresh or go back and then forward I will get the page up, but it takes double the CPU.
Title: Re: cognosisapi.dll
Post by: mattbartos on 18 Mar 2015 09:52:47 AM
so for those who have isapi working as prescribed...this is what I have done:

- set cognosisapi.dll as the default
- created the handler mappings in cgi-bin virtual directory (I don't use ibmcognos for a virtual directory because I just deleted the default web site in IIS and created a cognos web site that points to the webcontent directory thus cgi-bin is my virtual directory) for the cognosisapi.dll to have execute
- ensured that cognosisapi.dll  has the enabled unspecified isapi modules to execute checked

It still clogs up the cpu's and never delivers the page on the first try.

I took a dmp file of the w3wp process and uploaded it to IBM and they are analyzing it but for those of you that have no issues with it...on a tertiary glance do you see something I may have missed.  I am new to the COGNOS realm and any assistance I can get would be more than greatly appreciated.
Title: Re: cognosisapi.dll
Post by: redstang on 18 Mar 2015 12:03:45 PM
The fact that IIS will serve you up the Cognos portal at all would seem to indicate that at a bare minimum you have the permissions set up ok.  I use this document when configuring IIS:

http://www.ibm.com/developerworks/data/library/cognos/infrastructure/web_servers/page599.html

I have configured the website both under the default site as well on its own site with a domain name bound to it so you don't have to put the '/ibmcognos' at the end if you don't want to.  I've never had any CPU usage issues just loading the portal.  I have also run this on physical servers and VMs with little difference. 

It would seem you have something wrong with the specific server you are using.  Do you have another server you could try to install it on to test?
Title: Re: cognosisapi.dll
Post by: mattbartos on 18 Mar 2015 12:25:57 PM
Yeah I am working on that now.  The government workers (gs-types) are making this difficult to say the least.  And DoD and all the security specs and what not do not help either
Title: Re: cognosisapi.dll
Post by: Nimirod on 25 Mar 2015 03:54:41 AM
You said you supress the default web site from IIS, and what about the application pools ?

There is a default application pool configurated for defaul website so i think that you should configurate correctly the application pool for your cognos apllication in order to balance correctly the load.

Well that's just an idea i had reading your problem.

Good luck.

N
Title: Re: cognosisapi.dll
Post by: mattbartos on 08 Apr 2015 10:30:07 AM
Hot damn that did it...thank you ever so much

I didn't even think about my web site being the default since I deleted the "real" default...so with the default app pool just sitting idle it was confused.  I deleted the secondary app pool, assigned the web-site to the default and bam it works as expected.