Follow the steps given below to run a WSO2 product as a service on Private PaaS, which runs on Kubernetes:
Step 1: Deploying Private PaaS on a preferred IaaS
...
| Panel |
|---|
Download the Private PaaS cartridges from the product page. Navigate to the <PRIVATE-PAAS-CARTRIDGES>/wso2esb/4.8.1/docker directory. | Code Block |
|---|
cd <PRIVATE-PAAS-CARTRIDGES>/wso2esb/4.8.1/docker |
Run the build.sh file to build the Docker image. | Info |
|---|
This will copy the plugins and the Template Module to the Docker image. |
List the Docker images. Example response format: If you have successfully build the Docker image, you will get the following as the response: | Code Block |
|---|
wso2/das 3.0.0 ac57800e96c2 2 minutes ago 777.6 MB |
Save the new image to a .tar file. | Code Block |
|---|
docker save <NEW_IMAGE_NAME> > <LOCATION_OF_OF_TAR_FILE> |
For example: | Code Block |
|---|
docker save myppaasimage > /tmp/myppaasimage.tar |
Copy the Docker image to the Kubernetes minion node. | Code Block |
|---|
scp <IMAGE_NAME>.tar core@<NODE_IP>: |
Example: | Code Block |
|---|
scp myppaasimage.tar core@172.17.8.102: |
| Info |
|---|
Execute the kubectl get nodes command to get the IP address of the Kubernetes nodes. |
SSH into the Kubernetes node using one of the following commands: | Code Block |
|---|
ssh core@<NODE_IP> or vagrant ssh node-01 |
Load the .tar file to the Kubernetes node. | Code Block |
|---|
docker load < <LOCATION_OF_OF_TAR_FILE> |
Example: | Code Block |
|---|
docker load < /tmp/myppaasimage.tar |
| Info |
|---|
If more than one Kubernetes node exists, repeat step 4, 5 and 6 for the remaining nodes. |
|
Step 4: Creating product specific databases
...
| Notepanel |
|---|
This step is optional. To confirm if the product you are running on top of WSO2 PPaaS requires a database table, refer the README file that is in the specific product or cartridge folder. |
panelIt is mandatory to create the registry database for all products. Example: | Code Block |
|---|
mysql> create database regdb;
mysql> use regdb;
mysql> source <APIM_HOME>/dbscripts/mysql.sql;
mysql> grant all on regdb.* TO username@localhost identified by "password"; |
Create a database (or databases depending on the requirement) using the following commands, where <PRODUCT_HOME> is the path to any of the product instances you installed, and specify the username and password. | Info |
|---|
| title | About using MySQL in different operating systems |
|---|
| For users of Microsoft Windows, when creating the database in MySQL, it is important to specify the character set as latin1. Failure to do this may result in an error (error code: 1709) when starting your cluster. This error occurs in certain versions of MySQL (5.6.x) and is related to the UTF-8 encoding. MySQL originally used the latin1 character set by default, which stored characters in a 2-byte sequence. However, in recent versions, MySQL defaults to UTF-8 to be friendlier to international users. Hence, you must use latin1 as the character set as indicated below in the database creation commands to avoid this problem. Note that this may result in issues with non-latin characters (like Hebrew, Japanese, etc.). The following is how your database creation command should look. mysql> create database <DATABASE_NAME> character set latin1; For users of other operating systems, the standard database creation commands will suffice. For these operating systems, the following is how your database creation command should look. mysql> create database <DATABASE_NAME>; |
| Expand |
|---|
| title | Click here to see and example |
|---|
| You will need to create 3 databases for API Manager as shown below: | Code Block |
|---|
mysql> create database apimgtdb;
mysql> use apimgtdb;
mysql> source <APIM_HOME>/dbscripts/apimgt/mysql.sql;
mysql> grant all on apimgtdb.* TO username@localhost identified by "password";
mysql> create database userdb;
mysql> use userdb;
mysql> source <APIM_HOME>/dbscripts/mysql.sql;
mysql> grant all on userdb.* TO username@localhost identified by "password";
mysql> create database regdb;
mysql> use regdb;
mysql> source <APIM_HOME>/dbscripts/mysql.sql;
mysql> grant all on regdb.* TO username@localhost identified by "password"; |
| Note |
|---|
Ensure that MySQL is configured so that all nodes can connect to it. |
|
|
...