Installing the OATedge Edge Controllersupport.oatsystems.com/training/oat70_docs/7.1/Edge... · 2010. 2. 16. · OATedge Controller . Installation Guide . Version 7.1 OATSystems,

OATedge Controller Installation Guide

Version 7.1 OATSystems, Inc. January 2010 Document Number: OATedge_Controller_IG_7.1

i

Copyright © 2010 OATSystems Inc. All Rights Reserved.

This document contains proprietary information that is owned by OATSystems. Copying or reproduction of any material either in part or full from this document to any other location for further reproduction or redistribution is expressly prohibited. Any reproduction or redistribution of the files not in accordance with the terms of the License Statement is a violation of copyright law.

OAT and Senseware are registered trademarks of OATSystems, Inc.

Java and all Java‐based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. OATSystems is independent of Sun Microsystems, Inc.

IBM is a registered trademark of International Business Machines Corporation.

Linux is a registered trademark of Linus Torvalds.

MicroStrategy 8, MicroStrategy Intelligence Server, MicroStrategy Web Universal, and MicroStrategy Desktop are registered trademarks or trademarks of MicroStrategy Incorporated.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates.

Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trade names and trademarks are the property of their respective owners.

OATSystems makes no warranties, express or implied, with regards to its products in this document.

Support Information

You can contact the OAT Support Center (OSC) for technical support at OATSystems, Inc. 309 Waverley Oaks Road, Suite 306 Waltham, MA 02452 USA

Phone: 877‐OAT‐SUPPORT or 781‐907‐6081 Fax: 781‐907‐6098 Email: [email protected] Web site: https://support.oatsystems.com

https://support.oatsystems.com/

iii

CONTENTS INTRODUCTION .......................................................................................................... 1

Features................................................................................................................ 1

Specifications ......................................................................................................... 1

Arcom Zeus ......................................................................................................... 1

Linux Device ........................................................................................................ 2

PRE-INSTALLATION REQUIREMENTS ................................................................................ 2

INSTALLATION OF EDGE CONTROLLER ............................................................................. 3

Installation using User Interface ................................................................................... 3

OATxpress Information for This Install Session................................................................ 5

Edge Controller-Specific Information ........................................................................... 6

Installation using Command Line .................................................................................. 8

OATEDGE SETUP VERIFICATION .................................................................................... 11

Installation Verification ............................................................................................ 12

Status Verification .................................................................................................. 12

Hardware Verification .............................................................................................. 13

Upgrading OATedge on Arcom Zeus .............................................................................. 15

ADDING EDGE CONTROLLER TO OATXPRESS ..................................................................... 15

ACCESSING ADMINISTRATION PAGE ................................................................................ 16

The Edge Controller Properties ................................................................................... 17

General ............................................................................................................. 18

Log Settings ........................................................................................................ 19

Deployed Scenarios ................................................................................................. 20

View Logs ............................................................................................................. 20

Installing the OATedge Controller

Introduction This guide describes the installation of OATedge Controller software on both the Arcom Zeus and Linux device. Installation can be done using the command line or the user interface.

Features The Arcom Zeus and Linux device are supported target platforms for Edge Controller installations. The features of Arcom Zeus and Linux device are as follows:

• Arcom Zeus is a single‐board computer, based on Intelʹs 520 MHz processor. For Edge Controller usage, it is typically deployed in an Industrial Compact Enclosure (ICE) configuration, outfitted with 64MB flash memory, and at least 128MB RAM. For more information, see http://www.arcom.com/pxa270‐xscale‐zeus.htm

Arcom Zeus can be provisioned for Digital IO. The Arcom AIM‐104/Relay‐8 device provides opto‐isolated circuitry for controlling up to 8 on‐off output points (for example, lights), and processing changes in the state of up to 8 input signals (for example,. switches or sensors). These device features are frequently used for control and provide feedback on deployed RFID solutions.

• Linux device as Edge Controller is deployed with the standard Linux configuration. Linux device has no provision for Digital IO, though external Digital IO device can be added to the Linux device.

Specifications The required specifications in Arcom Zeus and Linux device for the use of Edge Controller are as follows:

Arcom Zeus

Hardware specifications:

• CPU: Intel PXA270 RISC‐based processor, 520 MHz

• RAM: 128 MB (specific application requirements may raise this to 256MB)

• Permanent Storage: 64 MB flash memory for file system

• Other: One AIM Relay8 Digital IO device integrated

• Typical: cabling for light stack and input sensors or switches

http://www.arcom.com/pxa270-xscale-zeus.htm


Software platform specifications:

• Arcom Embedded Linux (AEL). Latest rev. is “2.6.16.28‐arcom2‐1‐zeus #7”

• IBM J9 JRE rev. IVE 2.3 with jclMax J2ME profile (installed in /opt/wece6.1)

• Additional jars required (in /opt/wece6.1/lib/jclMax/ext):

o dom.jar, jaxp‐api.jar, sax.jar, xercesImpl.jar (JAXP 1.3.2 jars from java.net)

o aim104.jar (from Arcom)

Patches are separately available from OAT Systems.

Linux Device

Hardware specifications:

• Standard Linux Hardware Configuration.

Software platform specifications:

• Linux device

o Redhat Linux 4.0 AS and ES

o Linux Core 2.6

• Sun JDK 1.6

Pre-installation Requirements Ensure that the following information is available before installation of either Arcom Zeus or Linux device:

• An Edge ID for the new Edge Controller.

NOTE: The new Edge ID should be unique among your network of OAT servers and Edge Controllers. If an Edge Controller configuration does not already exist for this Edge ID in the OATxpress server database, then it will be necessary to first create this configuration using the OAT Enterprise Administrator Web UI (or the OATxpress server Web UI).

• The IP address of the OATxpress server to which this Edge Controller is being assigned.

• The port number for the web application on the OATxpress server.

• The IP address for the edge controller hardware, whether already configured on the Arcom Zeus/ Linux device, or assigned for configuration during this setup.

• The root or superuser account password on the Arcom Zeus/Linux device.

• If the network has not been setup on the Arcom Zeus, then a null‐modem serial cable and terminal emulation software is needed for initial access to the Arcom Zeus and Linux environment for network setup. In the case of Linux device, the network configuration can be setup by logging in to the device directly.

2 Installation Guide

Ensure the date and time in Edge Controller is set same as the server in which OFS is running. To set the date and Time in Edge Controller, in the command prompt type for example:

date 11181527.00

Where the date is set to ʺWed Nov 18 15:27:00 IST 2010ʺ using the format ʺMMDDhhmm[[CC]YY][.ss]ʺ

NOTE: The rest of this document assumes that a usable network configuration has already been established for the Arcom Zeus/ Linux device and Linux platform. These instructions are also available through OATSystems support.

Installation of Edge Controller Installation of Edge Controller can be done on Arcom Zeus and Linux device in one of following ways:

• Installation using the User Interface

• Installation using the Command Line

Installation using User Interface Steps to install OATedge using the User Interface are as follows:

1. Navigate to the OATxpress server to access the OAT Foundation Suite OATxpress.

NOTE: It is also possible to obtain an Edge Controller installation page through the OAT Enterprise Administrator User Interface, if available. For more information, refer to the OATenterprise User Guide.

2. Enter a valid username and password with administrative privileges. Click Log In to display the Configuration page.

OATedge Controller 3


3. Click Edge Controllers icon for a list of Edge Controllers.

4. Click Install Edge Controllers link to display the Install Edge Controllers page.


5. Fill in the required details in the text fields. Those marked with an asterisk are mandatory fields.

OATxpress Information for This Install Session

Parameter Description

IP Address Enter the IP address of the OATxpress server to which the Edge Controller(s) is being installed in this session.

NOTE: When installing Edge Controllers from the OAT Enterprise Administrator User Interface, the IP address should be of the OATxpress server specifically assigned for this set of Edge Controllers and not the IP address of OAT Enterprise Administrator server.

Port number Enter the port number for the Web application on the OATxpress server to which the Edge Controller(s) installed will be assigned.

Server Port for Bridge/ Messaging System Enter the port number of the messaging communication system running on the OATxpress server. It allows communication between Edge Controllers and the OATxpress server.

Default Server Port for Bridge/Messaging System is 1884 for Arcom Zeus, and for Linux device it is 61616



Edge Controller-Specific Information


Edge ID Enter a unique numeric identifier of 4 or 5 digit number for the new Edge Controlle, for example, 0001

IP Address Enter the IP address of the Edge Controller host.

Platform Select Arcom or Linux.

Login ID Enter “root”‐ for the Arcom platform.

Enter an appropriate login ID ‐ for a generic Linux installation.

Password Enter the password.

Local Port for Bridge/ Messaging System Enter the port number of the messaging communication system running on the OATxpress servert allows communication between the Edge Controller and OATxpress server. For Arcom Zeus it is 1884 and for Linux device it is 61616.

Device Agent Model Select one of the following Device Kits to install:

• ArcomDio

• None

NOTE: Choose “Arcom Dio”to install on an Arcom Zeus specifically set up with the Arcom AIM‐104 Relay‐8 Digital IO device.

Device Kit is an Open Source project hosted by Eclipse.org, which provides a software framework for integrating RFID devices into OSGi‐based RFID software applications and frameworks such as the OAT Edge Controller.

NOTE: This parameter is not applicable for Linux device installations.

Copy Location Enter the temporary storage location on the Arcom Zeus or Linux device where the installer archive is copied before extraction and installation. The default is /tmp.



Install Location (optional) Enter the location where OATedge Controller files are installed on the target platform.

NOTE: This is set internally to “/opt” for Arcom Zeus, and the same directory as Copy Location for Linux device if left empty.

Binary Version (optional) Select from the dropdown list of installable image versions.

6. Click Add to display the following screen:



7. Click Install for the following screen.

On completion of installation, the Result column displays if the installation was a success or failure.

Installation using Command Line The Arcom Zeus and Linux device has an “sshd” service available when it is running Linux as the operating system. You can use SSH (Secure Shell) client utilities to copy files onto the device, as well as to obtain a command interpreter shell on the device. Available SSH clients for Windows include:

• PuTTY (http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html)

• A Cygwin‐based SSH client (http://pigtail.net/LRP/printsrv/cygwin‐ssh.html and http://www.udel.edu/topics/connect/sw/exceed/docs/cygwin.html offer instructions on how to install the SSH client utilities).

Steps to install OATedge using the command‐line are as follows:

1. Copy the installer archive oatNano_Arcom.tar.gz to a temporary folder on the Arcom Zeus device. The screen displays the use of the scp utility to copy the installer archive from a folder on a Windows system to the /tmp folder on the Arcom Zeus device.

NOTE: For Linux device copy the installer archive oatNano_Linux_AMQ.tar.gz to a temporary folder on the Linux device. The scp (secure copy) utility is a part of the SSH client utilities.

If you are using PuTTY, the secure copy utility is named pscp.exe.


http://www.chiark.greenend.org.uk/%7Esgtatham/putty/download.html

http://pigtail.net/LRP/printsrv/cygwin-ssh.html

http://www.udel.edu/topics/connect/sw/exceed/docs/cygwin.html

NOTE: The screenshot uses a Cygwin SSH client on a Windows system.

Open a command interpreter shell as root (the superuser) on the Arcom Zeus/ Linux device, using the SSH client. (Substitute 172.17.0.172 with the actual IP address of your Arcom Zeus/

3. the password for the root user. Enter the valid password to get a Linux device.

ry in which the installer archive is copied:

contents of the installer archive:

contents of the installer archive:

tar –zxvf oatNano_Linux_AMQ.tar.gz

ew sub‐directory called oatInstall. This contains e files required for installation.

6. Change your working directory to the newly reated oatInstall directory:

2.

Linux device on your network).

ssh [email protected]

You will be prompted to enter root shell on the Arcom Zeus/

4. Change your working directory to the directo

cd /tmp

5. Extract the

tar –zxvf oatNano_Arcom.tar.gz

NOTE: In case of Linux Device, extract the

Extracting the contents of the archive creates a nth

c

cd oatInstall




7. , the following installation script:

MB_LOCAL_PORT} -Ms ${MB_SERVER_PORT} ${OATedge_ID} ${SITESERVER_IP} ${SITESERVER_PORT}

e

N

ading “./” is required, to specify that the install.sh file in the current directory is to be executed.

Arcom Digital IO devic Arcom Zeus platform,

. For Arcom Digital IO continue with

Arcom Zeus specifically set up with the Arcom AIM‐104 Relay‐8 Digital IO hardware and drivers, enter the parameter as:

h –c none 1000 172.17.0.214 7777

The installer will install the Edge Controller files onto the file system.

To install OATedge

./install.sh -c ${DISK_AGENT_TYPE} -Ml ${

Ensure that you choose a different port for the OATedge if OATxpress is installed on the samachine. This would create port conflict. m

OTE:

• The le

• The –c parameter (DISK_AGENT_TYPE) allows you to choose whether to set up a Device Kit profile for the e, which works on the

• • <MB_LOCAL_PORT> is the message broker local port. • <MB_SERVER_PORT> is the message broker OATxpress port. • <OATedge ID> is the OAT Arcom Zeus and Linux device

the steps listed below.

8. If you are installing on an

‐c arcomdio you can also explicitly select the default configuration ‐c none

For example:

./install.s

When the installation is complete, the installer displays a message.

NOTE: To verify the success of your installation, you can check the contents of the /opt folder. It should now contain a new oat sub‐directory, which contains the files required to run the Edge Controller.

9. Since the Arcom Zeus device has limited storage, after a successful installation remove the temporary files created during installation.

cd /tmp

NOTE: Not required if using Linux device.

ice Configuration User Interface (this configuration

sh y have been done): cd /opt/oat/osgi

U o (on the Zeus), or the editor built into WinSCP3, to edit the file DeviceAgentConfig.xml.

Arcom Digital IO device has to be set up either during installation, or later by using the setup.sh command.

11. Replace every occurrence of the text GPIO_DEV_NAME (or the previous device name, if this is a

12.

command to verify that the library pre‐requisites for Arcom Digital

sh command to verify that the hardware is set up correctly.

the nd‐line installation procedure

rm -rf oat*

10. Edit the file /opt/oat/osgi/DeviceAgentConfig.xml to set the actual device name.

Edit this file, and replace the initial placeholder value GPIO_DEV_NAME with the actual devname given to the device in the OATxpress ould alread

se either vi or nan

NOTE: Edge Controller to be used with the

rename) with the actual name given to this device. There are 15 occurrences in this file.

Perform the following platform verification steps:

• Use the test_profile.sh IO are present.

• After testing the library pre‐requisites, use the test_relays.

See “Hardware Verification” for more information about setup.sh and the other utility commands mentioned in this section.

OATedge Setup Verification After opening a superuser (root) command interpreter shell on the device (using SSH as described at beginning of the comma ), perform the following tasks:

• Installation Verification • Status Verification • Hardware Verification



Installation Verification


Verify the contents of the file in the folder. If certain settings were

e e

e e

edge.premises.port

EdgeConfig.xml /opt/oat/osginot supplied during the installation procedure, or were incorrectly specified, you can edit this file to correct the settings. The critical settings to verify are:

dg .id

dg .premises.ip

Status Verification You can control the Edge Controller service or check its status by issuing the following commands:

Command Action

cd /opt/oat/osgi Starts the Edge Controller software (starts the OSGi runtime).

Though OSGi runs in the background, log output is still provided to the console used to issue this command.

./oatedge start

cd /opt/oat/osgi Stops the Edge Controller (stops OSGi). ./oatedge stop

cd /opt/oat/osgi

./oatedge restart Restarts the Edge Controller (stops, then restarts OSGi)

cd /opt/oat/osgi

./oatedge isrunning

Prints a message telling you if the service is running.

cd /opt/oat/osgi

./oatedge enableautorun

Enables autorun, which means the Edge Controller will be started as a background process, automatically, when the platform is rebooted.

cd /opt/oat/osgi

./oatedge disableautorun

Disables autorun, so that on subsequent platform reboots the be started OAT Edge Controller software will not automatically

as a background process.

cd /opt/oat/osgi

./oatedge testautorun

Prints an indication of whether autorun is enabled or disabled.

Hardware Verification Several tools are provided for validating the configuration of the Edge Controller platform, and, in

are integrated wntroller application. These tools are described below:

particular, to test hardw ith the Arcom Digital IO drivers, before attempting to use the drivers in the running Edge Co

Command Action

cd /opt/oat/bin

./test_profile.sh

Tests if the JVM and libraries profile are correctly set up. A successful test should produce output like the following:

is the installed profile. Testing

s...

--OK

‐104.jar the Edge

are.

root@zeus2 bin# ./test_profile.sh

J9 v2.3 in expected location: /opt/wece6.1/bin/j9 --OK

jclMax profile...

Success!!!

Checking for additional installed component

aim-104 jar is correctly installed

root@zeus2 bin#

NOTE: This test performs a rudimentary check on the aimfile, necessary for using the Arcom Digital IO device withController softw

This feature is not available for the Linux device.

cd /opt/oat/bin

./test_relays.sh

at the re for Arcom Digital IO is correctly set up, after

,

tus line like “Relay status = 0x1” is printed.

h, the script th a

Tests if the Arcom Digital IO is correctly set up (to test thhardware and softwaverifying the presence of the aim‐104.jar file using the JVM test above). When the test starts, watch the output hardware (light stackdiodes, etc.), each of which should flash in turn. As each output point is flashed, a sta

After all output points have been flashed once eaccontinuously reads from inputs until the script is terminated wiCtrl‐C keypress. If an input pin is triggered during this time, the displayed value changes, indicating that the state change has been ʺseen.ʺ A correct test should produce output like the following:

root@zeus2 bin# ./test_relays.sh

Starting Relay8 Test...........

Relay status = 0x1

Relay status = 0x2

Relay status = 0x4

Relay status = 0x8

Relay status = 0x10



Command Action Relay status = 0x20

Relay status = 0x40

Relay status = 0x80

Inputs(0x180) = 0x2 [Pin 1 high]

Motion detected, Pin 1 goes

[Ctrl-C pressed here]

Relay8 Linux driver (exercised by this ) by

. The test script repeatedly samples the input pins by reading a byte from this e hex values, representing the aggregate

bjectʹs

Inputs(0x180) = 0x2

Inputs(0x180) = 0x2

Inputs(0x180) = 0x2

Inputs(0x180) = 0x0 [low]

Inputs(0x180) = 0x0

Inputs(0x180) = 0x0

Inputs(0x180) = 0x0

Inputs(0x180) = 0x0

Inputs(0x180) = 0x0

Inputs(0x180) = 0x2 [Pin 1 goes high again]

Inputs(0x180) = 0x2

Inputs(0x180) = 0x2

Inputs(0x180) = 0x2

At the level of the AIM‐104/test), the input (and output) pin settings are read (or written toperforming binary I/O directly on the character‐based file /dev/arcom/aim104/relay8/0instantaneous values of the file. The values displayed arsettings of all 8 input pins.

The example shows 1 motion sensor on Pin 1, which is wired to be high by default (i.e. in its untriggered state the connection is closed),and transition to low (connection open) when sensing an opresence:

NOTE: This is not supported for Linux.

cd /opt/oat/osgi

./setup.sh <CONFIG>

e one specified by <CONFIG>. Available

s is not supported for Linux.

Switches configuration to thchoices are “none” or “arcomdio.” Edits to the properties files applicable to the current configuration is preserved, so they can be re‐used later if necessary.

NOTE: Thi


Upgrading OATedge on Arcom Zeus To u m Zeus from pre‐MICHIGAN release follow the steps listed below:

• s b

/opt/oat/osgi/configura

/opt/oat/osgi/DeviceAge

/opt/oat/osgi/EdgeConfig.properties

• lation using User Interface or Installation using

up files to their original location except for

le and update the following parameters from the

Ad

Fill in the required details in the text fields. Those marked with an asterisk are mandatory fields.

pgrde OATedge on Arco

Backup the following file efore upgrading:

tion/config.ini

ntConfig.xml

/opt/oat/osgi/savant.properties

/opt/oat/osgi/startosgi

Follow the Arcom Zeus installation. Refer to InstalCommand Line for details.

• After successful installation, restore all the backed/opt/oat/osgi/startosgi.

• Edit the new /opt/oat/osgi/startosgi fibackup startosgi file: o LOCAL_PORT o REMOTE_PORT

ding Edge Controller to OATxpress The following screen displays a sample Add/Edit Edge Controller Page:




Edge Controller Name Name given to the OATedge installation.

IP Address IP address of the Arcom Zeus/ Linux device.

Port Number HTTP port number of the Edge Controller on the Arcom Zeus/ Linux device.

Server that Controller connected to Edge Controller ID on OATxpress.

Edge Controller ID ID of the Edge used in the OATedge installation.

Accessing Administration Page There are two ways to access the Administration page for an Edge Controller:

NOTE: The identity of the user is the same on Edge Controller as the OATxpress server.

to the Edge Controller Admini terface.

ame and password must be ler and the Edge controller va ress.

The scre

Enter a Username and Password valid for OATxpress server to successfully log in. The Edge Controllerʹs Administration page is displayed, as shown below:

• Navigate to the Edge Controller from the OATxpress server.

• Log in directly stration User In

NOTE: The usernLogin User Interface,

independently entered in the Edge Controllidates the login credentials with the OATxp

enshot above displays the login screen for the Edge Controllerʹs User Interface.


Options in the Administration page are explained in the following pages:

The Edge Controller Properties

Configuration of the General and Log Settings of Edge Control Properties are as follows:

The following screen displays a sample of the Edge Controller Properties page.




General

The basic Edge Controller properties can be maintained through the Web Admin user interface, if necessary.


OATedgeID Enter a numeric identifier for this Edge Controller. This id should match the one created in the installation and add edge controller step

Server IP address or host name Enter the IP address of OATxpress server to which the Edge Controller is assigned.

Server Port Number Enter the port number for the web application on the OATxpress server to which this Edge Controller is assigned.

Enable Auto Start Select Yes ‐ for the Edge Controller software to be started automatically when the host platform is powered on or rebooted.

Enable EPC Forwarding Select Yes – for RFID tags inventoried by any reader device that is assigned to this Edge Controller, to be forwarded and logged in the OATxpress server database.

Restart Now Click this button to initiate restart of the Edge

NOTE: This does not reboot the Linux platform.

Controller software. This causes the OSGiruntime to be restarted.

NOTE: It may be necessary to restart the Edge Controller for the following reasons if you have:

anged the Edge ID for the controller.

Assigned the Edge Controller to a different

Changed the device configuration for the Ed sing the OATxpress server User Interface).

Deployed a new device to the edge controlle

Downloaded a new or updated custom component onto the Edge Controller (for example, rimitives or User Interface compo

Ch

OATxpress server.

ge Controller (u

r.

scenario p nents, or a device support bundle).

L

The Edge Controller can be configured to forward log enoffline access. Each Edge Controller gets a separate log fi with a name such as:

ofs/log/edges/edge.<edgeid

NOTE: <edgeid> is the Edge ID of the respective Edge C file.

On the OATxpress server, the log4j settings can be modiController log files, and the maximum size to which eac

T s section on the Edge Controller Propert

og Settings

tries to the OATxpress server, for storage and le on the OATxpress server,

ontroller whose log output is stored in that

fied to control the maximum number of Edge h file can grow.

he Log Setting ies page has the following settings:


Console Logging Threshold severity level of log entries to be posted to a

Edge Controller (typically ignored, since the Edge Controller will be running as a background

platform).

Select from the dropdown list, the threshold

console window, if one is in use for this

process on the host

Buffer old Select from the dropdown list, the threshold severity level of log retained in the memory,

ular logging buffer.

Logging Thresh

circ

Buffer to be retained in memory, in a circular buffer. This is the number of entries that can be paged through using the online log viewer, or downloaded to a file from the Logging User Interface..

Size Enter the maximum number of log entries

Forwarder Logging Threshold Select from the dropdown list, the threshold severity level of log messages to be forwarded to the server (if log message forwarding is not disabled).

Disable log message forwarding Deselect this box to forward the log messages to OATxpress server for logging to a file. This can impact the performance, especially if there are many Edge Controllers associated with a given OATxpress server.

Selected as default ‐ to disable forwarding.




enarios

View Logs The Edge Controllerʹs internal logging buffer displays thControllers. The logs can be refreshed to get the latest in buffer is a downloaded for offline vi d Messages.

Deployed ScThe screen below displays the lists of deployed scenario processes on the Edge Controller:

e efficiency and responsiveness of Edge formation. The internal logging

vailable online, which can beisplays a sample of the Log

ewing, support purposes etc. The screen below


the OAT Edge Controller. For more assistance, please refer to the OAT This completes installation forInstallation and Configuration Guide or contact OAT Support at [email protected] OAT‐SUPPORT.

or at 1‐877‐

Documents

Installing the OATedge Edge Controllersupport.oatsystems.com/training/oat70_docs/7.1/Edge... · 2010. 2. 16. · OATedge Controller . Installation Guide . Version 7.1 OATSystems,