Business Application Workload Monitoring Best Practices › Business Applications › Business Application Names

Business Application Names

Business application names can be anything you like—often unrelated to the address space or task name. You can set separate performance and alerting criteria for each name. Names can have optional dynamic suffixes (for example, local port, job name, remote address, or remote port).

Examples: Business Application Names

• The following application names group connections by ports:
  • WebSphereMQ as an application name for all connections to local port 1414
  • Tomcat as an application name for all connections to local ports 8080 and 8443
  • FredUpd as an application name for all connections to task name FRED, port 12300
  • FredAdm as an application name for all connections to task name FRED, port 12301
• The following application name groups all connections between task ABC and local port 12345, and remote address x: BANK1TRANS.
• The following application names group connections by functions:
  • Web as an application name for all connections to local ports 80, 8080, 443, and 8443
  • HTTPS as an application name for all connections to local ports 443 and 8443
  • HTTP as an application name for all connections to local ports 80 and 8080
• The following application name groups all connections to remote address x and port y: PerthOffice.
• The following application names group connections to tasks:
  • CICSSYD as an application name for all connections to CICS* from remote addresses w through x
  • CICSMELB as an application name for all connections to CICS* from remote addresses y through z
  • CICSaddr as an application name for all connections to CICS* from remote address addr
• You can use the same name for a business application on different systems, even if the address space names are different.

  CICSACCT can refer to address space CICSSYS1 on SYS1 and CICSSYS2 on SYS2.