The RPC Plugin

A description of the RPC plugins provided by and how they operate.

RPC plugins are compiled .dll files (on Microsoft Windows) or .so files (on UNIX-like operating systems). These libraries are called by the Sybase CEP Server, and are able to communicate with RPC servers. The RPC plugin calls the remote procedure, typically using Simple Object Access Protocol (SOAP), HTTP, or another protocol appropriate for the specific remotely callable procedure.

The plugin receives information (such as the body of an email message, a stock symbol, or an employee ID number) from the CCL statement and passes the information to the remote procedure. The plugin also receives information from the remote procedure (when appropriate) and makes it available to the CCL statement.

The RPC plugin you are using must be designed and configured to work with the specific remote procedure you are using. The plugin must be able to contact the RPC server (for example, via an HTTP URL), must invoke the name of the desired remote procedure on that RPC server, and so on. In some cases, the appropriate plugin may be obtainable from a third-party vendor. You can also write your own RPC plugin.

provides two generic plugins that allow you to make remote procedure calls to RPC servers that handle SOAP and HTTP protocols. Each of these plugins may be used as-is or customized for your needs. The generic SOAP plugin includes an example SOAP RPC plugin and corresponding service entry in the c8-services.xml file.

Note: Do not confuse the RPC plugins discussed in this chapter with Sybase CEP Server plugins discussed in HTTP and SOAP Plugin Preferences. Although there are some similarities, they are not the same.