Re: [Dev] [WSO2 Connector] Concur- getExchangeRate issue

[Rajjaz Mohammed]

Hi,

Method removed from the connector and will add a new version in the store.
Other then getExchangeRate method other methods are works fine[1].

[1] https://wso2.org/jira/browse/ESBCONNECT-107

On Sat, Jul 2, 2016 at 11:18 AM, Keerthika Mahendralingam <
keerth...@wso2.com> wrote:

> Hi Godwin,
>
> According to the documentation [1], this method is not available in the
> API. I have created a public JIRA[2] to remove this method from the
> connector.
>
> [1].
> https://developer.concur.com/api-reference/expense/expense-report/expense-form.html
>
> [2]. https://wso2.org/jira/browse/ESBCONNECT-107
>
> Thanks,
> Keerthika.
>
> On Sat, Jul 2, 2016 at 1:10 AM, Godwin Shrimal  wrote:
>
>> Hi All,
>>
>> I am trying to get exchange rate using WSO2 Concur connector and getting
>> below response.
>>
>> 
>> Not Found
>> 2016-07-01T15:31:40
>> 26D1A0AC-E21C-4626-85A3-2BB5380505DF
>> 
>>
>> Once we enable wire log it has an outbound as *GET
>> /api/v3.0/expense/exchangerates/?forDate=01/01/2016& HTTP/1.1 , *So we
>> try the relevant rest endpoint   which is in [1] also give the same result.
>> Concur shows the particular error in [2].
>>
>> Any thought ?
>>
>>
>> [1]
>> https://www.concursolutions.com/api/v3.0/expense/exchangerates/?forDate=05/05/2016
>> [2] https://developer.concur.com/tools-support/reference/http-codes.html
>>
>> *Note: My token is valid since when I try some other endpoint those are
>> working properly.*
>>
>> Thanks
>> Godwin
>>
>> --
>> *Godwin Amila Shrimal*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *http://lnkd.in/KUum6D *
>> twitter: https://twitter.com/godwinamila
>>
>
>
>
> --
> 
> Keerthika Mahendralingam
> Software Engineer
> Mobile :+94 (0) 776 121144
> keerth...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thank you
Best Regards

*Rajjaz HM*
Associate Software Engineer
Platform Extension Team
WSO2 Inc. 
lean | enterprise | middleware
Mobile | +94752833834|+94777226874
Email   | raj...@wso2.com
LinkedIn  | Blogger
 | WSO2 Profile

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Provide Support to run Jaggery apps in Tomcat Server

[KasunG Gajasinghe]

Good work Nisala.

Can we also do a performance round to see whether there are any perf gains
when running Jaggery apps in vanilla Tomcat/AS6?

How are you going to manage the codebase for Carbon vs Tomcat Jaggery
support? Better if we can maintain it in the same place.

On Sat, Jul 2, 2016 at 12:51 PM, Nisala Nanayakkara  wrote:

> Hi all,
>
> This is an update regarding the feature 'Provide Support to run Jaggery
> apps in Tomcat Server'.
>
> At present Jaggery scripts can only be executed in a jaggery server.
> Because Jaggery Server which is powered by WSO2 carbon OSGi Runtime, is the
> Runtime Environment that hosts Jaggery applications. The goal of this
> feature is to provide support to run jaggery apps in a pure tomcat server
> without any modifications to the jaggery apps.This will enable developers
> to write Jaggery scripts and directly deploy them in apache tomcat server.
> So this will improve the flexibility of the jaggery apps.
>
> This is an extension for the Apache tomcat 8 to run the jaggery app
> without modifying it. Although this is implemented as a requirement of WSO2
> Application Server 6, Users who want to run jaggery apps without jaggery
> server, can use this feature to run their jaggery apps in Apache tomcat
> server.
>
> I have attached the documentation and sample jaggery with this email.
> Please find these attachments and relevant jaggery branch here[1]. Please
> feel free to ask any questions.
>
> [1] - https://github.com/wso2/jaggery/tree/tomcat-8.0.x-jaggery
>
> Thanks,
> Nisala
>
> --
> *Nisala Niroshana Nanayakkara,*
> Software Engineer
> Mobile:(+94)717600022
> WSO2 Inc., http://wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] log user events to audit.log file via Jaggery block layer

[Amalka Subasinghe]

Hi,

We can log adding following to the jaggery.

var audit = org.wso2.carbon.CarbonConstants.AUDIT_LOG;
audit.info("User : " + jagg.getUser() + ", Action : " +  action);

Here. I want to log who is the user logged in and what action he called.
Would it be ok to add this code to the router jag in app cloud? As I know
all requests/actions go through it. am I right?

Thanks
Amalka

On Fri, Jul 1, 2016 at 12:13 PM, Amalka Subasinghe  wrote:

> Hi,
>
> I have a Jaggery app deployed in WSO2AS, I want to log user activities via
> block layer to a separate file (to audit.log).
> Please help.
>
> Thanks
> Amalka
>
>


-- 
Amalka Subasinghe

WSO2 Inc.
Mobile: +94 77 9401267
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] Changing the name of publisher in ES

[Megala Uthayakumar]

Thanks Rajith. I will try that.

On Fri, Jul 1, 2016 at 9:46 PM, Rajith Roshan  wrote:

> Hi Megala,
>
> The following jira [1] summarizes the changes required to rename the
> publisher app. But AFAIK this feature is not properly tested in ES. Could
> you please try the changes suggested in the jira
>
> [1] - https://wso2.org/jira/browse/STORE-936
>
> Thanks!
> Rajith
>
> On Fri, Jul 1, 2016 at 7:20 PM, Udara Rathnayake  wrote:
>
>> Hi All,
>>
>> I remember adding ES store/publisher apps along with the APIM store
>> publisher apps. (can't remember whether we have renamed ES stuff or APIM :(
>> ). Does anyone remember this?
>>
>> On Thu, Jun 30, 2016 at 9:08 AM, Megala Uthayakumar 
>> wrote:
>>
>>> Hi All,
>>>
>>> Is it possible to change the default name of publisher in ES to a
>>> customized one(i.e publisher -> wso2-publisher)? If so how to achieve it ?
>>>
>>> Thanks.
>>>
>>> Regards,
>>> Megala
>>>
>>> --
>>> Megala Uthayakumar
>>>
>>> Software Engineer
>>> Mobile : 0779967122
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Regards,
>> UdaraR
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rajith Roshan
> Software Engineer, WSO2 Inc.
> Mobile: +94-72-642-8350 <%2B94-71-554-8430>
>



-- 
Megala Uthayakumar

Software Engineer
Mobile : 0779967122
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] WSO2 API Manager 2.0.0 BETA2 Released!

[Tania Mahanama]

On Sat, Jul 2, 2016 at 1:12 PM, Bhathiya Jayasekara 
wrote:

> Hi Shavantha,
>
> Dashborad is something you use to monitor stuff. Usually a dashboard is a
> set of gadgets. But in APIm what we have in /admin is a set of
> settings/controllers for admins. Hence the context change. Further, from
> now on it wll be called  "Admin Portal" Instead of "Admin Dashboard".
>
> @Tania: We need to update docs accordingly.
>

Noted, thanks!


>
> Thanks,
> Bhathiya
>
> On Sat, Jul 2, 2016 at 12:26 PM, Shavantha Weerasinghe  > wrote:
>
>> Hi Harsha
>>
>> Any specific reason for the admin-dashboard to be renamed as admin. I
>> checked the services under running applications and the context is listed
>> as /admin
>> 
>>
>> regards,
>> Shavantha Weerasinghe
>> Senior Software Engineer QA
>> WSO2, Inc.
>> lean.enterprise.middleware.
>> http://wso2.com
>> http://wso2.org
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>>
>>
>> On Fri, Jul 1, 2016 at 9:21 PM, Harsha Kumara  wrote:
>>
>>> WSO2 API Manager 2.0.0 BETA2 Released!
>>> 
>>>
>>> We are pleased to announce the BETA2 release of WSO2 API Manager 2.0.0.
>>>
>>> WSO2 API Manager is a complete solution for designing and publishing
>>> APIs, securing and routing API traffic in a scalable way, whilst nurturing
>>> a developer community around the API ecosystem.
>>>
>>> This release comes with both the runtime and analytics, providing
>>> out-of-the-box support for API usage and performance analysis. You can
>>> download these distributions below.
>>>
>>> Runtime - wso2am-2.0.0-BETA2.zip
>>> 
>>> Analytics - wso2analytics-apim-1.0.0-beta2.zip
>>> 
>>> P2-Repository - p2-repository
>>> 
>>> Improvements and Bug Fixes - WSO2 API Manager - Version 2.0.0-Beta2Bug
>>>
>>>- [APIMANAGER-4228 ] -
>>>When using the publisher REST API is used, internal server error (code 
>>> 500)
>>>occurs in following cases
>>>- [APIMANAGER-4963 ] -
>>>It takes more than 7 minutes to start the APIM server with few errors
>>>- [APIMANAGER-5047 ] -
>>>[Cluster setup] APIs are not visible in the Store side
>>>- [APIMANAGER-5048 ] -
>>>Exceptions thrown when starting the server with -Dsetup by pointing API
>>>Manager database to Mysql 5.7
>>>- [APIMANAGER-5066 ] -
>>>'There is already an object named 'APPLICATION_NAME_CONSTRAINT' in the
>>>database' error occurs when executing MSSQL script given for AM DB.
>>>- [APIMANAGER-5067 ] -
>>>Read me and release notes files in APIM 2.0.0 pack aren't up to date
>>>- [APIMANAGER-5078 ] -
>>>Statistics are not displayed in Publisher and Store dashboards when 
>>> connect
>>>to an analytics cluster
>>>- [APIMANAGER-5081 ] -
>>>go to overview option via add new API throws an exception
>>>- [APIMANAGER-5097 ] -
>>>Application throttled out response body showing a 'No Content' when
>>>enabling analytics
>>>- [APIMANAGER-5105 ] -
>>>Case Sensitive tags are displayed as same in capital letters
>>>- [APIMANAGER-5108 ] -
>>>No statistics displayed for subscribers other than admin in Published 
>>> APIs
>>>over time
>>>- [APIMANAGER-5109 ] -
>>>Dropdown should rename as 'API subscribed by' in Publish APIs over time
>>>Statistics
>>>- [APIMANAGER-5110 ] -
>>>Other tenant subscribers aren't displayed in 'API subscribed by' drop 
>>> down
>>>in Published APIs Over Time Statistics
>>>- [APIMANAGER-5111 ] -
>>>Cannot Delete subscriptions when API or provider name contains "-" from 
>>> CXF
>>>Store REST API
>>>- [APIMANAGER-5116 ] -
>>>No Statistics displayed for API Usage Across Usage Agent Statistics
>>>- [APIMANAGER-5117 ] -
>>>[Tiers API]tierPlan returns null eventhough ther

Re: [Dev] [Architecture] WSO2 API Manager 2.0.0 BETA2 Released!

[Harsha Kumara]

Hi Shavantha,

AFAIK it's for consistency as we have applications namely publisher and
store and also the functionalities that offered from the admin application
no much related to dashboard rather it's provide configurations settings.

Thanks,
Harsha

On Sat, Jul 2, 2016 at 12:26 PM, Shavantha Weerasinghe 
wrote:

> Hi Harsha
>
> Any specific reason for the admin-dashboard to be renamed as admin. I
> checked the services under running applications and the context is listed
> as /admin
> 
>
> regards,
> Shavantha Weerasinghe
> Senior Software Engineer QA
> WSO2, Inc.
> lean.enterprise.middleware.
> http://wso2.com
> http://wso2.org
> Tel : 94 11 214 5345
> Fax :94 11 2145300
>
>
> On Fri, Jul 1, 2016 at 9:21 PM, Harsha Kumara  wrote:
>
>> WSO2 API Manager 2.0.0 BETA2 Released!
>> 
>>
>> We are pleased to announce the BETA2 release of WSO2 API Manager 2.0.0.
>>
>> WSO2 API Manager is a complete solution for designing and publishing
>> APIs, securing and routing API traffic in a scalable way, whilst nurturing
>> a developer community around the API ecosystem.
>>
>> This release comes with both the runtime and analytics, providing
>> out-of-the-box support for API usage and performance analysis. You can
>> download these distributions below.
>>
>> Runtime - wso2am-2.0.0-BETA2.zip
>> 
>> Analytics - wso2analytics-apim-1.0.0-beta2.zip
>> 
>> P2-Repository - p2-repository
>> 
>> Improvements and Bug Fixes - WSO2 API Manager - Version 2.0.0-Beta2Bug
>>
>>- [APIMANAGER-4228 ] -
>>When using the publisher REST API is used, internal server error (code 
>> 500)
>>occurs in following cases
>>- [APIMANAGER-4963 ] -
>>It takes more than 7 minutes to start the APIM server with few errors
>>- [APIMANAGER-5047 ] -
>>[Cluster setup] APIs are not visible in the Store side
>>- [APIMANAGER-5048 ] -
>>Exceptions thrown when starting the server with -Dsetup by pointing API
>>Manager database to Mysql 5.7
>>- [APIMANAGER-5066 ] -
>>'There is already an object named 'APPLICATION_NAME_CONSTRAINT' in the
>>database' error occurs when executing MSSQL script given for AM DB.
>>- [APIMANAGER-5067 ] -
>>Read me and release notes files in APIM 2.0.0 pack aren't up to date
>>- [APIMANAGER-5078 ] -
>>Statistics are not displayed in Publisher and Store dashboards when 
>> connect
>>to an analytics cluster
>>- [APIMANAGER-5081 ] -
>>go to overview option via add new API throws an exception
>>- [APIMANAGER-5097 ] -
>>Application throttled out response body showing a 'No Content' when
>>enabling analytics
>>- [APIMANAGER-5105 ] -
>>Case Sensitive tags are displayed as same in capital letters
>>- [APIMANAGER-5108 ] -
>>No statistics displayed for subscribers other than admin in Published APIs
>>over time
>>- [APIMANAGER-5109 ] -
>>Dropdown should rename as 'API subscribed by' in Publish APIs over time
>>Statistics
>>- [APIMANAGER-5110 ] -
>>Other tenant subscribers aren't displayed in 'API subscribed by' drop down
>>in Published APIs Over Time Statistics
>>- [APIMANAGER-5111 ] -
>>Cannot Delete subscriptions when API or provider name contains "-" from 
>> CXF
>>Store REST API
>>- [APIMANAGER-5116 ] -
>>No Statistics displayed for API Usage Across Usage Agent Statistics
>>- [APIMANAGER-5117 ] -
>>[Tiers API]tierPlan returns null eventhough there is a tier plan set to a
>>API tier
>>- [APIMANAGER-5118 ] -
>>[Tiers API]Attributes are returned as blank eventhough there are set of
>>attributes defined for an API level tier
>>- [APIMANAGER-5120 

Re: [Dev] [Architecture] WSO2 API Manager 2.0.0 BETA2 Released!

[Bhathiya Jayasekara]

Hi Shavantha,

Dashborad is something you use to monitor stuff. Usually a dashboard is a
set of gadgets. But in APIm what we have in /admin is a set of
settings/controllers for admins. Hence the context change. Further, from
now on it wll be called  "Admin Portal" Instead of "Admin Dashboard".

@Tania: We need to update docs accordingly.

Thanks,
Bhathiya

On Sat, Jul 2, 2016 at 12:26 PM, Shavantha Weerasinghe 
wrote:

> Hi Harsha
>
> Any specific reason for the admin-dashboard to be renamed as admin. I
> checked the services under running applications and the context is listed
> as /admin
> 
>
> regards,
> Shavantha Weerasinghe
> Senior Software Engineer QA
> WSO2, Inc.
> lean.enterprise.middleware.
> http://wso2.com
> http://wso2.org
> Tel : 94 11 214 5345
> Fax :94 11 2145300
>
>
> On Fri, Jul 1, 2016 at 9:21 PM, Harsha Kumara  wrote:
>
>> WSO2 API Manager 2.0.0 BETA2 Released!
>> 
>>
>> We are pleased to announce the BETA2 release of WSO2 API Manager 2.0.0.
>>
>> WSO2 API Manager is a complete solution for designing and publishing
>> APIs, securing and routing API traffic in a scalable way, whilst nurturing
>> a developer community around the API ecosystem.
>>
>> This release comes with both the runtime and analytics, providing
>> out-of-the-box support for API usage and performance analysis. You can
>> download these distributions below.
>>
>> Runtime - wso2am-2.0.0-BETA2.zip
>> 
>> Analytics - wso2analytics-apim-1.0.0-beta2.zip
>> 
>> P2-Repository - p2-repository
>> 
>> Improvements and Bug Fixes - WSO2 API Manager - Version 2.0.0-Beta2Bug
>>
>>- [APIMANAGER-4228 ] -
>>When using the publisher REST API is used, internal server error (code 
>> 500)
>>occurs in following cases
>>- [APIMANAGER-4963 ] -
>>It takes more than 7 minutes to start the APIM server with few errors
>>- [APIMANAGER-5047 ] -
>>[Cluster setup] APIs are not visible in the Store side
>>- [APIMANAGER-5048 ] -
>>Exceptions thrown when starting the server with -Dsetup by pointing API
>>Manager database to Mysql 5.7
>>- [APIMANAGER-5066 ] -
>>'There is already an object named 'APPLICATION_NAME_CONSTRAINT' in the
>>database' error occurs when executing MSSQL script given for AM DB.
>>- [APIMANAGER-5067 ] -
>>Read me and release notes files in APIM 2.0.0 pack aren't up to date
>>- [APIMANAGER-5078 ] -
>>Statistics are not displayed in Publisher and Store dashboards when 
>> connect
>>to an analytics cluster
>>- [APIMANAGER-5081 ] -
>>go to overview option via add new API throws an exception
>>- [APIMANAGER-5097 ] -
>>Application throttled out response body showing a 'No Content' when
>>enabling analytics
>>- [APIMANAGER-5105 ] -
>>Case Sensitive tags are displayed as same in capital letters
>>- [APIMANAGER-5108 ] -
>>No statistics displayed for subscribers other than admin in Published APIs
>>over time
>>- [APIMANAGER-5109 ] -
>>Dropdown should rename as 'API subscribed by' in Publish APIs over time
>>Statistics
>>- [APIMANAGER-5110 ] -
>>Other tenant subscribers aren't displayed in 'API subscribed by' drop down
>>in Published APIs Over Time Statistics
>>- [APIMANAGER-5111 ] -
>>Cannot Delete subscriptions when API or provider name contains "-" from 
>> CXF
>>Store REST API
>>- [APIMANAGER-5116 ] -
>>No Statistics displayed for API Usage Across Usage Agent Statistics
>>- [APIMANAGER-5117 ] -
>>[Tiers API]tierPlan returns null eventhough there is a tier plan set to a
>>API tier
>>- [APIMANAGER-5118 ] -
>>[Tiers API]Attributes are returned as blank eventhough there are set of
>>a