Bootcamp Training Setup Guide-V1.7nuevo

Training Setup Guide v1.7

Bootcamp Training Student Setup Guide This guide walks you through everything you need to do to set up your machine for taking the Bootcamp 6.0 training class (classroom or online). The typical installation is on a PC so that is what is covered here. Note that for developing iOS applications, you'll ALSO need a Mac computer to finish the final compilation and deployment on devices/simulators for testing. Setting up the PC and the Mac are covered in this document.


Table of Contents

PREREQUISITES 3 EMAIL WITH LICENSE AND LOGIN INFO 3 VISUALIZER CLOUD REQUIREMENTS 3 LICENSE SUMMARY 5

COMPUTER REQUIREMENTS 5 PC REQUIREMENTS 5 ANDROID DEVICE 5 SET YOU DEVICE TO ALLOW USB DEBUGGING 5 INSTALLING DRIVERS 5

NETWORK 6

PREREQUISITE SOFTWARE INSTALLATIONS 7 INSTALL JAVA JDK 1.7 7 CHECKING FOR JAVA_HOME ENVIRONMENT VARIABLE 7 SETTING JAVA_HOME ENVIRONMENT VARIABLE 8 INSTALL DEVICE SDKS 11 ANDROID (REQUIRED) 12 BLACKBERRY (OPTIONAL) 18 WINDOWS PHONE SDK 8 (OPTIONAL) 19

KONY SOFTWARE INSTALLS 19 KONY STUDIO 19 DOWNLOADING AND INSTALLING KONY STUDIO 19 CREATING OTHER ANDROID EMULATORS 44 USING A REAL ANDROID DEVICE (OPTIONAL) 52 KONY SERVER 53 USING THE MIDDLEWARE.LIC FILE 56 FIXING THE PORT CONFLICT ERROR 56 CONFIGURING THE MAC FOR IOS TESTING 58 TESTING THE MAC CONFIGURATION 60 KONY VISUALIZER 63 KONY SYNC SERVER 67 INSTALL MS SQL EXPRESS 67 CONFIGURING SQL EXPRESS 73 INSTALL KONY SYNC SERVER 76 TESTING THE KONY SYNC SERVER 87 CHANGING SYNC SERVER PORT NUMBER 89 INSTALLING THE TRAINING SAMPLE DATABASE – GENERICINC 90 KONY MESSAGING SERVER 94 INSTALLING THE KMS 94 TESTING THE KMS 100 CHANGING MESSAGING SERVER PORT NUMBER 101

APPENDIX A: GENERICINC DATABASE CREATING SCRIPT 103

APPENDIX B – INSTALLATION CHECKLIST 114


Prerequisites Before you are able to install the software you'll need for Bootcamp, you'll need the appropriate licenses and logins. Email with License and Login Info As part of registering for Bootcamp, you will (very shortly if you're reading this doc) or have received an email from our licensing team with:

• A login to http://developer.kony.com • A license file for Kony Studio • A license file for Kony Server • A license file for Kony Sync

If, for whatever reason, you don't get this email or have any concerns, reach out to us by sending an email to [email protected] You'll access the developer website to download all the Kony software and you'll use the license files for gaining access to the various tools you install…EXCEPT for Visualizer. Visualizer Cloud requirements You'll be able to download our Visualizer tool, but to log into that tool you need a valid Visualizer cloud license. The Visualizer cloud is a hosted component that, in part at least, is responsible for validating Visualizer credentials to gain access to the tool. IF your organization already has a Visualizer cloud (do you have other people working with the Visualizer tool? If so, you probably have a cloud), then you just need to get your email address and have the admin invite you to the cloud. This will generate an email that lets you create a password. You can now use your email and that password to login to the Visualizer tool when you get to that section of this doc. IF your organization does not have a Visualizer cloud, you'll need one. If you're going to use Visualizer in your organization on an ongoing basis, you'll need to have a permanent Visualizer cloud so you'll need to talk to your Kony representative about the business side of that to get that set up. You can, however, request a free 90-‐day trial cloud! This is perfect to get through the training and give your organization a time to work out purchasing access to the cloud for the long term. To get started go to: http://cloud.kony.com/products/visualization#get-‐started :


Click on the Request Access link and that lets you request that free trial. Note that it may take a day or two to get approval. You'll also need to use your corporate email when you sign up – no Gmail, yahoo or similar addresses will be accepted. If you feel you're not getting an adequately speedy response, please reach out to us so we can possibly nudge the process along. Email us at: [email protected] and tell us it's taking to long – we'll ping the cloud team. Once that comes through, you'll have a valid login AND you'll be the admin so if others on your team need access too, you can now invite them to your cloud and they'll now have valid logins too as long as that cloud instance is active.


License summary In the rest of this doc, whenever it talks about a login or license files, you'll use the files from the email and your Visualizer login. Let's now talk about setting that software up…

Computer Requirements PC requirements You can install the Kony tools on a Windows 7, windows 8 or later computer. Here are the specifications:

Item Minimum Recommended Processor I5 I7 RAM 4G 8G Free disk space 200G 200G

Android Device While it's not required, it is also very helpful to have an Android 4.0 or later device with USB cable and ADB driver installed on your PC. Students will find that the Google provided Android emulators are slow and a bit cumbersome. You can save a lot of time and reduce your frustration if you're able to deploy to an actual device. To use a device, you'll need to do a few things to make sure it's set up.

Set you device to allow USB debugging On the android device you'll have to enable USB debugging. That is an option in the system settings. Each android phone may be different, but on my Samsung Galaxy S4, in Settings I go to the "More…" option and there is a section called "Developer options". Go in there and make sure the option called "USB debugging" is checked.

Installing drivers There are drivers for each type of device. Do a Google search for drivers for your actual device. They are all different based on the model and manufacturer. If you don't install the drivers properly, you'll know it because your computer will think that connected device is only a mass storage drive or it will show an error on the device. Once the drivers are properly installed, you'll know by checking your computer's Device Manager. Here is what my Samsung Galaxy S4 looks like when the drivers are properly installed:


Of course you phone needs to be connected to your computer using a USB cable. Later on when we talk about testing the app, there is a section on how to run the app on a connected device.

Network All student machines need to have direct Internet connectivity to be able to use various 3rd party public web services that we use in training. Here is a list of these domains that we use throughout the training:

• http://feeds.foxnews.com • http://api.remix.bestbuy.com • http://graphical.weather.gov • http://www.geoplugin.net • https://maps.google.com (used in an example, not mandatory to have access)


Prerequisite Software Installations In preparation for the Bootcamp training you will need to install some third party software development kits (SDKs) and the Java JDK on the PC you will be bringing to class. Computers are not provided. These are important steps of the installation process:

Install Java JDK 1.7 Download Java JDK (this must be version 1.7 and it should be 32 bit or 64 bit based on Windows x86 or Windows 64 respectively). http://www.oracle.com/technetwork/java/javase/downloads/jdk7-‐downloads-‐1880260.html Here is an image of the files you're looking for on that page:

Note: you'll have to check the "Accept License Agreement" option in the header of this list before you can download anything. Once it's downloaded, just double-‐click to kick off the installer. There aren't many options so just click through the "next" buttons accepting all the defaults.

Checking for JAVA_HOME environment variable Note that you will possibly need to set your JAVA_HOME system environment variable. You can test if you already have it set by opening a command window and typing in "set" and hitting return. Here is what it looks like. The listing are alphabetical and you can see that in this list, sure enough, there is NO JAVA_HOME entry:


If you see the same, then you'll need to set your JAVA_HOME variable. The next section explains how to do that

Setting JAVA_HOME environment variable The following steps walk you through on a Windows 7 machine. Here's what you need to do:

1. First, click on your Start icon and RIGHT-‐CLICK Computer and then pick the Properties option in the dialog. Here's what that looks like:


2. In the control panel dialog that shows up, click on the Advanced system settings link:

3. In the System Properties dialog that shows up, click on the Environment Variables button:


4. In the Environment Variables dialog, down at the bottom under System Variables, click the New button:


5. In this dialog, give the variable name the value of: JAVA_HOME and for the variable value, enter the path to where your Java jdk was installed. Here's my values when I installed the Java JDK using all the defaults:

6. Click Ok on this dialog, click Ok on the previous dialog and click Ok on the dialog

before that. When you're back to the control panel, you can close that down. You're all done! Now when you recheck your "set" command in a command window, you should see your new JAVA_HOME (note, you may need to close the command window and reopen it to make sure it's not using cached old values):

Install Device SDKS This section will guide you though the various device SDKs you'll install.


Android (required) There are several steps to getting the Android SDK installed and configured. That’s all covered here:

Downloading and Installing the Android SDK Navigate to http://developer.android.com/sdk/index.html scroll down to the "Other Download Options" and under SDK Tools download installer_r24.0.2-‐windows.exe. Here's what that looks like:

Note: you'll have to accept their terms and agreements to download. Once downloaded, run it – it's the installer. Choose what options you want, but when you get to the Install Location dialog, change the default file location (it'll want to put it in Program Files) to install it directly on your main drive. Ok to use the suggested folder name but put it on the main drive. Here's an example:


The idea is that you don't want to install it anywhere there is a space in the path. Installing it directly on the main drive will always work. It'll install, ask you about a shortcut (do whatever you want) and when finished, make sure that option to start the SDK Manager is checked and click Finish:

Download the Android packages using the SDK Manager tool If you checked the option during installation, the SDK Manager tool will now be running. If not, don’t worry; you can always launch it from the Android SDK install folder:


When the tool first launches, you'll see lots of things you can check to install. Shown on this next screen shot are the components you NEED to install. Don't install anything else just yet, first start with these and make sure they get installed properly:



Note also that you need to check Google Play services under Extras. Make sure you UN-‐check the Android 5.0.1 (API 21). When you've checked the Platform-‐tools, Android 4.0 (API 14) and Android 2.3.3 (API 10) then click the Install 13 packages button. You'll need to accept the agreements to proceed:

It will take a little while to download and install everything. Note that sometimes not everything is installed in that one action. You may have to go back and accept another license and download other items. Just pay attention to any messages and when you think you're done, go back and check that all your components now say "installed" by them. You've now installed everything that is needed to continue the installation. Now, the Android 4.0 package is not very new. We'll now install the 4.4.2 SDK – it's API 19. Back in the SDK manager, now check Android 4.4.2(API 19):


Note that you don't need the Glass Development Kit so you can uncheck that one – it's a separate install anyway so you're saving disk space. You'll also note that this AVD manager always wants to install the latest so just check that it didn't re-‐check some higher API for you. Click Install to install the 4.4.2 items. You'll need to accept the license agreement like before and then it'll download it to your machine. Now…you'll need to do one more thing. In your Android SDK install folder, go to the following folder:

<install directory>/extras/google/google_play_services/libproject/google-‐play-‐services_lib/


In that folder you'll need to edit the project.properties file. In the editor, change the indicated line to say "android-‐14":

You'll only need to change the number. Save and close that file. That's it!

Blackberry (optional) Go to: https://developer.blackberry.com/java/download/previousjdeversions download and install the SDKs you want to use.


Windows Phone SDK 8 (optional) Microsoft will not let you install the Windows Phone 8x SDK on Windows 7, you must run Windows 8 to have the SDK installed. This also means access to the simulators. Go to: http://go.microsoft.com/fwlink/?LinkID=257234&clcid=0x409 extract the ISO and run the installer.

Kony Software Installs All the software you need is available at this Kony developer website: http://developer.kony.com. Make sure you can log in using your credentials (sent in the licensing email). Once you are in, follow the instructions in the following sections to install the Kony Software. Your starting point is to go to the downloads page. Click on the DOWNLOAD link on the developer site's main page:

One thing that's nice about the downloads page is that you have access to previous versions of Kony software if you need to set up an environment to support a project done in a previous version:

The developer Bootcamp always uses the latest versions so make sure you are on the Kony v6.0 GA tab before you start downloading software for the class. Kony Studio The first installation we'll do is for Kony Studio.

Downloading and Installing Kony Studio On the downloads page you'll see these 2 options:


If you are running a 64 bit operating system then make sure you pick the 64 bit installer by clicking that Download button. If you're running a 32 bit operating system, choose the other Download button. Note that the Kony documentation set has the full Installation guide and it can be found here for further reference: http://docs.kony.com/konylibrary/ -‐ welcome_studio.htm%3FTocPath=Kony%2520Studio|_____0 . That opens up the online documents and from there you can find the installer doc as shown below:

Anyway, once you've downloaded the Kony Studio installer, go ahead and run it. The first screen is just an info screen:


click Next to continue the install… The next screen is the terms and agreement:

You'll have to check the "I accept…" option to continue the install… The next screen talks about your license for Kony Studio:


The Kony Studio license file you got in the email is what you'll use. Check that middle option ("I have an Enterprise License File") and you'll see it expand to let you go browse to that file. You're looking for the ide.lic file. Find that file (wherever you saved it) and choose it:

Note that you can ALSO use a cloud license IF you have one. You're welcome to use that or you own license file if you have them. The one we provide has a 3 month expiration so it's ONLY good for training and some practice after the class. Once it expires, you're on your own to get a cloud account or a "real" license file. The next screen gathers info about you to activate your license:


Just fill that in and go to Next to continue the installation… The installer then looks at your system to see if it can find the prerequisite software installed on your system. Since we already installed Java and the Android SDK (and optionally the other device SDKs) it SHOULD find those. Here is what it looks like:

If it can't find your Java or Android SDK, you did something wrong earlier. Go back and make sure you installed them properly and your JAVA_HOME is set. Once you see it confirm (like in the screenshot above), click Next… This next screen is just informational to give you links to the device SDKs:


You can just continue by clicking Next… This next screen asks you where you want to install Kony Studio. This is up to you but one place I recommend you DON'T install it is where it defaults to – Program Files. I find that the best place to put your Kony Studio is right there on your main drive. So I change the default and type in my own folder name (C:\Kony) as shown below:

Click Next to continue… The next screen asks if you want to also install the Kony Server. YES! Make sure that option is checked:


Click Next to continue… This is a summary screen to make sure you have the right locations:

Click the Install button to actually start the installation… After installing everything, it'll show this screen:


It's not uncommon that you'll have a proxy at work. Kony Studio and Kony Server both assume they can connect directly to internet resources. If you DO have a proxy at work, then click the links that will take you to pages on developer.kony.com that will tell you what to do to make the tools work behind your proxy. Click Next to continue… Here is a note about copying some files IF you're going to be doing SAP development.:

This is not part of the Bootcamp course, so you can skip this and click Next… Now, FINALLY you are done:


Go ahead and UN-‐check that Launch Kony Studio option. We'll run it ourselves. Click Done.

Testing Kony Studio Installation The installation put a shortcut on your desktop, we'll use that to start Kony Studio:

Double-‐click it to run Kony Studio. When you run it for the first time, you'll see this:


A workspace is a folder that will contain all your Kony Studio projects and configurations. You can have as many workspaces as you want. Since they contain configuration information, if you install a newer version of Kony Studio, it's best to create a NEW workspace. You don't want projects made from different versions of Kony Studio in one folder. This first dialog suggests the KonySampleApps workspace and wants to put it in your user folder. Leave that as is. The installer put that folder there and it has a sample app in it that we'll use to test our install. Leaving the option ("Use this as the default and do not ask again") UN-‐checked is best. This way, each time you start Kony Studio you'll get this screen. That way you can always pick which workspace you'll work on rather than always launching in the same place. Click OK… Now you'll get the welcome screen:

You can close this by clicking the "x" on the Welcome tab. Once you close this welcome screen you're now in Kony Studio:


In the Console view at the bottom you'll see a lot of debug and startup info logged. It's possible that you have a port conflict. By default the build in Jetty Server uses port 8888. If that port is already used on your machine, you'll see something in the logs showing an error that it couldn't start Jetty on port 8888.

Changing the Jetty Server Port (only if needed) You can always change the default port in Studio by going to the Windows/Prefrerences menu item and that brings up the preferences dialog. In that dialog open the Kony Dev Studio branch and then the Embedded server item:


Here you can change the default port it uses to whatever you want. Note that you'll have to stop and restart the Jetty server. We don't use the HTTPS port in training so you don't have to worry about that one. In your Studio applications view, right-‐click in that view and go to the Jetty Web Server menu and choose Stop:


And then go right back in and choose Start to restart it:

Now it should start with no port conflict errors.

Adding Java bin directory to Path environment variable (if needed) One other issue that may come up is you get some Java related errors either here or when you test the application in the section that follows this. At this point you should have your Java's bin directory in your computer's Path environment variable. We've already talked about making sure that JAVA_HOME is set so now let's check what values are in our PATH environment variable. You can look by running the "set" command in a command window:


In the above example, the Path variable has a lot of folders identified. At the end of the list we see the Java's bin directory specified pointing to where we installed Java. This is what you WANT to see – a proper path specified. If you don't see the bin directory then you'll have to manually add it in. Go back to your computer's environment variables area and this time we'll find the Path variable under System variables and we'll choose the Edit… option:


In the dialog, just scroll to the end and enter the path to your Java installation's bin directory:

Note: depending on what installation options you chose ("just for me" or "for everyone that uses this machine") you might find that the bin directory is listed in the User variables Path definition:


That's ok but then only that user can successfully us Studio on this machine. It's ok to copy it to the System Variables so this way anyone logged into the machine will have access to that version of Java. The point is to make sure that the Java bin directory is called on in one of those 2 Path variable definitions.

Testing the HelloWorld application Notice that on the left, in that one pane, you see something called "HelloWorld". That is the sample application that came in this default workspace. Click on the little arrow to expand the tree to see the app components:


What we are going to do is build this app and try running it on our Android emulator. Now, don't worry about why we're doing what we're doing, that is what the Bootcamp class is for! Let's just follow along to make sure everything is ok.

Build the app If the HelloWorld project/application is not highlighted, click it to make sure it's highlighted. You'll see a little circle with a "play button" in it. It's a dropdown so expand the dropdown and pick the Build without Clean option:

This will bring up the build screen. On that screen check the box for Android native AND the Android HTML5 SPA options:


Click Build… If you used your cloud credentials for licensing then you MAY see this error message when you try to build:

Click on Configure and that will open up the application properties sheet to the Kony Server tab. In this page, expand the dropdown for Kony Server and pick ANY value (we'll teach you all about what this means in the training):

Once you pick a value (note your cloud value will show YOUR cloud, not our training cloud), click Finish to close the properties page and the build will continue on.


You should see the console at the bottom of Studio start showing a bunch of build messages and a few dialogs saying what's going on. When it's all done, you SHOULD see this (if everything went ok):

Wahoo! Ok, you're good so far.

Troubleshooting the Build On the other hand, it's not uncommon to get this error:

When you look at the console (you might need to scroll up a bit) you see something in RED that says something about Ant not being recognized as an external command. Ant is a utility that is installed in your installation folder. Kony Studio SHOULD be able to find it. It should have created an environment variable for you:

You can also test to see if the system knows what "Ant" is by running "ant" in a command window:


If you see anything like the above it's working just fine (otherwise you'd see an error saying it doesn't recognize ant as a command). If Ant IS working then just restart Kony Studio. I see this issue frequently when people run Kony Studio directly from the installer (leaving that Launch Kony Studio option checked). Once Kony Studio restarts, try the build again. It should work now. If it doesn't, close Studio and try right-‐clicking the desktop shortcut and try "Run as Administrator". See if that fixes the issue.

Testing the Build Ok, now that you have built the application, we're going to try running it in the Android emulator. In the lower right corner of Studio, you'll see the middle tab says HelloWorld Emulators – you might have to expand (by dragging the pane border) the area to show the full tab title):

The green checkmark by T3 under Android/Mobile means that it knows you did a successful build for Android Native. The other devices shown have the red x indicating that you did not build for those devices. Double-‐click the T3 – this will launch the emulator:


It will also launch a little status window:

What's happening is that the emulator is booting up. The status window is waiting for the emulator to boot up and then it will install the app and run it:


You'll see a failure message when trying to uninstall the app – that's ok since this is the first time you've installed the app. When you run on the simulator a second time, it'll always uninstall the old version and install the new version. You'll see the "Starting kony application" and then if there are no more errors, your emulator should be running the app:

You can now dismiss the status screen by "Press any key to continue…" as the message says. This screen will launch each time you run your app so they will pile up quickly if you don't dismiss them.


Testing the HTML5 SPA web app Now for one final test. As mentiond above, Kony Studio uses port 8888 to host an internal Jetty server. The reason we built the app for HTML5 SPA is to test that the Jetty server is running properly. We first must know what the IP address is of your computer. If you know it or know how to get it, great, go get it. If you don't, bring up a command window and type in "ipconfig". It'll show you your IP address. You'll need that in just a bit…

On the Android simulator, click the Home icon on the emulator control pad on the right to bring up the home screen:

Click on the world icon at the bottom right corner of the screen to bring up the device web browser. On the browser, click at the top of the screen to bring up the address bar:


In the address bar, clear out the address and enter the following address:

http://<your IP address>:8888/HelloWorld/p Note that this uses the default port 8888. If you had to change that port number, of course you'll need to change it here as well. Wait! Does your keyboard work on this device? If not, then it's an issue in the definition of this emulator. Shut the emulator down. There are 2 ways to fix this:

1) in the Manager, select the konyavdmap emulator and click Edit…

a. Make sure the option is checked.

b. Save and re-‐launch the emulator 2) Since that emulator definition was built by Kony Studio, it's possible that your AVD

Manager (depending on it's version) can't edit that definition (it crashes the AVD Manager). Here's how to manually edit that emulator definition:

a. Go to your user folder (C:/users/<you>) and there you'll find a .android folder. In there is an avd folder and in there are folders for each of your emulators. Here's one example showing 2 emulators already defined:

b. Go into your konyavdmap.avd folder and open the config.ini file in a text

editor c. Add " hw.keyboard=yes" right after the last letter in the file (all the

parameters like this are put together with no spaces). d. The end of your file will look something like:

e. Save and close the file and re-‐launch the emulator


With either of these fixes, you'll now see an onscreen keyboard so you can use that to type your address. Back to the web app, here is an example of the browser with with my IP address:

Note: the full address for MY machine is: http://10.211.55.4:8888/HelloWorld/p Here is what you should see in your browser:

That's the web version of the same app!


Ok, you are DONE with the Studio install for now. Everything is working for what you need for the class.

Creating other Android Emulators Ok so the default emulator (T3) is the old 2.3.3 version of Android. That is why we downloaded that API version – it's used to create the default emulator instance. You'll want an emulator that is newer so let's go create one! Note that this is not required for class, but it's a really good idea to have a newer emulator ready for class. Shut down your emulator by closing that screen (click on the window x). Go to your Android SDK installation folder (remember, we put it directly on our main drive) and run the AVD Manager.exe application:

Here is what it'll look like:


That one entry is your T3 emulator that we just ran. If you look at the top of the emulator window (when it was running), it tells you it's name:

You'll see where the "T3" came from in just a bit. Ok, in the AVD Manager, click the "Create…" button to create a new emulator. Fill out and pick the same options as I show below to create an emulator instance that is a 4.0 device:


Click OK to save your work. Note! You must use the Google API's not the Android API's when creating the emulator. If you forget and do the Android API, you may see an error when trying to deploy your app saying "Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]". Just go back into the AVD manager and switch to the Google API and relaunch. Now go back to Studio. Back in the emulators window, right-‐click on Mobile (in Android) and choose Add:


Fill out the dialog as shown below:

The Name is what you'll see in your emulator window. The other emulator's name is "T3". The Location is in your Android SDK's tools directory – pick the emulator.exe app. The AVD Name is the name we gave our new emulator in the AVD Manager tool and must match exactly. Click Finish. Now we should see it along with our old T3:

How do you test it? Double-‐click it! (make sure your other emulator is closed – it'll complain if you try to have 2 emulators open at once) The only real difference you'll see is that your emulator is showing the home locked screen: Slide the unlock icon to the right to unlock the screen:


And it will reveal the running app below:


ONE last test is to launch the functional preview app. Don't worry about what it is – you'll learn in class. Here's what you need to do: Right-‐click your emulator, go in the App Preview menu and choose the Launch option:

Note that it's NOT the Launch option in the top level menu (that will run the HelloWorld application – same as double-‐clicking the emulator), you have to go into the App Preview menu and pick Launch there. That will launch another app on your RUNNING emulator (you don't have to ever close the emulator):


We just created the 4.0 emulator and that is the lowest Android version Kony supports. We installed the 2.3.3 version since the T3 automatically builds for that and it still works. What we'll now do is create ANOTHER emulator version using Android 4.4.2. Back in the AVD Manager (in your Android SDK home directory), we'll click the Create button again to create another emulator. Here is the configuration you can use (remember to pick the Google target NOT Android):


Click OK to save your work. Back in Studio, we'll now add this other emulator by right clicking the Mobile node under Android and choosing Add:


We'll configure it like this:

Click Finish and now you can test 4.0 and 4.4.2 Android devices. Feel free to re-‐do the earlier tests by running it on this new emulator to make sure it's working. Congratulations! Your Studio and Android emulators are all set up and ready for the training.

Using a Real Android Device (optional) At the very beginning of this doc we explained how to set up an actual Android device (install drivers and set the device for USB debugging). This section will show you how to test that. Once you've verified that the drivers are installed properly and your device is connected via USB, then in Studio, you first must connect to that device. In the emulators view, right-‐click on the Device node and choose "Get Connected Devices via USB":

Down in the lower corner of Studio you'll see it trying to find your device:


IF it works you'll see your device show up:

Now you can launch the app (double-‐click or right-‐click and pick Launch) and/or functional preview (right-‐click, go into App Preview and pick Launch) to test. You can also try browsing to the HTML5 SPA app in your phone's browser. I find that it takes several attempts usually for it to connect. You MAY see a popup on the device asking if it's ok to connect via USB debugging so look for that. Also you may need to disconnect and then reconnect the device. Try it a few times – it'll connect at some point. This is NOT required for the classes so if you don't get it working, don't worry. You'll still be able to get through everything using the emulators

Testing SPA on Device Note that if testing SPA on a device, you can test it if you are NOT connected via USB. The only requirement is that your network is set up such that your device and Studio are on the same network. If they are on the same network, then if your firewall allows it, you should be able to browse to the SAP application running from your Studio Jetty server. Kony Server When you installed Kony Studio, you checked the box to ALSO install Kony Server. So in your Kony Studio install folder, you'll see 2 shortcuts that you'll use to start and test the Kony Server:


First, double-‐click Memcached. That will launch what looks to be a blank command window:

That's exactly how it looks so do NOT close it, just minimize it to get it out of the way but make sure you leave it running. Closing this window will kill the program. Once you've started Memcached, now double-‐click the Kony Server(Start) shortcut to launch the Kony Server:


It'll take a minute or so for everything to get started. Since you installed this as part of the Studio install, you don't really need that middleware.lic file you got for the Server. If you look in the command window, you'll actually see this message:

but don’t worry, it's not a fatal error and the server should be fine. When it's done, you should see this:

The way to test if the server is indeed running is to run the admin console web app. In a browser, go to this address: http://<your ip address>:8080/admin You'll have to use YOUR IP address. For example, on MY machine I navigate to: http://10.211.55.4:8080/admin If the server is running, you should get a login popup. The default credentials are: Uername: admin Password: admin_1234


Once you login you should see the console:

Since we haven't done anything with the server, if you click on the + next to Applications there will be nothing. That's ok! Congratulations! The Kony Server seems to be running and ready for action.

Using the middleware.lic File Ok, if you don't like that fatal error message about not having a license, you can fix that by putting the middleware.lic file (that you got in your installation package) in the right place. The folder is: users/<you>/.kony You'll see your ide.lic file sitting there (it was put there during the install process when you gave it your license file). In the example below, I'm logged in as administrator so here is where I copy my middleware.lic file:

Now when you re-‐start the Kony server, you'll not get that license error message.

Fixing the Port Conflict Error Kony Server, by default, uses port 8080 on your machine to communicate. If you already have OTHER programs that are using that port, you will get an error when starting Kony Server that the port is already in use.


You have 2 choices:

1) stop that other program to release port 8080. This is only viable is you don't need that other program. Chances are it's running for a reason so this might not be a good option for you

2) change the port that Kony Server runs on. Let's show you how to do that… To change the port first stop Kony Server and Memcached (sure, it probably crashed but close the windows to be sure). In your Kony Studio install folder, go to the: Kony_Server/tomcat-‐7.0.52/instance1/conf folder and edit the server.xml file:

You can search for "8080" but about midway down in the file you'll find 2 instances that you need to change to whatever port you want:


In this example, I changed it to 8089. After you save your edits, restart the Kony server. Now it should not have that port conflict. If it starts now, you're all done! Note that in the training, we use port 8080 in ALL the examples. If you had to change your port, just remember that you did this!!! Jot down your new port number and you'll have to use that whenever you access the Kony Server. Configuring the Mac for iOS testing Kony lets you build cross-‐platform applications. In order to actually build and test for iOS devices you need a Mac computer. This can be a shared resource used by all developers Mac OS X Yosemite i.e., 10.10 and xCode 6.1 are necessary to build and test apps for iOS devices (iPhone and iPad). This computer must also be on the same network as the PC machine so that the PC will be able to push generated code to the Mac for final compilation and testing on iOS simulators/devices. The idea is that when you do the build in Kony Studio, you can now push that generated code to the Mac/xCode where you'll do a final build to test it on the iOS simulators or an actual device (developer certificates required). In xCode is only ONE project that is overwritten each time you build for iOS. If everyone on the team is using the Mac you'll all overwrite each other's projects. Once you know that the Mac is on the same network as your PC, you only need to configure the Mac details in Kony Studio for it to be able to push the build to that Mac.


In Kony Studio use the menu options and go to Windows-‐> Preferences. In that dialog expand the Kony Dev Studio node and pick iOS. The first task is to test that you can indeed connect to that Mac computer. Enter valid credentials for connecting to the Mac and click the Test Connection button:

Once you can connect to the Mac, check the "Open project in Xcode" option and refresh the Xcode Version and make sure it shows it in the dialog:

Then below that refresh the Base SDK Version and make sure that comes up and also choose which iOS device you'd like to use by default in the Simulator Type dropdown:

Click the Apply button and then the OK button.


Testing the Mac configuration Now we can go back to our Application and build it for iPhone to test:

And in the build screen, we'll uncheck everything and check iPhone native:

Click Build… When it's done, now back in the emulator view we see a nice green check mark next to our iPhone:


Double-‐click the iPhone to launch the app over in the iPhone simulator on your Mac. When it's done, over on the Mac you should see something like this in xCode:

And your default simulator (whatever you set in your Studio preferences) should now be running the app:

Note that xCode isn't actually running though. You can now, in xCode, click the play button to launch the app again. In xCode you can also choose a different device if you want:


I mention this because in the training, you'll put print statements to debug your code. If you are not actually running FROM xCode then you won't see them. By running your app in xCode, you'll now see your print statements and other debug info in the console. Try that now, Click the "play" button and now you should see debug statements in the console and the application will just re-‐launch on the emulator:

If all this works then you've successfully connected to the Mac for iOS builds!


Kony Visualizer Now let's install Kony Visualizer. From the developer portal download the Kony Visualizer installer for Windows:

When you run the installer, the first screen is an information screen:

Click Next… The next screen asks you where you want to install Visualizer. Like Kony Studio, it's usually best to install directly onto your main drive. It's not necessary, but as a developer, it's easier to have everything close by. Here is that screen with the destination folder edited to put it on the main drive:


Click Next… The next screen now asks you where you want your Visualizer workspace to live. Since we put our Kony Studio workspace right on our main drive, we'll do the same for the Visualizer workspace (the default install locations is buried in your user folder). Here is that screen with the workspace folder edited to put it on the main drive AND change the name of the workspace to "Viz_workspace" to make it clear which is which:

Click Next… The next screen is the user agreement screen:


You'll have to check the "I accept the terms of the License Agreement" option to continue the install. Click the Install button… It will take a little bit while everything gets installed and then you're done. Like before you can uncheck the launch option and choose Done:

On the desktop you now have a nice Visualizer shortcut:


Go ahead and double-‐click that to launch Visualizer. Note: Depending on the antivirus software that you may have installed, you might run into an issue. Norton, for example, will quarantine the nw.exe app that is installed with Visualizer. So when you go to launch the app via the shortcut you may get an error saying that the application doesn't exist. If that is the case, go to your antivirus software and restore the file. Now try again. When Visualizer launches you're on the Login screen:

Here is where you will need your Visualizer cloud login. There is no license file for this, you must have a valid Visualizer cloud login of your own. Once you login to Visualizer, here is what you see:


That's all there is to it! Visualizer is now properly installed.

Kony Sync Server The next piece we need to install is the local Kony Sync Server. Note that in the training we show how to use the local server as well as the Cloud version. Installing locally means you have control over it (starting, stopping and direct access) AND we'll also use the installed SQL Express database to host the training sample database. Unfortunately, if you are using the cloud, you can't connect to your own local database instance (since the cloud can't access the database on your machine) so you'll not be able to do the exercise and use the sample database. For this reason, we're installing it locally.

Install MS SQL Express Before we install the Sync Server, we need to install a database. The Sync Server can run on MS SQL Server (including SQL Express), Oracle, MySQL and PostgreSQL. If you already have one of those installed and up and running on your machine, you can use that and skip this step. If you don't have a database or want to install a new one, we'll use MS SQL Express. Navigate to the Microsoft download page: http://www.microsoft.com/en-‐in/download/details.aspx?id=30438 :


Clicking the Download button takes you to the page where you can select the proper installer. On that page, scroll down the list and you'll see the 64 bit and 32 bit installers for the version we need:

Check the option for your computer and hit the Next button to initiate the download. Once it's downloaded, run the installer. The first screen shows your installation options:


Choose the New Installation option… The next screen is the License Terms:

You have to accept the license and click Next to continue… After a bit of processing, the next screen lets you pick what you want installed. You don't need the replication services so you can uncheck that one box. Here is what you should have selected:


Click Next… For the Instance Configuration, leave it all default:

Click Next… The next screen configures the server. No need to change anything:


Click Next… This next screen configures the database. Here you need to be sure you check Mixed Mode. When you do that it will prompt you for a password for the built-‐in sa account. Enter a password (and remember it!):

Click Next… It's totally up to you if you want to share error reports with Microsoft:


Click Next… Now it'll go through the major part of the installation…give it a few minutes to complete. When it's done you'll see the complete message screen:

Click Close… The original installer screen is still open so you can close that as well.


Configuring SQL Express Ok so the installation is complete but now we need to configure it to allow remote connections (namely from our Sync Server). Go to Start > All Programs > Microsoft SQL Server 2005/2008 > Configuration Tools and click SQL Server Configuration Manager:

This opens the Configuration Management tool:

In this dialog, expand the SQL Server Network Configuration node and click on Protocols for SQLEXPRESS:


Now right click on TCP/IP in the right pane and select Properties:

In that dialog, open the IP Addresses tab and scroll to the bottom. There you should see the entry IPALL. Clear out any entry in TCP Dynamic Ports and make sure TCP Port is set to 1433:


Click OK. It'll tell you it'll apply the changes after you restart the service. Make sure that TCP/IP is enabled. If it says disabled, then enable it by right-‐clicking TCP/IP and selecting Enable:

Back in the Configuration Manager tool, click on SQL Server Services and on the SQL Server (SQLEXPRESS) item, right-‐click it and select restart:


You're all done! You're now ready to install the Kony Sync Server

Install Kony Sync Server Before we begin to start the Kony Sync Server, make sure that your Kony Server is stopped and not running. We'll explain in a bit. Back in the Kony developer portal, we need to go to a new page to get access to the Sync Server installer. Navigate here: http://developer.kony.com/Sync On that page, go to the Download area:

That will take you to the download page. Choose the right installer depending on whether you're running a 32 bit or 64 bit operating system:


When it's done downloading, you'll end up with a .zip file. Extract the contents somewhere and run the installer program:

Note: the filename will change as new versions come out. Also note that the installer might be running behind your other windows. Sometimes it seems like nothing happened but the installer is running behind all the other open windows your computer. The first screen is just information:


Click Next… The next screen tells you need a database – we just installed SQL Express so we're ok:

Click Next… The next screen is the license agreement. Note that you must scroll the text for the "I accept…" option to be enabled. You have to agree to continue:


Click Next… The next screens will be to set up your license file. This is part of the package and you'll need the sync.lic file for these steps. Here is the first screen:

Click Next… You'll then be asked to locate your sync.lic file:


Click Finish… The next screen asks you where you want to install the Sync Server. Note that it's default is right on the main drive – right where we want it:

Click Next… The next screen asks what type of application server you want. We'll use Tomcat so select that option:


Click Next… The next screen asks for the type of communication protocol. We're only connecting to our local instance so HTTP is fine:

Click Next… Ok, this next screen lets you pick the ports you want to use. We'll leave it as default so that it matches what you see in the training materials. Note that we're using port 8080 and that is the same as the Kony Server. So this means you can't run both at the same time. You don't need to do that to take the training BUT if you want, you can change the value here so that you don't have to remember to only run one at a time. Note that you'll also have to


remember this new port number so that when you do the training exercise you use the right port number:

Click Next… The next screen asks for a windows user to use to run the Sync when it's run as a service. You have to give it valid credentials:

Click Next… The next screen is where we connect to our SQL Express instance for the Sync Console (it has it's own database). In this dialog, use the port number 1433 and provide that sa password you set up when you installed SQL Express:


Click Test Connection… If everything is working you'll see the success message:

If you don't, you'll get some error message. You'll have to troubleshoot based on what it says. When it's working click Next… The next screen is the same database connection screen but this time it's for the Sync Services database. We're using the same database so the information you enter is the same:


Test the connection and when it works, click Next… The next screen lets you configure a proxy server. We're not doing that so leave that option unchecked:

Click Next… The next screen will install Ant if you want. We already have Ant installed as part of Kony Studio so we can leave this option unchecked:


Click Next… The next screen is to configure the Sync plugin for Kony Studio. We definitely want this option so check the option and provide the path to your Kony Studio plugins folder. That is in the Kony Studio install folder's Kony_Studio folder. In that folder you'll find the plugins:

Click Next… The next screen is for installing sample applications. We'll not use any in the training BUT there is no reason not to install them. You'll have more samples and that is always a good thing:


Click Next… Finally we are at the summary screen:

Click Install… In a few minutes, it'll be finished:


Click Done.

Testing the Kony Sync Server The Kony Sync Server was installed as a service. If you go to your control panel or administration tools and open the services tool, you'll see the KonySync service is started:

Note that if you had your Kony Server running, the service would fail to start because of the port conflict (if you left it to the default 8080). Also note that if you want to use your local Kony Server, you'll have to come to this services view and stop the KonySync service first. You'll know something is wrong because you'll see that the Kony Server failed to start with a port conflict.


Open a browser and let's try loading the Sync Console. The address is: http://<your ip address>:8080/syncconsole

If everything is working you'll get a login dialog. Use the following credentials:

User: syncadmin Password: SyncAdmin123

If the console displays then everything is working just fine:

Now that we know the Sync Server is running properly we're all done. But since we know we won't get to the Sync training materials for a while, let's shut down the service. We'll need to run our Kony Server long before we need to run this Sync Server. In your services, right-‐click and choose Stop:


That's it for the Kony Sync installation.

Changing Sync Server port number Ok, so now that it's all installed you realize that you don't want it running on port 8080. Just like the Kony Server, we change that in the Tomcat's conf folder's server.xml file:

Edit the file and about halfway down you'll see the 2 places you need to change to use a new port:


After you restart the service, test it out by browsing to the sync console using that new port.

Installing the Training sample database – GenericInc For training, we created a sample database that is used for all the examples and exercises. First log into the SQL Server Management Studio with the credentials you used when you installed it (note you'll have to specify "localhost" as the Server name):

Once logged in, you'll want to open up a new query window by clicking the New Query button on the toolbar:


That will open a new blank query window:

The script for creating the database is found in Appendix A of this document. Copy that entire block of text (several pages worth) and paste it into the query window:


Now we can run this query that will create our sample database and populate it with the data:

Note: it will try to create the database and log files on your computer. You'll need to make sure there is enough space. If you get a disk space error, then you'll need to modify the first few lines of the SQL script to change the drive from c: to whatever drive you have that has sufficient space. Here are the 2 lines you need to change:


Make the change and re-‐execute the script. After this runs successfully, then you'll need to refresh your view to see your new database in the management console:

You'll now see a new database called GenericInc in your list of databases! Let's open it up and make sure the data is there. Expand the Database to see the tables. Right-‐click on the Customers table and select the Edit Top 200 Rows option to bring back the first 200 rows (we have way fewer) into an edit mode:

And if you see this data, you're all set:


Note that there should be data in all the tables. Make sure you have all the data before trying to use this database. That's it! You've successfully installed the sample GenericInc database. Kony Messaging Server The Kony Messaging Server also needs a database to run. If, for whatever reason, you didn't do the Kony Sync Server installation yet, make sure that you've at least installed SQL Express before trying to install the Kony Messaging Server.

Installing the KMS We'll go back to the main downloads page on the developer portal:

http://developer.kony.com/KonyReleases We'll now use the KMS (Kony Messaging Server) installer:

Note there is only one version (no 32 bit or 64 bit installers). Download the installer. The installer is zipped up so unzip it in a known location. From there let's run the installer:

Like the other installers, it might be hidden behind other windows. Go find it. The first screen is just an introduction screen:


Click Next… The next screen, like the Sync Server, tells us we need a database for the KMS to run. We already installed SQL Express so we are good:

Click Next… The next screen is the license agreement. You must scroll to the bottom to enable the "I accept…" option. You must agree to continue:


Click Next… The next screen asks where you want it installed. The default is right on our main drive right where we want it. You can accept that default path:

Click Next… The next screen asks what type of application server you want. We'll use Tomcat:


Click Next… On the next screen, here we go again where we have to specify a port. By default the Messaging Server also runs on port 8080. For the training we'll not need to run the other servers so it's ok to leave it to the default. BUT for real development going forward you very much might want a unique port. Feel free to change it but then remember that you did! You'll need that info when you are using the admin console. In my example, I'll leave it as the default 8080 (and we don’t need the proxy):

Click Next…


The next screen asks what protocols to use. Since we're running this locally we only need HTTP:

Click Next… The next screen asks for a valid windows user to use for setting up the service. Just like the Sync Server, give it a valid login:

Click Next… The next screen is where you configure the database access. On this screen, change the Database to SQL Server 2008 or higher and fill out the information. Note that this screen


has a default database user of "admin". We didn't set that user up, so make sure to change it to "sa" and the password you set when you installed SQL Express. Leave the database name the same and make sure the Create Database option is checked:

Click Next… At this point, if your database connection fails (there is no Test Connection button), you'll get an error message. Make sure you select to Re-‐Try it. It brings you back to the database screen so you can correct any mistakes.

Click Install… After a minute or so it'll finish:


Click Done.

Testing the KMS The Kony Messaging Server has a console app as well. After installation the service is running so we can navigate to our console with:

http://<your IP address>:8080/kpns It will ask for login credentials. Use the following:

User: admin Password: admin

If everything is running you should see the console:


That's it! The KMS is now successfully installed. Like the Sync server, let's not leave it up and running on port 8080 since we'll need the Kony Server before we need the messaging server. Back in service manager, find the KonyMobileFabricMessaging service, right-‐click it and select Stop:

Changing Messaging Server port number Ok, so now that it's all installed you realize that you don't want it running on port 8080. Just like the Kony Server, we change that in the Tomcat/instance1/conf folder's server.xml file:


Edit the file and about halfway down you'll see the 2 places you need to change to use a new port:

After you restart the service, test it out by browsing to the sync console using that new port. YOU ARE ALL DONE AND READY FOR CLASS!!!


Appendix A: GenericInc Database creating script The following is the complete script for creating the GenericInc database that is used with the Kony Sync training. Copy the whole script: USE [master] GO /****** Object: Database [GenericInc] Script Date: 07/03/2014 11:28:07 ******/ CREATE DATABASE [GenericInc] ON PRIMARY ( NAME = N'GenericInc', FILENAME = N'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\GenericInc.mdf' , SIZE = 2048KB , MAXSIZE = UNLIMITED, FILEGROWTH = 1024KB ) LOG ON ( NAME = N'GenericInc_log', FILENAME = N'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\GenericInc_log.ldf' , SIZE = 1024KB , MAXSIZE = 2048GB , FILEGROWTH = 10%) GO ALTER DATABASE [GenericInc] SET COMPATIBILITY_LEVEL = 100 GO IF (1 = FULLTEXTSERVICEPROPERTY('IsFullTextInstalled')) begin EXEC [GenericInc].[dbo].[sp_fulltext_database] @action = 'enable' end GO ALTER DATABASE [GenericInc] SET ANSI_NULL_DEFAULT OFF GO ALTER DATABASE [GenericInc] SET ANSI_NULLS OFF GO ALTER DATABASE [GenericInc] SET ANSI_PADDING OFF GO ALTER DATABASE [GenericInc] SET ANSI_WARNINGS OFF GO ALTER DATABASE [GenericInc] SET ARITHABORT OFF GO


ALTER DATABASE [GenericInc] SET AUTO_CLOSE OFF GO ALTER DATABASE [GenericInc] SET AUTO_CREATE_STATISTICS ON GO ALTER DATABASE [GenericInc] SET AUTO_SHRINK OFF GO ALTER DATABASE [GenericInc] SET AUTO_UPDATE_STATISTICS ON GO ALTER DATABASE [GenericInc] SET CURSOR_CLOSE_ON_COMMIT OFF GO ALTER DATABASE [GenericInc] SET CURSOR_DEFAULT GLOBAL GO ALTER DATABASE [GenericInc] SET CONCAT_NULL_YIELDS_NULL OFF GO ALTER DATABASE [GenericInc] SET NUMERIC_ROUNDABORT OFF GO ALTER DATABASE [GenericInc] SET QUOTED_IDENTIFIER OFF GO ALTER DATABASE [GenericInc] SET RECURSIVE_TRIGGERS OFF GO ALTER DATABASE [GenericInc] SET DISABLE_BROKER GO ALTER DATABASE [GenericInc] SET AUTO_UPDATE_STATISTICS_ASYNC OFF GO ALTER DATABASE [GenericInc] SET DATE_CORRELATION_OPTIMIZATION OFF GO ALTER DATABASE [GenericInc] SET TRUSTWORTHY OFF GO ALTER DATABASE [GenericInc] SET ALLOW_SNAPSHOT_ISOLATION OFF GO


ALTER DATABASE [GenericInc] SET PARAMETERIZATION SIMPLE GO ALTER DATABASE [GenericInc] SET READ_COMMITTED_SNAPSHOT OFF GO ALTER DATABASE [GenericInc] SET HONOR_BROKER_PRIORITY OFF GO ALTER DATABASE [GenericInc] SET READ_WRITE GO ALTER DATABASE [GenericInc] SET RECOVERY SIMPLE GO ALTER DATABASE [GenericInc] SET MULTI_USER GO ALTER DATABASE [GenericInc] SET PAGE_VERIFY CHECKSUM GO ALTER DATABASE [GenericInc] SET DB_CHAINING OFF GO USE [GenericInc] GO /****** Object: Table [dbo].[SalesPerson] Script Date: 07/03/2014 11:28:08 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO CREATE TABLE [dbo].[SalesPerson]( [ID] [int] IDENTITY(101,1) NOT NULL, [FirstName] [nvarchar](50) NULL, [LastName] [nvarchar](50) NULL, [Territory] [nchar](10) NOT NULL, [ChangedDate] [timestamp] NOT NULL,


[isDeleted] [bit] NOT NULL, CONSTRAINT [PK_SalesPerson] PRIMARY KEY CLUSTERED ( [ID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] GO /****** Object: Table [dbo].[Product] Script Date: 07/03/2014 11:28:08 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO CREATE TABLE [dbo].[Product]( [ID] [int] IDENTITY(101,1) NOT NULL, [Name] [nvarchar](50) NOT NULL, [Price] [money] NOT NULL, [Color] [nvarchar](50) NULL, [ChangedDate] [timestamp] NOT NULL, [isDeleted] [bit] NOT NULL, CONSTRAINT [PK_Product] PRIMARY KEY CLUSTERED ( [ID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] GO /****** Object: Table [dbo].[PlaceInfo] Script Date: 07/03/2014 11:28:08 ******/ SET ANSI_NULLS ON


GO SET QUOTED_IDENTIFIER ON GO CREATE TABLE [dbo].[PlaceInfo]( [ID] [int] IDENTITY(1000,1) NOT NULL, [Name] [nchar](100) NOT NULL, [State] [nchar](10) NOT NULL, [Rating] [int] NOT NULL, [isDeleted] [bit] NOT NULL, [ChangedDate] [timestamp] NOT NULL, CONSTRAINT [PK_PlaceInfo] PRIMARY KEY CLUSTERED ( [ID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] GO /****** Object: Table [dbo].[Customer] Script Date: 07/03/2014 11:28:08 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO CREATE TABLE [dbo].[Customer]( [ID] [int] IDENTITY(101,1) NOT NULL, [FirstName] [nvarchar](50) NULL, [LastName] [nvarchar](50) NULL, [LoyaltyLevel] [int] NOT NULL, [ChangedDate] [timestamp] NOT NULL, [isDeleted] [bit] NOT NULL, CONSTRAINT [PK_Customer] PRIMARY KEY CLUSTERED


( [ID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] GO /****** Object: Table [dbo].[CustomerOrder] Script Date: 07/03/2014 11:28:08 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO CREATE TABLE [dbo].[CustomerOrder]( [ID] [int] IDENTITY(101,1) NOT NULL, [CustomerID] [int] NOT NULL, [SalesPersonID] [int] NULL, [OrderTotal] [money] NULL, [ChangedDate] [timestamp] NOT NULL, [isDeleted] [bit] NOT NULL, CONSTRAINT [PK_Order] PRIMARY KEY CLUSTERED ( [ID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] GO CREATE UNIQUE NONCLUSTERED INDEX [IX_Order] ON [dbo].[CustomerOrder] ( [ID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]


GO /****** Object: Table [dbo].[OrderItem] Script Date: 07/03/2014 11:28:08 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO CREATE TABLE [dbo].[OrderItem]( [ID] [int] IDENTITY(101,1) NOT NULL, [OrderID] [int] NOT NULL, [ProductID] [int] NOT NULL, [Quantity] [int] NOT NULL, [SubTotal] [money] NOT NULL, [ChangedDate] [timestamp] NOT NULL, [isDeleted] [bit] NOT NULL, CONSTRAINT [PK_OrderItem] PRIMARY KEY CLUSTERED ( [ID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] GO CREATE NONCLUSTERED INDEX [IX_OrderItem] ON [dbo].[OrderItem] ( [ID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] GO /****** Object: ForeignKey [FK_Order_Customer] Script Date: 07/03/2014 11:28:08 ******/


ALTER TABLE [dbo].[CustomerOrder] WITH CHECK ADD CONSTRAINT [FK_Order_Customer] FOREIGN KEY([CustomerID]) REFERENCES [dbo].[Customer] ([ID]) GO ALTER TABLE [dbo].[CustomerOrder] CHECK CONSTRAINT [FK_Order_Customer] GO /****** Object: ForeignKey [FK_Order_SalesPerson] Script Date: 07/03/2014 11:28:08 ******/ ALTER TABLE [dbo].[CustomerOrder] WITH CHECK ADD CONSTRAINT [FK_Order_SalesPerson] FOREIGN KEY([SalesPersonID]) REFERENCES [dbo].[SalesPerson] ([ID]) GO ALTER TABLE [dbo].[CustomerOrder] CHECK CONSTRAINT [FK_Order_SalesPerson] GO /****** Object: ForeignKey [FK_OrderItem_Order] Script Date: 07/03/2014 11:28:08 ******/ ALTER TABLE [dbo].[OrderItem] WITH CHECK ADD CONSTRAINT [FK_OrderItem_Order] FOREIGN KEY([OrderID]) REFERENCES [dbo].[CustomerOrder] ([ID]) GO ALTER TABLE [dbo].[OrderItem] CHECK CONSTRAINT [FK_OrderItem_Order] GO USE [GenericInc] GO /****** Object: Table [dbo].[SalesPerson] Script Date: 07/03/2014 12:04:54 ******/ SET IDENTITY_INSERT [dbo].[SalesPerson] ON INSERT [dbo].[SalesPerson] ([ID], [FirstName], [LastName], [Territory], [isDeleted]) VALUES (101, N'Aster', N'Stone', N'East ', 0) INSERT [dbo].[SalesPerson] ([ID], [FirstName], [LastName], [Territory], [isDeleted]) VALUES (102, N'Jake', N'Frenz', N'West ', 0) INSERT [dbo].[SalesPerson] ([ID], [FirstName], [LastName], [Territory], [isDeleted]) VALUES (103, N'Frida', N'Ipswitch', N'North ', 0)


INSERT [dbo].[SalesPerson] ([ID], [FirstName], [LastName], [Territory], [isDeleted]) VALUES (104, N'Amanda', N'Fredricks', N'South ', 0) INSERT [dbo].[SalesPerson] ([ID], [FirstName], [LastName], [Territory], [isDeleted]) VALUES (105, N'Julie', N'Finster', N'East ', 0) INSERT [dbo].[SalesPerson] ([ID], [FirstName], [LastName], [Territory], [isDeleted]) VALUES (106, N'Arnold', N'Longly', N'North ', 0) SET IDENTITY_INSERT [dbo].[SalesPerson] OFF /****** Object: Table [dbo].[Product] Script Date: 07/03/2014 12:04:54 ******/ SET IDENTITY_INSERT [dbo].[Product] ON INSERT [dbo].[Product] ([ID], [Name], [Price], [Color], [isDeleted]) VALUES (101, N'Table Lamp', 44.3400, N'Gold', 1) INSERT [dbo].[Product] ([ID], [Name], [Price], [Color], [isDeleted]) VALUES (102, N'Dish Set', 59.9500, N'White', 0) INSERT [dbo].[Product] ([ID], [Name], [Price], [Color], [isDeleted]) VALUES (103, N'Soap Dish', 5.9900, N'Black', 0) INSERT [dbo].[Product] ([ID], [Name], [Price], [Color], [isDeleted]) VALUES (104, N'Knife Set', 104.5500, NULL, 0) INSERT [dbo].[Product] ([ID], [Name], [Price], [Color], [isDeleted]) VALUES (105, N'Snow Tires', 109.9900, N'Black', 0) INSERT [dbo].[Product] ([ID], [Name], [Price], [Color], [isDeleted]) VALUES (106, N'Canary Feeder', 14.3300, N'Walnut', 0) INSERT [dbo].[Product] ([ID], [Name], [Price], [Color], [isDeleted]) VALUES (107, N'Igloo', 599.9900, N'White', 0) INSERT [dbo].[Product] ([ID], [Name], [Price], [Color], [isDeleted]) VALUES (108, N'Table', 128.9500, N'Blue', 0) INSERT [dbo].[Product] ([ID], [Name], [Price], [Color], [isDeleted]) VALUES (109, N'Garden Hose', 29.9900, N'Black', 0) SET IDENTITY_INSERT [dbo].[Product] OFF /****** Object: Table [dbo].[PlaceInfo] Script Date: 07/03/2014 12:04:54 ******/ SET IDENTITY_INSERT [dbo].[PlaceInfo] ON INSERT [dbo].[PlaceInfo] ([ID], [Name], [State], [Rating], [isDeleted]) VALUES (1001, N'Space Needle ', N'WA ', 4, 0) INSERT [dbo].[PlaceInfo] ([ID], [Name], [State], [Rating], [isDeleted]) VALUES (1003, N'Grand Canyon ', N'AZ ', 5, 0)


INSERT [dbo].[PlaceInfo] ([ID], [Name], [State], [Rating], [isDeleted]) VALUES (1004, N'Golden Gate Bridge ', N'CA ', 3, 0) INSERT [dbo].[PlaceInfo] ([ID], [Name], [State], [Rating], [isDeleted]) VALUES (1005, N'Baseball Hall of Fame ', N'OH ', 3, 0) SET IDENTITY_INSERT [dbo].[PlaceInfo] OFF /****** Object: Table [dbo].[Customer] Script Date: 07/03/2014 12:04:54 ******/ SET IDENTITY_INSERT [dbo].[Customer] ON INSERT [dbo].[Customer] ([ID], [FirstName], [LastName], [LoyaltyLevel], [isDeleted]) VALUES (101, N'Frank', N'Wystrom', 0, 0) INSERT [dbo].[Customer] ([ID], [FirstName], [LastName], [LoyaltyLevel], [isDeleted]) VALUES (102, N'Wilma', N'Jenson', 1, 0) INSERT [dbo].[Customer] ([ID], [FirstName], [LastName], [LoyaltyLevel], [isDeleted]) VALUES (103, N'Anil', N'Gupta', 2, 0) INSERT [dbo].[Customer] ([ID], [FirstName], [LastName], [LoyaltyLevel], [isDeleted]) VALUES (104, N'Francis', N'Wong', 2, 0) INSERT [dbo].[Customer] ([ID], [FirstName], [LastName], [LoyaltyLevel], [isDeleted]) VALUES (105, N'Anna', N'Cryzstoczech', 3, 0) INSERT [dbo].[Customer] ([ID], [FirstName], [LastName], [LoyaltyLevel], [isDeleted]) VALUES (106, N'Adi', N'Simmons', 2, 0) INSERT [dbo].[Customer] ([ID], [FirstName], [LastName], [LoyaltyLevel], [isDeleted]) VALUES (107, N'Jane', N'Van Der Mark', 0, 0) INSERT [dbo].[Customer] ([ID], [FirstName], [LastName], [LoyaltyLevel], [isDeleted]) VALUES (108, N'Sanjay', N'Gupta', 3, 0) INSERT [dbo].[Customer] ([ID], [FirstName], [LastName], [LoyaltyLevel], [isDeleted]) VALUES (109, N'Doorm', N'Singer', 2, 0) SET IDENTITY_INSERT [dbo].[Customer] OFF /****** Object: Table [dbo].[CustomerOrder] Script Date: 07/03/2014 12:04:54 ******/ SET IDENTITY_INSERT [dbo].[CustomerOrder] ON INSERT [dbo].[CustomerOrder] ([ID], [CustomerID], [SalesPersonID], [OrderTotal], [isDeleted]) VALUES (101, 104, 104, 447.8900, 0) INSERT [dbo].[CustomerOrder] ([ID], [CustomerID], [SalesPersonID], [OrderTotal], [isDeleted]) VALUES (102, 101, 106, 11.9800, 0) INSERT [dbo].[CustomerOrder] ([ID], [CustomerID], [SalesPersonID], [OrderTotal], [isDeleted]) VALUES (103, 105, 102, 419.9900, 0) SET IDENTITY_INSERT [dbo].[CustomerOrder] OFF


/****** Object: Table [dbo].[OrderItem] Script Date: 07/03/2014 12:04:54 ******/ SET IDENTITY_INSERT [dbo].[OrderItem] ON INSERT [dbo].[OrderItem] ([ID], [OrderID], [ProductID], [Quantity], [SubTotal], [isDeleted]) VALUES (101, 101, 102, 2, 119.9000, 0) INSERT [dbo].[OrderItem] ([ID], [OrderID], [ProductID], [Quantity], [SubTotal], [isDeleted]) VALUES (102, 101, 105, 4, 439.9600, 0) INSERT [dbo].[OrderItem] ([ID], [OrderID], [ProductID], [Quantity], [SubTotal], [isDeleted]) VALUES (103, 102, 103, 2, 11.9800, 0) INSERT [dbo].[OrderItem] ([ID], [OrderID], [ProductID], [Quantity], [SubTotal], [isDeleted]) VALUES (104, 103, 107, 1, 599.9900, 0) SET IDENTITY_INSERT [dbo].[OrderItem] OFF


Appendix B – Installation Checklist Check off the items from the list as you complete them: ☐ Get access to a Visualizer Cloud – have login credentials ☐ Have licensing email and all licenses are ready to use ☐ Validated access to the various domains used in training ☐ Java JDK 1.7 installed ☐ JAVA_HOME environment variable created ☐ Downloaded and installed the Android SDK ☐ Android API's 10, 14 and 21 are installed using SDK manager ☐ Android Google play project.properties file was edited to use "android-‐14" ☐ (optional) Install BlackBerry SDK ☐ (optional) Install Windows Phone SDK ☐ Successfully download and install Kony Studio WITH Kony Server option

selected ☐ Able to launch Kony Studio using the KonySampleApps workspace ☐ (optional) Changed Jetty port number if there was a failure because of a port

conflict when starting Kony Studio ☐ Verified that Java bin directory is in the path environment variable ☐ Successfully build the HelloWorld app for Android native and SPA ☐ Successfully ran the native app on Android emulator ☐ Successfully ran the SPA app on Android emulator in browser ☐ Created Android 4.0 and 4.4.2 emulators and ran HelloWorld app on them to

make sure they work ☐ Kony server starts up with no errors ☐ Successfully browse to the server admin console and login ☐ (optional) Changed Kony Server port number if there was a failure because of a

port conflict when starting Kony Server ☐ Configured Mac details in Kony Studio preferences ☐ Successfully built and tested native app on iOS phone simulator ☐ Installed Kony Visualizer ☐ Successfully logged in to Visualizer ☐ Installed MS SQL Express ☐ Configured SQL Express protocols ☐ Downloaded and Installed Kony Sync server ☐ Running Sync Server and successfully logging into the console web app ☐ (optional) Changed Sync Server port number if there was a failure because of a

port conflict when starting Sync Server ☐ Installed the Generic Inc database on SQL Express ☐ Downloaded and Installed Kony Messaging Server (KMS) ☐ Successfully logged into KMS console web app ☐ (optional) Changed KMS port number if there was a failure because of a port

conflict when starting KMS ☐ Congratulated myself for getting this installation done!

Date post:	30-Jan-2016
Category:	Documents
Upload:	paola-bonilla
View:	20 times
Download:	0 times

Bootcamp Training Setup Guide-V1.7nuevo

Documents