Re: [Dev] [GSoC 2017][ESB]Native inbound and connector for IBM MQ 8.0
Hi Dushan, Thank you for your question because it made me to study more about the project. Using native IBM classes to communicate with IBM MQ, increases the performance and gives more ibm mq specific features such as SSL authentication, connection caching and more message handling options. [1] that you provided uses ibm jars written for jms transport and we can write inbound that uses only ibm mq java classes by avoiding jms.jar dependencies as I have tried in [2]. [1] https://github.com/Kirishanthy/IBM-MQ-J/tree/master/ibmmq-inbound-endpoint-1.0.0/src/main/java/org/wso2/carbon/inbound/ibmmq/poll [2] https://github.com/chanakadinesh/MQ-Client Thanks, On Tue, Mar 21, 2017 at 9:39 AM, Dushan Abeyruwan <dus...@wso2.com> wrote: > Hi All, > Can you explain or distinguish the effort from [1]? what sort of > additional features can we expect from Inbound EP for 8.0? > > [1] https://github.com/Kirishanthy/IBM-MQ-J/tree/master/ > ibmmq-inbound-endpoint-1.0.0/src/main/java/org/wso2/carbon/ > inbound/ibmmq/poll > > Cheers, > Dushan > > On Mon, Mar 20, 2017 at 3:41 AM, Chanaka Balasooriya <chanaka...@gmail.com > > wrote: > >> Hi Malaka, >> >> Need some clarifications, >> >> >> As you can see in the sample that I implemented [1] I have used >> asynchronous message listener which is provided by JMS, for the consumer >> >> to retrieve messages from the server. Is it ok to use that JMS listener >> >> when implementing inbound or do I need to look for a pattern like pooling >> for message retrieving in consumer? >> >> [1] https://github.com/chanakadinesh/MQ-Client/blob/master/s >> rc/main/java/esb/wso2/org/client/MQConsumer.java >> >> Thanks, >> >> >> On Mon, Mar 20, 2017 at 10:14 AM, Malaka Silva <mal...@wso2.com> wrote: >> >>> Looks good >>> >>> On Sun, Mar 19, 2017 at 1:29 PM, Chanaka Balasooriya < >>> chanaka...@gmail.com> wrote: >>> >>>> Hi Malaka, >>>> >>>> As you suggested, I implemented a simple method for generating >>>> SSLContext by reading trustStore and keyStore files [1]. >>>> >>>> So those System properties were removed. For now this was checked only >>>> for self-signed certificates and I will try to use WSO2 ESB default >>>> trustStore and KeyStore files >>>> >>>> to generate this SSL Contex later. >>>> >>>> [1] https://github.com/chanakadinesh/MQ-Client/blob/master/src/m >>>> ain/java/esb/wso2/org/client/MQConnectionBuilder.java >>>> >>>> Thanks, >>>> >>>> On Sun, Mar 19, 2017 at 5:41 AM, Malaka Silva <mal...@wso2.com> wrote: >>>> >>>>> Hi Chanaka, >>>>> >>>>> This looks good so far. >>>>> >>>>> Can we check if it is possible to have an alternative way to set SSL >>>>> details other than system properties with IBM MQ client libraries. >>>>> >>>>> The reason for that is we are limiting our self to one set of >>>>> properties per JVM. >>>>> >>>>> eg: System.setProperty( >>>>> >>>>> On Sat, Mar 18, 2017 at 11:41 PM, Chanaka Balasooriya < >>>>> chanaka...@gmail.com> wrote: >>>>> >>>>>> Hi Malaka, >>>>>> >>>>>> After some effort I could upgrade MQ-Client [1] that I created >>>>>> earlier, to establish SSL connections with IBM WebSphere MQ. >>>>>> Please have a look. >>>>>> >>>>>> Here I used SSL_RSA_WITH_3DES_EDE_CBC_SHA Cipher Suit and IBM MQ >>>>>> self signed certificate. >>>>>> During that implementation I could realized that even though IBM MQ >>>>>> supports a long list of cipher suits only few cipher suits are supported >>>>>> for >>>>>> Oracal Java JVM. So I will list down all possible ciper-suits in near >>>>>> future. >>>>>> >>>>>> Now I believe that I have a solid background of the project idea and >>>>>> am looking forward to do this in GSoC. >>>>>> >>>>>> [1]https://github.com/chanakadinesh/MQ-Client >>>>>> >>>>>> Thanks, >>>>>> >>>>>> On Mon, Mar 13, 2017 at 6:15 PM, Malaka Silva <mal...@wso2.com> >>>>>> wrote: >>>>>> >>>>>>> Hi Chanaka,
Re: [Dev] [GSoC 2017][ESB]Native inbound and connector for IBM MQ 8.0
Hi Malaka, Need some clarifications, As you can see in the sample that I implemented [1] I have used asynchronous message listener which is provided by JMS, for the consumer to retrieve messages from the server. Is it ok to use that JMS listener when implementing inbound or do I need to look for a pattern like pooling for message retrieving in consumer? [1] https://github.com/chanakadinesh/MQ-Client/blob/master/src/main/java/esb/wso2/org/client/MQConsumer.java Thanks, On Mon, Mar 20, 2017 at 10:14 AM, Malaka Silva <mal...@wso2.com> wrote: > Looks good > > On Sun, Mar 19, 2017 at 1:29 PM, Chanaka Balasooriya <chanaka...@gmail.com > > wrote: > >> Hi Malaka, >> >> As you suggested, I implemented a simple method for generating SSLContext >> by reading trustStore and keyStore files [1]. >> >> So those System properties were removed. For now this was checked only >> for self-signed certificates and I will try to use WSO2 ESB default >> trustStore and KeyStore files >> >> to generate this SSL Contex later. >> >> [1] https://github.com/chanakadinesh/MQ-Client/blob/master/src/ >> main/java/esb/wso2/org/client/MQConnectionBuilder.java >> >> Thanks, >> >> On Sun, Mar 19, 2017 at 5:41 AM, Malaka Silva <mal...@wso2.com> wrote: >> >>> Hi Chanaka, >>> >>> This looks good so far. >>> >>> Can we check if it is possible to have an alternative way to set SSL >>> details other than system properties with IBM MQ client libraries. >>> >>> The reason for that is we are limiting our self to one set of properties >>> per JVM. >>> >>> eg: System.setProperty( >>> >>> On Sat, Mar 18, 2017 at 11:41 PM, Chanaka Balasooriya < >>> chanaka...@gmail.com> wrote: >>> >>>> Hi Malaka, >>>> >>>> After some effort I could upgrade MQ-Client [1] that I created earlier, >>>> to establish SSL connections with IBM WebSphere MQ. >>>> Please have a look. >>>> >>>> Here I used SSL_RSA_WITH_3DES_EDE_CBC_SHA Cipher Suit and IBM MQ self >>>> signed certificate. >>>> During that implementation I could realized that even though IBM MQ >>>> supports a long list of cipher suits only few cipher suits are supported >>>> for >>>> Oracal Java JVM. So I will list down all possible ciper-suits in near >>>> future. >>>> >>>> Now I believe that I have a solid background of the project idea and am >>>> looking forward to do this in GSoC. >>>> >>>> [1]https://github.com/chanakadinesh/MQ-Client >>>> >>>> Thanks, >>>> >>>> On Mon, Mar 13, 2017 at 6:15 PM, Malaka Silva <mal...@wso2.com> wrote: >>>> >>>>> Hi Chanaka, >>>>> >>>>> Also better to think about how to secure the connections with >>>>> credentials and SSL. >>>>> >>>>> On Mon, Mar 13, 2017 at 11:04 AM, Chanaka Balasooriya < >>>>> chanaka...@gmail.com> wrote: >>>>> >>>>>> Hi Malaka, >>>>>> >>>>>> I've been studying specifications of using native IBM MQ jars with >>>>>> the help of resources you sent and I could understand that It gives more >>>>>> flexibility on configuring >>>>>> connections and some binding options. >>>>>> >>>>>> I tried to implement sample MQ-Client [1] that can connect to IBM MQ >>>>>> without .binding file and we can improve that to implement inbound >>>>>> endpoint >>>>>> and the connector. please have a look. >>>>>> I am going to improve that MQ-Client to support more ibm specific >>>>>> options such as SSL connections within next few days. >>>>>> >>>>>> [1]https://github.com/chanakadinesh/MQ-Client >>>>>> >>>>>> Thanks, >>>>>> >>>>>> On Thu, Mar 2, 2017 at 4:51 PM, Malaka Silva <mal...@wso2.com> wrote: >>>>>> >>>>>>> Hi Chanaka, >>>>>>> >>>>>>> Following will help. >>>>>>> >>>>>>> [1] http://mrmalakasilva.blogspot.com/2013/10/connecting-mechani >>>>>>> sms-other-than.html >>>>>>> [2] http://www-01.ibm.com/support/docview.wss?uid=swg24037500 >>>>>>> [3] http://stackoverflow.com
Re: [Dev] [GSoC 2017][ESB]Native inbound and connector for IBM MQ 8.0
Hi Malaka, As you suggested, I implemented a simple method for generating SSLContext by reading trustStore and keyStore files [1]. So those System properties were removed. For now this was checked only for self-signed certificates and I will try to use WSO2 ESB default trustStore and KeyStore files to generate this SSL Contex later. [1] https://github.com/chanakadinesh/MQ-Client/blob/master/src/main/java/esb/wso2/org/client/MQConnectionBuilder.java Thanks, On Sun, Mar 19, 2017 at 5:41 AM, Malaka Silva <mal...@wso2.com> wrote: > Hi Chanaka, > > This looks good so far. > > Can we check if it is possible to have an alternative way to set SSL > details other than system properties with IBM MQ client libraries. > > The reason for that is we are limiting our self to one set of properties > per JVM. > > eg: System.setProperty( > > On Sat, Mar 18, 2017 at 11:41 PM, Chanaka Balasooriya < > chanaka...@gmail.com> wrote: > >> Hi Malaka, >> >> After some effort I could upgrade MQ-Client [1] that I created earlier, >> to establish SSL connections with IBM WebSphere MQ. >> Please have a look. >> >> Here I used SSL_RSA_WITH_3DES_EDE_CBC_SHA Cipher Suit and IBM MQ self >> signed certificate. >> During that implementation I could realized that even though IBM MQ >> supports a long list of cipher suits only few cipher suits are supported for >> Oracal Java JVM. So I will list down all possible ciper-suits in near >> future. >> >> Now I believe that I have a solid background of the project idea and am >> looking forward to do this in GSoC. >> >> [1]https://github.com/chanakadinesh/MQ-Client >> >> Thanks, >> >> On Mon, Mar 13, 2017 at 6:15 PM, Malaka Silva <mal...@wso2.com> wrote: >> >>> Hi Chanaka, >>> >>> Also better to think about how to secure the connections with >>> credentials and SSL. >>> >>> On Mon, Mar 13, 2017 at 11:04 AM, Chanaka Balasooriya < >>> chanaka...@gmail.com> wrote: >>> >>>> Hi Malaka, >>>> >>>> I've been studying specifications of using native IBM MQ jars with the >>>> help of resources you sent and I could understand that It gives more >>>> flexibility on configuring >>>> connections and some binding options. >>>> >>>> I tried to implement sample MQ-Client [1] that can connect to IBM MQ >>>> without .binding file and we can improve that to implement inbound endpoint >>>> and the connector. please have a look. >>>> I am going to improve that MQ-Client to support more ibm specific >>>> options such as SSL connections within next few days. >>>> >>>> [1]https://github.com/chanakadinesh/MQ-Client >>>> >>>> Thanks, >>>> >>>> On Thu, Mar 2, 2017 at 4:51 PM, Malaka Silva <mal...@wso2.com> wrote: >>>> >>>>> Hi Chanaka, >>>>> >>>>> Following will help. >>>>> >>>>> [1] http://mrmalakasilva.blogspot.com/2013/10/connecting-mechani >>>>> sms-other-than.html >>>>> [2] http://www-01.ibm.com/support/docview.wss?uid=swg24037500 >>>>> [3] http://stackoverflow.com/questions/2692070/connecting-to >>>>> -a-websphere-mq-in-java-with-ssl-keystore >>>>> [4] http://www.kevinboone.net/simplewmqclient.html >>>>> >>>>> On Wed, Mar 1, 2017 at 3:04 PM, Chanaka Balasooriya < >>>>> chanaka...@gmail.com> wrote: >>>>> >>>>>> Hi Malaka, >>>>>> >>>>>> Thank you for your response. >>>>>> >>>>>> As you mentioned, to understand the advantage of using native IBM MQ >>>>>> jars I will need to compare the current ESB IBM MQ support with native >>>>>> IBM >>>>>> MQ. >>>>>> So please share if you have any recommended reading materials to know >>>>>> more about IBM MQ other than [1] and it will be really helpful to get a >>>>>> better approach to this project. >>>>>> >>>>>> (I do confirm that I am a full time student and eligible to >>>>>> participate GSoC. ) >>>>>> >>>>>> [1] https://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0 >>>>>> /com.ibm.mq.helphome.v80.doc/WelcomePagev8r0.html >>>>>> >>>>>> Thanks, >>>>>> >>>>>> On Tue, Feb 28, 2017 at 9:39 PM, M
Re: [Dev] [GSoC 2017][ESB]Native inbound and connector for IBM MQ 8.0
Hi Malaka, After some effort I could upgrade MQ-Client [1] that I created earlier, to establish SSL connections with IBM WebSphere MQ. Please have a look. Here I used SSL_RSA_WITH_3DES_EDE_CBC_SHA Cipher Suit and IBM MQ self signed certificate. During that implementation I could realized that even though IBM MQ supports a long list of cipher suits only few cipher suits are supported for Oracal Java JVM. So I will list down all possible ciper-suits in near future. Now I believe that I have a solid background of the project idea and am looking forward to do this in GSoC. [1]https://github.com/chanakadinesh/MQ-Client Thanks, On Mon, Mar 13, 2017 at 6:15 PM, Malaka Silva <mal...@wso2.com> wrote: > Hi Chanaka, > > Also better to think about how to secure the connections with credentials > and SSL. > > On Mon, Mar 13, 2017 at 11:04 AM, Chanaka Balasooriya < > chanaka...@gmail.com> wrote: > >> Hi Malaka, >> >> I've been studying specifications of using native IBM MQ jars with the >> help of resources you sent and I could understand that It gives more >> flexibility on configuring >> connections and some binding options. >> >> I tried to implement sample MQ-Client [1] that can connect to IBM MQ >> without .binding file and we can improve that to implement inbound endpoint >> and the connector. please have a look. >> I am going to improve that MQ-Client to support more ibm specific options >> such as SSL connections within next few days. >> >> [1]https://github.com/chanakadinesh/MQ-Client >> >> Thanks, >> >> On Thu, Mar 2, 2017 at 4:51 PM, Malaka Silva <mal...@wso2.com> wrote: >> >>> Hi Chanaka, >>> >>> Following will help. >>> >>> [1] http://mrmalakasilva.blogspot.com/2013/10/connecting-mechani >>> sms-other-than.html >>> [2] http://www-01.ibm.com/support/docview.wss?uid=swg24037500 >>> [3] http://stackoverflow.com/questions/2692070/connecting-to >>> -a-websphere-mq-in-java-with-ssl-keystore >>> [4] http://www.kevinboone.net/simplewmqclient.html >>> >>> On Wed, Mar 1, 2017 at 3:04 PM, Chanaka Balasooriya < >>> chanaka...@gmail.com> wrote: >>> >>>> Hi Malaka, >>>> >>>> Thank you for your response. >>>> >>>> As you mentioned, to understand the advantage of using native IBM MQ >>>> jars I will need to compare the current ESB IBM MQ support with native IBM >>>> MQ. >>>> So please share if you have any recommended reading materials to know >>>> more about IBM MQ other than [1] and it will be really helpful to get a >>>> better approach to this project. >>>> >>>> (I do confirm that I am a full time student and eligible to participate >>>> GSoC. ) >>>> >>>> [1] https://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0 >>>> /com.ibm.mq.helphome.v80.doc/WelcomePagev8r0.html >>>> >>>> Thanks, >>>> >>>> On Tue, Feb 28, 2017 at 9:39 PM, Malaka Silva <mal...@wso2.com> wrote: >>>> >>>>> Hi Chanaka, >>>>> >>>>> Thank you for your interest in this project. >>>>> >>>>> Currently with WSO2 ESB there is a generic JMS inbound endpoint that >>>>> can be used to consume messages from different brokers. [1] >>>>> >>>>> However there are complexities when configuring WSO2 ESB with IBM MQ. >>>>> This is mainly due to class loading issues. Also IBM provides more >>>>> customized options that are written on top of JMS transport. >>>>> >>>>> Part of this project is to identify those and develop a new Inbound >>>>> Endpoint to support this integration. >>>>> >>>>> Also please confirm that you are a full time student and currently not >>>>> employed since it is against GSoC rules. >>>>> >>>>> [1] https://docs.wso2.com/display/ESB500/JMS+Inbound+Protocol >>>>> >>>>> On Tue, Feb 28, 2017 at 4:47 PM, Chanaka Balasooriya < >>>>> chanaka...@gmail.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I am Chanaka Balasooriya, final year undergraduate at Computer >>>>>> Science and Engineering Department, University of Moratuwa. I am highly >>>>>> interested in distributed computing and Java related things and it led me >>>>>> to select and find more about this project. I was an
Re: [Dev] [GSoC 2017][ESB]Native inbound and connector for IBM MQ 8.0
Hi Malaka, I've been studying specifications of using native IBM MQ jars with the help of resources you sent and I could understand that It gives more flexibility on configuring connections and some binding options. I tried to implement sample MQ-Client [1] that can connect to IBM MQ without .binding file and we can improve that to implement inbound endpoint and the connector. please have a look. I am going to improve that MQ-Client to support more ibm specific options such as SSL connections within next few days. [1]https://github.com/chanakadinesh/MQ-Client Thanks, On Thu, Mar 2, 2017 at 4:51 PM, Malaka Silva <mal...@wso2.com> wrote: > Hi Chanaka, > > Following will help. > > [1] http://mrmalakasilva.blogspot.com/2013/10/connecting- > mechanisms-other-than.html > [2] http://www-01.ibm.com/support/docview.wss?uid=swg24037500 > [3] http://stackoverflow.com/questions/2692070/connecting- > to-a-websphere-mq-in-java-with-ssl-keystore > [4] http://www.kevinboone.net/simplewmqclient.html > > On Wed, Mar 1, 2017 at 3:04 PM, Chanaka Balasooriya <chanaka...@gmail.com> > wrote: > >> Hi Malaka, >> >> Thank you for your response. >> >> As you mentioned, to understand the advantage of using native IBM MQ jars >> I will need to compare the current ESB IBM MQ support with native IBM MQ. >> So please share if you have any recommended reading materials to know >> more about IBM MQ other than [1] and it will be really helpful to get a >> better approach to this project. >> >> (I do confirm that I am a full time student and eligible to participate >> GSoC. ) >> >> [1] https://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0. >> 0/com.ibm.mq.helphome.v80.doc/WelcomePagev8r0.html >> >> Thanks, >> >> On Tue, Feb 28, 2017 at 9:39 PM, Malaka Silva <mal...@wso2.com> wrote: >> >>> Hi Chanaka, >>> >>> Thank you for your interest in this project. >>> >>> Currently with WSO2 ESB there is a generic JMS inbound endpoint that can >>> be used to consume messages from different brokers. [1] >>> >>> However there are complexities when configuring WSO2 ESB with IBM MQ. >>> This is mainly due to class loading issues. Also IBM provides more >>> customized options that are written on top of JMS transport. >>> >>> Part of this project is to identify those and develop a new Inbound >>> Endpoint to support this integration. >>> >>> Also please confirm that you are a full time student and currently not >>> employed since it is against GSoC rules. >>> >>> [1] https://docs.wso2.com/display/ESB500/JMS+Inbound+Protocol >>> >>> On Tue, Feb 28, 2017 at 4:47 PM, Chanaka Balasooriya < >>> chanaka...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I am Chanaka Balasooriya, final year undergraduate at Computer Science >>>> and Engineering Department, University of Moratuwa. I am highly interested >>>> in distributed computing and Java related things and it led me to select >>>> and find more about this project. I was an intern at WSO2 and I have a keen >>>> knowledge about WSO2ESB, inbound endpoints and transports since my >>>> internship project was related to them. >>>> >>>> Regarding this project, I have already started to follow the WSO2 doc >>>> about current implementation of WSO2 ESB for IBM WebSphere MQ through JMS >>>> transport. I would be grateful if you can give me some suggestions and >>>> materials to understand the project more. >>>> >>>> Thanks, >>>> -- >>>> Chanaka Balasooriya >>>> Undergraduate >>>> Department of Computer Science and Engineering >>>> University of Moratuwa >>>> +9471 294 7898 <071%20294%207898> >>>> >>> >>> >>> >>> -- >>> >>> Best Regards, >>> >>> Malaka Silva >>> Associate Director / Architect >>> M: +94 777 219 791 <+94%2077%20721%209791> >>> Tel : 94 11 214 5345 >>> Fax :94 11 2145300 <011%202%20145300> >>> Skype : malaka.sampath.silva >>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >>> Blog : http://mrmalakasilva.blogspot.com/ >>> >>> WSO2, Inc. >>> lean . enterprise . middleware >>> https://wso2.com/signature >>> http://www.wso2.com/about/team/malaka-silva/ >>> <http://wso2.com/about/team/malaka-silva/> >>> https://store.wso2.com/store/ &g
Re: [Dev] [GSoC 2017][ESB]Native inbound and connector for IBM MQ 8.0
Hi Malaka, Thank you for your response. As you mentioned, to understand the advantage of using native IBM MQ jars I will need to compare the current ESB IBM MQ support with native IBM MQ. So please share if you have any recommended reading materials to know more about IBM MQ other than [1] and it will be really helpful to get a better approach to this project. (I do confirm that I am a full time student and eligible to participate GSoC. ) [1] https://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.helphome.v80.doc/WelcomePagev8r0.html Thanks, On Tue, Feb 28, 2017 at 9:39 PM, Malaka Silva <mal...@wso2.com> wrote: > Hi Chanaka, > > Thank you for your interest in this project. > > Currently with WSO2 ESB there is a generic JMS inbound endpoint that can > be used to consume messages from different brokers. [1] > > However there are complexities when configuring WSO2 ESB with IBM MQ. This > is mainly due to class loading issues. Also IBM provides more customized > options that are written on top of JMS transport. > > Part of this project is to identify those and develop a new Inbound > Endpoint to support this integration. > > Also please confirm that you are a full time student and currently not > employed since it is against GSoC rules. > > [1] https://docs.wso2.com/display/ESB500/JMS+Inbound+Protocol > > On Tue, Feb 28, 2017 at 4:47 PM, Chanaka Balasooriya <chanaka...@gmail.com > > wrote: > >> Hi, >> >> I am Chanaka Balasooriya, final year undergraduate at Computer Science >> and Engineering Department, University of Moratuwa. I am highly interested >> in distributed computing and Java related things and it led me to select >> and find more about this project. I was an intern at WSO2 and I have a keen >> knowledge about WSO2ESB, inbound endpoints and transports since my >> internship project was related to them. >> >> Regarding this project, I have already started to follow the WSO2 doc >> about current implementation of WSO2 ESB for IBM WebSphere MQ through JMS >> transport. I would be grateful if you can give me some suggestions and >> materials to understand the project more. >> >> Thanks, >> -- >> Chanaka Balasooriya >> Undergraduate >> Department of Computer Science and Engineering >> University of Moratuwa >> +9471 294 7898 <071%20294%207898> >> > > > > -- > > Best Regards, > > Malaka Silva > Associate Director / Architect > M: +94 777 219 791 <+94%2077%20721%209791> > Tel : 94 11 214 5345 > Fax :94 11 2145300 > Skype : malaka.sampath.silva > LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 > Blog : http://mrmalakasilva.blogspot.com/ > > WSO2, Inc. > lean . enterprise . middleware > https://wso2.com/signature > http://www.wso2.com/about/team/malaka-silva/ > <http://wso2.com/about/team/malaka-silva/> > https://store.wso2.com/store/ > > Don't make Trees rare, we should keep them with care > -- Chanaka Balasooriya Undergraduate Department of Computer Science and Engineering University of Moratuwa +9471 294 7898 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [GSoC 2017][ESB]Native inbound and connector for IBM MQ 8.0
Hi, I am Chanaka Balasooriya, final year undergraduate at Computer Science and Engineering Department, University of Moratuwa. I am highly interested in distributed computing and Java related things and it led me to select and find more about this project. I was an intern at WSO2 and I have a keen knowledge about WSO2ESB, inbound endpoints and transports since my internship project was related to them. Regarding this project, I have already started to follow the WSO2 doc about current implementation of WSO2 ESB for IBM WebSphere MQ through JMS transport. I would be grateful if you can give me some suggestions and materials to understand the project more. Thanks, -- Chanaka Balasooriya Undergraduate Department of Computer Science and Engineering University of Moratuwa +9471 294 7898 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
