Cisco ACE XML Gateway User Guide (Software Version 6.1) - First Steps [Cisco ACE XML Gateways]

Table Of Contents

First Steps

Logging In to the Manager Web Console

Navigating the Manager Web Console

Navigation Menu

Status Bar

Property Pages

Using Subpolicies to Organize the Policy

Adding Gateways to the Manager's Control

Adding Gateways to the Default Cluster

Logging Out of the Console Securely

First Steps

This chapter introduces the ACE XML Manager web console. It covers these topics:

•Logging In to the Manager Web Console

•Navigating the Manager Web Console

•Using Subpolicies to Organize the Policy

•Adding Gateways to the Manager's Control

•Logging Out of the Console Securely

Logging In to the Manager Web Console

Once the ACE XML Manager is installed on your network, you can log into the browser-based environment for developing the ACE XML Gateway policy, the ACE XML Manager web console.

The ACE XML Manager web console works with recent versions of most types of browsers. It is specifically supported on Mozilla Firefox 1.5.0.x and 2.0.0.x and Microsoft Internet Explorer 5.5 and 6. JavaScript functionality must be enabled in the browser for many ACE XML Manager web console features to work properly.

To log in to the ACE XML Manager web console:

Step 1 On a computer accessible by network to the ACE XML Manager appliance, open a browser and go to the following address:

https://<hostname>:8243

Where <hostname> is the IP address or hostname of your ACE XML Manager. Notice that secure HTTP (HTTPS) is used for the connection and the default port on which the ACE XML Manager listens for console requests is 8243.

The browser displays the login page, as shown in Figure 3-1.

Figure 3-1 ACE XML Manager web console login

The hostname for the ACE XML Manager is configured at initial installation time. If you don't know the path to the login page for your installation, ask your administrator.

Other users who are already logged into the web console are listed on the login page. It is important to note when other users are logged into the console. The ACE XML Manager does not prevent you from overwriting each others' changes (the last save wins if a single settings page is edited by multiple users at the same time). For this reason, it is important that you check your work carefully and test new policies in a testing environment before deploying them to production.

Step 2 If this ACE XML Manager is used to administer multiple clusters of ACE XML Gateways, a menu may appear that allows you to choose which cluster policy you want to access. In this case, choose the name of the cluster to edit from the menu.

Step 3 Enter your username in the Username field. For example, if you are the administrator, enter administrator in this field. This is a preconfigured user account with full privileges to the console.

Note For details on adding user accounts for the ACE XML Manager web console, see Chapter 33, "Managing Web Console Users."

Step 4 Enter the password in the Password field.

Note The default password for the Administrator user is "swordfish". For security reasons, be sure to change the default password.

Step 5 Click the Log In button.

If you do not enter a valid username and password combination, an error message appears. Depending on how your administrator has configured Manager access, you may have a limited number of failed login attempts before the ACE XML Manager exits unconditionally and disables the user account (three, by default). This security feature applies to all user accounts except the administrator user account. (It does apply to user accounts created with the administrator user type).

For information on this feature and restoring a user account, see "Configuring Failed Login Attempt User Blocking" section on page 35-360.

If you enter a valid username/password combination, one of several pages may appear:

•The license error page appears if a license has not yet been configured for the ACE XML Manager. See the Cisco ACE XML Gateway Administration Guide for more information on acquiring and applying licenses for the ACE XML Gateway and Manager.

•The Welcome page appears if the ACE XML Manager has a valid license and the policy is not yet configured for service routing. From the Welcome page, you can start defining virtual services.

•If the policy contains virtual services, the Dashboard page appears. The Manager Dashboard provides an overview of system events and activities.

It is recommended that you change the password from the one assigned to you upon first login. To do so, click on your username at the top right of the page. In the User Information window, click the Change Password button to specify a new password.

By default, the console requires passwords to meet a minimum level of complexity. The password must be at least eight characters long, it should not consist of a dictionary word as more than a minimum percentage of the overall password, and it should not resemble a social security number or national ID number. In general, it is recommended that you use a combination of letters, numerals, and special characters in your password.

Navigating the Manager Web Console

shows the main parts of the ACE XML Manager web console interface.

Figure 3-2 ACE XML Manager Dashboard

As shown in , the ACE XML Manager web console is organized into these areas:

•Navigation Menu

•Status Bar

•Property Pages

Navigation Menu

The navigation menu appears at the left side of the console. It provides links to the primary settings and monitoring pages in the console, organized into these categories:

•Policy section contains links for pages for defining the rules and processing operations applicable to traffic handled by the ACE XML Gateway.

•Resources section links to pages for managing the resource files used in the policy. For more information, see Chapter 28, "Managing Resource Files."

•Reports & Tools links to pages for monitoring the status of the ACE XML Gateway and the network.

•Administration has links to pages that allow console administrators to control the ACE XML Manager itself, for example, for licenses, user accounts, audit logging, and diagnostics.

The Quick Links button () appears next to the Policy heading of the navigation menu. It provides access to common tasks, including importing a WSDL file, creating a virtual service, and creating an authenticator (the policy object used to control access to services).

Status Bar

The status bar appears at the top of every page in the console. It displays the currently active subpolicy and the username of the user account currently accessing the console. It provides buttons for common operations in the console, such as deploying the policy and logging out.

Administrator users can configure banner text that appears in the status bar, for example, to post notifications or other types of information for other console users.

A subpolicy is a container for organizing objects within a policy. The Shared subpolicy is a built-in subpolicy that's present whether or not you are using subpolicies to organize your work. It contains the common objects used throughout all subpolicies.

If subpolicies besides Shared exist in the policy in your environment, the Switch button appears next to the subpolicy label. Click the Switch button to change your working context to another subpolicy.

For more information on subpolicies, see "Working with Subpolicies" section on page 30-300.

Property Pages

A property page displays information or settings for a particular area of the system's operations. In general, the property page provides access to the configuration controls for any configurable settings associated with the feature.

Using Subpolicies to Organize the Policy

You can organize related objects in a policy with subpolicies. A subpolicy is a subset of the objects in a given policy. Access to subpolicies can be controlled, so that only console users with privileges to a subpolicy can make changes to it.

The system includes a built-in subpolicy named Shared. When you first log in to the web console for a newly installed ACE XML Manager, the Shared subpolicy is active. The Shared subpolicy is the only subpolicy whose objects that can be accessed from other subpolicies. Otherwise, settings and objects cannot be used across subpolicies.

The best organizational strategy for subpolicies—that is, how you choose which objects are created in particular subpolicies or in Shared—will likely vary from one implementation to another. In general, however, the Shared subpolicy should hold resources needed across projects, such as port settings, certificate authorities, common back-end HTTP servers, and so on. Subpolicies, on the other hand, usually hold application-specific objects, such as virtual services and authentication objects.

If subpolicies are used in your policy, it is important to be aware of which subpolicy is active in the ACE XML Manager web console before making configuration changes or adding policy objects. When you create a policy object in a given subpolicy, it will be editable only in the context of that subpolicy, and only by users who have privileges to modify that subpolicy.

Subpolicies help you to manage and secure your policy development environment. Approval-based deployment provides a similar benefit. With approval-based deployment, a console administrator must approve a policy deployment for it to be propagated to the ACE XML Gateways. This feature helps to control and manage the policy change and deployment process.

While subpolicies provide a means of organizing objects within a policy, large implementations may require the use of different policies to partition work. The multiple cluster management feature of the ACE XML Manager allows you to develop different policies in a given ACE XML Manager instance and deploy them to different ACE XML Gateway clusters.

Adding Gateways to the Manager's Control

As described in the Cisco ACE XML Gateway Administration Guide, an ACE XML appliance can operate in one of three modes: in gateway, manager, or standalone mode (in which the appliance operates as both gateway and manager mode).

For a standalone appliance, after initial configuration, the ACE XML Manager is already configured for self-management (that is, an entry for itself exists in the Manager's managed Gateway list). You can start working on the policy immediately, without having to add Gateways to the configuration.

However, if the appliance is in Manager-only mode, you will need to add a Gateway to the Manager's administrative control before you can deploy and test a policy, as described here.

Note For a standalone appliance, the ACE XML Manager can control other Gateway appliances as well as its own Gateway instance. Therefore, these steps are also applicable if you want to add Gateways to the administrative control of a Manager on a standalone appliance.

An ACE XML Gateway should not be configured to be in the control of more than one ACE XML Manager at a time. This restriction applies to management by actual Manager appliances or Manager instances created with the Multiple Cluster Management feature.

The general steps for adding a Gateway to the Manager's control are:

1. When configuring the operating mode of the Gateway from the appliance shell interface, specify the IP address of the Manager that is to control this Gateway.

Note For more information, see the Cisco ACE XML Gateway Administration Guide.

2. In the web console for the ACE XML Manager, add the Gateway to one of the Manager's cluster pools, such as to its default cluster.

3. Check the licensing status of the added ACE XML Gateway in the web console. If needed, request and apply a license.

This section describes step 2, how to add a Gateway to one of the Manager's clusters. Once the Gateway belongs to a cluster group, it can receive policy deployments from the Manager. In turn, the Gateway reports on its activities back to the Manager, which aggregates logging information for all Gateways in its control. For more information on steps 1 and 3, see the Cisco ACE XML Gateway Administration Guide.

Note An ACE XML Manager can control more than one cluster of Gateways. While all Gateways in a single cluster should have the same policy version, multiple clusters in the Manager's control can apply different policy versions. For more information, see Chapter 34, "Managing Gateway Clusters."

Adding Gateways to the Default Cluster

To add an ACE XML Gateway to the Manager's control, you add it to a cluster in the Manager configuration. As noted, you do not need to perform these steps for a standalone appliance; they are needed only if configuring a Manager-only appliance or to add additional Gateways to a standalone appliance's administrative control.

The Manager comes with a preconfigured cluster named "Default Cluster" to which you can add ACE XML Gateways. Notice that you can rename the default cluster and make other changes to its settings. You should not add new clusters to the Manager configuration unless you specifically intend to maintain separate ACE XML Gateway environments. For more information, see Chapter 34, "Managing Gateway Clusters."

To add an ACE XML Gateway to the default cluster:

Step 1 As a user with administrator privileges in the Manager web console, click the Cluster Management link from the navigation menu.

The cluster management page should show a cluster named "Default Cluster." On the Manager of a standalone mode appliance, the Default Cluster lists this appliance as the only member. Otherwise, new installations will show the default cluster as empty.

Step 2 Add the Gateway to the cluster by clicking the edit link next to the Default Cluster.

Step 3 Optionally, modify the preconfigured settings for the default cluster, such as its name and HTTPS port and the security certificate used for SSL access to the Manager web console.

The SSL Certificate shown on this page applies to the connection from a web browser to the Manager web console. As indicated in the menu, the Manager provides a temporary certificate that is used by default. It is recommended that you replace the built-in certificate with a server certificate you generate. If the Manager and development workstations will be operating within a secure network, you may choose to use a self-signed certificate. However, for greater security it is recommended that you use a CA-signed certificate, particularly if the cluster is deployed in a production environment.

You can generate a new certificate to use for the browser connection by clicking the Manage SSL Certificates button on the Cluster Management page. From there, use the Generate CSR button to generate a certificate signing request. For more information, see "Generating a CSR" section on page 28-284. Once the server certificate is generated and uploaded in the Manager, choose it from the menu on this page to apply it to the browser connection.

Step 4 In the Cluster Members text field, type the IP address and administration port of each ACE XML Gateway you want to add to this cluster. The address for each Gateway should be on its own line in the text field, such as:

10.0.5.12
10.0.5.22

The administration port used by the Manager and Gateway to exchange administrative information, such as log events, is 8200. If you have a specific network prerequisite that prevents you from using it, you can specify another port by appending it to the IP address.

Step 5 Click Save Changes.

Step 6 After being added to a cluster, the Gateway usually needs to be configured with a license. To check the license status of the Gateway, open the License Management page in the web console. If a license is required for the Gateway, refer to the Cisco ACE XML Gateway Administration Guide for information on acquiring and applying product licenses to the appliance.

The ACE XML Gateway should appear as a member of the cluster in the Cluster Management page. You can now deploy the policy from the ACE XML Manager to the ACE XML Gateways in its control.

For more information on working with clusters, see Chapter 34, "Managing Gateway Clusters."

Logging Out of the Console Securely

For security reasons, it is extremely important that you do not leave any user session with the ACE XML Manager web console unattended. After using web console, you should log out and close all browser windows you used. If you do not, other users could view pages cached by your browser during the user session.

Take the following steps to log out of the ACE XML Manager securely:

Step 1 Click the Logout button.

Step 2 In the confirmation dialog, click the OK button to log out.

Step 3 Close all browser windows used in your console session.

For additional security, clear your browser's cache after you log out of the ACE XML Manager.

	Cisco ACE XML Gateway User Guide (Software Version 6.1)
	First Steps
Cisco ACE XML Gateway User Guide (Software Version 6.1) Preface Introducing the Cisco ACE XML Gateway Basic Concepts First Steps Working with Virtual Services Working with Handlers, Routes, and Service Descriptors Controlling Access to Services Authenticating Requests to Backend Systems Editing and Maintaining Virtual Services Using Variables in Paths Validating Messages Processing SOAP Messages XML Encryption and XML Signature Transforming Messages with XSLT Configuring Destination Server Settings Working with Ports and Hostnames Working with JMS Traffic Working with TIB/RV and MQ Services Working with ebXML Traffic Securing Traffic with SSL/TLS Configuring Reactor Processing Caching Service Responses Mapping HTTP Error Responses Setting Global Traffic Rules Securing Web Applications Working with Virtual Web Applications Working with Profiles Developing Rules and Signatures Managing Resource Files Deploying the Policy Managing the Policy Publishing Service Information Monitoring System Status Managing Web Console Users Managing Gateway Clusters Configuring the Manager Web Console Using the ACE XML Manager SOAP API Troubleshooting Log Messages	Download this chapter First Steps Download the complete book Cisco ACE XML Gateway User Guide Book-Length PDF (PDF - 10 MB) Feedback Table Of Contents First Steps Logging In to the Manager Web Console Navigating the Manager Web Console Navigation Menu Status Bar Property Pages Using Subpolicies to Organize the Policy Adding Gateways to the Manager's Control Adding Gateways to the Default Cluster Logging Out of the Console Securely First Steps This chapter introduces the ACE XML Manager web console. It covers these topics: •Logging In to the Manager Web Console •Navigating the Manager Web Console •Using Subpolicies to Organize the Policy •Adding Gateways to the Manager's Control •Logging Out of the Console Securely Logging In to the Manager Web Console Once the ACE XML Manager is installed on your network, you can log into the browser-based environment for developing the ACE XML Gateway policy, the ACE XML Manager web console. The ACE XML Manager web console works with recent versions of most types of browsers. It is specifically supported on Mozilla Firefox 1.5.0.x and 2.0.0.x and Microsoft Internet Explorer 5.5 and 6. JavaScript functionality must be enabled in the browser for many ACE XML Manager web console features to work properly. To log in to the ACE XML Manager web console: Step 1 On a computer accessible by network to the ACE XML Manager appliance, open a browser and go to the following address: https://<hostname>:8243 Where <hostname> is the IP address or hostname of your ACE XML Manager. Notice that secure HTTP (HTTPS) is used for the connection and the default port on which the ACE XML Manager listens for console requests is 8243. The browser displays the login page, as shown in Figure 3-1. Figure 3-1 ACE XML Manager web console login The hostname for the ACE XML Manager is configured at initial installation time. If you don't know the path to the login page for your installation, ask your administrator. Other users who are already logged into the web console are listed on the login page. It is important to note when other users are logged into the console. The ACE XML Manager does not prevent you from overwriting each others' changes (the last save wins if a single settings page is edited by multiple users at the same time). For this reason, it is important that you check your work carefully and test new policies in a testing environment before deploying them to production. Step 2 If this ACE XML Manager is used to administer multiple clusters of ACE XML Gateways, a menu may appear that allows you to choose which cluster policy you want to access. In this case, choose the name of the cluster to edit from the menu. Step 3 Enter your username in the Username field. For example, if you are the administrator, enter `administrator` in this field. This is a preconfigured user account with full privileges to the console. Note For details on adding user accounts for the ACE XML Manager web console, see Chapter 33, "Managing Web Console Users." Step 4 Enter the password in the Password field. Note The default password for the Administrator user is "swordfish". For security reasons, be sure to change the default password. Step 5 Click the Log In button. If you do not enter a valid username and password combination, an error message appears. Depending on how your administrator has configured Manager access, you may have a limited number of failed login attempts before the ACE XML Manager exits unconditionally and disables the user account (three, by default). This security feature applies to all user accounts except the administrator user account. (It does apply to user accounts created with the administrator user type). For information on this feature and restoring a user account, see "Configuring Failed Login Attempt User Blocking" section on page 35-360. If you enter a valid username/password combination, one of several pages may appear: •The license error page appears if a license has not yet been configured for the ACE XML Manager. See the Cisco ACE XML Gateway Administration Guide for more information on acquiring and applying licenses for the ACE XML Gateway and Manager. •The Welcome page appears if the ACE XML Manager has a valid license and the policy is not yet configured for service routing. From the Welcome page, you can start defining virtual services. •If the policy contains virtual services, the Dashboard page appears. The Manager Dashboard provides an overview of system events and activities. It is recommended that you change the password from the one assigned to you upon first login. To do so, click on your username at the top right of the page. In the User Information window, click the Change Password button to specify a new password. By default, the console requires passwords to meet a minimum level of complexity. The password must be at least eight characters long, it should not consist of a dictionary word as more than a minimum percentage of the overall password, and it should not resemble a social security number or national ID number. In general, it is recommended that you use a combination of letters, numerals, and special characters in your password. Navigating the Manager Web Console shows the main parts of the ACE XML Manager web console interface. Figure 3-2 ACE XML Manager Dashboard As shown in , the ACE XML Manager web console is organized into these areas: •Navigation Menu •Status Bar •Property Pages Navigation Menu The navigation menu appears at the left side of the console. It provides links to the primary settings and monitoring pages in the console, organized into these categories: •Policy section contains links for pages for defining the rules and processing operations applicable to traffic handled by the ACE XML Gateway. •Resources section links to pages for managing the resource files used in the policy. For more information, see Chapter 28, "Managing Resource Files." •Reports & Tools links to pages for monitoring the status of the ACE XML Gateway and the network. •Administration has links to pages that allow console administrators to control the ACE XML Manager itself, for example, for licenses, user accounts, audit logging, and diagnostics. The Quick Links button () appears next to the Policy heading of the navigation menu. It provides access to common tasks, including importing a WSDL file, creating a virtual service, and creating an authenticator (the policy object used to control access to services). Status Bar The status bar appears at the top of every page in the console. It displays the currently active subpolicy and the username of the user account currently accessing the console. It provides buttons for common operations in the console, such as deploying the policy and logging out. Administrator users can configure banner text that appears in the status bar, for example, to post notifications or other types of information for other console users. A subpolicy is a container for organizing objects within a policy. The Shared subpolicy is a built-in subpolicy that's present whether or not you are using subpolicies to organize your work. It contains the common objects used throughout all subpolicies. If subpolicies besides Shared exist in the policy in your environment, the Switch button appears next to the subpolicy label. Click the Switch button to change your working context to another subpolicy. For more information on subpolicies, see "Working with Subpolicies" section on page 30-300. Property Pages A property page displays information or settings for a particular area of the system's operations. In general, the property page provides access to the configuration controls for any configurable settings associated with the feature. Using Subpolicies to Organize the Policy You can organize related objects in a policy with subpolicies. A subpolicy is a subset of the objects in a given policy. Access to subpolicies can be controlled, so that only console users with privileges to a subpolicy can make changes to it. The system includes a built-in subpolicy named Shared. When you first log in to the web console for a newly installed ACE XML Manager, the Shared subpolicy is active. The Shared subpolicy is the only subpolicy whose objects that can be accessed from other subpolicies. Otherwise, settings and objects cannot be used across subpolicies. The best organizational strategy for subpolicies—that is, how you choose which objects are created in particular subpolicies or in Shared—will likely vary from one implementation to another. In general, however, the Shared subpolicy should hold resources needed across projects, such as port settings, certificate authorities, common back-end HTTP servers, and so on. Subpolicies, on the other hand, usually hold application-specific objects, such as virtual services and authentication objects. If subpolicies are used in your policy, it is important to be aware of which subpolicy is active in the ACE XML Manager web console before making configuration changes or adding policy objects. When you create a policy object in a given subpolicy, it will be editable only in the context of that subpolicy, and only by users who have privileges to modify that subpolicy. Subpolicies help you to manage and secure your policy development environment. Approval-based deployment provides a similar benefit. With approval-based deployment, a console administrator must approve a policy deployment for it to be propagated to the ACE XML Gateways. This feature helps to control and manage the policy change and deployment process. While subpolicies provide a means of organizing objects within a policy, large implementations may require the use of different policies to partition work. The multiple cluster management feature of the ACE XML Manager allows you to develop different policies in a given ACE XML Manager instance and deploy them to different ACE XML Gateway clusters. Adding Gateways to the Manager's Control As described in the Cisco ACE XML Gateway Administration Guide, an ACE XML appliance can operate in one of three modes: in gateway, manager, or standalone mode (in which the appliance operates as both gateway and manager mode). For a standalone appliance, after initial configuration, the ACE XML Manager is already configured for self-management (that is, an entry for itself exists in the Manager's managed Gateway list). You can start working on the policy immediately, without having to add Gateways to the configuration. However, if the appliance is in Manager-only mode, you will need to add a Gateway to the Manager's administrative control before you can deploy and test a policy, as described here. Note For a standalone appliance, the ACE XML Manager can control other Gateway appliances as well as its own Gateway instance. Therefore, these steps are also applicable if you want to add Gateways to the administrative control of a Manager on a standalone appliance. An ACE XML Gateway should not be configured to be in the control of more than one ACE XML Manager at a time. This restriction applies to management by actual Manager appliances or Manager instances created with the Multiple Cluster Management feature. The general steps for adding a Gateway to the Manager's control are: 1. When configuring the operating mode of the Gateway from the appliance shell interface, specify the IP address of the Manager that is to control this Gateway. Note For more information, see the Cisco ACE XML Gateway Administration Guide. 2. In the web console for the ACE XML Manager, add the Gateway to one of the Manager's cluster pools, such as to its default cluster. 3. Check the licensing status of the added ACE XML Gateway in the web console. If needed, request and apply a license. This section describes step 2, how to add a Gateway to one of the Manager's clusters. Once the Gateway belongs to a cluster group, it can receive policy deployments from the Manager. In turn, the Gateway reports on its activities back to the Manager, which aggregates logging information for all Gateways in its control. For more information on steps 1 and 3, see the Cisco ACE XML Gateway Administration Guide. Note An ACE XML Manager can control more than one cluster of Gateways. While all Gateways in a single cluster should have the same policy version, multiple clusters in the Manager's control can apply different policy versions. For more information, see Chapter 34, "Managing Gateway Clusters." Adding Gateways to the Default Cluster To add an ACE XML Gateway to the Manager's control, you add it to a cluster in the Manager configuration. As noted, you do not need to perform these steps for a standalone appliance; they are needed only if configuring a Manager-only appliance or to add additional Gateways to a standalone appliance's administrative control. The Manager comes with a preconfigured cluster named "Default Cluster" to which you can add ACE XML Gateways. Notice that you can rename the default cluster and make other changes to its settings. You should not add new clusters to the Manager configuration unless you specifically intend to maintain separate ACE XML Gateway environments. For more information, see Chapter 34, "Managing Gateway Clusters." To add an ACE XML Gateway to the default cluster: Step 1 As a user with administrator privileges in the Manager web console, click the Cluster Management link from the navigation menu. The cluster management page should show a cluster named "Default Cluster." On the Manager of a standalone mode appliance, the Default Cluster lists this appliance as the only member. Otherwise, new installations will show the default cluster as empty. Step 2 Add the Gateway to the cluster by clicking the edit link next to the Default Cluster. Step 3 Optionally, modify the preconfigured settings for the default cluster, such as its name and HTTPS port and the security certificate used for SSL access to the Manager web console. The SSL Certificate shown on this page applies to the connection from a web browser to the Manager web console. As indicated in the menu, the Manager provides a temporary certificate that is used by default. It is recommended that you replace the built-in certificate with a server certificate you generate. If the Manager and development workstations will be operating within a secure network, you may choose to use a self-signed certificate. However, for greater security it is recommended that you use a CA-signed certificate, particularly if the cluster is deployed in a production environment. You can generate a new certificate to use for the browser connection by clicking the Manage SSL Certificates button on the Cluster Management page. From there, use the Generate CSR button to generate a certificate signing request. For more information, see "Generating a CSR" section on page 28-284. Once the server certificate is generated and uploaded in the Manager, choose it from the menu on this page to apply it to the browser connection. Step 4 In the Cluster Members text field, type the IP address and administration port of each ACE XML Gateway you want to add to this cluster. The address for each Gateway should be on its own line in the text field, such as: 10.0.5.12 10.0.5.22 The administration port used by the Manager and Gateway to exchange administrative information, such as log events, is 8200. If you have a specific network prerequisite that prevents you from using it, you can specify another port by appending it to the IP address. Step 5 Click Save Changes. Step 6 After being added to a cluster, the Gateway usually needs to be configured with a license. To check the license status of the Gateway, open the License Management page in the web console. If a license is required for the Gateway, refer to the Cisco ACE XML Gateway Administration Guide for information on acquiring and applying product licenses to the appliance. The ACE XML Gateway should appear as a member of the cluster in the Cluster Management page. You can now deploy the policy from the ACE XML Manager to the ACE XML Gateways in its control. For more information on working with clusters, see Chapter 34, "Managing Gateway Clusters." Logging Out of the Console Securely For security reasons, it is extremely important that you do not leave any user session with the ACE XML Manager web console unattended. After using web console, you should log out and close all browser windows you used. If you do not, other users could view pages cached by your browser during the user session. Take the following steps to log out of the ACE XML Manager securely: Step 1 Click the Logout button. Step 2 In the confirmation dialog, click the OK button to log out. Step 3 Close all browser windows used in your console session. For additional security, clear your browser's cache after you log out of the ACE XML Manager.
	Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks