Hi, Thanks a lot for the reply. It was really helpful. But there is a small difference observed executing between locally and on EC2. I tested both locally and on ec-2 same workflow. input--> output. Below are the messages received.
Locally I get workflow invoked message (http://imagebin.org/273926) But on ec-2 (http://imagebin.org/273927) Any idea why this change happens? Thanks a lot for the help ! On Fri, Oct 18, 2013 at 1:03 AM, Lahiru Gunathilake <[email protected]>wrote: > Hi Ishara, > > If you could access the registry successfully that IP has to work with > accessing the messagebox service. > And more importantly is there any url which you can access one of the > services in airavata axis2 services, > Ex: in my local machine I can access Eventing service wsdl as below, > http://149.160.173.22:8080/airavata-server/services/EventingService?wsdl > > Please find that IP address and do the following change and see. > > Ideally you do not have to put any IP address in XBaya GUI if you have > configured Airavata server properly, because when we connect to registry we > pull all the urls from registry and show in the XBaya GUI. > > You need to put whatever accessible URL in the airavata-server.properties > as below, > ip=192.2.33.12 > > Lahiru > > > > > > > On Thu, Oct 17, 2013 at 6:42 AM, Ishara RANATUNGA <[email protected]>wrote: > >> Hi, >> >> I tried to run Airavata Server on Amazon EC-2 instance and tried to >> execute a workflow via xbaya that is started locally. I gave public DNS as >> the host when I configured Airavata registry. >> And when executing the workflow I gave public DNS as the host (replacing >> localhost) of GFac url. >> And kept workflow interpreter url as it is. Although I could load >> registry I got following error when executing the workflow. >> >> http://imagebin.org/273875 >> >> Your help is really appreciated. >> >> >> Thank You ! >> >> >> > > > > -- > System Analyst Programmer > PTI Lab > Indiana University >
