Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Intelligence (Analytics)
ways to remove iportal from url and work with http://mymachine:8700/
bcmp
<p>What is the procedure to remove the /iportal from url and make it work with <a data-ipb='nomediaparse' href='
http://mymachine:8700/'>http://mymachine:8700/</a></p>
;
<p> </p>
<p>Thanks</p>
Find more posts tagged with
Comments
Clement Wong
<p>Yes, it's possible. What version of BIRT iHub are you using?</p>
<p> </p>
<p>How did you deploy Information Console? Are you using the embedded Tomcat, or did you deploy into a separate application server?</p>
bcmp
<p>version 3.1</p>
<p>Standard deployment, using the embedded tomcat</p>
Clement Wong
<p>The quickest way to have <a data-ipb='nomediaparse' href='
http://yourserver:8700'>http://yourserver:8700</a>redirect
to Information Console is to create an <strong>index.jsp </strong>under C:\Actuate3\BIRTiHubVisualization\modules\BIRTiHub\iHub\web\webapps\ROOT with the following:</p>
<pre class="_prettyXprint">
<%
response.sendRedirect("/iportal");
%></pre>
<p>Otherwise, to change the actual context path to / instead of /iportal will require several files to change.<br>
</p>
bcmp
Much appreciated, if you could Share the ways to change the context part
Clement Wong
<p><strong>[For iHub 3.1 – Embedded Information Console]</strong><br><br>
1. Stop iHub.</p>
<p> </p>
<p>
2. Backup and edit <strong>acpmdconfig.xml</strong> under <em>C:\Actuate3\BIRTiHubVisualization\modules\BIRTiHub\iHub\etc</em><br><br>
Remove the two "/iportal" in path and samlEntityID:<br><br><span style="font-family:'courier new', courier, monospace;"> <Context path="/iportal" docBase="C:/Actuate3/BIRTiHubVisualization/modules/BIRTiHub/iHub/web/iportal" welcome="login.jsp" workDir="C:/Actuate3/BIRTiHubVisualization/modules/BIRTiHub/iHub/data/web/work/localhost/iportal" jarsToSkip="a*.jar;b*.jar;c*.jar;e*.jar;f*.jar;g*.jar;h*.jar;i*.jar;ja*.jar;m*.jar;n*.jar;o*.jar;r*.jar;sa*.jar;sc*.jar;sh*.jar;sl*.jar;t*.jar;w*.jar;x*.jar" crossContext="true" samlEntityID="<a data-ipb='nomediaparse' href='
http://actuateone.localdomain:8700/iportal'>http://actuateone.localdomain:8700/iportal"</a>sessionCookiePath="/"/>
; </span><br><br>
AFTER EXAMPLE</p>
<p><span style="font-family:'courier new', courier, monospace;"> <Context path="" docBase="C:/Actuate3/BIRTiHubVisualization/modules/BIRTiHub/iHub/web/iportal" welcome="login.jsp" workDir="C:/Actuate3/BIRTiHubVisualization/modules/BIRTiHub/iHub/data/web/work/localhost/iportal" jarsToSkip="a*.jar;b*.jar;c*.jar;e*.jar;f*.jar;g*.jar;h*.jar;i*.jar;ja*.jar;m*.jar;n*.jar;o*.jar;r*.jar;sa*.jar;sc*.jar;sh*.jar;sl*.jar;t*.jar;w*.jar;x*.jar" crossContext="true" samlEntityID="<a data-ipb='nomediaparse' href='
http://actuateone.localdomain:8700'>http://actuateone.localdomain:8700"</a>sessionCookiePath="/"/>
; </span><br><br><br>
3. Backup and modify <strong>Shingdig.properties</strong> under <em>C:\Actuate3\BIRTiHubVisualization\modules\BIRTiHub\iHub\web\iportal\WEB-INF\classes</em><br><br>
Find "/iportal" and replace with "" (empty string) in the three occurrences:<br><br><span style="font-family:'courier new', courier, monospace;"> Line 37: shindig.signing.global-callback-url=<a data-ipb='nomediaparse' href='
http://ActuateOne:8700/iportal/gadgets/oauthcallback'>http://ActuateOne:8700/iportal/gadgets/oauthcallback</a><br>
;
Line 55: shindig.content-rewrite.proxy-url=/iportal/gadgets/proxy?url=<br>
Line 57: shindig.content-rewrite.concat-url=/iportal/gadgets/concat?</span><br><br>
AFTER EXAMPLE<br>
</p>
<p><span style="font-family:'courier new', courier, monospace;">shindig.signing.global-callback-url=<a data-ipb='nomediaparse' href='
http://yourihubserver:8700/gadgets/oauthcallback'>http://yourihubserver:8700/gadgets/oauthcallback</a><br>
;
shindig.content-rewrite.proxy-url=/gadgets/proxy?url=<br>
shindig.content-rewrite.concat-url=/gadgets/concat?</span><br><br><br>
4. Backup and modify <strong>container.js</strong> under <em>C:\Actuate3\BIRTiHubVisualization\modules\BIRTiHub\iHub\web\iportal\WEB-INF\classes\containers\default </em><br><br>
Find and replace "/iportal" with "" (empty string) to remove from the fourteen instances.<br><br><span style="font-family:'courier new', courier, monospace;"> Line 78: "gadgets.jsUriTemplate" : "
http://%host%/iportal/gadgets/js/%js%",<br>
;
Line 86: "gadgets.uri.js.path" : "/iportal/gadgets/js",<br>
Line 90: "gadgets.uri.oauth.callbackTemplate" : "//%host%/iportal/gadgets/oauthcallback",<br>
Line 98: "gadgets.osDataUri" : "
http://%host%/iportal/rpc",<br>
;
Line 117: "gadgets.uri.js.path": "/iportal/gadgets/js",<br>
Line 121: "gadgets.uri.concat.path" : "/iportal/gadgets/concat",<br>
Line 126: "gadgets.uri.proxy.path" : "/iportal/gadgets/proxy",<br>
Line 138: "proxyUrl" : "//%host%/iportal/gadgets/proxy?container=default&refresh=%refresh%&url=%url%%rewriteMime%",<br>
Line 139: "jsonProxyUrl" : "//%host%/iportal/gadgets/makeRequest"<br>
Line 144: "urlTemplate" : "<a data-ipb='nomediaparse' href='
http://ActuateOne/iportal/gadgets/profile?{var}'>http://ActuateOne/iportal/gadgets/profile?{var}",</a><br>
;
Line 149: "urlTemplate" : "<a data-ipb='nomediaparse' href='
http://ActuateOne/iportal/gadgets/canvas?{var}'>http://ActuateOne/iportal/gadgets/canvas?{var}",</a><br>
;
Line 246: "path" : "
http://%host%/iportal/rpc",<br>
;
Line 248: "invalidatePath" : "
http://%host%/iportal/rpc",<br>
;
Line 274: "endPoints" : [ "
http://%host%/iportal/rpc"
; ]</span><br><br>
<br>
5. <span style="color:#0000ff;">[OPTIONAL STEP]</span> If you embed editable dashboards with JSAPI, you will have missing images in the Manage Data and Share dialogs. This was fixed in iHub 3.1.1. Here is the workaround:<br><br>
A. Backup and modify <strong>feature18501.js</strong> under <em>C:\Actuate3\BIRTiHubVisualization\modules\BIRTiHub\iHub\web\iportal\iv\dialog</em><br>
B. Find the exact string (staring with a double quote)<span style="font-family:'courier new', courier, monospace;"><strong> "iportal/jsapi</strong></span><br>
C. Replace all 4 instances with <span style="font-family:'courier new', courier, monospace;"><strong>actuate.Viewer().getDefaultIportalUrl() + "iportal/jsapi</strong></span><br><br>
// NOTE: There will be 4 instances for two buttons and their hover images.<br><br>
EXAMPLE BEFORE<br>
<span style="font-family:'courier new', courier, monospace;">icon:"iportal/jsapi/actuate/dialog/images/greenbutton-arrow-right.png"</span><br><br>
EXAMPLE AFTER<br><span style="font-family:'courier new', courier, monospace;"> icon: actuate.Viewer().getDefaultIportalUrl() + "iportal/jsapi/actuate/dialog/images/greenbutton-arrow-right.png"</span><br><br><br>
6. Restart iHub.<br><br><br>
Clear the browser's cache, or use private/incognito mode before testing.<br><br>
</p>
bcmp
<p>Thanks!</p>
<p> </p>
<p>Could you share what are the pros and cons of approach 1 & 2.</p>
Clement Wong
<p>The main difference is that it's minimal change being only 1 line, but references will need to have /iportal for resource access.</p>
<p> </p>
<p>Otherwise, you'll be manually editing a few files, which may or may not lead to typos or mistakes. You'll have the backup file in case you need to revert.</p>