Hi Chamila
As i understand regarding APIMANAGER-2662
<https://wso2.org/jira/browse/APIMANAGER-2662> following are the two
workarounds.
1. As mentioned in the readme.txt., edit *each* api xml in the
APIM_1.7.0/repository/deployment/server/synapse-config/default/api
directory.
Replace
<handler
class="org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler"/>
with
<handler
class="org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler">
<property name="configKey"
value="gov:/apimgt/statistics/ga-config.xml"/>
</handler>
2. Manually go to implement tab in the edit mode of *each* of the APIs and
click manage
If a customer wants to migrate hundreds of APIs, is it a feasible solution
from the customer's perspective? Ideally when a customer migrates from an
older version, they should be able to work with their data as they worked
before the migration. Since invoking an API is the core functionality of
API Manager, is it really feasible in asking the customer to follow above
1st or 2nd method?
>From the customer/user perspective above given solution cannot be accepted.
In my opinion this should be handled by our side without asking the
customer/user to take extra effort in bringing his migrated data to work
properly.
Thank You
Erandi
On Mon, Aug 18, 2014 at 11:40 AM, Chamila Adhikarinayake <chami...@wso2.com>
wrote:
> Hi Chathurika,
>
> Issues mentioned in the previous mail are fixed in the latest 17/08/2014
> pack[1]. There are some updates done to the migration tool readme.txt file
> as well. You can proceed with the migration testing. For the issue
> APIMANAGER-2662 <https://wso2.org/jira/browse/APIMANAGER-2662> please
> read the comments in the jira (these instructions are added to the
> readme.txt).
>
> [1] https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/
> Thanks,
> Chamila.
>
>
> On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva <chathuri...@wso2.com
> > wrote:
>
>> Hi All
>>
>> As per the pack released on 05/08/2014 following is the status
>>
>> 1. APIMANAGER-2662 <https://wso2.org/jira/browse/APIMANAGER-2662> -
>> issue status - inprogress. This is the main scenario of the migration. Thus
>> the fix for this is crucial to proceed with the proper user scenario based
>> testing
>> 2. APIMANAGER-2698 <https://wso2.org/jira/browse/APIMANAGER-2698> -
>> issue status - reopened. This issue corrupts the entire database.
>> 3. APIMANAGER-2669 <https://wso2.org/jira/browse/APIMANAGER-2669> -
>> issue status - reopened. The resources added before the migration is not
>> copied correctly
>> 3. APIMANAGER-2672 <https://wso2.org/jira/browse/APIMANAGER-2672> -
>> issue status - reopened (due to APIMANAGER-2669
>> <https://wso2.org/jira/browse/APIMANAGER-2669>) . This issue cannot be
>> verified until APIMANAGER-2698
>> <https://wso2.org/jira/browse/APIMANAGER-2698> is fixed.
>>
>> Since the above mentioned issues are blocking, the migration testing
>> cannot be proceeded for the 05/08/2014 pack
>>
>> Thank You
>>
>>
>> On Mon, Aug 11, 2014 at 2:26 PM, Uvindra Dias Jayasinha <uvin...@wso2.com
>> > wrote:
>>
>>> The ticket has been resolved, please continue with testing
>>>
>>>
>>> On 11 August 2014 12:49, Uvindra Dias Jayasinha <uvin...@wso2.com>
>>> wrote:
>>>
>>>> Seems the stack trace is different from what was originally reported
>>>> for this ticket, can we have a closer look at this? Please ping me when you
>>>> get back to your seat. Thanks
>>>>
>>>>
>>>> On 11 August 2014 12:30, Chathurika De Silva <chathuri...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> We started to test the migration with the 05/08/2014 pack and
>>>>> APIMANAGER-2529 is reopened. This is currently blocking the testing
>>>>>
>>>>> Thank You
>>>>>
>>>>>
>>>>> On Tue, Aug 5, 2014 at 10:26 AM, Chalitha Waldeniyage <
>>>>> chali...@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> We have covered entire cycle of testing with 29th pack.But untill we
>>>>>> get the above mentioned issues fixed,we cannot proceed with migration
>>>>>> testing in API Manager 1.7.1 further.
>>>>>>
>>>>>> Thank you
>>>>>>
>>>>>>
>>>>>> On Fri, Aug 1, 2014 at 6:10 PM, Chathurika De Silva <
>>>>>> chathuri...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi All
>>>>>>>
>>>>>>> As of today (01.08.2014) the migration test is being done with the
>>>>>>> API Manager pack (29/07/2014)
>>>>>>>
>>>>>>> The issue APIMANAGER-2559 is now fixed and thus closed after
>>>>>>> verifying in the above mentioned pack.
>>>>>>>
>>>>>>> Furthermore a smoke test was done in the windows environment for the
>>>>>>> migration as well as for basic API Manager scenarios.
>>>>>>>
>>>>>>> Thank You
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Jul 31, 2014 at 6:09 PM, Chathurika De Silva <
>>>>>>> chathuri...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi All
>>>>>>>>
>>>>>>>> I conducted a test on windows environment to verify APIMANAGER-2559
>>>>>>>>
>>>>>>>> This is issue is fixed for super tenant but not for other tenants
>>>>>>>> due to APIMANAGER-2529. Both of the above issues are reopened since
>>>>>>>> it's
>>>>>>>> blocking tenant related data migration.
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks and best regards
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Jul 30, 2014 at 6:06 PM, Chathurika De Silva <
>>>>>>>> chathuri...@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi All
>>>>>>>>>
>>>>>>>>> I am going to conduct a testing round in Windows to verify
>>>>>>>>> APIMANAGER-2559. Will circle back to you once i am done.
>>>>>>>>>
>>>>>>>>> Thank You
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Jul 30, 2014 at 6:03 PM, Chalitha Waldeniyage <
>>>>>>>>> chali...@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi All
>>>>>>>>>>
>>>>>>>>>> We are currently carrying on the $subject and please find the
>>>>>>>>>> update as of 30.07.2014
>>>>>>>>>>
>>>>>>>>>> *QA Personal* : Chalitha Waldeniyage and Chathurika De Silva
>>>>>>>>>>
>>>>>>>>>> *Environment details*:
>>>>>>>>>>
>>>>>>>>>> Operating System : Linux
>>>>>>>>>> Java Version/Java VM :jdk1.7.0 (Oracle)
>>>>>>>>>> Packs : APIM 1.7.1
>>>>>>>>>> DBMS: mysql and oracle
>>>>>>>>>> Browser : Firefox 29.0 and Chrome 35.0
>>>>>>>>>> Set up :Stand alone pack
>>>>>>>>>>
>>>>>>>>>> *Issues reported - Priority (Blocker)*
>>>>>>>>>>
>>>>>>>>>> APIMANAGER-2529 - This issue is blocking the actual migration
>>>>>>>>>> process but a workaround has been given.The latest documentation
>>>>>>>>>> should be
>>>>>>>>>> updated accordingly
>>>>>>>>>> APIMANAGER-2534 - This issue is related to missing information
>>>>>>>>>> after the migration
>>>>>>>>>> APIMANAGER-2535 - HTTP verbs are not correctly copied to the
>>>>>>>>>> migrated APIs.
>>>>>>>>>> APIMANAGER-2672 - When versions are created. HTTP verbs are not
>>>>>>>>>> correctly copied for them
>>>>>>>>>> APIMANAGER-2662 - Cannot invoke an API which is in state
>>>>>>>>>> published after migration.
>>>>>>>>>>
>>>>>>>>>> *Problems encountered: specific to oracle*
>>>>>>>>>>
>>>>>>>>>> Oracle database script of API Manager 1.6.0 should be updated to
>>>>>>>>>> work with workflows. This is blocking the migration testing related
>>>>>>>>>> to
>>>>>>>>>> workflows.
>>>>>>>>>>
>>>>>>>>>> In summary as of today, the migration test scenarios cannot be
>>>>>>>>>> fully covered due to above reported issues.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thank you,
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> *Chalitha Maheshwari*
>>>>>>>>>> Software Engineer-QA,
>>>>>>>>>> WSO2 Inc.
>>>>>>>>>>
>>>>>>>>>> *E-mail:* chali...@wso2.com
>>>>>>>>>> *Mobile: *+94710 411 112
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> *Chathurika Erandi*
>>>>>>>>> Software Engineer,
>>>>>>>>> WSO2 Inc.
>>>>>>>>>
>>>>>>>>> *E-mail:* chathuri...@wso2.com
>>>>>>>>> *Mobile: *+94714 328 612
>>>>>>>>> *Blog*: chathurikaerandi.blogspot.com
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Chathurika Erandi*
>>>>>>>> Software Engineer,
>>>>>>>> WSO2 Inc.
>>>>>>>>
>>>>>>>> *E-mail:* chathuri...@wso2.com
>>>>>>>> *Mobile: *+94714 328 612
>>>>>>>> *Blog*: chathurikaerandi.blogspot.com
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Chathurika Erandi*
>>>>>>> Software Engineer,
>>>>>>> WSO2 Inc.
>>>>>>>
>>>>>>> *E-mail:* chathuri...@wso2.com
>>>>>>> *Mobile: *+94714 328 612
>>>>>>> *Blog*: chathurikaerandi.blogspot.com
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Chalitha Maheshwari*
>>>>>> Software Engineer-QA,
>>>>>> WSO2 Inc.
>>>>>>
>>>>>> *E-mail:* chali...@wso2.com
>>>>>> *Mobile: *+94710 411 112
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Chathurika Erandi*
>>>>> Software Engineer,
>>>>> WSO2 Inc.
>>>>>
>>>>> *E-mail:* chathuri...@wso2.com
>>>>> *Mobile: *+94714 328 612
>>>>> *Blog*: chathurikaerandi.blogspot.com
>>>>>
>>>>> _______________________________________________
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>> Uvindra
>>>>
>>>> Mobile: 777733962
>>>>
>>>
>>>
>>>
>>> --
>>> Regards,
>>> Uvindra
>>>
>>> Mobile: 777733962
>>>
>>
>>
>>
>> --
>> *Chathurika Erandi*
>> Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>> _______________________________________________
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Regards,
> Chamila Adhikarinayake
> Software Engineer
> WSO2, Inc.
> Mobile - +94712346437
> Email - chami...@wso2.com
>
--
*Chathurika Erandi*
Software Engineer,
WSO2 Inc.
*E-mail:* chathuri...@wso2.com
*Mobile: *+94714 328 612
*Blog*: chathurikaerandi.blogspot.com
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
