View Source

h1. Problem

Sometimes it is necessary to access the web interface over very slow links, such as international WAN lines, or slow VPNs. 

While initial operation will give you data on the pages, after a while, you may see dropped connection messages on the Status viewer or Event console applications, if your link is slow enough. 

h1. Solution

Adjust the retires for the status and event console applications:

Steps:
1) stop gwservices:
{code}
/etc/init.d/groundwork stop gwservices
{code}
{note:title=Note}
This will log out all users.
{note}

2) Copy StatusViewer /usr/local/groundwork/foundation/container/webapps/jboss/jboss-portal.sar/portal-statusviewer.war to a tmp directory (e.g /tmp/status)
3) Copy Event Console /usr/local/groundwork/foundation/container/webapps/jboss/jboss-portal.sar/portal-console.war to a tmp directory (e.g /tmp/console)
4) cd to the temp directory:
{code}
cd /tmp/status
{code}
5) Extract the WAR file:
{code}
jar xf portal-statusviewer.war
{code}

6) edit web.xml:
{code}
vi WEB-INF/web.xml
{code}
7) Insert the following XML fragment after line 20:
{code}
<context-param>
<param-name>com.icesoft.faces.heartbeatRetries</param-name>
<param-value>15</param-value>
</context-param>
{code}
8) Save the web.xml file.
9) Delete the file /tmp/status/portal-statusviewer.war
10) Repackage the war file:
{code}
jar cf ../portal-statusviewer.war
{code}
{note:title=Note:}
This will create a new war file.
{note}
11) Copy the war file you created into place:
{code}
cp portal-statusviewer.war /usr/local/groundwork/foundation/container/webapps/jboss/jboss-portal.sar/
{code}
12) start gwservices
{code}
/etc/init.d/groundwork start gwservices
{code}


Repeat steps 4-9 for portal-console.war