Re: [Dev] IAM: Error while uploading the metadata file in Sp creation.
>>> doFilter(CharacterSetFilter.java:65) >>>> at org.apache.catalina.core.ApplicationFilterChain. >>>> internalDoFilter(ApplicationFilterChain.java:241) >>>> at org.apache.catalina.core.ApplicationFilterChain.doFilter( >>>> ApplicationFilterChain.java:208) >>>> at org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter( >>>> HttpHeaderSecurityFilter.java:124) >>>> at org.apache.catalina.core.ApplicationFilterChain. >>>> internalDoFilter(ApplicationFilterChain.java:241) >>>> at org.apache.catalina.core.ApplicationFilterChain.doFilter( >>>> ApplicationFilterChain.java:208) >>>> at org.apache.catalina.core.StandardWrapperValve.invoke( >>>> StandardWrapperValve.java:219) >>>> at org.apache.catalina.core.StandardContextValve.invoke( >>>> StandardContextValve.java:110) >>>> at org.apache.catalina.core.StandardHostValve.invoke( >>>> StandardHostValve.java:169) >>>> at org.apache.catalina.valves.ErrorReportValve.invoke( >>>> ErrorReportValve.java:103) >>>> at org.wso2.carbon.identity.context.rewrite.valve. >>>> TenantContextRewriteValve.invoke(TenantContextRewriteValve.java:80) >>>> at org.wso2.carbon.identity.authz.valve.AuthorizationValve.invoke( >>>> AuthorizationValve.java:91) >>>> at org.wso2.carbon.identity.auth.valve.AuthenticationValve. >>>> invoke(AuthenticationValve.java:60) >>>> at org.wso2.carbon.tomcat.ext.valves.CompositeValve. >>>> continueInvocation(CompositeValve.java:99) >>>> at org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1. >>>> invoke(CarbonTomcatValve.java:47) >>>> at org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke( >>>> TenantLazyLoaderValve.java:57) >>>> at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer. >>>> invokeValves(TomcatValveContainer.java:47) >>>> at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke( >>>> CompositeValve.java:62) >>>> at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValv >>>> e.invoke(CarbonStuckThreadDetectionValve.java:159) >>>> at org.apache.catalina.valves.AccessLogValve.invoke( >>>> AccessLogValve.java:962) >>>> at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve. >>>> invoke(CarbonContextCreatorValve.java:57) >>>> at org.apache.catalina.core.StandardEngineValve.invoke( >>>> StandardEngineValve.java:116) >>>> at org.apache.catalina.connector.CoyoteAdapter.service( >>>> CoyoteAdapter.java:445) >>>> at org.apache.coyote.http11.AbstractHttp11Processor.process( >>>> AbstractHttp11Processor.java:1115) >>>> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler. >>>> process(AbstractProtocol.java:637) >>>> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor. >>>> doRun(NioEndpoint.java:1775) >>>> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor. >>>> run(NioEndpoint.java:1734) >>>> at java.util.concurrent.ThreadPoolExecutor.runWorker( >>>> ThreadPoolExecutor.java:1149) >>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run( >>>> ThreadPoolExecutor.java:624) >>>> at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run( >>>> TaskThread.java:61) >>>> at java.lang.Thread.run(Thread.java:748) >>>> Caused by: org.wso2.carbon.identity.base.IdentityException: Issuer >>>> cannot be found in the provided arguments. >>>> at org.wso2.carbon.identity.core.dao.SAMLSSOServiceProviderDAO. >>>> addServiceProvider(SAMLSSOServiceProviderDAO.java:216) >>>> at org.wso2.carbon.identity.core.persistence. >>>> IdentityPersistenceManager.addServiceProvider( >>>> IdentityPersistenceManager.java:239) >>>> at org.wso2.carbon.identity.sso.saml.admin.SAMLSSOConfigAdmin. >>>> uploadRelyingPartyServiceProvider(SAMLSSOConfigAdmin.java:163) >>>> ... 73 more >>>> >>>> >>>> >>>> >>>> *Thanks & Best Regards!* >>>> >>>> *Achini Jayasena* >>>> *Software Engineer - QA | WSO2* >>>> >>>> Email: achi...@wso2.com >>>> Mobile: +943 882 897 >>>> >>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>> >>>> On Mon, Jul 16, 2018 at 10:46 AM, Achini Jayasena >>>> wrote: >>>> >>>>> Hi All, >>>>> >>>>> Scenario: SP creation - metadata configuration. >>>>> >>>>> Uploading the metadata file gives following error >>>>> Error: Metadata uploading failed. Error while uploading the service >>>>> provider. >>>>> >>>>> I use the same metadata file given in the reference [1]. Anybody have >>>>> idea to sort this out? >>>>> >>>>> [1] Reference: https://docs.wso2.com/display/ >>>>> IS550/Adding+and+Configuring+a+Service+Provider# >>>>> AddingandConfiguringaServiceProvider-Metadatafileconfiguration >>>>> >>>>> Please find the metadata file attached herewith. >>>>> >>>>> >>>>> *Thanks & Best Regards!* >>>>> >>>>> *Achini Jayasena* >>>>> *Software Engineer - QA | WSO2* >>>>> >>>>> Email: achi...@wso2.com >>>>> Mobile: +943 882 897 >>>>> >>>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>>> >>>> >>>> >>> >>> >>> -- >>> Farasath Ahamed >>> Senior Software Engineer, WSO2 Inc.; http://wso2.com >>> Mobile: +94777603866 >>> Blog: blog.farazath.com >>> Twitter: @farazath619 <https://twitter.com/farazath619> >>> <http://wso2.com/signature> >>> >>> >>> >>> >> > > -- > > *Ruwan Abeykoon* > *Associate Director/Architect**,* > *WSO2, Inc. http://wso2.com <https://wso2.com/signature> * > *lean.enterprise.middleware.* > > -- > You received this message because you are subscribed to the Google Groups > "WSO2 Documentation Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to documentation+unsubscr...@wso2.com. > For more options, visit https://groups.google.com/a/wso2.com/d/optout. > -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB-4.9.0]NPE at save configuration
patcher.java:486) >> at >> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:411) >> at >> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:338) >> at >> org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.forward(RequestDispatcherAdaptor.java:30) >> at >> org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.forward(ContextPathServletAdaptor.java:362) >> at >> org.apache.tiles.servlet.context.ServletTilesRequestContext.forward(ServletTilesRequestContext.java:198) >> at >> org.apache.tiles.servlet.context.ServletTilesRequestContext.dispatch(ServletTilesRequestContext.java:185) >> at >> org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:419) >> at >> org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:370) >> at org.wso2.carbon.ui.action.ActionHelper.render(ActionHelper.java:52) >> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:101) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) >> at >> org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37) >> at >> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61) >> at >> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128) >> at >> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) >> at >> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68) >> at >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) >> at >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) >> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) >> at >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) >> at >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) >> at >> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61) >> at >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) >> at >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) >> at >> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) >> at >> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) >> at >> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504) >> at >> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170) >> at >> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) >> at >> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99) >> at >> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49) >> at >> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62) >> at >> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159) >> at >> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950) >> at >> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57) >> at >> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) >> at >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421) >> at >> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074) >> at >> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611) >> at >> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1739) >> at >> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1698) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >> at >> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) >> at java.lang.Thread.run(Thread.java:745) >> >> >> -Ajith >> >> -- >> Ajith Vitharana. >> >> WSO2 Inc. - http://wso2.com >> Email : aji...@wso2.com >> Blog: http://vitharana.org >> Mobile : +1-812-360-5335 >> >> > > > -- > Ajith Vitharana. > > WSO2 Inc. - http://wso2.com > Email : aji...@wso2.com > Blog: http://vitharana.org > Mobile : +1-812-360-5335 > > -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB-4.9.0]NPE at save configuration
Done. Thank you! On Mon, Oct 5, 2015 at 9:17 AM, Ajith Vitharana <aji...@wso2.com> wrote: > Please remove "DurableSubscriberEndpoint" /> from sub1_fails sequence. > > -Ajith > > On Sun, Oct 4, 2015 at 11:44 PM, Nirdesha Munasinghe <nirde...@wso2.com> > wrote: > >> Hi Ajith, >> >> Thanks for the info. I made the suggested edits. >> >> Cheers, >> -Nirdesha >> >> On Mon, Oct 5, 2015 at 2:59 AM, Ajith Vitharana <aji...@wso2.com> wrote: >> >>> While debugging found that task manager is not initialize. This is due >>> to outdated configurations. The EIP sample should be updated with following >>> configuration changes. >>> >>> 1. add >> "org.wso2.carbon.mediation.ntask.NTaskTaskManager"/> >>> 2. class should be org.apache.synapse.message.processor.*impl* >>> .forwarder.ScheduledMessageForwardingProcessor >>> 3. target.endpoint parameter is missing in messageProcessor >>> configurations. >>> >>> [1] >>> https://docs.wso2.com/display/ESB490/Sample+702%3A+Introduction+to+Message+Forwarding+Processor >>> >>> -Ajith >>> >>> On Sun, Oct 4, 2015 at 3:54 PM, Ajith Vitharana <aji...@wso2.com> wrote: >>> >>>> Hi All, >>>> >>>> First I replaced the source view from the configuration [1] and it >>>> worked. Then I just click on update button. Now each time getting this NPE. >>>> >>>> [1] >>>> https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber >>>> >>>> >>>> [2015-10-04 15:50:36,869] ERROR - ConfigAdmin Error while updating the >>>> Synapse configuration >>>> j*ava.lang.NullPointerException* >>>> * at >>>> org.apache.synapse.message.processor.impl.ScheduledMessageProcessor.destroy(ScheduledMessageProcessor.java:309)* >>>> at >>>> org.wso2.carbon.mediation.configadmin.ConfigurationUpdater.cleanupCurrentConfiguration(ConfigurationUpdater.java:202) >>>> at >>>> org.wso2.carbon.mediation.configadmin.ConfigurationUpdater.update(ConfigurationUpdater.java:130) >>>> at >>>> org.wso2.carbon.mediation.configadmin.ConfigAdmin.updateConfiguration(ConfigAdmin.java:150) >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>> at >>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) >>>> at >>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>>> at java.lang.reflect.Method.invoke(Method.java:606) >>>> at >>>> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212) >>>> at >>>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117) >>>> at >>>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40) >>>> at >>>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110) >>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) >>>> at >>>> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169) >>>> at >>>> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82) >>>> at >>>> org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45) >>>> at >>>> org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77) >>>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442) >>>> at >>>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430) >>>> at >>>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225) >>>> at >>>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149) >>>> at >>>> org.wso2.carbon.mediation.configadmin.stub.ConfigServiceAdminStub.updateConfiguration(ConfigServiceAdminStub.java:1340) >>>> at >>>> org.wso2.carbon.mediation.configadmin.ui.ConfigManagementClient.updateConfiguration(ConfigManagementClient.java:98) >>>> at >>>> org.apache.jsp.configadmi
Re: [Dev] [VOTE] Release G-Reg 5.0.0 RC 2
The context sensitive help links are in the product UIs. AFAIK, these links are component-based rather than product based? Please correct me if I am wrong. If they are component-based, we cannot link to the wiki of a specific product from there as many other products might also be using the same component. Maybe we should simply disable these help links until we find a better way to maintain them. Thanks, -Nirdesha On Wed, Sep 2, 2015 at 10:30 AM, Pubudu Priyashan <pubu...@wso2.com> wrote: > Hi Nirdesha, > > Can we please point the current context sensitive help pages to relevant > product documentation of GReg 5.0.0 release? > > Cheers, > > Pubudu D.P > Senior Software Engineer - QA Team | WSO2 inc. > Mobile : +94775464547 > > On Wed, Sep 2, 2015 at 9:42 AM, Ajith Vitharana <aji...@wso2.com> wrote: > >> >> >> On Wed, Sep 2, 2015 at 12:08 AM, Evanthika Amarasiri <evanth...@wso2.com> >> wrote: >> >>> Ack! >>> >>> @Chalitha/Thaya/Pubudu. Please note. >>> >> >> And all the context sensitive help pages are outdated . >> >> -Ajith >> >> >>> >>> Regards, >>> Evanthika Amarasiri >>> Senior Technical Lead - Quality Assurance >>> Mobile: +94773125935 >>> Blog: evanthika.blogspot.com >>> >>> wso2.com lean.enterprise.middleware >>> >>> On Wed, Sep 2, 2015 at 9:32 AM, Ajith Vitharana <aji...@wso2.com> wrote: >>> >>>> Hi All >>>> >>>> This is non a bug but please fix the about page if possible because >>>> this is a major release. (find the attached image) >>>> >>>> -Ajith >>>> >>>> >>>> >>>> >>>> >>>> On Tue, Sep 1, 2015 at 11:05 PM, Prasanna Dangalla <prasa...@wso2.com> >>>> wrote: >>>> >>>>> Hi All, >>>>> >>>>> *This is the RC 2 release candidate of G-Reg 5.0.0 * >>>>> >>>>> This release fixes the following issues: >>>>> >>>>> https://wso2.org/jira/browse/REGISTRY-2895?filter=12384 >>>>> https://wso2.org/jira/browse/REGISTRY-2908 >>>>> >>>>> Please download, test and vote. Please refer the release verification >>>>> guide for detailed information on verifying this release. >>>>> >>>>> *Source & binary distribution files:* >>>>> >>>>> >>>>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/org/wso2/greg/wso2greg/5.0.0/ >>>>> >>>>> *Maven staging repo:* >>>>> >>>>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-026/ >>>>> >>>>> *The tag to be voted upon:* >>>>> >>>>> https://github.com/wso2/product-greg/tree/v5.0.0-rc2 >>>>> >>>>> >>>>> >>>>> [*+*] Stable - go ahead and release >>>>> >>>>> [*-*] Broken - do not release (explain why) >>>>> >>>>> Thanks and Regards >>>>> G-Reg team >>>>> >>>>> Prasanna Dangalla >>>>> Software Engineer, WSO2, Inc.; http://wso2.com/ >>>>> lean.enterprise.middleware >>>>> >>>>> cell: +94 718 11 27 51 >>>>> twitter: @prasa77 >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Ajith Vitharana. >>>> >>>> WSO2 Inc. - http://wso2.com >>>> Email : aji...@wso2.com >>>> Blog: http://vitharana.org >>>> Mobile : +1-812-360-5335 >>>> >>>> >>> >> >> >> -- >> Ajith Vitharana. >> >> WSO2 Inc. - http://wso2.com >> Email : aji...@wso2.com >> Blog: http://vitharana.org >> Mobile : +1-812-360-5335 >> >> > -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB-Connector] Google Spreadsheet Connector Documentation not Changed
Copying Nisrin... On Sun, Aug 16, 2015 at 2:58 PM, Rajjaz Mohammed raj...@wso2.com wrote: Hi All, Please Note $Subject . Authentication method changed to OAuth 2.0 so init method should be oAuth2init . but its still not updated in Documentation. -- Thank you Best Regards *Rajjaz HM* Associate Software Engineer WSO2 Inc. http://wso2.com/ lean | enterprise | middleware Mobile : +94752833834 Email :raj...@wso2.com LinkedIn | Blogger | WSO2 Profile http://wso2.com/about/team/mohammer_rajjaz/ -- You received this message because you are subscribed to the Google Groups WSO2 Documentation Group group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/d/optout. -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] WSO2 Data Analytics Server 3.0.0 Beta Released!
by giving 'from' 'to' time-stamp - [BAM-2065 https://wso2.org/jira/browse/BAM-2065] - Event Tracer does not work properly - [BAM-2068 https://wso2.org/jira/browse/BAM-2068] - New Dashboard pages get duplicate content as the first page - [BAM-2071 https://wso2.org/jira/browse/BAM-2071] - Include 'Complex Event Processor' Server Role - [BAM-2076 https://wso2.org/jira/browse/BAM-2076] - Error when using the analytics API in remote mode with HTTPS protocol. - [BAM-2078 https://wso2.org/jira/browse/BAM-2078] - Remove streaming events from spark feaure to different bundle from spark.core. - [BAM-2080 https://wso2.org/jira/browse/BAM-2080] - Back up tool does not back up data batch wise - [BAM-2084 https://wso2.org/jira/browse/BAM-2084] - Introduce syncing/flushing for the HDFS Analytics file system Improvements - [BAM-2022 https://wso2.org/jira/browse/BAM-2022] - Enable custom UDFs for DAS - [BAM-2028 https://wso2.org/jira/browse/BAM-2028] - Tune the Spark configurations in DAS for best performance - [BAM-2029 https://wso2.org/jira/browse/BAM-2029] - Implement multiple data sources in DAS - [BAM-2030 https://wso2.org/jira/browse/BAM-2030] - Implement custom analyzer support in spark using registry lookup - [BAM-2048 https://wso2.org/jira/browse/BAM-2048] - Add secure vault support to analytics API configuration - [BAM-2074 https://wso2.org/jira/browse/BAM-2074] - Event sink to store only one event when Realtime (CEP) within DAS is configured in HA mode - [BAM-2075 https://wso2.org/jira/browse/BAM-2075] - Make event sink related parameters configurable with configuration file, and have a worker pool to store the events received. - [BAM-2077 https://wso2.org/jira/browse/BAM-2077] - Introducing AUTO mode in carbon analytics API to switch between LOCAL and REMOTE automatically. - [BAM-2079 https://wso2.org/jira/browse/BAM-2079] - Search a field by its whole content to match the exact content - [BAM-2082 https://wso2.org/jira/browse/BAM-2082] - Multiple Record Store Support - [BAM-2083 https://wso2.org/jira/browse/BAM-2083] - Refactor HBase Analytics Datastore to remove obsolete operations - [BAM-2085 https://wso2.org/jira/browse/BAM-2085] - Add CEP Execution Manager feature to DAS pack Tasks - [BAM-2064 https://wso2.org/jira/browse/BAM-2064] - Rename analytics-dataservice-config.xml to analytics-config.xml - [BAM-2073 https://wso2.org/jira/browse/BAM-2073] - Add disable/enable to analytics components in DAS The documentation for this release can be found at the WSO2 DAS 3.0.0 Documentation https://docs.wso2.com/display/DAS300/WSO2+Data+Analytics+Server+Documentation site. We value your feedback and suggestions are welcome, and issues could be reported at the WSO2 DAS Issue Tracking https://wso2.org/jira/browse/BAM page. Thanks, WSO2 DAS Development Team. [*] Download: https://svn.wso2.org/repos/wso2/people/inosh/wso2das-3.0.0-BETA.zip [*] Documentation: https://docs.wso2.com/display/DAS300/WSO2+Data+Analytics+Server+Documentation [*] Issue reporting: https://wso2.org/jira/browse/BAM -- Gokul Balakrishnan Senior Software Engineer, WSO2, Inc. http://wso2.com Mob: +94 77 593 5789 | +1 650 272 9927 -- Gokul Balakrishnan Senior Software Engineer, WSO2, Inc. http://wso2.com Mob: +94 77 593 5789 | +1 650 272 9927 ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Gimantha Bandara Software Engineer WSO2. Inc : http://wso2.com Mobile : +94714961919 -- Gimantha Bandara Software Engineer WSO2. Inc : http://wso2.com Mobile : +94714961919 -- Regards, Dunith Dhanushka, Senior Software Engineer - BAM, WSO2 Inc, Mobile - +94 71 8615744 Blog - dunithd.wordpress.com http://blog.dunith.com Twitter - @dunithd http://twitter.com/dunithd ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks Best Regards, *Praneesha Chandrasiri* *Technical Writer* *WSO2 Inc. * *Mobile: +(94) 718156888 %2B%2894%29%20718156888* *E-mail: pranee...@wso2.com pranee...@wso2.com* -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/d/optout. -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman
Re: [Dev] Clarification on Require re-subscription functionality
Hi Sewmini, Please note that I changed the doc as described in the JIRA. Added the following note: *If unchecked**, all users who are subscribed to the older version of the API will be automatically subscribed to the new version. If not, they need to subscribe to the new version again.* The JIRA is now closed. I'm still not sure how it will be handled if there are multiple older versions to an API and someone leaves this unchecked when creating a new version. Will be great if someone can clarify that. Thanks, -Nirdesha On Thu, May 21, 2015 at 11:36 AM, Nirdesha Munasinghe nirde...@wso2.com wrote: I also raised a JIRA as the 'deprecate old versions' and 'require re-subscription' options don't show when we try to publish a prototyped API version (with old versions) using the LIfecycle tab: https://wso2.org/jira/browse/APIMANAGER-3624. Thanks, -Nirdesha On Thu, May 21, 2015 at 11:13 AM, Nirdesha Munasinghe nirde...@wso2.com wrote: Hi, If we do not click this option, does it mean that the users who subscribed to the old version do not have to subscribe to the new one again? If that is the case, can someone please explain how to document it if there are multiple old versions (say v1 and v2) with different user subscriptions each. Do all of them get subscribed to v3 automatically? Thanks, -Nirdesha On Wed, May 20, 2015 at 11:08 AM, Sewmini Jayaweera sewm...@wso2.com wrote: Hi, In API manager documentation [1] Require Re-Subscription functionality is being described as Invalidates current user subscriptions, forcing the users to subscribe again. In the product When user publish a new version given 'Require re-subscription' option doesn't invalidates original API subscriptions. There is a mismatch between the functionality and the documentation. I have already reported a documentation jira [2] Will you please confirm that the functionality is correct. [1] https://docs.wso2.com/display/AM190/Publish+the+new+Version+and+Deprecate+the+old [2] https://wso2.org/jira/browse/DOCUMENTATION-1742 Thanks Regards, Sewmini Sewmini Jayaweera *Software Engineer - QA Team* Mobile: +94 (0) 773 381 250 sewm...@wso2.com -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/d/optout. -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Clarification on Require re-subscription functionality
I also raised a JIRA as the 'deprecate old versions' and 'require re-subscription' options don't show when we try to publish a prototyped API version (with old versions) using the LIfecycle tab: https://wso2.org/jira/browse/APIMANAGER-3624. Thanks, -Nirdesha On Thu, May 21, 2015 at 11:13 AM, Nirdesha Munasinghe nirde...@wso2.com wrote: Hi, If we do not click this option, does it mean that the users who subscribed to the old version do not have to subscribe to the new one again? If that is the case, can someone please explain how to document it if there are multiple old versions (say v1 and v2) with different user subscriptions each. Do all of them get subscribed to v3 automatically? Thanks, -Nirdesha On Wed, May 20, 2015 at 11:08 AM, Sewmini Jayaweera sewm...@wso2.com wrote: Hi, In API manager documentation [1] Require Re-Subscription functionality is being described as Invalidates current user subscriptions, forcing the users to subscribe again. In the product When user publish a new version given 'Require re-subscription' option doesn't invalidates original API subscriptions. There is a mismatch between the functionality and the documentation. I have already reported a documentation jira [2] Will you please confirm that the functionality is correct. [1] https://docs.wso2.com/display/AM190/Publish+the+new+Version+and+Deprecate+the+old [2] https://wso2.org/jira/browse/DOCUMENTATION-1742 Thanks Regards, Sewmini Sewmini Jayaweera *Software Engineer - QA Team* Mobile: +94 (0) 773 381 250 sewm...@wso2.com -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/d/optout. -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Clarification on Require re-subscription functionality
Hi, If we do not click this option, does it mean that the users who subscribed to the old version do not have to subscribe to the new one again? If that is the case, can someone please explain how to document it if there are multiple old versions (say v1 and v2) with different user subscriptions each. Do all of them get subscribed to v3 automatically? Thanks, -Nirdesha On Wed, May 20, 2015 at 11:08 AM, Sewmini Jayaweera sewm...@wso2.com wrote: Hi, In API manager documentation [1] Require Re-Subscription functionality is being described as Invalidates current user subscriptions, forcing the users to subscribe again. In the product When user publish a new version given 'Require re-subscription' option doesn't invalidates original API subscriptions. There is a mismatch between the functionality and the documentation. I have already reported a documentation jira [2] Will you please confirm that the functionality is correct. [1] https://docs.wso2.com/display/AM190/Publish+the+new+Version+and+Deprecate+the+old [2] https://wso2.org/jira/browse/DOCUMENTATION-1742 Thanks Regards, Sewmini Sewmini Jayaweera *Software Engineer - QA Team* Mobile: +94 (0) 773 381 250 sewm...@wso2.com -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/d/optout. -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Clarification on Key validator and Key manager server profiles.
Copying Samuel as well... On Thu, May 7, 2015 at 5:47 PM, Amila De Silva ami...@wso2.com wrote: Hi Sewmini, KeyManager configuration will be mainly used when integrating with a Third Party Authorization Server. Configuration specific to the external Authorization Server can be provided under KeyManager section. This is explained in doc link available at [1]. When clustering, you should only change the KeyValidator section. Gateway should know the location of the KeyValidator, so KeyValidator section of Gateway should be configured pointing to KeyValidator component. Store will be talking to KeyVaidator when creating OAuth clients. Therefore , Store should also know the location of KeyValidator. [1] https://docs.google.com/document/d/14y-1QmYsf2sm5n_5nFh8R4fePSxlcdMLO_J4FxTmWyc/edit On Thu, May 7, 2015 at 3:58 PM, Sewmini Jayaweera sewm...@wso2.com wrote: Hi All, As per the offline discussion, Key validator server profile is acting as Key manager when there is no third party Auth server is used. In the API Manager 1.9.0 pack AM_HOME/repository/conf/api-manager.xml Key validator is enabled and Key manager is being commented out by default. 1. Is there a reason why Key Manager configuration is there? 2. If so when should we enable Key manager instead of Key validator? 3. When we are clustering instead of changing Key manager configurations should we change key validation configurations and what are the configurations? Thanks Regards, Sewmini Sewmini Jayaweera *Software Engineer - QA Team* Mobile: +94 (0) 773 381 250 sewm...@wso2.com -- *Amila De Silva* WSO2 Inc. mobile :(+94) 775119302 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Clarification on Key validator and Key manager server profiles.
Hi All, Is this the way to start only the Key Validator components when starting the server: wso2server.sh -Dprofile=api-key-validator Thanks, -Nirdesha On Thu, May 7, 2015 at 5:47 PM, Amila De Silva ami...@wso2.com wrote: Hi Sewmini, KeyManager configuration will be mainly used when integrating with a Third Party Authorization Server. Configuration specific to the external Authorization Server can be provided under KeyManager section. This is explained in doc link available at [1]. When clustering, you should only change the KeyValidator section. Gateway should know the location of the KeyValidator, so KeyValidator section of Gateway should be configured pointing to KeyValidator component. Store will be talking to KeyVaidator when creating OAuth clients. Therefore , Store should also know the location of KeyValidator. [1] https://docs.google.com/document/d/14y-1QmYsf2sm5n_5nFh8R4fePSxlcdMLO_J4FxTmWyc/edit On Thu, May 7, 2015 at 3:58 PM, Sewmini Jayaweera sewm...@wso2.com wrote: Hi All, As per the offline discussion, Key validator server profile is acting as Key manager when there is no third party Auth server is used. In the API Manager 1.9.0 pack AM_HOME/repository/conf/api-manager.xml Key validator is enabled and Key manager is being commented out by default. 1. Is there a reason why Key Manager configuration is there? 2. If so when should we enable Key manager instead of Key validator? 3. When we are clustering instead of changing Key manager configurations should we change key validation configurations and what are the configurations? Thanks Regards, Sewmini Sewmini Jayaweera *Software Engineer - QA Team* Mobile: +94 (0) 773 381 250 sewm...@wso2.com -- *Amila De Silva* WSO2 Inc. mobile :(+94) 775119302 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Clarification on Key validator and Key manager server profiles.
Hi Nuwan, I already changed the docs according to a JIRA (copying Ushani). The relevant configuration in the api-manager.xml file is APIKeyValidator. Calling it the Key Manager might be confusing to users, especially because we also have a separate configuration as APIKeyManager in the same file. Thanks, -Nirdesha On Wed, May 13, 2015 at 5:03 PM, Nuwan Dias nuw...@wso2.com wrote: I don't think we need to complicate this thing of Key-Manager vs Key-Validator. This separation/complication only comes into play when we're actually using an external (third party) key manager. I suggest that we stick to the same terminology (Key Manager) as before for the default key manager. For folks who are interested in using a third party key manager, they are the only ones who would be required to understand the difference between the two and go into the details. Therefore let's just leave the current terminology as is it so we don't mess with the concepts that have already been set. Thanks, NuwanD. On Wed, May 13, 2015 at 11:22 PM, Nirdesha Munasinghe nirde...@wso2.com wrote: Copying Samuel as well... On Thu, May 7, 2015 at 5:47 PM, Amila De Silva ami...@wso2.com wrote: Hi Sewmini, KeyManager configuration will be mainly used when integrating with a Third Party Authorization Server. Configuration specific to the external Authorization Server can be provided under KeyManager section. This is explained in doc link available at [1]. When clustering, you should only change the KeyValidator section. Gateway should know the location of the KeyValidator, so KeyValidator section of Gateway should be configured pointing to KeyValidator component. Store will be talking to KeyVaidator when creating OAuth clients. Therefore , Store should also know the location of KeyValidator. [1] https://docs.google.com/document/d/14y-1QmYsf2sm5n_5nFh8R4fePSxlcdMLO_J4FxTmWyc/edit On Thu, May 7, 2015 at 3:58 PM, Sewmini Jayaweera sewm...@wso2.com wrote: Hi All, As per the offline discussion, Key validator server profile is acting as Key manager when there is no third party Auth server is used. In the API Manager 1.9.0 pack AM_HOME/repository/conf/api-manager.xml Key validator is enabled and Key manager is being commented out by default. 1. Is there a reason why Key Manager configuration is there? 2. If so when should we enable Key manager instead of Key validator? 3. When we are clustering instead of changing Key manager configurations should we change key validation configurations and what are the configurations? Thanks Regards, Sewmini Sewmini Jayaweera *Software Engineer - QA Team* Mobile: +94 (0) 773 381 250 sewm...@wso2.com -- *Amila De Silva* WSO2 Inc. mobile :(+94) 775119302 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- Nuwan Dias Technical Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API manager throttling requirement clarification.
Hi Ushani, Why would the last request (5th one) fail to resource 2 please? Silver throttling tier allows 5 requests per minute, isn't it? Thanks, -Nirdesha On Wed, Apr 29, 2015 at 3:36 PM, Ushani Balasooriya ush...@wso2.com wrote: Hi Sewmini, I think it should work like, 1st 3 requests to Resource 1 = 1st request successful, Next 2 requests unsuccessful due to resource level throttling. Next 5 requests 2 Resource 2 = 1st 4 requests should be successful and last one should be unsucessful due to API level throttling. On Wed, Apr 29, 2015 at 3:23 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Sewmini In your case since you have sent 5 requests to the both of the resources these will be successful due to your API level throttling tier being 5. After that requests will be terminated. Please find the below documentation that will be a help to you https://docs.wso2.com/display/AM180/Key+Concepts#KeyConcepts-Throttlingtiers Thank You Erandi On Wed, Apr 29, 2015 at 3:14 PM, Sewmini Jayaweera sewm...@wso2.com wrote: Hi Ushani, When I say unsuccessful, what i meant was request fails due to resource level throttling exceeding. Say I have given API level throttling - silver (5) App level throttling - unlimited API resource 1 throttling - bronze (1) API resource 2 throttling - unlimited When I send first three requests to resource 1 and next 5 requests to resource 2, my last 3 request should fail due to API level throttling is it ? Thanks Regards, Sewmini Sewmini Jayaweera *Software Engineer - QA Team* Mobile: +94 (0) 773 381 250 sewm...@wso2.com On Wed, Apr 29, 2015 at 2:48 PM, Ushani Balasooriya ush...@wso2.com wrote: Hi Sewmini, AFAIK, throttling count will start when the API is invoked. Therefore it should be a successful invocation. First it checks API level throttling limit and then Application level throttling limit and then it goes to resource level throttling check. Regards, Ushani On Wed, Apr 29, 2015 at 1:59 PM, Sewmini Jayaweera sewm...@wso2.com wrote: Hi, In API manager throttling functionality, How exactly the throttling tier exceed? 1. At the end of 20 successful invocations/hits or 2. When total number of hits (successful and faulty) exceeds 20? When I test this in both API manager 1.8.0 and 1.9.0 packs, count was taken using number of successful hits. Therefore I reported [1] documentation Jira. Please do verify and let me know if the functionality is wrong. [1]. https://wso2.org/jira/browse/DOCUMENTATION-1665 https://wso2.org/jira/browse/DOCUMENTATION-1665 Thanks Regards, Sewmini Sewmini Jayaweera *Software Engineer - QA Team* Mobile: +94 (0) 773 381 250 sewm...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Ushani Balasooriya* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; +94772636796 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Chathurika Erandi* Software Engineer, WSO2 Inc. *E-mail:* chathuri...@wso2.com *Mobile: *+94714 328 612 *Blog*: chathurikaerandi.blogspot.com -- *Ushani Balasooriya* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; +94772636796 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API manager throttling requirement clarification.
Thanks for the clarification, Ushani. I missed that it is the same API being invoked. On Thu, Apr 30, 2015 at 8:38 AM, Ushani Balasooriya ush...@wso2.com wrote: Hi Nirdesha, In this use case, the same API is being invoked but 2 different resources. E.g., GET, PUT So for the first resource (Bronze) it will count as 1 and next 2 requests for the same resource will exceed the resource level throttling. Next invocation for the 2nd resource will accept only 4 requests in the same minute since the whole API level throttling is silver (5) So the 5th request will not be successful due to the API level throttling (4+1) On Wed, Apr 29, 2015 at 10:06 PM, Nirdesha Munasinghe nirde...@wso2.com wrote: Hi Ushani, Why would the last request (5th one) fail to resource 2 please? Silver throttling tier allows 5 requests per minute, isn't it? Thanks, -Nirdesha On Wed, Apr 29, 2015 at 3:36 PM, Ushani Balasooriya ush...@wso2.com wrote: Hi Sewmini, I think it should work like, 1st 3 requests to Resource 1 = 1st request successful, Next 2 requests unsuccessful due to resource level throttling. Next 5 requests 2 Resource 2 = 1st 4 requests should be successful and last one should be unsucessful due to API level throttling. On Wed, Apr 29, 2015 at 3:23 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Sewmini In your case since you have sent 5 requests to the both of the resources these will be successful due to your API level throttling tier being 5. After that requests will be terminated. Please find the below documentation that will be a help to you https://docs.wso2.com/display/AM180/Key+Concepts#KeyConcepts-Throttlingtiers Thank You Erandi On Wed, Apr 29, 2015 at 3:14 PM, Sewmini Jayaweera sewm...@wso2.com wrote: Hi Ushani, When I say unsuccessful, what i meant was request fails due to resource level throttling exceeding. Say I have given API level throttling - silver (5) App level throttling - unlimited API resource 1 throttling - bronze (1) API resource 2 throttling - unlimited When I send first three requests to resource 1 and next 5 requests to resource 2, my last 3 request should fail due to API level throttling is it ? Thanks Regards, Sewmini Sewmini Jayaweera *Software Engineer - QA Team* Mobile: +94 (0) 773 381 250 sewm...@wso2.com On Wed, Apr 29, 2015 at 2:48 PM, Ushani Balasooriya ush...@wso2.com wrote: Hi Sewmini, AFAIK, throttling count will start when the API is invoked. Therefore it should be a successful invocation. First it checks API level throttling limit and then Application level throttling limit and then it goes to resource level throttling check. Regards, Ushani On Wed, Apr 29, 2015 at 1:59 PM, Sewmini Jayaweera sewm...@wso2.com wrote: Hi, In API manager throttling functionality, How exactly the throttling tier exceed? 1. At the end of 20 successful invocations/hits or 2. When total number of hits (successful and faulty) exceeds 20? When I test this in both API manager 1.8.0 and 1.9.0 packs, count was taken using number of successful hits. Therefore I reported [1] documentation Jira. Please do verify and let me know if the functionality is wrong. [1]. https://wso2.org/jira/browse/DOCUMENTATION-1665 https://wso2.org/jira/browse/DOCUMENTATION-1665 Thanks Regards, Sewmini Sewmini Jayaweera *Software Engineer - QA Team* Mobile: +94 (0) 773 381 250 sewm...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Ushani Balasooriya* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; +94772636796 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Chathurika Erandi* Software Engineer, WSO2 Inc. *E-mail:* chathuri...@wso2.com *Mobile: *+94714 328 612 *Blog*: chathurikaerandi.blogspot.com -- *Ushani Balasooriya* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; +94772636796 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- *Ushani Balasooriya* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; +94772636796 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API manager throttling requirement clarification.
Sewmini, will look into the JIRA. Thanks for the info. On Thu, Apr 30, 2015 at 11:16 AM, Nirdesha Munasinghe nirde...@wso2.com wrote: Thanks for the clarification, Ushani. I missed that it is the same API being invoked. On Thu, Apr 30, 2015 at 8:38 AM, Ushani Balasooriya ush...@wso2.com wrote: Hi Nirdesha, In this use case, the same API is being invoked but 2 different resources. E.g., GET, PUT So for the first resource (Bronze) it will count as 1 and next 2 requests for the same resource will exceed the resource level throttling. Next invocation for the 2nd resource will accept only 4 requests in the same minute since the whole API level throttling is silver (5) So the 5th request will not be successful due to the API level throttling (4+1) On Wed, Apr 29, 2015 at 10:06 PM, Nirdesha Munasinghe nirde...@wso2.com wrote: Hi Ushani, Why would the last request (5th one) fail to resource 2 please? Silver throttling tier allows 5 requests per minute, isn't it? Thanks, -Nirdesha On Wed, Apr 29, 2015 at 3:36 PM, Ushani Balasooriya ush...@wso2.com wrote: Hi Sewmini, I think it should work like, 1st 3 requests to Resource 1 = 1st request successful, Next 2 requests unsuccessful due to resource level throttling. Next 5 requests 2 Resource 2 = 1st 4 requests should be successful and last one should be unsucessful due to API level throttling. On Wed, Apr 29, 2015 at 3:23 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Sewmini In your case since you have sent 5 requests to the both of the resources these will be successful due to your API level throttling tier being 5. After that requests will be terminated. Please find the below documentation that will be a help to you https://docs.wso2.com/display/AM180/Key+Concepts#KeyConcepts-Throttlingtiers Thank You Erandi On Wed, Apr 29, 2015 at 3:14 PM, Sewmini Jayaweera sewm...@wso2.com wrote: Hi Ushani, When I say unsuccessful, what i meant was request fails due to resource level throttling exceeding. Say I have given API level throttling - silver (5) App level throttling - unlimited API resource 1 throttling - bronze (1) API resource 2 throttling - unlimited When I send first three requests to resource 1 and next 5 requests to resource 2, my last 3 request should fail due to API level throttling is it ? Thanks Regards, Sewmini Sewmini Jayaweera *Software Engineer - QA Team* Mobile: +94 (0) 773 381 250 sewm...@wso2.com On Wed, Apr 29, 2015 at 2:48 PM, Ushani Balasooriya ush...@wso2.com wrote: Hi Sewmini, AFAIK, throttling count will start when the API is invoked. Therefore it should be a successful invocation. First it checks API level throttling limit and then Application level throttling limit and then it goes to resource level throttling check. Regards, Ushani On Wed, Apr 29, 2015 at 1:59 PM, Sewmini Jayaweera sewm...@wso2.com wrote: Hi, In API manager throttling functionality, How exactly the throttling tier exceed? 1. At the end of 20 successful invocations/hits or 2. When total number of hits (successful and faulty) exceeds 20? When I test this in both API manager 1.8.0 and 1.9.0 packs, count was taken using number of successful hits. Therefore I reported [1] documentation Jira. Please do verify and let me know if the functionality is wrong. [1]. https://wso2.org/jira/browse/DOCUMENTATION-1665 https://wso2.org/jira/browse/DOCUMENTATION-1665 Thanks Regards, Sewmini Sewmini Jayaweera *Software Engineer - QA Team* Mobile: +94 (0) 773 381 250 sewm...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Ushani Balasooriya* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; +94772636796 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Chathurika Erandi* Software Engineer, WSO2 Inc. *E-mail:* chathuri...@wso2.com *Mobile: *+94714 328 612 *Blog*: chathurikaerandi.blogspot.com -- *Ushani Balasooriya* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; +94772636796 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- *Ushani Balasooriya* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; +94772636796 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Greg] What is the difference between overloaded findGenericArtifacts method in GenericArtifactManager
Copying Tania On Tue, Mar 17, 2015 at 2:17 PM, Isuruwan Herath isuru...@wso2.com wrote: On Tue, Mar 17, 2015 at 1:26 PM, Punnadi Gunarathna punn...@wso2.com wrote: Hi Isuruwan and Sagara, Thank you for the explanation. I can share the sample and descriptions. On Tue, Mar 17, 2015 at 1:06 PM, Sagara Gunathunga sag...@wso2.com wrote: On Tue, Mar 17, 2015 at 12:25 PM, Isuruwan Herath isuru...@wso2.com wrote: Hi Punnadi, Option 1 will only retrieve the artifacts according to the criteria of the given attribute key-value pair. Option 2 can do custom filtering as well and its implementation underneath will query all artifacts of the given type first (calling getAllGovernanceArtifacts() ) and then do the filtering. This could be the reason why you are getting the exception in second method. Shall we incorporate your description with 2 examples into API Java doc, in case if it's not already there ? +1 Sagara. It should go here [1]. [1] https://docs.wso2.com/display/Governance460/Configurable+Governance+Artifacts+with+API Thanks ! Thanks! Isuruwan On Tue, Mar 17, 2015 at 10:23 AM, Punnadi Gunarathna punn...@wso2.com wrote: Hi All, I am working with GenericArtifactManager and just wanted to know the difference between these two implementations: 1. Passing an attribute map to findGenericArtifacts method 2. Passing GenericArtifactFilter instance to findGenericArtifacts method Because in my case, when one of the saved artifact is corrupted, 1 would return correct artifact objects of rest of the artifacts saved in Greg where as 2 would throw an exception. -- Thanks and Regards, Punnadi Gunarathna Senior Software Engineer, WSO2, Inc.; http://wso2.com http://wso2 Blog: http://hi-my-world.blogspot.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 http://lalajisureshika.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Isuruwan Herath Technical Lead Contact: +94 776 273 296 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- Thanks and Regards, Punnadi Gunarathna Senior Software Engineer, WSO2, Inc.; http://wso2.com http://wso2 Blog: http://hi-my-world.blogspot.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 http://lalajisureshika.blogspot.com/ -- Isuruwan Herath Technical Lead Contact: +94 776 273 296 -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/d/optout. -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] App factory 2.1.0 samples
Hi AF team, I sent a mail last week saying that we do not plan to document AF samples in wiki from 2.1.0 onwards. The reason is because we already have a list of comprehensive tutorials, which cover the sample scenarios end-to-end. We want the users to try out the tutorials when they want to go through the use cases. I feel that a separate samples section is redundant and mostly repetitive. Samples are good for quick demonstrations as you don't have to set up all configurations from scratch. In that case, we will have detailed Readme files inside the product pack. Please get the content team involved when you are documenting the Readme files. Please let us know if you have any concerns about this approach. Thanks, -Nirdesha On Mon, Feb 2, 2015 at 11:52 AM, Danushka Fernando danush...@wso2.com wrote: Hi Shamin We haven't updated the samples for 2.1.0 yet. However there shouldn't be much changes to 2.0.0 since we are still on Carbon 4.2.0. So tryout 2.0.0 samples and if you find any issues report them. We will fix them. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 On Sun, Feb 1, 2015 at 10:07 PM, Mahesh Chinthaka mahe...@wso2.com wrote: Hi Shamin, Please try this link - https://docs.wso2.com/display/AF200/Samples On Mon, Feb 2, 2015 at 11:25 AM, Shamin Goonetileke sha...@wso2.com wrote: Hi, I have created jira [1] since samples are not available in app factory 2.1.0 documentation, sample are not available. According to the comment, provided by Nirdesha app factory team will add readme files for each sample in the pack. If so do we need to test the 2.1.0 samples and from which documentation should we refer for the test. [1] https://wso2.org/jira/browse/DOCUMENTATION-1451 Thank you, Shamin -- Intern - Software Engineer WSO2, Inc.http://wso2.com/ http://wso2.com/ Mobile :- +94 71 6290133 Email :- sha...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Mahesh Chinthaka Vidanagama* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 63 63 083 | Work: +94 112 145 345 Email: mahe...@wso2.com | Web: www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [API-M] Exception occurs while testing the Encrypting passwords process
Thanks for bringing this up. I verified with Lakmali and removed the content. Also added a note saying that we cannot encrypt the passwords of registry resources ATM. On Fri, Jan 16, 2015 at 5:21 PM, Lakmali Baminiwatta lakm...@wso2.com wrote: Hi Kala, On 16 January 2015 at 15:13, Kala Weerawardana k...@wso2.com wrote: Hi, I followed the Encrypting passwords documentation at [1] to test the scenario. While doing that I got the below mentioned exception. Exception in thread main org.wso2.ciphertool.CipherToolException: Element for secret alias 'APIManager.WorkFlowExtensions.ApplicationCreation.Password' can not be found in api-manager.xml file or You have entered invalid Xpath value at org.wso2.ciphertool.CipherTool.handleException(CipherTool.java:882) at org.wso2.ciphertool.CipherTool.writeTokenToConfigFile(CipherTool.java:501) at org.wso2.ciphertool.CipherTool.writeSecureVaultConfigTokens(CipherTool.java:395) at org.wso2.ciphertool.CipherTool.main(CipherTool.java:83) And looking in to it I figured out that this has a new implementation as it is moved on to registry. So this content should be removed from the documentation as well. [2] +1. Yes we need to. How is secure vault testing with workflows done now? Since the workflow configuration file is moved to registry, now we don't have a password encryption related functionality on that. Thanks, Lakmali And is there a documentation I can refer to test this flow? [1] - https://docs.wso2.com/display/AM170/Encrypting+Passwords [2] - https://wso2.org/jira/browse/DOCUMENTATION-1413 Thanks Regards, Kala https://docs.wso2.com/display/AM170/Encrypting+Passwords-- Kala C. Weerawardana *Software Engineer - QA Team* *WSO2 Inc. * Mobile : +94 (0) 716189886 +94 (0) 772877683 k...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM][DOC] API Manager 1.8.0 with Java Security Manager enabled
Hi Nilmini, I had a chat with Sanjeewa (copied) and did the following changes to the content that you produced: - Instructed the user to create the scripts on their own but gave the ones that are in Sanjeewa's blog as examples. Users can write their own scripts too. - According to Sanjeewa, we can use a single script to sign all JAR files. - Note that I added steps 2 and 3 to generate the key and then import it to the keystore. - In the last step, the user is instructed to change the sec.policy file and start the server. Changing the file is optional IMO, and the example is for the APIM only. Other writers might have to change it according to their products. I have copied this to the shared space and logged an All JIRA: https://wso2.org/jira/browse/DOCUMENTATION-1399. Please let me know if there are any discrepancies. Thanks, -Nirdesha On Wed, Dec 10, 2014 at 10:36 AM, Nilmini Perera nilm...@wso2.com wrote: Hi, Thanks for this information Sanjeewa. Looping Aruna, Sameera and Sanjaya. We previously documented the process of enabling Java Security Manager for Carbon products [1], which was based on Aruna's blog [2]. This is still under review because the scripts need to be reviewed. [Please refer mail: Official document for enabling security manager] However, based on the information given in both blogs, could we clarify the following: - Can we instruct the users to create the scripts on their own as mentioned by Sanjeewa?, or do we provide the necessary scripts as an attachment in the documentation? Which would be the recommended approach? - Also, is it necessary to sign the product pack and the patches separately (using two different scripts) as explained in [1]? [1] https://docs.wso2.com/display/Carbon430/Enable+Java+Security+Manager [2] http://java.dzone.com/articles/enable-java-security-manager Thanks and Best Regards, Nilmini On Tue, Dec 9, 2014 at 10:07 PM, Nirdesha Munasinghe nirde...@wso2.com wrote: +1. Thanks for the blog posts, Sanjeewa. I added a JIRA to track this task: https://wso2.org/jira/browse/DOCUMENTATION-1365. On Tue, Dec 9, 2014 at 8:26 PM, Sanjeewa Malalgoda sanje...@wso2.com wrote: We might need to add this[1] to product documentation. WDYT? [1] http://sanjeewamalalgoda.blogspot.com/2014/12/how-to-run-wso2-api-manager-180-with.html Thanks, sanjeewa. -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/ http://sanjeewamalalgoda.blogspot.com/ -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/d/optout. -- Nilmini Perera Senior Technical Writer WSO2 Inc. Mobile: 0094776722152 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Update Tutorial on How to write WSO2 carbon component
+1 for adding this to the Carbon docs. On Fri, Dec 19, 2014 at 11:15 AM, Praneesha Chandrasiri pranee...@wso2.com wrote: Thanks for bringing this up Chamin! @Nilmini - May be we can add this content to Carbon docs after Amal confirms. On Fri, Dec 19, 2014 at 1:34 AM, Amal Gunatilake am...@wso2.com wrote: Hi Chamin, Thanks for letting know. I had this in mind to update the configs but didn't get a chance to attend. I'll review and update the configurations. Thank you Best regards, *Amal Gunatilake* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware On Fri, Dec 19, 2014 at 1:14 AM, Chamin Nalinda cha...@wso2.com wrote: Hi all, I think the following tutorial[1] need a small update. The existing pom in related to Student Manager UI Component missing some dependencies, repositories and plugin management. Following are missing. dependency groupIdorg.apache.axis2.wso2/groupId artifactIdaxis2-client/artifactId version1.6.1.wso2v10/version /dependency repositories repository idwso2-nexus/id nameWSO2 internal Repository/name urlhttp://maven.wso2.org/nexus/content/groups/wso2-public/ /url releases enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyignore/checksumPolicy /releases /repository /repositories pluginManagement plugins !--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.-- plugin groupIdorg.eclipse.m2e/groupId artifactIdlifecycle-mapping/artifactId version1.0.0/version configuration lifecycleMappingMetadata pluginExecutions pluginExecution pluginExecutionFilter groupId org.codehaus.mojo /groupId artifactId build-helper-maven-plugin /artifactId versionRange [1.9.1,) /versionRange goals goaladd-source/goal /goals /pluginExecutionFilter action ignore/ignore /action /pluginExecution /pluginExecutions /lifecycleMappingMetadata /configuration /plugin /plugins /pluginManagement I think these need to add otherwise a build fail will occur following a warning.ma @Amal : like to know your opinion. @Praneesha : please to the update this if Amal agrees and relevant to documentation team. * [java] Retrieving document at 'src/main/resources/StudentManager.wsdl'. [java] Dec 18, 2014 6:46:33 PM org.apache.axis2.schema.SchemaCompiler compile [java] WARNING: No schemaLocation for import of http://data.mgt.student.carbon.wso2.org/xsd http://data.mgt.student.carbon.wso2.org/xsd; compilation may fail* Here I attached the pom file with necessary changes. [1] http://wso2.com/library/tutorials/2014/03/how-to-write-a-wso2-carbon-component/ -- *Chamin Nalinda* Intern - Engineering WSO2 Inc. http://www.wso2.com lean.enterprise.middleware Mobile: (+94) 77 241 66 04 Linkedin: https://www.linkedin.com/in/chaminnalinda Web: http://www.ckreativity.com Blog: http://techspiro.blogspot.com/ -- Thanks Best Regards, *Praneesha Chandrasiri* *Technical Writer* *WSO2 Inc. * *Mobile: +(94) 718156888 %2B%2894%29%20718156888* *E-mail: pranee...@wso2.com pranee...@wso2.com* -- You received this message because you are subscribed to the Google Groups WSO2 techcontent-group group. To unsubscribe from this group and stop receiving emails from it, send an email to techcontent-group+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/d/optout. -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fwd: [DEV][APIM]Adding a secondary JDBC userstore
. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/d/optout. -- Nilmini Perera Senior Technical Writer WSO2 Inc. Mobile: 0094776722152 -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/d/optout. -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM][DOC] API Manager 1.8.0 with Java Security Manager enabled
+1. Thanks for the blog posts, Sanjeewa. I added a JIRA to track this task: https://wso2.org/jira/browse/DOCUMENTATION-1365. On Tue, Dec 9, 2014 at 8:26 PM, Sanjeewa Malalgoda sanje...@wso2.com wrote: We might need to add this[1] to product documentation. WDYT? [1] http://sanjeewamalalgoda.blogspot.com/2014/12/how-to-run-wso2-api-manager-180-with.html Thanks, sanjeewa. -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/ http://sanjeewamalalgoda.blogspot.com/ -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM] Introduce a new API to add new subscriptions.
Hi Tanya, I fixed both 1.7.0 and 1.8.0 with the following info: - To add a subscription by application ID: action=*addSubscription* name=xxxversion=xxxprovider=xxxtier=xxx*applicationId*=xxx - To add a subscription by application name: action=*addAPISubscription* name=xxxversion=xxxprovider=xxxtier=xxx*applicationName*=xxx Will be great if you can verify if this is correct. Thanks, -Nirdesha On Tue, Nov 18, 2014 at 9:30 AM, Jackie Wheeler jac...@wso2.com wrote: Nirdesha, can you take a look? Thanks, Jackie On Mon, Nov 17, 2014 at 1:17 AM, Roshan Wijesena ros...@wso2.com wrote: Thanks Tanya/Sanjeewa. It would be great if we can get documented this somewhere in our docs? Regards Roshan. On Mon, Nov 17, 2014 at 2:34 PM, Tanya Madurapperuma ta...@wso2.com wrote: subscription-add.jag [1] has else if (action == addAPISubscription request.getMethod() == 'POST') which takes application name to make a subscription. It calls the addAPISubscription method at [2] which calls the jsFunction_addAPISubscription method of api store hostobject [3] Hence no need to write a new api. [1] https://github.com/wso2-dev/carbon-apimgt/blob/master/components/apimgt/api-store-web/src/site/blocks/subscription/subscription-add/ajax/subscription-add.jag [2] https://github.com/wso2-dev/carbon-apimgt/blob/master/components/apimgt/api-store-web/src/modules/subscription/add.jag [3] https://github.com/wso2-dev/carbon-apimgt/blob/master/components/apimgt/org.wso2.carbon.apimgt.hostobjects/src/main/java/org/wso2/carbon/apimgt/hostobjects/APIStoreHostObject.java Thanks, Tanya On Mon, Nov 17, 2014 at 2:17 PM, Sanjeewa Malalgoda sanje...@wso2.com wrote: It seems you need to expose API to pass *Application name* and user name here. Previously mentioned action require *application ID*. So we may be able to keep current API as it is and add new action as you mentioned. So users who use existing rest API do not have to change their application code. Thanks, sanjeewa. On Mon, Nov 17, 2014 at 1:54 PM, Sanjeewa Malalgoda sanje...@wso2.com wrote: On Mon, Nov 17, 2014 at 1:36 PM, Tanya Madurapperuma ta...@wso2.com wrote: Isn''t the *addAPISubscription* action in subscription-add.jag does the same? +1. Yes we may use same Thanks, sanjeewa. Thanks, Tanya On Mon, Nov 17, 2014 at 12:32 PM, Roshan Wijesena ros...@wso2.com wrote: Hi Devs, Current existing addSubscription API [1] accept Application Id as a parameter in POST request. It seems, use an internal attribute as an API parameter would not be a good approach. Further, I would like to propose a new API, which will take application name and user name as parameters instead of application ID. Sample curl request for the proposed API will be as below. curl -X POST -b cookies http://localhost:9763/store/site/blocks/subscription/subscription-add/ajax/subscription-add.jag -d 'action=addSubscriptionByNamename=API1version=v1provider=admintier=GoldapplicationName=PizzaShopuserName=admin' WDYT? [1] https://docs.wso2.com/display/AM170/Store+APIs. Regards Roshan. -- Roshan Wijesena. Senior Software Engineer-WSO2 Inc. Mobile: *+94752126789* Email: ros...@wso2.com *WSO2, Inc. :** wso2.com http://wso2.com/* lean.enterprise.middleware. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Tanya Madurapperuma Software Engineer, WSO2 Inc. : wso2.com Mobile : +94718184439 Blog : http://tanyamadurapperuma.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/ http://sanjeewamalalgoda.blogspot.com/ -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/ http://sanjeewamalalgoda.blogspot.com/ -- Tanya Madurapperuma Software Engineer, WSO2 Inc. : wso2.com Mobile : +94718184439 Blog : http://tanyamadurapperuma.blogspot.com -- Roshan Wijesena. Senior Software Engineer-WSO2 Inc. Mobile: *+94752126789* Email: ros...@wso2.com *WSO2, Inc. :** wso2.com http://wso2.com/* lean.enterprise.middleware. -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/d/optout. -- *Jackie Wheeler* VP, Technical Content WSO2, Inc. Mobile: +1 510 725-2876 http://wso2.com/ -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http
Re: [Dev] [APIM] Introduce a new API to add new subscriptions.
Thanks, Tanya! I will verify with the APIM team and add it to 1.6.0 as well. On Tue, Nov 18, 2014 at 5:24 PM, Tanya Madurapperuma ta...@wso2.com wrote: On Tue, Nov 18, 2014 at 5:20 PM, Tanya Madurapperuma ta...@wso2.com wrote: Verified in 1.6 and 1.7. Sorry I mean 1.8 not 1.6 But In the code base of 1.6 also this api is there. Think we need to add in 1.6 docs as well. Thanks, Tanya Thanks, Tanya On Tue, Nov 18, 2014 at 5:14 PM, Nirdesha Munasinghe nirde...@wso2.com wrote: Hi Tanya, I fixed both 1.7.0 and 1.8.0 with the following info: - To add a subscription by application ID: action=*addSubscription* name=xxxversion=xxxprovider=xxxtier=xxx*applicationId*=xxx - To add a subscription by application name: action= *addAPISubscription*name=xxxversion=xxxprovider=xxxtier=xxx *applicationName*=xxx Will be great if you can verify if this is correct. Thanks, -Nirdesha On Tue, Nov 18, 2014 at 9:30 AM, Jackie Wheeler jac...@wso2.com wrote: Nirdesha, can you take a look? Thanks, Jackie On Mon, Nov 17, 2014 at 1:17 AM, Roshan Wijesena ros...@wso2.com wrote: Thanks Tanya/Sanjeewa. It would be great if we can get documented this somewhere in our docs? Regards Roshan. On Mon, Nov 17, 2014 at 2:34 PM, Tanya Madurapperuma ta...@wso2.com wrote: subscription-add.jag [1] has else if (action == addAPISubscription request.getMethod() == 'POST') which takes application name to make a subscription. It calls the addAPISubscription method at [2] which calls the jsFunction_addAPISubscription method of api store hostobject [3] Hence no need to write a new api. [1] https://github.com/wso2-dev/carbon-apimgt/blob/master/components/apimgt/api-store-web/src/site/blocks/subscription/subscription-add/ajax/subscription-add.jag [2] https://github.com/wso2-dev/carbon-apimgt/blob/master/components/apimgt/api-store-web/src/modules/subscription/add.jag [3] https://github.com/wso2-dev/carbon-apimgt/blob/master/components/apimgt/org.wso2.carbon.apimgt.hostobjects/src/main/java/org/wso2/carbon/apimgt/hostobjects/APIStoreHostObject.java Thanks, Tanya On Mon, Nov 17, 2014 at 2:17 PM, Sanjeewa Malalgoda sanje...@wso2.com wrote: It seems you need to expose API to pass *Application name* and user name here. Previously mentioned action require *application ID*. So we may be able to keep current API as it is and add new action as you mentioned. So users who use existing rest API do not have to change their application code. Thanks, sanjeewa. On Mon, Nov 17, 2014 at 1:54 PM, Sanjeewa Malalgoda sanje...@wso2.com wrote: On Mon, Nov 17, 2014 at 1:36 PM, Tanya Madurapperuma ta...@wso2.com wrote: Isn''t the *addAPISubscription* action in subscription-add.jag does the same? +1. Yes we may use same Thanks, sanjeewa. Thanks, Tanya On Mon, Nov 17, 2014 at 12:32 PM, Roshan Wijesena ros...@wso2.com wrote: Hi Devs, Current existing addSubscription API [1] accept Application Id as a parameter in POST request. It seems, use an internal attribute as an API parameter would not be a good approach. Further, I would like to propose a new API, which will take application name and user name as parameters instead of application ID. Sample curl request for the proposed API will be as below. curl -X POST -b cookies http://localhost:9763/store/site/blocks/subscription/subscription-add/ajax/subscription-add.jag -d 'action=addSubscriptionByNamename=API1version=v1provider=admintier=GoldapplicationName=PizzaShopuserName=admin' WDYT? [1] https://docs.wso2.com/display/AM170/Store+APIs. Regards Roshan. -- Roshan Wijesena. Senior Software Engineer-WSO2 Inc. Mobile: *+94752126789* Email: ros...@wso2.com *WSO2, Inc. :** wso2.com http://wso2.com/* lean.enterprise.middleware. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Tanya Madurapperuma Software Engineer, WSO2 Inc. : wso2.com Mobile : +94718184439 Blog : http://tanyamadurapperuma.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/ http://sanjeewamalalgoda.blogspot.com/ -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/ http://sanjeewamalalgoda.blogspot.com/ -- Tanya Madurapperuma Software Engineer, WSO2 Inc. : wso2.com Mobile : +94718184439 Blog : http://tanyamadurapperuma.blogspot.com -- Roshan Wijesena. Senior Software Engineer-WSO2 Inc. Mobile: *+94752126789* Email: ros...@wso2.com *WSO2, Inc. :** wso2.com http://wso2.com/* lean.enterprise.middleware. -- You received this message because you are subscribed
Re: [Dev] Invalid content in APIM documentation
Will look into this. Thanks, -Nirdesha On Sat, Oct 25, 2014 at 7:04 AM, Shamika Ariyawansa sham...@wso2.com wrote: Hi all, Writing custom authenticate handlers as described in [1] seems to be no longer valid. With APIM 1.7.0 on-wards we have to introduce custom authentication handlers by editing the template file located in AM_HOME/repository/resources/api_templates/velocity_template.xml. However when doing that we have to make sure that it skips the default APIAuthenticationHandler too. Please see the following modified segment in that file which does this, handlers xmlns=http://ws.apache.org/ns/synapse; handler class=org.wso2.carbon.apimgt.custom.authentication.handler.CustomAPIAuthenticationHandler / #foreach($handler in $handlers) #if(!($handler.className == org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler)) handler xmlns=http://ws.apache.org/ns/synapse; class=$handler.className #if($handler.hasProperties()) #set ($map = $handler.getProperties() ) #foreach($property in $map.entrySet()) property name=$!property.key value=$!property.value/ #end #end /handler #end #end /handlers We have to do this as the handlers are passed from the code itself. Also please note that the package name of the custom implementation in [1] should be changed as it will conflict with org.wso2.carbon.apimgt.gateway bundle which will lead to some class loading issues. Please correct me if am wrong on this. [1] https://docs.wso2.com/display/AM170/Writing+Custom+Authentication+Handlers Regards, -- Shamika Ariyawansa Senior Software Engineer WSO2, Inc.; http://wso2.com LK - +94 7639629 Ext 5999 US - +1 408 754 7388 Ext 51732 Mob:+ 94 772929486 *twitter: **https://twitter.com/Amila_Shamika* https://twitter.com/Amila_Shamika *linked-in: *http://www.linkedin.com/pub/dir/Shamika/Ariyawansa *Lean . Enterprise . Middleware* -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Invalid content in APIM documentation
JIRA: https://wso2.org/jira/browse/DOCUMENTATION-1209 On Mon, Oct 27, 2014 at 9:22 AM, Nirdesha Munasinghe nirde...@wso2.com wrote: Will look into this. Thanks, -Nirdesha On Sat, Oct 25, 2014 at 7:04 AM, Shamika Ariyawansa sham...@wso2.com wrote: Hi all, Writing custom authenticate handlers as described in [1] seems to be no longer valid. With APIM 1.7.0 on-wards we have to introduce custom authentication handlers by editing the template file located in AM_HOME/repository/resources/api_templates/velocity_template.xml. However when doing that we have to make sure that it skips the default APIAuthenticationHandler too. Please see the following modified segment in that file which does this, handlers xmlns=http://ws.apache.org/ns/synapse; handler class=org.wso2.carbon.apimgt.custom.authentication.handler.CustomAPIAuthenticationHandler / #foreach($handler in $handlers) #if(!($handler.className == org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler)) handler xmlns=http://ws.apache.org/ns/synapse; class=$handler.className #if($handler.hasProperties()) #set ($map = $handler.getProperties() ) #foreach($property in $map.entrySet()) property name=$!property.key value=$!property.value/ #end #end /handler #end #end /handlers We have to do this as the handlers are passed from the code itself. Also please note that the package name of the custom implementation in [1] should be changed as it will conflict with org.wso2.carbon.apimgt.gateway bundle which will lead to some class loading issues. Please correct me if am wrong on this. [1] https://docs.wso2.com/display/AM170/Writing+Custom+Authentication+Handlers Regards, -- Shamika Ariyawansa Senior Software Engineer WSO2, Inc.; http://wso2.com LK - +94 7639629 Ext 5999 US - +1 408 754 7388 Ext 51732 Mob:+ 94 772929486 *twitter: **https://twitter.com/Amila_Shamika* https://twitter.com/Amila_Shamika *linked-in: *http://www.linkedin.com/pub/dir/Shamika/Ariyawansa *Lean . Enterprise . Middleware* -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM][Publisher REST API] copy API rest call should be updated in the docs
Fixed. Thanks for reporting! On Tue, Sep 9, 2014 at 6:30 PM, Waruna Perera waru...@wso2.com wrote: Hi, I tried to invoke API manager REST publisher API via in a test case to copy API to new version and failed[1]. There is a additional parameter added in 1.2.2 code path to check whether the newly created version is default version or not. So doc should be updated as follows. curl -X POST -b cookies http://localhost:9763/publisher/site/blocks/overview/ajax/overview.jag -d action=createNewAPIprovider=user1apiName=API1version=1.0.0newVersion=2.0.0 *isDefaultVersion=default_version*” [1] https://docs.wso2.com/display/AM170/Publisher+APIs#PublisherAPIs-CopyanAPI -- Waruna Perera Senior Software Engineer - Test Automation Mobile: +94 77 3867037 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/d/optout. -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Our documentation on changing the default keystore is not enough
Hi Samuel, Please look into this query. Once you are done, let the other writers know so that they can add it into their docs as well. Thanks, -Nirdesha On Thu, Sep 11, 2014 at 12:05 AM, Amila Maha Arachchi ami...@wso2.com wrote: Hi all, $Subject. I couldn't find a proper document. I only found this https://docs.wso2.com/display/MB220/Changing+Default+Keystores If there is a proper doc, please point me. Otherwise, this needs to be in the admin tasks of each product. I can provide the necessary instructions if needed. Regards, Amila. -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [App Factory] - Delete application created in a tenant
Will add this to the docs. Thanks, -Nirdesha On Thu, Aug 21, 2014 at 11:25 AM, Godwin Amila Shrimal god...@wso2.com wrote: Hi Manisha, Thanks, I checked in the wso2.docs in earlier. This solve our problem. On Thu, Aug 21, 2014 at 10:42 AM, Manisha Gayathri mani...@wso2.com wrote: Hi Godwin, Delete Application too is already implemented. *ApplicationManagementService.deleteApplication *is available. On Thu, Aug 21, 2014 at 10:24 AM, Udara Liyanage ud...@wso2.com wrote: Hi Godwin, May be DELETE method is not yet implemented. @Danuska can you confirm. On Thu, Aug 21, 2014 at 10:19 AM, Godwin Amila Shrimal god...@wso2.com wrote: Hi Udara, Thanks, as you pointed, there is a REST API to the the applications ( getApplicationsOfUser https://docs.wso2.com/plugins/servlet/mobile#RESTAPIs-getApplicationsOfUser), But I did't see any delete application operation there. How can we delete them ? On Thu, Aug 21, 2014 at 1:06 AM, Udara Liyanage ud...@wso2.com wrote: Hi, You can call AppFac REST API for this. Please refer to [1] [1] https://docs.wso2.com/plugins/servlet/mobile#RESTAPIs-getApplicationsOfUser Touched, not typed. Erroneous words are a feature, not a typo. On Aug 20, 2014 7:40 PM, Godwin Amila Shrimal god...@wso2.com wrote: Hi, How can we check the already created application for a specific tenant and delete them in App Factory. Is there any admin service to perform this ? Thanks Godwin -- *Godwin Amila Shrimal* Senior Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: *+94772264165* linkedin: *http://lnkd.in/KUum6D http://lnkd.in/KUum6D* twitter: https://twitter.com/godwinamila ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Godwin Amila Shrimal* Senior Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: *+94772264165* linkedin: *http://lnkd.in/KUum6D http://lnkd.in/KUum6D* twitter: https://twitter.com/godwinamila -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- ~Regards *Manisha Eleperuma* Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware *blog: http://manisha-eleperuma.blogspot.com/ http://manisha-eleperuma.blogspot.com/* *mobile: +94 71 8279777 %2B94%2071%208279777* -- *Godwin Amila Shrimal* Senior Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: *+94772264165* linkedin: *http://lnkd.in/KUum6D http://lnkd.in/KUum6D* twitter: https://twitter.com/godwinamila ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Remove Running the management console in ELB docs
Copying Samuel... On Mon, Aug 4, 2014 at 7:32 PM, Amila Maha Arachchi ami...@wso2.com wrote: ELB has no use from the management console (at least at the moment). Therefore, shouldn't we removing the section on accessing the management console of the ELB. See https://docs.wso2.com/display/ELB211/Running+the+Product Users read this and try to access the management console. But some required files seems to be missing. See http://stackoverflow.com/questions/25094112/authenticators-xml-is-missing-in-wso2-elb So, shall we $Subject? -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ETA for on-premise App Factory
Done. 2.0.1 docs are public. Thanks, -Nirdesha On Wed, Jul 23, 2014 at 5:17 PM, Dimuthu Leelarathne dimut...@wso2.com wrote: Hi, If we have the docs ready, then it is a matter of opening it up. If we have continuous deployment I believe our doc strategy should change to reflect that? @Nirdesha - Could we just make 2.0.1 docs public? So that as we deploy things into cloud people can access the docs? thanks, dimuthu On Wed, Jul 23, 2014 at 4:53 PM, Dmitry Sotnikov dmi...@wso2.com wrote: Janaka, This comment by Nirdesha reads to me like a statement that although the scripts and docs will be created, it will not be until 2.0.1 release that they will be made public - so potentially much later than July 29. Is that so? As we are not going to give scripts with AF 2.0.0, I will remove that section from the 2.0.0 docs. We will be adding the content to 2.0.1 docs. Dmitry On Wed, Jul 23, 2014 at 3:11 PM, Janaka Ranabahu jan...@wso2.com wrote: Hi, Our plan is to complete the docs by 29 July. Samith will be working on these with me. Thanks, Janaka On Wed, Jul 23, 2014 at 11:42 AM, Nirdesha Munasinghe nirde...@wso2.com wrote: Janaka will be adding the draft steps to wiki or in a Google doc. Please let me know once you are done so that I can complete this page. As we are not going to give scripts with AF 2.0.0, I will remove that section from the 2.0.0 docs. We will be adding the content to 2.0.1 docs. Thanks, -Nirdesha On Wed, Jul 23, 2014 at 11:08 AM, Dmitry Sotnikov dmi...@wso2.com wrote: Quick check on the status of this: - The scripts have been released, right? - What is the ETA for documentation on using them to install AF? Dmitry On Sat, Jul 5, 2014 at 4:10 PM, Dmitry Sotnikov dmi...@wso2.com wrote: Thanks Harsha! I will let the customer know it is coming within a couple of weeks or so. Please let me know when everything is ready. Dmitry On Jul 4, 2014 7:01 PM, Harsha Thirimanna hars...@wso2.com wrote: Hi Dimitry, We are in final stage of this. After finish the appfactory puppet scripts we hope to run it with privatepaas puppet and do the complete test. We can finish it on next friday (11th July). Thanks On Jul 4, 2014 5:20 PM, Dmitry Sotnikov dmi...@wso2.com wrote: An App Cloud user just asked me when the on-premise App Factory 2 support coming. He wants to install it but docs are saying that this is not possible: https://docs.wso2.com/display/AF200/Installing+On-Premise Thanks! Dmitry ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware http://wso2.com/events/ -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- *Janaka Ranabahu* Senior Software Engineer; WSO2 Inc.; http://wso2.com * E-mail: jan...@wso2.com http://wso2.com**M: **+94 718370861 %2B94%20718370861* Lean . Enterprise . Middleware -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware http://wso2.com/events/ -- Dimuthu Leelarathne Architect Product Lead of App Factory WSO2, Inc. (http://wso2.com) email: dimut...@wso2.com Mobile : 0773661935 Lean . Enterprise . Middleware -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Concern in configuring IS as key manager doc
Samuel, please note On Fri, Jun 27, 2014 at 1:47 PM, Lahiru Sandaruwan lahi...@wso2.com wrote: On Fri, Jun 27, 2014 at 1:44 PM, Nirmal Fernando nir...@wso2.com wrote: Hi Lahiru, In latest APIM's mysql script, IS DB related tables are there by default. Hence, you don't need to run both scripts. I'm working with API Manager 1.6. On Fri, Jun 27, 2014 at 1:37 PM, Lahiru Sandaruwan lahi...@wso2.com wrote: Yes, when i run /identity/mysql.sql after apimgt/mysql.sql there were two duplicates. Couldn't record the log :( On Fri, Jun 27, 2014 at 12:02 PM, Sanjeewa Malalgoda sanje...@wso2.com wrote: 10th step is about database creation. Did get duplicates while doing that? Thanks, sanjeewa. On Thu, Jun 26, 2014 at 7:44 PM, Lahiru Sandaruwan lahi...@wso2.com wrote: Hi, At [1], while following 10th step of IS configuration, it complains about two duplication. We can manually remove them and fix. Is my process wrong or need to go to docs? Thanks. [1] https://docs.wso2.org/display/CLUSTER420/Configuring+WSO2+Identity+Server+as+the+Key+Manager -- -- Lahiru Sandaruwan Committer and PMC member, Apache Stratos, Senior Software Engineer, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com cell: (+94) 773 325 954 blog: http://lahiruwrites.blogspot.com/ twitter: http://twitter.com/lahirus linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/ http://sanjeewamalalgoda.blogspot.com/ -- -- Lahiru Sandaruwan Committer and PMC member, Apache Stratos, Senior Software Engineer, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com cell: (+94) 773 325 954 blog: http://lahiruwrites.blogspot.com/ twitter: http://twitter.com/lahirus linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ -- -- Lahiru Sandaruwan Committer and PMC member, Apache Stratos, Senior Software Engineer, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com cell: (+94) 773 325 954 blog: http://lahiruwrites.blogspot.com/ twitter: http://twitter.com/lahirus linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/d/optout. -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Gateway cache clearing for regenerated and revoked tokens
Thanks, Sanjeewa. I added this infor in [1].
Samuel, if relevant, please point to this section from the clustering guide
too. This is about how to clear the API Gateway cache and the steps
actually explain how to configure this in a clustered APIM setup.
[1] https://docs.wso2.org/display/AM170/Configuring+Caching#Claring API
Gateway cache
On Fri, May 23, 2014 at 1:19 AM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
On Mon, May 19, 2014 at 11:57 AM, Nirdesha Munasinghe
nirde...@wso2.comwrote:
Thanks for reporting. Doc JIRA created:
https://wso2.org/jira/browse/DOCUMENTATION-842.
On Sat, May 17, 2014 at 8:49 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
Hi All,
We found following issues in gateway cache when we regenerate
application tokens from API store user interface(or calling revoke API).
01. If we generate new application access token from ui old tokens
remain as active in gateway cache.
02. If we use revoke API deployed in gateway it will clear only super
tenants cache.
hi Nirdesha,
Please note following change in this configurations.
To address these issues recently we introduced new parameter named
RevokeAPIURL. In distributed deployment we need to configure this parameter
in API key manager node. Then it will call API pointed by RevokeAPIURL
parameter. RevokeAPIURL parameter should be pointed to revoke API deployed
API gateway nodes. If it is gateway cluster we can point to one node. So
from this release on wards all revoke requests will route to oauth service
through revoke API deployed in API manager. When revoke response route
through revoke API cache clear handler will invoke. Then it will extract
relevant information form transport headers and clear associated cache
entries. In distributed deployment we should configure followings.
01. In key manager node, point gateway API revoke end point as follows.
!-- This the API URL for revoke API. When we revoke tokens revoke
requests should go through this
API deployed in API gateway. Then it will do cache
invalidations related to revoked tokens.
In distributed deployment we should configure this property in key
manager node by pointing
gateway https url. Also please note that we should point gateway
revoke service to key manager--
RevokeAPIURLhttps://
${carbon.local.ip}:${https.nio.port}/revoke/RevokeAPIURL
02. In API gateway revoke API should be pointed to oauth application
deployed in key manager node.
api name=_WSO2AMRevokeAPI_ context=/revoke
resource methods=POST url-mapping=/*
faultSequence=_token_fault_
inSequence
send
endpoint
address uri=
https://keymgt.wso2.com:9445/oauth2/revoke/
/endpoint
/send
/inSequence
outSequence
send/
/outSequence
/resource
handlers
handler
class=org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerCacheExtensionHandler/
/handlers
/api
We need to add this to our product documents as well.
Thanks,
sanjeewa.
--
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779
http://sanjeewamalalgoda.blogspot.com/blog
:http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/
--
Thanks,
Nirdesha Munasinghe,
WSO2 Inc.
Web:http://wso2.com
Mobile: +94 776321920
--
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779
http://sanjeewamalalgoda.blogspot.com/blog
:http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/
--
Thanks,
Nirdesha Munasinghe,
WSO2 Inc.
Web:http://wso2.com
Mobile: +94 776321920
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Gateway cache clearing for regenerated and revoked tokens
Fixed a typo in the title:
https://docs.wso2.org/display/AM170/Configuring+Caching#Clearing the API
Gateway cache
On Mon, May 26, 2014 at 2:49 PM, Nirdesha Munasinghe nirde...@wso2.comwrote:
Thanks, Sanjeewa. I added this infor in [1].
Samuel, if relevant, please point to this section from the clustering
guide too. This is about how to clear the API Gateway cache and the steps
actually explain how to configure this in a clustered APIM setup.
[1] https://docs.wso2.org/display/AM170/Configuring+Caching#Claring API
Gateway cache
On Fri, May 23, 2014 at 1:19 AM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
On Mon, May 19, 2014 at 11:57 AM, Nirdesha Munasinghe
nirde...@wso2.comwrote:
Thanks for reporting. Doc JIRA created:
https://wso2.org/jira/browse/DOCUMENTATION-842.
On Sat, May 17, 2014 at 8:49 PM, Sanjeewa Malalgoda
sanje...@wso2.comwrote:
Hi All,
We found following issues in gateway cache when we regenerate
application tokens from API store user interface(or calling revoke API).
01. If we generate new application access token from ui old tokens
remain as active in gateway cache.
02. If we use revoke API deployed in gateway it will clear only super
tenants cache.
hi Nirdesha,
Please note following change in this configurations.
To address these issues recently we introduced new parameter named
RevokeAPIURL. In distributed deployment we need to configure this parameter
in API key manager node. Then it will call API pointed by RevokeAPIURL
parameter. RevokeAPIURL parameter should be pointed to revoke API deployed
API gateway nodes. If it is gateway cluster we can point to one node. So
from this release on wards all revoke requests will route to oauth service
through revoke API deployed in API manager. When revoke response route
through revoke API cache clear handler will invoke. Then it will extract
relevant information form transport headers and clear associated cache
entries. In distributed deployment we should configure followings.
01. In key manager node, point gateway API revoke end point as follows.
!-- This the API URL for revoke API. When we revoke tokens revoke
requests should go through this
API deployed in API gateway. Then it will do cache
invalidations related to revoked tokens.
In distributed deployment we should configure this property in key
manager node by pointing
gateway https url. Also please note that we should point gateway
revoke service to key manager--
RevokeAPIURLhttps://
${carbon.local.ip}:${https.nio.port}/revoke/RevokeAPIURL
02. In API gateway revoke API should be pointed to oauth application
deployed in key manager node.
api name=_WSO2AMRevokeAPI_ context=/revoke
resource methods=POST url-mapping=/*
faultSequence=_token_fault_
inSequence
send
endpoint
address uri=
https://keymgt.wso2.com:9445/oauth2/revoke/
/endpoint
/send
/inSequence
outSequence
send/
/outSequence
/resource
handlers
handler
class=org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerCacheExtensionHandler/
/handlers
/api
We need to add this to our product documents as well.
Thanks,
sanjeewa.
--
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779
http://sanjeewamalalgoda.blogspot.com/blog
:http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/
--
Thanks,
Nirdesha Munasinghe,
WSO2 Inc.
Web:http://wso2.com
Mobile: +94 776321920
--
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779
http://sanjeewamalalgoda.blogspot.com/blog
:http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/
--
Thanks,
Nirdesha Munasinghe,
WSO2 Inc.
Web:http://wso2.com
Mobile: +94 776321920
--
Thanks,
Nirdesha Munasinghe,
WSO2 Inc.
Web:http://wso2.com
Mobile: +94 776321920
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] What should be the correct behavior in publishing services from G-Reg to APIM
Small clarification please. So the expected behavior is that the API will be created in the API Publisher and will be in CREATED state only. It will not be in the PUBLISHED state nor is it visible in the API Store. Am I right? On Tue, May 20, 2014 at 6:39 PM, Chathurika Mahaarachchi chathur...@wso2.com wrote: Thanks for the update Ajith. Adding Nirdesha : This should be update in documents https://docs.wso2.org/display/AM170/Integrating+with+WSO2+Governance+Registry+Services Regards, Chathurika On Tue, May 20, 2014 at 6:02 PM, Ajith Vitharana aji...@wso2.com wrote: On Tue, May 20, 2014 at 5:39 PM, Chathurika Mahaarachchi chathur...@wso2.com wrote: Hi, I tried “Integrating APIM with WSO2 Governance Registry Services” scenario with G-Reg 4.6.0 and API Manager 1.7.0 18th May pack . Configurations are added accordingly as mentioned in the docs. “ https://docs.wso2.org/display/AM160/Integrating+with+WSO2+Governance+Registry+Services” and I have added the following patch to the G-Reg https://svn.wso2.com/wso2/custom/projects/projects/carbon/turing/patches/patch0155 . Once I publish a service to APIM using G-reg , The service is published to to the APIM – Publisher page in created state. But according to the document is says it should publish in APIM Store. What should be the correct expected behavior and status in this scenario? It should be the publisher state, because the informations are available in G-Reg side is not enough to publish as a complete API to store. Thanks. Ajith. Thanks and Regards, Chathurika -- *Chathurika Mahaarachchi* Software Engineer, QA. WSO2 Inc.: http://wso2.com/ lean.enterprise.middleware Mobile: +94718223950 -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- *Chathurika Mahaarachchi* Software Engineer, QA. WSO2 Inc.: http://wso2.com/ lean.enterprise.middleware Mobile: +94718223950 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] What should be the correct behavior in publishing services from G-Reg to APIM
Hi Chathurika, Thanks for the clarification. I updated the page accordingly. Regards, -Nirdesha On Mon, May 26, 2014 at 8:13 PM, Chathurika Mahaarachchi chathur...@wso2.com wrote: Hi Nirdesha, Yes. The Created API should display in APIM Publisher page in CREATED state only, and not visible in Store. Once you publish the API , it is visible in Store. Thanks, Chathurika On Mon, May 26, 2014 at 5:09 PM, Nirdesha Munasinghe nirde...@wso2.comwrote: Small clarification please. So the expected behavior is that the API will be created in the API Publisher and will be in CREATED state only. It will not be in the PUBLISHED state nor is it visible in the API Store. Am I right? On Tue, May 20, 2014 at 6:39 PM, Chathurika Mahaarachchi chathur...@wso2.com wrote: Thanks for the update Ajith. Adding Nirdesha : This should be update in documents https://docs.wso2.org/display/AM170/Integrating+with+WSO2+Governance+Registry+Services Regards, Chathurika On Tue, May 20, 2014 at 6:02 PM, Ajith Vitharana aji...@wso2.comwrote: On Tue, May 20, 2014 at 5:39 PM, Chathurika Mahaarachchi chathur...@wso2.com wrote: Hi, I tried “Integrating APIM with WSO2 Governance Registry Services” scenario with G-Reg 4.6.0 and API Manager 1.7.0 18th May pack . Configurations are added accordingly as mentioned in the docs. “ https://docs.wso2.org/display/AM160/Integrating+with+WSO2+Governance+Registry+Services” and I have added the following patch to the G-Reg https://svn.wso2.com/wso2/custom/projects/projects/carbon/turing/patches/patch0155 . Once I publish a service to APIM using G-reg , The service is published to to the APIM – Publisher page in created state. But according to the document is says it should publish in APIM Store. What should be the correct expected behavior and status in this scenario? It should be the publisher state, because the informations are available in G-Reg side is not enough to publish as a complete API to store. Thanks. Ajith. Thanks and Regards, Chathurika -- *Chathurika Mahaarachchi* Software Engineer, QA. WSO2 Inc.: http://wso2.com/ lean.enterprise.middleware Mobile: +94718223950 -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- *Chathurika Mahaarachchi* Software Engineer, QA. WSO2 Inc.: http://wso2.com/ lean.enterprise.middleware Mobile: +94718223950 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- *Chathurika Mahaarachchi* Software Engineer, QA. WSO2 Inc.: http://wso2.com/ lean.enterprise.middleware Mobile: +94718223950 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Gateway cache clearing for regenerated and revoked tokens
Thanks for reporting. Doc JIRA created:
https://wso2.org/jira/browse/DOCUMENTATION-842.
On Sat, May 17, 2014 at 8:49 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
Hi All,
We found following issues in gateway cache when we regenerate application
tokens from API store user interface(or calling revoke API).
01. If we generate new application access token from ui old tokens remain
as active in gateway cache.
02. If we use revoke API deployed in gateway it will clear only super
tenants cache.
To address these issues recently we introduced new parameter named
RevokeAPIURL. In distributed deployment we need to configure this parameter
in API store node. Then it will call API pointed by RevokeAPIURL parameter.
RevokeAPIURL parameter should be pointed to revoke API deployed API gateway
nodes. If it is gateway cluster we can point to one node. So from this
release on wards all revoke requests will route to oauth service through
revoke API deployed in API manager. When revoke response route through
revoke API cache clear handler will invoke. Then it will extract relevant
information form transport headers and clear associated cache entries. In
distributed deployment we should configure followings.
01. In key manager node, point gateway API revoke end point as follows.
!-- This the API URL for revoke API. When we revoke tokens revoke
requests should go through this
API deployed in API gateway. Then it will do cache
invalidations related to revoked tokens.
In distributed deployment we should configure this property in key
manager node by pointing
gateway https url. Also please note that we should point gateway
revoke service to key manager--
RevokeAPIURLhttps://
${carbon.local.ip}:${https.nio.port}/revoke/RevokeAPIURL
02. In API gateway revoke API should be pointed to oauth application
deployed in key manager node.
api name=_WSO2AMRevokeAPI_ context=/revoke
resource methods=POST url-mapping=/*
faultSequence=_token_fault_
inSequence
send
endpoint
address uri=
https://keymgt.wso2.com:9445/oauth2/revoke/
/endpoint
/send
/inSequence
outSequence
send/
/outSequence
/resource
handlers
handler
class=org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerCacheExtensionHandler/
/handlers
/api
We need to add this to our product documents as well.
Thanks,
sanjeewa.
--
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779
http://sanjeewamalalgoda.blogspot.com/blog
:http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/
--
Thanks,
Nirdesha Munasinghe,
WSO2 Inc.
Web:http://wso2.com
Mobile: +94 776321920
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Aren't we going to fix https://wso2.org/jira/browse/APIMANAGER-1886 in AM-1.7.0?
Thanks, Sanjeewa. I changed 1.7.0 docs: https://docs.wso2.org/display/AM170/Managing+API+Usage. Cheers, -Nirdesha On Fri, May 16, 2014 at 10:58 AM, Sanjeewa Malalgoda sanje...@wso2.comwrote: Yes i have created doc JIRA[1] for this issue and added updated content. @Nirdesha please add them to our 1.7.0 documents. [1]https://wso2.org/jira/browse/DOCUMENTATION-805 Thanks, sanjeewa. On Thu, May 15, 2014 at 11:16 PM, Charitha Kankanamge chari...@wso2.comwrote: Ok. I figured that we are not going to fix this - https://wso2.org/jira/browse/APIMANAGER-2303 Please make sure to state these limitations in AM documentation. Charitha Kankanamge cell: +1 812-391-7730 http://charithaka.blogspot.com *SOA and Testing without nonsense* On Thu, May 15, 2014 at 10:53 PM, Charitha Kankanamge chari...@wso2.comwrote: Hi Sanjeewa, @Subject. This is about cache invalidation. Will we be able to specify a cache timeout duration in AM-1.7.0? Thanks! Charitha -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/ -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Changing the name of Carbon Applications
Hi Team, From which release cycles do we plan to change the name of Carbon applications to composite applications in the management console UIs please? Asking this because we need to change the docs accordingly. -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] EIP Guide - Message Expiration example scenario is not working.
) at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:166) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:411) at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) What could be the issue here? [1] https://docs.wso2.org/display/IntegrationPatterns/Message+Expiration Thank you Sajini. -- Sajini De SIlva Software Engineer; WSO2 Inc.; http://wso2.com , Email: saj...@wso2.com Blog: http://sajinid.blogspot.com/ Git hub profile: https://github.com/sajinidesilva ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Harsha Kumara Software Engineer, WSO2 Inc. Mobile: +94775505618 Blog:harshcreationz.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Chathurika Mahaarachchi* Software Engineer, QA. WSO2 Inc.: http://wso2.com/ lean.enterprise.middleware Mobile: +94718223950 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- -- Chanaka Fernando Technical Lead WSO2, Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 773337238 Blog : http://soatutorials.blogspot.com LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 Twitter:https://twitter.com/chanakaudaya Wordpress:http://chanakaudaya.wordpress.com -- *Chathurika Mahaarachchi* Software Engineer, QA. WSO2 Inc.: http://wso2.com/ lean.enterprise.middleware Mobile: +94718223950 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] EIP Guide
Fixed it. Thanks for reporting. On Fri, Mar 7, 2014 at 2:43 PM, Gayan Gunawardana ga...@wso2.com wrote: Hi, In EIP guide [1] configuration need to be changed send endpoint address uri= http://localhost:9000/services/SimpleStockQuoteService;http://localhost:9000/services/SimpleStockQuoteService format=soap11/ /endpoint /send With soap version 1.1 try to send without soap action. Soap action need be added (property name=SOAPAction value=getQuote scope=transport/property) [1] https://docs.wso2.org/display/IntegrationPatterns/Messaging+Bridge -- Gayan Gunawardana Software Engineer; WSO2 Inc.; http://wso2.com/ Email: ga...@wso2.com Mobile: +94 (71) 8020933 Blog: http://gayanj2ee.blogspot.com/ -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/d/optout. -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Why don't we have BAM mediator in ESB docs
Added a note in BAM that the BAM mediator config steps are the same for any other server with a listening Thrift port, such as the CEP: http://docs.wso2.org/display/BAM240/Setting+up+BAM+Mediator. Thanks, -Nirdesha On Tue, Oct 29, 2013 at 1:28 PM, Nirdesha Munasinghe nirde...@wso2.comwrote: Hi Jackie, I just talked to the CEP team. As you said, the steps are similar to the ones given in BAM docs. Only difference is that we just point to a CEP server IP instead of BAM. In the docs, we can just say any listening Thrift port and mention BAM, CEP as examples of such. This way we can use the same content for any product with a listening Thrift port. The mediator name is also planned to be changed in an upcoming release to a more generic one. Copying Mohan to add in if I have missed anything. Thanks, -Nirdesha On Tue, Oct 29, 2013 at 12:01 PM, Susinda Perera susi...@wso2.com wrote: On Tue, Oct 29, 2013 at 9:30 AM, Jackie Wheeler jac...@wso2.com wrote: Can you give me more information on how to configure CEP integration? The steps in the BAM documentation are no longer applicable in ESB 4.8.0, which has the BAM feature already installed. For CEP, do you follow the steps to configure a BAM server profile but just point to a CEP server instead, and then use the BAM mediator to send data to that server profile? For CEP, do you follow the steps to configure a BAM server profile but just point to a CEP server instead, and then use the BAM mediator to send data to that server profile? YES, thats why i thought these need to be go with docs, But i'm not much familiar with these stuff better we could discuss this with ESB and CEP guys before proceed. Thanks, Jackie On Mon, Oct 28, 2013 at 8:41 PM, Susinda Perera susi...@wso2.comwrote: Also we need to address CEP integration with ESB, How about going for a title like *WSO2 BAM/CEP Integration http://docs.wso2.org/display/ESB480/WSO2+BAM+Integration *in http://docs.wso2.org/display/ESB480/WSO2+BAM+Integration Thanks On Tue, Oct 29, 2013 at 1:57 AM, Jackie Wheeler jac...@wso2.comwrote: I've added the following pages to address BAM integration with the ESB: http://docs.wso2.org/display/ESB480/WSO2+BAM+Integration http://docs.wso2.org/display/ESB480/Configuring+a+BAM+Server+Profile http://docs.wso2.org/display/ESB480/BAM+Mediator Please let me know if you have any comments or corrections. Please note that as I was testing the configuration, I noticed that *Mediation Data Publishing* link on the Configure tab of the ESB Mgmt Console does not do anything. Is this still needed? Thanks, Jackie On Mon, Oct 28, 2013 at 11:12 AM, Jackie Wheeler jac...@wso2.comwrote: Thanks for the heads up...I'm adding this now. Cheers, Jackie On Thu, Oct 24, 2013 at 11:02 PM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi Susindu, You can find BAM Mediator documentation from[1]. It is covered under BAM docs. I also wonder why BAM Mediator is not listed under Mediator section in ESB docs. [1] http://docs.wso2.org/display/BAM230/Setting+up+BAM+Mediator Thanks, Nuwanw On Thu, Oct 24, 2013 at 7:48 PM, Susinda Perera susi...@wso2.comwrote: Hi All I could not find docs or samples for BAM Mediator in ESB docs BAM mediator is not listed in[1] [1] - http://docs.wso2.org/display/ESB480/Mediators Isnt it should be @ [1] ??? -- *Susinda Perera* Software Engineer Mobile:(+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/groups/opt_out. -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/groups/opt_out. -- *Jackie Wheeler* VP, Technical Content WSO2, Inc. Mobile: +1 510 725-2876 http://wso2.com/ -- *Jackie Wheeler* VP, Technical Content WSO2, Inc. Mobile: +1 510 725-2876 http://wso2.com/ -- *Susinda Perera* Software Engineer Mobile:(+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 -- *Jackie Wheeler* VP, Technical Content WSO2, Inc. Mobile: +1 510 725-2876 http://wso2.com/ -- *Susinda Perera* Software Engineer Mobile:(+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920
Re: [Dev] Why don't we have BAM mediator in ESB docs
Hi Jackie, I just talked to the CEP team. As you said, the steps are similar to the ones given in BAM docs. Only difference is that we just point to a CEP server IP instead of BAM. In the docs, we can just say any listening Thrift port and mention BAM, CEP as examples of such. This way we can use the same content for any product with a listening Thrift port. The mediator name is also planned to be changed in an upcoming release to a more generic one. Copying Mohan to add in if I have missed anything. Thanks, -Nirdesha On Tue, Oct 29, 2013 at 12:01 PM, Susinda Perera susi...@wso2.com wrote: On Tue, Oct 29, 2013 at 9:30 AM, Jackie Wheeler jac...@wso2.com wrote: Can you give me more information on how to configure CEP integration? The steps in the BAM documentation are no longer applicable in ESB 4.8.0, which has the BAM feature already installed. For CEP, do you follow the steps to configure a BAM server profile but just point to a CEP server instead, and then use the BAM mediator to send data to that server profile? For CEP, do you follow the steps to configure a BAM server profile but just point to a CEP server instead, and then use the BAM mediator to send data to that server profile? YES, thats why i thought these need to be go with docs, But i'm not much familiar with these stuff better we could discuss this with ESB and CEP guys before proceed. Thanks, Jackie On Mon, Oct 28, 2013 at 8:41 PM, Susinda Perera susi...@wso2.com wrote: Also we need to address CEP integration with ESB, How about going for a title like *WSO2 BAM/CEP Integrationhttp://docs.wso2.org/display/ESB480/WSO2+BAM+Integration *in http://docs.wso2.org/display/ESB480/WSO2+BAM+Integration Thanks On Tue, Oct 29, 2013 at 1:57 AM, Jackie Wheeler jac...@wso2.com wrote: I've added the following pages to address BAM integration with the ESB: http://docs.wso2.org/display/ESB480/WSO2+BAM+Integration http://docs.wso2.org/display/ESB480/Configuring+a+BAM+Server+Profile http://docs.wso2.org/display/ESB480/BAM+Mediator Please let me know if you have any comments or corrections. Please note that as I was testing the configuration, I noticed that *Mediation Data Publishing* link on the Configure tab of the ESB Mgmt Console does not do anything. Is this still needed? Thanks, Jackie On Mon, Oct 28, 2013 at 11:12 AM, Jackie Wheeler jac...@wso2.comwrote: Thanks for the heads up...I'm adding this now. Cheers, Jackie On Thu, Oct 24, 2013 at 11:02 PM, Nuwan Wimalasekara nuw...@wso2.comwrote: Hi Susindu, You can find BAM Mediator documentation from[1]. It is covered under BAM docs. I also wonder why BAM Mediator is not listed under Mediator section in ESB docs. [1] http://docs.wso2.org/display/BAM230/Setting+up+BAM+Mediator Thanks, Nuwanw On Thu, Oct 24, 2013 at 7:48 PM, Susinda Perera susi...@wso2.comwrote: Hi All I could not find docs or samples for BAM Mediator in ESB docs BAM mediator is not listed in[1] [1] - http://docs.wso2.org/display/ESB480/Mediators Isnt it should be @ [1] ??? -- *Susinda Perera* Software Engineer Mobile:(+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/groups/opt_out. -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/groups/opt_out. -- *Jackie Wheeler* VP, Technical Content WSO2, Inc. Mobile: +1 510 725-2876 http://wso2.com/ -- *Jackie Wheeler* VP, Technical Content WSO2, Inc. Mobile: +1 510 725-2876 http://wso2.com/ -- *Susinda Perera* Software Engineer Mobile:(+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 -- *Jackie Wheeler* VP, Technical Content WSO2, Inc. Mobile: +1 510 725-2876 http://wso2.com/ -- *Susinda Perera* Software Engineer Mobile:(+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] IS configuration need to be done for SSO to work in API Manager
Added the comment to the JIRA. Thanks, -Nirdesha On Mon, Sep 16, 2013 at 12:09 PM, Dulanja Liyanage dula...@wso2.com wrote: Hi, repository/conf/security/application-authenticators.xml is now changed in chunk-02. By default a relative path is given as below: Authenticators Authenticator name=BasicAuthenticator disabled=false factor=1 Status value=10 loginPage= /authenticationendpoint/login.dohttps://localhost:9443/authenticationendpoint/login.do / /Authenticator /Authenticators You only have to specify the full URL if the login page is out of the carbon pack. Thanks regards Dulanja On Tue, Sep 10, 2013 at 3:57 PM, Chamara Ariyarathne chama...@wso2.comwrote: This configuration need to be done in API Manager side too to work some scenarios. Created a doc jira. https://wso2.org/jira/browse/APIMANAGER-1623 On Fri, Sep 6, 2013 at 10:13 PM, Nirdesha Munasinghe nirde...@wso2.comwrote: Thanks Sumedha. On Fri, Sep 6, 2013 at 8:16 PM, Sumedha Rubasinghe sume...@wso2.comwrote: Created a doc issue (https://wso2.org/jira/browse/DOCUMENTATION-285) to track. On Fri, Sep 6, 2013 at 3:12 PM, Chamara Ariyarathne chama...@wso2.comwrote: security/authenticators.xml: Parameter name=IdentityProviderSSOServiceURL https://localhost:9443/samlsso/Parameter as well. https://wso2.org/jira/browse/IDENTITY-1801 On Fri, Sep 6, 2013 at 2:59 PM, Chamara Ariyarathne chama...@wso2.com wrote: https://wso2.org/jira/browse/IDENTITY-1803 is a improvement suggested for IS. The configuration in the repository/conf/security/application-authenticators.xml Authenticators Authenticator name=BasicAuthenticator disabled=false factor=1 Status value=10 loginPage= https://localhost:9443/authenticationendpoint/login.do; / /Authenticator /Authenticators need to be updated if IS is running on a different port. So this needs to go into the APIM docs here. http://docs.wso2.org/display/AM150/Single+Sign-on+with+SAML+2.0 -- *Chamara Ariyarathne* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; *+94772786766* -- *Chamara Ariyarathne* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; *+94772786766* -- /sumedha b : bit.ly/sumedha -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- *Chamara Ariyarathne* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; *+94772786766* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dulanja Liyanage Senior Software Engineer - WSO2 Inc. M: +94776764717 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Misleading configuration in BAM document
Hi Ishara, Please note that this is fixed in BAM 2.3.0: http://docs.wso2.org/display/BAM230/Setting+up+Mediation+Data+Agent Thanks, -Nirdesha On Wed, Sep 4, 2013 at 8:13 AM, Nirdesha Munasinghe nirde...@wso2.comwrote: Will fix this. Please feel free to log a JIRA when you see doc issues going forward. A JIRA is easier for us to track to closure. Thanks, -Nirdesha On Tue, Sep 3, 2013 at 7:28 AM, Ishara Karunarathna isha...@wso2.comwrote: Hi, In the following document, under *Send Messages to the ESB * 1. Download and start WSO2 BAM. Before starting the server, change its port offset to a different value in BAM_home\repository\conf\Carbon.xml file. For example, Offset2/Offset but in the same document it set the offset of the ESB to 2, so its better to use some other value there. Thanks, [1] http://docs.wso2.org/display/BAM230/Setting+up+Mediation+Data+Agent-- Ishara Karunarathna Software Engineer WSO2 Inc. - lean . enterprise . middleware | wso2.com email: isha...@wso2.com, blog: isharaaruna.blogspot.com, mobile: +94 718211678 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] IS configuration need to be done for SSO to work in API Manager
Thanks Sumedha. On Fri, Sep 6, 2013 at 8:16 PM, Sumedha Rubasinghe sume...@wso2.com wrote: Created a doc issue (https://wso2.org/jira/browse/DOCUMENTATION-285) to track. On Fri, Sep 6, 2013 at 3:12 PM, Chamara Ariyarathne chama...@wso2.comwrote: security/authenticators.xml: Parameter name=IdentityProviderSSOServiceURL https://localhost:9443/samlsso/Parameter as well. https://wso2.org/jira/browse/IDENTITY-1801 On Fri, Sep 6, 2013 at 2:59 PM, Chamara Ariyarathne chama...@wso2.comwrote: https://wso2.org/jira/browse/IDENTITY-1803 is a improvement suggested for IS. The configuration in the repository/conf/security/application-authenticators.xml Authenticators Authenticator name=BasicAuthenticator disabled=false factor=1 Status value=10 loginPage= https://localhost:9443/authenticationendpoint/login.do; / /Authenticator /Authenticators need to be updated if IS is running on a different port. So this needs to go into the APIM docs here. http://docs.wso2.org/display/AM150/Single+Sign-on+with+SAML+2.0 -- *Chamara Ariyarathne* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; *+94772786766* -- *Chamara Ariyarathne* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; *+94772786766* -- /sumedha b : bit.ly/sumedha -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Misleading configuration in BAM document
Will fix this. Please feel free to log a JIRA when you see doc issues going forward. A JIRA is easier for us to track to closure. Thanks, -Nirdesha On Tue, Sep 3, 2013 at 7:28 AM, Ishara Karunarathna isha...@wso2.comwrote: Hi, In the following document, under *Send Messages to the ESB * 1. Download and start WSO2 BAM. Before starting the server, change its port offset to a different value in BAM_home\repository\conf\Carbon.xml file. For example, Offset2/Offset but in the same document it set the offset of the ESB to 2, so its better to use some other value there. Thanks, [1] http://docs.wso2.org/display/BAM230/Setting+up+Mediation+Data+Agent-- Ishara Karunarathna Software Engineer WSO2 Inc. - lean . enterprise . middleware | wso2.com email: isha...@wso2.com, blog: isharaaruna.blogspot.com, mobile: +94 718211678 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [API-M 1.4] Document asks me to subscribe using Bronze tier, but it is not listed
Hi Nirmal, Just verified with the APIM team that the Twitter sample is created with the Gold tier. I'll fix the docs. Thanks for reporting this. Regards, -Nirdesha On Wed, Aug 28, 2013 at 1:14 PM, Nirdesha Munasinghe nirde...@wso2.comwrote: Isn't the default application supposed to have all tiers enabled? On Wed, Aug 28, 2013 at 1:00 AM, Nirmal Fernando nir...@wso2.com wrote: This is the sample, I am invoking. On Wed, Aug 28, 2013 at 12:58 AM, Lahiru Sandaruwan lahi...@wso2.comwrote: Did you add 'Bronze' under Tier Availability while creating? Thanks. On Wed, Aug 28, 2013 at 12:39 AM, Nirmal Fernando nir...@wso2.comwrote: http://docs.wso2.org/display/AM140/Access+Twitter%27s+Search+Using+an+API I can see only Gold in tiers. -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/groups/opt_out. -- -- Lahiru Sandaruwan Software Engineer, Platform Technologies, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com cell: (+94) 773 325 954 blog: http://lahiruwrites.blogspot.com/ twitter: http://twitter.com/lahirus linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/groups/opt_out. -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] categorizing samples in AS docs
+1. I have raised [1] to track this. [1] https://wso2.org/jira/browse/DOCUMENTATION-99 On Fri, Jun 21, 2013 at 8:57 AM, Afkham Azeez az...@wso2.com wrote: +1. Great suggestion. Azeez On Fri, Jun 21, 2013 at 7:15 AM, Supun Malinga sup...@wso2.com wrote: Hi All, We have increasing number of sample in AS now. Once j2ee things are done, there will be even more. So as its already confusing to directly say from above, which sample is which, I propose categorize the samples and put them under each category. We do need to discuss and select the categories. For eg: it can be like, j2ee samples, web application samples, axis2 services samples, jaggery samples, mashup samples, data-services samples, etc. But there can be situations this separation won't be clear cut. So we need to discuss and figure this out. WDYT?. [1] http://docs.wso2.org/wiki/display/AS510/Samples thanks, -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/groups/opt_out. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/groups/opt_out. -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] hot deploy not working in ELB
, Test Automation WSO2 Inc. http://wso2.com email : dharsha...@wso2.com dharsha...@wso2.com cell : +94772202595 blog : http://dharshanaw.blogspot.com lean . enterprise . middleware -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/groups/opt_out. -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ -- You received this message because you are subscribed to the Google Groups WSO2 Documentation group. To unsubscribe from this group and stop receiving emails from it, send an email to documentation+unsubscr...@wso2.com. For more options, visit https://groups.google.com/a/wso2.com/groups/opt_out. -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] RabbitMQ sample does not work
Copying documentat...@wso2.com On Thu, May 23, 2013 at 7:55 AM, Eranda Sooriyabandara era...@wso2.comwrote: HI Kishanthan, Its ESB 4.6.0. thanks Eranda On Thu, May 23, 2013 at 7:50 AM, Kishanthan Thangarajah kishant...@wso2.com wrote: Hi Eranda, On which ESB version you tried this? The feature repo was created against 4.5.1. This documentation should point to that version. But for 4.6.0, need to test /create a new repo. @Nirdesha, This documentation heading is wrong - TTRabbitMQ AMQP Transportpdf. It should be corrected as RabbitMQ AMQP Transport. Looks like all the entries in the carbon transport section has this issue : http://docs.wso2.org/wiki/display/ESB460/TTWSO2+Carbon+Transportspdf Thanks, Kishanthan. On Wed, May 22, 2013 at 11:37 PM, Eranda Sooriyabandara era...@wso2.comwrote: HI all, I was able to copy the two jars to dropins and make it work. But as per the sample its a work around. thanks Eranda On Wed, May 22, 2013 at 9:26 PM, Eranda Sooriyabandara era...@wso2.comwrote: Hi all, I followed the steps in [1] but it I was not able to complete it since the feature installation not succeeded. As in the document I add the repo and ESB didn't identify any feature inside it. thanks Eranda [1]. http://docs.wso2.org/wiki/display/ESB460/TTRabbitMQ+AMQP+Transportpdf -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ * * -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ * * -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ * * -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] RabbitMQ sample does not work
Copying documentat...@wso2.com. Missed it last time. On Thu, May 23, 2013 at 8:12 AM, Nirdesha Munasinghe nirde...@wso2.comwrote: Copying documentat...@wso2.com On Thu, May 23, 2013 at 7:55 AM, Eranda Sooriyabandara era...@wso2.comwrote: HI Kishanthan, Its ESB 4.6.0. thanks Eranda On Thu, May 23, 2013 at 7:50 AM, Kishanthan Thangarajah kishant...@wso2.com wrote: Hi Eranda, On which ESB version you tried this? The feature repo was created against 4.5.1. This documentation should point to that version. But for 4.6.0, need to test /create a new repo. @Nirdesha, This documentation heading is wrong - TTRabbitMQ AMQP Transportpdf. It should be corrected as RabbitMQ AMQP Transport. Looks like all the entries in the carbon transport section has this issue : http://docs.wso2.org/wiki/display/ESB460/TTWSO2+Carbon+Transportspdf Thanks, Kishanthan. On Wed, May 22, 2013 at 11:37 PM, Eranda Sooriyabandara era...@wso2.com wrote: HI all, I was able to copy the two jars to dropins and make it work. But as per the sample its a work around. thanks Eranda On Wed, May 22, 2013 at 9:26 PM, Eranda Sooriyabandara era...@wso2.com wrote: Hi all, I followed the steps in [1] but it I was not able to complete it since the feature installation not succeeded. As in the document I add the repo and ESB didn't identify any feature inside it. thanks Eranda [1]. http://docs.wso2.org/wiki/display/ESB460/TTRabbitMQ+AMQP+Transportpdf -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ * * -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ * * -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ * * -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Cant find REMOTE_HOST property in ESB doc wiki
Hi Jackie, I have fixed this in 4.7.0 as well. Regards, -Nirdesha On Thu, May 2, 2013 at 10:04 PM, Jackie Wheeler jac...@wso2.com wrote: Nirdesha, please also make those changes to the 4.7.0 docs. Thanks, Jackie On Thu, May 2, 2013 at 1:55 AM, Amila Maha Arachchi ami...@wso2.comwrote: Great. Thanks Nirdesha. On Thu, May 2, 2013 at 1:40 PM, Nirdesha Munasinghe nirde...@wso2.comwrote: Hi Amila, There were few properties missing, which I added to 4.6.0: http://docs.wso2.org/wiki/display/ESB460/Properties+Reference Thanks for informing. Regards, -Nirdesha On Tue, Apr 30, 2013 at 5:15 PM, Amila Maha Arachchi ami...@wso2.comwrote: Hi, ESB 4.0.3 documentation [1] has some properties which are not available in the doc wiki [2]. Any reason for this? [1] http://wso2.org/project/esb/java/4.0.3/docs/properties_guide.html#http [2] http://docs.wso2.org/wiki/display/ESB460/Properties+Reference Regards, AmilaM. -- *Amila Maharachchi* Technical Lead Member, Management Committee - Cloud Platform TG WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- *Amila Maharachchi* Technical Lead Member, Management Committee - Cloud Platform TG WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 -- *Jackie Wheeler* VP, Technical Content WSO2, Inc. Mobile: +1 510 725-2876 http://wso2.com/ -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Cant find REMOTE_HOST property in ESB doc wiki
Hi Amila, There were few properties missing, which I added to 4.6.0: http://docs.wso2.org/wiki/display/ESB460/Properties+Reference Thanks for informing. Regards, -Nirdesha On Tue, Apr 30, 2013 at 5:15 PM, Amila Maha Arachchi ami...@wso2.comwrote: Hi, ESB 4.0.3 documentation [1] has some properties which are not available in the doc wiki [2]. Any reason for this? [1] http://wso2.org/project/esb/java/4.0.3/docs/properties_guide.html#http [2] http://docs.wso2.org/wiki/display/ESB460/Properties+Reference Regards, AmilaM. -- *Amila Maharachchi* Technical Lead Member, Management Committee - Cloud Platform TG WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WkaBasedMembershipScheme No responses received from WKA members
Hi Nirmal, I removed the page and edited the titles a bit. Thanks, -Nirdesha On Thu, May 2, 2013 at 10:08 AM, Nirdesha Munasinghe nirde...@wso2.comwrote: Hi Nirmal, Both pages have similar content mostly. I think the content in [1] is already captured in the new page. Shall we remove [1] please since it is repeating. [1]: http://docs.wso2.org/wiki/display/ELB203/Configuring+Management+and+Worker+Node+Separated+Setup Thanks, -Nirdesha On Thu, May 2, 2013 at 8:51 AM, Nirmal Fernando nir...@wso2.com wrote: Hi Eranda, Please let us know whether you find http://docs.wso2.org/wiki/display/ELB203/Configuring+Management+and+Worker+Node+Separated+Setupuseful and any improvements that you think we need to add. On Wed, May 1, 2013 at 2:25 PM, Nirmal Fernando nir...@wso2.com wrote: Hi Eranda, Please follow http://docs.wso2.org/wiki/display/ELB203/Configuring+Management+and+Worker+Node+Separated+Setup We're working on removing [1]. On Wed, May 1, 2013 at 1:49 PM, Eranda Sooriyabandara era...@wso2.comwrote: Hi Again, I followed the documentation in [1]. Used ESB 4.6.0 and LB 2.0.3. I did add those entries as in the documentation. It works for the master node, but not working for the slave nodes. thanks Eranda [1]. http://docs.wso2.org/wiki/display/ELB203/Setup+ELB+with+WSO2+ESB#SetupELBwithWSO2ESB-management On Wed, May 1, 2013 at 1:24 PM, Nirmal Fernando nir...@wso2.comwrote: Hi Eranda, Probably, you don't have a matching GroupManagementAgent created for this cluster in ELB side. Please check that there's an entry in loadbalancer.conf to match your cluster's domain and sub domain. On Wed, May 1, 2013 at 12:59 PM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Nirmal, Following log appears in the worker node when setting up the ELB. What can be the cause for this. [2013-05-01 12:57:00,657] INFO - WkaBasedMembershipScheme Sending JOIN message to WKA members... [2013-05-01 12:57:10,671] INFO - WkaBasedMembershipScheme No responses received from WKA members [2013-05-01 12:57:15,672] INFO - WkaBasedMembershipScheme Sending JOIN message to WKA members... [2013-05-01 12:57:25,674] INFO - WkaBasedMembershipScheme No responses received from WKA members [2013-05-01 12:57:30,675] INFO - WkaBasedMembershipScheme Sending JOIN message to WKA members... thanks Eranda -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ * * -- Thanks regards, Nirmal Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ * * -- Thanks regards, Nirmal Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ -- Thanks regards, Nirmal Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Developer oriented content in Carbon documentation
Hi team, We'll look into this. I am adding Mariangela to the loop. Regards, -Nirdesha On Thu, Apr 18, 2013 at 6:34 AM, Nirmal Fernando nir...@wso2.com wrote: +1 would be very useful. On Apr 18, 2013 12:05 AM, Sameera Jayasoma same...@wso2.com wrote: +1 for adding such content apart from the user-guides. Contents regarding some of the topics are already available in the form of Presentations, Webinars and mail theads. I can contribute to the class loading related content. Thanks, Sameera. On Wed, Apr 17, 2013 at 10:53 AM, Pradeep Fernando prad...@wso2.comwrote: Hi All, Right now our wiki based documentation[1] for Carbon only contains user(middleware user) oriented documentation. However being a server framework Carbon documentation should have developer aspect as well. IMO, it should contain topics such as, - Carbon component development and best practices - ClassLoading hierarchy - Creating/Provisioning your own product using maven. - How to create multiple profile distribution - Logging internals. - etc The above topics wont much of an interest to a typical user, however Carbon developers, both internal/external will benefit from the above. [1] http://docs.wso2.org/wiki/display/Carbon410/Carbon+Features Thanks, --Pradeep ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sameera Jayasoma Senior Technical Lead WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://sameera.adahas.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] everyone role name renamed to Internal/everyone
Hi All, I just had a chat with Asela and seems like this change will be applied to products based on Carbon 4.2.x and after. Therefore, I will not be changing this in any of the docs released recently. Thanks, -Nirdesha On Tue, Mar 12, 2013 at 7:14 AM, Samisa Abeysinghe sam...@wso2.com wrote: Any data migration implications due to this for our cloud stuff and existing on-premise deployments? If there are, we need to create data migration tools too please. On Tue, Mar 12, 2013 at 1:14 AM, Ajith Vitharana aji...@wso2.com wrote: On Tue, Mar 12, 2013 at 12:57 AM, Prabath Siriwardena prab...@wso2.comwrote: Yes.. now we have a clear separation between internal/external and system roles. Please update the docs accordingly.. sorry for the trouble. Anyway all UM docs need to be updated. Ok. But not only the docs but also we have to provide the migrations scripts and configuration migration guides for the future releases, if we stored those values in DB and configurations. Thanks Ajith Thanks regards, -Prabath On Tue, Mar 12, 2013 at 12:49 AM, Ajith Vitharana aji...@wso2.comwrote: Hi all, According to my understand this is just a constant and value can be any valid name. What are the advantages we got to changed this to Internal/everyone ? Every product have to update their documentations , images, samples and configurations with this change. [1] http://docs.wso2.org/wiki/dosearchsite.action?queryString=everyonewhere=Governance460type=lastModified=contributor=contributorUsername= Thanks Ajith -- Ajith Vitharana. Senior Software Engineer, Member,Management Committee, Integration Technologies. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com -- Ajith Vitharana. Senior Software Engineer, Member,Management Committee, Integration Technologies. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB 4.5.1 UDP Transport documentation is incorrect
Thanks Shelan. +1 for editing then and there as you see minor issues like configuration/file path changes and obvious typos. Everyone at WSO2 has edit rights to all docs. On Wed, Mar 20, 2013 at 4:17 AM, Shelan Perera she...@wso2.com wrote: Hi, It is better to edit if it is identified :). We have the edit rights. ( i have done couple of those edits otherwise it may get slipped) Best On Tue, Mar 19, 2013 at 3:39 PM, Kasun Weranga kas...@wso2.com wrote: Hi, transportReceiver name=udp/ transportSender name=udp/ Should be corrected as transportReceiver name=udp class= org.apache.axis2.transport.udp.UDPListener/ transportSender name=udp class= org.apache.axis2.transport.udp.UDPSender/ Thanks, KasunW. doc link - http://docs.wso2.org/wiki/display/ESB451/Configuring+WSO2+ESB+for+UDP+Transport -- *Kasun Weranga* ** Member, Management Committee - Data Technologies Software Engineer *WSO2, Inc. *lean.enterprise.middleware. mobile : +94 772314602 http://sanjeewamalalgoda.blogspot.com/blog : http://kasunweranga.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Shelan Perera* Software Engineer ** *WSO2, Inc. : wso2.com* lean.enterprise.middleware. *Home Page* : shelan.org *Blog* : blog.shelan.org *Linked-i*n : http://www.linkedin.com/pub/shelan-perera/a/194/465 *Twitter* :https://twitter.com/#!/shelan *Mobile* : +94 772 604 402 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Wiki page on HL7 transport is missing in ESB 4.5.0
Hi Nirmal, I just added it to 4.5.0. :) Information about HL7 transport was added to docs after 4.5.0 was released, which is probably why it didn't appear in 4.5.0. Generally we update only the latest version available at the time as docs get obsolete quickly due to frequent releases. Thanks, -Nirdesha On Sun, Mar 10, 2013 at 10:03 PM, Nirmal Fernando nir...@wso2.com wrote: Sorry for the noise, it's there. On Sun, Mar 10, 2013 at 9:50 PM, Nirmal Fernando nir...@wso2.com wrote: Can't find it here: http://docs.wso2.org/wiki/display/ESB450/Enterprise+Service+Bus+Documentation -- Thanks regards, Nirmal Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ http://nirmalfdo.blogspot.com/ -- Thanks regards, Nirmal Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ http://nirmalfdo.blogspot.com/ -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] APIM documentation does not mention about the key manager
Hi Amila, I will write up a description which the team can add in to. Key manager should appear as a component here. Thanks for pointing out. Regards, -Nirdesha On Wed, Jan 16, 2013 at 2:56 PM, Amila Maha Arachchi ami...@wso2.comwrote: Hi, [1] Does not mention about the key manager components of APIM. Any reason? [1] http://docs.wso2.org/wiki/display/AM130/API+Manager+Components Regards, AmilaM. -- *Amila Maharachchi* Technical Lead Member, Management Committee - Cloud Platform TG WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] APIM documentation does not mention about the key manager
Hi Sanjeewa, Thanks. Will take the content from your OT article. Regards, -Nirdesha On Wed, Jan 16, 2013 at 3:13 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote: HI Nirdesha, I have done article describing all these components and their usages(on publishing process). So we can take content directly from that and update document. Thanks. On Wed, Jan 16, 2013 at 3:09 PM, Nirdesha Munasinghe nirde...@wso2.comwrote: Hi Amila, I will write up a description which the team can add in to. Key manager should appear as a component here. Thanks for pointing out. Regards, -Nirdesha On Wed, Jan 16, 2013 at 2:56 PM, Amila Maha Arachchi ami...@wso2.comwrote: Hi, [1] Does not mention about the key manager components of APIM. Any reason? [1] http://docs.wso2.org/wiki/display/AM130/API+Manager+Components Regards, AmilaM. -- *Amila Maharachchi* Technical Lead Member, Management Committee - Cloud Platform TG WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +14084122175 | +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/ -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Overall organization and content for Developer Studio docs
Wiki migration also needs to be done. Regards, -Nirdesha On Mon, Dec 10, 2012 at 8:26 PM, Chathuri Wimalasena kamalas...@gmail.comwrote: Hi Harshana, Adding and starting Carbon server docs can be found here [1]. IMO, I think we may need to come up with better topics. Thanks and Regards, Chathuri [1] http://dist.wso2.org/products/developer-studio/2.1.0/docs/testing_deploying_category.html#Deploy On Mon, Dec 10, 2012 at 3:25 AM, Harshana Martin harsh...@wso2.comwrote: he adding and starting a carbon server from Eclipse. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Plan for WSO2 API Manager Documentation
Hi Sumedha, It's started and content is being added: http://docs.wso2.org/wiki/display/AM100/WSO2+API+Manager+Documentation Currently there is no issue in getting the doc ready before 3rd August. Regards, -Nirdesha On Tue, Jul 24, 2012 at 10:23 AM, Sumedha Rubasinghe sume...@wso2.comwrote: Nirdesha, How is $subject progressing? -- /sumedha -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] AS 5.0.0 Documentation
Hi Isuru, While I create new spaces for the latest features, please let me know if there is anything you like to change in the new AS documentation structure. It has changed a lot from the previous doc version. Regards, -Nirdesha On Tue, Jun 26, 2012 at 11:08 AM, Isuru Suriarachchi is...@wso2.com wrote: Hi Nirdesha, Here's a rough list of new features added in AS 5.0.0. Webapp based JAX-WS support JAX-RS support Lazy loading for Services Lazy loading for Web Applications Jaggery Javascript Services Total Tomcat compliance There are list of improvements also which should go under existing features. Thanks, ~Isuru On Mon, Jun 25, 2012 at 3:08 PM, Nirdesha Munasinghe nirde...@wso2.comwrote: Hi Isuru, I think we can do a feature-based documentation for AS 5.0.0 since all AS-related features used in the older version are documented now. Using them, I created this space manually (Homepage to be edited): http://docs.wso2.org/wiki/display/AS500/WSO2+Application+Server+Documentation Please refer to the information hierarchy and let me know if you are fine with it. You can find the feature list and their space URLs here: https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0Am89tsNpm9bfdEdyamJhNnJpOTJFWnYzM0VnQ1gxY1E#gid=0 Please let me know any new features which need to be added to AS 5.0.0. Once the existing features are edited and new ones are added, we can incorporate them and recreate the new documentation. Regards, -Nirdesha On Mon, Jun 25, 2012 at 11:31 AM, Isuru Suriarachchi is...@wso2.comwrote: As we are getting closer to the release now it's time to concentrate on the documentation as well. According to Nirdesha, she has already done the wiki based documentation for AS 4.1.2 [1]. So we have to create a new doc for 5.0.0 and include all the new features and changes done for the existing features. I think with this new wiki based documentation, we don't need docs packs through the build. Now we only need the context sensitive helps coming from each component. Shall we remove doc pack generation from the build?? Thanks, ~Isuru [1] http://docs.wso2.org/wiki/display/AS412/WSO2+Application+Server+Documentation -- Isuru Suriarachchi Senior Technical Lead WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 -- Isuru Suriarachchi Senior Technical Lead WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] AS 5.0.0 Documentation
+1 to Isuru's idea. The plan is to gradually retire the old docs and completely move to wiki. It is easier for users to have a single place to refer to in terms of formal product documentation, which can have links to other resources where applicable. Thanks, -Nirdesha On Mon, Jun 25, 2012 at 1:10 PM, Isuru Suriarachchi is...@wso2.com wrote: On Mon, Jun 25, 2012 at 1:05 PM, Senaka Fernando sen...@wso2.com wrote: Java API docs can't be written on the wiki docs, :). These are javadocs and need to be packed in this way, isn't it? You don't have to write java docs on the wiki :). Host it somewhere and point to that from the wiki based doc. Having java docs on a different distribution and having other docs on the wiki is a mess. All should be in a single place. Thanks, ~Isuru Thanks, Senaka. On Mon, Jun 25, 2012 at 1:02 PM, Isuru Suriarachchi is...@wso2.comwrote: On Mon, Jun 25, 2012 at 1:00 PM, Senaka Fernando sen...@wso2.comwrote: Hi all, FYI, we have already removed docs from G-Reg distro, but we still build a docs pack that contains the release note, and the Java APIs, details on checking out source etc Why can't we move these also to the wiki based documentation and completely get rid of the docs pack? Thanks, ~Isuru (auto-generated by Maven), and several hyperlinks. Thanks, Senaka. On Mon, Jun 25, 2012 at 11:37 AM, Supun Malinga sup...@wso2.comwrote: On Mon, Jun 25, 2012 at 11:31 AM, Isuru Suriarachchi is...@wso2.comwrote: As we are getting closer to the release now it's time to concentrate on the documentation as well. According to Nirdesha, she has already done the wiki based documentation for AS 4.1.2 [1]. So we have to create a new doc for 5.0.0 and include all the new features and changes done for the existing features. I think with this new wiki based documentation, we don't need docs packs through the build. Now we only need the context sensitive helps coming from each component. Shall we remove doc pack generation from the build?? +1 lets make sure we incorporate all the stuff in doc packs in the wiki. thanks, Thanks, ~Isuru [1] http://docs.wso2.org/wiki/display/AS412/WSO2+Application+Server+Documentation -- Isuru Suriarachchi Senior Technical Lead WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Senaka Fernando* Member - Integration Technologies Management Committee; Technical Lead; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware -- Isuru Suriarachchi Senior Technical Lead WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware -- *Senaka Fernando* Member - Integration Technologies Management Committee; Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware -- Isuru Suriarachchi Senior Technical Lead WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] docs.wso2.com is inaccessible
Hi All, Infra recently upgraded the server and seems like the URLs have changed. Here are the links: http://docs.wso2.org/wiki/display/ESB403/Enterprise+Service+Bus+Documentation http://docs.wso2.org/wiki/dashboard.action Regards, -Nirdesha On Mon, Jun 11, 2012 at 12:07 PM, Nuwan Dias nuw...@wso2.com wrote: Same happened to me as well. I am away from wso2 network too. Thanks, NuwanD. On Mon, Jun 11, 2012 at 5:59 PM, Yumani Ranaweera yum...@wso2.com wrote: Hi, I get docs.wso2.org redirected to a faulty url. i.e. Tried accessing esb documentation [1] and it failed at following redirection loop [2]. Am away frm wso2 network, hence tried after connecting to vpn also. But the results are same. Please ignore this if I have missed ant notification.. [1] http://docs.wso2.org/display/ESB403/Send+Mediator#SendMediator-Anonymous [2] http://docs.wso2.org/wikiwikiwikiwikiwikiwikiwikiwikiwikiwikiwikiwikiwikiwikiwikiwikiwikiwikiwikiwikiwikidisplay/ESB403/URLRewrite+Mediator -- Thanks, * * * Yumani Ranaweera* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nuwan Dias Software Engineer - WSO2, Inc. Integration Technologies Team email : nuw...@wso2.com Phone : +94 777 775 729 -- Thanks, Nirdesha Munasinghe, WSO2 Inc. Web:http://wso2.com Mobile: +94 776321920 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
