There are two components to the SRP HTTP Framework: the Deployment Package and the Database Tables. Please review the following articles to ensure a smooth installation process.
Installing the Deployment Package
The SRP HTTP Framework ships as a standard deployment (aka RDK) package, usually in .zip format. The name of the compressed file should be SRPHTTPFramework4.0.1.zip (where 4.0.1 would be the current version of the product).
By default, all entities in the deployment are keyed to the FRAMEWORKS application. You may have made special arrangements to re-key the entities to another application. If not and if this is required, please contact us at support@srpcs.com before installing the package.
Installation is as simple as placing the uncompressed deployment files into an empty folder and running the RDKInstall routine to install the entities (e.g., from the System Monitor enter RUN RDKINSTALL "C:\HTTPFrameworkRDK").
Once this is done, you are ready to attached the database tables.
Installing the Database Tables
The SRP HTTP Framework ships with two database tables: CONTACTS and WEB_ACCOUNTS. These are typically provided as .LK/.OV files in a compressed file called WebAppData.zip. Also included in this compressed file is a sub-folder called ContactPictures. This includes several portrait images that correspond with the data in the CONTACTS table.
We recommend placing the uncompressed files into a separate folder, like WebAppData, directly underneath your OpenInsight folder. These tables are keyed to the GLOBAL database so they should be easy to attach using the Database Manager. Once they have been attached we also recommend saving the database so that the application will remember to attach these tables whenever it is launched.
The CONTACTS database table includes data that will be accessed by the sample Contacts web API that ships with the SRP HTTP Framework.
The WEB_ACCOUNTS table is used by the SRP HTTP Framework to authenticate API requests.
Once you are familiar with writing APIs and have other tables that are being accessed, you can remove the CONTACTS table from your environment. The WEB_ACCOUNTS table should be kept unless or until you employ an alternative form of authentication.
