I can't launch wso2 micro-integrator 7.0.1. I launch files micro-integrator.sh or launcher_micro-integrator.sh or command wso2mi, after that i have strings in logs (look below), after that nothing, MI isn't loaded later. What is wrong? My Java_Home is correct. User who launches MI has all permissions on MI directory.
INFO {org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager} - Pass-through HTTP Listener started on 0.0.0.0:8290
INFO {org.apache.axis2.transport.mail.MailTransportListener} - MAILTO listener started
INFO {org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager} - Pass-through HTTPS Listener started on 0.0.0.0:8253
INFO {org.wso2.micro.integrator.initializer.StartupFinalizer} - WSO2 Micro Integrator started in 4 seconds
According to the below log, your Micro integrator has started successfully.
INFO {org.wso2.micro.integrator.initializer.StartupFinalizer} - WSO2 Micro Integrator started in 4 seconds
Micro integrator is starting in a very little time compared to the WSO2 Enterprise integrator and does not have the Mgt console capability of WSO2 Enterprise Integrator. However, you can access MI monitoring dashboard by referring to this doc.
Please check this quick start guide for more details on WSO2 Micro integrator.
Related
Enviroment:
Server Almalinux 8.7
java: java-11-openjdk-11.0.17.0.8-2.el8_6.x86_64
Micro integrator installed (4.1.0) Micro Integrator Dashboard installed (4.1.0)
The micro-integrator connects to the Dashboard, but when I try to login, the dashboard says "No running micro integrator instances found. Pls start a server a login":
The MI runs after the dashboard. The dashboard registers de MI as per below log line, but when I try to login it says that no MI is running....
New node dev_node_2 in group : mi_dev is registered. Inserting heartbeat information ERROR {LoginDelegate} - No running micro integrator instances found. Please start a server and login.
I verified the default "-DenableManagementApi=true" system parameter value in micro-integrator.sh.
What else can I do?
The MI node might not be registering its hostname properly. Along with the dashboard url, please try configuring MI's hostname and port as well.
[dashboard_config]
dashboard_url = "https://{hostname/ip}:{port}/dashboard/api/"
management_hostname = "<HOST_NAME>"
management_port = <PORT>
Enviroment:
1 Linux Serves
Micro integrator installed (4.1.0)
Micro Integrator Dashboard installed (4.1.0)
The micro-integrator connects to the Dashboard, but when I try to login, the dashboard says "No running micro integrator instances found. Pls start a server a login":
any help?
Thanks!
Daniel
I reviewed both deployment.toml files, and everything seems to be ok.
You need to configure the mi with the dashboard. This config needs to be added at each mi node.
[dashboard_config]
dashboard_url = "https://{hostname/ip}:{port}/dashboard/api/"
heartbeat_interval = 5
group_id = "mi_dev"
node_id = "dev_node_2"
More information can be found in here[1].
[1] - https://apim.docs.wso2.com/en/latest/observe/mi-observe/working-with-monitoring-dashboard/#step-2-configure-the-mi-servers
Make sure you start the MI dashboard first and after the dashboard is up and running start the MI server. Please verify the configs you have added with the configurations mentioned here[1].
[1] https://apim.docs.wso2.com/en/latest/observe/mi-observe/working-with-monitoring-dashboard/
I am trying to install and use the WSO2 API management in CentOS6. I was able to install and start the server but the management console page is not up in the browser.The url for console is also different than the localhost as below
[2016-02-02 16:56:53,465] INFO - StartupFinalizerServiceComponent WSO2 Carbon started in 33 sec
[2016-02-02 16:56:53,549] INFO - StatisticsServiceComponent BAM Service Stat Publishing is disabled
[2016-02-02 16:56:53,969] INFO - CarbonUIServiceComponent Mgt Console URL : https://172.17.42.1:9443/carbon/
[2016-02-02 16:56:53,970] INFO - CarbonUIServiceComponent API Publisher Default Context : http://172.17.42.1:9763/publisher
[2016-02-02 16:56:53,970] INFO - CarbonUIServiceComponent API Store Default Context : http://172.17.42.1:9763/store
[2016-02-02 16:56:54,244] INFO - DefaultKeyValidationHandler org.wso2.carbon.apimgt.keymgt.handlers.DefaultKeyValidationHandler Initialised
[2016-02-02 16:56:54,244] INFO - APIKeyValidationService Initialised KeyValidationHandler instance successfully
[2016-02-02 16:56:54,245] INFO - APIKeyMgtServiceComponent Setting default carbon host for thrift key management service: 172.17.42.1
[2016-02-02 16:56:54,267] INFO - APIKeyMgtServiceComponent Started thrift key mgt service at port:10397
The console here shows to have started at https://172.17.42.1:9443/carbon/ whereas the host is different in which the server is running.
Did you encounter any errors during the start up?
The reason for having a different host IP could be due to the availability of multiple network interfaces on your CentOS machine.
Also verify whether the relevant ports are opened on your CentOS6 instance. Ref.
I got the following error when runnning WSO2 API Manager 1.3.1 to use the WSO2 BAM Server 2.0.1.
TID: [0] [AM] [2013-05-02 18:58:40,609] ERROR
{org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageDataBridgeDataPublisher}
- Error initializing APIMgtUsageDataBridgeDataPublisher {org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageDataBridgeDataPublisher}
org.wso2.carbon.databridge.agent.thrift.exception.AgentException:
Error when finding event stream definition for :
org.wso2.apimgt.statistics.request 1.0.0
Both API Manager and BAM are running on the same machine and I changed offset to 1 in /home/jtao/api/wso2bam-2.0.1/repository/conf/carbon.xml based on Monetization of API Usage.
I also checked that BAM_HOME/repository/conf/etc/cassandra-component.xml doesn't exist in BAM 2.0.1. as someone suggested in the answer of another question "Configuring WSO2 API Manager to use the WSO2 BAM Server"
Any ideas?
I ran the same scenario described in guide and it works without any error. May be your have missed a part in the configuration guide? Make sure BAM_HOME is set correctly and BAM server is started before the AM server.
The following guide too can be used to integrate AM 1.3.1 with BAM 2.0.1
http://docs.wso2.org/wiki/display/AM131/Monitoring+and+Statistics
Ishara
I was trying to monitor jboss EAP 6.0/jboss AS 7 MBeans in WS02 BAM 2.2.0 using JMX Data Agent. I followed the tutorial to expose JBOSS MBeans, remotely in jconsole.
In WSO2 BAM while adding JMX Server Profile, I enter the URL:
service:jmx:remoting-jmx://{host_name}:{port}]
It says protocol is not supported. I suspect protocol remoting-jmx is not supported, where as in previous case, I see rmi protocol was supported. How can I import Remote JBOSS AS 7 MBean to WSO2 BAM 2.2.0 ?