I have installed WSO2 CEP on Linux. But when I tried to open the management console with the https:///carbon/, it says "The website is not available."
I have the WSO2 CEP running (and it said WSO2 Carbon started in 19 sec).
Is this because I didn't install the CEP properly?
Please help. I am new to the WSO2..
If you started the WSO2 CEP or any other WSO2 products properly, then you can see the management console in
https://localhost:9443/
With the default configuration all the WSO2 products works in 9443 port. For more information regarding the WSO2 CEP please refer the [1].
[1] http://docs.wso2.org/wiki/display/CEP210/Complex+Event+Processor+Documentation
Regards,
Mohan
Start the server using the command
sh wso2server.sh
Then when the server start proccess completed, on your browser
https://localhost:9443/carbon
may be you may got https certification error proceed no mater.
Enjoy
Related
Something similar is happening to me. I'm quite new in WSO2 world.
On the same server I have installed:
wso2am-4.1.0 --> API Manager executed as linux service (api-manager.sh) wso2ei-7.1.0 --> Micro Integrator and dashboard , both exec. as linux services. MI is the last one to load.
I'm not using the embedded micro-integration of the API Mgr due it hasn't got any dataservice features (and I don't know how to enable them, by the way..)
Under Micro Integrator (wso2ei-7.1.0)'s conf/deployment.toml file, I have this section:
[[service_catalog]]
apim_host = "https://localhost:9443"
enable = true
username = "xxxxxxxx"
password = "xxxxxxxx"
BUT,no integrated service published to the service catalog. ALSO, under Micro Integrator's LOG I didn't see any statement like : "Succesfully updated the Service Catalog" nor error msg..
Any help? Thanks in advance! Daniel
I tried changing the conf file settings, service url, etc..
The service catalog feature is only available in MI 4.x versions.
You can manually create the API in the API Manager by importing the OpenAPI(Swagger) definition.
In order to use API Manager's Service Catalog feature, both API Manager and Micro-integrator should be on the same version.
You need to use Micro-integrator 4.1.0 along with API Manager 4.1.0 to use this capability.
I am running WSO2 APIM 3.2.0 and Analytics 3.2.0 on different client servers. I did all the required settings to configure WSO2 APIM with WSO2 Analytics. Started both the servers successfully and WSO2 APIM URL's open well. But, when I open the Analytics Dashboard URL (https://<Analytics_Host>:9643/analytics-dashboard/login), I get the below warning in the dashboard server logs, and the login page does not appear. Only a blank screen appears.
WARN {org.wso2.msf4j.internal.MSF4JHttpConnectorListener} - Unmapped
exception feign.RetryableException: No subject alternative names
matching IP address <APIM_IP> found executing GET
https://<APIM_Host>:9443/api/am/admin/v0.16/custom-urls/carbon.super
In the browser console I can see errors as shown in the below screenshot.
One more thing I noticed is in the management console of WSO2 APIM, difference in Service Providers list when compared with my local. I didn't find all the service providers on the client server which I can see on my local.
WSO2 APIM Carbon Console Service Providers list on my local:
WSO2 APIM Carbon Console list on the client server:
Am I missing out on some configurations? Need suggestions on this issue.
I'm trying to use WSO2 ESB 5.0.0 with WSO2 ESB Analytics on my local machine (ubuntu 14.04). I have created an API using wso2 development studio and deployed it to WSO2 server. While running both WSO2 server and analytics server on my local machine, the newly created API was called through PostMan. I'm getting correct response, but I can see following error on WSO2 ESB console.
Exception in thread "message-flow-reporter-0-tenant--1234" java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:3332)
at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:137)
at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:121)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:622)
at java.lang.StringBuilder.append(StringBuilder.java:202)
at java.util.AbstractMap.toString(AbstractMap.java:539)
at org.apache.synapse.aspects.flow.statistics.publishing.PublishingEvent.getObjectAsList(PublishingEvent.java:274)
at org.apache.synapse.aspects.flow.statistics.publishing.PublishingFlow.addEvent(PublishingFlow.java:43)
at org.apache.synapse.aspects.flow.statistics.util.TracingDataCollectionHelper.createPublishingFlow(TracingDataCollectionHelper.java:170)
at org.wso2.carbon.das.messageflow.data.publisher.services.MessageFlowReporterThread.processAndPublishEventList(MessageFlowReporterThread.java:225)
at org.wso2.carbon.das.messageflow.data.publisher.services.MessageFlowReporterThread.run(MessageFlowReporterThread.java:95)
When analytics server is stopped, I'm not getting that error. After getting this error, analytics server will not update with any statistics until next server restart.
Does anyone know why I'm getting this kind of error?
I'm using WSO2 API MANAGER VERSION 1.10.0
Sample API published with script description in publisher portal
and i open the api detail in store portal
setting carbon.xml is below
<XSSPreventionConfig>
<Enabled>true</Enabled>
<Rule>allow</Rule>
<!--Patterns>
<Pattern></Pattern>
</Patterns-->
</XSSPreventionConfig>
How can I solve it with setting?
You can download security patches for APIM 1.10.0 from here. This is already fixed in them.
After installing (https://docs.wso2.com/display/DAS301/Installing+as+a+Windows+Service) and starting WSO2 DAS 3.0.1 as a windows service, there is an exception when opening page of view roles from users page as below,
Then popup blank page,
However, this error does not happen if I use wso2server.bat running in command console. The same issue happens to WSO2 AM 1.10.0 as well.
Cheers,
Sean
Try adding below line to wrapper.conf
wrapper.java.additional.26 = -Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false
This is mentioned in Identity Server Docs. I reopened a WSO2 Document JIRA about this.