Here are additional architectural issues to keep in mind when programming with the Financial Management objects:
Financial Management is a session-based system, not a transaction-based system. A client remains logged onto an application server, enabling users to perform multiple transactions before logging off.
Security and authentication is automatically applied by Financial Management. The objects enable you to programmatically define application security; however, as a programmer you do not need to do anything to enforce the security that has been defined for an application.
Since an application can have multiple application servers, Financial Management automatically checks the data in the database before it updates a cell’s data. This “synchronization” of data across application servers is automatically applied by Financial Management; you do not need to write any code to do this. For more information, see Data Across Multiple Application Servers: Subcube Caching.