I'm working on the last bit of XECS-1487 which involves sipXsupervisor checking the existence of an SQL Database resource defined in a process definition file.
First of all, it appears that the only way to really check to ensure that a database is defined is to actually try and connect to it. This is the approach that I'm planning on taking to verify this. In order to connect to a database using ODBC, the following parameters are required: 1. Database Name 2. Server Name 3. User Name 4. Database Driver 5. Password At present, the schema for process defnition files only allows/provides the Database Name that is a required resource for the process. Obviously this is not enough information to attempt a database connection. There are a few solutions that I can look into: A) Modify the schema to allow the other necessary parameters to be provided. B) Define constant values for the other parameters and use those in the code since at present all our database are Postgres, running on the local host and use the username 'Postgres' with no password. C) Modify the sipXsupervisor config file to include definitions for these parameters. D) Combination of B + C. If the config file has a definition use it otherwise use the constant value. Method A provides the most flexibility but do we need this as sipXecs today only uses local databases? Method B is not very flexible but maybe good enough for our needs. Method C provides more flexibility than B. Method D is probably the best compromise and similar to what is done today in sipXProxy. Does anyone have any other suggestions or a preference for one of the methods above? Thanks in advance Raymond
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
