Versions Compared

Old Version 55

changes.mady.by.user Kiuwan Editor User

Saved on

compared with

New Version 56

changes.mady.by.user Kiuwan Editor User

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

After execution, KOP will come back to configuration previous to the execution of run_change_ToHTTPS.sh script.

 

Step 6. Accessing Kiuwan On Premise

KOP URL

Once Kiuwan On Premise container is running, you can access it from a browser in the following URL:

http[s]://<KIUWAN_HOST>:<KIUWAN_PORT>/saas 

where KIUWAN_HOST and KIUWAN_PORT match the values of those properties as configured in settings.custom

KOP REST-API URL

http[s]://<KIUWAN_HOST>:<KIUWAN_PORT>/saas/rest/v1


 


KOP built-in users

KOP comes with the following built-in users.

  • kiuwanadmin (password: kiuwanadmin)
    • access to Kiuwan "functional" administration modules such as Users, Applications and Model Management  (see Admin Guide )
    • log in as kiuwanadmin to create users of your KOP instance
  • sysadmin (password: sysadmin)
    • log in as sysadmin to access functionalities related to monitoring and tuning KOP execution
    • sysadmin will give you access KOP sysconsole


Upgrading your KOP installation

In order to maintain your KOP installation up-to-date to new features, bugfixes, etc, you will have to upgrade your KOP installation.

 

Log in to Console as SysAdmin and check the status of your  KOP installation:

Image Added

 

 

The following pages describe the upgrading Installation procedures of releases of KOP.

 

Before starting the upgrade process, it's always advisable to make a backup of current KOP installation.

  1. stop the container 
    1. docker stop <$KIUWAN_HOST>
  2. make a backup of MySQL (optional, step #3 also makes a backup copy of MySQL)
  3. from docker server, make a copy of permanent volume ( $DIR_PERSISTENT_VOLUME setting ).
    1. cp -rpf <$DIR_PERSISTENT_VOLUME/$KIUWAN_HOST> <$DIR_PERSISTENT_VOLUME/$KIUWAN_HOST>.bck
    2. Substitute DIR_PERSISTENT_VOLUME and KIUWAN_HOST with values configured at settings.custom file.
  4. start the container
    1. run_kop.sh

 

Basically, a new relase is distributed as a new KOP Installation Package,  consisting on a tarball gz file (docker-for-kiuwan_master.X.Y.tar.gz) containing all the new kiuwan docker files.

  1. copy the new distribution tarball to your host server’s updates directory ($KOP_INSTDIR/updates/download)
  2. uncompress the distribution tarball  
    • tar xvzf docker-for-kiuwan_master.X.Y.tar.gz 
    • a $KOP_INSTDIR/updates/download/docker-for-kiuwan_master.X.Y directory  will be created
  3. change directory to $KOP_INSTDIR/updates/bin



To upgrade Kiuwan Core AND Kiuwan Clients:

  • execute the script updateKiuwanLauncher.sh
    • this script makes all the work to upgrade your current KOP app instance to the new one (CORE and CLIENTES will be updated)

 Just

in case new KOP distribution only contains new clients (KLA, K4D) but it doesn't include changes in Kiuwan app, do not execute step #4 but execute next commandTo upgrade ONLY Kiuwan Clients:

  • execute the script updateClientsLauncher.sh
    • this script makes new KLA and K4D ready to be downloadable by KOP client users

 

 

...