Copy Right
© 2012 WSO2 Inc. Powered by 
Configuring WSO2 ESB V4.0.0 with QpidWSO2 ESB V4.0.0 comes with Apache Qpid as built-in JMS provider. In this knowledge base, we will look at the configurations for Apache Qpid as the JMS transport provider as well as the back-end queue for Message Store functionality.
Crypto Caching for Web Services hosted in WSO2 Carbon PlatformAll products of WSO2 platform uses the Apache Rampart to provide security for Web Services. As a result, all features of Apache Rampart are inherited by the WSO2 products. Crypto objects are used to store properties that required to perform signature/encryption. Crypto objects have information such as as crypto provider, keystore and its password. Until now, Crypto objects were initialized on per call basis. Handling a http-get request and invoking an external Web service with WSO2 ESBThis Knowledge Base discusses how to handle a rest like http-get request from WSO2 ESB and call an external web service. In order to clarify this subject, we use the simple usecase described. The relevant configuration files, steps to run the sample and the messages flowing through the system is shown.
Troubleshooting WSO2 Product ClustersWhat do you do when the WSO2 product cluster hangs during restart? WSO2 ESB and Apache Qpid Setup GuideThis Knowledge Base item explains how to setup WSO2 ESB and Apache Qpid from scratch. This Guide doesn't contain any internal message flow configurations of ESB. In this setup, as the first step, WSO2 ESB (ESB1) is forwarding messages that come to the proxy, to Apache Qpid. Once messages come to a particular queue WSO2 ESB (ESB2) picks them from Apache Qpid and forwards it to some endpoint. Introduction of Component test automation frameworkTest automation is one of the most important aspects in the software QA process. It reduces testing time and costs in testing software. This Knowledge-Base Item explains how to develop a test automation framework for WSO2 Carbon platform testing.
WSO2 Carbon Studio: How to point to a resource from your SequenceUsing the registry as a source of data is now becoming a very common practice. In this short knowledge base I'm explaining how you can specify an XSLT to a XSLT mediator. This covers the scenarios where the XSLT is location in the registry or in the local file system. WSO2 Carbon Studio: How to point to a non-anonymous endpoint from a sequenceTodays style is to write your synapse configuration files independently as much as possible because when things change the updates does not have to propagate through the whole synapse configuration. Even though they are independent, we'll have to connect them together to make it meaningful. In this short KB I'm going to explain the scenario of connecting sequences in Carbon Studio with named or referenced endpoints.
|