-
Cisco Application Velocity System User Guide (Software Version 5.0)
-
Preface
-
Product Overview
-
AVS Description
-
Appliance Administration
-
Command Line Interface
-
Configuration Reference
-
AppScreen Configuration
-
Management Console
-
Reporting
-
NMS Integration
-
Availability Manager Clustering
-
Database Maintenance
-
Logs
-
SNMP MIB
-
Deployment Options
-
Frequently Asked Questions and Troubleshooting
-
Anonymous Base File Statistical Model
-
Regular Expressions
-
AppScreen Rules DTD
-
Glossary
-
Index
-
Table Of Contents
Accessing the Management Console
Changing the User Name or Password
Node-Level Global Configuration
Node-Level Destination Mapping Configuration
Node-Level Application Class Configuration
Node-Level AppScreen Class Configuration
Database User Name and Password
Securing the Management Console
Management Console
You can use the web browser-based Management Console to manage all Performance Nodes (each node represents an application appliance server). The Management Console allows you to:
•
group nodes into logical administrative groups, called clusters
•
•
Note
This chapter includes these sections:
•
•
Accessing the Management Console
Note
To view the Management Console, you'll need to know its IP address and port number. Start your web browser and enter a URL in the following format:
http://consoleIPAddress:consolePort/fgconsole/
For example:
http://10.0.0.2:9000/fgconsole/
A dialog will request your user name and password. The default values are:
user name: admin
password: adminIf you want to change the user name and/or password, see "Changing the User Name or Password" below.
After entering the correct user name and password, the web browser displays the Management Console shown in Figure 7-1.
Figure 7-1 Management Console Main Page
Changing the User Name or Password
To change the Management Console user name or password, open the following file in a text editor:
$AVS_HOME/console/jboss-3.0.1_tomcat-4.0.4/server/default/deploy/fgconsole.war/users.properties
The user name and password are set by this line:
admin=adminThe user name appears before the = sign and the password appears after the = sign. For example, to change the user name to "Cisco" and the password to "accelerate", this line should read:
Cisco=accelerateIf you are changing the user name, you also must change this file:
$AVS_HOME/console/jboss-3.0.1_tomcat-4.0.4/server/default/deploy/fgconsole.war/roles.properties
The user name is set by the line that contains:
admin=The user name appears before the = sign. For example, to change the user name to "Cisco", change it to:
Cisco=Do not change the text after the = sign in this file.
The user name entered here must match the one in the users.properties file, above.
Clusters
Before you can do anything, you must register a cluster and register one or more nodes in it. A cluster is simply a named group of one or more nodes.
If you have deployed multiple Performance Nodes, you can group them into clusters to logically divide administration. Of course, this isn't required; you can have a single cluster containing all nodes, or just one node, if that is all you are using. But you must have at least one cluster in order to manage a node and generate reports.
To create a cluster, use the Register Cluster command, as described in the following section.
Register Cluster
Before you can manage an individual node, you must create at least one cluster and add the node to it.
To create a cluster, click Register Cluster in the left pane of the console. The resulting page prompts you for a cluster name, as shown in Figure 7-2. Enter the name and click the button Register Cluster.
Figure 7-2 Register Cluster Page
The cluster you just created now appears as a folder in the left pane of the console. Click it to expand it and see the following menu items:
These menu items are described in the following subsections.
Additionally, the menu includes a Cluster Configuration folder that contains more menu items that relate to cluster configuration and control and comprise the Web Configurator:
These items are described in the "Cluster Configuration" section.
Register Node
Use the Register Node command to add an application appliance server node to a cluster. Click this command to display a form where you identify the node you want to add to the cluster, as shown in Figure 7-3. Fill in the fields on the form and click Register to add the node to the cluster.
Note
Figure 7-3 Register Node Page
Here's a description of the form fields:
•
•
•
•
•
•
•
•
•
•
•
After you have added one or more nodes to the cluster, their names will appear under the cluster folder, and you can click a node name to manage the individual node. For details on managing an individual node, see the "Managing Individual Nodes" section.
If an error occurs while performing the operation, an error like that in Figure 7-4 is shown.
Figure 7-4 Error Message
Edit Cluster Name
Use the Edit Cluster Name command to change the name of a cluster. Click this command to display a page where you can rename the cluster, as shown in Figure 7-5. Enter the new cluster name and click Apply to change the name, or Cancel to leave the name unchanged.
Figure 7-5 Edit Cluster Name Page
Unregister Cluster
Use the Unregister Cluster command to delete a cluster. Click this command to display a page where you can confirm that you want to delete the cluster, as shown in Figure 7-6. Click Yes to delete the cluster, or No to leave the cluster unchanged.
Caution
Figure 7-6 Unregister Cluster Page
Cluster Status
Use the Cluster Status command to view the status of all nodes in the cluster. Click this command to display a page that shows a status line for each node in the cluster, as shown in Figure 7-7.
The status line shows the node name and IP address, type, status (running or stopped), and the machine load. The status page is refreshed every 15 seconds.
Figure 7-7 Cluster Status Page
Cluster Control
Use the Cluster Control command to control the status of all nodes in the cluster. Click this command to display a page that shows a status line for each node in the cluster, as shown in Figure 7-8.
The status line shows the operational state of the node (Running or Stopped), and the node name, IP address, and type.
Figure 7-8 Cluster Control Page
From this page you can run, stop, or restart the nodes in the cluster. Check the check boxes next to the nodes that you want to control, and then click Run, Stop, or Restart to perform that operation on the checked nodes. You can use the Include All Nodes and Exclude All Nodes buttons at the top to check or clear all check boxes.
The check boxes in the lower part of the page control other aspects of the operation:
•
•
Cluster Information
Use the Cluster Information command to view information about the nodes in the cluster. Click this command to display a page that shows an information block for each node in the cluster, as shown in Figure 7-9.
The information block shows the node version, home directory, listening port, and disk utilization.
Figure 7-9 Cluster Information Page
Cluster Configuration
The Management Console allows you to edit the configuration of all nodes in a cluster. This capability allows you to quickly set up all nodes in a cluster with the same configuration (stored in the fgn.conf file) and to easily change the configuration using the Web Configurator feature of the Management Console, rather than editing the configuration text files manually.
The Web Configurator commands are available under the Cluster Configuration menu folder:
After you add one or more nodes to a cluster, you can also edit the configuration of those individual nodes by using the menu items under the Configuration folder inside the node folder. These menu items include the Global, Destination Mapping, Application Class, AppScreen Class, and View Configuration commands. These commands work the same as at the cluster level, but apply only to the fgn.conf file of a single node. They are described in the "Configuring Individual Nodes" section.
Here are the steps to edit the configuration of nodes at the cluster level:
1.
2.
3.
4.
5.
6.
See the following subsections for details on using each of the commands related to cluster configuration.
Global
Use the Global command to edit the global configuration parameters in the template that applies to all nodes in the cluster. Click this command to display a form where you can edit the existing parameters and add a new parameter, as shown in Figure 7-10. Edit the fields on the form and click Apply Changes to apply the changes to the template. (Note that the changes are not copied to the individual nodes until you use the Publish command.)
Figure 7-10 Global Page
You can add one parameter at a time to the form by choosing a parameter to add from the Add New Parameter list at the bottom of the form. When you choose the parameter, the appropriate field to enter its value appears below its name. Enter its value (or choose it from a list, if applicable) and click Apply Changes to add the parameter.
You can add a new parameter that is not listed in the Add New Parameter list by choosing the "-unlisted-" item. Then in the Value field that appears, enter the name of the parameter, a space, and then its value, like this:
NewParameter theValueSuch an unlisted parameter is not validated, unless you enter the name of a known parameter, which is validated when you click Apply Changes.
To remove a parameter from the form, erase the value in an editable field or choose "-delete-" in a list. When you click Apply Changes, the parameter is removed.
For information on the global configuration keywords shown in the form, refer to the "fgn.conf" section on page 5-1.
Node-Level Global Configuration
The Global command also appears within the node folder. That command works the same as at the cluster level, but applies only to the fgn.conf file of a single node. For details see the "Global" section.
At the node level, the editing form shows only parameters that are set at the node level. Other parameters may be set at the cluster level. If the same parameter is set at both levels, the value set at the node level overrides the value set at the cluster level. The parameter name is shown in italics in the node-level editing form to indicate that it is overriding the cluster setting.
Destination Mapping
Use the Destination Mapping command to edit the global destination mapping keywords in the template that applies to all nodes in the cluster. Click this command to display a form where you can edit the existing destination mapping configurations and add new ones, as shown in Figure 7-11. (Note that any changes are not copied to the individual nodes until you use the Publish command.)
Figure 7-11 Destination Mapping Page
You can add one destination mapping configuration at a time to the form by choosing its type from the Add New Destination Mapping list at the bottom of the form. When you choose the type, the appropriate fields to configure it appear below its name. Enter the values (or choose from a list, if applicable) and click Apply Changes to add the destination mapping configuration. For information on the destination mapping configuration keywords, refer to the "Destination Mapping Configuration" section on page 5-30.
To change the order of destination mapping lines in the configuration file, enter a new order for one or more lines in the Ordinal column. Changing the order of a mapping to 0 moves it to the top of the list after you click Apply Changes. Changing the order of a mapping to a number greater than the last mapping moves it to the end of the list.
To delete one or more mappings, check the box in the Delete column for the mapping. Click Apply Changes to delete the checked mappings.
Node-Level Destination Mapping Configuration
The Destination Mapping command also appears within the node folder. That command works the same as at the cluster level, but applies only to the fgn.conf file of a single node. For details see the "Destination Mapping" section.
Application Class
Use the Application Class command to edit the global Application Classes in the template that applies to all nodes in the cluster. Click this command to display a form where you can edit the existing Application Classes and add new ones, as shown in Figure 7-12. (Note that any changes are not copied to the individual nodes until you use the Publish command.)
Figure 7-12 Application Class Page
The Application Class Summary section at the top allows you to change the order of classes, delete classes, clone classes, and add new classes. Below that, each class is listed with its parameters. These are read-only listings.
To edit a class, click the Edit button in the summary, or click the class name link that is at the top of a class listing. A form similar to that shown in Figure 7-13 is displayed where you can edit, add, or delete parameters. For information on the Application Class configuration keywords, refer to the "Application Class Specification" section on page 5-7.
To change the order of Application Classes in the configuration file, enter a new order for one or more classes in the Order column. Changing the order of a class to 0 moves it to the top of the list after you click Apply Changes. Changing the order of a class to a number greater than the last class moves it to the end of the list.
To delete one or more classes, check the box in the Delete column for the class. Click Delete Checked Classes to delete the checked classes.
To copy a class to use as the basis of a new class, click the Clone button next to the class you want to clone. Cloned classes are put at the top of the list.
To add a new class, click Add New Application Class. This displays a new form where you can edit the class name and its parameters, as shown in Figure 7-13. To select multiple keywords in the OptimizationPolicy list, hold down the Ctrl key while clicking on keywords.
To add a new parameter to the class, select it from the New Parameter list at the bottom of the form and enter its value in the field that will appear under its name. Click Apply Changes when you are done editing or adding new parameters. To go back to the Application Class summary page, click the Application Class command again in the menu at the left side. New classes are put at the top of the list.
You can add a new parameter that is not listed in the New Parameter list by choosing the "-unlisted-" item. Then in the Value field that appears, enter the name of the parameter, a space, and then its value, like this:
NewParameter theValueSuch an unlisted parameter is not validated, unless you enter the name of a known parameter, which is validated when you click Apply Changes.
Figure 7-13 Add a New Application Class Page
Node-Level Application Class Configuration
The Application Class command also appears within the node folder. That command works the same as at the cluster level, but applies only to the fgn.conf file of a single node. For details see the "Application Class" section.
At the node level, the editing form shows only Application Classes that are set at the node level. Other Application Classes may be set at the cluster level. If an Application Class with the same name is set at both levels, the one set at the node level overrides the one set at the cluster level because it is placed first in the configuration file when it is published to the node.
If you add a new Application Class, it is prefixed with the node name to distinguish it from Application Classes defined at the cluster level.
AppScreen Class
Use the AppScreen Class command to edit the global AppScreen Classes in the template that applies to all nodes in the cluster. Click this command to display a form where you can edit the existing AppScreen Classes and add new ones, as shown in Figure 7-14. (Note that any changes are not copied to the individual nodes until you use the Publish command.)
Figure 7-14 AppScreen Class Page
The AppScreen Class Summary section at the top allows you to change the order of classes, delete classes, clone classes, and add new classes. Below that, each class is listed with its parameters. These are read-only listings.
To edit a class, click the Edit button in the summary, or click the class name link that is at the top of a class listing. A form similar to that shown in Figure 7-15 is displayed where you can edit, add, or delete parameters. For information on the AppScreen Class configuration keywords, refer to Chapter 6, "AppScreen Configuration."
To change the order of AppScreen Classes in the configuration file, enter a new order for one or more classes in the Order column. Changing the order of a class to 0 moves it to the top of the list after you click Apply Changes. Changing the order of a class to a number greater than the last class moves it to the end of the list.
To delete one or more classes, check the box in the Delete column for the class. Click Delete Checked Classes to delete the checked classes.
To copy a class to use as the basis of a new class, click the Clone button next to the class you want to clone. Cloned classes are put at the top of the list.
To add a new class, click Add New AppScreen Class. This displays a new form where you can edit the class name and its parameters, as shown in Figure 7-15.
Figure 7-15 Add a New AppScreen Class Page
To add a new parameter to the class, select it from the New Parameter list at the bottom of the form and enter its value in the field that will appear under its name. Click Apply Changes when you are done editing or adding new parameters. To go back to the AppScreen Class summary page, click the AppScreen Class command again in the menu at the left side. New classes are put at the top of the list.
When you add or edit the AppScreenPolicy parameter, you can edit this field manually, or use the AppScreen Policy Builder. To use the AppScreen Policy Builder, click the Edit button next to the field you want to edit. This pops up the AppScreen Policy Builder window, as shown in Figure 7-16. Here you can specify the Rule, Disposition, and Actions for this AppScreen Policy. When done, click Apply Changes to close the Policy Builder window, then click Apply Changes again in the AppScreen Class window.
Figure 7-16 AppScreen Policy Builder Window
Node-Level AppScreen Class Configuration
The AppScreen Class command also appears within the node folder. That command works the same as at the cluster level, but applies only to the fgn.conf file of a single node. For details see the "AppScreen Class" section.
At the node level, the editing form shows only AppScreen Classes that are set at the node level. Other AppScreen Classes may be set at the cluster level. If an AppScreen Class with the same name is set at both levels, the one set at the node level overrides the one set at the cluster level because it is placed first in the configuration file when it is published to the node.
If you add a new AppScreen Class, it is prefixed with the node name to distinguish it from AppScreen Classes defined at the cluster level.
Publish
Use the Publish command to write out actual fgn.conf files to each of the nodes in the cluster. This command displays a form where you can select which nodes to publish the current configuration to, as shown in Figure 7-17.
Figure 7-17 Publish Page
Check the Include check box next to each node that you want to publish the current configuration to. You can use the Clear All button to clear all check boxes, or the Check All button to check them all. When you have selected the appropriate nodes to publish to, click Publish. Note that the new configuration takes effect only after the affected nodes are restarted. You can use the Cluster Control command to restart nodes.
The Conf State column shows whether the configuration for a node is Consistent or Inconsistent. Consistent means that the configuration file for the node matches the database representation (as shown by the View Configuration command). Inconsistent means that the node configuration file does not match the database representation and may have been manually edited outside the Management Console interface.
Publishing to nodes overwrites the existing node configuration files. A backup copy of the previous configuration is saved and named fgn.conf.backup.date, where date is the date/time when the new configuration was published. In the event that a node fails to start with a newly published configuration, you can either edit the configuration and republish it by using the Management Console commands, or you can revert to the saved backup configuration.
To revert to a saved backup configuration, use the Import command and select a previously saved configuration to import. Then publish this configuration to the nodes you want to restore. Alternatively, you can manually run the rollback.sh script in the /conf directory, which restores the last saved configuration.
Import
Use the Import command to import a configuration file from one of the nodes in the cluster, or the factory default, to use as a template for all nodes in the cluster. This imports an fgn.conf file into the Management Console database, so that it can be viewed and edited via your web browser. Note that you must use the Publish command to publish the configuration to nodes to make it take effect.
Click the Import command to display a form where you select the node whose configuration file you want to import, as shown in Figure 7-18. Select the node and click Preview to preview the configuration before actually importing it.
Alternatively, you can reset the cluster configuration template to the factory default settings for Performance Suite nodes, or you can restore a previously saved configuration. Choose the appropriate configuration and click Preview to preview the configuration before actually importing it. If you choose Select From Previously Published Configurations, when you click Preview, an additional screen will allow you to choose which saved backup configuration you want to restore. Choose one and click Preview again.
Figure 7-18 Import Selection Page
The global configuration is shown for you to preview (Figure 7-19). Click the Import Configuration button to actually import the configuration.
Figure 7-19 Import Preview Page
Managing Individual Nodes
To manage an individual application appliance, you must first create a cluster and add the application appliance node to it.
Open a cluster by clicking on the cluster folder name in the left pane; then click on an application appliance name in that cluster. Several menu items are shown below the application appliance name, as illustrated in Figure 7-20.
Figure 7-20 Management Menu
The following sections describe the menu items that are available for managing a node:
There is also a Configuration folder under the node. This folder contains additional menu items for configuring the node and these are described in the "Configuring Individual Nodes" section.
Edit Properties
Use the Edit Properties command to edit some of the properties of an application appliance. Click this command to display a page where you can view and change various properties, as shown in Figure 7-21. Click Apply to save any changes you make, or click Cancel to cancel them.
These are the same properties set by the Register Node command; for details on the fields, see the "Register Node" section.
Figure 7-21 Edit Properties Page
Unregister Node
Use the Unregister Node command to remove a node from the cluster. Click this command to display a page where you can confirm that you want to remove the node, as shown in Figure 7-22. Click Yes to remove the node, or No to leave it unchanged.
Figure 7-22 Unregister Node Page
Cache Management
This Cache Management page lets you manage the application appliance cache, as shown in Figure 7-23.
Using the controls on this page you can:
•
•
•
Check the box next to each type of file you want to delete and select the target cache location from which to delete files: Disk, Memory, or both. The default location from which to delete files is both Disk and Memory (both are initially checked).
Click Submit to perform the operation, or click Clear to clear all check boxes.
Figure 7-23 Cache Management Page
Configuring Individual Nodes
The Management Console allows you to edit the configuration of all nodes in a cluster, or of individual nodes. This graphical configuration editing feature is known as the Web Configurator.
This section describes the commands that allow you to edit the configuration of an individual node. For information on using the Cluster Configuration commands to configure all nodes in a cluster, see the "Cluster Configuration" section.
The commands that allow you to edit the configuration of an individual node are available in the Configuration folder under the node. The following sections describe the configuration menu items:
Global
Use the Global command to edit the global configuration that applies to the node. Click this command to display a form where you can edit the existing parameters and add a new parameter, as shown in Figure 7-24. Edit the fields on the form and click Apply Changes to apply the changes to the node. (Note that the changes are not copied to the node's fgn.conf file until you use the Publish command at the cluster level.)
Figure 7-24 Global Configuration Page
This form shows only parameters that are set at the node level. Other parameters may be set at the cluster level (see the "Global" section). If the same parameter is set at both levels, the value set at the node level overrides the value set at the cluster level. A parameter name is shown in italics here to indicate that it is overriding the cluster setting.
You can add one parameter at a time to the form by choosing a parameter to add from the New Parameter list at the bottom of the form. When you choose the parameter, the appropriate field to enter its value appears below its name. Enter its value (or choose it from a list, if applicable) and click Apply Changes to add the parameter.
You can add a new parameter that is not listed in the Add New Parameter list by choosing the "-unlisted-" item. Then in the Value field that appears, enter the name of the parameter, a space, and then its value, like this:
NewParameter theValueSuch an unlisted parameter is not validated, unless you enter the name of a known parameter, which is validated when you click Apply Changes.
To remove a parameter from the form, erase the value in an editable field or choose "-delete-" in a list. When you click Apply Changes, the parameter is removed.
For information on the global configuration keywords shown in the form, refer to the "fgn.conf" section on page 5-1.
Destination Mapping
Use the Destination Mapping command to edit the destination mappings for the node. Click this command to display a form where you can edit the existing destination mapping configurations and add new ones, as shown in Figure 7-25. (Note that the changes are not copied to the node's fgn.conf file until you use the Publish command at the cluster level.)
Figure 7-25 Destination Mapping Page
You can add one destination mapping configuration at a time to the form by choosing its type from the Add New Destination Mapping list at the bottom of the form. When you choose the type, the appropriate fields to configure it appear below its name. Enter the values (or choose from a list, if applicable) and click Apply Changes to add the destination mapping configuration. For information on the destination mapping configuration keywords, refer to the "Destination Mapping Configuration" section on page 5-30.
To change the order of destination mapping lines in the configuration file, enter a new order for one or more lines in the Ordinal column. Changing the order of a mapping to 0 moves it to the top of the list after you click Apply Changes. Changing the order of a mapping to a number greater than the last mapping moves it to the end of the list.
To delete one or more mappings, check the box in the Delete column for the mapping. Click Apply Changes to delete the checked mappings.
This form shows only destination mappings that are set at the node level. Other destination mappings may be set at the cluster level (see the "Destination Mapping" section).
Application Class
Use the Application Class command to edit the Application Classes for the node. Click this command to display a form where you can edit the existing Application Classes and add new ones, as shown in Figure 7-26. (Note that any changes are not copied to the node's fgn.conf file until you use the Publish command at the cluster level.)
Figure 7-26 Application Class Configuration Page
This form shows only Application Classes that are set at the node level. Other Application Classes may be set at the cluster level (see the "Application Class" section). If an Application Class with the same name is set at both levels, the one set at the node level overrides the one set at the cluster level because it is placed first in the configuration file when it is published to the node.
The Application Class Summary section at the top allows you to change the order of classes, delete classes, clone classes, and add new classes. Below that, each class is listed with its parameters. These are read-only listings. To edit a class, click the Edit button in the summary, or click the class name link that is at the top of a class listing. A form similar to that shown in Figure 7-27 is displayed where you can edit, add, or delete parameters. For information on the Application Class configuration keywords, refer to the "Application Class Specification" section on page 5-7.
To change the order of Application Classes in the configuration file, enter a new order for one or more classes in the Order column. Changing the order of a class to 0 moves it to the top of the list after you click Apply Changes. Changing the order of a class to a number greater than the last class moves it to the end of the list.
To delete one or more classes, check the box in the Delete column for the class. Click Delete Checked Classes to delete the checked classes.
To copy a class to use as the basis of a new class, click the Clone button next to the class you want to clone. Cloned classes are put at the top of the list.
To add a new class, click Add New Application Class. This displays a new form where you can edit the class name and its parameters, as shown in Figure 7-27. To select multiple keywords in lists, hold down the Ctrl key while clicking on keywords.
To add a new parameter to the class, select it from the New Parameter list at the bottom of the form and enter its value in the field that will appear under its name. Click Apply Changes when you are done editing or adding new parameters. To go back to the Application Class summary page, click the Application Class command again in the menu at the left side. New classes are put at the top of the list.
You can add a new parameter that is not listed in the New Parameter list by choosing the "-unlisted-" item. Then in the Value field that appears, enter the name of the parameter, a space, and then its value, like this:
NewParameter theValueSuch an unlisted parameter is not validated, unless you enter the name of a known parameter, which is validated when you click Apply Changes.
Figure 7-27 Add a New Application Class Page
AppScreen Class
Use the AppScreen Class command to edit the AppScreen Classes for the node. Click this command to display a form where you can edit the existing AppScreen Classes and add new ones, as shown in Figure 7-28. (Note that any changes are not copied to the node's fgn.conf file until you use the Publish command at the cluster level.)
Figure 7-28 AppScreen Class Configuration Page
This form shows only AppScreen Classes that are set at the node level. Other AppScreen Classes may be set at the cluster level (see the "AppScreen Class" section). If an AppScreen Class with the same name is set at both levels, the one set at the node level overrides the one set at the cluster level because it is placed first in the configuration file when it is published to the node.
The AppScreen Class Summary section at the top allows you to change the order of classes, delete classes, clone classes, and add new classes. Below that, each class is listed with its parameters. These are read-only listings. To edit a class, click the Edit button in the summary, or click the class name link that is at the top of a class listing. A form similar to that shown in Figure 7-29 is displayed where you can edit, add, or delete parameters. For information on the AppScreen Class configuration keywords, refer to the "AppScreen Class" section on page 6-3.
To change the order of AppScreen Classes in the configuration file, enter a new order for one or more classes in the Order column. Changing the order of a class to 0 moves it to the top of the list after you click Apply Changes. Changing the order of a class to a number greater than the last class moves it to the end of the list.
To delete one or more classes, check the box in the Delete column for the class. Click Delete Checked Classes to delete the checked classes.
To copy a class to use as the basis of a new class, click the Clone button next to the class you want to clone. Cloned classes are put at the top of the list.
To add a new class, click Add New AppScreen Class. This displays a new form where you can edit the class name and its parameters, as shown in Figure 7-29.
Figure 7-29 Add a New AppScreen Class Page
To add a new parameter to the class, select it from the New Parameter list at the bottom of the form and enter its value in the field that will appear under its name. Click Apply Changes when you are done editing or adding new parameters. To go back to the AppScreen Class summary page, click the AppScreen Class command again in the menu at the left side. New classes are put at the top of the list.
When you add or edit the AppScreenPolicy parameter, you can edit this field manually, or use the AppScreen Policy Builder. To use the AppScreen Policy Builder, click the Edit button next to the field you want to edit. This pops up the AppScreen Policy Builder window, as shown in Figure 7-30. Here you can specify the Rule, Disposition, and Actions for this AppScreen Policy.
Figure 7-30 AppScreen Policy Builder Window
View Configuration
Use the View Configuration command to view the database representation of the node configuration. This command displays a page with the configuration, as shown in Figure 7-31. The configuration displayed is exactly what would be written to the fgn.conf file for the node if it is published.
The configuration is divided into four blocks:
•
•
•
•
Figure 7-31 View Configuration Page
Reports
After you have added one or more nodes to a cluster, reports that are available are listed under the Reports folder.
Note
The following AppScope-related report items are available:
•
•
•
•
•
•
•
And the following other reports and items are available:
•
•
•
•
•
For details on reporting items, see Chapter 8, "Reporting." For details on the Transaction Types and Transaction Groups items, see Chapter 9, "NMS Integration." For details on the Database Archiving item, see Chapter 11, "Database Maintenance."
Version
Use the Version command to display a page showing the version of the Management Console that is running.
Console Configuration
You can configure this item in the Management Console:
•
Database User Name and Password
The user name and password to access the Management Console database are set during the Management Console install process. If you later want to change these, you can modify an XML configuration file that the Management Console server reads on startup.
Look for the following file and open it in a text editor:
$AVS_HOME/console/jboss-3.0.1_tomcat-4.0.4/server/default/deploy/postgres-service.xml
In this file, look for the following section:
<!--set these only if you want only default logins, not through JAAS --><config-property name="UserName" type="java.lang.String">fineground</config-property><config-property name="Password" type="java.lang.String">condenser</config-property>To change the user name, change the value for the UserName configuration property (fineground in this example). To change the password, change the value for the Password configuration property (condenser in this example). Save and close the file. You will also need to stop and restart the Management Console for the new setting to take effect.
Securing the Management Console
By default, the Management Console communicates with the browser using standard HTTP on port 9000. It is possible to configure the Management Console to support secure HTTPS. To make the Management Console more secure, follow these steps:
Step 1
Step 2
velocity> set console stop
Note
# /etc/init.d/fgnmc_de1eb23f6ecf273bee6b4561cd29368e3e539712 stop
# /etc/init.d/fgndb_de1eb23f6ecf273bee6b4561cd29368e3e539712 stop
Step 3
# AVS_HOME=/usr/avs# export AVS_HOME# PATH=$PATH:$AVS_HOME/console/j2sdk1.4.0_03/bin# export AVS_HOME
Note
Step 4
# cd $AVS_HOME/console/jboss-3.0.1_tomcat-4.0.4/server/default/conf/# keytool -import -trustcacerts -alias consolecertificate -file server.x509 -keystore ./console.keystoreStep 5
Trust this certificate? [no]:Step 6
Make the following changes to this file:
•
•
•
•
1 <?xml version="1.0" encoding="UTF-8"?>2 <!-- Set catalina.home to the location of the Tomcat-4.x dist.3 The default value is that of the JBoss/Catalina bundle where the4 jakarta-tomcat-4.0.3-LE-jdk14 is included as jboss_dist/catalina5 -->6 <!DOCTYPE server [7 <!ENTITY catalina.home "../catalina">8 ]>910 <!-- The service configuration for the embedded Tomcat4 web container11 -->12 <server>1314 <classpath codebase="file:&catalina.home;/common/lib/" archives="*"/>15 <classpath codebase="file:&catalina.home;/server/lib/" archives="*"/>16 <classpath codebase="file:&catalina.home;/bin/" archives="*"/>17 <classpath codebase="file:&catalina.home;/lib/" archives="*"/>18 <classpath codebase="." archives="tomcat4-service.jar"/>1920212223 <!-- NON SSL SETUP BEGIN: Comment the following for SSL SETUP -->24 <mbean code="org.jboss.web.catalina.EmbeddedCatalinaServiceSX"25 name="jboss.web:service=EmbeddedCatalinaSX">26 <attribute name="CatalinaHome">&catalina.home;</attribute>272829 <attribute name="Config">30 <Server>31 <Service name = "JBoss-Tomcat">32 <Engine name="MainEngine" defaultHost="localhost">33 <Logger className = "org.jboss.web.catalina.Log4jLogger"34 verbosityLevel = "trace" category = "org.jboss.web.localhost.Engine"/>35 <Host name="localhost">36 <Valve className = "org.apache.catalina.valves.AccessLogValve"37 prefix = "localhost_access" suffix = ".log"38 pattern = "common" directory = "../server/default/log" />39 <DefaultContext cookies = "true" crossContext = "true" override = "true" />40 </Host>41 </Engine>424344 <Connector className = "org.apache.catalina.connector.http.HttpConnector"45 port = "9000" minProcessors = "3" maxProcessors = "10" enableLookups = "true"46 acceptCount = "10" debug = "0" connectionTimeout = "60000"/>47 </Service>48 </Server>49 </attribute>50 </mbean>51 <!-- NON SSL SETUP END -->525354 <!-- SSL SETUP BEGIN: Comment the following for Non SSL SETUP55 replace mySecurityDomain, keystorepassword in the following text.56 -->5758 <!---5960 <mbean code="org.jboss.security.plugins.JaasSecurityDomain"61 name="Security:name=JaasSecurityDomain,domain=mySecurityDomain">62 <constructor>63 <arg type="java.lang.String" value="mySecurityDomain"/>64 </constructor>65 <attribute name="KeyStoreURL">console.keystore</attribute>66 <attribute name="KeyStorePass">keystorepassword</attribute>67 </mbean>686970 <mbean code="org.jboss.web.catalina.EmbeddedCatalinaServiceSX"71 name="DefaultDomain:service=EmbeddedCatalinaSX">72 <attribute name="CatalinaHome">&catalina.home;</attribute>73 <attribute name="Config">74 <Server>75 <Service name = "JBoss-Tomcat">76 <Engine name="MainEngine" defaultHost="localhost">77 <Logger className = "org.jboss.web.catalina.Log4jLogger"78 verbosityLevel = "warn" category = "org.jboss.web.localhost.Engine"/>79 <Host name="localhost">80 <Valve className = "org.apache.catalina.valves.AccessLogValve"81 prefix = "localhost_access" suffix = ".log"82 pattern = "common" directory = "../server/default/log" />83 <DefaultContext cookies = "true" crossContext = "true" override = "true" />84 </Host>85 </Engine>868788 <Connector className = "org.apache.catalina.connector.http.HttpConnector"89 port = "9000" scheme = "https" secure = "true" >90 <Factory className = "org.jboss.web.catalina.security.SSLServerSocketFactory"91 securityDomainName = "java:/jaas/mySecurityDomain" clientAuth = "false"92 protocol = "TLS"/>93 </Connector>94 </Service>95 </Server>96 </attribute>97 </mbean>9899 -->100101 <!-- SSL SETUP END -->102103104105106 </server>107Step 7
velocity> set console start
Note
# /etc/init.d/fgndb_de1eb23f6ecf273bee6b4561cd29368e3e539712 start
# /etc/init.d/fgnmc_de1eb23f6ecf273bee6b4561cd29368e3e539712 start
After this procedure, you must access the Management Console by using the HTTPS protocol, like this:
https://consoleIPAddress:consolePort/fgconsole/
