3.2 WAM Application Design

• When designing a LANSA Web application, you must determine the number of WAMs required by your application and the WEBROUTINES that will belong to each WAM. Typically, you will divide your application into functional areas where each area is represented by a WAM.

• You must also understand WAM session management (refer to WAM Session Management) when designing your WAM/WEBROUTINE structures. By default, each WAM maintains its own session state independent of other WAMs, but you may chain WAM sessions.

• Modularize your WAM applications by using other RDMLX components. Use RDMLX Components in your WEBROUTINEs and assign business rule processing to them. This design will provide a good foundation for code re-use across different presentation technologies, such as GUI and browser-based applications.

• Using a WEBROUTINE Service Name provides greater flexibility when deploying WAM applications. For example, it allows applications to be re-deployed to a different Partition, WAM or WEBROUTINE without having to modify any external URL references to it.