• Methods to run web apps in SSSP:

• 1. Web app server

• 2. USB Method

• 3. Developer Mode

• Description of the sssp_config.xml

• Attribute of the sssp_config.xml

Methods to run web apps in SSSP:

1. Web app server

In order to run a Native Application from a Server URL you should follow these steps:

• Create project folder (such as tizen) to a webserver and upload any .wgt test application to a
  webserver folder. Example URL would be: http://IP:Port/tizen/

  Structured in Tomcat Sever
  

  

  
  

• Prepare the configuration fileand upload it to a webserver. Example: location of this file would be at following path: http://IP:Port/tizen/ sssp_config.xml
  

  

  
  

• On the LFD now change the Server URL to be the path that contains your sssp_config.xml file. Example URL would be: http://IP:Port/tizen/
  

  

  
  

2. USB Method

In order to run a USB Application from a Server URL you should follow these steps:

• Create SSSP folder in usb root location
• Copy .wgt test application inside of the SSSP folder
  
  
• Prepare the configuration file and copy it to SSSP Folder. Example URL would be: SSSP/sssp_config.xml
  
  
• Select Install from USB device option and run application (Home >> URL Launcher Settings >> Install from USB device )
  
  
• Set the Pin number-> Enter the PIN number, Default Pin is 0000.
  Note: Its required only once in app launching.
  
  
  
  
  
  
  Sample application installed and launches on LFD device.

3. Developer Mode

Connect your PC and LFD to the same network. (same network means same router)
Set “Developer Mode” in the LFD and install application on SSSP device.
For more information see, Remote Web Inspector

Description of the sssp_config.xml

Users must save packaged wgt app (such as HelloTizen.wgt) and mandatory configuration file ‘sssp_config.xml’ inside same folder.

Each time SSSP is starting it will perform a check for the existence of sssp_config.xml at the URL you provided.
If it exists on the Server URL, the system will perform different processes based on the differences between the online copy and local copy of sssp_config.xml.

1. If the version and name both are the same, SSSP will launch the app from the internal memory.

2. If the name is same but the version is different:

   • Launcher will show Updating banner

   • Downloads updated application package and copy of new sssp_config.xml

   • Launch the installed application

3. If name is different:

   • Launcher will show Downloading banner

   • Downloads new application package and remove old application if exist in memory.

   • Install new application and Launch

Attribute of the sssp_config.xml

The configuration file sssp_config.xml contains very important information about the web app.
As soon as user launch application from the URL Launcher, LFD Device looks for name, version and size information (size of the HelloTizen.wgt on disk) as shown below:

1. ver is the version of your application.
   Based on increment, new version of .wgt application will install on LFD.

2. size is how large your application’s wgt package is in kilobytes.
   "There is not enough storage space to download the URL launcher" error pop up will display on LFD, If free space is not available for application in LFD storage.
   There might be chances to come black screen on LFD, if size attribute is not used in sssp_config.xml file and required free space is not available on storage memory.

3. widgetname is the filename of your application wgt package not including the .wgt extension.
   For example the wgt file will be HelloTizen.wgt and the widgetname will be HelloTizen.

4. webtype is the optional parameter of sssp_config.xml file, to define the platform information.