N4A Services Check List

Application Note

EWS0300CL002 Version:2.00

03 January, 2012

General
TERMS OF USE OF NEW MATERIALS - PLEASE READ CAREFULLY From time to time, Enfora, in its sole discretion, may make available for download on its website (www.enfora.com), or may transmit via mail or email, updates or upgrades to, or new releases of, the firmware, software or documentation for its products (collectively, 'New Materials'). Use of such New Materials is subject to the terms and conditions set forth below, and may be subject to additional terms and conditions as set forth in Enfora's Technical Support Policy (posted on its website) and/or any written agreement between the user and Enfora. All New Materials are provided AS IS. Enfora makes no warranty or representation with respect to the merchantability, suitability, functionality, accuracy or completeness of any such New Materials. The user of such New Materials assumes all risk (known or unknown) of such use. Enfora reserves all rights in such New Materials. The user shall have only a revocable and limited license to use such New Materials in connection with the products for which they are intended. Distribution or modification of any New Materials without Enfora's consent is strictly prohibited. IN NO EVENT WILL ENFORA BE RESPONSIBLE FOR ANY INCIDENTAL, INDIRECT, CONSEQUENTIAL OR SPECIAL DAMAGES AS A RESULT OF THE USE OF ANY NEW MATERIALS. ENFORA'S MAXIMUM LIABILITY FOR ANY CLAIM BASED ON THE NEW MATERIALS SHALL NOT EXCEED FIFTY U.S. DOLLARS ($50).

- ii -

Copyright
2012 Enfora, Inc. All rights reserved. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording or otherwise), or for any purpose, without the express written permission of Enfora, Inc. Enfora and the Enfora logo are either registered trademarks or trademarks of Enfora, Inc. in the United States. 251 Renner Pkwy Richardson, TX 75080 USA Phone: (972) 633-4400 Fax: (972) 633-4444 Email: [email protected] www.enfora.com

- iii -

Table of Contents
1 Pre-Installation Checklists 1.1 Document Purpose 1.2 Customer Information 1.3 Device Checklists 1.4 Device Use Case 1.5 SIM Checklists 1.6 Application Server Hardware 1.6.1 Application Server Hardware Checklist 1.6.2 Network 1.6.3 Application Server Third Party Software Checklist 1.6.4 Application Server FOTARequirements (Optional) 1.7 Database Server Hardware Checklist 1.7.1 Hardware 1.7.2 Network 1.7.3 Third Party Software 1.8 Database Checklist 1.8.1 n4a (CMS) Database 1.9 Network / Firewall Checklist 1.10 Pre-Installation Connectivity Test Checklist 1.10.1 Intranet Tests 1.10.2 Internet Tests 2 Post-Installation Checklists 2.1 CMS 2.2 Provisioner 3 Customer Confidential Checklist 3.1 Application Server - iv 1 1 2 2 3 3 3 3 4 4 4 5 5 5 5 6 6 6 7 7 7 8 8 8 9 9

3.2 Database Server

-v-

1 Pre-Installation Checklists
1.1 Document Purpose
This document is intended to assist customers with the necessary configurations for setting up n4a Services in a production environment. Please fill out and return this document to your Enfora FAE contact person before the Enfora product installation. The information gathered in this document will be used by Enfora personnel as reference for working with Enfora FAEs and support personnel. Please return Section 1 to your Enfora FAE contact person support personnel or your Enfora Field Account Engineer (FAE) before conducting the installation and keep a copy of this document handy in the case that you need to contact Enfora for technical support. It is recommended that you consult Enfora support or an Enfora Field Account Engineer for specific recommendations of device, architecture or server specifications based upon your environment, device volume, IT considerations, and specific business use case. The detailed installation of the n4a Software is described in the n4a Installation Guide. A summary of the installation process is outlined below. 1. 2. 3. 4. 5. 6. 7. 8. Examine the server and application requirements in this document and the n4a installation Guide. Create and configure the application and database servers. Complete the Customer confidential checklists. Install and configure the database application. Create n4a database(s). Create n4a database userid, password and permissions. Test the n4a database access. Install and configure all third party required software on the application server. a. JAVA JDK 1.6+download and installation. b. JBOSS 5.10.GA download and installation. c. FTP configuration (optional for FOTA). Configure your firewall for use with the system. Perform pre-installation tests and complete checklist. Complete and return the checklists in Section 1 of this document to Enfora. Enfora will provide the n4a Installer and appropriate licenses. Install n4a Services. Install n4a License. Perform post-installation tests and complete checklists in section.

9. 10. 11. 12. 13. 14. 15.

-1-

1.2 Customer Information

<Customer Name> <Customer Address and Phone> Customer Contact Information Customer Business contact Customer Technical contact Enfora Sales Contact Enfora FAE Other Name Email Phone

1.3 Device Checklists

This information will indicate if custom tables and CMS configuration will need to be created in the n4a Database. Enfora personnel will assist you in completing this information.
Device Types Enabler IIIG (GSM0308) Enabler IIIG-BGA (GSM0408) Spider AT (GSM5108) SpiderAT 3000 (GSM5218-00FFA) Spider AT3010 (GSM5218-00FFB) Spider AT 4000 (GSM5218-02) Spider MT Gi (GSM2354/GSM2356) Spider MT Gu (GSM2338) Spider MT Gu (GSM2358) Spider MT Gu (GSM2368) Spider MT Gu (GSM2438) Spider MT 1000 (GSM2404) Spider MT 2500 (GSM2418) Spider MT 3000 (GSM237x) Spider MT 4000 (GSM2448) Mini MT (GSM2228) SA-G+ (GSM1318) Other Y/N Number of Devices Firmware Version

-2-

1.4 Device Use Case

Please write a short summary of how the devices will be used. What is tracked, how often does the device need to report in, and under what circumstances the device needs to report in (triggering events). This will help Enfora to develop the correct configurations and determine if the use case is within scope of the customer requirements.
Device Type Spider AT (example) Asset Type Generator Triggered event and reporting scheduled Once a day while stationary Every 5 minutes while in motion Use case description We recover heavy construction equipment when stolen

1.5 SIM Checklists

This information will assist Enfora in determining if device setting changes may be required.
SIM SIM type1 Other Provider APN Name Activated (Y/N) Valid Data Plan? (Y/N)

1.6 Application Server Hardware

With consultation from Enfora, the application and database server may run on a single server.

1.6.1 Application Server Hardware Checklist

Hardware Requirements Number of CPUs CPU Processor Speed (GHZ) Total RAM (GB) Disk space (GB) Operating System Recommended 2 quad core 2 GHz + 16 GB 150 Windows Server 2008 Linux Red Hat Enterprise 6.X (only) Actual

-3-

1.6.2 Network
Network External DNS Name Internal DNS Name External IP Address Internal IP Address Connection Type (RDP,SSH, Putty, VPN) Recommended n/a n/a n/a n/a If external access is given to Enfora personnel Actual

1.6.3 Application Server Third Party Software Checklist

Software Requirements JAVA JAVA Installation Directory Linux- /opt/java JAVA_HOME system environment variable set JAVA_HOME content Linux - /opt/JAVA PATH system environment variable includes %JAVA_HOME%\bin; JBOSS JBOSS Installation Directory Linux - /opt/jboss JBOSS Installation Directory Linux- /opt/java Are other applications running on this server? None Windows C:\ Yes 5.1.0 GA (only) Windows C:\JBOSS Yes Windows- C:\JAVA Recommended JAVA JDK 1.6 or above Windows C:\JAVA Actual

1.6.4 Application Server FOTARequirements (Optional)

The FOTA server may reside on any server. It is not required to be on the Enfora application server.
FOTA Pre-requisites FTP supporting Active Mode (Windows) Any FTP server supporting active mode FTP (Linux) FTP root directory FTP Userid FTP password FOTA diff (.bin) files (provided by Enfora and based upon your current device firmware versions Recommended IIS with FTP server Apache FTP server n/a n/a n/a * Enfora will assist you with this information Actual

-4-

1.7 Database Server Hardware Checklist

The database may run on the same server as the n4a application for low volume production and test systems. Contact Enfora FAEs or Enfora support for specific recommendations.

1.7.1 Hardware
Hardware Requirements Number of CPUs CPU Processor Speed (GHZ) Total RAM (GB) Disk space (GB) Operating System Recommended 2 quad core 2GHz + 12 to 16 GB 150 Windows Server 2008 Linux Red Hat Enterprise 6.X (only) Actual

1.7.2 Network
Network External DNS Name Internal DNS Name External IP Address Internal IP Address Connection Type (RDP,SSH, Putty, VPN) Recommended n/a n/a n/a n/a If external access is given to Enfora personnel Actual

1.7.3 Third Party Software

Software Pre-requisites Database Recommended MS SQL Server 2008 MySQL 5.X Enterprise MySQL 5.X Community JAVA JDK 1.6+ JBOSS 5.1.0 GA only Actual

-5-

1.8 Database Checklist

1.8.1 n4a (CMS) Database
Setting CMS Database Name (created before install) CMS Database User Name CMS Database User Password CMS User Name DB access rights CMS Initial Database Size CMS Database Port Recommended / Default Company_CMS CMS_Login planet DB Owner, Read, Write, Create, Access 500 MB (min) 1433 (MS SQL Server 2008) 3306 (MySQL) Host (Database Server IP Address) Can CMS user log into database via MS SQL Server Manager or My SQL Query Browser * DB Tables created during installation n/a Yes Actual

1.9 Network / Firewall Checklist

Setting Firewall IP Network Pipe Bandwidth between Application server and Database server Provisioner Port If application to be accessed outside firewall n4a CMS Port If application to be accessed outside firewall ActiveMQ Management Web Console Device UDP Ports. Required for device communication MS SQL Server System Access MySQL 5.x System Access ActiveMQ System Access SSH, Putty Port if required FTP (for FOTA) Recommended / Default n/a 100MB to I GB TCP 8087 TCP 8085 TCP 8161 (optional) UDP 1720 1721 (required) TCP 1433 (optional) TCP 3306 (optional) TCP 61616 (required) TCP 22 (optional) TCP 21 (optional) Actual

-6-

1.10 Pre-Installation Connectivity Test Checklist

1.10.1 Intranet Tests
Inside Network Tests Application Server to Database Server (if multi-server) Ping by Internal IP? Application Server to Database Connect to Database on Specified Port? Test Ping by Internal DNS? Results

1.10.2 Internet Tests

Outside Network Tests Application Server Ping External IP? FTP on Port 21 (optional)? Device packet test. UDP Test on port 1720 or 1721 Connect to Server? Test Ping External DNS Name? Results

-7-

2 Post-Installation Checklists
2.1 CMS
Test the connectivity of CMS after installation.
CMS CMS UI available? Able to login to CMS? License applied to CMS and valid? Device data appears in CMS? Device Probe data is populated? Test http://<CMS dns or_IP>:8085/gw Login as root/root System -> View License Home Page and Device Report CMS device report. IMEI and IMSI fields populated? Results

2.2 Provisioner
Test the connectivity of Provisioner after installation.
Provisioner Provisioner UI available? Able to login to Provisioner? License applied to Provisioner and valid? Provisioner connection to Gateway? Upload of Device Configuration Utility provisioning log into device group? Able to Provision device? Test http://<provisioner dns or_IP>/:8087/pv Login as root/root System -> View License System -> System settings Device Inventory Deployment Results

-8-

3 Customer Confidential Checklist

3.1 Application Server
Accessibility Administrative Userid Administrative password Recommended n/a n/a Actual

3.2 Database Server

Accessibility Administrative Userid Administrative password Recommended n/a n/a Actual

-9-