Hi,
maybe at this stage some general clarification would be good. There are two general issues that are rather unrelated to RA itself: (1) Making JBoss listen on the right interfaces and (2) making the client know whom to talk with.
To have JBoss listen on
all devices, start "run.bat -b 0.0.0.0" or "run.sh -b 0.0.0.0". You can go to server/default/deploy/jbossweb.sar/server.xml and check the binding address. If the option is checked in the installer, this may have been overridden.
<Connector protocol="HTTP/1.1" port="${jboss.web.http.port}" address="${jboss.bind.address}"
redirectPort="${jboss.web.https.port}" />
Once you got that working, point your
browser to localhost:8080, hostname:8080, 127.0.0.1:8080 and ipaddress:8080 (e.g. 192.168.1.1:8080) to see whether you can access it from everywhere,
in particular from the host that you want to use RapidMiner on. If the IP addresses work but the hostnames don't then this is a DNS problem. Note that configuring a hostname in the local network will not automatically make that name known to other hosts.
Now issue (2). When RapidMiner talks to RapidAnalytics for the first time it will use the hostname you specify when you add the repository. After that, it uses the one listed in the WSDL files, e.g.
http://localhost:8080/RAWS/RepositoryService?wsdl close to the very bottom:
<soap:address location="http://127.0.0.1:8080/RAWS/RepositoryService"/>
The example above (taken from the initial post) is bad because 127.0.0.1 has a different meaning on each host. It always means the host you are on. JBoss will do its best to fill in a reasonable value here and when your network is well configured this will work. If it is not, you can override this setting by editing server/default/deployers/jbossws-jaxrpc.deployer/META-INF/stack-agnostic-jboss-beans.xml. Therein, look for this line:
<property name="webServiceHost">${jboss.bind.address}</property>
Note that by default, the value of the variable jboss.bind.address is used again. If that does not work, just replace the contents of this tag by whatever is an appropriate hostname and check your WSDL file again. To make sure everything works fine, go to
http://localhost:8080/RAWS/RepositoryService?wsdl and check whether the hostname has been inserted. To be absolutely sure, copy it out of the XML and paste into your browser's URL field. If that works, RapidMiner will connect correctly.
Hope this helps.
Best,
Simon
P.S.: One more common pitfall: When hostnames are not configured correctly and your ISP thinks it is a good idea to use a DNS server that, whenever it cannot resolve a hostname, points you to a search engine, you're in trouble. When that happens in a browser it may be ok because you will see that you arrived at a search form. When that happens to RapidMiner, this can get really confusing: RapidMiner will try to access
http://yourhost:8080/RepositoryRService?wsdl expecting an XML file. But when "yourhost" is misspelt and the DNS server redirects RapidMiner to a search form it will receive some rather meaningless HTML and complain about malformed XML.
