Getting Started with vfabric tc Server

Transcription

1 Getting Started with vfabric tc Server VMware vfabric Cloud Application Platform 5.0 VMware vfabric tc Server 2.6 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see EN

2 You can find the most up-to-date technical documentation on the VMware Web site at: support. The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: Copyright 2012 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. VMware, Inc., 3401 Hillview Avenue, Palo Alto, CA

3 Table of Contents 1. About Getting Started with vfabric tc Server... 1 Intended Audience Quick Start Overview of tc Server... 5 Usability Enhancements to Apache Tomcat... 5 Easy Configuration and Monitoring with the Hyperic tc Server Plug-In... 5 Agile Application Development with Spring Insight Developer... 6 Application Cluster Monitoring with Spring Insight Operations... 6 Enhanced Diagnostics... 7 tc Server Command-Line Interface and Scripts... 7 tc Server Editions... 7 How tc Server and Hyperic Work Together... 9 Related Documentation Comparing tc Runtime and Apache Tomcat Standard Application Server Features Enterprise Application Server Features Advanced Configuration Features Operations Features Installing vfabric tc Server Meeting System Software Requirements for tc Server Installing tc Server as Part of vfabric Cloud Application Platform Install tc Server Developer Edition Install tc Server Standard Edition (tc Runtime Only) Install tc Server Standard Edition and Hyperic Management Components Activate a Local vfabric tc Server License Overview of tc Server Directories, Variables, and Configuration Files Enabling Bash Completion for tc Server Scripts Setting Up Unix Users for tc Server and Hyperic Post-Installation Tasks Creating a New tc Runtime Instance Starting and Stopping tc Runtime Instances Windows: Installing the Hyperic Server and Agents as Windows Services Starting and Stopping the Hyperic Server and Agents Getting Started with the Hyperic User Interface Deploying Applications to tc Runtime Instances Uninstalling tc Server: Typical Steps Upgrade and Migration Guide Upgrading a 2.0.X, 2.1.X, or 2.5.X tc Server Installation to Upgrading a 2.6.X tc Runtime to the Latest Version Tutorial: Using Hyperic to Configure and Manage tc Runtime Instances Before You Begin Restart a tc Runtime Instance Reconfigure a tc Runtime Instance Deploy a Web Application to a tc Server Runtime Instance Add tc Runtime Instances to the Favorite Resources Portlet Create an Hyperic Group of Multiple tc Runtime Instances Monitoring tc Runtime Instances Manage the Preconfigured Deadlock Detected Alert Tutorial: Very Simple HelloWorld Web Application Before You Begin Creating and Deploying the HelloWorld Web Application Java Source of the Hello.java Servlet VMware vfabric tc Server 2.6 iii

4 JSP Source for the hello.jsp JSP... Sample web.xml File... Sample Default index.html File... Ant Build File to Compile and Package the Example Troubleshooting... Hyperic: Resources Not Showing up in the Hyperic User Interface... Hyperic: Errors When Trying to Add an Auto-Discovered Resource... Hyperic Agent: Errors When Starting on Solaris... tc Runtime: Hot Redeploy/Stop/Undeploy on Windows Fails... tc Runtime: Error When Running a Web Application on tc Runtime and Using SpringSource Tool Suite... tc Runtime: JVM Performing a Full GC... iv Getting Started with tc Server

5 About Getting Started with vfabric tc Server 1 1. About Getting Started with vfabric tc Server Getting Started with vfabric tc Server describes product concepts and provides setup instructions for VMware vfabric tc Server, a component of the VMware vfabric Cloud Application Platform. Read the documentation to learn how to create, start, and stop tc Runtime instances; deploy Web applications; and use the VMware vfabric Hyperic management tool to monitor tc Runtime instances. This documentation includes tutorials for creating and deploying a HelloWorld Web application and for using vfabric Hyperic with tc Server. Intended Audience Getting Started with vfabric tc Server is intended for anyone who wants to install, configure, and use tc Server to develop or to serve Web applications. VMware vfabric tc Server 2.6 1

6 2 Getting Started with tc Server 2 About Getting Started with vfabric tc Server

7 Quick Start 3 2. Quick Start This section provides quick start instructions for installing VMware vfabric tc Server Standard Edition, creating a tc Runtime instance, and starting the tc Runtime instance. tc Runtime is the runtime component of tc Server. If you are upgrading an existing tc Server installation, see the upgrade documentation. If you are installing tc Server Developer Edition, see Installing tc Server. If you obtain tc Server as part of vfabric Platform, first complete the license activation and installation procedures in Getting Started with vfabric Cloud Application Platform. Then follow the procedures here to install tc Server and create and start a tc Runtime instance. Install tc Server 1. Download and install a JDK or JRE on the computer on which you are installing tc Server. See Required Software: JDK or JRE. 2. Determine the user that is going to create and run the tc Runtime instances, and create it if necessary. Consider creating a user dedicated to tc Server tasks and disabling its interactive login for security purposes. On Unix, never run tc Runtime instances as the root user. See Setting Up Unix Users for tc Server and Hyperic. For clarity, it is assumed in this topic that you will install and run tc Server as the tcserver user. 3. Login to the computer on which you are installing tc Server as the appropriate user, such as tcserver. If you have disabled interactive login, login as the root user and use su - tcserver to become the user. 4. Open a terminal (Unix) or Command Prompt (Windows) and create a directory to contain the tc Runtime component (such as /opt/vmware) if it doesn't already exist. Unix example: prompt$ mkdir /opt/vmware Windows example: prompt> mkdir \opt\vmware 5. From the VMware Download Center, download the most recent vfabric-tc-server-standard-version.zip file and unzip the contents into the directory you created in the preceding step. The version in the zip file name is the version number, for example RELEASE. This is all that is required to install tc Runtime; there is no installer program. For example, in Unix, if you specified a directory called /opt/vmware in the preceding step and downloaded the Standard Edition file to your home directory: prompt$ cd /opt/vmware prompt$ unzip ~/vfabric-tc-server-standard release.zip In Windows Explorer, double-click the ZIP file you downloaded to launch the Windows Extraction Wizard and extract the file into the directory you created in the preceding step. After you unzip the ZIP file you will have a directory called /opt/vmware/vfabric-tc-serverstandard-version. This directory contains all the tc Runtime files and directories. VMware vfabric tc Server 2.6 3

8 4 Getting Started with tc Server Create and start a tc Runtime instance 1. From your terminal window or Command Prompt, change to the tc Runtime directory and execute the tcruntimeinstance command to create a basic tc Runtime instance (called myserver in the examples). VMware recommends that you use the --instance-directory option to specify the full pathname of a directory in which the new instance will be created, and that this directory be different from the installation directory. Be sure the tcserver user can write to this directory and that the directory already exists. Unix example: prompt$ cd /opt/vmware/vfabric-tc-server-standard release prompt$./tcruntime-instance.sh create --instance-directory /var/opt/vmware/vfabric-tc-server-standard myserver Windows example: prompt> cd \opt\vmware\vfabric-tc-server-standard release prompt> tcruntime-instance.bat create --instance-directory \var\opt\vmware\vfabric-tc-server-standard myserver 2. (Windows only) Use the tcruntime-ctl command to make the new runtime instance a Windows service; use the -n option to specify the directory in which the instance is located: prompt> tcruntime-ctl.bat myserver install -n \var\opt\vmware\vfabric-tc-server-standard 3. Execute the tcruntime-ctl command to start the new tc Runtime instance; use the -n option to specify the directory in which the instance is located. Unix example: prompt$./tcruntime-ctl.sh myserver start -n /var/opt/vmware/vfabric-tc-server-standard Windows example: prompt> tcruntime-ctl.bat myserver start -n \var\opt\vmware\vfabric-tc-server-standard To confirm that the tc Runtime instance is running, invoke its welcome page in a browser. Use the URL where host is the name or IP address of the computer on which the tc Runtime instance is running (localhost if local). What to do next Read about tc Server features Install tc Server Developer Edition Install vfabric Hyperic to manage tc Runtime instances Read about options for creating tc Runtime Instances 4 Quick Start

9 Overview of tc Server 5 3. Overview of tc Server VMware vfabric tc Server is a Web application server based on open-source Apache Tomcat. It preserves the best of Tomcat and adds many mission-critical operational capabilities that are unavailable in the open-source product. tc Server harnesses the power of traditional JEE architectures and eliminates their complexity and performance drawbacks, making it easier, faster, and more cost-effective to build and run cloud-ready applications. With its lean architecture and small, 10MB memory footprint, tc Server requires significantly fewer resources than conventional servers, which allows for greater server density in virtual and cloud environments. Subtopics Usability Enhancements to Apache Tomcat Easy Configuration and Monitoring with vfabric Hyperic Agile Application Development with Spring Insight Developer Application Cluster Monitoring with Spring Insight Operations Enhanced Diagnostics tc Server Command-line Interface and Command Scripts tc Server Editions How tc Server and Hyperic Work Together Related Documentation Usability Enhancements to Apache Tomcat The tc Server runtime component, known as tc Runtime, offers usability advantages that make it easier, faster, and more flexible to configure and operate than Apache Tomcat. tc Runtime includes the following usability enhancements: Improved out-of-the-box configuration. In most cases, you can use tc Server immediately after you install it, with no additional configuration. Easy creation of a tc Runtime instance with the tcruntime-instance command script. You can leverage additional (optional) configuration features by specifying prepackaged templates when you create a tc Runtime instance, such as automatically configuring clustering or SSL. Easy and intuitive startup of a tc Runtime instance on both UNIX and Windows platforms. Default configuration of high-concurrency JDBC connection pool in new tc Runtime instances. For a detailed comparison of tc Server and Apache Tomcat features, see Comparing tc Runtime and Apache Tomcat. Easy Configuration and Monitoring with the Hyperic tc Server Plug-In Hyperic includes a tc Server plug-in that gives tc Server Standard Edition customers access to the Hyperic enterprise application management tool. Hyperic can manage and monitor tc Runtime instances, Spring-powered applications, and a variety of nonvmware platforms and application servers such as Apache Tomcat. The server instances and applications can be running on multiple computers. Hyperic provides a single console with powerful dashboards through which you can easily check the health of your applications. The Hyperic tc Server plug-in gives you the following capabilities: VMware vfabric tc Server 2.6 5

10 6 Getting Started with tc Server Manage the lifecycle of tc Runtime instances by starting, stopping, and restarting a local or remote instance. Manage the lifecycle of a group of tc Runtime instances that are distributed over a network of computers. Configure a single instance of tc Runtime. Configuration options include the various port numbers to which the tc Runtime instance listens, JVM options such as heap size and enabling debugging, default server values for JSPs and static content, JDBC datasources, various tc Runtime connectors, and so on. Using the tcsadmin command-line tool, configure a group of tc Runtime instances. Deploy a Web application from an accessible file system, either local or remote. You can deploy to a single tc Runtime instance or to a predefined group of servers. Manage the lifecycle of applications deployed to a single tc Runtime instance or group of servers. Application lifecycle operations include start, stop, redeploy, undeploy, and reload. In addition to the preceding tc Runtime-specific Hyperic tasks, you perform the standard tasks : Inventory the resources on your network. Monitor resources. Receive alerts on problems with resources. The Hyperic plug-in includes a variety of preconfigured alerts. Control resources. Agile Application Development with Spring Insight Developer Spring Insight Developer, bundled with tc Server Developer Edition, makes it easy for application developers to observe the runtime behavior of Web applications. It allows you to see what is happening deep in the application, while it is running, with no required instrumentation. The visibility Spring Insight provides enables you to identify and solve problems quickly and to harden and tune the application by using readily available performance observations. Spring Insight Developer gives you the following capabilities: View the throughput, error rate, and response time for each application endpoint over time. View trace information for any recent request, revealing how much time the application spends in the following activities: Dispatching requests Executing JDBC queries Executing custom methods Mapping objects to database tables Rendering views Identify where and why exceptions occur. Identify which application components are busiest at any given time. Application Cluster Monitoring with Spring Insight Operations Spring Insight Operations enables administrators to monitor the real-time behavior and health of Web applications and the servers on which they are deployed. It gives the same deep visibility into applications as Spring Insight Developer, as well as the capability to view the information across a cluster or to drill down to any single server. 6 Overview of tc Server

11 Overview of tc Server 7 Whereas Spring Insight Developer runs within a single tc Server instance alongside the Web applications it analyzes, Spring Insight Operations has a distributed architecture. A single, dedicated tc Server instance runs the Spring Insight Dashboard. Each tc Server instance hosting applications in your cluster runs the Spring Insight Agent application. The Agents collect trace data and submit it to the Dashboard, where the information is compiled and rendered. This design minimizes the overhead Spring Insight adds to your production servers and makes it easier to secure the Dashboard. In addition to everything you can do with Spring Insight Developer, here are some things you can do with Spring Insight Operations: View graphs of the health, throughput, error rate, and response time for each application endpoint across the cluster, or drill down to individual servers. Visually identify failed or under-performing servers. See which servers are handling too much or too little of the load. Enhanced Diagnostics The following diagnostic features make it easy for you to troubleshoot problems with a tc Runtime instance and the applications that you deploy to tc Server: Thread diagnostics. When clients connect to a deployed Web application on a tc Runtime instance, they might occasionally encounter slow or failed requests. By default, tc Runtime logs errors in the log files; however, it is often difficult to pinpoint the exact source of the error and how to fix it. With thread diagnostics enabled, tc Runtime provides additional troubleshooting information. Deadlock detection. The tc Server Hyperic plug-in automatically detects whether a thread deadlock occurs in a tc Runtime instance or an application deployed to the instance. Time-in garbage collection.the tc Server Hyperic plug-in has a new metric that represents the percentage of process up time (0-100) that a tc Runtime instance spends in garbage collection. Tomcat JDBC datasource monitoring. A new tc Server Hyperic plug-in service represents the high-concurrency Tomcat JDBC datasources that you have configured for your tc Runtime instance. This service monitors the health of the datasource, such as whether its connection to the database has failed or was abandoned, and whether the JDBC queries that clients execute are taking too long. For some diagnostics features, the tc Server Hyperic plug-in includes one or more preconfigured alerts that make it easy for you to monitor the tc Runtime instance, as well as manage the various thresholds at which an alert is triggered. For additional information about these diagnostic features, and information about managing the associated Hyperic alerts, see "Managing tc Runtime-Related Hyperic Alerts" in vfabric tc Server Administration. tc Server Command-Line Interface and Scripts Use the command-line interface (CLI) tcsadmin to perform the following tasks: List servers, groups, and deployed applications. Deploy applications. Configure tc Runtime instances and groups. Control tc Runtime instances and groups. tc Server Editions tc Server is available in three different editions. tc Server Developer is geared towards the enterprise application developer. tc Server Standard is designed for operators and administrators. tc Server Spring Edition, a part of vfabric Cloud Application VMware vfabric tc Server 2.6 7

12 8 Getting Started with tc Server Platform 5.0, is for operators and administrators deploying tc Server enterprise applications on VMware vsphere and VMware ESXi hosts. Table 3.1. vfabric tc Server Editions Feature Developer Edition Standard Edition Spring Edition tc Runtime # # # Spring Insight Developer # # # vfabric Hyperic with tc Server Plug-In Spring Insight Operations # Elastic Memory for Java (EM4J) # Commercial Spring Support # The following sections describe the tc Server editions: Developer Edition Standard Edition Spring Edition Developer Edition The Developer Edition of tc Server is geared towards the application developer. It contains the tc Runtime; utilities to create and start tc Runtime instances; and a set of templates for creating specific preconfigured tc Runtime instances, such as cluster-node ready and SSL-enabled. This edition also includes Spring Insight Developer, an application that provides real-time visibility into the behavior and performance of user applications. The tc Server Developer Edition contains a template called insight that includes the Spring Insight application. You use this template to create new tc Runtime instances enabled with Spring Insight. See Spring Insight Developer for help setting up and using Spring Insight. tc Server Developer Edition includes Tomcat Web Application Manager, a web application you can use to deploy and manage tc Runtime applications. This edition does not include access to Hyperic Server and Agent. The Developer Edition is distributed as either a ZIP or compressed TAR file with the following names: vfabric-tc-server-developer-2.6.x.release.zip vfabric-tc-server-developer-2.6.x.release.tar.gz Standard Edition The Standard Edition of tc Server is for administrators and operators. Similar to the Developer Edition, the Standard Edition contains the tc Runtime, scripts to easily create and start tc Runtime instances, and templates to quickly create specific types of tc Runtime instances (such as cluster-node ready or SSL-enabled). This edition does not include Spring Insight Developer. With the Standard Edition, you have access to the vfabric Hyperic management system, which (as of version 4.6) includes the tc Server Hyperic plug-in in the general distribution. Install vfabric Hyperic if you want to use Hyperic to configure and manage the tc Runtime. If you do not want to use Hyperic to manage tc Runtime instances and want to use the tc Runtime on its own, install only the tc Runtime. The Standard Edition is distributed as either a ZIP or compressed TAR file with the following names: vfabric-tc-server-standard-2.6.x.release.zip 8 Overview of tc Server

13 Overview of tc Server 9 vfabric-tc-server-standard-2.6.x.release.tar.gz To download an evaluation of Hyperic, go to the VMware Downloads Center. Spring Edition The tc Server Spring Edition is part of vfabric Cloud Application Platform 5.0. It includes all of the components and features of tc Standard Edition, plus Spring Insight Operations, Elastic Memory for Java (EM4J) and Spring commercial support. Spring Insight Operations differs from Spring Insight Developer, which is included in the tc Server Developer Edition, in that it is designed to be used with an in-production system. It allows you to view real-time behavior and health of your production applications. You can see application behavior across all servers and drill down to see specific servers. With Spring Insight Operations, you create one tc Runtime Instance using the Insight Dashboard template. This instance contains the Spring Insight user interface. You create production tc Runtime instances with the Insight Agent template. The Agent template adds the ability to collect traces from your web applications and forward them to the Dashboard instance. EM4J improves memory management for Java applications running in VMs on an ESXi host. It works with a new ESXi 5.0 memory management interface to implement ballooning technology in the JVM. Because of the way Java manages its memory, it has been in the past best practice to give the JVM 100% of the memory it needs, while sizing the heap as small as possible to avoid wasting memory. This prevented VMs running Java applications from participating in all of the ESXi advanced memory sharing capabilities. EM4J establishes a balloon directory in the Java heap, freeing the memory for ESXi to share with other VMs that need it. EM4J encourages the JVM to use memory conservatively and helps applications behave predictably and gracefully as memory becomes scarce. It also makes it possible to over-commit memory, improving consolidation ratios for Java applications running on ESXi hosts. The tc Server Spring Edition is the same binary distribution as the Standard Edition, with licensing differences. The Spring Insight Operations Dashboard and Agent templates are separate downloads at the VMware Downloads Center. How tc Server and Hyperic Work Together tc Server standard edition, targeted to administrators, includes access to the Hyperic management capabilities. This section shows how the runtime component of tc Server (called the tc Runtime) and the Hyperic components (Hyperic Server and Hyperic Agents) work together, and possible configurations that you can install on one or more computers. The simplest installation is one in which you install all components (tc Runtime, Hyperic Agent, and Hyperic Server) on the same computer. The computer acts as a host for the tc Runtime instances and their deployed applications as well as a host to the Hyperic Server and Hyperic Agent, which are used to manage the tc Runtime instances. In the following figure, the Hyperic Server is managing one tc Runtime instance. Figure 3.1. Installing on One Computer Hyperic Server can, of course, manage multiple instances, and manage other kinds of servers. Because the tc Runtime instances are all on one computer, you only need to install one Hyperic Agent. This is illustrated in the following figure. VMware vfabric tc Server 2.6 9

14 10 Getting Started with tc Server Figure 3.2. Multiple tc Runtime Instances on One Computer You can create multiple tc Runtime instances on one computer and install Hyperic Server on another computer. One Hyperic Agent must be installed on any computer running one or more tc Server instances. You can create multiple tc Runtime instances on ComputerA, and install the Hyperic Server on ComputerB, as shown in the next figure. ComputerA is known as a managed node. Figure 3.3. Installing on Two Computers In another scenario, you host the Hyperic Server on computerb, but want to install tc Runtime on many computers, possibly of different platforms such as Unix and Windows. In this case you must also install the Hyperic Agent on each computer (managed node) that hosts the tc Runtime instances. In the following figure, for example, computerc might be a Windows platform while all the rest of the computers are Unix. Also note that each computer has a different set of tc Runtimes installed, but only one Hyperic Agent. In the figure, all computers except computerb are managed nodes. 10 Overview of tc Server

15 Overview of tc Server 11 Figure 3.4. Installing on Multiple Computers Related Documentation Because tc Runtime is based on Apache Tomcat, much information about the tc Runtime itself is provided by Apache. See the following documentation: Apache Tomcat 6.0 Documentation Apache Tomcat 7.0 Documentation Apache Tomcat FAQ The Hyperic management component of tc Server provides monitoring and management for your Web infrastructure. You can use it to streamline operations, manage infrastructure complexity, and drive service-level improvements. The Hyperic user interface includes online-help for generic Hyperic functionality and related tc Server functionality. The following links provide additional documentation for programmers who develop Web applications using the Spring Framework and standard Java EE technologies such as servlets and JSPs: Spring Framework Reference Manuals and Javadoc Java Servlet Technology VMware vfabric tc Server

16 12 Getting Started with tc Server JavaServer Pages (JSP) Technology 12 Overview of tc Server

17 Comparing tc Runtime and Apache Tomcat Comparing tc Runtime and Apache Tomcat The 100-percent compatibility between vfabric tc Server and Apache Tomcat 6 ensures a seamless upgrade path for existing custom-built and commercial software applications already certified for Tomcat. Maintaining this level of compatibility enables customers to add the functionality they need to run and manage their applications more effectively with the least amount of effort. The tc Server runtime component, tc Runtime, also adds many business-critical features to standard Apache Tomcat functionality in the areas of enterprise server configuration, operations and management, diagnostics, and scripting. Subtopics Standard Application Server Features Enterprise Application Server Features Advanced Configuration Features Operations Features Standard Application Server Features tc Runtime and Apache Tomcat share key standard features of application servers. Table 4.1. Standard Application Server Feature Comparison Application Server Features tc Runtime Apache Tomcat Servlet 2.5 support Java Server Pages (JSP) 2.1 support HTTP session clustering Advanced I/O features Pre-built advanced non-blocking I/O components Basic Windows service wrapper Enterprise Application Server Features Because tc Runtime is based on Apache Tomcat 6, it provides a powerful yet lightweight platform that is compatible with existing Tomcat-based applications and with Web applications that run on other Java EE application servers such as IBM WebSphere or Oracle WebLogic. Applications can be seamlessly moved from Apache Tomcat to tc Runtime to gain the benefits that tc Runtime provides beyond the base Apache Tomcat. Table 4.2. Enterprise Application Server Feature Comparison Enterprise Application Server Features tc Runtime Apache Tomcat Multiple runtime instances from a single binary installation No New high-concurrency JDBC connection pool` No Preconfigured for JMX management No Includes latest security vulnerability and bug fixes Rebuild Tomcat yourself to apply incremental fixes. Binary patch updates Binary patches are not provided by Tomcat community. Unix boot scripts No Enhanced Windows service wrapper No VMware vfabric tc Server

18 14 Getting Started with tc Server Advanced Configuration Features tc Runtime has a number of advanced configuration features that Apache Tomcat does not. Table Advanced Configuration Feature Comparison Advanced Configuration Features tc Runtime Apache Tomcat Templated production-ready configuration out-of-the-box. No Create Tomcat single server configuration. No Modify general server configuration including JVM startup parameters. No Modify context container configuration. No Modify server defaults for JSPs and static content. No Add, modify, and delete JDBC datasources. No Modify HTTP and AJP connector settings. No Create and view general services. No Modify general engine configuration. No Pre-tuned JVM options. No Operations Features tc Runtime includes advanced, distributed management and monitoring capabilities through a centralized management console called Hyperic user interface. The tables in this section list the capabilities that tc Runtime provides over and above the base Apache Tomcat and also notes the features that Hyperic provides for existing Apache Tomcat environments. tc Runtime provides a wide range of capabilities that enable developers, administrators, and operators to centrally diagnose, measure, and monitor the distributed application infrastructure. Table 4.4. Diagnostics, Metrics, and Monitoring Feature Comparison Diagnostics, Metrics, and Monitoring Features tc Runtime Apache Tomcat Application deadlock detection No Uncaught exception detection No Garbage collection metrics, including throughput and count No SQL query time monitoring metrics. No Enhance response time monitoring metrics No Enhanced connection pool health metrics No Enhanced thread pool health metrics No Role-based customizable dashboard (via Hyperic) Automated inventory of application servers and software resources (via Hyperic) Real-time metric collection and monitoring of tc Runtime, Tomcat, Apache Web server, Apache ActiveMQ, underlying JVM, operating system, and other resources (via Hyperic) 14 Comparing tc Runtime and Apache Tomcat

19 Comparing tc Runtime and Apache Tomcat 15 Diagnostics, Metrics, and Monitoring Features tc Runtime Apache Tomcat Charting and graphing performance (via Hyperic) Advanced alerting: multi-conditional, availability, event, and recovery alerts, groupbased alerting, and escalation schemes. (via Hyperic) Log file tracing, alerts on event levels (via Hyperic) Alerts based on configuration file updates (via Hyperic) Performance baselining for alert thresholds (via Hyperic) tc Runtime provides a centralized, secure dashboard that enables administrators and operators to organize, operate, and control their distributed applications and infrastructure. Table 4.5. Centralized Operations and Management Feature Comparison Centralized Operations and Management Features tc Runtime Apache Tomcat Secure, distributed, JMX-based server management No Create application server groups (via Hyperic) Application server start/stop/restart from central console (via Hyperic) List deployed applications and current status No Application deploy/undeploy/reload/start/stop No Security and access/authorization control (via Hyperic) Scheduled control: maintenance activities, on-demand actions, scheduled remediation actions, or scheduled responses to alert conditions (via Hyperic) tc Runtime provides scripting support for administrators and operators who prefer to create and run scripts to handle distributed configuration and deployment steps. Table 4.6. Scripting Feature Comparison Scripting Features tc Runtime Apache Tomcat List deployed servers. No Create server groups. No Add and delete servers to and from groups. No List deployed applications, including current status. No Deploy application WAR file. No Undeploy application. No Start, stop, and reload deployed applications. No Get (download) configuration files and JVM parameters from a server. No Modify configuration files on an individual server. No VMware vfabric tc Server

20 16 Getting Started with tc Server Scripting Features tc Runtime Apache Tomcat Set (push) configuration files and JVM parameters to a server group. No Start, stop, and restart a server or group of servers No 16 Comparing tc Runtime and Apache Tomcat

21 Installing vfabric tc Server Installing vfabric tc Server vfabric tc Server has several options for installation and setup. Installation options vary according to the tc Server edition you choose; whether you install tc Server standalone or as part of vfabric Platform installation; and whether your operating system is Linux or another supported platform. Installation also varies according to whether you are installing tc Server for the first time or are upgrading from a previous version. If you have already installed a previous version of tc Server; have created one or more tc Runtime instances; and now want to upgrade all components to the latest version, see Upgrade and Migration Guide. The upgrade guide also describes how to upgrade an existing pre-4.5 Hyperic installation so that it can manage tc Runtime instances. Subtopics Meeting Software System Requirements for tc Server Installing tc Server as Part of vfabric Cloud Application Platform Install tc Server Developer Edition Install tc Server Standard Edition (tc Runtime Only) Install tc Server Standard Edition with Hyperic Management Components Activate a Local vfabric tc Server License Overview of tc Server Directories, Variables, and Configuration Enabling Bash Completion for tc Server Scripts Setting Up Unix Users for tc Server and Hyperic Meeting System Software Requirements for tc Server tc Server requires the Java Development Kit (JDK) or Java Runtime Environment (JRE). Depending on your installation, you might also need to install GNUtar and a database server. Determine whether you must install these components: GNUtar. If you install the compressed TAR file of tc Server in a Unix environment and your tar command does not support the -z option, you must install GNUtar. Database server. If you install tc Server Standard Edition and the platform-neutral version of Hyperic Server and Agent, you must install a database server. It is also recommended that you install a database server for production purposes, if you install the platformneutral or platform-specific version of the Hyperic distribution. The platform-specific versions of the Hyperic distribution bundle a database to get you started, but this database is not recommended for production. For Hyperic Server and Agent requirements, see "Installation Requirements" in vfabric Hyperic Installation Guide. Subtopics Required: Install JDK or JRE Possibly Required: Install a Database Server Possibly Required: Install GNUtar VMware vfabric tc Server

22 18 Getting Started with tc Server Required: Install JDK or JRE All tc Server editions require you to download a JDK or JRE. If you are installing the Hyperic components, the JDK or JRE requirement depends on whether you install a platform-specific version or the platform-neutral version. The platform-neutral version requires a JDK or JRE, and the platform-specific versions bundle one. Prerequisites For platform-specific details of supported and tested JDK or JRE versions, see the tc Server Release Notes on the tc Server Documentation Web site. Go to the appropriate download site for your platform: Java SE Downloads or IBM JDK and JRE Downloads. Procedure 1. On each computer where you plan to install the tc Runtime component of tc Server, download and install a JDK or JRE. 2. If you plan to install the platform-neutral version of the Hyperic components, install a JDK or JRE on each computer on which you will install Hyperic Server or a Hyperic Agent. Each computer requires one JDK or JRE. If you already installed a JDK or JRE on the computer in step 1, you do not need to install another one. 3. Set your JAVA_HOME environment variable to point to your installation and update your PATH environment variable to point to the JAVA_HOME/bin directory. 4. If you are installing the management components of tc Server (Hyperic Server and Hyperic Agent) on a Windows platform, set HQ_JAVA_HOME as a system environment variable that points to the location of your JDK or JRE. Make sure you set HQ_JAVA_HOME as a system environment variable. If you set it as a user environment variable, the Hyperic Agent aborts on startup. Possibly Required: Install a Database Server The Hyperic Server uses a database to store its metadata. The platform-neutral version of Hyperic Server does not, however, bundle a database. If you install tc Server Standard edition and you want to install the platform-neutral version of the Hyperic Server and Agent components, you need to install a database server. It is also recommended that you install a database server for production purposes, if you install the platformneutral or platform-specific version of the Hyperic distribution. The platform-specific versions of the Hyperic distribution bundle a database for you to get started, but this database is not recommended for production. Procedure Follow the procedure in "Set Up Hyperic Database" in vfabric Hyperic Installation Guide. Hyperic Server supports Oracle 10g/11g, PostgreSQL, and MySQL 5.x. Possibly Required: Install GNUtar If you are installing tc Server on Unix and have downloaded the compressed TAR file format (*.tar.gz), the tar command on your computer must be compatible with the tar command required by the tc Server. If the commands are not, compatible, you must install GNUtar. Procedure 1. Open a terminal window and enter: prompt$ tar --help 18 Installing vfabric tc Server

23 Installing vfabric tc Server Search the help output for a -z option, which filters the output through gzip. If the tar command on your computer supports the -z option, then it is compatible with the one required by tc Server and you can begin installing tc Server. If your tar command does not support this option, then you must install GNUtar (gtar) from an external source. Proceed to step Download GNUtar for free from Sunfreeware.com. 4. Update the PATH environment variable (either of the user installing tc Server or the system-wide environment variable) to include the location of the gtar command. The location depends on the directory in which you installed GNUtar. 5. For any references to tar in the tc Server installation procedures, substitute the command gtar. Installing tc Server as Part of vfabric Cloud Application Platform As with previous versions of the product, this version of vfabric tc Server is available as a standalone product installation. Beginning with version 2.6, tc Server is also available as part of vfabric Cloud Application Platform, a set of runtime components that let you build, scale, and run modern, agile applications in virtual environments. If you obtain tc Server standalone, you can install it on both physical and virtual machines according to the procedures in this document. If you obtain tc Server as part of a Standard or Advanced vfabric Platform package, you install it exclusively on VMware virtual machines that run on vsphere. The platform install process adds the vfabric License Server to an existing vcenter server. The vfabric License Server accepts a network license, actually a pool of licenses for vfabric components, which makes it easy to manage the licensing of all components installed on the VMs. If you obtain tc Server as part of vfabric Platform, first complete the license activation and installation procedures in Getting Started with vfabric Cloud Application Platform. Then follow procedures in this document to install tc Server and complete any remaining tc Server-specific installation and configuration tasks. Install tc Server Developer Edition When you install the Developer Edition of tc Server, you create a tc Runtime instance that contains Spring Insight Developer. The procedure covers Unix and Windows installation, although most instructions are specific to Unix. If you install on Windows, change the forward slashes (/) to back slashes (\); other differences in the installation are called out. Prerequisites Verify that your system meets the installation requirements. See Meeting System Software Requirements for tc Server. Review information about tc Server Developer edition and its *.zip or *.tar.gz distribution files. See tc Server Editions. Determine the user that is going to create and run the tc Runtime instances, and create it if necessary. Consider creating a user dedicated to tc Server tasks, putting the user in a separate group from regular users, and disabling its interactive login for security purposes. See Setting Up Unix Users for tc Server and Hyperic. On Unix, never run tc Runtime instances as the root user. For clarity, it is assumed in this topic that you will install and run tc Server as the tcserver user. VMware vfabric tc Server

24 20 Getting Started with tc Server Procedure 1. On the VMware Download page, navigate to the tc Server download page and download the Developer Edition distribution in ZIP or compressed TAR file format. vfabric-tc-server-developer-2.6.x.release.zip vfabric-tc-server-developer-2.6.x.release.tar.gz 2. Login to the computer on which you are installing tc Server as the appropriate user, such as tcserver. On Unix, if you have disabled interactive login, login as the root user and use su - tcserver to become the user. 3. Open a terminal (Unix) or command window (Windows) and create the main tc Server installation directory, such as /opt/ vmware. For example, on Unix: prompt$ mkdir /opt/vmware 4. Extract the tc Server distribution file into the new directory. This action creates a directory called vfabric-tc-server-developer in the main tc Server installation directory that contains the tc Runtime utility scripts, the templates directory, the tomcat-version directory, and so on. The templates directory contains a template called insight that contains the Spring Insight application. 5. Create a tc Runtime instance that contains Spring Insight by specifying the insight template. Unix: Change to the /opt/vmware/vfabric-tc-server-developer directory and execute the tcruntimeinstance.sh script to create an instance. VMware recommends that you use the -i option to specify the full pathname of a directory in which the new instance will be created, and that this directory be different from the installation directory. Be sure the tcserver user can write to this directory and that the directory already exists. For example: prompt$ cd /opt/vmware/vfabric-tc-server-developer prompt$./tcruntime-instance.sh create -t insight \ -i /var/opt/vmware/vfabric-tc-server-developer insight-instance Windows: Change to the \opt\vmware\vfabric-tc-server-developer directory and execute the tcruntime-instance.bat script to create an instance: prompt> cd \opt\vmware\vfabric-tc-server-developer prompt> tcruntime-instance.bat create insight-instance -t insight \ -i \var\opt\vmware\vfabric-tc-server-developer 6. Start the new tc Runtime instance. Unix: Execute the tcruntime-ctl.sh script to start the instance; use the -n option to specify the directory in which the instance is located. For example: prompt$./tcruntime-ctl.sh insight-instance start -n /var/opt/vmware/vfabric-tc-server-developer Windows: Execute the tcruntime-ctl.bat script to first install the tc Runtime instance as a Windows service and then start it; for both commands, use the -n option to specify the directory in which the instance is located: prompt> tcruntime-ctl.bat insight-instance install -n \var\opt\vmware\vfabric-tc-server-developer prompt> tcruntime-ctl.bat insight-instance start -n \var\opt\vmware\vfabric-tc-server-developer 20 Installing vfabric tc Server

25 Installing vfabric tc Server 21 On Windows, VMware recommends that you subsequently start and stop the tc Runtime instance through the Windows Services console. The tc Runtime instance is displayed in the console with the name SpringSource tc Runtime - unique-name, where unique-name is a unique combination of server name and servger directory. 7. After the tc Runtime instance starts, invoke Spring Insight in your browser: where host refers to the computer on which Spring Insight is running. If you are on the same computer, you can use localhost: What to do next For details about the directories you installed, see Overview of tc Server Directories, Variables, and Configuration Files. For Spring Insight overview information and to create plug-ins that extend Spring Insight, see Spring Insight Developer. Try out the tutorials. See Tutorial: Using Hyperic to Configure and Manage tc Runtime Instances and Tutorial: Very Simple Web Application Development. Install tc Server Standard Edition (tc Runtime Only) When you install tc Server Standard Edition, you can choose to install the tc Runtime component only, without installing any Hyperic components. Prerequisites Verify that your system meets the installation requirements. See Meeting System Software Requirements for tc Server. Review information about tc Server Standard edition and its *.zip or *.tar.gz distribution files. See tc Server Editions. Determine the user that is going to create and run the tc Runtime instances, and create it if necessary. Consider creating a user dedicated to tc Server tasks, putting the user in a separate group from regular users, and disabling its interactive login for security purposes. See Setting Up Unix Users for tc Server and Hyperic. On Unix, never run tc Runtime instances as the root user. For clarity, it is assumed in this topic that you will install and run tc Server as the tcserver user. Procedure 1. From the VMware Download page, navigate to the VMware vfabric tc Server download page. 2. Download the Standard Edition Runtime package distribution in ZIP or compressed TAR format to a directory on your computer, for example /home/downloads. vfabric-tc-server-standard-2.6.x.release.zip vfabric-tc-server-standard-2.6.x.release.tar.gz 3. Login to the computer on which you are installing tc Server as the appropriate user, such as tcserver. On Unix, if you have disabled interactive login, login as the root user and use su - tcserver to become the user. VMware vfabric tc Server

26 22 4. Getting Started with tc Server Open a terminal (Unix) or command window (Windows) and create the main tc Server installation directory, such as /opt/ vmware. For example, on Unix: prompt$ mkdir /opt/vmware 5. Extract the tc Server distribution file into the new directory. This action installs tc Runtime; there is no installer program. For example, if you created a directory called /opt/vmware in the preceding step, and downloaded the Standard Edition ZIP file in the /home/downloads directory: prompt$ cd /opt/vmware prompt$ unzip /home/downloads/vfabric-tc-server-standard release.zip This action creates a directory called vfabric-tc-server-standard in the main tc Server installation directory that contains the tc Runtime utility scripts, the templates directory, the tomcat-version directory, and so on. What to do next If you installed tc Server standalone, activate a local tc Server license as described in Activate a Local vfabric tc Server License. If you installed tc Server as part of vfabric Cloud Application Platform, then you should have already activated a network license using the vsphere client, as described in Installing tc Server as Part of vfabric Cloud Application Platform. For details about the directories you installed, see Overview of tc Server Directories, Variables, and Configuration Files For typical post-installation procedures such as creating tc Runtime instances, starting tc Server components, and getting started with the Hyperic user interface, see Post-Installation Tasks. Try out the tutorials. See Tutorial: Using Hyperic to Configure and Manage tc Runtime Instances and Tutorial: Very Simple Web Application Development. Install tc Server Standard Edition and Hyperic Management Components When you install tc Server Standard Edition, you have the option of also installing VMware vfabric Hyperic to monitor and manage tc Server. Hyperic 4.5 and later includes the tc Server Hyperic plug-in, which allows you to use the Hyperic interface to monitor and manage tc Runtime instances. There are two Hyperic components to install. Hyperic Agent is installed on every computer running a tc Runtime instance. Hyperic Agent discovers tc Runtime processes, adds them to the inventory and manages them, through the tc Server plug-in. A computer with tc Server runtime instances and Hyperic Agent is called a "managed node." The other component, Hyperic Server, can be installed on any computer in the network and provides the central control point and user interface to use Hyperic to manage multiple deployments. The procedure breaks the installation steps into those you do on managed node computer(s) and those you do on the Hyperic Server computer. If you are installing everything on the same computer, then simply execute all steps on the same computer. If you are installing tc Runtime instances on multiple computers you must install Hyperic Agent on each computer. Prerequisites Verify that your system meets the installation requirements for installing tc Server with Hyperic management components. See Meeting System Software Requirements for tc Server. 22 Installing vfabric tc Server