Amalka Subasinghe's Blog

Environment variables allow you to change an application's internal configuration without changing its source code. Let’s say you want to deploy the same application in development, testing  and production environments. Then database related configs and some other internal configurations may change from one environment to another. If we can define these configurations as an environment variables we can easily set those without changing the source code of that application. When you deploy your application in WSO2 Integration Cloud, it lets you define environment variables via the UI. Whenever you change the values of environment variables, you just need to redeploy the application for the changes to take effect. Predefined environment variables Key Concepts - Environment Variables   provides you some predefined set of environment variables which will be useful when deploying applications in WSO2 Integration Cloud. Sample on how to use environment variables ...

In WSO2 Integration Cloud, we provide WSO2 ESB as an app type. So you can configure to FHIR connector on WSO2 ESB.   At the moment we don't have a specific document on configuring the FHIR connector on WSO2 Integration Cloud. But, we have included an example document [1] on how to configure a sample (Twitter) connector. This is a general guide a user can follow, it shows how to create a CAR file and import it onto the Integration Cloud. For information on configuring the FHIR connector, you can follow the document here.[2] Please note that if you wants to add custom server certificates into the client truststore or requires any custom configurations, you need to create custom docker image and deploy it in WSO2 Integration Cloud. [3] [1]. https://docs.wso2.com/display/ IntegrationCloud/Use+a+WSO2+ ESB+Connector+to+Invoke+Third+ Party+Functionality [2]. https://docs.wso2.com/display/ ESBCONNECTORS/FHIR+REST+ Connector [3]. https://docs.wso2.com/display/ In...

Sometimes, you may require to access your tenant by WSO2 cloud team, to investigate a issue, do some configurations changes on behalf of you, etc... This blog will say how you can allow WSO2 cloud team to access your tenant. 1. Go to cloud organization management portal: https://cloudmgt.cloud.wso2. com/cloudmgt/site/pages/ organization.jag 2. Click on check box (Allow Access to WSO2 Support) inline with your tenant name Later you can remove it clicking on the check box agina.

Let's say, we have a use case which is deployed in Integration Cloud and that involves number of applications. There can be a PHP/Web application which user interact, ESB which provide integration with number of systems and DSS to manipulate database. So let's say we want to start/stop these 3 applications as a group. But at the moment, Integration Cloud does not provide any grouping. So you have to login to the Integration Cloud and go to each and every application and start/stop those. To make this little easier, we can use Integration Cloud REST API and write our own script. This is the script to start the all applications as a group. You need to provide username, password, organization name and file which contains application list with versions How to execute this script ./startProject.sh <username> <password> <orgnaizationName> wso2Project.txt wso2Project.txt file content should be like this. There you should provide applicationName and ve...

Currently, the WSO2 Integration Cloud supports adding multiple database users for a same database, but does not support changing user privileges. Let's say someone has a requirement of using same database via two different user, one user has full access, where other user should have READ_ONLY access. How we do this in Integration Cloud? We are planning to add this as feature to change the user permissions, but until that you can do it as I have mentioned below. Steps: 1. Login Create a database with a user 2. Once you create a database you can see it as below, and you can add another user when clicking on the All users icon 3. There you can create new user or you can attach existing user to the same database I added two users  u_mb_2NNq0tjT and  test_2NNq0tjT to the database wso2mb_esbtenant1 My requirement is to give full access to the  u_mb_2NNq0tjT  user and remove INSERT permission from  test_2NNq0tjT  user. 4. Login to ...

This blog post guides you on how to run Jenkins in WSO2 Integration Cloud  and configure it to build an GitHub project. Currently the WSO2 Integration Cloud does not support Jenkins as a app type, but we can use Custom docker app type with Jenkins docker image. First we need to find out, proper Jenkins docker image, which we can use for this  or we have to build it from the scratch. If you go to https://hub.docker.com/_/jenkins/ you can find official Jenkins images in docker hub, but we can't use this images as it is due to several reasons. So I'm going to create a fork of https://github.com/jenkinsci/docker  and do some changes to the Dockerfile. I use the https://github.com/amalkasubasinghe/docker/tree/alpine branch here. A. You will see it has VOLUMN mount - at the moment WSO2 Integration Cloud does not allow you to upload an image which has VOLUMN mount. So we need to comment it out #VOLUME /var/jenkins_home B. My plan is to build Git hub proje...

Here are the instructions to change the Organisation Name: 1. Go to Organization Page from Cloud management app. 2. Select the organization that you want to change and select profile 3. Change the Organization name and update the profile How to change the Organization Key: Changing Organization Key is not possible. We generate the  key  from the  organization  name users provide at the registration time. It is a unique value and plays a major role in multi-tenancy. We have certain internal criteria for this  key . Another reason why we cannot do this is, we are using the  organization   key  in the internal registries when storing API related metadata. So, if we  change  it, there is a data migration involved.

Let's say you want to change the organisation name appear in invoices when you subscribe to a paid plan. Here are the instructions: 1. Login to the WSO2 Cloud and go the the Accounts page. 2. You can find the contact information in the Accounts page. Click on 'update contact Info'. 3. Change the organization name, Add the organization name which you want to display in the invoice. 4. Save the changes. 5. You can see the changed organization name in the Accounts Summary.

Here are the instructions: 1. Go to: https://cloudmgt.cloud.wso2.com/cloudmgt/site/pages/account-summary.jag 2. Log in with your WSO2 credentials (email and password), 3. Click the 'New Payment Method' button: 4. Supply the new credit card information, click the Payment Info button and then the Proceed button. Let us know if you need further help :)

Currently we have 6 app types in WSO2 App Cloud and when we load a app home page of created applications we can see a section called "Endpoints". This blog post is about how we load endpoints per each and every app type and it's implementation Loading endpoints for Java web application, Jaggery and PHP app types for these 3 app types, user have to define the application context, when creating an application as shown in below image. Then we append that context to the app version url/default url and display in app home page as below. Loading endpoints for Microservices app type for microservices app type, microservices 2.0.0 itself provides a swagger url, we just display the swagger url here. Loading endpoints for WSO2 dataservices app type for dataservices app type, we need to invoke the ServiceAdmin soap service to get the endpoints. So we developed a axis2service and deployed in dss runtime, which invokes the ServiceAdmin and return the endpoints...

Currently, WSO2 App Cloud follows the container based approach to provide different runtime to deploy application artifacts. Likewise we can follow the same approach to deploy ESB car file as a app type in WSO2 App Cloud. But, our requirement is to provide a separate cloud perspective (view) for end users for integration solutions, so we thought to generalize the app cloud to operate in two modes (as app cloud and integration cloud) on single app cloud deployment. 1. We need two different URLs ( https://apps.cloud.wso2.com and https://integration.cloud.wso2.com ) to login to separate clouds. How SSO works : Currently, when a user login, it redirect to WSO2IS for SSO and then it comes to app cloud with https://apps.cloud.wso2.com url. Same as when user requests integration cloud it should redirect to WSO2IS and then it comes to the app cloud with https://integration.cloud.wso2.com url. For that we use 2 different issuers and 2 SPs configured in IS side. When the r...