[kepler-users] Opal 2.0 and Kepler 1.0

[Jianwu Wang]

Hi Luca,

    Thanks for your info. It turned out that I have other modules which 
also have axis.jar, but the version of these two are different. It works 
for me after I change suite to Kepler.

Hi Tirath,

    Luca and I are working and testing on the instructions to import 
opal into Kepler 1.0. We will let you know once we figure it out.

Best wishes

Sincerely yours

Jianwu Wang
jianwu at sdsc.edu
http://users.sdsc.edu/~jianwu/

Scientific Workflow Automation Technologies (SWAT) Laboratory
San Diego Supercomputer Center 
University of California, San Diego
San Diego, CA, U.S.A. 



Luca Clementi wrote:
> Jianwu Wang wrote:
>> Hi Luca,
>>
>>     I got the following exception when trying to open your workflow 
>> with Kepler trunk. Would you please have a look? Thanks.
>>
>>       [run] java.lang.NoSuchFieldError: DOCUMENT
>>       [run]     at 
>> edu.sdsc.nbcr.opal.AppServicePortTypeSoapBindingStub._initOperationDesc1(AppServicePortTypeSoapBindingStub.java:33) 
>>
>
>
>>
>>  I got another exception when I tried to open it for the second time.
>>
>>       [run] java.lang.NoClassDefFoundError
>>       [run]     at 
>> edu.sdsc.nbcr.opal.AppServiceLocator.getAppServicePort(AppServiceLocator.java:55) 
>>
>
> Hi Jianwu,
> that's weird. Why two different errors?
> I tested the WF yesterday and to day after SVN update and in both 
> cases it worked.
>
> The only problem I can think about is the AXIS library that is in the 
> modules/common/lib/jar/axis.jar
>
> Maybe you are not importing that?
>
> Luca
>
>
>>
>> Best wishes
>>
>> Sincerely yours
>>
>> Jianwu Wang
>> jianwu at sdsc.edu
>> http://users.sdsc.edu/~jianwu/
>>
>> Scientific Workflow Automation Technologies (SWAT) Laboratory
>> San Diego Supercomputer Center University of California, San Diego
>> San Diego, CA, U.S.A.
>>
>>
>> Luca Clementi wrote:
>>>
>>>
>>>> Tirath Ramdas wrote:
>>>>> Hi,
>>>>>
>>> Dear Tirath,
>>> see below...
>>>
>>>>> I would like to deploy some apps with Opal 2.0, and to orchestrate 
>>>>> these with Kepler 1.0.0. For what it's worth, the 
>>>>> WebServicesAndDataTransformation example workflow does work for me.
>>>>>
>>>>> I've set up opal-ws-2.0 with jakarta-tomcat-5_0_30, with the 
>>>>> "/bin/date" sample service, locally (i.e. on the same system I'm 
>>>>> running Kepler). I get the desired result running the service with 
>>>>> the Opal generic client, with launchJob [1], and subsequently with 
>>>>> the queryStatus/getOutputs methods. Unfortunately, I can't repeat 
>>>>> this with Kepler, pointing to the endpoint 
>>>>> http://localhost:8080/opal2/services/DateServicePort?wsdl.
>>>>>
>>>>> [1] java edu.sdsc.nbcr.opal.GenericServiceClient -l 
>>>>> http://localhost:8080/opal2/services/DateServicePort -r launchJob
>>>>>
>>>>> I give some arbitrary input to the launchJobInput port which the 
>>>>> actor instantiates the moment I specify the endpoint and method 
>>>>> (launchJob), basically treating this input like a trigger. The 
>>>>> result is the same if it's a constant (1) or an empty string: the 
>>>>> workflow returns "executions finished" almost instantly, with no 
>>>>> output on either the launchJobOutput port or the error port. 
>>>>> Looking at the Opal dashboard, it doesn't look like any of these 
>>>>> jobs get started.
>>>
>>> If I have understood you are trying to use the generic web service 
>>> actor, and for that actor you need to input a string containing a 
>>> properly formatted SOAP XML request, which is not very easy to make.
>>>
>>> For this reason we have developed a OpalClient actor that can be 
>>> used to invoke opal services. You can simply drag and drop the opal 
>>> actor set the URL of your service in the "serviceURL" parameter.
>>>
>>> After this you have to type the command line of set the various 
>>> properties of the actor. Input ports are input files, and outputs 
>>> are the URL of the output files.
>>>
>>> Attached an example which invoke meme and mast.
>>>
>>> Regards,
>>> Luca
>>>