Slow Performance When Opening Forms Using a Dial-Up Connection

Scenario:

Opening a form using a slow network connection (for example, with a modem) is slow.

Solution:

You can increase the network bandwidth when opening forms by modifying the web.xml file. This compresses by approximately 90% the data stream sent from the Oracle Hyperion Planning server to the client.

Note:

If you use a WebLogic (all supported versions) Web application server, complete the second procedure, specific to WebLogic. If you use another Web application server, complete the first procedure.

To improve performance for a Web application server other than WebLogic:

With a text editor, open the web.xml file in HyperionPlanning.ear or HyperionPlanning.war.
After the tag </description> and before the tag <listener>, insert these lines:

    <filter>

      <filter-name>HspCompressionFilter</filter-name> <filter-class>com.hyperion.planning.HspCompressionFilter</filter-class>

      <init-param>

         <param-name>compressionThreshold</param-name>

         <param-value>2048</param-value>

      </init-param>

      <init-param>

        <param-name>debug</param-name>      <param-value>1</param-value>

      </init-param>

     </filter>

    <filter-mapping>

      <filter-name>HspCompressionFilter</filter-name>

        <url-pattern>/EnterData.jsp</url-pattern>

    </filter-mapping>
Save the web.xml file.

If you use WebLogic, you must manually modify the .ear file and redeploy it for the Web application server.

To improve performance with a WebLogic application server:

Unzip the HyperionPlanning.ear file to /ear, for example.
Unzip Hyperion.war under /ear to /war.
With a text editor, open /war/WEB-INF/web.xml and modify it using the instructions in step 2 in the preceding procedure.
Compress the content in /war to /ear/HyperionPlanning.war.
Compress the content in /ear into /ear/HyperionPlanning.ear.
Deploy the new HyperionPlanning.ear for the WebLogic Web application server.