On Mon, May 6, 2013 at 12:27 PM, Sanjeewa Malalgoda <[email protected]>wrote:
> Hi kishanthan, > Some of API manager users deploy API xml file manually to gateway file > system(they synch up publisher node synapse config with gateway manually). > This may be problem in that case. But i think once first request hits > everything should work as expected. > Yes, then this should not be an issue. Kishanthan. > > Thanks, > Sanjeewa, > > > On Mon, May 6, 2013 at 11:53 AM, Kishanthan Thangarajah < > [email protected]> wrote: > >> >> >> >> On Mon, May 6, 2013 at 8:47 AM, Nuwan Dias <[email protected]> wrote: >> >>> On Sun, May 5, 2013 at 11:47 PM, Kishanthan Thangarajah < >>> [email protected]> wrote: >>> >>>> >>>> >>>> >>>> On Fri, May 3, 2013 at 10:40 AM, Nuwan Dias <[email protected]> wrote: >>>> >>>>> On Fri, May 3, 2013 at 10:32 AM, Kishanthan Thangarajah < >>>>> [email protected]> wrote: >>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Thu, May 2, 2013 at 8:23 PM, Nuwan Dias <[email protected]> wrote: >>>>>> >>>>>>> On Wed, Apr 3, 2013 at 2:32 PM, Kishanthan Thangarajah < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Apr 3, 2013 at 1:48 PM, Sanjeewa Malalgoda < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Hi Kishanthan, >>>>>>>>> Just found that we are not supporting hot update(synch up >>>>>>>>> artifacts with file system changes) for tenants. Is this bug or >>>>>>>>> expected behavior? >>>>>>>>> >>>>>>>> >>>>>>>> No, it works. I just tried this (hot update) for a tenant on ESB >>>>>>>> 4.6.0. >>>>>>>> >>>>>>> >>>>>>> Hot update does not seem to work for tenants. I tried to update a >>>>>>> tenant synapse-artifact on an API Manager pack built on platform 4.1.2. >>>>>>> >>>>>> >>>>>> Where can I find the latest packs? What are the artifacts you are >>>>>> trying update here? >>>>>> >>>>> >>>>> A pack can be found from [1]. To reproduce this, create a tenant >>>>> admin. Login to the publisher and create an API and change its lifecycle >>>>> to >>>>> Published. The Synapse API will now be deployed to the tenants space. Now >>>>> edit this API (put a log mediator) and monitor the console. The changes >>>>> will not be reflected. >>>>> >>>> >>>> I just tried the hotupdate functionality with the pack from the given >>>> location. It seems to work fine. >>>> >>>> Here are the steps I followed. >>>> >>>> 1. Created a new tenant. >>>> 2. Logged into the publisher as tenant and created an API. >>>> 3. Changed the life-cycle state to published. Observed the following >>>> logs. >>>> >>>> [2013-05-05 23:32:29,359] INFO - Axis2SynapseController Deploying the >>>> Synapse service... >>>> [2013-05-05 23:32:29,359] INFO - Axis2SynapseController Deploying >>>> Proxy services... >>>> [2013-05-05 23:32:29,360] INFO - Axis2SynapseController Deploying >>>> EventSources... >>>> [2013-05-05 23:32:29,361] INFO - ServerManager Server ready for >>>> processing... >>>> [2013-05-05 23:32:29,365] WARN - MediationStatisticsServiceComponent >>>> Couldn't find the mediation statistics store for tenant id: 1 >>>> [2013-05-05 23:32:29,377] INFO - TenantAxisUtils Loaded tenant >>>> kicha.org in 502 ms >>>> [2013-05-05 23:32:29,413] INFO - API Initializing API: >>>> kicha-AT-kicha.org--api1 >>>> >>>> 4. Then did a change to the api xml file via file system. Observed the >>>> following update logs. >>>> [2013-05-05 23:33:14,041] INFO - API Initializing API: >>>> kicha-AT-kicha.org--api1 >>>> [2013-05-05 23:33:14,043] INFO - APIDeployer API: >>>> kicha-AT-kicha.org--api1:v1.0.0 has been updated from the file: >>>> /home/kicha/wso2/dist/am/wso2am-1.4.0/repository/tenants/1/synapse-configs/default/api/kicha-AT-kicha.org--api1_v1.0.0.xml >>>> >>>> 5. Also tried to update via the source view, then also it worked fine. >>>> >>>> Anything else should I need to consider? >>>> >>> >>> Maybe this occurs intermittently. I also had super tenant artifacts >>> deployed at the time I tried this. Can you check that case as well? This >>> issue was reported by the QA guys as well. >>> >> >> >> I think I know the issue here. Say that you created a tenant and added an >> API. Then you restarted the server or the tenant got unloaded. Now you >> login to the publisher as the tenant. Note that action this will not load >> the tenant into the system. Now if you do any changes to the api xml via >> file system, it will not get reflected, because the tenant's >> configurationContext is not yet loaded. If you do any change to the API >> (say you changed the life-cycle state), then the tanant gets loaded and the >> changes will get reflected. >> >> This is the normal behavior of all the carbon servers as-well. If the >> tenant is not loaded, file system changes related to the tenant, will have >> no effect until the tenant is loaded. >> >> Then my question would be, in the API Manger case, why are you trying do >> changes via file system? >> >> Kishanthan. >> >>> >>> Thanks, >>> NuwanD. >>> >>>> >>>> Thanks, >>>> Kishanthan. >>>> >>>> >>>> >>>>> [1] - http://builder3.us1.wso2.org/builds/02-May-2013/ >>>>> >>>>>> >>>>>> >>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> Thanks. >>>>>>>>> Sanjeewa. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Apr 3, 2013 at 1:22 PM, Nuwan Dias <[email protected]>wrote: >>>>>>>>> >>>>>>>>>> On Wed, Apr 3, 2013 at 12:50 PM, Kishanthan Thangarajah < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Nuwan, >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Tue, Apr 2, 2013 at 9:10 PM, Nuwan Dias <[email protected]>wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi, >>>>>>>>>>>> >>>>>>>>>>>> In any multi-tenanted carbon server, the tenant specific >>>>>>>>>>>> deployment directory structure (Ex: >>>>>>>>>>>> repository/tenants/1/axis2services) is >>>>>>>>>>>> always created when the tenant tries to deploy an artifact for the >>>>>>>>>>>> first >>>>>>>>>>>> time. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> They get created on first access to the tenant (mgt-console >>>>>>>>>>> login, request to some artifact, etc). This is where the >>>>>>>>>>> axisConfiguration >>>>>>>>>>> for that tenant gets created and during that time only, those >>>>>>>>>>> dir-structure gets created. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> Is there any possibility of having an extension hook for the >>>>>>>>>>>> deployment directory structure creation so that it could be used >>>>>>>>>>>> to deploy >>>>>>>>>>>> custom artifacts under a chosen directory structure? >>>>>>>>>>>> >>>>>>>>>>>> My use case is that I need to deploy a custom set of sequences >>>>>>>>>>>> under each tenant's synapse-configs/default/sequences directory. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Is the requirement is to deploy those sequences into relevant >>>>>>>>>>> tenants repo, when the tenant being loaded for the first time? >>>>>>>>>>> >>>>>>>>>> Yes. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> What I mean is, before any request is received by the tenant, >>>>>>>>>>> you want to have those artifacts deployed there? >>>>>>>>>>> >>>>>>>>>> No, it is sufficient to have these artifacts created when the >>>>>>>>>> tenant receives its first request. What I am looking for is a method >>>>>>>>>> to >>>>>>>>>> deploy a set of custom sequences per-tenant. If you look at the >>>>>>>>>> synapse-configs/default/sequences directory of the tenant, you will >>>>>>>>>> see >>>>>>>>>> that a fault.xml and main.xml files are created. I want to add a few >>>>>>>>>> more >>>>>>>>>> sequences and override the default fault.xml >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Thanks, >>>>>>>>>>> Kishanthan >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Thanks, >>>>>>>>>>>> NuwanD. >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Nuwan Dias >>>>>>>>>>>> >>>>>>>>>>>> Software Engineer - WSO2, Inc. http://wso2.com >>>>>>>>>>>> email : [email protected] >>>>>>>>>>>> Phone : +94 777 775 729 >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Dev mailing list >>>>>>>>>>>> [email protected] >>>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> *Kishanthan Thangarajah* >>>>>>>>>>> Software Engineer, >>>>>>>>>>> Development Technologies Team, >>>>>>>>>>> WSO2, Inc. >>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>> >>>>>>>>>>> Mobile - +94773426635 >>>>>>>>>>> Blog - *http://kishanthan.wordpress.com* >>>>>>>>>>> Twitter - *http://twitter.com/kishanthan* >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Nuwan Dias >>>>>>>>>> >>>>>>>>>> Software Engineer - WSO2, Inc. http://wso2.com >>>>>>>>>> email : [email protected] >>>>>>>>>> Phone : +94 777 775 729 >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Dev mailing list >>>>>>>>>> [email protected] >>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> *Sanjeewa Malalgoda* >>>>>>>>> WSO2 Inc. >>>>>>>>> Mobile : +14084122175 | +94713068779 >>>>>>>>> >>>>>>>>> <http://sanjeewamalalgoda.blogspot.com/>blog >>>>>>>>> :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> *Kishanthan Thangarajah* >>>>>>>> Software Engineer, >>>>>>>> Development Technologies Team, >>>>>>>> WSO2, Inc. >>>>>>>> lean.enterprise.middleware >>>>>>>> >>>>>>>> Mobile - +94773426635 >>>>>>>> Blog - *http://kishanthan.wordpress.com* >>>>>>>> Twitter - *http://twitter.com/kishanthan* >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Nuwan Dias >>>>>>> >>>>>>> Member, Management Committee - Solutions Technology Group >>>>>>> >>>>>>> Software Engineer - WSO2, Inc. http://wso2.com >>>>>>> email : [email protected] >>>>>>> Phone : +94 777 775 729 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Kishanthan Thangarajah* >>>>>> Software Engineer, >>>>>> Development Technologies Team, >>>>>> WSO2, Inc. >>>>>> lean.enterprise.middleware >>>>>> >>>>>> Mobile - +94773426635 >>>>>> Blog - *http://kishanthan.wordpress.com* >>>>>> Twitter - *http://twitter.com/kishanthan* >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Nuwan Dias >>>>> >>>>> Member, Management Committee - Solutions Technology Group >>>>> Software Engineer - WSO2, Inc. http://wso2.com >>>>> email : [email protected] >>>>> Phone : +94 777 775 729 >>>>> >>>> >>>> >>>> >>>> -- >>>> *Kishanthan Thangarajah* >>>> Software Engineer, >>>> Development Technologies Team, >>>> WSO2, Inc. >>>> lean.enterprise.middleware >>>> >>>> Mobile - +94773426635 >>>> Blog - *http://kishanthan.wordpress.com* >>>> Twitter - *http://twitter.com/kishanthan* >>>> >>> >>> >>> >>> -- >>> Nuwan Dias >>> >>> Member, Management Committee - Solutions Technology Group >>> Software Engineer - WSO2, Inc. http://wso2.com >>> email : [email protected] >>> Phone : +94 777 775 729 >>> >> >> >> >> -- >> *Kishanthan Thangarajah* >> Software Engineer, >> Development Technologies Team, >> WSO2, Inc. >> lean.enterprise.middleware >> >> Mobile - +94773426635 >> Blog - *http://kishanthan.wordpress.com* >> Twitter - *http://twitter.com/kishanthan* >> > > > > -- > *Sanjeewa Malalgoda* > WSO2 Inc. > Mobile : +14084122175 | +94713068779 > > <http://sanjeewamalalgoda.blogspot.com/>blog > :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/> > -- *Kishanthan Thangarajah* Software Engineer, Development Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
