Deployment

Q: Can Blaise 5 interface with our current systems using out current Blaise 4 (individual BDB) approach?

With some custom programming and data conversion this is possible.

Q: Can you run more than one version of Blaise 5 software in production (on the same device)?

No.

Q: Can you use Blaise in a Cloud?

Yes.

Q: Do we need to shut down Blaise Services if we want to upgrade our survey during production? What would be the consequences of this?

No, but you might Deactivate the survey, and wait until there are no active sessions anymore.

Q: Does the Blaise 5 API have to be registered before using it on a computer/device without Blaise 5 installed?

Some dll's have to be registered, but not all.

Q: Is it possible to install and run Blaise 5 in a Virtual Desktop Environment (VDI)?

Yes, but you cannot get to shared locations from there.

Q: What Blaise 5 software is required on (stand-alone) interviewer devices (Manipula, DEP, Server Manager, DLL dependencies, etc.)?

You will need the .exe file of the programs and a few dll's (System.Data.SQLite.dll and msvcr100.dll). Notice that there a separate 32-bit and 64-bit versions of the dll's, and you'll have to ship the right ones to the disconnected device.

Q: What happens if a server crashes?

All data up to the last server contact will be stored in the Session Database. The Audit Trail saves information every couple of seconds, so minimal amounts of data will be lost in most cases. All cases that were already completed or saved in between are stored in the ‘real’ database (.bdbx).

Q: What is the difference between connected and disconnected surveys? How is data stored?

Connected is Client-Server based, disconnected is Thick-Client (locally on the device). Data is stored on the Data Server. Depending on the run mode, it will be sent there continually (connected) or when you connect and choose upload (disconnected).

Gaining deeper understanding