Skip to main content

Bundle different WSO2 products into one and run in one runtime environment

Example: Bundle API Manager, ESB and BAM into one bundle and run in single JVM.

We use WSO2 Carbon [1] as the platform and on top of that we have developed reusable features. Each WSO2 product is a collection of features.
So,there are two options to achieve this requirement;
A) Take WSO2 Carbon and install required features related to API Manager, ESB and BAM on it [2]
B) Take any product (eg: ESB) and install required features of other products (eg: API Manager and BAM) [3]
[1] https://docs.wso2.com/display/Carbon420/WSO2+Carbon+Documentation
[2] https://docs.wso2.com/display/Carbon420/Feature+Management
[3] https://docs.wso2.com/display/ESB481/Working+with+Features


Installing Carbon 4.2.0 based features on Carbon 4.4.0 is wrong and not allowed. Use WSO2 Carbon 4.2.0 feature repo and install the required features on WSO2 Carbon 4.2.0 (or on any WSO2 Carbon 4.2.0 based product as described above).

Features are available on the feature repo only when the products which use those features are released (each WSO2 Product is a collection of features. Please refer [4] for more information).
For example if you consider WSO2 ESB 4.8.1 which is based on WSO2 Carbon 4.2.0, features used for WSO2 ESB 4.8.1 are available on the feature repo when WSO2 ESB 4.8.1 is released.
[4] https://docs.wso2.com/display/Carbon420/Carbon+Architecture

WSO2 Carbon 4.3.0 and 4.4.0 was released very recently. At the moment not all products are released based on those version.






Labels:

Comments

Post a Comment

Popular posts from this blog

How to generate random unique number in SOAP UI request

eg 1: ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} eg 2: ${=java.util.UUID.randomUUID()} ${=java.util.UUID.randomUUID()} ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf
Post a Comment
Read more

Tips on using environment variables in WSO2 Integration Cloud

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 ...
Post a Comment
Read more

WSO2 ESB communication with WSO2 ESB Analytics

This blog post is about how & what ports involved when connecting from WSO2 ESB to WSO2 ESB Analytics. How to configure: This document explains how to configure it https://docs.wso2.com/display/ESB500/Prerequisites+to+Publish+Statistics Let's say we have WSO2 ESB  and WSO2 ESB Analytics packs we want to run in same physical machine, then we have to offset one instance.  But we don't want to do that since WSO2 ESB Analytics by default come with the offset. So WSO2ESB will run on 9443 port, WSO2 ESB Analytics will run on 9444 port WSO2 ESB publish data to the WSO2 ESB Analytics via thrift. By default thrift port is 7611 and corresponding ssl thrift port is 7711 (7611+100), check the data-bridge-config.xml file which is in analytics server config directory .  Since we are shipping analytics products with offset 1 then thrift ports are 7612 and ssl port is 7712. Here, ssl port (7712) is used for initial authentication purposes of data publisher ...
Post a Comment
Read more