Appendix B Migrating Open Server Applications to EAServer
After you have modified your Open Server application and have built your DLLs or shared objects, you need to register your event handlers and configure an Open Server port using Jaguar Manager. This section discusses:
EAServer fully supports all Open Server event handlers. The only difference is that instead of creating a binary file linking the DLL or shared object, you create a DLL or shared object consisting of your event handlers and then specify the location of this file using Jaguar Manager (instead of specifying them in the code).
To specify an event handler from Jaguar Manager:
Event handler | Called |
---|---|
Connect | Each time a client connects to EAServer |
Disconnect | When the client disconnects from EAServer |
Error | When an Open Server processing error occurs |
Initialization | Before starting EAServer |
Start | After initialization, but before accepting client requests |
Stop | When a request to stop the server is made |
Language | When a client sends a language request, such as a SQL statement |
RPC | When a client issues a remote procedure call |
Attention | When an attention had been received. An attention is an immediate event; EAServer services the attention as soon as it occurs, rather than adding it to the client's event queue |
Cursor | When a client sends a cursor request |
Dynamic | When a client sends a dynamic SQL request |
Message | When the client sends a message |
Option | When a client sends an option command |
Bulk | When a client issues a bulk copy request |
To support Open Server clients, you must install a listener in your server that supports Open Server clients. The listener must use protocol TDS and the "Enable Open Server Events" option must be enabled. If you are using the preconfigured Jaguar server, the Jaguar_OpenServer listener supports Open Server connections. Refer to the EAServer System Administration Guide for more information about listeners.
Copyright © 2002 Sybase, Inc. All rights reserved. |
![]() |