Faint idea to published website. An OpenWGA Tutorial, Part 3

Page 2 of 3

Let's do (OpenWGA) server setup!

So OpenWGA server is now installed and running on your machine. To access it just fire up any browser on your client machine (according to me Google Chrome or Mozilla Firefox are good choices, Internet Explorer is null and not a browser) and access your server on port 8080 via URL:


What you should see now is the "start page" of OpenWGA. It tells the following:


Yes, now that we finished (Linux) server setup we are going to continue wiht (OpenWGA) server setup. For that we click the button labeled "Start OpenWGA Setup Wizard" and login there with user "admin" and password "wga".

Now follow the OpenWGA setup wizard, which is mostly self-explaining. However, here are some notes about the wizard steps regarding our situation:

  • Welcome to.... : Feel welcomed, because we really do (welcome you) !
  • Create a database server definition: We need to tell OpenWGA where to store its data. "MySQL server" here is the obvious choice. Give it some title of no special meaning and keep "localhost" as DNS. As MySQL user enter "root" and give OpenWGA the MySQL password you determined earlier. (Linux cracks: Yes, of course you may choose another MySQL login with lower rights, as long as it is able to create databases and fill them with tables)
  • Setup admin login: Determine some OpenWGA admin login of your choice. Choose some secure password, but, most importantly, keep your login information for later use.
  • Setup simple authentication...: Here you determine an authoring login which you will use when feeding content to your website later, directly on your live server.
  • Confirmation: Check your settings, correct if necessary, then confirm

Confirming you setup will take you back to the start page, now offering some other options to continue. We will ignore them here.

Install necessary plugins

Just as your local server your live server will need the basic website kit plugin (and dependencies) to publish your website.

So head back to part 1 of this tutorial. There on page 4 where it says "Installing the basic website kit" the procedure to do so is described. Use the "OpenWGA Admin Client" link on the start page to open this client and then install the basic website kit to your live server using this section of the tutorial.

After you finished the "Installing the basic website kit" section (should be just page 4) head back here to continue.

Export your web application

Back to your dev studio. Now we are gonna push the data inside your runtime project (or rather the largest part of it) up to your setup OpenWGA live server. To start this right-click your runtime project in Package Explorer, then choose from the menu "OpenWGA > Export web application....".

Clicking this will first ask to start the dev studio server for this runtime (if it not already is) which you should confirm. After it finished doing that it will ask you which web application to export:


Mine is called "main", as seen in some earlier tutorial chapter. Yours should come up here too.

The next step will ask you about the connection information to your live server. Enter the URL to your server, the same that you entered to call the OpenWGA start page, and give the dev studio the admin login which you determined in OpenWGA setup wizard:


Next the dev studio will check your settings including the connection to your server. Ideally all checks should end like this:


The next step will offer you settings on how your exported web application should be created on the live server. Most importantly you should choose the database server there that should host the data of your app. You should find the MySQL server connection which you created in OpenWGA setup in this step as "Available database server":


If you want the dev studio to also push the content which you have created in your runtime up to the server (you most likely want that) then keep "copy local content" checked. Instead uncheck "include ACL". This would copy the access settings also from dev studio to live server. Most likely these have nothing in common, as your authoring user on the live server may have a different name than in the dev studio.

The next step will sum up what the studio is doing when clicking "Finish":


You might notice that "Plugin status" identifies some plugins that are different on the server.  However that should be no problem. On my system this is because I started the tutorial on WDS side with OpenWGA 5.5. However the live server is now OpenWGA 6.0 and supports a newer version of the basic website kit, that however should be backward compatible. So ignore this for now.

Now click "Finish" and let the studio do its work. After some time you should hopefully see:


That's it! Your application has reached your live server. You can check that by opening the URL to your app on this server that is:


On to the next page...

Enter Your Comment:

use markdown syntax



Last comments

  • Oliver:
    Als Antwort auf "Anonym" vom 27. Dezember 2015 (..
  • anonym:
    Habbo als abzocke zu deklarieren finde ich schon..
  • anonym:
    Wenn du es dir leisten kannst und es dich glückl..
  • Jebote:
    ja sicher kommen alle auf diesen 5 jahre alten a..
  • Micha:
    @Ingo, na klar. Alles legitim und voll ok ;-) Mu..

Really currently consuming


  • Mehr Whisky
  • Ich@Twitter
  • Dina
  • Julia
  • Der Meister (nebst Frau Meister)
  • Rockender Webworker
  • Irgendwas mit Fischen