- User contributions [en]

WhizniumSBE Wikipedia

2019-10-28T05:44:40Z

Mpsitech:

This page describes the four-step Whiznium early adopter onboarding procedure.

PLEASE NOTE: while the early adopter onboarding procedure is ready, it is advisable to go through the steps with the complimentary help of our engineers. Please drop us a line at contact@mpsitechnologies.com for assistance!

The four steps are:

1. [[Creating an account]]

2. [[Setting up your local environment]]

3. [[Launching your dedicated cloud-based Whiznium service]]

4. [[Using your dedicated cloud-based Whiznium service]]

WhizniumSBE Wikipedia

2019-10-28T05:44:02Z

Mpsitech:

This page describes the four-step Whiznium early adopter onboarding procedure.

PLEASE NOTE: while the early adopter onboarding procedure is ready, it is advisable to go through the steps with the complimentary help of our engineers. Please drop us a line at <a href="mailtocontact@mpsitechnologies.com"></a> for assistance.

The four steps are:

1. [[Creating an account]]

2. [[Setting up your local environment]]

3. [[Launching your dedicated cloud-based Whiznium service]]

4. [[Using your dedicated cloud-based Whiznium service]]

WhizniumSBE Wikipedia

2019-10-28T05:43:33Z

Mpsitech:

This page describes the four-step Whiznium early adopter onboarding procedure.

PLEASE NOTE: while the early adopter onboarding procedure is ready, it is advisable to go through the steps with the complimentary help of our engineers. Please drop us a line at <a href="mailto:contact@mpsitechnologies.com">contact@mpsitechnologies.com</a> for assistance.

The four steps are:

1. [[Creating an account]]

2. [[Setting up your local environment]]

3. [[Launching your dedicated cloud-based Whiznium service]]

4. [[Using your dedicated cloud-based Whiznium service]]

WhizniumSBE Wikipedia

2019-10-28T05:42:44Z

Mpsitech:

This page describes the four-step Whiznium early adopter onboarding procedure.

PLEASE NOTE: while the early adopter onboarding procedure is ready, it is advisable to go through the steps with the complimentary help of our engineers. Please drop us a line at contact@mpsitechnologies.com for assistance.

The four steps are:

1. [[Creating an account]]

2. [[Setting up your local environment]]

3. [[Launching your dedicated cloud-based Whiznium service]]

4. [[Using your dedicated cloud-based Whiznium service]]

WhizniumSBE Wikipedia

2019-10-28T05:41:49Z

Mpsitech:

This page describes the four-step Whiznium early adopter onboarding procedure.

{{font color|red|yellow|PLEASE NOTE: while the early adopter onboarding procedure is ready, it is advisable to go through the steps with the complimentary help of our engineers. Please drop us a line at contact@mpsitechnologies.com for assistance.}}

The four steps are:

1. [[Creating an account]]

2. [[Setting up your local environment]]

3. [[Launching your dedicated cloud-based Whiznium service]]

4. [[Using your dedicated cloud-based Whiznium service]]

Setting up your local environment

2019-08-26T11:00:18Z

Mpsitech:

For convenience, MPSI provides a self-contained local folder structure for building WhizniumSBE and WhizniumDBE projects. The paths are configured such that no modifications to the workstation's file system outside of this folder structure are necessary.

Four tested configurations are available, two of which are catering to Yocto/PetaLinux cross-compile environments:

1. apalis: for Toradex's [https://developer.toradex.com/products/apalis-imx6 Apalis iMX6] board featuring dual/quad Cortex-A9 ARM cores

2. arty: for the [https://reference.digilentinc.com/reference/programmable-logic/arty-z7/start Digilent Arty Z7] board which is built around Xilinx's Z7010/Z7020 Zynq All-Programmable SOC, featuring dual Cortex-A9 ARM cores and FPGA fabric

3. linux: for ubuntu workstations, tested for 16.04 and 18.04

4. mac: for Apple computers

== Prerequisites ==

1. apalis: have your Yocto project set up on your workstation

2. arty: have your PetaLinux project set up on your workstation

3. linux: the following packages are required:

sudo apt install make gcc libxml2-dev mysql-client mysql-server libmysqlclient-dev postgresql postgresql-contrib libpq-dev sqlite3 libsqlite3-dev libmicrohttpd-dev libcurl3-dev libjpeg-dev

4. mac: the following installations are required (you may consider using Homebrew instead of building from source):

MySQL from https://dev.mysql.com/downloads/mysql/ 8.0.16, use Legacy Password Encryption

libcurl: https://curl.haxx.se/download.html, installation should end up in /usr/include and /usr/lib

libxml2: ftp://xmlsoft.org/libxml2, installation should end up in /usr/local/include/libxml2 and /usr/local/lib

libmicrohttpd: https://ftp.gnu.org/gnu/libmicrohttpd, installation should end up in /usr/local/include and /usr/local/lib

libjpeg-turbo: https://sourceforge.net/projects/libjpeg-turbo/files, installation should end up in /opt/libjpeg-turbo/include and /opt/libjpeg-turbo/lib

== Download and configure ==

The Whiznium local folder structure is available at https://mpsitech-public.s3.amazonaws.com/whiznium_root.tgz. Download it and unpack it at your location of choice. The unpacked folder will be your Whiznium root directory and a shell variable ${WHIZROOT} will be defined for it.

== Build essentials ==

Carefully follow the instructions in ${WHIZROOT}/setup_<machine type>.sh: this file contains shell command snippets but is not meant to be executed as a whole.

A note on the 'manually edit ${WHIZROOT}/srcrep/sbecore/config.h' task: in this header file you define which DBMS types are available on your system. The options include MariaDB (SBECORE_MAR), MySQL (SBECORE_MY), PostgreSQL (SBECORE_PG) and SQLite3 (SBECORE_LITE).

The default configuration is 1. apalis SBECORE_LITE, 2. arty SBECORE_LITE, 3. linux SBECORE_MY + SBECORE_PG, 4. mac SBECORE_MY.

Setting up your local environment

2019-08-26T09:34:12Z

Mpsitech:

For convenience, MPSI provides a self-contained local folder structure for building WhizniumSBE and WhizniumDBE projects. The paths are configured such that no modifications to the workstation's file system outside of this folder structure are necessary.

Four tested configurations are available, two of which are catering to Yocto/PetaLinux cross-compile environments:

1. apalis: for Toradex's [https://developer.toradex.com/products/apalis-imx6 Apalis iMX6] board featuring dual/quad Cortex-A9 ARM cores

2. arty: for the [https://reference.digilentinc.com/reference/programmable-logic/arty-z7/start Digilent Arty Z7] board which is built around Xilinx's Z7010/Z7020 Zynq All-Programmable SOC, featuring dual Cortex-A9 ARM cores and FPGA fabric

3. linux: for ubuntu workstations, tested for 16.04 and 18.04

4. mac: for Apple computers

== Prerequisites ==

1. apalis: have your Yocto project set up on your workstation

2. arty: have your PetaLinux project set up on your workstation

3. linux: the following packages are required:

sudo apt install make gcc libxml2-dev mysql-client mysql-server libmysqlclient-dev postgresql postgresql-contrib libpq-dev sqlite3 libsqlite3-dev libmicrohttpd-dev libcurl3-dev libjpeg-dev

4. mac: the following installations are required (you may consider using Homebrew instead of building from source):

MySQL from https://dev.mysql.com/downloads/mysql/ 8.0.16, use Legacy Password Encryption

libcurl: https://curl.haxx.se/download.html, installation should end up in /usr/include and /usr/lib

libxml2: ftp://xmlsoft.org/libxml2, installation should end up in /usr/local/include/libxml2 and /usr/local/lib

libmicrohttpd: https://ftp.gnu.org/gnu/libmicrohttpd, installation should end up in /usr/local/include and /usr/local/lib

== Download and configure ==

The Whiznium local folder structure is available at https://mpsitech-public.s3.amazonaws.com/whiznium_root.tgz. Download it and unpack it at your location of choice. The unpacked folder will be your Whiznium root directory and a shell variable ${WHIZROOT} will be defined for it.

== Build essentials ==

Carefully follow the instructions in ${WHIZROOT}/setup_<machine type>.sh: this file contains shell command snippets but is not meant to be executed as a whole.

A note on the 'manually edit ${WHIZROOT}/srcrep/sbecore/config.h' task: in this header file you define which DBMS types are available on your system. The options include MariaDB (SBECORE_MAR), MySQL (SBECORE_MY), PostgreSQL (SBECORE_PG) and SQLite3 (SBECORE_LITE).

The default configuration is 1. apalis SBECORE_LITE, 2. arty SBECORE_LITE, 3. linux SBECORE_MY + SBECORE_PG, 4. mac SBECORE_MY.

HelloWhiznium

2019-08-25T10:58:50Z

Mpsitech:

Building HelloWhiznium

<pre>
cd ${WHIZROOT[_CCH]}/srcrep/hwzd

cd _rls/ezdevhwzd_<machine>
./checkout.sh

cd [${SYSROOT}]${WHIZROOT}/src/ezdevhwzd
./makeall.sh
</pre>

<pre>
cd ${WHIZROOT[_CCH]}/srcrep/hlwz

cd _rls/dbshlwz_<machine>
./checkout.sh
cd ../hlwzcmbd_<machine>
./checkout.sh
cd ../webapphlwz_<machine>
./checkout.sh

cd [${SYSROOT}]${WHIZROOT}/src/dbshlwz
./makeall.sh
cd ../hlwzcmbd
./make.sh all
</pre>

Generate acv/hlwz and tmp/hlwz directories

Running HelloWhiznium for the first time

The executable directory for the HelloWhiznium combined engine Hlwzcmbd is ${WHIZROOT}/bin/hlwzcmbd.

Copy the preferences file PrefHlwzcmbd.xml from ${WHIZROOT[_CCH]}/srcrep/hlzw/_ini/hlwzcmbd_<machine> to the executable directory.

Perform some required customizations:

<pre>
<StgHlwzAppsrv>
<Si sref="port"> application server port of choice, e.g. 13100 </Si>
<Si sref="https"> true if you would like to use secure communication (see below) </Si>
</StgHlwzAppsrv>
<StgHlwzcmbd>
<Si sref="jobprcn"> number of job processor threads, should be at least 2 and otherwise match the number of cores </Si>
...
</StgHlwzcmbd>
</pre>

<StgHlwzDatabase> 
:<Si sref="srefIxDbsVDbstype">my</Si> 
:... 
:<Si sref="dbsname">DbsHlwz</Si> 
:<Si sref="username">mpsitech</Si> 
:<Si sref="password">asdf1234</Si> 
:<Si sref="ip">127.0.0.1</Si> 
:<Si sref="port">3306</Si> 
</StgHlwzDatabase> 

- or -

<StgHlwzDatabase> 
:<Si sref="srefIxDbsVDbstype">lite</Si> 
:<Si sref="dbspath">$WHIZROOT/bin/hlwzcmbd/DbsHlwz.sql</Si> 
:... 
</StgHlwzDatabase> 

<StgHlwzPath> 
:<Si sref="acvpath"> $WHIZROOT/acv/hlwz </Si> 
:... 
:<Si sref="tmppath"> $WHIZROOT/tmp/hlwz </Si> 
:<Si sref="webpath"> $WHIZROOT/web/apphlwz </Si> 
:... 
</StgHlwzPath> 

If you would like to use HTTPS for the application server, you need to create a private/public key pair, e.g. using OpenSSL. In the executable directory, run:

openssl genrsa -out server.key 4096
openssl req -days 365 -out server.pem -new -x509 -key server.key

Set up the database:

MySQL database

sudo mysql -p < ${WHIZROOT}/srcrep/hlwz/_ini/dbshlwz/CreateDbsHlwzMy.sql

The two 'CREATE USER ...' lines need to be commented out in case the user already exists.

SQLite database

In the executable directory, run

sqlite3 DbsHlwz.sql 
sqlite3> .read ${WHIZROOT}/srcrep/hlwz/_ini/dbshlwz/CreateDbsHlwzLite.sql 
sqlite3> .quit 

As within sqlite3 the shell variable ${WHIZROOT} is unknown, you'll need to expand it manually.

If you are in a cross-compile environment (machines apalis and arty), you need to secure-copy a number of files to the target machine. Exemplary commands on the host machine read:

cd ${WHIZROOT}
export set IP=192.168.2.26
scp -r bin/hlwzcmbd root@${IP}:whiznium/bin
scp -r acv/hlwz root@${IP}:whiznium/acv
scp -r tmp/hlwz root@${IP}:whiznium/tmp
scp -r web/apphlwz root@${IP}:whiznium/web

Run HelloWhiznium for the first time and populate:

Hlwzcmbd >> clearAll

Use Chrome/Safari and go to https://127.0.0.1:13100, log in as 'temp'/'asdf1234'

Load initialization data.

${WHIZROOT[_CCH]}/srcrep/hlwz/_ini/hlwzcmbd/IexHlwzIni.xml

From now you can log in as 'hlwzuser'/'asdf1234' or 'hlwzuserdech'/'asdf1234'.

HelloWhiznium

2019-08-24T12:27:17Z

Mpsitech:

Building HelloWhiznium

<pre>
cd ${WHIZROOT[_CCH]}/srcrep/hlwz

cd _rls/dbshlwz_<machine>
./checkout.sh
cd ../hlwzcmbd_<machine>
./checkout.sh
cd ../webapphlwz_<machine>
./checkout.sh

cd [${SYSROOT}]${WHIZROOT}/src/dbshlwz
./makeall.sh
cd ../hlwzcmbd
./make.sh all
</pre>

Generate acv/hlwz and tmp/hlwz directories

Running HelloWhiznium for the first time

The executable directory for the HelloWhiznium combined engine Hlwzcmbd is ${WHIZROOT}/bin/hlwzcmbd.

Copy the preferences file PrefHlwzcmbd.xml from ${WHIZROOT[_CCH]}/srcrep/hlzw/_ini/hlwzcmbd_<machine> to the executable directory.

Perform some required customizations:

<pre>
<StgHlwzAppsrv>
<Si sref="port"> application server port of choice, e.g. 13100 </Si>
<Si sref="https"> true if you would like to use secure communication (see below) </Si>
</StgHlwzAppsrv>
<StgHlwzcmbd>
<Si sref="jobprcn"> number of job processor threads, should be at least 2 and otherwise match the number of cores </Si>
...
</StgHlwzcmbd>
</pre>

<StgHlwzDatabase> 
:<Si sref="srefIxDbsVDbstype">my</Si> 
:... 
:<Si sref="dbsname">DbsHlwz</Si> 
:<Si sref="username">mpsitech</Si> 
:<Si sref="password">asdf1234</Si> 
:<Si sref="ip">127.0.0.1</Si> 
:<Si sref="port">3306</Si> 
</StgHlwzDatabase> 

- or -

<StgHlwzDatabase> 
:<Si sref="srefIxDbsVDbstype">lite</Si> 
:<Si sref="dbspath">$WHIZROOT/bin/hlwzcmbd/DbsHlwz.sql</Si> 
:... 
</StgHlwzDatabase> 

<StgHlwzPath> 
:<Si sref="acvpath"> $WHIZROOT/acv/hlwz </Si> 
:... 
:<Si sref="tmppath"> $WHIZROOT/tmp/hlwz </Si> 
:<Si sref="webpath"> $WHIZROOT/web/apphlwz </Si> 
:... 
</StgHlwzPath> 

If you would like to use HTTPS for the application server, you need to create a private/public key pair, e.g. using OpenSSL. In the executable directory, run:

openssl genrsa -out server.key 4096
openssl req -days 365 -out server.pem -new -x509 -key server.key

Set up the database:

MySQL database

sudo mysql -p < ${WHIZROOT}/srcrep/hlwz/_ini/dbshlwz/CreateDbsHlwzMy.sql

The two 'CREATE USER ...' lines need to be commented out in case the user already exists.

SQLite database

In the executable directory, run

sqlite3 DbsHlwz.sql 
sqlite3> .read ${WHIZROOT}/srcrep/hlwz/_ini/dbshlwz/CreateDbsHlwzLite.sql 
sqlite3> .quit 

As within sqlite3 the shell variable ${WHIZROOT} is unknown, you'll need to expand it manually.

If you are in a cross-compile environment (machines apalis and arty), you need to secure-copy a number of files to the target machine. Exemplary commands on the host machine read:

cd ${WHIZROOT}
export set IP=192.168.2.26
scp -r bin/hlwzcmbd root@${IP}:whiznium/bin
scp -r acv/hlwz root@${IP}:whiznium/acv
scp -r tmp/hlwz root@${IP}:whiznium/tmp
scp -r web/apphlwz root@${IP}:whiznium/web

Run HelloWhiznium for the first time and populate:

Hlwzcmbd >> clearAll

Use Chrome/Safari and go to https://127.0.0.1:13100, log in as 'temp'/'asdf1234'

Load initialization data.

${WHIZROOT[_CCH]}/srcrep/hlwz/_ini/hlwzcmbd/IexHlwzIni.xml

From now you can log in as 'hlwzuser'/'asdf1234' or 'hlwzuserdech'/'asdf1234'.

HelloWhiznium

2019-08-24T11:01:15Z

Mpsitech:

Building HelloWhiznium

<pre>
cd ${WHIZROOT[_CCH]}/srcrep/hlwz

cd _rls/dbshlwz_<machine>
./checkout.sh
cd ../hlwzcmbd_<machine>
./checkout.sh
cd ../webapphlwz_<machine>
./checkout.sh

cd [${SYSROOT}]${WHIZROOT}/src/dbshlwz
./makeall.sh
cd ../hlwzcmbd
./make.sh all
</pre>

Generate acv/hlwz and tmp/hlwz directories

Running HelloWhiznium for the first time

The executable directory for the HelloWhiznium combined engine Hlwzcmbd is ${WHIZROOT}/bin/hlwzcmbd.

Copy the preferences file PrefHlwzcmbd.xml from ${WHIZROOT[_CCH]}/srcrep/hlzw/_ini/hlwzcmbd_<machine> to the executable directory.

Perform some required customizations:

<pre>
<StgHlwzAppsrv>
<Si sref="port"> application server port of choice, e.g. 13100 </Si>
<Si sref="https"> true if you would like to use secure communication (see below) </Si>
</StgHlwzAppsrv>
<StgHlwzcmbd>
<Si sref="jobprcn"> number of job processor threads, should be at least 2 and otherwise match the number of cores </Si>
...
</StgHlwzcmbd>
</pre>

<StgHlwzDatabase> 
:<Si sref="srefIxDbsVDbstype">my</Si> 
:... 
:<Si sref="dbsname">DbsHlwz</Si> 
:<Si sref="username">mpsitech</Si> 
:<Si sref="password">asdf1234</Si> 
:<Si sref="ip">127.0.0.1</Si> 
:<Si sref="port">3306</Si> 
</StgHlwzDatabase> 

- or -

<StgHlwzDatabase> 
:<Si sref="srefIxDbsVDbstype">lite</Si> 
:<Si sref="dbspath">$WHIZROOT/bin/hlwzcmbd/DbsHlwz.sql</Si> 
:... 
</StgHlwzDatabase> 

<StgHlwzPath> 
:<Si sref="acvpath"> $WHIZROOT/acv/hlwz </Si> 
:... 
:<Si sref="tmppath"> $WHIZROOT/tmp/hlwz </Si> 
:<Si sref="webpath"> $WHIZROOT/web/apphlwz </Si> 
:... 
</StgHlwzPath> 

If you would like to use HTTPS for the application server, you need to create a private/public key pair, e.g. using OpenSSL. In the executable directory, run:

openssl genrsa -out server.key 4096
openssl req -days 365 -out server.pem -new -x509 -key server.key

Set up the database:

MySQL database

sudo mysql -p < ${WHIZROOT}/srcrep/hlwz/_ini/dbshlwz/CreateDbsHlwzMy.sql

The two 'CREATE USER ...' lines need to be commented out in case the user already exists.

SQLite database

In the executable directory, run

sqlite3 DbsHlwz.sql 
sqlite3> .read ${WHIZROOT}/srcrep/hlwz/_ini/dbshlwz/CreateDbsHlwzLite.sql 
sqlite3> .quit 

As within sqlite3 the shell variable ${WHIZROOT} is unknown, you'll need to expand it manually.

Run HelloWhiznium for the first time and populate:

Hlwzcmbd >> clearAll

Use Chrome/Safari and go to https://127.0.0.1:13100, log in as 'temp'/'asdf1234'

Load initialization data.

${WHIZROOT[_CCH]}/srcrep/hlwz/_ini/hlwzcmbd/IexHlwzIni.xml

From now you can log in as 'hlwzuser'/'asdf1234' or 'hlwzuserdech'/'asdf1234'.

HelloWhiznium

2019-08-24T10:59:27Z

Mpsitech:

Building HelloWhiznium

<pre>
cd ${WHIZROOT[_CCH]}/srcrep/hlwz

cd _rls/dbshlwz_<machine>
./checkout.sh
cd ../hlwzcmbd_<machine>
./checkout.sh
cd ../webapphlwz_<machine>
./checkout.sh

cd ${WHIZROOT}/src/dbshlwz
./makeall.sh
cd ../hlwzcmbd
./make.sh all
</pre>

Generate acv/hlwz and tmp/hlwz directories

Running HelloWhiznium for the first time

The executable directory for the HelloWhiznium combined engine Hlwzcmbd is ${WHIZROOT}/bin/hlwzcmbd.

Copy the preferences file PrefHlwzcmbd.xml from ${WHIZROOT[_CCH]}/srcrep/hlzw/_ini/hlwzcmbd_<machine> to the executable directory.

Perform some required customizations:

<pre>
<StgHlwzAppsrv>
<Si sref="port"> application server port of choice, e.g. 13100 </Si>
<Si sref="https"> true if you would like to use secure communication (see below) </Si>
</StgHlwzAppsrv>
<StgHlwzcmbd>
<Si sref="jobprcn"> number of job processor threads, should be at least 2 and otherwise match the number of cores </Si>
...
</StgHlwzcmbd>
</pre>

<StgHlwzDatabase> 
:<Si sref="srefIxDbsVDbstype">my</Si> 
:... 
:<Si sref="dbsname">DbsHlwz</Si> 
:<Si sref="username">mpsitech</Si> 
:<Si sref="password">asdf1234</Si> 
:<Si sref="ip">127.0.0.1</Si> 
:<Si sref="port">3306</Si> 
</StgHlwzDatabase> 

- or -

<StgHlwzDatabase> 
:<Si sref="srefIxDbsVDbstype">lite</Si> 
:<Si sref="dbspath">$WHIZROOT/bin/hlwzcmbd/DbsHlwz.sql</Si> 
:... 
</StgHlwzDatabase> 

<StgHlwzPath> 
:<Si sref="acvpath"> $WHIZROOT/acv/hlwz </Si> 
:... 
:<Si sref="tmppath"> $WHIZROOT/tmp/hlwz </Si> 
:<Si sref="webpath"> $WHIZROOT/web/apphlwz </Si> 
:... 
</StgHlwzPath> 

If you would like to use HTTPS for the application server, you need to create a private/public key pair, e.g. using OpenSSL. In the executable directory, run:

openssl genrsa -out server.key 4096
openssl req -days 365 -out server.pem -new -x509 -key server.key

Set up the database:

MySQL database

sudo mysql -p < ${WHIZROOT}/srcrep/hlwz/_ini/dbshlwz/CreateDbsHlwzMy.sql

The two 'CREATE USER ...' lines need to be commented out in case the user already exists.

SQLite database

In the executable directory, run

sqlite3 DbsHlwz.sql 
sqlite3> .read ${WHIZROOT}/srcrep/hlwz/_ini/dbshlwz/CreateDbsHlwzLite.sql 
sqlite3> .quit 

As within sqlite3 the shell variable ${WHIZROOT} is unknown, you'll need to expand it manually.

Run HelloWhiznium for the first time and populate:

Hlwzcmbd >> clearAll

Use Chrome/Safari and go to https://127.0.0.1:13100, log in as 'temp'/'asdf1234'

Load initialization data.

${WHIZROOT[_CCH]}/srcrep/hlwz/_ini/hlwzcmbd/IexHlwzIni.xml

From now you can log in as 'hlwzuser'/'asdf1234' or 'hlwzuserdech'/'asdf1234'.

HelloWhiznium

2019-08-24T10:24:52Z

Mpsitech:

Building HelloWhiznium

Generate acv/hlwz and tmp/hlwz directories

Running HelloWhiznium for the first time

The executable directory for the HelloWhiznium combined engine Hlwzcmbd is ${WHIZROOT}/bin/hlwzcmbd.

Copy the preferences file PrefHlwzcmbd.xml from ${WHIZROOT[_CCH]}/srcrep/hlzw/_ini/hlwzcmbd_<machine> to the executable directory.

Perform some required customizations:

<pre>
<StgHlwzAppsrv>
<Si sref="port"> application server port of choice, e.g. 13100 </Si>
<Si sref="https"> true if you would like to use secure communication (see below) </Si>
</StgHlwzAppsrv>
<StgHlwzcmbd>
<Si sref="jobprcn"> number of job processor threads, should be at least 2 and otherwise match the number of cores </Si>
...
</StgHlwzcmbd>
</pre>

<StgHlwzDatabase> 
:<Si sref="srefIxDbsVDbstype">my</Si> 
:... 
:<Si sref="dbsname">DbsHlwz</Si> 
:<Si sref="username">mpsitech</Si> 
:<Si sref="password">asdf1234</Si> 
:<Si sref="ip">127.0.0.1</Si> 
:<Si sref="port">3306</Si> 
</StgHlwzDatabase> 

- or -

<StgHlwzDatabase> 
:<Si sref="srefIxDbsVDbstype">lite</Si> 
:<Si sref="dbspath">$WHIZROOT/bin/hlwzcmbd/DbsHlwz.sql</Si> 
:... 
</StgHlwzDatabase> 

<StgHlwzPath> 
:<Si sref="acvpath"> $WHIZROOT/acv/hlwz </Si> 
:... 
:<Si sref="tmppath"> $WHIZROOT/tmp/hlwz </Si> 
:<Si sref="webpath"> $WHIZROOT/web/apphlwz </Si> 
:... 
</StgHlwzPath> 

If you would like to use HTTPS for the application server, you need to create a private/public key pair, e.g. using OpenSSL. In the executable directory, run:

openssl genrsa -out server.key 4096
openssl req -days 365 -out server.pem -new -x509 -key server.key

Set up the database:

MySQL database

sudo mysql -p < ${WHIZROOT}/srcrep/hlwz/_ini/dbshlwz/CreateDbsHlwzMy.sql

The two 'CREATE USER ...' lines need to be commented out in case the user already exists.

SQLite database

In the executable directory, run

sqlite3 DbsHlwz.sql 
sqlite3> .read ${WHIZROOT}/srcrep/hlwz/_ini/dbshlwz/CreateDbsHlwzLite.sql 
sqlite3> .quit 

As within sqlite3 the shell variable ${WHIZROOT} is unknown, you'll need to expand it manually.

Run HelloWhiznium for the first time and populate:

Hlwzcmbd >> clearAll

Use Chrome/Safari and go to https://127.0.0.1:13100, log in as 'temp'/'asdf1234'

Load initialization data.

${WHIZROOT[_CCH]}/srcrep/hlwz/_ini/hlwzcmbd/IexHlwzIni.xml

From now you can log in as 'hlwzuser'/'asdf1234' or 'hlwzuserdech'/'asdf1234'.

HelloWhiznium

2019-08-24T08:08:16Z

Mpsitech:

Building HelloWhiznium

Running HelloWhiznium for the first time

Copy the preferences file from ... to ... .

If you would like to use HTTPS server, you need to create a private/public key pair, e.g. using OpenSSL. In the executable directory, run

and rename the generated files

mv ... server.pem
mv ... server.key

Set up the database:

MySQL database

sudo mysql -p < ${WHIZROOT}/srcrep/hlwz/_ini/dbshlwz/CreateDbsHlwzMy.sql

The two 'CREATE USER ...' line needs to be commented out in case the user already exists.

SQLIte database

In the executable directory, run

sqlite3 DbsHlwz.sql
sqlite3> .read ${WHIZROOT}/srcrep/hlwz/_ini/dbshlwz/CreateDbsHlwzLite.sql

HelloWhiznium

2019-08-24T08:04:21Z

Mpsitech:

Building HelloWhiznium

Running HelloWhiznium for the first time

Copy the preferences file from ... to ... .

If you would like to use HTTPS server, you need to create a private/public key pair, e.g. using OpenSSL. In the executable directory, run

and rename the generated files

mv ... server.pem
mv ... server.key

Set up the database:

MySQL databases

sudo mysql -p < ${WHIZROOT}/srcrep/hlwz/_ini/dbshlwz/CreateDbsHlwzMy.sql

The 'CREATE USER ...' part needs to be commented out in case the user already exists.

HelloWhiznium

2019-08-24T07:49:56Z

Mpsitech: Created page with "Building HelloWhiznium Running HelloWhiznium for the first time Copy the preferences file from ... to ... . If you would like to use HTTPS server, you need to create a pri..."

Setting up your local environment

2019-06-26T08:28:54Z

Mpsitech:

For convenience, MPSI provides a self-contained local folder structure for building WhizniumSBE and WhizniumDBE projects. The paths are configured such that no modifications to the workstation's file system outside of this folder structure are necessary.

Four tested configurations are available, two of which are catering to Yocto/PetaLinux cross-compile environments:

1. apalis: for Toradex's [https://developer.toradex.com/products/apalis-imx6 Apalis iMX6] board featuring dual/quad Cortex-A9 ARM cores

2. arty: for the [https://reference.digilentinc.com/reference/programmable-logic/arty-z7/start Digilent Arty Z7] board which is built around Xilinx's Z7010/Z7020 Zynq All-Programmable SOC, featuring dual Cortex-A9 ARM cores and FPGA fabric

3. linux: for ubuntu workstations, tested for 16.04 and 18.04

4. mac: for Apple computers

== Prerequisites ==

1. apalis: have your Yocto project set up on your workstation

2. arty: have your PetaLinux project set up on your workstation

3. linux: the following packages are required:

sudo apt install make gcc libxml2-dev mysql-client mysql-server libmysqlclient-dev postgresql postgresql-contrib libpq-dev sqlite3 libsqlite3-dev libmicrohttpd-dev libcurl3-dev

4. mac: the following installations are required (you may consider using Homebrew instead of building from source):

MySQL from https://dev.mysql.com/downloads/mysql/ 8.0.16, use Legacy Password Encryption

libcurl: https://curl.haxx.se/download.html, installation should end up in /usr/include and /usr/lib

libxml2: ftp://xmlsoft.org/libxml2, installation should end up in /usr/local/include/libxml2 and /usr/local/lib

libmicrohttpd: https://ftp.gnu.org/gnu/libmicrohttpd, installation should end up in /usr/local/include and /usr/local/lib

== Download and configure ==

The Whiznium local folder structure is available at https://mpsitech-public.s3.amazonaws.com/whiznium_root.tgz. Download it and unpack it at your location of choice. The unpacked folder will be your Whiznium root directory and a shell variable ${WHIZROOT} will be defined for it.

== Build essentials ==

Carefully follow the instructions in ${WHIZROOT}/setup_<machine type>.sh: this file contains shell command snippets but is not meant to be executed as a whole.

A note on the 'manually edit ${WHIZROOT}/srcrep/sbecore/config.h' task: in this header file you define which DBMS types are available on your system. The options include MariaDB (SBECORE_MAR), MySQL (SBECORE_MY), PostgreSQL (SBECORE_PG) and SQLite3 (SBECORE_LITE).

The default configuration is 1. apalis SBECORE_LITE, 2. arty SBECORE_LITE, 3. linux SBECORE_MY + SBECORE_PG, 4. mac SBECORE_MY.

Setting up your local environment

2019-06-26T08:28:07Z

Mpsitech:

For convenience, MPSI provides a self-contained local folder structure for building WhizniumSBE and WhizniumDBE projects. The paths are configured such that no modifications to the workstation's file system outside of this folder structure are necessary.

Four tested configurations are available, two of which are catering to Yocto/PetaLinux cross-compile environments:

1. apalis: for Toradex's [https://developer.toradex.com/products/apalis-imx6 Apalis iMX6] board featuring dual/quad Cortex-A9 ARM cores

2. arty: for the [https://reference.digilentinc.com/reference/programmable-logic/arty-z7/start Digilent Arty Z7] board which is built around Xilinx's Z7010/Z7020 Zynq All-Programmable SOC, featuring dual Cortex-A9 ARM cores and FPGA fabric

3. linux: for ubuntu workstations, tested for 16.04 and 18.04

4. mac: for Apple computers

== Prerequisites ==

1. apalis: have your Yocto project set up on your workstation

2. arty: have your PetaLinux project set up on your workstation

3. linux: the following packages are required:

sudo apt install make gcc libxml2-dev mysql-client mysql-server libmysqlclient-dev postgresql postgresql-contrib libpq-dev sqlite3 libsqlite3-dev libmicrohttpd-dev libcurl3-dev

4. mac: the following installations are required (you may consider using Homebrew instead of building from source):

MySQL from https://dev.mysql.com/downloads/mysql/ 8.0.16, use Legacy Password Encryption

libcurl: https://curl.haxx.se/download.html, installation should end up in /usr/include and /usr/lib

libxml2: ftp://xmlsoft.org/libxml2, installation should end up in /usr/local/include/libxml2 and /usr/local/lib

libmicrohttpd: https://ftp.gnu.org/gnu/libmicrohttpd, installation should end up in /usr/local/include and /usr/local/lib

== Download and configure ==

The Whiznium local folder structure is available at https://mpsitech-public.s3.amazonaws.com/whiznium_root.tgz. Download it and unpack it at your location of choice. The unpacked folder will be your Whiznium root directory and a shell variable ${WHIZROOT} will be defined for it.

== Build essentials ==

Carefully follow the instructions in ${WHIZROOT}/setup_<machine type>.sh: this file contains shell command snippets but is not meant to be executed as a whole.

A note on the 'manually edit ${WHIZROOT}/srcrep/sbecore/config.h' task: in this header file you define which DBMS types are available on your system. The options include MariaDB (SBECORE_MAR), MySQL (SBECORE_MY), PostgreSQL (SBECORE_PG) and SQLite3 (SBECORE_LITE).

The default configuration is 1. apalis SBECORE_LITE, 2. arty SBECORE_LITE, 3. linux SBECORE_MY + SBECORE_PG, 4. mac SBECORE_MY

Setting up your local environment

2019-06-26T08:27:32Z

Mpsitech:

For convenience, MPSI provides a self-contained local folder structure for building WhizniumSBE and WhizniumDBE projects. The paths are configured such that no modifications to the workstation's file system outside of this folder structure are necessary.

Four tested configurations are available, two of which are catering to Yocto/PetaLinux cross-compile environments:

1. apalis: for Toradex's [https://developer.toradex.com/products/apalis-imx6 Apalis iMX6] board featuring dual/quad Cortex-A9 ARM cores

2. arty: for the [https://reference.digilentinc.com/reference/programmable-logic/arty-z7/start Digilent Arty Z7] board which is built around Xilinx's Z7010/Z7020 Zynq All-Programmable SOC, featuring dual Cortex-A9 ARM cores and FPGA fabric

3. linux: for ubuntu workstations, tested for 16.04 and 18.04

4. mac: for Apple computers

== Prerequisites ==

1. apalis: have your Yocto project set up on your workstation

2. arty: have your PetaLinux project set up on your workstation

3. linux: the following packages are required:

sudo apt-get install make gcc libxml2-dev mysql-client mysql-server libmysqlclient-dev postgresql postgresql-contrib libpq-dev sqlite3 libsqlite3-dev libmicrohttpd-dev libcurl3-dev

4. mac: the following installations are required (you may consider using Homebrew instead of building from source):

MySQL from https://dev.mysql.com/downloads/mysql/ 8.0.16, use Legacy Password Encryption

libcurl: https://curl.haxx.se/download.html, installation should end up in /usr/include and /usr/lib

libxml2: ftp://xmlsoft.org/libxml2, installation should end up in /usr/local/include/libxml2 and /usr/local/lib

libmicrohttpd: https://ftp.gnu.org/gnu/libmicrohttpd, installation should end up in /usr/local/include and /usr/local/lib

== Download and configure ==

The Whiznium local folder structure is available at https://mpsitech-public.s3.amazonaws.com/whiznium_root.tgz. Download it and unpack it at your location of choice. The unpacked folder will be your Whiznium root directory and a shell variable ${WHIZROOT} will be defined for it.

== Build essentials ==

Carefully follow the instructions in ${WHIZROOT}/setup_<machine type>.sh: this file contains shell command snippets but is not meant to be executed as a whole.

A note on the 'manually edit ${WHIZROOT}/srcrep/sbecore/config.h' task: in this header file you define which DBMS types are available on your system. The options include MariaDB (SBECORE_MAR), MySQL (SBECORE_MY), PostgreSQL (SBECORE_PG) and SQLite3 (SBECORE_LITE).

The default configuration is 1. apalis SBECORE_LITE, 2. arty SBECORE_LITE, 3. linux SBECORE_MY + SBECORE_PG, 4. mac SBECORE_MY

Setting up your local environment

2019-06-26T08:23:20Z

Mpsitech:

For convenience, MPSI provides a self-contained local folder structure for building WhizniumSBE and WhizniumDBE projects. The paths are configured such that no modifications to the workstation's file system outside of this folder structure are necessary.

Four tested configurations are available, two of which catering to Yocto/PetaLinux cross-compile environments:

1. apalis: for Toradex's [https://developer.toradex.com/products/apalis-imx6 Apalis iMX6] board featuring dual/quad Cortex-A9 ARM cores

2. arty: for the [https://reference.digilentinc.com/reference/programmable-logic/arty-z7/start Digilent Arty Z7] board which is built around Xilinx's Z7010/Z7020 Zynq All-Programmable SOC, featuring dual Cortex-A9 ARM cores and FPGA fabric

3. linux: for ubuntu workstations, tested for 16.04 and 18.04

4. mac: for Apple computers

== Prerequisites ==

1. apalis: have your Yocto project set up on your workstation

2. arty: have your PetaLinux project set up on your workstation

3. linux: the following packages are required:

sudo apt-get install make gcc libxml2-dev mysql-client mysql-server libmysqlclient-dev postgresql postgresql-contrib libpq-dev sqlite3 libsqlite3-dev libmicrohttpd-dev libcurl3-dev

4. mac: the following installations are required (you may consider using Homebrew instead of building from source):

MySQL from https://dev.mysql.com/downloads/mysql/ 8.0.16, use Legacy Password Encryption

libcurl: https://curl.haxx.se/download.html, installation should end up in /usr/include and /usr/lib

libxml2: ftp://xmlsoft.org/libxml2, installation should end up in /usr/local/include/libxml2 and /usr/local/lib

libmicrohttpd: https://ftp.gnu.org/gnu/libmicrohttpd, installation should end up in /usr/local/include and /usr/local/lib

== Download and configure ==

The Whiznium local folder structure is available at https://mpsitech-public.s3.amazonaws.com/whiznium_root.tgz. Download it and unpack it at your location of choice. The unpacked folder will be your Whiznium root directory and a shell variable ${WHIZROOT} will be defined for it.

== Build essentials ==

Carefully follow the instructions in ${WHIZROOT}/setup_<machine type>.sh: this file contains shell command snippets but is not meant to be executed as a whole.

A note on the 'manually edit ${WHIZROOT}/srcrep/sbecore/config.h' task: in this header file you define which DBMS types are available on your system. The options include MariaDB (SBECORE_MAR), MySQL (SBECORE_MY), PostgreSQL (SBECORE_PG) and SQLite3 (SBECORE_LITE).

The default configuration is 1. apalis SBECORE_LITE, 2. arty SBECORE_LITE, 3. linux SBECORE_MY + SBECORE_PG, 4. mac SBECORE_MY

Setting up your local environment

2019-06-26T08:17:27Z

Mpsitech:

For convenience, MPSI provides a self-contained local folder structure for building WhizniumSBE and WhizniumDBE projects. The paths are configured such that no modifications to the workstation's file system outside of this folder structure are necessary.

Four tested configurations are available, two of which catering to Yocto/PetaLinux cross-compile environments:

1. apalis: for Toradex's [https://developer.toradex.com/products/apalis-imx6 Apalis iMX6] board featuring dual/quad Cortex-A9 ARM cores

2. arty: for the [https://reference.digilentinc.com/reference/programmable-logic/arty-z7/start Digilent Arty Z7] board which is built around Xilinx's Z7010/Z7020 Zynq All-Programmable SOC, featuring dual Cortex-A9 ARM cores and FPGA fabric

3. linux: for ubuntu workstations, tested for 16.04 and 18.04

4. mac: for Apple computers

== Prerequisites ==

1. apalis: have your Yocto project set up on your workstation

2. arty: have your PetaLinux project set up on your workstation

3. linux: the following packages are required:

sudo apt-get install make gcc libxml2-dev mysql-client mysql-server libmysqlclient-dev postgresql postgresql-contrib libpq-dev sqlite3 libsqlite3-dev libmicrohttpd-dev libcurl3-dev

4. mac: the following installations are required (you may consider using Homebrew instead of building from source):

MySQL from https://dev.mysql.com/downloads/mysql/ 8.0.16, use Legacy Password Encryption

libcurl: https://curl.haxx.se/download.html, installation should end up in /usr/include and /usr/lib

libxml2: ftp://xmlsoft.org/libxml2, installation should end up in /usr/local/include/libxml2 and /usr/local/lib

libmicrohttpd: https://ftp.gnu.org/gnu/libmicrohttpd, installation should end up in /usr/local/include and /usr/local/lib

== Download and configure ==

The Whiznium local folder structure is available at https://mpsitech-public.s3.amazonaws.com/whiznium_root.tgz. Download it and unpack it at your location of choice. The unpacked folder will be your Whiznium root directory and a shell variable ${WHIZROOT} will be defined for it.

== Build essentials ==

Carefully follow the instructions in ${WHIZROOT}/setup_<machine type>.sh: this file contains shell command snippets but is not meant to be executed as a whole.

Setting up your local environment

2019-06-26T08:16:55Z

Mpsitech:

For convenience, MPSI provides a self-contained local folder structure for building WhizniumSBE and WhizniumDBE projects. The paths are configured such that no modifications to the workstation's file system outside of this folder structure are necessary.

Four tested configurations are available, two of which catering to Yocto/PetaLinux cross-compile environments:

1. apalis: for Toradex's [https://developer.toradex.com/products/apalis-imx6 Apalis iMX6] board featuring dual/quad Cortex-A9 ARM cores

2. arty: for the [https://reference.digilentinc.com/reference/programmable-logic/arty-z7/start Digilent Arty Z7] board which is built around Xilinx's Z7010/Z7020 Zynq All-Programmable SOC, featuring dual Cortex-A9 ARM cores and FPGA fabric

3. linux: for ubuntu workstations, tested for 16.04 and 18.04

4. mac: for Apple computers

== Prerequisites ==

1. apalis: have your Yocto project set up on your workstation

2. arty: have your PetaLinux project set up on your workstation

3. linux: the following packages are required:

sudo apt-get install make gcc libxml2-dev mysql-client mysql-server libmysqlclient-dev postgresql postgresql-contrib libpq-dev sqlite3 libsqlite3-dev libmicrohttpd-dev libcurl3-dev

4. mac: the following installations are required (you may consider using Homebrew instead of building from source):

MySQL from https://dev.mysql.com/downloads/mysql/ 8.0.16, use Legacy Password Encryption

libcurl: https://curl.haxx.se/download.html, installation should end up in /usr/include and /usr/lib

libxml2: ftp://xmlsoft.org/libxml2, installation should end up in /usr/local/include/libxml2 and /usr/local/lib

libmicrohttpd: https://ftp.gnu.org/gnu/libmicrohttpd, installation should end up in /usr/local/include and /usr/local/lib

== Download and configure ==

The Whiznium local folder structure is available at https://mpsitech-public.s3.amazonaws.com/whiznium_root.tgz. Download it and unpack it at your location of choice. The unpacked folder will be your Whiznium root directory and a shell variable ${WHIZROOT} will be defined for it.

== Build essentials ==

Carefully follow the instructions in setup_<machine type>.sh: this file contains shell command snippets but is not meant to be executed as a whole.

Setting up your local environment

2019-06-26T08:12:27Z

Mpsitech:

For convenience, MPSI provides a self-contained local folder structure for building WhizniumSBE and WhizniumDBE projects. The paths are configured such that no modifications to the workstation's file system outside of this folder structure are necessary.

Four tested configurations are available, two of which catering to (Yocto/PetaLinux) cross-compile environments:

1. apalis: for Toradex's [https://developer.toradex.com/products/apalis-imx6 Apalis iMX6] board featuring dual/quad Cortex-A9 ARM cores

2. arty: for the [https://reference.digilentinc.com/reference/programmable-logic/arty-z7/start Digilent Arty Z7] board which is built around Xilinx's Z7010/Z7020 Zynq All-Programmable SOC, featuring dual Cortex-A9 ARM cores and FPGA fabric

3. linux: for ubuntu workstations, tested for 16.04 and 18.04

4. mac: for Apple computers

== Prerequisites ==

1. apalis: have your Yocto project set up on your workstation

2. arty: have your PetaLinux project set up on your workstation

3. linux: the following packages are required:

sudo apt-get install make gcc libxml2-dev mysql-client mysql-server libmysqlclient-dev postgresql postgresql-contrib libpq-dev sqlite3 libsqlite3-dev libmicrohttpd-dev libcurl3-dev

4. mac: the following installations are required (you may consider using Homebrew instead of building from source):

MySQL from https://dev.mysql.com/downloads/mysql/ 8.0.16, use Legacy Password Encryption

libcurl: https://curl.haxx.se/download.html, installation should end up in /usr/include and /usr/lib

libxml2: ftp://xmlsoft.org/libxml2, installation should end up in /usr/local/include/libxml2 and /usr/local/lib

libmicrohttpd: https://ftp.gnu.org/gnu/libmicrohttpd, installation should end up in /usr/local/include and /usr/local/lib

== Download and unpack ==

The Whiznium local folder structure is available at https://mpsitech-public.s3.amazonaws.com/whiznium_root.tgz. Download it and unpack it at your location of choice.

== Build essentials ==

Setting up your local environment

2019-06-26T08:11:56Z

Mpsitech:

For convenience, MPSI provides a self-contained local folder structure for building WhizniumSBE and WhizniumDBE projects. The paths are configured such that no modifications to the workstation's file system outside of this folder structure are necessary.

Four tested configurations are available, two of which catering to (Yocto/PetaLinux) cross-compile environments:

1. apalis: for Toradex's [https://developer.toradex.com/products/apalis-imx6 Apalis iMX6] board featuring dual/quad Cortex-A9 ARM cores

2. arty: for the [https://reference.digilentinc.com/reference/programmable-logic/arty-z7/start Digilent Arty Z7] board which is built around Xilinx's Z7010/Z7020 Zynq All-Programmable SOC, featuring dual Cortex-A9 ARM cores and FPGA fabric

3. linux: for ubuntu workstations, tested for 16.04 and 18.04

4. mac: for Apple computers

== Prerequisites ==

1. apalis: have your Yocto project set up on your workstation

2. arty: have your PetaLinux project set up on your workstation

3. linux: the following packages are required:

sudo apt-get install make gcc libxml2-dev mysql-client mysql-server libmysqlclient-dev postgresql postgresql-contrib libpq-dev sqlite3 libsqlite3-dev libmicrohttpd-dev libcurl3-dev

4. mac: the following installations are required (you may consider using Homebrew instead of building from source):

MySQL from https://dev.mysql.com/downloads/mysql/ 8.0.16, use Legacy Password Encryption

libcurl: https://curl.haxx.se/download.html, installation should end up in /usr/include and /usr/lib

libxml2: ftp://xmlsoft.org/libxml2, installation should end up in /usr/local/include/libxml2 and /usr/local/lib

libmicrohttpd: https://ftp.gnu.org/gnu/libmicrohttpd, installation should end up in /usr/local/include and /usr/local/lib

== Download and unpack ==

The Whiznium local folder structure is available at https://mpsitech-public.s3.amazonaws.com/whiznium_root.tar.gz. Download it and unpack it at your location of choice.

== Build essentials ==

Setting up your local environment

2019-06-26T08:11:28Z

Mpsitech:

For convenience, MPSI provides a self-contained local folder structure for building WhizniumSBE and WhizniumDBE projects. The paths are configured such that no modifications to the workstation's file system outside of this folder structure are necessary.

Four tested configurations are available, two of which catering to (Yocto/PetaLinux) cross-compile environments:

1. apalis: for Toradex's [https://developer.toradex.com/products/apalis-imx6 Apalis iMX6] board featuring dual/quad Cortex-A9 ARM cores

2. arty: for the [https://reference.digilentinc.com/reference/programmable-logic/arty-z7/start Digilent Arty Z7] board which is built around Xilinx's Z7010/Z7020 Zynq All-Programmable SOC, featuring dual Cortex-A9 ARM cores and FPGA fabric

3. linux: for ubuntu workstations, tested for 16.04 and 18.04

4. mac: for Apple computers

== Prerequisites ==

1. apalis: have your Yocto project set up on your workstation

2. arty: have your PetaLinux project set up on your workstation

3. linux: the following packages are required:

sudo apt-get install make gcc libxml2-dev mysql-client mysql-server libmysqlclient-dev postgresql postgresql-contrib libpq-dev sqlite3 libsqlite3-dev libmicrohttpd-dev libcurl3-dev

4. mac: the following installations are required (you may consider using Homebrew instead of building from source):

MySQL from https://dev.mysql.com/downloads/mysql/ 8.0.16, use Legacy Password Encryption

libcurl: https://curl.haxx.se/download.html, installation should end up in /usr/include and /usr/lib

libxml2: ftp://xmlsoft.org/libxml2, installation should end up in /usr/local/include/libxml2 and /usr/local/lib

libmicrohttpd: https://ftp.gnu.org/gnu/libmicrohttpd, installation should end up in /usr/local/include and /usr/local/lib

== Download and unpack ==

The Whiznium local folder structure is available at https://mpsitech-public.s3.amazonaws.com/whiznium-root.tar.gz. Download it and unpack it at your location of choice.

== Build essentials ==

Setting up your local environment

2019-06-26T08:07:32Z

Mpsitech:

For convenience, MPSI provides a self-contained folder structure for building WhizniumSBE and WhizniumDBE projects. The paths are configured such that no modifications to the workstation's file system outside of this folder structure are necessary.

Four tested configurations are available, two of which catering to (Yocto/PetaLinux) cross-compile environments:

1. apalis: for Toradex's [https://developer.toradex.com/products/apalis-imx6 Apalis iMX6] board featuring dual/quad Cortex-A9 ARM cores

2. arty: for the [https://reference.digilentinc.com/reference/programmable-logic/arty-z7/start Digilent Arty Z7] board which is built around Xilinx's Z7010/Z7020 Zynq All-Programmable SOC, featuring dual Cortex-A9 ARM cores and FPGA fabric

3. linux: for ubuntu workstations, tested for 16.04 and 18.04

4. mac: for Apple computers

== Prerequisites ==

1. apalis: have your Yocto project set up on your workstation

2. arty: have your PetaLinux project set up on your workstation

3. linux: the following packages are required:

sudo apt-get install make gcc libxml2-dev mysql-client mysql-server libmysqlclient-dev postgresql postgresql-contrib libpq-dev sqlite3 libsqlite3-dev libmicrohttpd-dev libcurl3-dev

4. mac: the following installations are required (you may consider using Homebrew instead of building from source):

MySQL from https://dev.mysql.com/downloads/mysql/ 8.0.16, use Legacy Password Encryption

libcurl: https://curl.haxx.se/download.html, installation should end up in /usr/include and /usr/lib

libxml2: ftp://xmlsoft.org/libxml2, installation should end up in /usr/local/include/libxml2 and /usr/local/lib

libmicrohttpd: https://ftp.gnu.org/gnu/libmicrohttpd, installation should end up in /usr/local/include and /usr/local/lib

Setting up your local environment

2019-06-26T07:54:16Z

Mpsitech: Created page with "For convenience, MPSI provides a self-contained folder structure for building WhizniumSBE and WhizniumDBE projects. The paths are configured such that no modifications to the..."

WhizniumSBE Wikipedia

2019-06-26T07:45:40Z

Mpsitech:

This page describes the four-step Whiznium early adopter onboarding procedure.

The four steps are:

1. [[Creating an account]]

2. [[Setting up your local environment]]

3. [[Launching your dedicated cloud-based Whiznium service]]

4. [[Using your dedicated cloud-based Whiznium service]]

Creating an account

2019-06-26T07:44:07Z

Mpsitech:

Using the Whiznium services (free-trial or paid) requires creating an account with MPSI. While we do want to know who you are and which organization you work for, we do not collect any payment details such as credit card data.

Management of accounts and their associated Whiznium services (cloud- or container-based) are handled in a web-based tool called Whiznium License Manager. Its URL is https://license.mpsitech.cloud:15100.

There is a YouTube video [https://www.youtube.com/watch?v=otUZN0vL25s] explaining all necessary steps.

Creating an account

2019-06-26T07:43:45Z

Mpsitech:

Using the Whiznium services (free-trial or paid) requires creating an account with MPSI. While we do want to know who you are and which organization you work for, we do not collect any payment details such as credit card data.

Management of accounts and their associated Whiznium services (cloud- or container-based) are handled in a web-based tool called [https://license.mpsitech.cloud:15100 Whiznium License Manager]. Its URL is https://license.mpsitech.cloud:15100.

There is a YouTube video [https://www.youtube.com/watch?v=otUZN0vL25s] explaining all necessary steps.

Launching your dedicated cloud-based Whiznium service

2019-06-26T07:41:46Z

Mpsitech:

After you have successfully created an account and your local workstation has been set up to be used with Whiznium, you are now ready to start your dedicated WhizniumSBE or WhizniumDBE service (free-trial or paid).

The entry point again is the [https://license.mpsitech.cloud:15100 Whiznium License Manager].

A YouTube video [https://www.youtube.com/watch?v=fZEjTIY66Qk] details the necessary steps.

Launching your dedicated cloud-based Whiznium service

2019-06-26T07:41:27Z

Mpsitech:

After you have successfully created an account and your local workstation has been set up to be used with Whiznium, you are now ready to start your dedicated WhizniumSBE or WhizniumDBE service (free-trial or paid).

The entry point again is [https://license.mpsitech.cloud:15100 Whiznium License Manager].

A YouTube video [https://www.youtube.com/watch?v=fZEjTIY66Qk] details the necessary steps.

Launching your dedicated cloud-based Whiznium service

2019-06-26T07:40:31Z

Mpsitech: Created page with "After you have successfully created an account and your local workstation has been set up to be used with Whiznium, you are now ready to start your dedicated WhizniumSBE or Wh..."

After you have successfully created an account and your local workstation has been set up to be used with Whiznium, you are now ready to start your dedicated WhizniumSBE or WhizniumDBE service (free-trial or paid).

A YouTube video [https://www.youtube.com/watch?v=fZEjTIY66Qk] details the necessary steps.

Creating an account

2019-06-26T07:37:28Z

Mpsitech:

Using the Whiznium services (free trial or paid) requires creating an account with MPSI. While we do want to know who you are and which organization you work for, we do not collect any payment details such as credit card data.

There is a YouTube video [https://www.youtube.com/watch?v=otUZN0vL25s] explaining all necessary steps.

Creating an account

2019-06-26T07:36:47Z

Mpsitech: Created page with "Using the Whiznium services (free trial or paid) requires creating an account with MPSI. While we want to know who you are and which organization you work for, we do not colle..."

Using the Whiznium services (free trial or paid) requires creating an account with MPSI. While we want to know who you are and which organization you work for, we do not collect any payment details such as credit card data.

There is a YouTube video [https://www.youtube.com/watch?v=otUZN0vL25s] explaining all necessary steps.

WhizniumSBE Wikipedia

2019-06-26T07:32:05Z

Mpsitech:

This page describes the four-step Whiznium early adopter onboarding procedure in detail.

The four steps are:

1. [[Creating an account]]

2. [[Setting up your local environment]]

3. [[Launching your dedicated cloud-based Whiznium service]]

4. [[Using your dedicated cloud-based Whiznium service]]

WhizniumSBE Wikipedia

2019-06-26T07:28:34Z

Mpsitech: Mpsitech moved page Main Page to WhizniumSBE Wikipedia

This page describes the four-step Whiznium early adopter onboarding procedure in detail.

The four steps are:

1. Creating an account

2. Setting up your local environment

3. Launching your dedicated cloud-based Whiznium service

4. Using your dedicated cloud-based Whiznium service

Main Page

2019-06-26T07:28:34Z

Mpsitech: Mpsitech moved page Main Page to WhizniumSBE Wikipedia

#REDIRECT [[WhizniumSBE Wikipedia]]

WhizniumSBE Wikipedia

2019-06-26T07:19:32Z

Mpsitech: WhizniumSBE Wikipedia Main Page