SIP2 Manager after version 6.0 upgrade
When the program is first run after upgrading, it will display a form which populates the Master Message and Message Field tables.
It will also allow optional conversion of existing DIY parameter sets to the new table structure.
After completion there will an entry in the UPDATE_LOG Table in the LIB database for each process. The example below shows the creation of the master messages, conversion of parameter set 1 as a 3M device and parameter set 2 as an Envisionware device.
| PROCESS_ID | PROCESS_NAME | AMLIB_VERSION | DATE_STARTED | DATE_COMPLETED | STATUS | EXTRA_DATA |
|---|---|---|---|---|---|---|
|
266 |
DIYParamsToSIP2-MasterMessages |
6.0 |
2011-06-14 |
2011-06-14 |
S |
NULL |
|
267 |
DIYParamsToSIP2-1-3M |
6.0 |
2011-06-14 |
2011-06-14 |
S |
NULL |
|
268 |
DIYParamsToSIP2-2-EnvisionWare |
6.0 |
2011-06-14 |
2011-06-14 |
S |
NULL |
The parameters are stored in tables in the Local database – the tables and their created using the Amlib Changes upgrade script for this this specific version installed.
The SIP2 Server uses settings in the AmlibConfig.xml file maintained by the Amlib Configuration Manager
The SIP2 Subsystem must be defined before any activity can be done. Existing Amlib DIY configurations can be converted for the updated SIP2 Facility. See separate Notes on Conversion.
External Support Files
To facilitate the conversion process and setting up of specific vendors, external xml files contain default data. These files are:
DIYParametersConversion.xml – Holds parameter data from the existing DIY parameters relevant to SIP2 plus additional fields required for the new setup.
VendorsConversion.xml – Holds SIP2 message and field defaults for the currently supported vendors in DIY – 3M, EnvisionWare, STILogitrack, TalkingTech, SmartLibrary, Overdrive and Wheelers
DIYVendorDIYType.xml – Defines which parameters in the DIYParametersConversion.xml are relevant to the vendors in VendorsConversion.xml