ioxclient package generated tar not working in kinetic application issue

[pammula@cisco.com]

As part of one requirement i have created the package.tar file using the ioxclient in windows and uploaded the same tar in Kinetic application and deployed the application in to a respective gateway

But once the application deployed in the Gateway the application is not working as expected and facing the 2 different issues as follows,

1. “Invalid Archive file:Invalid Archive file: Mandatory metadata section is missing : app.apptype”

Please let me know am I doing any mistake while creating the tar file.

Steps followed to create tar as follows,

Ø  Downloaded “iotsp-device-sdk-java-master” from Devnet.

Ø  Built the application using the “gradlew clean build”.

Ø  Copied the .tar file from lib folder to IOxClient package.

Ø  Prepared the tar file using the “ioxclient package IOxPackage/“ command.

2. Showing application status as stopped instead of running and if I check in WatchDog.log file , it showing the message as  follows ,

          "App 2373_CS_FOG_APPLICATION_44687 Completed with exit code 2"

          "Stopping the container"

Please let me know how can I build the working copy of the application through ioxclient ? Your help really helpful to me.

P.S:- I am using the java 1.8 version

[Emmanuel Tychon]

Which gateway are you using? 

When referring to "Kinetic application", are you talking about the Gateway Management Module (GMM) at ciscokinetic.io?

Can you check or publish here the content of your package.yaml file before running the ioxclient command? This file looks like this and contains important information for your container that will be read by IOx and GMM:

https://github.com/CiscoDevNet/iox-app-template/blob/master/docker-python/package.yaml

Thanks,

Emmanuel

[pammula@cisco.com]

Hello Emmanuel,
Please find my yaml file as follows,
descriptor-schema-version: "2.0"

info:
name: CS_FOG_APPLICATION1
description: "IOx Java PaaS style Application for Rule Engine on Edge functionality with Batching and Compression Capabilities"
version: "1.0"
author-link: "http://www.cisco.com"
author-name: "Cisco Systems"

app:
# Indicate app type (vm, paas, lxc etc.,)
type: paas

resources:
profile: c1.large
cpu: 600
memory: 256
network:
-
interface-name: eth0
ports:
tcp:
- 8883

startup:
runtime: java-se-embedded-cp3
runtime-version: 1.8
runtime-options:
classpath: "$CAF_APP_PATH/"
target: launch.sh