Loading...
 
ESA > Join & Share > Forums > HMA Forum > Interface OGC 06-131r6 doesn't work with SSE Portal

HMA Forum

Help

Show posts:
Jump to forum:

Interface OGC 06-131r6 doesn't work with SSE Portal

Hello!

Could you please help me to figure out what's wrong with my service registration? I have deployed "an ebXML Registry Repository implemetation with Earth Observation extensions" and populated one with some metadata. I register the servce on the SSE Portal using "Catalogue Interface: OGC 06-131r6 v0.2.4, EO Products Extension Package for ebRIM (ISO/TS 15000-3) Application Profile". It seems my catalogue installation doesn't get request at all (while portal shows "An error occurred while processing your request. GetRecords failed for the following collection(s)"). I'm sure that my catalogue SOAP location is correct.
Looking through BPEL console I have found no WSDL that refer my service location, like it was for EOLI interface. I have tried to re-register service using empty interface, delete all the related BPEL processes, and then re-register the service again as OGC 06-131r6 v0.2.4. It doesn't help.

Regards,
Ilya


Re: Interface OGC 06-131r6 doesn't work with SSE Portal

Hi Ilya,
Can you confirm that your endpoint is working correctly? I received the following while running some tests:

CONNECTION ERROR. ERROR MESSAGE: (302)Moved Temporarily

Can be an arrror on my side.

Regards,
Ivo.

> Hello!
>
> Could you please help me to figure out what's wrong with my service registration? I have deployed "an ebXML Registry Repository implemetation with Earth Observation extensions" and populated one with some metadata. I register the servce on the SSE Portal using "Catalogue Interface: OGC 06-131r6 v0.2.4, EO Products Extension Package for ebRIM (ISO/TS 15000-3) Application Profile". It seems my catalogue installation doesn't get request at all (while portal shows "An error occurred while processing your request. GetRecords failed for the following collection(s)"). I'm sure that my catalogue SOAP location is correct.
> Looking through BPEL console I have found no WSDL that refer my service location, like it was for EOLI interface. I have tried to re-register service using empty interface, delete all the related BPEL processes, and then re-register the service again as OGC 06-131r6 v0.2.4. It doesn't help.
>
> Regards,
> Ilya


Re: Re: Interface OGC 06-131r6 doesn't work with SSE Portal

Hi Ivo,

Yes, I'm sure. At least build-in test facilities of ebRR and some simple tests using SoapUI were succesfull for the service. I'm also sure the installation is accessible from outside of our corporate network. I just have succefully opened http://genesis.satellite.dvo.ru/catalogue/webservice?wsdl via webbrowser.

Regards,
Ilya

> Hi Ilya,
> Can you confirm that your endpoint is working correctly? I received the following while running some tests:
>
> CONNECTION ERROR. ERROR MESSAGE: (302)Moved Temporarily
>
> Can be an arrror on my side.
>
> Regards,
> Ivo.


Re: Re: Re: Interface OGC 06-131r6 doesn't work with SSE Portal

Ilya have a look at the XML being sent and let me know if there are some unset properties, in the meantime I will contact Spacebel to shed some light on this.

Ivo.

> Hi Ivo,
>
> Yes, I'm sure. At least build-in test facilities of ebRR and some simple tests using SoapUI were succesfull for the service. I'm also sure the installation is accessible from outside of our corporate network. I just have succefully opened http://genesis.satellite.dvo.ru/catalogue/webservice?wsdl via webbrowser.
>
> Regards,
> Ilya
>
> > Hi Ilya,
> > Can you confirm that your endpoint is working correctly? I received the following while running some tests:
> >
> > CONNECTION ERROR. ERROR MESSAGE: (302)Moved Temporarily
> >
> > Can be an arrror on my side.
> >
> > Regards,
> > Ivo.


Re: Re: Re: Re: Interface OGC 06-131r6 doesn't work with SSE Portal

Hi Ivo,

Some properties are unset. I have tried to add some searchable fields, like it is done at http://services.eoportal.org/portal/order/PrepareOperation.do?serviceId=66807780&operation=Search. The properties are still unset, just some more were added.

I'm not very familiar with BPEL Console (btw it works ugly with all the webbrowsers except IE6). If I not mistaken, GetRecords is the actual body of the SOAP message that is being send to the service. If I send one directly via soapUI, I got following in ebRR log:

Dec 21, 2011 8:54:35 PM be.kzen.ergorr.query.QueryBuilderImpl2 getReturnType
INFO: Invalid QName in ElementSetName elemens typeNames attribute

I expected to see an output similar to one I get when perform search from the portal. Probably I'm wrong somwhere.

You can find the request I have extracted from "View Raw XML", request and response I used with SoapUI here.

Regards, Ilya

P.S. Portal always renames the catalogue workflows each time I re-register it. May be this is also somehow related to issue?

> Ilya have a look at the XML being sent and let me know if there are some unset properties, in the meantime I will contact Spacebel to shed some light on this.


Re: Re: Re: Re: Re: Interface OGC 06-131r6 doesn't work with SSE Portal

Hi Ilya,
The BPEL console only works properly with IE.
The following XSL produces a correct GetRecords (link to file), you can access it if you login as a service provider. Try to use it and then copy the from the BPEL console and paste it in SoapUI, you should get a proper response.
Still the SSE is unable to receive a proper response, and the error message from the server doesn't help, can you have a look at the server logs for any clue on the error?
Anyway I have contacted Spacebel and will let you know as soon as possible.

Kind regards,
Ivo.

> Hi Ivo,
>
> Some properties are unset. I have tried to add some searchable fields, like it is done at http://services.eoportal.org/portal/order/PrepareOperation.do?serviceId=66807780&operation=Search. The properties are still unset, just some more were added.
>
> I'm not very familiar with BPEL Console (btw it works ugly with all the webbrowsers except IE6). If I not mistaken, GetRecords is the actual body of the SOAP message that is being send to the service. If I send one directly via soapUI, I got following in ebRR log:
>
> Dec 21, 2011 8:54:35 PM be.kzen.ergorr.query.QueryBuilderImpl2 getReturnType
> INFO: Invalid QName in ElementSetName elemens typeNames attribute
>
> I expected to see an output similar to one I get when perform search from the portal. Probably I'm wrong somwhere.
>
> You can find the request I have extracted from "View Raw XML", request and response I used with SoapUI here.
>
> Regards, Ilya
>
> P.S. Portal always renames the catalogue workflows each time I re-register it. May be this is also somehow related to issue?
>
> > Ilya have a look at the XML being sent and let me know if there are some unset properties, in the meantime I will contact Spacebel to shed some light on this.


Re: Re: Re: Re: Re: Re: Interface OGC 06-131r6 doesn't work with SSE Portal

Adding to the above, the main issue is with the prefix "rim:" in the typeNames attribute, that is the relevant change on the default XSL.

ESRIN will close in the following week so we will only be able to reply again in January.

Kind regards,
Ivo.


> Hi Ilya,
> The BPEL console only works properly with IE.
> The following XSL produces a correct GetRecords (link to file), you can access it if you login as a service provider. Try to use it and then copy the from the BPEL console and paste it in SoapUI, you should get a proper response.
> Still the SSE is unable to receive a proper response, and the error message from the server doesn't help, can you have a look at the server logs for any clue on the error?
> Anyway I have contacted Spacebel and will let you know as soon as possible.
>
> Kind regards,
> Ivo.
>
> > Hi Ivo,
> >
> > Some properties are unset. I have tried to add some searchable fields, like it is done at http://services.eoportal.org/portal/order/PrepareOperation.do?serviceId=66807780&operation=Search. The properties are still unset, just some more were added.
> >
> > I'm not very familiar with BPEL Console (btw it works ugly with all the webbrowsers except IE6). If I not mistaken, GetRecords is the actual body of the SOAP message that is being send to the service. If I send one directly via soapUI, I got following in ebRR log:
> >
> > Dec 21, 2011 8:54:35 PM be.kzen.ergorr.query.QueryBuilderImpl2 getReturnType
> > INFO: Invalid QName in ElementSetName elemens typeNames attribute
> >
> > I expected to see an output similar to one I get when perform search from the portal. Probably I'm wrong somwhere.
> >
> > You can find the request I have extracted from "View Raw XML", request and response I used with SoapUI here.
> >
> > Regards, Ilya
> >
> > P.S. Portal always renames the catalogue workflows each time I re-register it. May be this is also somehow related to issue?
> >
> > > Ilya have a look at the XML being sent and let me know if there are some unset properties, in the meantime I will contact Spacebel to shed some light on this.


Re: Re: Re: Re: Re: Re: Re: Interface OGC 06-131r6 doesn't work with SSE Portal

Hi Ivo,

Thank you for the XSL provided, I'll perform the test bit later.

What for server log, do you mean catalina.out? I already have posted some output from one. I definetely can peform the test from the blank page again and provide the whole file to you and to inspect it myself more accurately.

Our best wishes to you and your collegues for upcoming Christmas and New Year!
Ilya


Re: Re: Re: Re: Re: Re: Re: Re: Interface OGC 06-131r6 doesn't work with SSE Portal

Hi Ilya,
I was trying to do some additional tests to clarify some details so that we can fix this problem but it seams that your server is not responding, I get an internal error: "Could not load objects from database". Is the server working properly?

Kind regards,
Ivo.


Re: Re: Re: Re: Re: Re: Re: Re: Re: Interface OGC 06-131r6 doesn't work with SSE Portal

Hi Ivo,

Sorry for delayed answer, the holidays in Russia are shifted to Janurary (due to Ortodox Christmas at January 7). I have checked the log and ftp://toolbox.satellite.dvo.ru:2120/ebrr2sse_issue/2/catalina.out is the part of it that probably related to the test you mention (there are few more similar exception staktraces). I hope this helps. I have restarted the server also.

By the time I will try to deploy fresh installation at another server to have something to compare with.

Regards,
Ilya

> Hi Ilya,
> I was trying to do some additional tests to clarify some details so that we can fix this problem but it seams that your server is not responding, I get an internal error: "Could not load objects from database". Is the server working properly?
>
> Kind regards,
> Ivo.


Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Interface OGC 06-131r6 doesn't work with SSE Portal

Hi Ivo,

I have tried another ErgoRR installation, got the same result - and finally given it up. Now I have deployed the catalogue under Toolbox and it works ok (I'm not sure if it is compatible with all the HMA tests, but at least it works with the portal). My issue is seems to be solved for now. Thank you for the assistance.

The remaining question is - why the portal doesn't work with ErgoRR, but does with Toolbox? It belive the issues isn't related to my installation only, but probably for any ErgoRR installation of this version. If you are about to investigate the issue using my ErgoRR installation - just ask and I'll try to do my best to provide you with necessary information. I will keep the instalation running for next couple of weeks or more, if you need.

Best regards,
Ilya


Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Interface OGC 06-131r6 doesn't work with SSE Portal

Hi Ilya,
I will check for known issues regarding the SSE and the ErgoRR, but we support the use of the SSE with the toolbox, the problem may be on the ErgoRR, I will let you know if I discover anything.

Kind regards,
Ivo.


Re: Re: Re: Interface OGC 06-131r6 doesn't work with SSE Portal

Hi Ilya,
I successfully queried your endpoint and it is working correctly. It seams that there are some unset parameters in the query sent by the SSE, still haven't understood why.
You can see the message your service is sending in the BPEL console by selecting the correct instance, selecting "Audit", and then "View Raw XML", have a look.

Ivo.

> Hi Ivo,
>
> Yes, I'm sure. At least build-in test facilities of ebRR and some simple tests using SoapUI were succesfull for the service. I'm also sure the installation is accessible from outside of our corporate network. I just have succefully opened http://genesis.satellite.dvo.ru/catalogue/webservice?wsdl via webbrowser.
>
> Regards,
> Ilya
>
> > Hi Ilya,
> > Can you confirm that your endpoint is working correctly? I received the following while running some tests:
> >
> > CONNECTION ERROR. ERROR MESSAGE: (302)Moved Temporarily
> >
> > Can be an arrror on my side.
> >
> > Regards,
> > Ivo.



Re: Interface OGC 06-131r6 doesn't work with SSE Portal

Hi Ilya,
I could not yet identify the problem, I will open an investigation with the maintainer and keep you up-to-date.

Regards,
Ivo.

> Hello!
>
> Could you please help me to figure out what's wrong with my service registration? I have deployed "an ebXML Registry Repository implemetation with Earth Observation extensions" and populated one with some metadata. I register the servce on the SSE Portal using "Catalogue Interface: OGC 06-131r6 v0.2.4, EO Products Extension Package for ebRIM (ISO/TS 15000-3) Application Profile". It seems my catalogue installation doesn't get request at all (while portal shows "An error occurred while processing your request. GetRecords failed for the following collection(s)"). I'm sure that my catalogue SOAP location is correct.
> Looking through BPEL console I have found no WSDL that refer my service location, like it was for EOLI interface. I have tried to re-register service using empty interface, delete all the related BPEL processes, and then re-register the service again as OGC 06-131r6 v0.2.4. It doesn't help.
>
> Regards,
> Ilya



Re: Interface OGC 06-131r6 doesn't work with SSE Portal

Dear Ivo,

I haven't encountered the problem you mentioned, but got another one. I'm still not able to perform search using the registration.

Portal says:
An error occurred while processing your request.



ebRR logs:

Dec 19, 2011 11:24:15 PM be.kzen.ergorr.query.QueryBuilderImpl2 initSortBy
INFO: SortBy init
Dec 19, 2011 11:24:15 PM be.kzen.ergorr.query.QueryBuilderImpl2 recurseQueryOperator
FINE: queryOperator: class be.kzen.ergorr.model.ogc.And
Dec 19, 2011 11:24:15 PM be.kzen.ergorr.query.QueryBuilderImpl2 recurseQueryOperator
FINE: queryOperator: class be.kzen.ergorr.model.ogc.PropertyIsEqualTo
Dec 19, 2011 11:24:15 PM be.kzen.ergorr.query.xpath.XPathToSqlConverter process
FINE: eval xpath: /rim:RegistryPackage/rim:RegistryObjectList*/rim:RegistryObject/@id
Dec 19, 2011 11:24:15 PM be.kzen.ergorr.query.xpath.XPathToSqlConverter process
INFO: Not a valid child node: RegistryObjectList


Is there any way to debug the registration? Is it possible to see reguest that the portal sends to my catalogue?

Regards, Ilya



Re: Interface OGC 06-131r6 doesn't work with SSE Portal

Dear Ilya,
I'm glad you managed to solve your problem. In the SSE Test Portal if you encounter the following error when performing a search:

"Error: form.cloudCoverPerc is undefined Source File: ..."

If it is a standard service make sure to check the combo to include cloud coverage percentage field in the second page of the service deploy wizard or if it is a custom service include:

"yes"

This issue is being addressed.

Kind regards,
Ivo.



Re: Interface OGC 06-131r6 doesn't work with SSE Portal

Solved. Service location should be entered in for http://localhost://webservice, NOT http://localhost:/


Show posts:
Jump to forum: