Appendix B Open Server Migration To Jaguar
Jaguar configuration
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:
Before configuring jaguar
You must install and start Jaguar, and Jaguar Manager, before
you can begin the configuration process. Refer to the Jaguar
CTS System Administration Guide for more information.
Installing event handlers
Jaguar 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).
Specifying event handlers
To specify an event handler from Jaguar Manager:
- Double-click the Servers folder.
- Highlight the server for which you are specifying
the event handler.
- Select File | Server Properties.
- Select the Handlers tab.
- Enter the DLL or shared library name and the function
name of the specific event handler being called, separated by a
colon.
The following examples illustrate an entry for a connect event
handler for Solaris and NT:
- Solaris
libsamp.so:debug_connect
where libsamp.so is the shared library name and debug_connect is
the function called whenever a connect event handler is called.
- NT
libsamp.dll:debug_connect
where libsamp.dll is the DLL name and debug_connect is
the function called whenever a connect event handler is called.
- The following table summarizes the types of event handlers
that you can install. For information on coding event handlers,
refer to"Additional event handler
information"and
your Open Server documentation.
Table 35-1: Individual server event handlers
Event handler
|
Called
|
Connect
|
Each time a client connects to Jaguar
|
Disconnect
|
When the client disconnects from Jaguar
|
Error
|
When a Jaguar server processing error
occurs
|
Initialization
|
Before starting Jaguar
|
Start
|
When a request to start the Jaguar server
is made
|
Stop
|
When a request to stop the Jaguar 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; Jaguar 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
|
Configuring an Open Server listener
To support Open Server clients, configure a Jaguar listener
that uses a TDS port and click the "Enable Open Server
Events" check box. This allows the port to dispatch client
requests in the same way as your current Open Server applications.
Configuration
tasks
This section describes how to modify the preconfigured OpenServer
listener to accept client connections. To access the Listeners folder
from Jaguar Manager:
- Double-click
the Servers folder.
- Double-click the server for which you want to establish
a listener.
- Click the Listeners folder on the left side of the
window.
- Highlight the OpenServer listener on the right side
of the window.
- Select File | Listener Properties. The
Listener Info dialog box appears.
- Configure the listener. The table below describes
the listener properties.
Table 35-2: Listener profile properties
Property
|
Description
|
Comments/example
|
Protocol
|
Jaguar supports:
- HTTP
- IIOP
- TDS
- HTTPS
- IIOPS
|
The OpenServer listener is already configured
to use TDS.
|
Host
|
The name or IP address of the
Jaguar host to which the listener is being assigned.
|
For the predefined OpenServer listener,
change the initial setting from "localhost" to
the actual machine name.
Note
If Jaguar is installed on the same host as your previous Open
Server application and you use the same port number to listen for
client requests, no client configuration is required. If, however,
Jaguar is on a different machine or a different port is used, you
must modify the interfaces file on the client to reflect the changes.
|
Port
|
The port number on the host
to which the listener is assigned.
|
Make sure that the port is not in use
by any other service.
|
Jaguar Security Profile
|
This field is enabled for only
the secure protocols (HTTPS or IIOPS).
|
Open Server ports do not support security
profiles.
|
Enable Open Server Events
|
When selected, the TDS port
accepts open server client connections, if not, only MASP requests
are accepted.
|
You must use TDS as the protocol for Open
Server Events.
|
After modifying a listener you must restart the Jaguar
server for your changes to take effect.
Refer to the Jaguar CTS System Administration Guide for
more information about listeners.
Copyright © 2000 Sybase, Inc. All rights reserved.
|
|