Error 404

[JodyW]

I integrated the mashboard into my Information Console war, and deployed on Websphere v6.1.0.27 with a context root of bi10mb.

When I navigate to the Sales tab and click on one of the bars in the "top 10 Reps", I receive the error
404: No target servlet configured for uri: iportal/executerepor.do.
See attached screenshot.

I think this is a context root issue. But, I would like to keep the references relative, as we have different iportal deployments for different iServers.

1. How can I fix the application to show the Rep's top 10 deals instead of the Error 404?

2. Is it possible to fix it without having to hardcode the context root (bi10mb in this case), so I can deploy the same war with minimal customizations.

Similarly I noticed that my jsapi page was not function. I was able to fix the jsapi tab by modifying the mashup.html. I changed the reference

from http://localhost:8700/iportal
to http://<iPortal>/bi10mb

Is it possible to keep it generic where I won't have to customize the mashboard. I have multiple Information consoles deployed on the same Websphere server, and am trying to keep the war files as identical as possible.

Thanks in advance. I'm just stumbling my way through this, as I'm not a programmer. This forum is a great asset.

[bhanley]

You have a couple issues here

1) the PECS event to show the Rep's top 10 deals. This is a link built out in the BIRT report design. The Hyperlink on the table refers to this link. You would need to take the report design off the server and update the build of the hyperlink inside BIRT. Then re-deploy the report and all will be well.

2) The JSAPI link is required as that is how the JSAPI core functionality is downloaded. As long as all your different contexts are on the same version of the iServer/Information Console, you could point that URL to a shared point as the JSAPI is not going to change and can be downloaded from anywhere.

The reference application is going to have some references to iPortal coded into it as it is intended to function with Information Console OOTB. Pointing it to different contexts will require some basic tweaking as you are experiencing. When you build out your won solutions, this requirement of being cross-context deployable can easily be factored for.