I'm new to WSO2 and working on an existing application that uses WSO2.
We load our database of assets into wso2 but not all of the assets show up in the store or publisher when queried.
It seems there is some disconnect between what is in the database/carbon and what can be seen in store/publisher.
the missing assets can be found by:
Calling the database directly
looking them up in carbon
using the store or publisher url with the asset id
the governance rest api through id only
the assets are missing in:
doing searches in the store/publisher gui
doing searches with the governance api
All the ones missing have invalid asset names according to our rxt definitions. I removed these validations in carbon but still was not able to find them.
We have validations in the rxt files for asset names, would this affect what is seen in store/publisher?
Is there a way to sync up the governance registry with the database so that it would show all the assets in the store and publisher?
Any help is much appreciated!!
I'm facing the same problem with store/publisher. After searching for a solution, we found some info about this issue. WSO2 is not indexing some assets in Solr.
You could try to reindex the assets with this steps:
1 - Backup the solr folder which resides in /solr and remove from API Manager home location.
2 - Open /repository/conf/registry.xml
3 - Under indexingConfiguration tag there is a value called lastAccessTimeLocation.
Default value is
/_system/local/repository/components/org.wso2.carbon.registry/indexing/lastaccesstime
Change that value to
/_system/local/repository/components/org.wso2.carbon.registry/indexing/lastaccesstime1
4 - Restart the server
For me this didn't work, but in some questions here many people said that could be the best solution for this issue.
WSO2 loss APIs after changes in docker container
WSO2 API Manager issues with solr
After some long investigating, I found that some entries weren't in the REG_LOG table and some dates in the REG_LOG table made entries not be indexed. The solution for this was adding to the REG_LOG table with current timestamps which forced a reindex and then the missing assets were able to be searched for in the web ui.
Related
What is the recommended way to deploy changes (for example change in some Content Type model) from development to production without downtime?
I’m using this setup.
I have development instance with development postgres database.
On production I have 3 strapi instances (serving both api & admin, using the same production postgres database) and those instances are behind loadbalancer.
Lets say that I have Content Type named: Article (both on development and deployed on production).
Lets assume that I want to change that content type for example I want to add some fields and remove some fields in Article content type.
How to deploy changes to production without downtime?
I’ve done some tests and when I for example update Strapi Production Instance #1 to pull new code for updated models, strapi will update database of course. And from that time Strapi Production Instance #2 and #3 have problems serving Admin panel for example (javascript errors because database was changes but JS model files are not updated).
After I updated code on instance #2 and #3 everything works as expected.
But doing something like this on “working product” will be visible as downtime.
How to properly handle this situation? Thanks for help!
Could PM2 solve this problem? Strapi mentiones this in their documentation
PM2 Runtime allows you to keep your Strapi project alive and to reload it without downtime.
Strapi Docs v4
I want to get my Larvel project ready for deployment.
I already found some guides in the web, but no one of them could answer me the following question(s):
Which file do I have to upload to the webserver?
I already tried to remove as much folders/files as possible to keep the project-size on my apache webserver as small as possible. But is there any guide which tells me, which folders/files do i exactly need to exchange?
When it comes to an update:
Once deployed, which files do i need to update?
Do I have to upload all the files again or can I exchange only certain ones?
Currently i followed the official laravel guide and uploaded all files to the webserver.
Strapi is a powerful tool, but I am unable to find any documentation/instructions which explain about the best practices/strategy to migrate contents from one environment to another, for example Dev to staging to production ?
If you got a lot of content and recreate all the content on each environment is not viable.
Please guide, how to move API and DB (mongo) stuff.
If there is only manual workaround for now, we should document it so that can be used for now.
For now there is no other way than manually import/export your database:
Github issue: Import / export data
In Weblogic 10.3.5, is there any way to expire an html file from cache without going through a server restart. I am supporting a server with frequent HTML changes and hoping to find a way not to restart the server each time the HTML is updated. Environment is supporting a PeopleSoft domain. Thanks.
There's a way indeed, the parameter "Resource Reload Check (in seconds)" which can be found on a web app setup is what you're looking for. I've setup this to 5(secondes) in order to have a periodic refresh on dynamic ressources generated by an application engine (an xml parsed by an xslt)
For some details here's doc of 12.1.2 but I confirm it exists also on 10.3.4 (so on your version too) : https://docs.oracle.com/middleware/1212/wls/WLACH/pagehelp/J2EEwebappwebappconfigurationtitle.html
I've created a Web Matrix web site from the starter template which creates a database with the a few tables for the login details. Most of these are names webpages_Membership, webpages_Roles etc. The hosting company I use only gives me one database and I want to have more than one site on the server. I want to prefix the table name with something to make it unique, but it looks like the web matrix framework will only work with the set table name. Does anyone know if this is possible?
If you use SQL Server Compact Edition, you can have as many databases as you like in your App_Data folder. Certainly something to consider if your sites aren't likely to be hugely busy. Otherwise you can develop your own Provider inheriting from ExtendedMembershipProvider and make it "site-aware". Dig around in the WebMatrix.Data source code for more details (available as part of the MVC source download).