Reference13r1:Concept App Platform

General

• V13 uses buildroot
• this is an own (innovaphone) collection of packages
• For further information see: Buildroot Documentations

Requirements

• V13 or up
• Gateway (arm): IPx10 (with CF card) or IPx11 (with mSATA SSD)
• Virtual (x86_64): HyperV or VMWare

Default credentials

• SSH-Login with admin and ipapps
• root login with root and iplinux (root login is not directly possible over SSH)
• web login pwd

App Platform - arm (Gateway)

• The installation image has a size of ~50MB. During installation, the following partitions are created:
  • /dev/sda1 fat32: 200MB (contains ramdisk, rootfs and kernel)
  • /dev/sda2 ext4: depends on disk size (contains databases, log files and apps)
  • /dev/sda3 ext4: 500MB (contains the rootfs)
  • /dev/sda4 swap: 512MB

App Platform - x86-64 (Virtual Machine)

• The default disk size is 16GB. It should be increased before the first start if needed!

• Multiple CPUs are supported, default is one CPU

• default RAM: 512MB
• static IP address, DNS, Gateway can be configured with the command setip on the console. Run setip --help to get a list of parameters. (Example: setip --addr=x.x.x.x --mask=x.x.x.x --gateway=x.x.x.x --dns1==x.x.x.x)
• If you have permission problems change to su user (Password is iplinux or your new admin password)
• To figure out your ip address you can use the command: ip address on the console.
• loadkeys de can be used to change to german keyboard layout (etc.)

• partitions:
  • /dev/sda1 ext2: 350MB (contains ramdisk, rootfs and kernel)
  • /dev/sda2 ext4: depends on disk size (contains databases, log files and apps)
  • /dev/sda3 ext4: 500MB (contains the rootfs)
  • /dev/sda4 swap: 512MB

Installation

ARM Gateway

If you setup a Gateway with the install procedure, the App Platform is installed automatically (Https Download has to be allowed and shouldn't be blocked by any firewall.)

You can also install it manually:

• Open App Platform -> General and Enable Linux Support. Restart the gateway.
• You need to enable Proxy-ARP on ETH0 or ETH1, so your Gateway and the Linux Appliance will share the same physical interface.
• Open App Platform -> IP and configure the IP settings of the App Platform. Restart the Gateway.
• Open App Platform -> Installation and select the given version or enter an own path to the app-platform-armel.img image file.
• The installation runs without any further required step.

Virtual machine

• Import the image into your server environment.
• Edit the disk size, if needed.
• Start the machine and wait until it reboots and starts again.

Backup of the Apps

Each App Service can have multiple instances and each instance has its own database. The manager app itself also has its own database.
There are no other files which need to be backuped.
The standard way to backup the databases is through the Devices App Reference13r1:Concept_App_Service_Devices#Backups.

An alternate way is to use a command file which is similar to the command files from the firmware.

Commands

• times 0,12 # backup only at 0 or 12 o'clock
• backup-instances http://user:pw@ip/path/#I-#D.dump PUT
  • PUT and POST are supported, all instances including the manager itself are saved
• backup-instance http://user:pw@ip/path/#I-#D.dump apidemo example.com PUT
  • backup a single instance with instance name and instance domain
• backup-manager http://user:pw@ip/path/#I-#D.dump

Hash parameters

• #L App Platform label (neu), e.g. 10024
• #A App label (neu), e.g. 130004
• #I instance name (neu), e.g. reporting1
• #D instance domain (neu), e.g. innovaphone.com
• #m MAC address of the LAP, e.g. 00ab11eeff
• #d Current date and time (plain UTC without daylight saving and timezone adjustments) 20051010-170130
• #bn rolling backup index
• ## escapes a hash mark

How-Tos

Resizing the disk of a Virtual machine

• stop the VM
• expand the disk using your VM utilities
• start the VM and boot from the first boot entry rescue/setup
• login with root and iplinux
• call /home/root/install_step1.sh log.txt resize
• the VM reboots automatically after a successful resize