Reconfigure a tc Runtime Instance

In this procedure you make a few simple configuration changes to the current tc Runtime instance. You change a startup-up JVM option (maximum heap size) and change the working directory of the default virtual host for the tc Runtime instance.

It is assumed in this procedure that you have already browsed to the tc Runtime instance that you want to configure, as described in Restart a tc Runtime Instance.

  1. Click the Views > Server Configuration tab:

    The server configuration pages consist of four tabs:

    • Home: Main Server Configuration page.

      There is also an Advanced group for performing more advanced tasks, such as reloading the settings from the tc Runtime instance server.xml file (in which you lose local changes made with the Hyperic user interface), reverting to a previous server configuration, and uploading a new server configuration using a server.xml file.

    • Configuration: Configure tc Runtime startup options, JVM options, context information for all deployed Web applications, default behavior of JSPs and static content, and so on.

    • Resources: Create and configure JDBC datasources.

    • Services: Create and configure tc Runtime services such as virtual hosts, connectors, and so on.

  2. Click the Configuration tab, then the Server Start option in the list on the left.

  3. In the General section on the right, enter 1024 in the Max Heap Size (MB) field.

  4. Click Save at the bottom of the page.

    The message Configuration saved successfully appears at the top, as shown in the following graphic. This means that Hyperic has updated its in-memory cache with your changes. Additionally, a box appears at the top of the page with the heading Changes have been made locally, along with two links to either write (push) the changes to the actual tc Runtime configuration files, such as CATALINA_HOME/bin/setenv.sh (in this case) or CATALINA_BASE/conf/server.xml, or to undo the changes.

    Hyperic displays this box until you save or undo, although you can make additional changes before you save or undo. In this tutorial, you make another change, and then write the changes to disk.

  5. Click the Services tab. In the table, click the Catalina service. This is the default service of tc Runtime.

  6. In the list on the left, click Hosts, then in the table on the right, click the localhost virtual host.

  7. In the Host Properties section, enter new_work_dir in the Work Directory field. This specifies that the localhost will use a different work directory from the default, which is CATALINA_BASE/work. Relative work directories are created under CATALINA_BASE, such as CATALINA_BASE/new_work_dir. The tc Runtime instance uses the work directory to perform its internal work.

  8. Click Save at the bottom of the page.

    The message Configuration saved successfully appears in the top.

    Note

    When you update the tc Runtime configuration using the Hyperic user interface, if the property you are updating was previously specified as a variable (such as ${jmx.port}), tc Runtime replaces that variable with the actual value in the server.xml file. This means, for example, that port="${jmx.port}" would become port="6954". The variable is still set in the catalina.properties file to the old value, but the tc Runtime does not actually use it because the property is now hardcoded in the server.xml file.

  9. In the box at the top titled Changes have been made locally, click Push configuration changes to Tomcat.

  10. Click Push Changes to Server.

  11. In the box at the top, click the restarted link to restart the tc Runtime instance so that the changes take effect.

  12. Click Restart Server.

    The message Server Restarted appears at the top.