OHDSI Home | Forums | Wiki | Github

WEBAPI sql server data source addition failure

Implementers
#1

We are starting the journey with a broadsea container on Azure, and are having problems connecting to the cdm implementation on Sql Server.
-The sql server driver is in the container root directory
-connection string tested successfully in other db IDE’s, but when added to the source table in the Broadsea postgres, the new source is not returned from the sources API or showing in the Atlas webapp.

Other than running the ddl scripts generated by webapi and adding the source_daemon lines per the installation, what is needed to get new data sources to show in Atlas?

Any tips appreciated
Holt Oliver

#2

This is cached and can be a source of problems: after inserting the data, can you restart your WebAPI service? After that, the sources from the service should be up to date.

#3

Source refreshed on cache worked. Thank you

#4

We did get sources to display in Atlas; however the Broadsea returns an application initiation error when we try to use it. Tried connecting to a DB with the ddl executed but without data with no success

Since it is a sql server , Just to confirm

  1. are there implicit requirements for data being in cdm/vocabulary tables for the application to connect
    2)Where JDBC driver should be stored, documentations indicated the root folder of the container git repo, but there are also connection jars in the HADES container and we want to follow best practice for specifing the driver
  2. Any configs other than connection strings that need to occur for it to be recognized to connect an MS SQL (some documentation indicates editing the xml config files in the WebAPI, but we are using the Broadsea default, so haven’t been touching those
t