wso2esb

What are the different log files in WSO2 ESB?

冷暖自知 提交于 2019-12-01 18:17:00
问题 In WSO2 ESB I have several log files in the repository/log directory. What are the differences and which one should I use for the daily control if everything is alright? Here the list of log files: 回答1: Well I experienced now the following: http_access_xxxx.log : Contains log of any HTTP access (in my case only the carbon admin jsp) wso2carbon.log : Contains the real log output of the Application Server (most important one) wso2carbon-trace-messages.log : Always empty - don't know what it is

What are the different log files in WSO2 ESB?

被刻印的时光 ゝ 提交于 2019-12-01 18:02:03
In WSO2 ESB I have several log files in the repository/log directory. What are the differences and which one should I use for the daily control if everything is alright? Here the list of log files: Well I experienced now the following: http_access_xxxx.log : Contains log of any HTTP access (in my case only the carbon admin jsp) wso2carbon.log : Contains the real log output of the Application Server (most important one) wso2carbon-trace-messages.log : Always empty - don't know what it is for wso2-esb-error.log : Lists all WARNING and ERROR message from the wso2carbon.log again here - no INFO or

How to dynamically route message in WSO2 ESB based on XML configuration file

我的未来我决定 提交于 2019-12-01 14:19:17
I am trying to route a message based on information in a XML snippet stored as a local entry (key=mapping_id_ep_v1.xml). The id used to look-up the correct endpoint and it is part of the message body. This is the XML snippet used to map id's to endpoints: <mappings> <mapping id="ep_1">http://localhost:8280/services/ep_1</mapping> <mapping id="ep_2">http://localhost:8280/services/ep_2</mapping> <mapping id="ep_3">http://localhost:8280/services/ep_3</mapping> <mappings> I retrieve the id from the body to look-up the endpoint using the following statement: <property name="LOOK-UP" expression="/

RabbitMQ AMQP Transport Support in WSO2 ESB 4.8

半腔热情 提交于 2019-12-01 14:02:11
http://docs.wso2.org/display/ESB480/RabbitMQ+AMQP+Transport i have gone through this example to get RabbitMQ AMQP transport support in WSO2 ESB 4.8 but i am getting following error during the Creation of the RabbitMQ Proxy Service. Unable to generate proxy data from source: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[16,93]Message: The reference to entity 'rabbitmq.server.port' must end with the ';' delimiter. any solution ?? thanks Admin console "complains" about unescaped & (ampersand) character. If you change the line with endpoint address by replacing & with & you should

How to access system property from WSO2 ESB and Registry

丶灬走出姿态 提交于 2019-12-01 13:24:36
问题 My WSO2 ESB proxy service references an endpoint which is located at different URLs in various environments - DEV, TEST, PROD. According to the WSO2 documentation, I need to store the endpoint definition in the Governance Registry and modify the URL in endpoint XML file in each environment. That might work fine for the organizations with 1 or 2 proxies, but becomes a significant overhead for a 10+ proxies. Another scenario is when I need to read certain environment-specific properties in my

How to retrieve multiple rows from database using WSO2 ESB?

风流意气都作罢 提交于 2019-12-01 13:01:29
I want to retrieve multiple rows in a db using wso2 esb. Using dblookup mediator I am able to retreive only one row. It is suggested to use WSO2 DSS can you please help me with using DSS to retrieve multiple rows in ESB completely. Thanks If you don't want to use DSS (which is our case), then you might try the custom mediator that can be found here. https://github.com/mephist/wso2-esb-dbselect Data Service server is used to expose your data(base) ,with sql ,as an available xml/restful web services . You could then call the data service through its endpoint from your ESB proxy service,

WSO2 API Manager - Expose Publisher & Store URLs to public

|▌冷眼眸甩不掉的悲伤 提交于 2019-12-01 12:19:07
问题 I'm using WSO2 API Manager for creating and managing a developer community. According to my knowledge API manager is driven on WSO2 Carbon Server which again runs on Apache Tomcat. Up to now I'm able to run WSO2 API manager without any issues. I could open up store and publisher using below urls. https://<MyHostName>:9443/publisher https://<MyHostName>:9443/store What I want to know is, how can I expose these two URLs to public? I would like something like below as URLs(without ports). https:

Working example on Spring Mediator in WSO2 ESB 4.6.0

一笑奈何 提交于 2019-12-01 11:58:38
Hi i am working on Spring Mediator in WSO2 ESB 4.6.0, using this and this tutorial I am getting the Error as follows: ERROR - SpringMediator Cannot look up Spring configuration conf/sample/resources/spring/springsample.xml ERROR - SpringMediatorCannot reference application context with key : conf/sample/resources/spring/springsample.xml Could you please explain me how to solve this. I got to work this as below, The class should extends AbstractMediator and override the mediate() method as follows, package com.test.spring.mediator.workingexampleonspringmediator; import org.apache.synapse

WSO2 API Manager - Expose Publisher & Store URLs to public

≯℡__Kan透↙ 提交于 2019-12-01 11:51:25
I'm using WSO2 API Manager for creating and managing a developer community. According to my knowledge API manager is driven on WSO2 Carbon Server which again runs on Apache Tomcat. Up to now I'm able to run WSO2 API manager without any issues. I could open up store and publisher using below urls. https://<MyHostName>:9443/publisher https://<MyHostName>:9443/store What I want to know is, how can I expose these two URLs to public? I would like something like below as URLs(without ports). https://<MyHostName>/publisher https://<MyHostName>/store or https://publisher.<MyHostName> https://store.

How to dynamically route message in WSO2 ESB based on XML configuration file

谁说我不能喝 提交于 2019-12-01 10:43:22
问题 I am trying to route a message based on information in a XML snippet stored as a local entry (key=mapping_id_ep_v1.xml). The id used to look-up the correct endpoint and it is part of the message body. This is the XML snippet used to map id's to endpoints: <mappings> <mapping id="ep_1">http://localhost:8280/services/ep_1</mapping> <mapping id="ep_2">http://localhost:8280/services/ep_2</mapping> <mapping id="ep_3">http://localhost:8280/services/ep_3</mapping> <mappings> I retrieve the id from