During the installation process, code is installed both on the U2 server as well as one or multiple work stations.
Note: Unix servers also require an Easysoft SQLServerODBC driver and setup (www.easysoft.com). We recommend using TTK Solutions (email@example.com) for the installation of that driver. While it can be purchased and installed by a customer directly, we find it is most successful if the installation is done per the recommendation.
The customer will need to define/answer questions about the name of the SQL server, where is it on the network, and what name to use for the new SQL databases. On the U2 side, the questions concern what account will be used to install the object code and triggers. Here is a listing of the object code or files that are updated:
|U2 File||U2 Records|
|*||BCI.PL||Contains BCI paragraphs - LOAD.BCI.ACTION, LOAD.BCI.OBJECTS, NovoMotion NOVO.GEN.SCHEMA, EXCHANGE, SHOW.BCI.EVENTS|
|*||BCI.BP||Contains BCI programs - only object code is installed|
|VOC||VOC pointers for each of the new functions|
|*||BCI.SCREENS||Contains new screens for the new paragraphs|
|*||BCI.REPORT.SOURCE||Contains new report|
|FUNCTION.MASTER||Contains new function master records needed to support the new paragraphs|
|*||BCI.EVENT.LOG||Used to store communication info - new dictionaries are delivered for this file|
|*||BCI.SCHEMA||Used to store the created schemas- new dictionaries are delivered for this file|
|*||BCI.ACTION||Used to capture records to process - new dictionaries are delivered for this file|
|*||BCI.QUARANTINE||Used to store action records that fail - new dictionaries are delivered for this file|
|FILE_DESC||Records needed to support the new files|
|*||BCI_INCLUDE||Contains common code blocks used by the new programs|
|*||EXCHANGE_DISTRIBUTION||Used by EXCHANGE - new dictionaries are delivered for this file|
|*||BCI.HELP||delivered with no data - new dictionaries are delivered for this file|
|*||NOVOG.BP||Contains new trigger creation programs|
|INDEX.CTL||new BCI.INTERFACE record|
|*||NOVO.CTL||new control file - also new dictionaries to support it|
|*||NOVO.SCRATCH||delivered with no data - new dictionaries are delivered for this file|
* Denotes a new Manage 2000 file.
On the SQL server, the interface and schema VB components need to be installed. This is done through an install script that puts the following items on any client (usually the SQL server):
This includes the componentry for the the NovoMotion Schema Editor and the NovoMotion Interface Control. There is a setup.exe that executes a standard InstallShield installation wizard and installs both of these applications. The setup.exe program is installed in the BCI folder of the installation PC.