Helping on WSO2 IoT Server - wso2

I install and configure WSO2 IoT Server version 3.3.0. everything is OK and i enrolled 3 android devices in device management section.
However, after installing android agent on mobile device and after approximately half hour of inactivity when i open agent apk in mobile device i received a toast with this text "Device Admin Disabled" and i have to enter server address and then Organization and Username and Password again to see IoT Server again. In server management Dashboard mobile devices are in "inactive" status and server can't communicate with mobile device.
Also This happen every time i restart server and i have to follow above steps to communicate between mobile device and IoT Server.
My question, Is it normal??? Where I was wrong???
thanks a lot for your reply.

I've had the same problem here.
The apk that comes with the default IOT Server installation seems to be outdated.
You can download the newest release here:
https://github.com/wso2/cdmf-agent-android/releases/tag/v3.3.1
I've installed this version and now everything is fine.

Related

WSO2 IoT (Broker) Error 403 - Forbidden on Carbon

I Installed IoT Server 3.1.0 and I launched the change-ip.sh script to change the hostname (iot.wso2.com) and create a new wildcard certificate *.wso2.com.
Carbon access in IoT-Core (hostname "iot.wso2.com") and IoT-Analytics (hostname "iot-das.wso2.com") is OK, but when I try to access the IoT Broker Carbon Interface (hostname iot-mb.wso2.com) I have:
Error 403 - Forbidden
No error messages on wso2carbon.log, also with all DEBUG switch on.
We have blocked the carbon console access for message broker intentionally as it has no use. But we are in the process of creating UI to view and access the MQTT messages and statistics. But that is not yet completed and will be available on next release version.
http://wso2-oxygen-tank.10903.n7.nabble.com/IoTS-MB-Backend-APIs-for-MQTT-related-informations-and-MQTT-management-UI-td145972.html
Carbon console access is only available with IoT core and Analytics server. But not with message broker.

WSO2 MDM Connection Failer

Im trying to setup WSO2MDM on Nexus 07 tablet.
I have configured web based backend and its up and running.
I followed the guide lines in documentation to set up Client mobile app on the tablet. (Already set the configuration according to steps on documentation and compiled it.)
But When I try to register using tablet it gives me an error saying "Authentication failed due to a connection failure do you want to try again?";
Please advise me how to sort this out.
What's the authentication parameters you tried? In a fresh pack, you may not have configured tenants. So your basic login parameters can be "admin", "admin" as the user name and password. That's basically the super admin's credentials.
First check whether you can enroll the device to that user. Then try with the new user you have created. Always keep the Domain field empty if you do not have a tenant set up. And if you are trying this setup in your local machine, make sure your device and server are in the same network. Android WIFI tethering may help you in that case.
Use this guide[1] when you are enrolling.
[1] - http://wso2.com/library/articles/2014/03/how-wso2-emm-addresses-the-android-challenge/
Thanks

WSO2 IOS Profile time out during install

I have WSO2 EMM version 1.1.0 set up. I have the certs all working and everything is playing nicely. I compiled the IOS client and have it installed on my phone via OTA. I am in the process of registering my device. I have a user setup and I have the proper password. I can successfully login from the registration page on my phone and I get the profile downloaded and it has the green "Verified" message on the profile. The problem occurs when I press the install button on the profile. I get a activity spinner at the top of the screen and it says "Installing Profile". It spins for about 30-60 seconds and then I get a message stating "Profile Installation Failed. The request timed out". Any ideas on what would be causing this?
Thanks
Go to {emm_home}/repository/conf/emm-config.xml and chehck whether the following entries are properly pointed to your server.
<iOSEnrollURL>https://10.10.10.174:9443/emm/scep</iOSEnrollURL>
<iOSProfileURL>https://10.10.10.174:9443/emm/profile</iOSProfileURL>
<iOSCheckinURL>https://10.10.10.174:9443/emm/checkin</iOSCheckinURL>
<iOSServerURL>https://10.10.10.174:9443/emm/server</iOSServerURL>
<!-- post url for device tokens -->
<TokenURL>http://10.10.10.174:9763/emm/api/devices/iostokenregister</TokenURL>

WSO2 CEP Management Console

I have installed WSO2 CEP on Linux. But when I tried to open the management console with the https:///carbon/, it says "The website is not available."
I have the WSO2 CEP running (and it said WSO2 Carbon started in 19 sec).
Is this because I didn't install the CEP properly?
Please help. I am new to the WSO2..
If you started the WSO2 CEP or any other WSO2 products properly, then you can see the management console in
https://localhost:9443/
With the default configuration all the WSO2 products works in 9443 port. For more information regarding the WSO2 CEP please refer the [1].
[1] http://docs.wso2.org/wiki/display/CEP210/Complex+Event+Processor+Documentation
Regards,
Mohan
Start the server using the command
sh wso2server.sh
Then when the server start proccess completed, on your browser
https://localhost:9443/carbon
may be you may got https certification error proceed no mater.
Enjoy

WSO2 VMware image - validate email address?

I'm running the WSO2 Stratos VMware image, and I have it to the point where it's running, I've got the browser open, it's at my internal deployment of WSO2, and I've created an account for myself. The problem is, the VM isn't networked to anything, so when it tells me it sent an email to my account and would I please validate it, I can't validate it because it never actually sent an email. I thought maybe there'd be a local mail server on the Linux guest, but I couldn't find one.
Am I missing something? Do I even need to validate the account? I can't seem to access any of the Stratos services, and I suspect that the account validation has something to do with that.
You can log in as an administrator (with the default username/password: admin/admin) and activate the tenant/account you created.