I am using Tomcat 7.0. I have deployed a Java-based application in it. I want to monitor application datasources health using JMX console. But, I must be missing something, because I have enabled JMX and connected to it, but I'm still unable to get the datasource details.
Same question goes about monitoring in wso2esb.
In WSO2, the custom datasources monitoring via JMX is not yet available. This is fixed in current master branch and it will be available in future versions.
Please check the WSO2 Carbon JIRA: CARBON-15172.
For Tomcat, if you use JNDI datasources managed via Tomcat Container, you will be able to see the JNDI datasources via JMX. If you are using Tomcat JDBC Pool outside the container, you will have to register the JDBC Pool with JMX.
Related
How do I upload the API I created in WSO2 Integration Studio installed on my own computer to the WSO2 API Manager on the remote server.
From the Add new server menu, I clicked the WSO2 Remote Server option under WSO2 and entered the host and server URL information, but it did not publish. When I examined WSO2's own documents, I could not find detailed resources about connecting to a remote server and publishing.
Can you help with this?
Can you add your integration studio version and WSO2 Api Manager version?
You can try this documentation https://apim.docs.wso2.com/en/latest/integrate/develop/working-with-service-catalog/
You can register the service in the service catelog as below.
Start the WSO2 Micro Integrator pointing to API Manager.
You should have the carbon app of that particular service in the Micro Integrator.
When Micro Integrator starts it registers the available services in the API Manager.
From logging into the APIM publisher you can create an API.
Instructions are available here - https://apim.docs.wso2.com/en/latest/integrate/develop/working-with-service-catalog/
How to connect a server that run wso2 API manager to show statics on a server that run wso2 analytics that actually exist on differnt servers with different IP.
I am using version 3.2.0
You can follow the documentation and configure analytics for APIM 3.2.0.
In the configurations, instead of using localhost, use the IP address of the analytics server.
https://apim.docs.wso2.com/en/3.2.0/learn/analytics/configuring-apim-analytics/#configuring-apim-analytics
Every time the esb service is restarted, the logs previously running are refreshed. How do you keep the history?thank you
When we deploy the ESB in a VM it will not clear the wso2carbon logs with a server restart. Could you please elaborate on the server deployment. If you are using a container-based deployment you will need to mount the logs to an external directory to avoid this.
I am setting up a WSO2 docker. I am using the WSO2 Dockerfiles from github (https://github.com/wso2/docker-apim) an the latest WSO2 Api Manager version (2.10). The Installation has succeeded, so I started the docker container. WSO2 starts up and I was able to deploy a Swagger URL based API.
I am also able to access the API through the store interface. And here starts my trouble: When I am trying to test the API through the integrated Swagger UI, the API manager is making use of the internal docker IP:
I have set up this port configuration:
How can I force WSO2 Api Manager to use the Docker public IP?
Many thanks :-)
In the repository/conf/api-manager.xml you can find following element
APIGateway/Environments/Environment/GatewayEndpoint
If you have multiple gateways, you may want to create an HTTP(S) load balancer.
I have an app deployed to Cloudfoundry that I've exposed JMX MBeans interfaces for our logging levels. I'd like to connect to the cloudfoundry instances with jconsole. Is this possible? How do I make this happen? What if I'm running more than 1 instance of Tomcat, how do I connect to a specific instance? or does it matter?
There is currently no way to connect to once specific instance of an application or for that matter any port other than http port via the main Cloud Foundry router.
In the platform we use an app deployed alongside the Login and UAA components (https://github.com/cloudfoundry/identity-tools/tree/master/varz). It gives read-only access to selected MBeans through a CF-like REST interface. It is opinionated about the most important MBeans to expose and may break on complex object graphs, but you can adapt it if you want. You could rip out the controller and use it in your app or do the same as we do in the platform with a standalone app, deploying your own war and the varz in the same container.
Also see Jolokia for a generic JMX REST wrapper.