yumani.blogspot.com
Yumani's Blog: Using operations scope to hold my values while iterating
http://yumani.blogspot.com/2014/04/using-operations-scope-to-hold-my.html
Day to day experience at WSO2. Saturday, April 5, 2014. Using operations scope to hold my values while iterating. Iterator mediator breaks a message from the given xpath pattern and produces smaller messages. If you need to collect an attribute value throughout the iteration, how do you do it? With lot of help from IsuruU. A] - Request message. Here is my insquence:. InSequence iterate xmlns:m0="http:/ services.samples" continueParent="true" preservePayload="true" attachPath="/ m0:getQuote" expressio...
yumani.blogspot.com
Yumani's Blog: RhinoEngine} java.lang.reflect.InvocationTargetException when acessing APIM-store -- was my fault
http://yumani.blogspot.com/2014/02/rhinoengine-javalangreflectinvocationta.html
Day to day experience at WSO2. Wednesday, February 5, 2014. RhinoEngine} java.lang.reflect.InvocationTargetException when acessing APIM-store - was my fault. I had following exception when accessing APIM store in distributed setup:. This has been due to an unclosed tag in store/repository/conf/api-manager.xml. TID: [0] [AM] [2014-02-06 10:41:49,048] ERROR {org.jaggeryjs.scriptengine.engine.RhinoEngine} - {org.jaggeryjs.scriptengine.engine.RhinoEngine}. At org.jaggeryjs.jaggery.core.manage...At org.ja...
yumani.blogspot.com
Yumani's Blog: Patch Management System - developed, maintained, enhanced using WSO2 Carbon products
http://yumani.blogspot.com/2015/06/patch-management-system-developed.html
Day to day experience at WSO2. Saturday, June 27, 2015. Patch Management System - developed, maintained, enhanced using WSO2 Carbon products. WSo2 support patching in brief. Patch Management Tool (PMT). So as described in above the main purposes of PMT are managing patching process, generating patch numbers, archiving patch metadata and providing search facility. This was initially introduced and designed by Samisa as a pet project for which Lasindu, Pulasthi helped with writing extensions as part of...
yumani.blogspot.com
Yumani's Blog: JTW test cases and queries related to WSO2 Carbon 4.2.0
http://yumani.blogspot.com/2015/03/jtw-test-cases-and-queries-related-to.html
Day to day experience at WSO2. Sunday, March 22, 2015. JTW test cases and queries related to WSO2 Carbon 4.2.0. JWT stands for JSON Web Token. Used for authentication as well as resource access. Decoding and verifying signed JWT token. Sample Java code to validate the signature is available here - http:/ xacmlinfo.org/2015/03/19/validate-and-process-jwt-tokens-with-java/. Is token generation and authentication happening in a different webapp in wso2 IS? How to generate custom tokens? There was a use case...
yumani.blogspot.com
Yumani's Blog: EnableSecureVault in API Manager 1.6.0
http://yumani.blogspot.com/2014/02/enablesecurevault-in-api-manager-160.html
Day to day experience at WSO2. Friday, February 14, 2014. EnableSecureVault in API Manager 1.6.0. 1 Change element EnableSecureVault in APIM HOME /repository/conf/api-manager.xml to true. 2 Update synapse.properties file in APIM HOME /repository/conf with following synapse property. synapse.xpath.func.extensions=org.wso2.carbon.mediation.security.vault.xpath.SecureVaultLookupXPathFunctionProvider. 3 Run the cipher tool available in APIM HOME /bin to create secret repositories. Property in the api's with;.
yumani.blogspot.com
Yumani's Blog: API Manager - Restricted by tenant
http://yumani.blogspot.com/2014/01/api-manager-restricted-by-tenant.html
Day to day experience at WSO2. Wednesday, January 22, 2014. API Manager - Restricted by tenant. We had a query on concept of 'Restricted by Tenant' in APIM Manager. There is tenant1, where creator created an API and publisher published it. If API is set to "Public", everyone sees it, as expected. If API is set to "Restricted by tenant", no one sees it, not even the subscriber who is in the same tenant! Why is it so:. Of course this does not allow same API to be viewed among allowed tenants.
yumani.blogspot.com
Yumani's Blog: hazelcast.max.no.heartbeat.seconds property
http://yumani.blogspot.com/2015/06/hazelcastmaxnoheartbeatseconds-property.html
Day to day experience at WSO2. Thursday, June 18, 2015. Hazelcast.max.no.heartbeat.seconds property. Hazelcast, uses heart beat monitoring as a fault detection mechanism where, the nodes sends heart beats to other nodes. If a heart beat message is not received by a given amount of time, then Hazelcast assumes the node is dead. This is configured via hazelcast.max.no.heartbeat.seconds property. By default, this is set to 600 seconds. The optimum value for this property would depend on your system.
yumani.blogspot.com
Yumani's Blog: Adding proxy server behind WSO2 ESB
http://yumani.blogspot.com/2015/05/adding-proxy-server-behind-wso2-esb.html
Day to day experience at WSO2. Sunday, May 31, 2015. Adding proxy server behind WSO2 ESB. When the message flow needs to be routed through a proxy, you need to add following parameters to transportSender configuration in axis2.xml. HttpproxyHost - proxy server's host name. HttpproxyPort - port number of the proxy server. Any host that need to by pass above proxy. Else you can set Java networking properties. I have my transport sender in axis2.xml configured as below:. Proxy name="Echo viaProxy" transport...
yumani.blogspot.com
Yumani's Blog: Fine Grained Authorization scenario
http://yumani.blogspot.com/2014/04/fine-grained-authorization-scenario.html
Day to day experience at WSO2. Sunday, April 6, 2014. Fine Grained Authorization scenario. This is actually a common scenario which I will also be posting in my blog. A request coming from the client will be authenticated at WSO2 ESB proxy, which acts as a XACML PEP and authorizes the request to access the back-end service by processing the request at WSO2 IS which acts as the XACML PDP. So the actors in the scenario are;. PEP - Policy Enforcement Point - WSO2 ESB. PDP - Policy Decision Point - WSO2 IS.
yumani.blogspot.com
Yumani's Blog: What happens to HTTP transport when service level security is enabled in carbon 4.2.0
http://yumani.blogspot.com/2014/04/enabling-and-diabling-of-https.html
Day to day experience at WSO2. Monday, April 7, 2014. What happens to HTTP transport when service level security is enabled in carbon 4.2.0. I was under impression this was a bug and am sure many of us will assume like that. In carbon 4.2.0 products for example WSO2 AS 5.2.0, when you apply security, the HTTP endpoint disables and disappears from service dashboard as well. In earlier carbon versions this did not happen, both endpoints use to still appear even if you have enabled security.
