Hi Thusitha,
I got this error when i shutdown the IS server. This is IS 5.4.0 and based
on kernel 4.4.17. This is not reproducible for everyone. Someone get this
problem.
[2017-07-25 14:26:32,663] FATAL
{org.wso2.carbon.core.init.CarbonServerManager} - WSO2 Carbon
initialization Failed
Hi All,
We planned to embed MB features [1] into API Manager 3.0 core to share API
Manager artifacts (APIs, Policies, Subscription, etc) between different
nodes/profiles.
All the products/features which are written on C5 should have default
configuration values in source code and should be able
Hi all,
I have tested following scenarios for iOS.
As an admin:
- Enrolled a device
- Execute operations (Lock, Ring, Notification, Location, Enterprise
wipe)
- Added a policy (restriction)
- Installed an enterprise application
As an user:
- Self sign up an user
-
Hi all,
I have tested the following scenarios for Android.
- Device enrollment
- Device grouping
- Device location
- Device status update
- Device search
- Operations (Mute, Message, Ring, Enterprise-Wipe)
- Policy (Restriction policy)
- App install
- Web-clip install
Hi all,
I have tested following scenarios for Windows 10.
1. Device enrollment.
2. Add windows operations
3. Create windows policy and apply to the device.
4. Edit Windows policy and done apply changes.
5. Create more policies and set priority and then apply to the device.
6. tested notification
Hi Melodies,
As per my knowledge, this config should work by sending the text/xml to the
backend. However, this could happen while rebuilding the message by the
PayloadFactory.
You can overcome your issue by setting the messageType property to text/xml.
.
Since this worked fine in 4.8.1 for
Hi all,
I've tested the following scenarios.
- User Registration
- Android Sense enrollment, Sensor data pushing on tenant / super tenant
account
- Role creation and role assign on tenant / super tenant account
- User password reset on tenant / super tenant account
- User
Hi All,
I am getting following error while running the IS 5.4.0-SNAPSHOT in the
Windows.
TID: [-1234] [] [2017-07-25 03:13:59,443] ERROR
{org.wso2.carbon.ldap.server.DirectoryActivator} - Could not start the
embedded-ldap.
org.wso2.carbon.ldap.server.exception.DirectoryServerException: Error
Hi Abimaran,
We have implemented enum based config read approach for all the above
configurations. Please find the implementation [1]. Every config has a
default value and it gets overrides after reading from the XML file. I
think we could figure out approach to read data from deployment.yaml and
Guys,
Just following up on IoT cluster. How's it looking in terms of testing?
Cheers,
Pubudu.
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547
Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp
On Tue, Jul 25, 2017 at 5:46 PM,
Hi All,
I have tested the following scenarios with super tenant user and a non
super tenant user.
- User Registration
- Android Sense enrollment, Sensor data pushing
- Role Management
- Recovery and reset password
- User Management
- Android operations
- Android enrollment
Hi all,
I tested the following scenarios.
*Android Enterprise Install:*
*> Super Tenant mode: Admin User*
1. Enrolled an Android device as the admin user.
2. Create and publish an Android App.
3. Installed the app to the admin user.
*> Super Tenant mode: Normal user.*
1.
Yasima/Chiranga,
Thanks, this was helpful.
Javier
From: Chiranga Alwis [mailto:chira...@wso2.com]
Sent: Tuesday, July 25, 2017 2:19 AM
To: Yasima Dewmini
Cc: Vazquez-Hidalgo, Javier; dev@wso2.org
Subject: Re: [Dev] [DEV] Clustering APIM 2.1.0
Hi all,
FYI we would be making this solution
Hi all,
I set up the cluster and tested the following scenarios.
- Creating separate profiles (Manager, backend, key manager)
- Enrolling iOS device
- Disenrolling iOS device
- Adding new policies
- Editing policies
- Applying changes in the policies to the already enrolled
Kind reminder on this
On Mon, Jul 24, 2017 at 6:26 PM, Shakila Sasikaran wrote:
> Hi all,
>
> I tried to send the parameters in the body instead of passing them as URL
> parameters from the authenticator to the external web app. It redirects to
> the URL
Hi all,
I have tested following scenarios in IOS flow.
Super tenant:
- Enrolled a device
- Execute operations - Device Lock, Ring, Notification, Location
- Passcode Policy
- Installed an enterprise application
New Tenant:
- Enrolled a device
- Execute operations - Device
Hi,
I have tested following functionalities for Android Devices.
- Geo Fencing Alerts
- Create Device Type
- Create Device Event
- View Device type
- Create a new device
- Publish device events
Found no issues.
[+] Stable - go ahead and release.
Regards.
On Mon, Jul 24,
Hi,
Is it possible to plug custom interceptors for micro-services in msf4j
2.1.0. (per service not globally)
Best Regards
Isuranga Perera
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Hi Melodies,
Can you please share your configuration.
Regards,
Vinod
On Tue, Jul 25, 2017 at 1:09 PM, Melodias wrote:
> Hi,
> When I use payload factory mediator then my content type is changing from
> text/xml to application/xml. After that, when I call backend i got
Hi Vinod Kavinda,
Thanks for replay.
My inSeq:
http://org.apache.synapse/xsd;
expression="get-property('transport', 'Content-Type')" name="LOG1" />
http://pl.esp.ws/;>
CODE_$1
Hi,
I have tried to build the projects with sonarqube locally. It seems the
results of local sonarqube and remote one are different. In addition, for
example in remote sonarqube some issues are shown as "critical" even though
the rules state them as "info".
I have used the same sonarqube
Dear WSO2
Does instruction in [1] can be used for API Manager version 2.0.0?
[1] https://docs.wso2.com/display/AM210/Deploying+API+Manager+
as+an+All-in-One+Instance
Thank you very much,
Tinnapat.
On Tue, Jul 25, 2017 at 11:10 AM, Yasima Dewmini wrote:
> Hi Javier,
>
>
Hi,
from WSO2 API Manager version 2.0.0 documentation:
https://docs.wso2.com/display/AM200/Deploying+API+Manager+as+an+All-in-One+Instance
.
On Wed, Jul 26, 2017 at 9:02 AM, T C wrote:
> Dear WSO2
>
> Does instruction in [1] can be used for API Manager version 2.0.0?
>
>
FYI
We were able to fix this issue in WSO2 AS using the patch [1]
[1]
https://svn.wso2.com/wso2/custom/projects/projects/carbon/wilkes/patches/patch0052
Thanks,
Suhan
On Fri, Jul 14, 2017 at 2:03 PM, Mushthaq Rumy wrote:
> Hi All,
>
> I'm getting an error while invoking
Hi all,
FYI we would be making this solution available on AWS Marketplace, for use
in the near future.
On Tue, Jul 25, 2017 at 9:40 AM, Yasima Dewmini wrote:
> Hi Javier,
>
> According to my understanding you need to cluster two API manager
> instances as All-in-One instance.
Congratulations Madhawa ... :)
*Maninda Edirisooriya*
Senior Software Engineer
*WSO2, Inc.*lean.enterprise.middleware.
*Blog* : http://maninda.blogspot.com/
*E-mail* : mani...@wso2.com
*Skype* : @manindae
*Twitter* : @maninda
On Mon, Jul 24, 2017 at 10:03 AM, Hasitha Amal De Silva
Hi,
When I use payload factory mediator then my content type is changing from
text/xml to application/xml. After that, when I call backend i got error. In
ESB 4.8.1 that problem not exists.
Is it intentional action of mediator or is it bug?
--
View this message in context:
Hi Isuranga,
In 2.1.0 we only support global interceptors. Resource level interceptors
were introduced in 2.3.0-m2.
Thanks
Thusitha
On Tue, Jul 25, 2017 at 11:55 PM, Isuranga Perera wrote:
> Hi,
>
> Is it possible to plug custom interceptors for micro-services in
28 matches
Mail list logo