Setting Up To Use Pspi; Calling Stored Procedures - Polycom ReadiVoice Reference Manual

ReadiVoice PSPI Reference

Setting Up to Use PSPI

Calling Stored Procedures

Caution!
4
To use PSPI in an application that you're developing, you must:
Install an ODBC (open database connectivity) or JDBC (Java database
1
connectivity) driver on the client computer.
Properly set up the environment on the client computer.
2
Configure the ODBC/JDBC driver to access your ReadiVoice database on
3
the server.
Set up your application to talk to the ODBC/JDBC driver.
4
The details depend on your client computer operating system, ODBC/JDBC
driver, and application development environment.
Most of the information you need should be in the documentation for the
ODBC/JDBC driver. For instance, if you're using Informix's I-Connect driver,
the driver documentation tells you how to set up the driver in Windows and
Unix environments and how to access and interact with an Informix database
server.
You can execute an SPC:
• From your code (on the client side)
• From within the Informix environment (on the server side)
Running a query alone before incorporating it into your code may be helpful
to you in programming. And running it alone may be useful in debugging a
problem.
Polycom strongly advises against server-side access in a production environment.
For this kind of testing and debugging, the system should be off line.
Regardless of how you call a stored procedure, you must specify all
parameters. You can't do something like this:
DeleteSub_v2320 (2143,,0,0) //WRONG
The value you specify for each parameter must be valid (correct data type and
length). In many cases, the value you specify must be found in the database.
The parameter descriptions for each procedure indicate when this is true.
The parameter descriptions also show when you can use a placeholder, or
"default" value, if you don't need a parameter, and what the correct
placeholder is. For instance, look at the
DeleteSub_v2320()
procedure on
Proprietary & Confidential