I use wso2 EI 6.1.1 installed as windows service with yajsw 11.03 like Installing as a Windows Service document:
https://docs.wso2.com/display/EI610/Installing+as+a+Windows+Service
. But I see a blank page when creating new in sequence in add proxy service menu or add api menu. My problem didn't solve with this config in wrraper.conf:
wrapper.java.additional.26 = -Dwso2.carbon.xml=${carbon_home}\\repository\\conf\\carbon.xml
wrapper.java.additional.27 = -Dwso2.registry.xml=${carbon_home}\\repository\\conf\\registry.xml
wrapper.java.additional.28 = -Dwso2.user.mgt.xml=${carbon_home}\\repository\\conf\\user-mgt.xml
wrapper.java.additional.29 = -Dwso2.transports.xml=${carbon_home}\\repository\\conf\\mgt-transports.xml
wrapper.java.additional.31 = -Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false wrapper.java.additional.33 = -Dfile.encoding=UTF8
I changed version of yajsw but wso2 EI don't install as windows service in other yajsw version. How can i solve this problem?
Related
I just installed WSO2 3.2.0 and Analytics 4.4.0 on the same machine using repositories on Debian 9.
Everything looks fine except the analytics Dashboard that I can't access for. According to the documentation here, I have to go on this url https://check.mydomain.com:9643/analytics-dashboard but all I got is this error :
Problem accessing: /analytics-dashboard. Reason: Not Found
I followed these steps to set up my domain name and enable analytics :
nano /usr/lib/wso2/wso2am/3.2.0/repository/conf/deployment.toml
[server]
hostname = "check.mydomain.com"
[apim.analytics]
enable = true
And I replaced every "localhost" string by ${server.hostname}
I followed these steps to start Analytics, API Manager and Dashboard :
service wso2sp-4.4.0-worker start
service wso2am-3.2.0 start
service wso2sp-4.4.0-dashboard start
Every service is fine regarding
service wso2sp-4.4.0-worker status
service wso2am-3.2.0 status
service wso2sp-4.4.0-dashboard status
Every other urls are working :
https://check.mydomain.com:9443/admin
https://check.mydomain.com:9443/carbon
https://check.mydomain.com:9443/devportal
https://check.mydomain.com:9443/publisher
Analytics is enabled and I can see subscription options on Publisher settings
Nothing happends on logs when I wisit https://check.mydomain.com:9643/analytics-dashboard
tail -f /usr/lib/wso2/wso2am/3.2.0/repository/logs/http_access_.2020-11-18.log
tail -f /usr/lib/wso2/wso2am/3.2.0/repository/logs/wso2carbon.log
tail -f /usr/lib/wso2/wso2sp/4.4.0/wso2/worker/logs/carbon.log
tail -f /usr/lib/wso2/wso2sp/4.4.0/wso2/dashboard/logs/carbon.log
Any help would be very appreciated, thanks.
You need to use wso2am analytics setup to configure analytics with the API manager. But I think now you are trying to use wso2 stream processor to configure the analytics and it's not supported with wso2am 3.2.
Follow the [1]documentation to download and set up the analytics.
You need to manually download the wso2am-analytics-3.2.0.zip.
if you follow the quick setup make sure wso2am-analytics-3.2.0 and wso2am folders locate in the same place. (since you installed apim via the apt installer you need to manually put anlytics setup in /usr/lib/wso2/wso2am/ folder and correctly set the path to API manager am_db in wso2am-analytics-3.2.0/conf/dashboard/deployment.yaml---> AM_DB -> jdbcUrl)
If you follow the standard setup no need to worry about the locations of wso2am pack and wso2am-analytics pack.
[1] https://apim.docs.wso2.com/en/latest/learn/analytics/configuring-apim-analytics/
How do I check which version of WSO2 API Manager I'm currently running in my RHEL 7 machine?
in the logs, you can check, when all the logs are loaded at the end it shows which version is of the API manager
\wso2am-3.0.0\bin>wso2server.bat --version
Result:
WSO2 API Manager v3.0.0
WSO2 Carbon Framework v4.5.1
The easiest way is to request it to the endpoint available for this porpouse and it is usually used for health checking:
curl -X GET https://localhost:9443/services/Version
Response:
<ns:getVersionResponse xmlns:ns="http://version.services.core.carbon.wso2.org">
<return>WSO2 API Manager-2.6.0</return>
</ns:getVersionResponse>
There is a version.txt file in the <AM_HOME>/bin directory. You can refer to this file as well.
this is my first question in Stackoverflow and i'm new in WSO2 ESB. I installed the 4.9.0 version of ESB and also installed Application Server feature on it. WSO2 ESB can not manage HttpSession. Can u help me please to solve this problem?
I already tried to change this parameter to true or false:
<session-config>
<session-timeout>30</session-timeout>
<cookie-config>
<secure>false</secure>
</cookie-config>
</session-config>
in ESB_HOME\repository\conf\tomcat\web.xml
Application server feature installed well i think. I can start my app and its working till i trying to use httpsession to manage users session and authentication.
Somebody had the same problem?
I am using WSO2 API Manager (1.8) and WSO2 BAM server(2.5.0) . I have done the
following configurations for getting statistics.
Configurations in :
https://github.com/Prasanthmv/Wso2/blob/master/configurations/all.doc
After that I started BAM and AM, but the following error appears :(I have
pushed the error in github):
AM error
BAM error
Why this error is showing, is my configuration
correct?
Here's documentation on how to set up API Manager / BAM integration: https://docs.wso2.com/display/AM180/Publishing+API+Runtime+Statistics
Alternatively, you can use WSO2 API Cloud (SaaS version of API Manager) in which everything is preconfigured and works out of the box.
According to the carbon logs, You must be using windows 7.
Therefore,
This could be due the BAM cannot execute cygwin commands. Please try to install Cywin into C drive and make sure no space in file path and append "C:\cygwin64\bin" to the windows PATH (using "Edit the system environment variables").
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 ?