External data sources definition in RefTracker (notes for programmers and DBA’s)

The data source definition defines the type of connection and connection string required to access the external data source. This information will need to be supplied by the owner of that data source (usually your IT department DBA or local web service programmer).

To add a new data source definition, enter a description, connection string and the type of data source and click Update.

To amend an existing data source definition, make any changes to the entries for that data source and click Update.

After a data source definition is added or updated the system will check that it can access that data source, and report an error if it cannot, to ensure that your new definition is a working one.

Description is a descriptive name for the external data source to be looked up.

Enabled allows a definition for a data source that is not yet accessible, to be saved as disabled, and enabled when it becomes available. This is necessary as all enabled definitions in this page must be valid.

Connection string is the information required to access this data source. It will need to be obtained from the owner of the data source that will be looked up. For SQL Server data sources, this will usually be provided by the DBA in your IT department. It will probably be in a format similar to this Data Source=utah9;Initial Catalog=xeno;User ID=sa;Password=ABC123 Important information for your DBA about setting up the external data source for this connection type is provided in the following section entitled “Setting up the SQL External database”.

For Native web service data sources, this will usually be provided by the programmer who will create the local SOAP compliant web service that matches our schema. Important information for your programmer about setting up for use of this local web service is provided in the following section entitled “Setting up for web service access”.

Type – there are currently two types of Lookup supported – SQL and Native web service. It is possible that other types may be required for other database types – customers should contact Altarama if they need other types of Lookups.

It’s important to note that you can definitely be pulling data from multiple data sources, regardless if it’s multiple SQL servers or native web services, or any combination therein. In each page within the Dynamic Lookups Module, in the top right-hand corner of the screen, you’ll notice a drop-down menu that shows you which datasource you’re reviewing:

While your viewing/editing of the different datasources needs to be done in separate windows, all of the DLM definitions from all datasources are available within the lookup of an individual form. This allows you to pull data from multiple data sources and display it in a form – for example, if you receive your client data from one data provider, and non-client data from another. You can use data from both datasources in one form – the Edit Lookups mode of a form will provide appropriate options from all relevant datasources:

However, you cannot use data from one datasource to populate the form with data from a second, different datasource.

Exercise

Your RefTracker Dynamic lookups module may have been supplied with an example data source so that you have some working examples.

Appendix 1 provides information about the layout of the Xeno example data source (and SQL database).

The screen print above shows the entry in the Datasources code table required to access the Xeno database, if it is included in your RefTracker system.

What are the data sources that you need to provide Lookups to?

How do you set up them up for access by RefTracker? What is expected at your external data source’s end?

The next section provides detailed instructions about what is required to access your external data sources both from the access perspective and from the perspective of the data that will be provided by the external data source.