I followed the instructions in the link (https://docs.wso2.com/display/IOTS330/Enterprise+IoT+solution) in Windows to start WSO2 IoT server. So, broker, iot-server and analytics are started. But, when I'm trying to log in to the device management console using admin login or the login credentials I created, it gives me an authentication error.
I tried the solutions in this answer (Not able to access WSO2 IoTS Device Management Console in wso2-iot-3.3.0 when logged in 'admin') also (Reducing Java version to 1.8.0_144 and making the compression parameter to off in all the catalina-server.xml files). But any of it didn't work for me.
I have attached the screen shots of the error. Please help me to go through this! Thank you.
Error in browser
Error description in iot-server console-Part 1
Error description in iot-server console-Part 2
This is related to the issue mentioned in the github issue mentioned below and it seems, it is already fixed in latest master.
As a quick workaround you could try to modify the startup script files (bat files in this case) and add the changes mentioned in the above git issue.
For example, you can change the file modules/distribution/src/core/bin/iot-server.bat at line number 73 as below.
FOR %%D in ("%CARBON_HOME%\wso2\lib\commons-lang*.jar") DO set CARBON_CLASSPATH=!CARBON_CLASSPATH!;".\wso2\lib\%%~nD%%~xD"
Similarly do the same change as above for files mentioned below as well.
modules/distribution/src/core/resources/profiles/backend/iot-server.bat
modules/distribution/src/core/resources/profiles/keymanager/iot-server.bat
modules/distribution/src/core/resources/profiles/manager/iot-server.bat
This should resolve the issues you are facing.
Related github issue - https://github.com/wso2/product-iots/pull/1838/files
Related
I'm currently experimenting/working on WSO2. What i'm trying to do is to have Data Analytics server configured. I started by following the below specified URL
https://docs.wso2.com/display/AM210/Configuring+APIM+Analytics#9d6747f5c0074928b18599abe472987d (Quick Steps)
After performing all the steps, i get the following issue on APIM cmd prompt
YES Its pretty evident from the error that no such table exists BUT that is exactly the issue i'm facing. What could really be the cause here?
Consider the following points:
I've not followed ALL the steps mentioned on
https://docs.wso2.com/display/DAS310/Getting+Started (BUT are they
required?)
In the installation prerequisites for DAS, JDBC-compliant Connector for Java is required which I've not yet installed (BUT its not mandatory at the same time)
Most of the QUICK STEPS for the configuration of DAS in the specified URL i.e. https://docs.wso2.com/display/AM210/Configuring+APIM+Analytics#9d6747f5c0074928b18599abe472987d where already in place and i only had to
Set Up JDK, ANT, Maven
enable the analytics section in the API-M_HOME/repository/conf/api-manager.xml
add log4j.rootLogger=, DAS_AGENT to API-M_HOME/repository/conf/log4j.properties
add snappy-java_1.1.1.7.jar to DAS_HOME\repository\components\lib
Yet the issue persists, Do let me know of what you think. Thank you
Since you are following quick start guide please extract the WSO2 API Manager and the WSO2 API-M Analytics distributions (zip files), to the same directory (preferably an empty directory).
Also, you need to generate some traffic to the published APIs in order to analytics server to create this table for the first time.
The WSO2IS sample app instructions are less than accurate and there are some key details to the instructions are missing. Does anyone have a complete set of instructions that will actually produce a working example?
Also, it seems like localhost is coded everywhere, some guidance on how to add and update the service provider and identity provider that are on different hosts is important.
also, is the patch or service pack needed for this to run correctly? That info is not in the documentation or blogs I've been reading from WSO2
I've written a post on configuring the sample for a tenant scenario1. You should be able to configure using this. Change the hostname of SAML.IdPUrl in WEB-INF/classes/travelocity.property to that of IS. Change Assertion Consumer URL at SP registration and on WEB-INF/classes/travelocity.property to that of SP(travelocit app).
1 - how-to-configure-identity-server-sso
i am approaching the development of Restful web services for the first time. I tried to follow this guide for Netbeans . I am stuck at the testing of the web service.
When i open the
http://localhost:8080/WebServicesTest/test-resbeans.html
page, none of the root resources appears in the left menu. (there should be entities.customer and entities.discountcode)
I really can't find a solution.
Thanks in advance to anyone who likes to give me a hint.
--------------- Edit
If i click on CustomerDB --> Deploy i get an error
In-place deployment at C:\Users\utente\Documents\NetBeansProjects\CustomerDB\build\web
GlassFish Server 4, deploy, null, false
C:\Users\utente\Documents\NetBeansProjects\CustomerDB\nbproject\build-impl.xml:1071:
The module has not been deployed.
See the server log for details.
The line 1071 of build-impl.xml is
<nbdeploy clientUrlPart="${client.urlPart}" debugmode="false" forceRedeploy="${forceRedeploy}"/>
I checked out the referenced tutorial.
Which exact path did you follow? Did you change anything?
Most likely your CustomerDB application is not deployed correctly (see GlassFish Server output in NetBeans) and thus is not able to expose the web service and thus is not displayed in the test page (nothing visible in the side bar).
I tried the tutorial myself and had that phenomenon when using another database ("test" instead of the sample db, which was not connectable in my installed environment), resulting in a message that "test__pm" resource was not found. I then created a conection pool and a jdbc reosurce for test and then it worked.
I have installed aws plugins from http://aws.amazon.com/eclipse.
While creating aws java project, next and finish buttons are not enabling.
While opening eclipse, I am getting below errors.
Couldn't read regions file,
Failed to cache regions file,
Unable to check status of AWS SDK for Java download and Unable to refresh security groups: Unable to execute HTTP request: peer not authenticated.
The problem is,your AWS SDK is not installed and updated properly . Just click on >Help in eclipse and then click on >Installation Details and from that reinstall AWS Eclipse plugin .
Please make sure that url of plugin is appropriated for your eclipse version.
It will solve your problem.
Try using a new workspace and you will be good to go.
Let know if the problem still persists.
I am trying to upload a carbon archive in the registry. Everything seems to be OK when I add a new application, but the log show the following error:
An error occurred while determining the latest version of the resource at the given path:
/_system/governance/trunk/wsdls/.... (path to the wsld deployed)
org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to obtain the user realm for tenant: -1
I log with the admin user and everything that should be upload is in the registry.
Any help?
Thanks,
I tried to reproduce this with WSO2 G-Reg 4.1.1 but unable to reproduce it.
Please indicate the G-Reg version you have tried out this scenario.
When you upload the CAR file from Management Console, make sure to remove the previous version of the same CAR file before you upload the newer version.
This error seems to be related versioning.
Since you remove the previous version of the CAR file, the aforementioned suggestion will solve your problem.
Thanks and Regards,
Harshana
WSDLs are stored in the /_system/governance/../trunk/wsdl/.. location if you upload them via management console or upload the resource from Developer Studio Registry Browser.
But when you deploy a WSDL via a C-App, when creating the registry resource from Developer Studio, you specify a location to deploy. Hence the WSDLs deployed via C-Apps are deployed to this specified location but not the other location.
Therefore from your proxy service, you should refer the location you have mentioned to deploy your WSDL but not the default location.
Once you fix this, your Proxy service will work fine.
Thanks and Regards,
Harshana