Difference between revisions of "HelloWhiznium"

From
Jump to: navigation, search
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
Building HelloWhiznium
 
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
 
Running HelloWhiznium for the first time
Line 51: Line 78:
 
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:
 
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 req -x509 -newkey rsa:4096 -keyout server.key -out server.pem -days 365
+
openssl genrsa -out server.key 4096
 +
openssl req -days 365 -out server.pem -new -x509 -key server.key
  
 
Set up the database:
 
Set up the database:
Line 70: Line 98:
  
 
As within sqlite3 the shell variable ${WHIZROOT} is unknown, you'll need to expand it manually.
 
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'.

Latest revision as of 11:58, 25 August 2019

Building HelloWhiznium

cd ${WHIZROOT[_CCH]}/srcrep/hwzd

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

cd [${SYSROOT}]${WHIZROOT}/src/ezdevhwzd
./makeall.sh
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

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:

<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>

<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'.