Skip to end of metadata
Go to start of metadata

tc Runtime Application Management

The Application Management page, available when a tc Runtime instance or a group of tc Runtime instances is selected, enables an authorized user to manage applications deployed that server instance or group.

The HQ super-user can use all the tc Runtime Application Management features of the HQ UI.  If, however, you log on to the HQ UI as a non-super-user, then that user must have certain permissions to be able to use the tc Runtime features.  See User Permissions Required to Use the tc Runtime Features for details.

An HQ Group is not a Cluster

An HQ group is not equivalent or similar to a tc Runtime cluster.

  • An HQ group is a set of other managed resources. An authorized user can create a group and assign resources to it. A group whose members are all of the same resource type is referred to as a compatible group. You can manage and monitor the resources in a compatible group at the group level. Grouping tc Runtime instances allows you manage applications across multiple tc Runtime instances.
  • A tc Runtime cluster enables session replication. Clustering behavior is defined in a tc Runtime instance's server.xml file.

Navigating to a tc Runtime Instance Or Group

To navigate to the Application Management page of a tc Runtime instance or group.

  1. Click Resources > Browse at the top of the HQ Dashboard.
    • To browse to a server instance:
      • Click Servers to view a list of of the servers to which you have access.  tc Runtime instances have the server type "SpringSource tc Runtime 6.0". Apache Tomcat server instances have the server type "Tomcat X.X".
    • To browse to a group of servers:
      • Click Compatible Groups/Clusters to view a list all the compatible groups to which you have access. Groups of tc Runtime have the type "SpringSource tc Runtime 6.0".
  2. In the table, click the name of the tc Runtime instance or group to which you want to navigate.
  3. Click Views > Application Management.

Creating tc Runtime Groups

Grouping tc Runtime instances eases the process of managing server instances and applications. For example, you can deploy an application to group of tc Runtime with a single command, instead of deploying to each instance individually. To create a group of tc Runtime instances:

  1. Click Resources > Browse at the top of the HQ Dashboard.
  2. Click Servers to list servers in inventory to which you have access. (Note: Only server instances that have been auto-discovered by HQ and added to inventory appear). tc Runtime instances have the server type "SpringSource tc Runtime 6.0". Apache Tomcat server instances have the server type "Tomcat X.X".
  3. Check the box to the left of each tc Runtime instance you want to include in the new group.
  4. Click Group.
  5. Enter a name for the group (required) and a description and location as desired.
  6. Click OK.

Listing Applications

Navigate to the Application Management page for a server instance or group. Deployed applications are listed in the Deployed Applications section of the page. For a group, the table lists all applications deployed to all servers in the group. The table shows:

  • Status - The state of the application - either "Running" or "Stopped".  For a group of servers:
    • "Running" or "Stopped" indicates that all instances of the application on all servers in the group have that state.
    • A numeric value indicates the number of servers upon which the application's state is "Running".
  • Sessions - The number of current active sessions for the application.

NOTE: Only applications on running tc Runtime instances appear.  HQ returns an error for application hosts that are not running.

Deploying Applications

Deploying an application is the process of uploading it to tc Runtime and making it available to users. You can deploy an application to a single tc Runtime instance or to a group of tc Runtime instances. If you deploy to a group, the application will be deployed to each of tc Runtime instance in that group, enabling users to run the application from any of the tc Runtime instances in the group.

You can deploy an application from a WAR file located:

  • on your local file system (on the the same machine as the browser you are using to connect to HQ's web user interface), or 
  • on the computer on which the tc Runtime resource is running.

Whether the WAR file is local or remote, you can either enter a new context path (string that uniquely identifies the Web application in the URL used to invoke it), or use the default value, which is the name of the WAR file, without the".war" extension.

  1. Navigate to the Application Management page for a tc Runtime instance or group.
  2. Depending on the location of the WAR file for the application, either:
    • Click Browse in the Deploy Application From Local Machine section to browse to the file's location.
    • Enter the full path to the WAR file on the computer hosting the tc Runtime resource in the Deploy Application from Server Machine section.
  3. As desired, enter a context path in the Context path text box.
  4. Optionally check the Use cold deployment strategy if you want the tc Runtime instance to shutdown, deploy the application, and then start up again. By default (if box is unchecked), the tc Runtime instance hot-deploys the application, which means it does not shutdown then restart but simply deploys the application while the instance is still running. Use the cold deployment strategy if you want to avoid common hot deployment errors, such as running out of PermGen space. The PermGen space holds the metadata about classes that have been loaded/created in the JVM.
  5. Click Upload and Deploy or Deploy, whichever is appropriate.
  6. See the top "Results of the last operation" section for details about the result of deploying the application. When you deploy an application to tc Runtime, the application is started.

Undeploying Applications

Undeploying an application removes it from the tc Runtime instance or group. If you want to temporarily prevent users from access an application, stop it rather than undeploy it. See Stopping Applications.

  1. Navigate to the application management page of a tc Runtime instance or group.
  2. In the Deployed Applications section, check the box to the far-left of the application(s) you want to undeploy.
  3. Click Undeploy. HQ removes the application from the list of deployed applications.
  4. See the top "Results of the last operation" section for details about the results of undeploying the application.

Starting Applications

Starting an application makes it available to users. You must have previously deployed the application to be able to start it.

  1. Navigate to the application management page of a tc Runtime instance or group.
  2. In the Deployed Applications section, check the box to the far-left of the application(s) you want to start.
  3. Click Start. The status of the application changes to "Running".
  4. See the top "Results of the last operation" section for details about the result of starting the application.

Stopping Applications

Stopping an application makes it unavailable to users.

  1. Navigate to the application management page of a tc Runtime instance or group.
  2. In the Deployed Applications section, check the box to the far-left of the application(s) you want to stop.
  3. Click Stop. The status of the application changes to "Stopped".
  4. See the top "Results of the last operation" section for details about the result of stopping the application.

Reloading Applications

When you reload an existing application, it shuts itself down and then reloads itself. For additional details, see Reload an Existing Application on the Apache Tomcat 6.0 Web site.

  1. Navigate to the application management page of a tc Runtime instance or group.
  2. In the Deployed Applications section, check the box to the far-left of the application(s) you want to reload.
  3. Click Reload. The status of the application changes to "Running."
  4. See the top "Results of the last operation" section for details about the result of reloading the application.
Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.