I'm learning wso2 and working with this sample: http://wso2.com/library/articles/2011/01/wso2-esb-example-file-processing/
I followed the instructions but when I start the server nothing happens. I don't see references to the FileProxy or sequences on the management console until I move the xml files to the deployment directory. When I do that I'll see the proxy and Sequences install but nothing else happens when I drop the txt file in the "in" directory.
I am not sure what I need to do to trigger the proxy. I'm not getting any error messages or anything. The server just kind of sits there.
What do I need to do to run the sample?
Thank you.
Try this sample https://docs.wso2.com/pages/viewpage.action?pageId=33136056 in WSO2 ESB 4.8.1 to get a basic understanding of VFS Proxy.
Related
I've installed WSO2 and have it running, devices connected (Android) etc.
I can see the device and the information about it, but the operations log is empty and it's not letting me view the installed applications or deploy new ones.
I've probably missed something basic, but I can't for the life of me see what it is, any help welcome!
Thanks
I hope you are running WSO2 IoT server 3.1.0.
Please follow these steps to enable debug logs.
Go to the IOT_HOME/conf/log4j.properties file.
Uncomment the following two
#log4j.logger.org.apache.synapse.transport.http.wire=DEBUG
#log4j.logger.feign=DEBUG
Comment the following one.
log4j.category.org.apache.synapse=WARN
Then restart the IoT server.
This will start printing debug logs in the IoT_HOME/repository/logs/wso2carbon.log file.
AS3 Webservice
I'm using this library to connect to a database where I store and retrieve files that my program uses. When I test it locally, it works fine, but when I put it online it has trouble connecting, I ran some debugs inside the library and after "DESCRIPTION LOADED" is traced, nothing happens. Also I'm not really sure where to run traces to see what the problem is exactly, I just removed the comments on some traces that were already there.
So to recap, when I run my program offline(locally) it runs fine, it connects, sends and receives no problem. Once online, it doesn't connect it doesn't even run the traces I have in the OperationSuccessful or OperationFailure functions.
So I'm wondering if anyone has been using this library successfully and could maybe share some tips or code that will help me, thank you!
EDIT
We seemed to have solved our problem with this method without using that third party webservice library.
I am going to assume a few things here.
1) the data server is not on the same domain.
2) the server with the data is open and not blocked by the firewall.
You need a crossdomain.xml file on the server with the data allowing the domain where the swf is located.
Something like this.
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<allow-access-from domain = "*"/>
</cross-domain-policy>
I have created two (java web applcaion ). one acts as a Server , I created ( web service) into. the second acts as client , I created ( Web service client) into .
I created them in netBeans, and they run .
but now I want to run them out net beans , how I can do this?
I want any way to run out netBeans such as command prompt or an where.
if you have idia about running (.war) file , please tell me.
thanks in advance.
What NetBeans did behind the scenes for you was to deploy your bundled and zipped source code into a servlet container (most likely Tomcat), which in turn takes care of everything between the webservice requests and your application.
Find out where your tomcat is located
Eventually stop tomcat manually via something like TOMCAT_HOME/bin/shutdown.sh
Copy your warfile into TOMCAT_HOME/webapps
Start tomcat (TOMCAT_HOME/bin/startup.sh)
Optionally observe the log (TOMCAT_HOME/logs/catalina.out) to find out about potential deployment problems
If everything went fine, you should be able to use your webservice with your client.
I am writing a small application to get the various diagnostic parameter of Apache Webserver like time of the start of the server, Worker mode or Prefork mode, server version and many more. I have found few API for getting info about these parameter. But I colud not find nay API for the getting start time of the WebServer. Is there any such kind of API?
If there is no API then there are different approaches like getting the start time using "ps" command in linux/unix and go for similar API in windows.There can be other approach that I could see is to have the time of the APache WebServer in any Variable or file.
Please enlighten me with your valuable comments, approaches.
TIA
Anil
Try to have a look at the Apache' the mod_status
After installing VMware Server I get the following error when I try to access the VMware web-based server manager:
The VMware Infrastructure Web Service
at "http://localhost:8222/sdk" is not
responding
Go into the services manager and check that the 'VMware Host Agent' service is running. If not, then start it and then try browsing to the site again.
Vmware Hostd was not working for me either.
However, in trying to start the service it stopped automatically. Typically when this happens it is because there is an error in your config.xml.
C:\ProgramData\VMware\VMware Server\hostd\config.xml
In my case, checking the logs at:
C:\ProgramData\VMware\VMware Server
showed it erroring out after "Trying hostsvc".
Searching the config.xml for hostsvc showed references to several things, the first thing was the datastore. In checking my datastores.xml file:
C:\ProgramData\VMware\VMware Server\hostd\datastores.xml .
I found it full of all sorts of random characters instead of a properly formed XML document.
Renaming datastores.xml to datastorex.xml.bad allowed me to start the service. At which point I had to add back my datastores through the GUI.
Hopefully this will help someone else out. I did not find any other references in Google to this issue.
Try accessing via "http://localhost:8222" without the /sdk. You can also try the secure site via "https://localhost:8333".