Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
top
top

Table of Contents
classcontents

web.xml

The web.xml file provides configuration and deployment information for the Yellowfin application. The Yellowfin web.xml file is located in the directory:
Yellowfin\appserver\webapps\ROOT\WEB-INF
A number of installation-specific settings are stored in web.xml when Yellowfin is installed. These settings are critical to Yellowfin starting and running successfully.

...

Clustering allows Yellowfin to be run on multiple servers off the same database. In order to cluster Yellowfin, the following will need to be added into the web.xml file, with your web services information filled in.

Code Block
xml
xml

<!-- Cluster Management -->
  <servlet>
    <servlet-name>ClusterManagement</servlet-name>  
    <servlet-class>com.hof.mi.servlet.ClusterManagement</servlet-class>  
    <init-param>
      <param-name>ServiceUser</param-name>
      <param-value>admin@yellowfin.com.au</param-value>
    </init-param>
    <init-param>
      <param-name>ServicePassword</param-name>
      <param-value>test</param-value>
    </init-param>
     <init-param>
      <param-name>ServiceAddress</param-name>
      <param-value>/services/AdministrationService</param-value>
    </init-param>
    <init-param>
      <param-name>ServicePort</param-name>
      <param-value>80</param-value>
    </init-param>
    <init-param>
      <param-name>ClusterHosts</param-name>
      <param-value>
         192.168.4.196
      </param-value>
    </init-param>
    <load-on-startup>11</load-on-startup>  
  </servlet>

...

  1. If changes are made to ref codes on one server, all other servers reload their ref codes.
  2. If a view is changed, the old version will be removed from the cache of all servers.
  3. If a new licence is uploaded, all servers are updated.
    Note: You will also need a special licence, which you will have to contact Yellowfin for (support@yellowfin.com.au).

...

The current defaults are 2 (minimum) and 5 (maximum). Amending this connection limit would help performance.

Note: if Yellowfin performance in an issue then changing the connection parameters may assist. However, you will also have to consider your hardware configuration to ensure that it is setup to support the number of concurrent users you have. Please refer to the server capacity white paper for more information.

...

  1. Shut down Yellowfin
  2. Edit the file Yellowfin\appserver\bin\catalina.bat
  3. Find the section:

    Code Block
    none
    none
    
    rem Memory limits.
    rem Use these options to set the Java memory limits.
    rem -Xms128m sets the initial Java heap size to 128Mb
    rem -Xmx512m sets the maximum Java heap size to 512Mb
    rem To set memory limits uncomment the following line:
    rem set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m
    
  4. Remove the "rem" from the start of the last line, and change the Xmx option to your desired max memory setting.
  5. Restart Yellowfin to pick up the changes.

...

  1. Shut down Yellowfin
  2. Edit the file Yellowfin/appserver/bin/catalina.sh
  3. Find the section:

    Code Block
    none
    none
    
    # Memory limits.
    # Use these options to set the Java memory limits.
    # -Xms64m sets the initial Java heap size to 64Mb
    # -Xmx256m sets the maximum Java heap size to 256Mb
    #JAVA_OPTS="$JAVA_OPTS -Xms64m -Xmx256m"
    
  4. Uncomment the last line, and change the Xmx option to your desired max memory setting.
  5. Restart Yellowfin to pick up the changes.

For more information on Performance, see the Yellowfin Forum post: http://www.yellowfinbi.com/YFForum-General-questions-on-performance-?thread=104626