Business Application Workload Monitoring Best Practices › Business Applications › Business Applications and Address Spaces

Business Applications and Address Spaces

Although you can optionally specify an address space name, port, and stack as criteria in a business application, you can name the application independently of address spaces. Business application setup is flexible and is not bound by address spaces. A business application does not need to know what address spaces a connection uses.

Examples: Business Application for Address Spaces

• A business application can be a subset of connections to one address space (such as those connections from specific foreign hosts or ports). One address space can have many associated business applications for different subsets of its connections.
• A business application can be all connections to a single address space. You can even call the application the same as the address space, though this implementation is a waste of business application flexibility.

  However, you can map an address space and its backup to the same business application. For example, you can map address spaces AS1 and AS1BKUP to business application APPL123, enabling you to keep continuous performance statistics even when the underlying address space changes.

• A business application can be a subset of the connections to multiple address spaces (for example, traffic from any address spaces to a specific printer).
• A business application can be all connections to multiple address spaces. For example, you have several CICS subsystems and want to group all CICS traffic.