I'm running WSO 5 components cluster (KeyManager, Gateway, Publisher, Store, Traffic Manager), each component has his own server and they are all exist in the same LAN.
Finally i got to a point where every component is running with no errors and i get this message below,
[2018-02-23 23:42:12,475] INFO - StartupFinalizerServiceComponent Server
: WSO2 API Manager-2.1.0
[2018-02-23 23:42:12,476] INFO - StartupFinalizerServiceComponent WSO2
Carbon started in 54 sec
[2018-02-23 23:42:12,720] INFO - CarbonUIServiceComponent Mgt Console URL
: https://172.31.25.234:9443/carbon/
[2018-02-23 23:42:12,720] INFO - CarbonUIServiceComponent API Publisher
DefaultContext : https://172.31.25.234:9443/publisher
[2018-02-23 23:42:12,720] INFO - CarbonUIServiceComponent API Store Default
Context : https://172.31.25.234:9443/store
wget -O- https://localhost:9443/publisher --no-check-certificate - give me the page and i can see its running locally, however , i cant reach the url from its external IP
Firewall disabled on CentOS. (firewall--cmd not exist)
I've tried also to use reverse proxy to my LAN publisher address:9443 but still no luck.
Appreciate your assistance.
Found the issue, although there is no firewall not sure why publisher ui management was not accessible from internet through port 9443
Finally i changed the port to 8080 on repository/conf/tomcat/catalina-server.xml and it worked.
Related
We are working on delivering a deployment of two WSO2 components - API Manager 3.0.0 and Identity Server 5.9.0 (which acts as Key Manager for APIM). For last few weeks everything worked fairly ok until today (or max few days ago) - suddenly we are getting following error when we try to log in to APIM Publisher:
ERROR {Jaggery service for token introspection} - {"data" : null, "xhr" : {}}
At same time publisher just keeps redirecting somewhere with an error message in the the browser logs:
Something went wrong while introspecting the token!!
Both components run on same virtual machine with offset for IS-as-KM set to 2. Datasources are OracleDB with full range of permissions for sake of testing.
Entire thing is handled using FQDN with wildcard certificate added to keystore.
Any idea about what this could be related to?
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.
I have change the carbon.xml, Offset 0 to 1
Server started with message:
[2017-08-03 11:51:56,169] INFO {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL : https://IP:9444/carbon/
But I am not able to access to Application server with the URL above
Issue have been resolved.
My LAN connection have blocked the port.
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 followed the same steps as mentioned in the WSO2 documentation for configuring BAM server and WSO2 AS. Both are in different computers. Still not able to solve the errors. Now I am getting new error when I click BAM EVENT_KS. My BAM server offset address is 0 by default. I changed my WSO2 AS offset to 2 in carbon.xml.
ERROR {org.wso2.carbon.databridge.agent.thrift.AsyncDataPublisher} - Error while connection to event receiver
org.wso2.carbon.databridge.agent.thrift.exception.AgentException: Cannot borrow client for TCP,203.252.180.178:9443,TCP,203.252.180.178:9543
at org.wso2.carbon.databridge.agent.thrift.internal.publisher.authenticator.AgentAuthenticator.connect(AgentAuthenticator.java:58)
and many more .....
Please help what will be the configuration problem with BAM. I tried all the latest 3 version.
Read [1] for configuration details. As I can see you have used ports 9443 and 9543 instead of 7611 or 7711 which are the correct Thrift server ports.
Use 7611 for unsecured port and 7711 for the secured port when no port offset is applied in BAM.
[1] http://docs.wso2.org/wiki/display/AS501/Collecting+Data+Statistics+of+Services