KMS, KMS-M2M Support

email: KMS@VisionX-online.com


Skip to end of metadata
Go to start of metadata

Client machines

Hardware

  • SCC-WA4,WA57 with Ethernet-card

    The Ethernet interface card is not included in the standard version, please order this separately from your appliance supplier.

  • SCCwe with Ethernet (standard)
  • connect directly to the TCP/IP network with Ethernet (RJ45) or with Powerlink-Device or with Wireless-Bridge or with GPRS/UMTS-Router


IP-Configuration over the user interface of the machine

Settings must be conform to the local network structure!

  • Device-IP
  • Netmask
  • Gateway-IP

M2M-Configuration with a pendrive

  • Enabled
  • ProxyServer (option for platform=internet, default is empty)
  • ProxyUser (option for platform=internet, default is empty)
  • ProxyPassword (option for platform=internet, default is empty)
  • M2M-Proxy (domain name or IP from the M2M proxy server, default is the M2M proxy server from Provicon "m2mproxy.net" )
  • DNS1, DNS2 server

Infrastructure

  • Platform = Internet (Ethernet connection to the Internet => like "laptop browse google")
    • Connect to the KMS-M2M Server over Internet gateway and DNS-Server
    • OR connect to the KMS-M2M Server over Internet gateway and PROXY-Server
  • Platform = Intranet
    • Connect to the KMS-M2M Server over the local Network (LAN)

back to the top

KMS-M2M server

Architecture

  • KMS-M2M server is a Java based server application executed in a Tomcat application container
  • The application background database is a PostgreSQL database server
  • The user interface is HTML/Javascript based (Java/JSF, PrimeFaces component set)
  • The communication between the client physical machines and the M2M server is a http request based API
  • The communication between the client KMS application and the M2M server is a http request based API
  • The communication between the external applications and the M2M server is a http/REST based API

KMS-M2M server as a virtual machine

  • The Guest Opsys is Redhat Enterprise Linux 5. All packages needed for the M2M server application are installed (including the M2M application itself)
  • KMS-M2M server is deployed in a VMware OVA format image
  • The OVA image can be used on VMware ESX hosts or with VMware (Workstation, Player) or VirtualBox on a Windows host
  • The virtual machine's default configuration is to get IP address from a DHCP server (setup can be changed as described below)
  • The guest system is configured to use 1 CPU, 1 GB RAM and 80 GB disk. The disk is dynamic - it grows physically as used up
  • Default virtual machine setup is 1GB RAM and 1 processor. This setup is proper for evaluation purpose only. The RAM should be changed to 4GB before any real business usage.

Running KMS-M2M server in VMware workstation or VMware player

  • Starting a virtual machine with default settings all of the available network adapters on the host machine will be assigned to the guest virtual machine. This situation can prevent the proper network connection.

Assign only the physical network adapter to the virtual machine

Before you start the virtual machine at first, time please be sure that only the physical network adapter is assigned to the virtual machine

  • Click Configure Adapters

  • Select the physical network adapter only

How to setup static IP address for the virtual machine (using X GUI)

  • If there is no DHCP service in the network or static IP must be set, the default configuration must be changed on the virtual machine
  • Start the virtual machine
  • Login to the virtual machine as root
  • Type startx to start the X terminal interface
  • Goto System -> Administration -> Network


  • Select eth0 device
  • Edit >  Statically set IP addresses


  • Set IP address > Ok > Activate

 

How to setup static IP address for the virtual machine (config files)

  • The end user should configure the network configuration of the guest opsys, so that it is reachable from the local area network.
  • The network configuration (setting IP address and default gateway) of the guest is done by editing the following configuration files

 

Remote access to the M2M server

  • For support purpose remote access to the M2M server should be setup
  • There should be a windows workstation in the LAN, from which the guest is reachable. This windows box should have an ssh client (eg. Putty) installed.
  • This windows host should be reachable from the Internet through RDP (remote desktop protocol) in a secure way (e.g. VPN, TeamViewer, GotoMeeting)
  • The windows host should reach the guest on TCP ports 22,80 and 443

External storage

  • For backup purposes the guest system should have some kind of external storage mounted. The file system may be nfs or cifs and should be mounted to the /external folder on the guest
  • Content of the /opt/m2m direcory has to be moved to the mounted directory
  • The /opt/m2m direcory must be deleted
  • New directory has to be symLinked with name m2m in the opt directory.

System backup

  • The backup function operates automatically, using directory \opt\m2m\backup
  • Time of backup can be preselected, using cron configuration "crontab".
    • Daily backup operates every day,  in /opt/m2m/backup/daily\SubDir. (SubDir is the number of the weekday),
    • Weekly backup operates every Monday, in /opt/m2m/backup/weekly/SubDir. (Value of SubDir can be 1/2/3/4, this represents the age of backup, 1 is the latest, 4 is the earliest backup in rotating system (during the new backup, earlier backup directorys will be aged 1->2, 2->3, 3->4, 4-> will be deleted),
    • Monthly backup operates at the first day of the month, in /opt/m2m/backup/monthly/SubDir. (SubDir is the number of the month),
    • Yearly backup operates at the first day of the year, in /opt/m2m/backup/yearly/SubDir. (SubDir is the number of the year),

Reach GUI - supported browser

  • KMS-M2M server GUI is browser based. Please see the list of supported browser versions below
  • IE7+
  • FF12+
  • Chrome19+
  • JavaScript execution must be enabled

Deploying new M2M server version

  • Scroll down to the bottom of the page (War file to deploy)

  • Press select file and choose the war file to deploy
  • Press Deploy button
  • After a successful deploy the previous version can be stopped and undeployed

back to the top

 

Links to other pages:

 

 

  • No labels