Cognos 5: frontend and server parameter transfer

front-end and server parameter transfer
Cognos content is generally displayed as a specific frame or a new window on the webpage. We can collect query conditions submitted by users in a unified external user interaction interface (generally implemented using JSP). After checking the validity of user input, pass these parameters to the Cognos gateway in the form of post (or get) according to the standards agreed by Cognos. The Cognos gateway returns the user query results to the frame.
based on different backend servers (ppes and IWR), there are two rules for passing parameters.
calling ppes content (cube/ppx)
the main parameters used are
parameter name explanation
display mode of DC reports, Q is dynamic HTML, R is the release location of PDF
E access content on ppes
dimension code value to be filtered by dm
category code of the corresponding filtering value for the FC-filtered dimension
ZZ indicates that the parameter transfer is complete.

The following is an example of an interface call:
Assume that the server name is servername.
After the ppx Report is published to the enterprise server, it is under the root directory of the Enterprise Server and named testreport.
If you want to access this report, you can use the following URL to call the report: http: // test/Cognos/cgi-bin/ppdscgi.exe? Dc = R & E = % 2 ftestreport
If you want to access a cube that can be dynamically analyzed, the corresponding URL is
Http: // test/Cognos/cgi-bin/ppdscgi.exe? Dc = Q & E = % 2 fcubename
Here: % 2f is the identifier used by a URL, and its prototype is the symbol "/".
If the report or cube is published in the test folder, the corresponding URL is:
Http: // test/Cognos/cgi-bin/ppdscgi.exe? Dc = R & E = % 2 ftest % 2 ftestreport

You can access any reports or cubes published to powerplay Enterprise Server through the above interfaces. To pass filtering conditions to reports or cubes, use the following call standards.
For example, an ICBC report is released on Enterprise Server. The report provides four parameter passing interfaces (years, products, locations, and channles ). You can choose to pass parameters to several interfaces.
If "Products" is set to "outdoor products ",
Http: // test/Cognos/cgi-bin/ppdsc... 20 products & ZZ = x
& Amp; DM = products // indicates the dimension products to be filtered.
& Fc = 0% 09 outdoor % 20 products // indicates the dimension products filter value

If two dimensions are filtered, for example, "Products" and "locations ",
Http: // info/Cognos/cgi-bin/ppdsc... 1% 09 Europe & ZZ = x
The & DM = products % 09 locations // dimensions are separated by % 09
& Fc = 0% 09 outdoor % 20 products % 091% 09 Europe // The dimension value starts from 0.

If it is to filter three dimensions, for example, to filter "Products", "locations" and "channels", call
Http: // info/Cognos/cgi-bin/ppdsc... ndependent & ZZ = x
The & DM = products % 09 locations % 09 channels // dimensions are separated by % 09
& Fc = 0% 09 outdoor % 20 products % 091% 09 Europe % 092% 09 independent
// The dimension value starts from 0.
Add & ZZ = x after each URL, indicating that the parameter transfer is complete.
Note: Both dimension names and dimension filter values must use their respective Code attributes instead of the name attribute.
Call CONTENT ON IWR
The gateway for IWR to accept parameters is/Cognos/cgi-bin/imrap. cgi. The accepted parameters can be divided into two types:
1) report parameters: Specify IWR servers and report numbers.
2) condition parameters: Mainly pass the user's filtering conditions.

report parameters:
parameter description
RID: this is the report sequence number, which can be found in IWR Server Admin.
IU: This is a reserved parameter, fixed value: imrap
Cd: Report display mode; R: Run; V: View
psrv: Reserved string, the
condition parameters can be obtained from the URL of any report. Generally, they are set according to the user's prompt in the IWR report. Generally, they must be consistent with the settings in script manager in Cognos powerprompts.

For example, <% getuservar ("T10") %> In the Script Editor above indicates that you want to send imrap to the gateway. CGI passes the condition parameter T10, and the parameter value is used as the report's promptu value (through the setpromptvalue statement) to filter the report data.
The following is an example of passing IWR parameters. To illustrate the problem, an HTML is used to pass the required parameters. In actual environments, JSP is often used to dynamically determine the parameters to be passed.
<HTML>
<! -- Place this webpage in the webcontent directory of the server where IWR is installed and access it with http: // hostname/Cognos/to_report.htm -->
<! -- Of course, you must first publish the reports package to IWR and set the point of powerprompts. -->
<! -- Then look at the report's RID and change the RID parameter in this webpage -->
<! -- Access this webpage through IE -->
<Head>
<Meta http-equiv = "content-language" content = "ZH-CN">
<Meta http-equiv = "Content-Type" content = "text/html; charset = gb2312">
<Meta name = "generator" content = "Microsoft FrontPage 4.0">
<Title> powerprompts interface demo </title>
</Head>

<Body>
<Form name = "mainform" method = "Post" Action = "/Cognos/cgi-bin/imrap. cgi"> <! -- Submit imrap. cgi to the server -->

<! -- The following parameters are the variables required by imrap. cgi -->
<Input type = "hidden" name = "RID" value = "24"> <! -- This is the report serial number, which can be found from IWR Server Admin -->
<Input type = "hidden" name = "IU" value = "imrap"> <! -- This is a reserved parameter, with a fixed value -->
<Input type = "hidden" name = "cd" value = "R"> <! -- This is the report display method, R is run, V is View -->
<Input type = "hidden" name = "psrv" value = "1-43434f46464545-8020-0-2f636f676e6f73-13-0 --"> <! -- This is a reserved string that can be obtained from any report URL -->

<! -- The following parameters are the names of the prompts in the report to be set in powerprompts. set their values here -->
<! -- Through this interface, you can flexibly set each prompt, regardless of ASP or JSP, even such a common web page. -->
<Input type = "hidden" name = "ordernumber" value = "125"> <! -- The value of prompt named ordernumber is 125 -->

<P> <input type = "Submit" value = "click here to view the result. "Name =" B1 "> </P>
</Form>
</Body>
</Html>