Automatic import

<< Click to display Table of Contents >>

Navigation:  Alarm > Location Manager > Setting up the Location Manager >

Automatic import

With the Alert Location Manager you have the possibility to import your organizations, alert units and devices automatically. An automatic import can be used if you maintain certain .csv files and do not want to carry out this maintenance effort on the interface of the Alert Location Manager.

 

For an automatic import please proceed as follows:

 

To enable it, store the files you want to use for the automatic import in the installation directory under ".../best_web/etc/asm/".

If this folder does not exist, you can easily create it.

 

In the following the individual files that you can use to import the corresponding data records via automatic import will be listed and explained.

 

Importing devices

 

The file for the import of devices has to be named index.csv.

 

The structure of the file can be as follows:

 

 

"oid";"uid";"room";"name";"description";"type"

 

oid

The ID of the organization which the device is assigned to.

uid

The ID of the alert unit which the device is assigned to.

room

Room in which the device is located.

name

The name of the device / user.

description

The description of the device.

type

The type of device. Here the following values are given: fat, thin and user.

 

 

Example

 

"name";"description";"oid";"room";"type";"uid"

"cwlaptop01";"Device description";"1234567";"Main Floor Room 01";"fat";"123"

"cwlaptop05";"Device description";"1234568";"Main Floor Room 12";"fat";"456"

"cwlaptop03";"Device description";"1234567";"Main Floor Room 03";"thin";"123"

"cwlaptop02";"Device description";"1234567";"Main Floor Room 02";"fat";"123"

"john.doe";"Device description";"1234569";"Main Floor Room 03";"user";"789"

 

 

Note

 

If the OID/UID does not exist or match, an error will be logged and the import is terminated. No new organizations or alert units can be created using the import for devices.

 

Importing organizations and alert units

 

The file for the import of organizations and alert units has to be named organization.csv.

 

The structure of the file can be as follows:

 

 

"oid";"uid";"organization";"organization_desc";"type";"unit";"unit_desc";"additional";"zipcode";"town";"active"

 

oid

Organization ID

uid

Alert unit ID

organization

name of the organization

organization_desc

description of the organization

type

Type of organization

unit

name of the alert unit

unit_desc

description of the alert unit

additional

Additional address regarding the alert unit

zipcode

ZIP-code of the alert unit

town

Name of the town of the alert unit

active

Is this organization active (true) or inactive (false)?

 

 

Example

 

"oid";"uid";"organization";"organization_desc";"type";"unit";"unit_desc";"additional";"zipcode";"town";"active"

"1234567";"123";"Example Company";"Example Company description";"Ltd.";"Example Street 1";"Example Street description";"Branch Example City";"80335";"Munich";"true"

"1234568";"456";"Example Name";"Example Company description";"PLC";"Example Street 2";"Example Street description";"Branch Example City";"80335";"Munich";"false"

"1234569";"789";"Example City";"Example Company description";"Ltd.";"Example Street 3";"Example Street description";"Branch Example City";"80335";"Munich";"true"

 

 

Note

 

If several alert units / organizations / postal codes with the same UID are entered, only the first data record will be imported.

 

Importing alert circles

 

The file for the import of alert circles has to be named relation.csv.

 

The structure of the file can be as follows:

 

 

"from_organization";"from_unit";"to_organization";"to_unit"

 

from_organization

ID of the organization that triggers the alert.

from_unit

ID of the alert unit of the organization that triggers the alert.

to_organization

ID of the organization that is the recipient of the alert.

to_unit

ID of the alert unit of the organization that is the recipient of the alert.

 

 

Example

 

"from_organization";"from_unit";"to_organization";"to_unit"

"1234569";"789";"1234568";"456"

"1234567";"123";"1234568";"456"

"1234568";"456";"1234567";"123"

"1234568";"456";"1234569";"789"

 

 

Note

 

If the OID/UID does not exist or match, an error will be logged and the import is terminated. No new organizations or alert units can be created using the import for relations.

 

Infoserver configuration settings for the automatic import:

 

The following configuration options are available and have to be entered in the [asm] section of the Infoserver.ini. You can also set these settings via the serverboard.

 

txt_autoimport_delete_db=

Default: false

 

txt_autoimport_delete_db=true will cause the following:

Cleans all data provided by the last import in the Alert Location Manager before the import to ensure that only the latest data is available.

txt_autoimport_delete_files=

Default: false

 

txt_autoimport_delete_files=true will cause the following:

The .csv files used for the import are deleted from the directory after the import.