We're evaluating a few WSO2 products for a solution. As part of the requirement we need to deploy the WSO2 analytics car file in DAS(preferably version 3.1.0). When we deploy the car it fails due to an incompatibility in the EsbAnalytics-ExecutionPlan-statistic execution plan file. A closer look inside the file shows that it refers to a custom stream function extension called esbAnalytics, this file is not available inside the car file or in the usual locations such as lib and dropins.
Can some one please share the steps to make the analytics car work in DAS?
If you are going to use ESB analytics features in DAS, you need to install its features first. The ESB analytics extension comes with those features.
Refer to the documentation[1] for the instructions on installing ESB analytics features on DAS 3.1.0.
[1] https://docs.wso2.com/display/DAS310/Working+with+Product+Specific+Analytics+Profiles#618096e7e77848b3abcc5785000d53cc
Related
I am trying to access the registry of WSO2 BPS and WSO2 ESB from Java in order to automatically fill the registry based on the data I provide.
I have already found a number of resources about the required Java code and dependencies, this being the most helpful one: [WSO2 Governance Registry]Using WSRegistryServiceClient. However, the approach described in these resources depends on the WSRegistryService service. This service is included in Governance Registry by default, but not in the other WSO2 products. I have verified that my code works for the Governance Registry. For any other WSO2 product on my machine, I get this error:
The service cannot be found for the endpoint reference (EPR) https://localhost:9445/services/WSRegistryService
I found an old thread suggesting that it should be possible to install the WSRegistryService on other WSO2 products as well, but I have not been able to find out how to do so. I can't seem to find it within the features I can install from the web console of the products. I have also tried manually copying the relevant jar from the plugins directory of Governance Registry into the plugins directory of other products, but that doesn't seem to be sufficient.
Note that my application for filling the registry will not be running on the carbon server whose registry I want to access, so using CarbonContext.getThreadLocalCarbonContext() (an approach I found in some other articles) is not an option.
I think your referring to how to install features to WSO2 products,
Please find this documentation.
I have a requirement to version control my "registry" artifacts (i.e. wsdls, xsds, xsls), that I currently upload to the WSO2 ESB 4.8.1 server. I'm not using WSO2 GREG at the moment. I came across the "Registry Resources Project" facility which I think would help me achieve this. However I'm unsure as to whether this facility can only be used with GREG or with ESB as well. Is there a way for me to generate a CApp Project, include the the above "Registry Resources Project" in it, and deploy it to my ESB server?
I've come across blogs which deploy standard ESB artifacts in the way, but not the registry. -
Please help....
You can create required registry resources as specified in the creating registry resources documentation. Once you have created your registry resource project, then you need to create composite application archive as specified in the Creating a Composite Application Archive (CAR) file documentation.
When you are creating CAR file, you need to specify server role as EnterpriseServiceBus to deploy your registry resources in ESB.
Thanks.
Kinda new to WSO products. Installed WSO DSS 3.5.0 and created a simple test data service following all the instructions on WSO documentation. it is working fine except I can not find out how to implement the security for data service as mentioned in the documentation :
https://docs.wso2.com/display/DSS350/Filtering+Content+to+Specific+User+Roles
The problem is that Quality Of Service Configuration Panel is empty in my web console and no menu exists there for security or anything else except the edit data service menu as you can see :
Spending a full day reading docs searching googling etc for the solution I have not found any..
Anyone else facing this same issue? should I activate it in features somehow or is there another product needed to be installed together with DSS for this to work?
WSO2 DSS 3.5.0 is carbon kernel 4.4.x based product. From kernel 4.4.x on wards QoS features are removed from the kernel.
You have to use WSO2 Developer Studio to implemnet QoS for the requirement.
After study WSO2 products, seems I got the following concepts, all of them are only my understanding, I don't know whether is correct or not, please advice:
All the products are running in Carbon which is a 'container' of the wso2 products, something like JSP like stuffs running in tomcat. am I right?
if No.1 is correct, so 'Enterprise Service Bus', 'Identity Server', 'Data Service Server', 'Governance Reistry' etc are all running in Carbon Server, actually I downloaded all the products, and I found they are all released with carbon together, which mean I can use command to start the management console directly, and each of them can running themselves, they have there own management console. right?
after I read Carbon user guide, it says 'all the products of wso2 are the components of Carbon', so I think 'Enterprise Service Bus', 'Identity Server', 'Data Service Server', 'Governance Reistry' can be put into one management console, which mean they can be integrated together, after I started Carbon server, all the features are running together?
I'm sorry ask such kind a stupid question, but after read many articles I still cant find out the structure between them, please advice, thanks in advance.
WSO2 middleware products come with a bunch of components. These are based on Java OSGi. So every product comes with a set of OSGi bundles (in OSGi terminology). Carbon is a core framework that's common to every product. This is again a bunch of OSGi components. Carbon core (which is also reffered to as just Carbon) contains a set of must have bundles. Logging, clustering, security etc... Carbon is a separate download also which you can run. Running carbon itself by its own is not very interesting unless you're doing something specific and you know what you're doing.
Now, coming back to the products .. each product have carbon core plus some more OSGi components. These additional components reflect product specific functionality. For example if you take the ESB, it's carbon core plus additional components that makes it an "ESB". Likewise for other products.
You can take the carbon server and install all these additional features. Feature installation is done via the same technology Eclipse is using to install plugins. Since everything is an OSGi bundle there has to be an OSGi container that all these run on. Carbon is running on top of Equinox OSGi container.
So Tomcat is also a separate OSGi bundle. You can install these components into any running carbon server and instantly add webapp hosting capability.
Yes. All WSO2 products are running inside WSO2 Carbon which is mainly a OSGi based framework.
Yes. A WSO2 Product (e.g., ESB) is a specialized Carbon framework. Management console is a part of Carbon where you can install external features to the product / uninstall existing features in the product to customize the product.
Yes theoretically. If the Carbon concept is correctly implemented in all the components of WSO2, they (ESB, IS, DSS as you said) should be installable in a single Carbon server without any problem using the WSO2 Feature Manager. But due to some dependency conflicts and version conflicts sometimes it may not be possible if you try to do it. But still you can resolve these OSGi conflicts in code level and make it possible to make them compatible, if you want.
Actually all the WSO2 products share the WSO2 components seamlessly among their products already. And in some instances we recommend to install multiple products in a single Carbon server. For example CEP feature is asked to be installed in BAM product when the user wants to use CEP as a realtime data processing solution with the BAM. For most other product combinations we have not yet tested well so the conflicts can occur. Thats why I said this theoretical.
The installation instructions are clear how to download a .zip for an individual product (e.g. ESB, Application Server, Mashup Server). But based on the OSGi component architecture, I thought it would be possible to, for example, add Mashup Server functionality to an existing install of the ESB. I've looked at the Feature Manager, and tried adding a repository (http://dist.wso2.org/p2/carbon/releases/3.2.4/), but have not had success.
Any guidance appreciated.
It's possible to install different features via the feature manager, but you have to determine the correct version of the feature compliant with the target server. For example, to install BPEL features to WSO2 ESB 4.0.2, first find the related WSO2 Carbon platform version. This can be determined by the version of $ESB-HOME/repository/components/plugins/org.wso2.carbon.core-x.x.x.jar. So if WSO2 ESB 4.0.2 is the target server, then the version of org.wso2.carbon.core jar would be 3.2.2. So the relevant BPEL feature version is 3.2.2.
You can read more about Installing+Features and How install the BPEL features via Feature Manager.
Please refer to WSO2 release matrix [1] in order to match the correct version
By looking at it, you can easily find the Carbon version of any product version.
For example ESB 4.0.2 has the carbon version 3.2.2
[1] http://wso2.com/products/carbon/release-matrix/