Step 3

: Build the Kiuwan Docker image

After the image creation, you will be able to list the images in your docker server and identify your kiuwan image by issuing the next command:

     docker images

Image Modified

Step 3.1 (Optional) Moving the image to another server host

After creating the image, if you want to move it to another host server you first must save it to a tarball by executing: 

     docker save kop:v1.2 > kop_v12_saved_image.tar 

     docker load --input kop_v12_saved_image.tar 

Step 4.1 Execution in debug mode (only sshd) 

Just in case you are running with problems while executing the Kiuwan container, you can run it in debug mode.

This means to apply the configuration but not starting the services, allowing you to access the container through ssh.

Step 5

: Making Kiuwan On

-Premises run on HTTPS (Optional)

If you need to execute Kiwuan On

-Premises over HTTPS protocol, please follow the next steps. 

Step 5.1 Create your KOP SSL configuration file

SSL configuration  is currently done by creating a configuration file (ssl.custom) within ssl directory 

There's a file (ssl.tpl) you can use as a template to configure your

settings.

1. cd ssl
2. Create ssl.custom file by copying the template file
   • cp ssl.tpl ssl.custom
3. Edit the properties of ssl.custom file and change default values

Step 5.2 Create the Private key and Certificate Signing Request (CSR) for your server

1. Within ssl directory execute the script CreateKey_and_ReqCSR.sh 

1. This script generates the CSR file under ssl/certs

1. • That file is named <yourhost.yourdomain.com>.csr

1. • , according to  $KIUWAN_HOST configuration property

1. Send CSR file to your CA (Certificate Authority) 
2. CA will send back to you two files: 
   • CA's Certificate file (IMPORTANT: rename it to ca.crt )

1. • Your host's Certificate file: for example yourhost.yourdomain.com.crt

1. Copy received files to ssl/certs directory

Step 5.3 Create the Keystore and switch from HTTP to HTTPS

1. Within ssl directory execute the script TransferFilesToContainer.sh

1. • This script transfers your server's certificate, your private key and CA's certificate to KOP container

1. • Also, it transfers the script templates that will be used to create the keystore and to change the configuration from http to https 

1. Within ssl directory execute the script run_create_Keystore.sh 

1. • This script executes (into the container) the script create_Keystore.sh (created from template create_Keystore.tpl)

1. Within ssl directory execute the script run_change_ToHTTPS.sh 
   

1. • This script stops wildfly service and executes the script change_ToHTTPS.sh (created from template change_ToHTTPS.tpl), this script will create files with .rollback extension of modified ones

1. • Then, it starts wildfly service 

Step 5.4 Just in case you are using your own CA, make it valid to your browsers and Java 

If the certificate is signed by your own Certification Authority, the browsers will not recognize it as a valid CA and you will get an error messages such as:

Your connection is not private
Attackers might be trying to steal your information from youthost.yourdomain.com (for example, passwords, messages, or credit cards).

NET::ERR_CERT_AUTHORITY_INVALID

To solve this issue, you have to import your CA Certificate into your browser : 

• In Chrome: Configuration >> Settings >> Advanced >> Manage certificates >>  Import (ca.crt) into "Trusted root certification entity store"

Log in to the KOP container and execute the next commands:

1. cd /opt/jdk*/jre/lib/security/
2. supervisorctl stop wildfly 
3. cp cacerts cacerts.bck.original 
4. keytool -import -noprompt -alias root -keystore cacerts -trustcacerts -file /<kiuwan_vol>/configurations/ssl/ca.crt -storepass

1. changeitsupervisorctl start wildfly
   • NOTE: change <kiuwan_vol> to the value of $KIUWAN_VOL (as configured in settings.custom) 

Then, log in to your docker server and make above changes persistent (i.e.

to keep them after rebooting the container):

1. docker commit <kop docker name> <kop docker image> 
   
   • NOTE: run 'docker ps' to get NAMES and IMAGE values of your KOP container

Rollback to HTTP

Advanced Configuration

As above specified,

the settings.custom file allows you to specify most (but not all) configuration parameters.

Appendix 1 - Configuring Apache as FrontEnd WebServer to KOP

If you choose the Apache web server as the front-end for your Kiuwan

On-Premises installation, you may follow the following configuration examples and/or check 

your current configuration agrees with the suggested examples.

HTTP Protocol

For this kind of access you just need to add a virtual host and configure how Apache will talk to Kiuwan.

Before this make sure your Apache installation has these modules available:

• mod_proxy

• mod_proxy_ajp (if you want ajp communication between front and backend servers)

• mod_proxy_http (if you want ajp communication between front and backend servers)

• mod_proxy_wstunnel

To add a virtual host for Kiuwan

On-Premises, you can add a file in your Apache installation folder (i.e. /etc/apache2/sites-available/kop.conf) with the following content. Make sure you replace the variables put inside brackets for those you previously configured when installing your Kiuwan

On-Premises instance and a protocol is set (choose between ajp or http) in the ProxyPass directives:

<VirtualHost *:[KIUWAN_WEBSERVER_PORT]>
	ServerName [KIUWAN_WEBSERVER_HOST]
	ServerAdmin webmaster@localhost
	DocumentRoot /var/www/html

	LogLevel debug
	ErrorLog ${APACHE_LOG_DIR}/error.log
	CustomLog ${APACHE_LOG_DIR}/access.log combined

	ProxyRequests Off
	ProxyPreserveHost On
	<Proxy *>
		Require all granted 
	</Proxy>
	 
	ProxyPass		/	[ajp|http]://[KIUWAN_HOST]:[KIUWAN_PORT]/
	ProxyPassReverse	/	[ajp|http]://[KIUWAN_HOST]:[KIUWAN_PORT]/
	 
	<Location />
		Require all granted
	</Location>
</VirtualHost>

HTTPS Protocol

For this kind of access you will need:

• A virtual host configured in Apache will talk to Kiuwan (see below).

• Open an https port in Apache (usually 443).

• A certificate for the exposed

• hostname (KIUWAN_WEBSERVER_HOST).

Before this make sure your Apache installation has these modules available:

• mod_proxy

• mod_proxy_ajp (if you want ajp communication between front and backend servers)

• mod_proxy_http (if you want ajp communication between front and backend servers)

• mod_proxy_wstunnel

• mod_rewrite

• mod_ssl

Please make sure you generate a certificate for your

Kiuwan hostname and it is signed by a trusted CA inside your organization. At this point you need three files:

• [KIUWAN_WEBSERVER_HOST].crt: the certificate for your kiuwan host.

• [KIUWAN_WEBSERVER_HOST].key: the private key.

• ca.crt: the trusted CA certificate.

Refer to PremisesInstallationGuide-Step5.2CreatethePrivatekeyandCertificateSigningRequest(CSR)foryourserver  for more information on how to create and install certificates.

Please note that you must install the CA certificate on the docker container before proceeding.

Place the previous files at

these locations (we put here the default locations for these files, but it is up to you to change

these paths):

• /etc/ssl/certs/[KIUWAN_WEBSERVER_HOST].crt

• /etc/ssl/private/[KIUWAN_WEBSERVER_HOST].key

• /etc/apache2/ssl.crt/ca.crt

Now you should tell Apache to listen on the configured https port, editing the ports.conf file (i.e. /etc/apache2/ports.conf):

To add a virtual host for Kiuwan

On-Premises, you can add a file in your Apache installation folder (i.e. /etc/apache2/sites-available/kop.conf) with the following content. Make sure you replace the variables put inside brackets for those you previously configured when installing your Kiuwan

On-Premises instance and a protocol is set (choose between ajp or http) in the ProxyPass directives: