Laserfiche WebLink
<br /> Appendix – Data Store Overview - 1 <br /> <br />Appendix: Data Store Overview <br />20 1 2 -0 5 -15 <br /> <br />Overview <br /> <br />Data stores are used to configure a “connection” to allow data access , and can be of the following type: <br /> <br />• Database Data Store – used when making connections to relational databas es such as Microsoft <br />SQL Server and Oracle. This type of data store is used when a software API (application <br />programmer interface) library is available for direct database communication, typically in an <br />enterprise computing environment. In this case the data store requires a da tabase server name and <br />database name . Database data stores typically are faster but have the disadvantage of requiring <br />that a database be available. <br />• Web Service Data Store – used when making connections to web service s. This type of data store <br />is used wh en a web service API is available, such as using SOAP or REST web service <br />technologies. Requests and data retrievals occur by making HTTP requests rather than direct <br />connections to a database. Web service data stores typically are slower than database da ta stores <br />but have the advantage of not requiring the database to be installed locally. One issue with web <br />services is that it is more difficult to provide data browsing features because lists of stations, etc., <br />must be retrieved with a performance penalt y. TSTool compensates for this by caching data <br />locally in memory or on disk; however, this can require more complex code. Internet access is <br />required to use web service data stores and performance is impacted by other internet users. <br />When using web serv ice data stores it may be appropriate to retrieve data to a local format and <br />then use the local data to perform additional processing. <br /> <br />Additional data store types may be added in the futu re. However, requiring a configuration file is <br />cumbersome for simpl e file access and consequently data stores will be implemented only in cases where <br />the data store configuration can easily be reused between TSTool sessions. <br /> <br />When opened by TSTool, the data store name is used on the end of time series identifiers (TSID) t o <br />indicate the storage location for data. For example, the end of the TSID is as follows: <br /> <br />L ocation .Source .DataType .Interval ~DataStoreName <br /> <br />It is envisioned that some of the legacy “input types” supported by TSTool will be converted to data <br />stores to take advantage of da ta store design features, including greater configuration ability. <br />9