The beta version of the CloudaIDE Framework works with FirebirdSQL, Oracle and PostgresSQL databases.

CloudaIDE Designer Installation

CloudaIDE designer (programmer tool) for the CloudaIDE Framework is provided for 64 bit Windows and Linux environments. CloudaIDE Designer is an Eclipse application. Therefore many things relevant to Eclipse are also relevant to CloudaIDE.

Database Server Objects Installation

In order to use CloudaIDE the database server has to have special supporting objects. Installation of these objects depends on the database server.

To install CloudaIDE objects the script mroovka_install_oracle.sql has to be run as user sys or other dba.

To install the demo application import the mroovka_demo_oracle.dmp file using impdp. The file creates the mroovka_demo user. The password is mroovka. Change it after import.

To install CloudaIDE objects the srcipt mroovka_install_fb.sql has to be run.

To install the demo application restore the database in file demo.fbk. This database contains CloudaIDE objects, so installation of them is not advised.

To install CloudaIDE objects the srcipt mroovka_install_pg.sql has to be run. It installs public objects.

To install the demo application use the pg_dump mroovka_demo_pg.sql script. First create a database using.

createdb -T template0 mroovka_db

where mroovka_db is a database name, where you want CloudaIDE demo to reside.

If there is no user mroovka_demo on the database server, create it.

Next import the objects and data using:

psql mroovka_db < mroovka_demo_pg.sql

To install CloudaIDE objects the script Cloudaide_install_mysql.sql has to be run. It installs in the database objects necessary to run CloudaIDE.

Alternatively to install the demo application use the CloudaIDE_Demo.sql script. This script contains cloudaide_install_mysql script. You have to run either pure system instalation (above) either demo installation script. First create a database using.

To install the demo application use the CloudaIDE_Demo.sql script. First create a database using.

mysql> create database mroovka_test;

mysql> use mroovka_test;

mysql> source CloudaIDE_Demo.sql

The definer of the objects is `MROOVKA_DEMO`@`%`, therefore you shoud create this user and run the demo installation script as this user. Alternatively you can do respective user string replacement in order to run the script as other user.

You can use also MySQL Workbench's Server ➜ Data Import option, using CloudaIDE_Demo.sql as the import source.

Administration Application

CloudaIDE distribution contains the Administration Application. Administration application is a tool to administer/configure the CloudaIDE environment.

You don't have to install CloudaIDE right from the start to develop software. The compiled admin application can be found within supplied template Tomcat (at.xxx.tar.gz), under %TOMCAT_ROOT%/webapps directory. There are two admin versions: adminMSQL (for MySQL) and admin for other databases. To configure JDBC connection parameters use xml files with respective names, that reside in the %TOMCAT_ROOT%/conf/Catalina/localhost directory. CloudaIDE also supplies source code for the admin application. The source code can be found in the "projectsxxx.zip" file.

On startup the application displays login form.

CloudIDE Administration Application login page

Figure 1.

CloudIDE Administration Application login page

The first user is "admin" and the password is "changeoninstall".

After logging in the main console is displayed.

CloudIDE Administration Application main console

Figure 2.

CloudIDE Administration Application main console

Immediately after installation it is recommended to change admin password. Choose "My Data" option.

CloudIDE Administration Application "My Data" form

Figure 3.

CloudIDE Administration Application "My Data" form

Server setup

Server setup option gives the possibility to configure CloudaIDE server as a whole.

CloudIDE Administration Application "Setup" form

Figure 4.

CloudIDE Administration Application "Setup" form

Compatibility level
(read only) Server objects compatibility level
SMTP Host Address
address of the SMTP server used by system to send e-mails
SMTP Host Port
port of the SMTP server used by system to send e-mails
SMTP Authentication Username
name of the user used to authenticate to SMTP server
SMTP Authentication Password
password of the user used to authenticate to SMTP server
Use SSL/TLS
  • yes – encrypted connection
  • no – plain connection
  • after connection is established (STARTLS) – switch to encrypted mode after establishing a connection
Default Email From address
an address substituted into e-mail from field if it is empty
URL of the User Self service
URL of the User Self service application

Registering applications

The "Applications" option gives the possibility to register and set properties of an applications

CloudIDE Administration Application "Applications" form

Figure 5.

CloudIDE Administration Application "Applications" form

To register an application fill in the following application data:

Code
the code of an application from application configuration file
Requires Grant
the right to use this application has to be granted for a particular user
Authentication Method
one of four values:
  • None – no user authentication is requested
  • Table – system stores the password data in the CloudaIDE table
  • Database – system uses user database account data to authenticate an user
  • CAS – system uses the password data in the CloudaIDE, but the authentication is carried out by CAS. This gives Single Sign On capability
BIRT URL
URL of BIRT reporting server (including trailing slash)
CAS URL
URL of CAS authentication server (including trailing slash)

The administrator enters also a list of authorizations recognizable by the application. Authorization Code is the code that can be granted to a user.

User Management

CloudIDE Administration Application "Users" form

Figure 6.

CloudIDE Administration Application "Users" form

After choosing the “Users” option the administrator can manage users data and privileges

Login
users login – always in lower case
Active
has to be checked to let user log-in to any protected application. After user self-registration this checkbox is unchecked. The admin has to accept the user
Blocked
if for any reason the user is not allowed to log-in this checkbox is checked
Email Verified
user responded to e-mail verification e-mail message
Email
stored in lower case

By checking "Granted" checkbox in "Application Access" table the administrator grants the access to an application, that requires grant.

By checking "Granted" checkbox in "Authorizations" table the administrator grants an authorization (if the application has any) to the user.

Sessions

Sessions Form displays information about user sessions

CloudIDE Administration Application "Sessions" form

Figure 7.

CloudIDE Administration Application "Sessions" form

System Log

System Log form displays system log entries

CloudIDE Administration Application "Log" form

Figure 8.

CloudIDE Administration Application "Log" form

User self administration

User self administration utility (cru) lets the user to:

  • register and account
  • restore forgotten password
CloudIDE User Registration Service

Figure 9.

CloudIDE User Registration Service

Reports Installation

The distribution media contains birt_mroovka application. You have to modify BIRT_VIEWER_WORKING_FOLDER parameter value WEB-INF/web.xml file to point to the folder containing reports definitions:

<!-- Report resources directory for preview. Defaults to ${birt home} --> <context-param> <param-name>BIRT_VIEWER_WORKING_FOLDER</param-name> <param-value>/usr/reports</param-value> </context-param>

You have also to modify conf/Catalina/localhost/birt_mroovka.xml to set proper datasource parameters.

The develop report for the supplied preconfigured Tomcat server use BIRT Framework version 2.6.2. The Birt Framework 4.4.2 contains a bug 431702 that makes the development with it hard.

CloudaIDE distribution contains workspace for the respectful OS. The workspace contains following projects:

  • Admin – administration utility
  • cru – user self service utility
  • Demo – demo application
  • AdminMSQL – administration utility for the MySQL database
  • DemoMSQL – demo application for the MySQL database

You have to comment/uncomment and modify mroovka.formica_cfg file. You have to set database JDBC url and user and password data to fit the database installation you use to develop the application.

The supplied tomcat server /conf/Catalina/localhost directory contains files:

  • demo.xml
  • cru.xml
  • admin.xml
  • demoMSQL.xml
  • adminMSQL.xml

The contents of these files should be modified to fit your deployment

The webapps directory contains (among others) demo, cru, admin, adminMSQL, demoMSQL directories that contain respectful applications.

Upgrades

CloudaIDE has three part version number major.minor.compilation eg 1.0.345. Sometimes there will new versions of Cloudaide come to existence.

On every upgrade CloudaIDE projects have to be upgraded. To do it:

  1. Select the CloudaIDE Project (demo)
  2. Launch popup menu (right clik)
  3. Select CloudaIDE ➜ Project Upgrade (the option will show up if the upgrade is necessary)
Project upgrade

Figure 10.

Project upgrade

After clicking on the option a wizard will show up:

Upgrade Wizard creates a new project. Copies mroovka.formica_cfg file and contens of war/mroovka, mroovka and mroovka_java directories. Other changes (if there were such) have to be ported from old project manually. Old project is backuped up in backup project. The project is closed.

Care should be taken before upgrade'ing CloudaIDE. The very good idea is to make a backup copy of entire workspace.

Project upgrade wizard

Figure 11.

Project upgrade wizard

If the CloudaIDE has major.minor numbers greater than database object compatibilty level then server upgrade is necessary. To do it select Server upgrade option of CloudaIDE Actions toolbar button.

Server upgrade

Figure 12.

Server upgrade

Next follow wizard instructions:

  1. Choose database system
  2. Click "Next"
Server upgrade wizard - first step

Figure 13.

Server upgrade wizard - first step

Edit JDBC URL, user and password. You should choose the user with proper priviledges (the one CloudaIDE was installed for the first time). Click "Connect to the database", then "Next"

Server upgrade wizard - second step

Figure 14.

Server upgrade wizard - second step

The wizard will display compatibility levels and depending on them will carry out the upgrade.

Server upgrade wizard - third step

Figure 15.

Server upgrade wizard - third step

Licence Key Installation

Immediately after installation the Designer has Community Edition key installed. To check the fact use CloudaIde Action – Show Licence option

Show Licence option

Figure 16.

Show Licence option

This option will display Licence Information Dialog

This Dialog informs the user about the date of release of the product, and that the licence type is Community Edition

Licence Information Dialog -  Community Edition

Figure 17.

Licence Information Dialog - Community Edition

To install Pro Licence key use CloudaIDE Actions Install Licence option

Install Licence option

Figure 18.

Install Licence option

This option will launch a File Browse Dialog for licence key file

Select licence key file

Figure 19.

Select licence key file

After the installation the Licence Information Dialog is displayed

Licence Information Dialog -  PRO

Figure 20.

Licence Information Dialog - PRO