Change CGI to ISAP via a powershell script?? is it even possible?? im lost!

by Nov 19, 2014

I have recently been on a basic powershell course and my first task now back to work is to turn the following into a powershell script and it has totally baffled me? Any help would be appreciated as i am totally lost :'(

Change CGI to ISAP:
                Two types of gateways available to connect to cognos,
                                1. Cognos.cgi and
                                2. cognosisapi.dll             
                Cognos.cgi will be used when a application with limited number of user and load. If application is big and having huge data load then IBM recommendation is to use cognosisapi.dll.
Current ORS application is using Cognos.cgi gateway. To change to cognosisapi.dll gateway follow below steps, This has to change in both App & IIS servers.
           App server Side:
               In file under d:openpagesauroraconf change as follows,

·         cognos.server=https://server name or DNS name :443/ibmcognos/cgi-bin/cognos.cgi
Change to => cognos.server=https://server name or DNS name:443/ibmcognos/cgi-bin/cognosisapi.dll

·        logout.url.cognos=https:// server name or DNS name :443/ibmcognos/cgi-bin/cognos.cgi?
Change to => logout.url.cognos=https:// server name or DNS name :443/ibmcognos/cgi-bin/cognosisapi.dll?


IIS Server Side:
             Click on Internet information services(IIS) manager under Start menuà All programs àAdministration tools à Internet information services(IIS) Manager, it will open  IIS manager window.
  In the left hand side under connections à expand on ‘server name’ à expand ‘Sites’ à expand ‘default web site’ à expand ‘IBM cognos’ à click on ‘cgi-bin’
1.     Double-click on Handler Mappings in the middle pane. This will bring up the list of handler mappings for this application in the middle pane.
Figure 14: Handler Mappings under the Feature View of cgi-bin application

Note that by default ISAPI and CGI are listed as Disabled. Also note that CGI is for .EXE file extensions only.
Figure 1: Default view of Handler Mappings with CGI and ISAPI disabled
2.     In the far right Actions pane click Add Module Mapping… to add the ISAPI mapping.
3.     Provide the required details to the Add Module Mapping dialog.
o    In the Request path: field, specify the value cognosisapi.dll. This is a mandatory value and cannot be any other value.
o    In the Module: field, select IsapiModule from the drop down list.
o    In the Executable (optional): field, specify the path to the cognosisapi.dll within the IBM Cognos Gateway install. This file will be in D:OpenPagescognosc10_64cgi-bincognosisapi.dll
o    In the Name: field, specify a name for this module (for example, IBMCOGNOS-ISAPI).
Figure : The Add Module Mapping dialog with required request path, module, executable and name
4.     Click OK.
5.     A dialog will appear to confirm that this new ISAPI extension should be allowed. Click Yes.
Figure : The Add Module Mapping prompt that will appear after creating the ISAPI module mapping
6.     Back at the Handler Mappings screen, the newly added handler (in this example IBMCOGNOS-ISAPI) will appear under the Enabled section.
Figure 18: The list of handler mappings now showing the enabled ISAPI module mapping
      Note: for adding new module mapping, we can follow IBM article (  or above steps.

·         Open ‘IBM cognos configuration’ click on to ‘Environment’ tab, change the Gateway URI to http://server name or DNS /ibmcognos/cgi-bin/cognosisapi.dll à click Save & close.

              Note: need to change all cogstartup files like DB re-pointing, normal cogstartup and all required files.

·         Navigate to D:OpenPagescognosc10_64webcontent, open Index.html in notepad and find for ‘cgi-bin/cognos.cgi’ and change to ‘cgi-bin/cognosisapi.dll’ à click save & close

·         Navigate to D:OpenPagescognosc10_64webcontent, open default.html in notepad and find for ‘cgi-bin/cognos.cgi’ and change to ‘cgi-bin/cognosisapi.dll’ à click save & close