Conditions that make migrating your application model easier

Your present server has adequate resources such as memory, speed, and disk space to be easily scaled up for use with the AppServer.

Your current model has a predominance of small, well-structured, identifiable transactions. The AppServer favors a small transaction model. For more information, see Transaction and record management considerations.

You are already using temp-tables to manipulate data before committing the data to the database. Or, if you are not using temp-tables, it is easy to get your present code to work with temp-tables rather than deal directly with your database.

Your current model is already set up such that neither procedures nor persistent procedures rely on shared/global data or buffers as parameters. These types of information cannot be shared between a client application and an AppServer agent.

Your current model already has a distinct division between the logic associated with the user interface and the logic associated with your application. This enables your code to be modular and portable, in keeping with how you will want your code to be deployed in a distributed environment using the AppServer.