The business logic part of an interaction should be isolated from the details of Web technology. As a result, it is valuable to consider the interface between the Web parts of the interaction (interaction controllers and UI logic) and the business logic. The business logic can be wrapped with JavaBeans. A command bean should usually represent a single function supported by the business logic. Its usage paradigm is: create the bean, initialize by setting the bean's properties, perform by calling the bean's methods, and inspect by getting the values of the bean's properties. Using command beans of this form provides several benefits including:

• Isolation of changes - wrapping the business logic with command beans as opposed to exposing the business logic model directly allows the business logic to evolve without disrupting the rest of the Web application.
• Distribution - command beans can be serialized and sent via a protocol (IIOP, HTTP, etc.) to a remote server to be executed and then sent back. This allows for very efficient communication.

The business logic part of a Web application is the piece of code ultimately responsible for satisfying client requests. As a result, business logic must address a wide range of potential requirements which include ensuring transactional integrity of application components, maintaining and quickly accessing application data, supporting the coordination of business workflow processes, and integrating new application components with existing applications.