Appendix B Migrating Open Server Applications to EAServer

Migration overview

Migrating your Open Server applications allows you to take advantage of EAServer features such as:

• High scalability and high performance engine - EAServer is based on kernel threads and supports symmetric multiprocessors (SMP)
• Built in worker thread and thread pooling facilities supports large concurrent client loads
• Ability for applications to make blocking or synchronous calls that do not block the entire process
• Operating system based authentication services
• Jaguar Manager, an easy-to-use graphical user interface for:
  
  
  • Installing and configuring event handlers
  • Managing the server
  • Monitoring the server
  • Accessing Open Client and ODBC connection cache facilities

To migrate an Open Server application to EAServer, the application must be built as a shared object or a DLL (on Windows) instead of a binary. The shared object contains all of the Open Server event handler code currently residing in the application code.

To migrate your Open Server applications to EAServer:

1. Modify your Open Server code to run in EAServer by:
   
   
   • Removing your existing code from the main function and placing it in an event handler and removing the srv_run and other routines. Refer to "Modifying main" for more information.
   • Modifying your application so that it runs in a preemptive scheduling environment. Refer to "Coding changes and examples" for coding examples and guidelines.
2. Once you have modified your code, create and build one or more DLLs or shared objects consisting of your event handlers. Refer to "DLLs, shared objects, and makefiles" for more information.
3. Using Jaguar Manager:
   
   
   • Install your event handlers. Refer to "Installing event handlers".
   • Configure an EAServer listener to accept client requests. Refer to "Configuring an Open Server listener".

Limitations

EAServer does not support DCE or Kerberos.

Copyright © 2002 Sybase, Inc. All rights reserved.