On Fri, Feb 27, 2015 at 10:25 AM, Ajith Vitharana <[email protected]> wrote:
> > > On Thu, Feb 26, 2015 at 11:37 PM, Sanjeewa Malalgoda <[email protected]> > wrote: > >> >> >> On Fri, Feb 27, 2015 at 3:29 AM, Ajith Vitharana <[email protected]> wrote: >> >>> >>> >>> On Thu, Feb 26, 2015 at 4:17 PM, Prabath Siriwardena <[email protected]> >>> wrote: >>> >>>> Yes.. but blocking wont allow you to delete it.. >>>> >>> >>> Yes. Currently no clean approach to delete it. >>> >>> But this is a workaround: >>> >>> 1. Change the LC sate to BLOCKED . >>> 2. Logged in to the Carbon Admin UI >>> 3. Home -> Metadata -> List -> APIs and delete that API, then API >>> will disappear from publisher. >>> >> This is completely wrong. We should never recommend this to anyone. API >> store may completely unusable due to this[1]. >> >> [1] >> http://sanjeewamalalgoda.blogspot.com/2014/03/how-to-fix-issue-in-wso2-api-manager.html >> >> > > It is not not completely wrong to delete *the API having > subscriptions* :). Only thing is 4th and 5th steps is missing . > > 4.) Find the API data from AM database and delete. > 5.) Go to > the wso2am-1.8.0/repository/deployment/server/synapse-configs/default/api > and delete the API artifact. > No still this is missing some steps. How about resource mapping associate with API? You cant simply find entries in all tables associate with API and delete them(see following list). That is why we do not recommend it. Hope you got it now :) String deleteLCEventQuery = "DELETE FROM AM_API_LC_EVENT WHERE API_ID=? "; String deleteCommentQuery = "DELETE FROM AM_API_COMMENTS WHERE API_ID=? "; String deleteRatingsQuery = "DELETE FROM AM_API_RATINGS WHERE API_ID=? "; String deleteSubscriptionQuery = "DELETE FROM AM_SUBSCRIPTION WHERE API_ID=?"; String deleteExternalAPIStoresQuery = "DELETE FROM AM_EXTERNAL_STORES WHERE API_ID=?"; String deleteAPIQuery = "DELETE FROM AM_API WHERE API_PROVIDER=? AND API_NAME=? AND API_VERSION=? "; String deleteURLTemplateQuery = "DELETE FROM AM_API_URL_MAPPING WHERE API_ID = ?"; Thanks, sanjeewa. > > Your blog post described *how to recover an API*, But what I have > mentioned here is *how to delete an API which is having user > subscriptions*(without removing subscriptions one by one from store). > Hope it is clear now. Am I missed anything ? > > -Ajith > >> >> Thanks, >> sanjeewa. >> >>> >>> Only problem is publisher doesn't allow you again to create API with >>> same name and context. Because when you delete the API from Admin UI, it >>> only delete the API from registry database and AM database still remain the >>> AM metadata(name, context ...etc). >>> >>> -Ajith >>> >>> >>>> >>>> Thanks & regards, >>>> -Prabath >>>> >>>> >>>> On Thu, Feb 26, 2015 at 1:15 PM, Ajith Vitharana <[email protected]> >>>> wrote: >>>> >>>>> >>>>> >>>>> On Thu, Feb 26, 2015 at 4:04 PM, Prabath Siriwardena <[email protected] >>>>> > wrote: >>>>> >>>>>> Thanks..! But who has to remove the subscriptions...? Is it the one >>>>>> who subscribed..? >>>>>> >>>>> >>>>> Currently yes. But I understand that , it is not possible when we >>>>> have lots of user subscriptions. >>>>> >>>>> >>>>>> I think there needs to be a way to remove an API by the API >>>>>> Publisher... >>>>>> >>>>> >>>>> So, without deleting the the API we can make the LC state to BLOCKED >>>>> in publisher. >>>>> >>>>> -Ajith >>>>> >>>>> >>>>>> >>>>>> Thanks & regards, >>>>>> -Prabath >>>>>> >>>>>> On Thu, Feb 26, 2015 at 1:00 PM, Ajith Vitharana <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> >>>>>>> Hi Prabath, >>>>>>> >>>>>>> AFAIK, It can't do from publisher, first we need to remove the >>>>>>> subscription from store , then delete from publisher. >>>>>>> >>>>>>> -Ajith >>>>>>> >>>>>>> On Thu, Feb 26, 2015 at 3:55 PM, Prabath Siriwardena < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> $subject... >>>>>>>> >>>>>>>> >>>>>>>> Thanks & Regards, >>>>>>>> Prabath >>>>>>>> >>>>>>>> Twitter : @prabath >>>>>>>> LinkedIn : http://www.linkedin.com/in/prabathsiriwardena >>>>>>>> >>>>>>>> Mobile : +1 650 625 7950 >>>>>>>> >>>>>>>> http://blog.facilelogin.com >>>>>>>> http://blog.api-security.org >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Dev mailing list >>>>>>>> [email protected] >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Ajith Vitharana. >>>>>>> WSO2 Inc. - http://wso2.org >>>>>>> Email : [email protected] >>>>>>> Mobile : +1-812-360-5335 >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Thanks & Regards, >>>>>> Prabath >>>>>> >>>>>> Twitter : @prabath >>>>>> LinkedIn : http://www.linkedin.com/in/prabathsiriwardena >>>>>> >>>>>> Mobile : +1 650 625 7950 >>>>>> >>>>>> http://blog.facilelogin.com >>>>>> http://blog.api-security.org >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Ajith Vitharana. >>>>> WSO2 Inc. - http://wso2.org >>>>> Email : [email protected] >>>>> Mobile : +1-812-360-5335 >>>>> >>>>> >>>> >>>> >>>> -- >>>> Thanks & Regards, >>>> Prabath >>>> >>>> Twitter : @prabath >>>> LinkedIn : http://www.linkedin.com/in/prabathsiriwardena >>>> >>>> Mobile : +1 650 625 7950 >>>> >>>> http://blog.facilelogin.com >>>> http://blog.api-security.org >>>> >>> >>> >>> >>> -- >>> Ajith Vitharana. >>> WSO2 Inc. - http://wso2.org >>> Email : [email protected] >>> Mobile : +1-812-360-5335 >>> >>> >> >> >> -- >> >> *Sanjeewa Malalgoda* >> WSO2 Inc. >> Mobile : +94713068779 >> >> <http://sanjeewamalalgoda.blogspot.com/>blog >> :http://sanjeewamalalgoda.blogspot.com/ >> <http://sanjeewamalalgoda.blogspot.com/> >> >> >> > > > -- > Ajith Vitharana. > WSO2 Inc. - http://wso2.org > Email : [email protected] > Mobile : +1-812-360-5335 > > -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 <http://sanjeewamalalgoda.blogspot.com/>blog :http://sanjeewamalalgoda.blogspot.com/ <http://sanjeewamalalgoda.blogspot.com/>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
