I want to use Mulesoft Anypoint studio to listen to some queues in rabbitMQ. But the latest version of Anypoint will not let me install the AMQP connector from the Anypoint Exchange suggested by several documentations. It will tell me Cannot complete the request see the error log for details. First of all I can not find the error log of the Anypoint Studio. But there is a hidden .log file in the workdirectory, but it also said See the error log for details.
Does anybody have a solution for this, or know what is wrong with the AMQP connector on the Anypoint Exchange?
When I want to install another connector like the MongoDB Connector, everything went ok.
You can install it as follows:
go to Help -> Install new software
select Anypoint Connectors Update Site
select Community -> Mule AMQP Transport
Try refreshing the Connector's update site following the steps below:
Go to Preferences
Select Install/Update --> Available Software Sites
Select the Connectors Update Site and clic option "Reload".
Related
I am just starting out to use Anypoint MQ and in the past have used Apache ActiveMQ.
In case of Apache ActiveMQ , Mule connector provides an option where we can choose if we want to publish a message as Persistent Vs NonPersistent
Dont see that option with Publish connector for AnypointMQ
Tried googling but am not getting any details regarding the same ....
any pointers would be appreciated .. Thanks !
Anypoint MQ doesn't used that terminology or has an equivalent feature. Having said that it always operates in a similar way to ActiveMQ persistent mode. You can find it in the public documentation:
Because the storage solution for Anypoint MQ is durable, messages that were already in the Anypoint MQ system before service was interrupted are retained.
I am new to Mule and followed this blog to create a "websphere-mq connector" through the jms connector. I am using the community edition.
In order to connect to the websphere mq server, I must run the application under a specific Windows username. Running the mule application in Mule Design under the specific username, I am able to connect and receive messages. However, I am unable to connect to the websphere mq server through the standalone application running on a windows server. I changed the user on the service that is running mule to the specific user but am unable to get authorization to the websphere mq server.
Any additional insight would be much appreciated.
I would suggest reviewing the "Getting going without turning off security" article for an introduction to MQ security. This might help get the MQ system correctly configured.
The stand alone application runs the Tanuki Software wrapper as the user assigned to the environment variable %USERNAME% in windows. Even though I updated the user in the Mule service to run as the approved user, the wrapper will take the environment variable.
To solve the problem, I updated the wrapper.conf file to include the following:
set.USERNAME=<approvedUsername>
the environment variable %USERNAME% is now set to the approved username, in which mule will allow the JMS connector to the authenticate with the correct username.
what is the best way to monitor the Mule ESB instances. Is there a way i can get alerted when my mule instance goes down for some reason. I have 4 instances of Mule running and how will I come to know if 1 of them got down due to some reason.
Thanks!
I assume you are running community edition? (Enterprise edition provides a Management Console which allows you to define alerts). If you are using CE, then you are able to enable JMX monitoring on the instances and then use one of many ways to verify based on JMX info, whether your server is running. One way is to write your own application that retrieves JMX data programmatically and act accordingly.
HTH
If you are using Mule EE, you can use MMC to monitor all your instances as Gabriel has already suggested. My suggestion would be to install MMC inside tomcat on a separate server. This is to ensure that even if your Mule Server crashes or goes down, your MMC is still running and can send you alerts about your Mule server downtime. You can refer below link for details on how to setup server down and up alerts.
https://developer.mulesoft.com/docs/display/current/Working+With+Alerts
Additionally I would recommend to use MMC with database persistence to ensure you have ability to recover MMC workspace even if your MMC server crashes. You can refer about MMC setup with DB persistence at below link.
https://developer.mulesoft.com/docs/display/current/Configuring+MMC+for+External+Databases+-+Quick+Reference
If you don't have Mule EE, you may want to explore other tools or customer alerting applications as suggested by Gabriel.
HTH
You can set up a JMX agent by adding the following lines into your "conf/wrapper.conf" file :
wrapper.java.additional.19=-Dcom.sun.management.jmxremote
wrapper.java.additional.20=-Dcom.sun.management.jmxremote.port=10055
wrapper.java.additional.21=-Dcom.sun.management.jmxremote.authenticate=false
wrapper.java.additional.22=-Dcom.sun.management.jmxremote.ssl=false
wrapper.java.additional.23=-Djava.rmi.server.hostname=127.0.0.1
don't forget to change the values accordingly. Also you can implement SSL authentication with a few extra lines.
Now once your monitoring platform is set up you can always activate Java pollers and start the server.
I have been tasked with integrating ActiveMQ with Weblogic (v 10.3.6.0).
I have downloaded ActiveMQ v 5.10.0, installed it upon the server and browsed to localhost:8161/admin in order to confirm that ActiveMQ is running.
I'm not sure how to progress from here in order to complete my goal. This link:
http://activemq.apache.org/weblogic-integration.html
.. suggests that there are two approaches to deploying ActiveMQ on Weblogic: either deploying a broker as an application or using a J2EE Connector. I'm investigating the latter approach as I have now installed ActiveMQ on the server (which means that I already have a running broker, I assume) but can't find much useful information on the Net about how to do this.
This page:
http://activemq.apache.org/resource-adapter.html
... suggests that it can be done via a JCA Resource Adapter but again does not give any details on how to do it.
If anyone has any advice or guidance, I'd appreciate it.
Thanks in advance.
Did you try this: http://activemq.apache.org/how-to-deploy-activemq-ra-versionrar-to-weblogic.html?
You will have to grab the resource adapter from maven.
Not that your local installation will help you much expect for testing etc. You should deploy AMQ inside WebLogic if you want it to serve as the JMS layer of WebLogic - otherwise a totally standalone installation is fine. But then you're done, and I suspect you want the deployed version non the less.
I have a question regarding to how to use the wso2 esb connector. I have just followed these steps: http://docs.wso2.org/display/ESB480/Using+a+Connector to get more information. Then I checked out the sample connector from: https://github.com/wso2/esb-connectors/tree/master/distribution/foo-connector to build and try to run this sample. After deploying successfully, I don't know how to use it. ESB. I am using wso2 esb 4.8.
Download the connector zip file from https://github.com/wso2/esb-connectors/tree/master/distribution
Add and enable connector as described in http://docs.wso2.org/display/ESB480/Managing+Connectors+in+Your+ESB+Instance
To add a connector:
On the Main tab in the ESB Management Console, under Connectors click Add.
Click Browse, specify the ZIP file, and click Open.
Click Upload.
The connector will now appear in the Connectors list and is ready to
be enabled in your ESB instance.
To enable a connector:
On the Main tab in the ESB Management Console, under Connectors click List to view your uploaded connectors.
Click Enable next to a connector you want to enable, and then confirm that you want to change its status. Repeat this step for each
connector you want to enable.
Use the connector as described in the doc (eg. Twitter Connector) within your ESB configuration.
I think the missing steps are to add a proxy to use connector, and visit the proxy to invoke the connector.