Admin Console User Guide

Kony MobileFabricTM
Integration Service
Admin Console User Guide

On-Premises
Release 6.5
Document Relevance and Accuracy
This document is considered relevant to the Release stated on this title page and the document version stated on the Revision History page.
Remember to always view and download the latest document version relevant to the software release you are using.
© 2015 by Kony, Inc. All rights reserved 1 of 5

Kony MobileFabric Integration Service Admin Console User Guide
Version 2.0
Copyright © 2014 Kony, Inc.
All rights reserved.
July, 2015
This document contains information proprietary to Kony, Inc., is bound by the Kony license
agreements and may not be used except in the context of understanding the use and methods of Kony
Inc, software without prior, express, written permission. Kony, Empowering Everywhere, Kony
MobileFabric, Kony Modeler,and Kony Visualizer are trademarks of Kony, Inc. Microsoft, the Microsoft
logo, Internet Explorer, Windows, and Windows Vista are registered trademarks of Microsoft
Corporation. Apple, the Apple logo, iTunes, iPhone, iPad, OS X, Objective-C, Safari, Apple Pay,
Apple Watch and Xcode are trademarks or registered trademarks of Apple, Inc. Google, the Google
logo, Android, and the Android logo are registered trademarks of Google, Inc. Chrome is a trademark
of Google, Inc. BlackBerry, PlayBook, Research in Motion, and RIM are registered trademarks of
BlackBerry. All other terms, trademarks, or service marks mentioned in this document have been
capitalized and are to be considered the property of their respective owners.

Version 2.0
Revision History
Date Document Description of

Version Modifications/Release
07/14/2015 2.0 In the document, appended a

section Configuring Log Files.
Rebranded Kony Server as Kony
MobileFabric Integration Service
for 6.5 release.
12/11/2014 1.0 Updated for release 6.0

Version 2.0
Table of Contents
1. Preface 1
1.1 Purpose 2
1.2 Intended Audience 2
1.3 Formatting Conventions 2
1.4 Contact Us 4
2. Launching Admin Console 5
3. Kony Studio Applications 6
3.1 View the list of services 6
3.2 Deleting an Application 6
4. Using Basic Reports 8
5. Using Legacy Reports 10
6. Using Custom Metrics 12
6.1 Prerequisites 12
6.2 Defining Custom Metrics in Kony MobileFabric Integration Service Admin Console 13
6.3 Rules for Custom Metrics Data Types 15
7. Configuring Report Settings 17
7.1 Report Display Settings 17
7.2 Report MetaData Mapping 19
7.3 Form MetaData Mapping 19
8. Managing User Access 21

Version 2.0
8.1 Adding a New User 21
8.2 Editing User Information 22
8.3 Changing the Password 23
8.4 Deleting an User 24
9. View the Configuration of the Admin Console 26
10. Configuring Log Files 27

1. Preface Kony MobileFabric Integration Service Admin Console User Guide
Version 2.0
1. Preface
Kony MobileFabric Integration Service App Services portal allows you to generate application reports,
delete an application and application's services, and configure settings.
You can select an application's services and delete them from the Kony MobileFabric Integration
Service Admin Console portal.
Kony MobileFabric Integration Service
The existing on-premises Kony MobileFabric Integration Service supports the feature of outputting a
message to a JMS queue for each service request. Kony provides a log deamon Java process that will
read from that JMS queue and insert the data into the Kony MobileFabric Integration Service
database. A customer can query this data directly or use a reporting.war file provided by Kony
that connects to this data and provides a visual representation of the data.
One key feature added for Kony Cloud analytics is a client side library that resides in the app binary
that manages the sessionID of the application. It contains the business logic to generate a sessionID
and rotate that sessionID if the app is closed or if the app is idle for more than thirty minutes.
Another key feature added for Kony Cloud analytics is a client side API to set the Kony User ID. This
value is then set to the Kony MobileFabric Integration Service and associated to the session. This
enabled the Kony Cloud analytics to also accurately track unique users based on userID defined by
the developer. This enables extremely accurate user tracking for apps running on the Kony Cloud that
aligns with your business definition and charging definition of app users.
Kony MobileFabric Sync

Version 2.0
The existing on-premise Kony MobileFabric Sync server does not output analytics to a JMS queue.
Instead, it maintains its own database and exposes usage reports within the Kony MobileFabric Sync
Console.
With cloud enabled for Kony MobileFabric Sync, a new capability is added to output a message to a
JMS queue on every request and to output a daily summary email of current Kony MobileFabric Sync
usage that included the number of apps, users and devices being serviced. These messages are only
generated when Kony MobileFabric Sync is running in the Kony Cloud.
It is not in currently in scope to support the Kony MobileFabric Sync metrics created for Kony Cloud in
an on-premise configuration at this time. However, the on-premise metrics database design should
consider this future requirement.
1.1 Purpose
This document explains the terms and concepts in the Kony MobileFabric Integration Service Admin
Console and also provides procedural information to perform various tasks in the Kony Studio.
1.2 Intended Audience
This document is targeted at developers who will use the IDE to write and develop applications.
1.3 Formatting Conventions
The following are the formatting conventions used throughout the document:

Version 2.0
Conventions Explanation
Monospace l User input text, system prompts, and

responses
l File path
l Commands
l Program code
l File names.
Italic l Emphasis
l Names of books and documents
l New terminology.
Bold l Windows
l Menus
l Buttons
l Icons
l Fields
l Tabs
l Folders.
URL Active link to a URL.
Provides helpful hints or additional information.

Note:
Highlights actions or information that might cause

Important:
problems to systems or data.

Version 2.0
1.4 Contact Us
We welcome your feedback on our documentation. Write to us at techpubs@konylabs.com. For

technical questions, suggestions, comments or to report problems on Kony's product line, contact
itssupport@konylabs.com.

2. Launching Admin Con- Kony MobileFabric Integration Service Admin Console User
sole Guide
Version 2.0
2. Launching Admin Console
To launch the admin console, enter the URL in the browser and press Enter. The following page
appears.
URL: http://<hostname>:<port>/admin
For example: http://10.10.1.105:9090/admin

3. Kony Studio Applic- Kony MobileFabric Integration Service Admin Console User
ations Guide
Version 2.0
3. Kony Studio Applications
The Kony Studio Apps page displays apps deployed to the server. Services associated with the
application are also displayed.
3.1 View the list of services
You can view the list of services associated to the application.
3.2 Deleting an Application
You can delete an application from the Kony Studio Apps page.
To delete an application's service, follow these steps:
1. Go to Kony MobileFabric Integration Service Admin Console.
2. Select an app from the Apps page.
3. Click Delete. A confirmation message appears.

3. Kony Studio Applic- Kony MobileFabric Integration Service Admin Console User
ations Guide
Version 2.0
4. Click OK. The application is deleted.

4. Using Basic Reports Kony MobileFabric Integration Service Admin Console User Guide
Version 2.0
4. Using Basic Reports
After the application is deployed, you can view the following statistics of an app:
1. App Usage: The intent of this report is to display app usage in used sessions and in users. The
users are based on the developer using the setKonyUserID() method. If the setKonyUserID()
method is not used, then the report should count unique deviceIDs and consider each unique
device as a unique user.
2. Requests per Service: This report shows the total requests to each serviceID associated with
the application.
3. Requests per Form: This report shows the total requests to each form in the application
4. Sessions per Device: The Sessions per Device report provides the total sessions categorized
by Platform, Channel and App Type.
5. Service Duration: View the total number of calls per application service including the min,
average and max time taken.
6. Service Duration Detail: View average service call duration as a stacked bar showing the time
taken for each phase of the service call.
Along with these type of reports, you can also generate the following legacy reports on the new data.
1. Traffic Report Service Requests (Native/SPA): Traffic reports are generated separately for
each platform, by selecting the appropriate platform from the drop-down.
2. Traffic Report Visitors (Native/SPA): Traffic reports are generated separately for each
platform, by selecting the appropriate platform from the drop-down.
3. Device Summary Report (Thinclient): This legacy report shows page views per thinclient
platform with date aggregation modes day, week, and month.
4. Traffic Report –TC- Page Views: Traffic reports are generated separately for each platform, by
selecting the appropriate platform from the drop-down.

4. Using Basic Reports Kony MobileFabric Integration Service Admin Console User Guide
Version 2.0
5. Traffic Report – TC - Visitors: Traffic reports are generated separately for each platform, by
To generate a basic report, follow these steps:
1. Select a report type from the Report list.
2. Set the date range (Start Date and End Date) for which the report is to be generated.
3. Select the application name from Application list. A list of applications deployed are available in
this list.
4. Select the platform from the Platform list. The report is will be generated for this platform.
5. Select the channel from the Channel list. The report will be generated for this specific channel.
6. Select the application type from the Application Type list. The available values include Hybrid,
Mixed Mode, Mobile Web, Native, and SPA.
7. Select the aggregation of the report from the Aggregation list. The report will be generated with
the selected aggregation. The available values include Day, Month, and Week.
8. Click Generate. The report will be generated.

5. Using Legacy Reports Kony MobileFabric Integration Service Admin Console User Guide
Version 2.0
5. Using Legacy Reports
The legacy reports tab will point to legacy data source and you can generate reports on them.
Note: Ensure that you have configured a JNDI entry for kony.legacy.db to access the
legacy reports database. Legacy Reports are only needed if you have upgraded from a 5.x Kony
MobileFabric Integration Service instance and need to run reports on data captured before the 6.x
upgrade.
You can generate the following legacy reports in Kony MobileFabric Integration Service Admin
Console portal:
1. Traffic Report Service Requests (Native/SPA): Traffic reports are generated separately for
each platform, by selecting the appropriate platform from the drop-down.
2. Traffic Report Visitors (Native/SPA): Traffic reports are generated separately for each
platform, by selecting the appropriate platform from the drop-down.
3. Device Summary Report (Thinclient): This legacy report shows page views per thinclient
platform with date aggregation modes day, week, and month.
4. Traffic Report –TC- Page Views: Traffic reports are generated separately for each platform, by
5. Traffic Report – TC - Visitors: Traffic reports are generated separately for each platform, by

5. Using Legacy Reports Kony MobileFabric Integration Service Admin Console User Guide
Version 2.0
To generate a legacy report, follow these steps:
1. Select a report type from the Report list.
2. Select the application name from Application list. A list of applications deployed are available in
this list.
3. Set the report period of the legacy report.
4. Select the platform from the Platform list. The report is will be generated for this platform.
5. Select the channel from the Channel list. The report will be generated for this specific channel.
6. Set the date range (Start Date and End Date) for which the report is to be generated.
7. Select the application type from the Application Type list. The available values include Hybrid,
Mixed Mode, Mobile Web, Native, and SPA.
8. Click Generate. The report will be generated.
After you generate the report, a Download as CSV option will be available to download
the report as a CSV file.

6. Using Custom Metrics Kony MobileFabric Integration Service Admin Console User Guide
Version 2.0
6. Using Custom Metrics
Custom metrics is a feature of Kony MobileFabric Integration Service Admin Console that enables an
application developer to capture custom data from an application and build reports using the data. In
addition to reports, the application developer also receives access to a set of standard metrics that are
gathered from the application like the platform channel to use in building custom reports. This feature
is available to any application deployed to Kony MobileFabric Integration Service.
The Kony MobileFabric Integration Service Admin Console enables a user to define custom metrics.
Administrator can view Custom Metrics under Reports tab:
l Custom Metrics - enables users to add or delete metrics that they intend to send from the
application. The Custom Metrics page shows a list of applications deployed to Kony
MobileFabric Integration Service. If a user deploys an application to Kony MobileFabric
Integration Service, it appears in the Custom Metrics page.
6.1 Prerequisites
Following are the prerequisites for creating custom metrics:
1. An application deployed to Kony MobileFabric Integration Service.

Version 2.0
6.2 Defining Custom Metrics in Kony MobileFabric Integration Service

Admin Console
The Custom Metrics page allows an application developer to define the metrics for an application.
Each metric is identified by a key that has to be unique within the application. There are six types of
data: String, Boolean, Long (Integer), Double, Date, and Timestamp. The page shows all applications
deployed to Kony MobileFabric Integration Service. To add custom metric parameters for an
application, under Custom Metrics tab in the Reports section of the application, click on + Add Custom
Metric button.
For applications that already have custom metrics defined, clicking on Add + will show the list of
Parameter Names, Data Type, and Default Aggregation function.
The application can send multiple key-value pairs that will be stored as custom metrics for reporting
purposes. The user must register each key sent by the application and provide the Data Type and
Default Aggregation values.
To create a custom metric, follow these steps:
1. Click Add Custom Metric. The following pane appears.
2. Enter a name in the Name (key) area. Each metric is identified by a key that must to be unique
within the application. The application code must use the same Name for sending data in the
key-value pairs in JSON string . The key is case insensitive.

Version 2.0
3. Select a Data Type from the list. The available values are Long (integer values), Double (values
with decimal points like 12.5), String, and Date.
Note: The data type mentioned here must match the data type sent from the application for
the metric name.
4. Select a Default Aggregation from the list. The Default Aggregation is the cumulative function
you apply to the data while building the application. The available values are Sum, Average,
Highest, Lowest, Count, and Distinct Count. Default Aggregation functions are only applicable
for Long and Double.
5. Click Save. The parameters will be defined and saved under the application name. The custom
metrics defined will be sent to the application to collect data.
6. Click Cancel to cancel adding custom metrics to the application.
To delete a custom metric, follow these steps:
1. Select the custom metric in the application.
2. Click Delete. A warning message appears.

Version 2.0
3. Click Soft Delete or Hard Delete to delete the custom metric.
Note: Data from an application with a key corresponding to a deleted parameter name will not be
saved. Existing reports and ad hoc views already created from the domain that use the deleted
parameter will work. However, creating new ad hoc views from the same domain will have the
underscore _ deleted suffix for the parameter name to denote to the developer building reports
that this is currently a deleted parameter.
6.3 Rules for Custom Metrics Data Types
l Long - Integer values
l Double - Values with decimal point like 450.99
l Boolean - true/false
l String - Any string value, maximum length 500 characters.
l Date - String value denoting date in the format yyyy-mm-dd. Example: "2014-05-01"

Version 2.0
Timestamp - String value denoting timestamp. Valid formats for timestamp are shown below
o yyyy-mm-dd hh:mm:ss --- preferred format
o yyyy-mm-dd hh:mm:ssz
o yyyy-mm-dd hh:mm:ss+hh:mm
o yyyy-mm-dd hh:mm:ss-hh:mm
o z stands for zulu (UTC)
o +hh:mm is positive offset of time from UTC
o -hh:mm is negative offset from UTC.
o Example:
"2014-04-15 13:02:55"
"2014-04-15 13:02:55z"
"2014-04-15 13:02:55+05:30"
"2014-04-15 13:02:55-05:30"
Note: For more information on adding custom metrics to an application, refer Custom Metrics
Documentation.

7. Configuring Report Set- Kony MobileFabric Integration Service Admin Console User
tings Guide
Version 2.0
7. Configuring Report Settings
You can configure the report display settings for the following areas:
1. Report Display Settings: Configure report display settings, application types, channel types,
and time zones.
2. Report MetaData Mapping: Reports can display additional metadata about each service to
enhance the readability of the report. The ServiceID is returned from the data warehouse and
you can specify a service friendly name, an associated menu that is related to that service call
and/or an associated user event name that triggers that service call.
3. Form MetaData Mapping: Reports can display additional metadata about each page or form
within the app to enhance the readability of the report. The FormID is returned from the data
warehouse and you can specify a form friendly name, an associated menu that is related to
viewing that form and/or an associated user event name that triggers that form to load.
7.1 Report Display Settings
Add or remove the platform types, application types, and channel types in the Report Display Settings
area.

tings Guide
Version 2.0
7.1.1 Add or Delete Platform Type
Set the platform type names you require to be displayed in the platform aggregation selection box
while creating a report.
1. To add a platform type, click + Add .
2. To delete a platform type, click Delete .
7.1.2 Add or Delete Application Types
Set the application type strings that you require to be displayed in the platform aggregation selection
box while creating a report.
1. To add a application type, click + Add .
2. To delete a application type, click Delete .
7.1.3 Channel Types
Set the channel type names you require to be displayed in the platform aggregation selection box
while creating a report.
1. To add a channel type, click + Add .
2. To delete a channel type, click Delete .
7.1.4 Time Zone
The time zone offset is used to calculate the delta of the timezone in which the customer wishes to
view the reports from UTC. This will be used in all queries to convert data from UTC to user’s
timezone. Default will be UTC

tings Guide
Version 2.0
7.2 Report MetaData Mapping
Report meta data mapping allows you to add, edit, and delete the meta data mappings.
To add or delete a service meta data mapping, follow these steps:
1. Click Add . A new row appears.
2. Select the application ID from the Application ID list.
3. Type the service ID in the Service ID box.
4. Type a service friendly name in Service Friendly Name box.
5. Type the associate menu in Associate Menu box.
6. Type the associated user event in Associated User Event box.
7. Click Save. The mapping is created.
8. To edit an existing mapping, select the mapping and click Edit.
9. To delete a service meta data mapping, select the mapping and click Delete.
7.3 Form MetaData Mapping
Form meta data mapping allows you to add, edit, and delete the form meta data mappings.

tings Guide
Version 2.0
To add or delete a form meta data mapping, follow these steps:
1. Click Add . A new row appears.
2. Select the application ID from the Application ID list.
3. Type the form ID in the Form ID box.
4. Type a form friendly name in Form Friendly Name box.
5. Type the associate menu in Associate Menu box.
6. Type the associated user event in Associated User Event box.
7. Click Save. The mapping is created.
8. To edit an existing mapping, select the mapping and click Edit.
9. To delete a service meta data mapping, select the mapping and click Delete.

8. Managing User Access Kony MobileFabric Integration Service Admin Console User Guide
Version 2.0
8. Managing User Access
You can manage user access from Settings > Console Users page. You can also add a new user,
edit an existing user, change password of the existing user, and delete the user.
8.1 Adding a New User
To add a new user, follow these steps:

Version 2.0
1. Click Add New User option. The Add New User pop-up appears.
2. Type an user ID in the User ID box.
3. Type a password in the Password box.
4. Retype your password in Confirm Password box.
5. Type your name in the Name box.
6. Type your email in the E-mail box.
7. Choose a role from the Role list. The available roles include Admin, Report Viewer, and
Publisher.
8. Click Add User. The user is created.
8.2 Editing User Information
To edit the information of an existing user, follow these steps:

Version 2.0
1. Click Edit . The Edit User pop-up appears.
2. Modify the details like Name, E-mail, and Role.
Note: You cannot change the User ID.
3. Click Save.
8.3 Changing the Password
To change the password of an existing user, follow these steps:

Version 2.0
1. In the Console Users page, click Change Password for an user.
2. Type the new password in the New Password and Confirm Password boxes.
Note: The default user name for the admin user of MobileFabric is admin, the default
password is admin123.
3. Click Save.
8.4 Deleting an User
To delete an user, follow these steps:
1. Click Delete corresponding to an user. A confirmation dialog appears.

Version 2.0
2. Click Ok. The user is deleted.

9. View the Configuration of the Admin Kony MobileFabric Integration Service Admin Console
Console User Guide
Version 2.0
9. View the Configuration of the Admin Console
You can view the configuration of the admin console. This page shows the basic environment setup.

10. Configuring Log Files Kony MobileFabric Integration Service Admin Console User Guide
Version 2.0
10. Configuring Log Files
Logs can be created for Device and Server from Runtime Configuration tab in Server Console. This
page displays the basic environment setup to view the log files.
These files are used for debugging by capturing the request / response payload in different log files
besides middleware.log.
Log All Device Request/Response
l To log the device request / response payloads, select Enabled from the property value list.
Log All Service Target Request/Response
l To log the server request / response payloads, select Enabled from the property value list.
Note: By default, the property value is set to Disabled.
By enabling these properties, log files are created in Middleware /Logs/Middleware folder.

10. Configuring Log Files Kony MobileFabric Integration Service Admin Console User Guide
Version 2.0
l device-payload.log file displays the download / upload request / response between the
device and Kony MobileFabric Integration Service.
l datasource-payload.log file ays t he download / upload request / response between

Kony MobileFabric Integration Service and back-end.

Version 2.0
Glossary
9 patch background
The 9-Patch images help you to create edges for your images that can be used
based on the orientation mode of the application.
Appservice
Appservice function allows you to launch and deeplink Kony native applications
from any third-party native application and browser application. This feature allows
better integration of Kony applications (all native applications) with other native
and browser based applications.
Composite Service
Composite Service is a combination of two or more services. These services can
be web services, XML services, or Java services. When you create a service as a
combination of services, you can specify the order of execution for the services.
The order can be sequential or concurrent
Deeplink
Deeplink function allows you to configure the link to a specific form/page of an
application, which facilitates navigation to that form directly, bypassing the startup
form/homepage.

Version 2.0
Emulators
An emulator simulates a mobile device on your local machine.
Enterprise Explorer
The Enterprise Explorer enables you to view all the services defined within the
workspace.
FFI
Foreign Function Interface (FFI) is a mechanism that provides support for the
application written in one programming language to use the methods, functions,
and services written in another programming language.
Internationalization
The process of designing or developing an application in such a way that it sup-
ports various languages and regions is known as Internationalization.
Java Service
A service that uses a custom Java connector is a Java service. The Java connector
is a custom Java Class that implements the com.konylab-
s.middleware.common.JavaService interface.
JSON Service
A service that communicates with an external data source using JSON data con-
nector over the HTTP protocol and returns a response in JSON format is known as

Version 2.0
a JSON Service. You must create a service definition file for the JSON services.
KAR
Kony Archive
KBF
Kony Binary Format
Looping Connector
A Looping Connector is a type of service that runs in a loop for the specified num-
ber of times.
Panorama view
Splits the screen into tabs
Perspective
A perspective defines the initial set and layout of views in Eclipse.
Pivot view
Splits the screen and creates panels that can be viewed one at a time
Porting
This feature allows users to copy all the properties of all the widgets within the
application from one platform to one or more platforms without modifying the code
base.

Version 2.0
Postprocessor
Postprocessor is a component invoked after the data is received from the external
data source but before that data is returned to the mobile device. This enables the
developer to include any business logic on the data before sending the response
to the mobile device.
Preprocessor
Preprocessor is a component that is invoked before passing the data to the
external data source. This enables the developer to include any business logic on
the data before forwarding the request to the external data source.
Profiler
The Profiler provides the performance analysis of an application which is
developed using the Kony Studio. It recognizes all Lua method calls and the Kony
API calls as well.
SAP Service
A service that uses a custom SAP connector is a SAP service.
Siebel Service
A Service that enables you to use Business Object and Business Services hosted
on a Siebel Server. You can use the Siebel services and objects to create your
own custom services and objects.
Skins
The skin attributes capture the look and feel of every widget. A widget can have a
different look and feel by applying a different skin to it. Skins are specific to widgets
and also specific to Platforms.

Version 2.0
SPA
A Single Page Application (SPA) represents a special type of the web applic-
ations, in which all the HTML, CSS, and JavaScript files necessary for the applic-
ation are retrieved with a single page load.
Splash screen
Splash Screen is the initial screen that appears when you launch an application.
Themes
KonyOne Studio provides a default theme that has a set of skins defined for all the
widgets within an application. The skins in this theme can be applied to widgets to
get a different look and feel for the widgets.
WebSphereMQ Service
A service that enables you to create configurations to connect to the WebSphere
MQ Server. Using these configurations you can create a service to send and
receive messages from the WebSphere MQ server.
Workspace
Workspace is a folder on the hard drive, which is a central repository of all applic-
ation files. The applications you create in the IDE are saved in the workspace. A
workspace can have any number of applications.
XML Service
A service that communicates with an external data source using an XML data con-
nector over the HTTP protocol is known as an XML Service. You must create a

Version 2.0
service definition file for the XML services.

Admin Console User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Admin Console User Guide

Uploaded by

Copyright:

Available Formats

Kony MobileFabricTM

Admin Console User Guide

© 2015 by Kony, Inc. All rights reserved 1 of 5

Copyright © 2014 Kony, Inc.

All rights reserved.

© 2015 by Kony, Inc. All rights reserved 2 of 5

Date Document Description of

07/14/2015 2.0 In the document, appended a

12/11/2014 1.0 Updated for release 6.0

© 2015 by Kony, Inc. All rights reserved 3 of 5

1.2 Intended Audience 2

1.3 Formatting Conventions 2

2. Launching Admin Console 5

3. Kony Studio Applications 6

3.1 View the list of services 6

3.2 Deleting an Application 6

4. Using Basic Reports 8

5. Using Legacy Reports 10

6. Using Custom Metrics 12

6.3 Rules for Custom Metrics Data Types 15

7. Configuring Report Settings 17

7.1 Report Display Settings 17

7.2 Report MetaData Mapping 19

7.3 Form MetaData Mapping 19

8. Managing User Access 21

© 2015 by Kony, Inc. All rights reserved 4 of 5

8.1 Adding a New User 21

8.2 Editing User Information 22

8.3 Changing the Password 23

8.4 Deleting an User 24

9. View the Configuration of the Admin Console 26

10. Configuring Log Files 27

© 2015 by Kony, Inc. All rights reserved 5 of 5

Kony MobileFabric Integration Service

Kony MobileFabric Sync

© 2015 by Kony, Inc. All rights reserved 1 of 34

1.2 Intended Audience

1.3 Formatting Conventions

© 2015 by Kony, Inc. All rights reserved 2 of 34

Monospace l User input text, system prompts, and

l Names of books and documents

URL Active link to a URL.

Provides helpful hints or additional information.

Highlights actions or information that might cause

© 2015 by Kony, Inc. All rights reserved 3 of 34

We welcome your feedback on our documentation. Write to us at techpubs@konylabs.com. For

© 2015 by Kony, Inc. All rights reserved 4 of 34

2. Launching Admin Console

For example: http://10.10.1.105:9090/admin

© 2015 by Kony, Inc. All rights reserved 5 of 34

3. Kony Studio Applications

3.1 View the list of services

You can view the list of services associated to the application.

3.2 Deleting an Application

To delete an application's service, follow these steps:

1. Go to Kony MobileFabric Integration Service Admin Console.

2. Select an app from the Apps page.

3. Click Delete. A confirmation message appears.

© 2015 by Kony, Inc. All rights reserved 6 of 34

4. Click OK. The application is deleted.

© 2015 by Kony, Inc. All rights reserved 7 of 34

4. Using Basic Reports

© 2015 by Kony, Inc. All rights reserved 8 of 34

To generate a basic report, follow these steps: