<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Nipuni Chandrasoma on Medium]]></title>
        <description><![CDATA[Stories by Nipuni Chandrasoma on Medium]]></description>
        <link>https://medium.com/@nipunichandrasoma?source=rss-cbbcbfa39f59------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*41GGT0M9enjZMA3-S1H1Eg.jpeg</url>
            <title>Stories by Nipuni Chandrasoma on Medium</title>
            <link>https://medium.com/@nipunichandrasoma?source=rss-cbbcbfa39f59------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 20:21:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nipunichandrasoma/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Changing the default home of WSO2 In-Place Updates]]></title>
            <link>https://medium.com/@nipunichandrasoma/changing-the-default-home-of-wso2-in-place-updates-6678e9270e48?source=rss-cbbcbfa39f59------2</link>
            <guid isPermaLink="false">https://medium.com/p/6678e9270e48</guid>
            <category><![CDATA[wso2-update-manager]]></category>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[wum]]></category>
            <dc:creator><![CDATA[Nipuni Chandrasoma]]></dc:creator>
            <pubDate>Fri, 01 Feb 2019 05:59:33 GMT</pubDate>
            <atom:updated>2019-03-20T17:34:09.258Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/557/0*hWa9d-k0Vh4syV5O.png" /></figure><p>1.Stop the WSO2 product server if it is running.<br>2. Go to the &lt;PRODUCT_HOME&gt;/bin directory and run the in-place updates tool that is appropriate to your OS:</p><pre>./update_linux --version (On Linux)<br>./update_darwin --version (On OS X)</pre><p>When the above command has executed, a file called config.yaml will be created under &lt;PRODUCT_HOME&gt;/updates directory. This file will be available only if you execute the above command.</p><p>3. In this file, you can define a new location under <strong>wso2.updates</strong> field.</p><pre>username: <a href="/service/mailto:nipunic@wso2.com">user@wso2.com</a><br>channel: full<br>active.prod: /home/user/wso2am-2.2.0<br><strong>wso2.updates: /tmp/updates<br></strong>uuid: be345a2c-e853-4ade-69a2-5b66f0fe82ab<br>repositories:<br>  wso2:<br>    enabled: true<br>    name: WSO2 Update Repository<br>    url: <a href="https://api.updates.wso2.com/">https://api.updates.wso2.com</a><br>    tokenurl: <a href="https://api.updates.wso2.com/token">https://api.updates.wso2.com/token</a><br>    appkey: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx<br>    refreshtoken: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx<br>    accesstoken: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx<br>product:<br>  pattern: wso2am-2.2.0<br>  name: wso2am<br>  version: 2.2.0<br>  kernel-version: 4.4.26<br>  last.backup: /home/user/backup/wso2am-2.2.0-1548997467526<br>  last.backup.size: 561976767<br>  default.md5: 08d5374303f3337432a0eefee5325889</pre><p>4. Save the file.</p><p>After this change whenever you use the WSO2 In-Place executable all the downloads will be placed under the new location.</p><p>Please find the official documentation on WSO2 Using WSO2 In-Place Updates [1]</p><p>[1] <a href="https://docs.wso2.com/display/updates/Using+WSO2+In-Place+Updates">https://docs.wso2.com/display/updates/Using+WSO2+In-Place+Updates</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6678e9270e48" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Changing WUM Home- WSO2 Updates Manager]]></title>
            <link>https://medium.com/@nipunichandrasoma/changing-wum-home-wso2-updates-manager-9f1f5051e11e?source=rss-cbbcbfa39f59------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f1f5051e11e</guid>
            <category><![CDATA[wum]]></category>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[wso2-update-manager]]></category>
            <dc:creator><![CDATA[Nipuni Chandrasoma]]></dc:creator>
            <pubDate>Fri, 01 Feb 2019 05:49:38 GMT</pubDate>
            <atom:updated>2019-02-01T05:49:38.134Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/557/0*2dmTKuyi_2FfaSUc.png" /></figure><p>We cannot move the .wum3/ directory from the default location. But we can move the Product directory which will be created in the default .wum-wso2/. Product directory has all the products and updates. Other files and directories will be maintained within the .wum3/ as it is.</p><p>Use below command to change the location of the local product repository with the WUM 3.0.</p><pre>wum config local.product.repo ~/&lt;location&gt;</pre><p>Please refer to the documentation [1] on the WUM for more details.</p><p>[1] <a href="https://docs.wso2.com/display/updates/WUM+Commands+Guide#WUMCommandsGuide-wumconfig">https://docs.wso2.com/display/updates/WUM+Commands+Guide#WUMCommandsGuide-wumconfig</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f1f5051e11e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WSO2 MB Message Store]]></title>
            <link>https://medium.com/@nipunichandrasoma/wso2-mb-message-store-672030958d06?source=rss-cbbcbfa39f59------2</link>
            <guid isPermaLink="false">https://medium.com/p/672030958d06</guid>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[wso2-mb-message-store]]></category>
            <category><![CDATA[message-store]]></category>
            <dc:creator><![CDATA[Nipuni Chandrasoma]]></dc:creator>
            <pubDate>Sun, 24 Jun 2018 07:31:08 GMT</pubDate>
            <atom:updated>2018-06-24T07:31:08.340Z</atom:updated>
            <content:encoded><![CDATA[<p>The newest member of WSO2 ESB message stores. This is introduced from the EI 6.1.1.</p><p>In WSO2 ESB we use message stores to store message which sends through the ESB. This is a useful feature because in case of unavailability of an endpoint we can make sure that message is not lost. But due to shortcomings of existing message stores within ESB such as server level configurations WSO2 has developed WSO2 MB Message store which can be configured on just application level.</p><p><strong>Creating Message Store</strong></p><p>In management console,</p><ol><li>Click the Main tab on the Management Console, go to Manage -&gt; Service Bus and then click Message Stores. The Manage Message Stores screen appears.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/312/1*byeuelIJLJxMnNdRWf9opw.png" /></figure><p>2. Click Add Message Stores. You will see the list of available message stores.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rRvI2BJZYud0d8WKUoUx2g.png" /></figure><p>3. Click the WSO2 MB Message Store.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kkqbI1-ixbLD7520TWRCww.png" /></figure><p>You will be needed to add below information when creating the message store.</p><p><strong>Message Store Name : </strong>A unique name should be given here.</p><p><strong>Initial Context Factory : </strong>This specifies the JNDI initial context factory class (java.naming.factory.initial). This class implements the implement the java.naming.spi.InitialContextFactory interface. The value is set to org.wso2.andes.jndi.PropertiesFileInitialContextFactory, by default.</p><p><strong>Queue Connection Factory</strong> : This is the connection factory Url for connecting to WSO2 MB. By default, the value is set to amqp://admin:admin@clientID/carbon?brokerlist=&#39;tcp://localhost:5672&#39;.</p><p>When using EI 6.1.1 the Message Broker’s is default offset is set to 3. Therefore the port value needs to be changed as</p><blockquote>tcp://localhost:5675.</blockquote><p><strong>JNDI Queue Name : </strong>The name of the queue in the broker that will store messages. When using this message store the Message Broker server should be up and running. Queue with the provided name should be already deployed.</p><p><strong>JMS API Specification Version</strong> : The JMS API version to be used. Possible values are 1.1 or 1.0. The value is set to 1.1, by default.</p><p>These are the required configurations that needs to be done before using the WSO2 MB Message Store.</p><p>Additionally you can set the parameters for guaranteed delivery of the message.</p><p><strong>Enable Producer Guaranteed Delivery : </strong>This flag specifies whether guaranteed delivery is enabled on the producer side. The value is set to False, by default.</p><p><strong>Fail over Message Store: </strong>The message store to which the store mediator should send messages when the original message store fails.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7yv91AY9l_xBTJt6BrgzxQ.png" /><figcaption>Sample Message Store configurations</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=672030958d06" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>