nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

read the information console name

jar

Hello,
 
We try to use multiple information consoles to have a different login experience for different customers. As these work on the same ihub portal we want to read the information console name (default is iportal) to filter the reports depending on which information console they are logging in from.
 
I have a variabele defined as follows:
reportContext.getHttpServletRequest().getContextPath();
 
And that gives me /iportal of /test depending on which information console I use. But this is in the designer PRO
 
As soon as I publish this report to the server i get an error :
Execute report failed (There is an error in processing your request. Error code: 17070.).
 
This is a very common error but no details available. This is on a iHub server 3.1 version. But the same fails on Suite 16 test server we have running. 
 
How can I get the context name from the server that might work on a server?
 
Any tips are appreciated.
 
Jeroen

Find more posts tagged with

Comments

Clement Wong

Jeroen,
 
Are the different customers on different iHub volumes, with unique names? If so, then you can use:
<pre class="_prettyXprint">
reportContext.getAppContext().get("VolumeName");</pre>
The context path of the Information Console will be available inside the report within the iHub during generation.
 
If the volume name option does not work for you, then another option is to pass session variables from Information Console to your BIRT report, in your case, the customer ID. All you would need is just a few lines of code in a JSP. After you have authenticated the user in Info Console, you can AJAX a call to a JSP to set the variable(s), or include the code into a common page after logging in. 
In the attached sample JSP, youâ€™ll see that the session parameter â€œmyParamâ€ value is set to â€œHi there!â€. Then the page is redirect to a report. 
<pre class="_prettyXprint">
<jsp:useBean id="SessionDefaultParameterValue" scope="session" class="com.actuate.parameter.SessionLevelParameter" />
<%
 SessionDefaultParameterValue.setParameterValue("myParam","Hi there!");
%></pre>
Again, these two lines can be anywhere that is in a common Information Console page. You would only need it to be called once, or multiple times if you want allow it changed during the session. 
The sample report is to demonstrate that the report parameter changes based on the parameters set via SessionDefaultParameterValue. You are NOT limited to just one parameter, and you can set as many parameters as you need. 
For reference, should you ever need to change the name of SessionDefaultParameterValue, you can do this via Information Consoleâ€™s web.xml. It will require a restart of the application server. 

<pre class="_prettyXprint">
 <context-param>
 <param-name>SESSION_DEFAULT_PARAMETER_VALUE_ID</param-name>
 <param-value>SessionDefaultParameterValue</param-value>
 </context-param>
</pre>

jar

Hello Clement,
 
Thank you for your suggestion and examples. 
We finally sat down with our system engineer and got this working. My report shows a different piece of the report with different data for each client depending on the information console they are logging in from. 
 
Very nice ...
 
But it is not working when we have the report added to a dashboard. All our client get directed after login to the __default_dashboard.dashboard in the root folder. We use a dashboard because we also offer the client a language choice from a combobox selection gadget.
 
When the report is run from the folder-tree in iHub (the report itself) it is working correctly but when the report is on a dashboard it still uses the default value that is set in the report (being "default"). The parameterTest.rptdesign you added to your solution also gives the default value when used in a dashboard, and the correct value when run as a report. 
 
Any tips on how to resolve that?
 
Kind regards,
Jeroen

jar

We tried a little more with this and it looks like the sessionDefaultParameterValue is not correctly passed with a dashboard. 
 
We added an alert in the dashboardcontent.jsp and it alerted us with the correct value for each information console so we know this is available when the dashboard is loaded. The report also picks the parameter set in login.jsp because when we run the report directly it is using the correct value. 
 
But the report on the dashboard together does not work. A we concluded that the parameter is available from an alert on the dashboardcontent.jsp it looks like a bug or we are missing something but no clue to what we are missing. 
 
How to proceed? We are using iHub 3.1.

Clement Wong

The issue you are encountering is fixed in iHub 16. The workaround in your version is to make the parameter NOT hidden.
 
In my sample report, just change the design so that myParam is not a hidden parameter.