|
|
|
If you choose to create business application names automatically when you run Express Setup, a business application name is created for discovered address spaces. The name allocated is the address space name, and the ports are those ports that are active when it is discovered. However, if you set up your business application names manually, you can define more meaningful names. Only you know who uses the applications, how they are used, and which ones are the most relevant to your business.
Before you define a business application name, you should analyze your environment and decide what you want to monitor. Business application names let you measure more than merely the traffic to one port/protocol or address space. The following examples give you some ideas of what you can define.
Example 1: Break Workload Down by Location and Department
You want to break down the Telnet workload at a location or departmental level. You define the following rules:
With these rules, you separate the Telnet workload for your factory, administration, and IT groups.
Example 2: Show Port Use by Application
You want to see what applications use what ports. You define the following rules:
Example 3: Show Remote Addresses or Ports by Location
You want to display remote addresses and ports by office location. You define the following rules:
Business application names can specify an address space name, port, and stack in their criteria; however, you can name them independently of any address space.
Business application name setup is not bound by address spaces. A business application name does not need any knowledge of the address spaces used by a connection. For example, a business application name can be defined as the following:
| Copyright © 2012 CA. All rights reserved. |
|