I'm facing some data purging issues with the WSO2 Analytics. There's this folder on ${WSO2_HOME}/repository/data that keeps growing and I'm not able to purge it through the WSO2 Analytics. Databases are being purged properly but this folder keeps growing and crashing the service as my server can't handle more data.
I've tried setting up as the doc says. And I'm still having this issue.
Does somebody have any idea or can confirm that setting up the conf with the link above should resolve this issue?
Thank you all for your responses.
Related
When I am trying to create a new API in WSO2 API Manager 3.2.0, I am getting the below error and the API doesn't get created.
But, on restarting the server, the API gets created. But I do keep facing the above issue frequently and restarting the server resolves it. Wanted to know what could be causing this issue? Also is it like I am missing out on some configurations and there is some permanent fix?
Community, appreciate your suggestions.
I have a UAT ENVIRONMENT where I am using NServiceBUS endpoints. Everything works. Then when we moved to Production, the method we used to make the environment was to make an IMAGE of the UAT server and restore on a new AWS server instance
We reinstalled RAVENDB but on Windows authentication page in manage server, we are seeing the authentication from the old server. I have removed the RavenSITE folder and uninstalled RavenDB, restarted the server and tried installing again, but the old authentication line items are still coming up. Where are these getting stored? So I can go delete them.
The endpoints are also not registering with the instance and the databases are not getting created for each endpoint
Please assist!
These are stored in the System database.
I am working on Tealium integration with Sitecore and I have installed Tealium Tag Manager Sitecore connector, as well as I have aslo done all the configuration which is needed to use Tealium.
After enabling Google Analytics service from Tealium my website keep loading.
Does anyone have any experience with Sitecore Tealium Connector?
Any help would be appreciated!
I had also faced the same issue.
In my Scenario it was a network proxy issue and i tried the same thing in open network and it worked for me.
Please check your network settings if there is any proxy.
I'm new to WSO2 products and I was trying to set up the API statistics by configuring APIM with BAM as said in this documentation for publishing the stats https://docs.wso2.com/display/AM170/Publishing+API+Runtime+Statistics#PublishingAPIRuntimeStatistics-point3.
However every time I try to configure the statistics, start BAM, and re-start APIM I always get an error on the APIM console "Error occured while getting API's".
What does this mean?
Does it mean I have to configure first APIM and BAM before I can make an API and check it's statistics?
I don't get it why following the manual results into something like an error. Is there something wrong with my configuration?
here are few ways to debug whats going wrong. How API-M and BAM integration works is that
API -> publish stats to BAM
BAM stores the stats in Cassandra
BAM uses Hive scripts to analyse the data and write the results to a RDBMS mentioned in master-datasources.xml
I would recommend you to check the number 2. by checking if stats are published to BAM. You can do this by login into the management console of BAM and going to the Analytic section and adding the following script
select * from APIRequestData;
Execute this script and see if any data is returned. If no data is returned then data is not correctly published from API-M to BAM. If data is available here then there is an issue in reading the data from RDBMS to API-M.
I recommend you check the master-datasources.xml file which you edited during configuration. There may be an issue there, if the API Manager cannot connect to its' own database. The datasources given in step 2 of the guide you used are in addition to the existing datasources. If this isn't it, then please provide a stack dump or more detailed error messages. Cheers.
I follow the guide Governance Partition in a Remote Registry found in WSO2 Documentaton. It seems to work fine but I am facing a strange problem. Let me explain my setup first.
Governance registry instalation
Installed GREG 4.5.3
Set the offset to 1 in order to GREG console mgmt runs on port 9444 (carbon.xml)
Create mysql database "wso2greg_reg" (for local/config/governance registry)
Updated datasource WSO2_CARBON_DB to point to wso2greg_reg database (master-datasources.xml)
Enabled clustering (axis2.xml)
Run GREG server with -Dsetup option in order to create all tables
Enterprise Service Bus instalation
Installed ESB 4.6.0
Set the offset to 2 in order to ESB console mgmt runs on port 9445 (carbon.xml)
Create mysql database "wso2esb_reg" (for local/config registry)
Updated datasource WSO2_CARBON_DB to point to wso2esb_reg database (master-datasources.xml)
Added datasource WSO2_GREG_DB to point to wso2greg_reg database (master-datasources.xml)
Enabled clustering (axis2.xml)
Set registry.xml to mount governance registry using wso2greg_reg database
Run ESB server with -Dsetup option in order to create all tables
My problem is happening when I start the two servers, dependening on which was the first server started I have diferent problems on the console managmenet of the secondly started server.
First case:
I start GREG first and ESB in second. When navigating to ESB Console MGMT, I am unable to add a new Pass Through Proxy, the respetive form is not showing and exceptions are logged to the ESB logs (see logs).
Second case:
I start ESB first and GREG in second. When navigating to GREG Console MGMT, the metadata menu is empty and exceptions are loged to the GREG logs (see logs)
Can someone point me to what I am doing wrong?
You need to create only one mysql database. It is this database that is used in the master-datasources.xml config for both G-Reg and ESB instances. What happens is, the mysql database is used as the central database.
Pls try this out and check if you still encounter the issues mentioned.
Cheers,
Gillian