Skip to main content

What is WSO2 Store and what you can get from it?

WSO2 provides extensions to provide additional functionality which are not available with the OOTB product offerings. These extensions are hosted in the WSO2 store. All the extensions can be downloaded for free and use without any cost.
WSO2 Store provides 4 types of extensions to WSO2 platform.
  1. ESB Connectors - These are connectors which can be used to connect WSO2 ESB with popular cloud APIs as well as enterprise systems. Some examples are Salesforce, SAP, PeopleSoft, AS4.
  2. IS Connectors - These are connectors which can be used to connect WSO2 Identity Server (IS) with external Identity providers over different protocols. Some examples are OpenID Connect, Mobile Connect, SAML Authenticator, SMSOTP
  3. Analytics Extensions - These are extensions which can be used integrate different technologies with Siddhi query language which is used in WSO2 Data Analytics Server (Stream Processor). Some examples are R extension, Python extension, Javascript extension, PMML extension
  4. Integration Solutions - These are pre-built integration templates which can be used integrate 2 or more different systems. Some examples are Github to Google Sheets template, Salesforce to Gmail and Google Sheets template
All these extensions comes with comprehensive documentation. WSO2 provides professional support for customers who wants to use these connectors in their enterprise systems.
Labels:

Comments

  1. PiyushMarch 11, 2019 at 11:48 PM

    Find out the Black Friday Deals and offers on two stores i.e. Lord and Taylor or Nordstrom. Don't miss this deals and offers on this Black Friday.
    Lord and Taylor Black Friday Deals
    Nordstrom Black Friday Deals

    ReplyDelete
  2. Nina AthenaMay 28, 2019 at 8:57 PM

    Thank you for sharing your thoughts and knowledge on this topic. This is really helpful and informative, as this gave me more insight to create more ideas and solutions for my plan. I would love to see more updates from you.

    Web Development Services

    ReplyDelete

Post a Comment

Popular posts from this blog

How to protect your APIs with self contained access token (JWT) using WSO2 API Manager and WSO2 Identity Server

In a typical enterprise information system, there is a high chance that people will use different types of systems built by different vendors to implement certain types of functionalities. The APIs might be hosted in an API Manager developed by vendor A and the user management can be implemented using a different vendor (vendor B). In this type of a situation, one system will not be able to directly contact the other system but they want to use both systems in tandem. Self-contained access tokens are used in these types of situations where applications can get the token from one system and use that in another system to access protected resources. In this scenario, the second system does not need to make a contact to the first system over the network to validate the user information since the token is self-contained and it has relevant details about the user. This will improve the token processing time significantly since it completely removes the network interaction. The below fig...
1 comment
Read more

WSO2 ESB creating a response for a "GET" request

When you are creating REST APIs with WSO2 ESB, you may need to send some response message back to the user when something goes wrong. In this kind of scenario, you can create a payload inside the ESB and send it back. For doing this, you can use the below configuration. <api xmlns=" http://ws.apache.org/ ns/synapse " name="LoopBackProxy" context="/loopback">    <resource methods="POST GET">       <inSequence>          <property name="NO_ENTITY_BODY" scope="axis2" action="remove"></property>          <log level="full"></log>          <payloadFactory media-type="xml">             <format>                <m:messageBeforeLoopBack xmlns:m=" http://services...
Post a Comment
Read more

How to configure timeouts in WSO2 ESB to get rid of client timeout errors

WSO2 ESB has defined some configuration parameters which controls the timeout of a particular request which is going out of ESB. In a particular  scneario, your client sends a request to ESB, and then ESB sends a request to another endpoint to serve the request. CLIENT->WSO2 ESB->BACKEND The reason for clients getting timeout is that ESB timeout is larger than client's timeout. This can be solved by either increasing the timeout at client side or by decreasing the timeout in ESB side. In any of the case, you can control the timeout in ESB using the below properties. 1) Global timeout defined in synapse.properties (ESB_HOME\repository\conf\) file. This will decide the maximum time that a callback is waiting in the ESB for a response for a particular request. If ESB does not get any response from Back End, it will drop the message and clears out the call back. This is a global level parameter which affects all the endpoints configured in ESB. synapse.global_timeout_inte...
6 comments
Read more