Technical information

i!-ConnectLinx

RMS NetLinx Programmer’s Guide

be retrieved by using LEVEL_EVENTs and DATA_EVENTs in your program and

must be saved. Then, when an action request is triggered via a BUTTON_EVENT,

you can retrieve these argument values and use them (as appropriate) for the

action to be executed.

Each argument is provided an ID at the time it is added. The ID’s start at one and

are numbered sequentially to each argument as they are added. When

i!-ConnectLinx posts the argument value, it supplies the ID number as well. For

numbers and levels, this ID is the level number to which the argument is posted.

For strings and enumerations, this ID is included in the string that posts the

argument value.

For an example, see the i!-ConnectLinxStandardFunctionShell.axi file.

Action Persistence and Distribution

i!-ConnectLinx stores the supported actions in a XML file called

i!-ConnectLinx.xml located in the doc:\user\connectlinx directory. All action

information is stored in this file. i!-ConnectLinx compatible technologies retrieve

this file directly from the NetLinx Master.

It may not always be practical to keep all the i!-ConnectLinx action list files on

the NetLinx Master. For instance, in a corporate environment with 20 NetLinx

Masters in various conference rooms, a user outside the company needs to have

direct access to each NetLinx Master through the firewall in order to download

the files. Additionally, each NetLinx Master needs it’s own DNS entry, so users

do not have to remember an IP Address.

To simplify action list management, i!-ConnectLinx compatibly technologies

support an action list index file format. This index file lists the names of various

files and a URL where the file can be retrieved. This allows you to move all the

action list files from the NetLinx Masters to a web server for easy retrieval. Place

this index file in a directory called connectlinx off the root directory of the web

server and name it i!-ConnectLinx.xml. However, it can contain links to any

URL with any file name in any folder.

In the above example, the IT department might collect all the action list files and

place them in the connectlinx directory of the company’s web server. Each file

should be renamed to reflect the room that the action list is for. Then a web

developer should edit the supplied i!-ConnectLinxList.xml file to reflect the