Status: Draft

Starting with 2.8, Contextor Studio and Interactive can manage a new kind of solution packaging:

  • Contextor Studio generates the solution in an archive file containing all files which need to be executed locally by Contextor Interactive (project script ('PSC'), JavaScript libraries, HTML source files for popups, …),
    • This archive is protected to prevent any local modification,
    • 'Pure' web mash-up applications won't be embedded in the archive, and will remain hosted on the distribution server,
  • Solution is uploaded on the distribution server (shared network or web repository)
  • Contextor Interactive detects any update on the distribution server and download the archive to be executed locally,
  • Archive is downloaded when changes are detected, which optimizes:
    • Bandwidth: script files are only downloaded when necessary (instead of being downloaded at each restart or session opening),
    • Startup speed: once Contextor checked the local package is up to date (comparing version with network archive), the local version is used,
    • Reliability: in case the network or server is temporarily unreachable, Contextor Interactive can start using the local version.

This new kind of packaging is optional (although recommended on all new projects), it is still possible to directly publish the target project file on the shared network, so that it is directly downloaded and executed at each startup. These behaviors are managed through options on the command line.


This action generates a new export output folder into the export project sub-folder.

According to the project structure, this output folder contains:

  • 'local' folder into an output zip file, if the compression option item has been selected. If the compression is not selected, all files from the 'Local' folder are copied as raw data files.
  • 'server' folder,
  • Markup file 'key.xml',

The export output folder name has the following structure:

  • <project name>_<project version>

The markup file ensures the integrity for:

  • All file names
  • All data files
  • Properties from the section XML <Properties> into the main project file.

Finally, if one of these conditions is invalid, the export will be rejected and the project will be cancelled.

Note: The export action produces also a raw zip file in the root export folder with the following structure name: <project name>_<project version>.zip. This file can be used with Contextor Galaxy product.

Project testing and deployment

For the production phase, a shared location and a local folder will be defined:

  • Shared location (network or http) to publish the solution,
  • Local working directory to extract project files and generate logs,

Example:

  • Project structure:
projectName
    projectName.pscp, projectName.pscr,
    local 
        projectName.psc,
        key.xml,
        js\file.js, ...
    server
        portal\index.html, ...
    log
        LogCtxt.000, ...
    export
        projectName_1.0
            projectName.zip
            key.xml
            portal\index.html, ...
   updatepkg
	MyApp_1.0
		Install.bat
		<Files and Folders>	

Deployment:

The server structure will be:

http://intranet.net/production/
    projectName.zip
    key.xml
    portal\index.html, ...

The local structure will be:

c:\Users\<login>\Documents
    projectName
        projectName.psc,
        key.xml,
        js \ file.js,
    LogCtxt.000, ...

During the development phase, when launching the project in test mode from Contextor Studio, the following folders are used:

  • 'local' : associated with variable 'WkMng_Info/CurrentURL'
  • 'server' : associated with variable 'WkMng_Info/ServerURL'
  • 'log' : associated with variable 'WkMng_Info/CurrentDir'

The corresponding folders in production phase are:

  • '<work dir.>\<project name>' : associated with variable 'WkMng_Info/CurrentURL'
  • 'http://intranet.net/production/' : associated with variable 'WkMng_Info/ServerURL'
  • <work dir.> : associated with variable 'WkMng_Info/CurrentDir'

Using menu 'Settings > Studio Debugger > Option file…', an option file (or a list of files, separated by 'I') can be specified. This value is transmitted to Interactive at startup (using option '-option I -o' in command line).

At startup the value(s) are listed in '/GLOBAL/WkMng_Info/OptionFiles' node: the value can be managed by Interactive to setup different options (for instance, choose production or test environment).

When launching the project in test mode, the default folder used for mash-up web pages (located in 'server' folder) is:

  • <root folder>\<project name>\server\

When testing web pages, it can be necessary to use a real http URL to enable JavaScript scripting, or simulate a web server. In such a case, a web alias can be declared on Studio. The setting is modified using the menu: “View > Studio Debugger Settings > Web URL for testing…”:

A local Web URL can be created locally using Microsoft IIS (Internet Information Services), to make a web redirection from the local files. Ex.:

Folder can also be redirected to a remote Web server (supposing the pages were published on this server). Ex.: