Problem contacting source

[Brad Ediger]

I am trying out VieleRETS for a client and I keep getting the message
"Problem contacting source [SourceName]" at the "Define Resource"
stage of source configuration.

The client uses Interealty (MLXchange) and I have verified that the
username/password I have work for MLXchange. I am using the sample
configuration settings provided on the CRT site for Interealty, and
the following RETS URL:

http://nwa.rets.interealty.com/Login.asmx/Login

Is there a way to monitor the RETS transaction to troubleshoot this
problem?

Thanks!
--
Brad Ediger
Madriska Media Group
www.madriska.com
866-334-4377 toll-free
815-301-3105 fax

[SIMG Joshua Mills]

Brad, My experience shows Interealty uses the GET method for the RETS servers. I spend a decent amount of troubleshooting and when I switched from POST to GET, all my problems went away. Thanks, Joshua Mills www.REAOS.com jos...@reaos.com Brad Ediger wrote: I am trying out VieleRETS for a client and I keep getting the message "Problem contacting source [SourceName]" at the "Define Resource" stage of source configuration. The client uses Interealty (MLXchange) and I have verified that the username/password I have work for MLXchange. I am using the sample configuration settings provided on the CRT site for Interealty, and the following RETS URL: http://nwa.rets.interealty.com/Login.asmx/Login Is there a way to monitor the RETS transaction to troubleshoot this problem? Thanks! -- Brad Ediger Madriska Media Group www.madriska.com 866-334-4377 toll-free 815-301-3105 fax _______________________________________________ viele-dev mailing list viel...@crt.realtors.org http://mail.crt.realtors.org/mailman/listinfo/viele-dev

[Brad Ediger]

I had already tried that... I'm assuming that turning off POST
requests in the source configuration switches to GET. No dice. :-(

On Jan 25, 2006, at 7:16 AM, SIMG Joshua Mills wrote:

> Brad,
>
> My experience shows Interealty uses the GET method for the RETS
> servers. I spend a decent amount of troubleshooting and when I
> switched from POST to GET, all my problems went away.
>
> Thanks,
>
> Joshua Mills
> www.REAOS.com
> jos...@reaos.com
>
>
> Brad Ediger wrote:
>> I am trying out VieleRETS for a client and I keep getting the
>> message "Problem contacting source [SourceName]" at the "Define
>> Resource" stage of source configuration.
>>
>> The client uses Interealty (MLXchange) and I have verified that
>> the username/password I have work for MLXchange. I am using the
>> sample configuration settings provided on the CRT site for

>> Interealty, and the following RET S URL:

[Mark Lesswing]

Brad,

The best choice to trace interaction between a server and client is with a
protocol analyzer like Ethereal.

The second choice would be to turn on tracing within VieleRETS itself. It
requires some editing, but here are the steps:

1) In {INSTALLATION}\common\rets_lite you will find exchange.php.

2) Open this file with an editor like Wordpad (or vi if you are linux) and
turn the following two defines to true:

a. GENERATE_TRANSPORT_TRACE

b. GENERATE_PAYLOAD_TRACE

3) Save the file and retry. Warning, the trace will be sent to your browser.

4) Cut the result from the browser and paste it in an e-mail to me (not the
list!). you can reach me at mles...@crt.realtors.org.

5) Of course, don't forget to turn these setting off again!


I'm preparing Version 1.1 of VieleRETS right now, so this kind of issue is
timely indeed.

Highlights of Version 1.1:

a) Direc t image support for RETS servers that do not support the RETS
GetObject Location option. This results in a 4X performance increase
(Rappatoni).

b) Ability to fetch only changes since the last request. Huge improvement.

c) Ability to match listings to OpenRealty user accounts. Again, huge if you
are an OR user.

d) Minor code efficiencies thanks to the suggestions from the community.

On Wednesday 25 January 2006 08:57, Brad Ediger wrote:
> I had already tried that... I'm assuming that turning off POST
> requests in the source configuration switches to GET. No dice. :-(
>
> On Jan 25, 2006, at 7:16 AM, SIMG Joshua Mills wrote:
> > Brad,
> >
> > My experience shows Interealty uses the GET method for the RETS
> > servers. I spend a decent amount of troubleshooting and when I
> > switched from POST to GET, all my problems went away.
> >
> > Thanks,
> >
> > Joshua Mills
> > www.REAOS.com

> > jos...@reaos.com

> >
> > Brad Ediger wrote:
> >> I am trying out VieleRETS for a client and I keep getting the
> >> message "Problem contacting source [SourceName]" at the "Define
> >> Resource" stage of source configuration.
> >>
> >> The client uses Interealty (MLXchange) and I have verified that
> >> the username/password I have work for MLXchange. I am using the
> >> sample configuration settings provided on the CRT site for

> >> Interealty, and the following RETS URL:

> >>
> >> http://nwa.rets.interealty.com/Login.asmx/Login
> >>
> >> Is there a way to monitor the RETS transaction to troubleshoot
> >> this problem?
> >>
> >> Thanks!
> >> --
> >> Brad Ediger
> >> Madriska Media Group
> >> www.madriska.com
> >> 866-334-4377 toll-free
> >> 815-301-3105 fax
> >>
> >>
> >> _______________________________________________
> >> viele-dev mailing list
> >> viel...@crt.realtors.org
> >> http://mail.crt.realtors.org/mailman/listinfo/viele-dev
> >
> > _______________________________________________
> > viele-dev mailing list
> > viel...@crt.realtors.org
> > http://mail.crt.realtors.org/mailman/listinfo/viele-dev

--
Mark Lesswing
Vice President, Center for REALTOR Technology
National Association of REALTORS
312.329.8273
http://blog.realtors.org/crt

[WOTech - Ross Chapman]

Version 1.1 will be the bomb if you can get listings from Rapattoni to
download faster. Currently, it takes fooooorrreeeevvvvverrr when doing the
photos. Without the photos, it goes pretty quick. And the ability to fetch
changes since last request sounds awesome as well.

Looking forward to it :D

Ross Chapman
402.216.0286

-----Original Message-----
From: viele-de...@crt.realtors.org
[mailto:viele-de...@crt.realtors.org] On Behalf Of Mark Lesswing
Sent: Thursday, January 26, 2006 11:00 AM
To: For discussion on the development of viele rets
Subject: Re: [viele-dev] Problem contacting source

Brad,

The best choice to trace interaction between a server and client is with a
protocol analyzer like Ethereal.

The second choice would be to turn on tracing within VieleRETS itself. It
requires some editing, but here are the steps:

1) In {INSTALLATION}\common\rets_lite you will f ind exchange.php.

2) Open this file with an editor like Wordpad (or vi if you are linux) and
turn the following two defines to true:

a. GENERATE_TRANSPORT_TRACE

b. GENERATE_PAYLOAD_TRACE

3) Save the file and retry. Warning, the trace will be sent to your
browser.

4) Cut the result from the browser and paste it in an e-mail to me (not the
list!). you can reach me at mles...@crt.realtors.org.

5) Of course, don't forget to turn these setting off again!


I'm preparing Version 1.1 of VieleRETS right now, so this kind of issue is
timely indeed.

Highlights of Version 1.1:

a) Direct image support for RETS servers that do not support the RETS

GetObject Location option. This results in a 4X performance increase
(Rappatoni).

b) Ability to fetch only changes since the last request. Huge improvement.

c) Ability to match listings to OpenRealty user accounts. Again, huge if
y ou
are an OR user.

d) Minor code efficiencies thanks to the suggestions from the community.



On Wednesday 25 January 2006 08:57, Brad Ediger wrote:
> I had already tried that... I'm assuming that turning off POST
> requests in the source configuration switches to GET. No dice. :-(
>
> On Jan 25, 2006, at 7:16 AM, SIMG Joshua Mills wrote:
> > Brad,
> >
> > My experience shows Interealty uses the GET method for the RETS
> > servers. I spend a decent amount of troubleshooting and when I
> > switched from POST to GET, all my problems went away.
> >
> > Thanks,
> >
> > Joshua Mills
> > www.REAOS.com
> > jos...@reaos.com
> >
> > Brad Ediger wrote:
> >> I am trying out VieleRETS for a client and I keep getting the
> >> message "Problem contacting source [SourceName]" at the "Define
> >> Resource" stage of source configuration.
> >>

> >> The client uses Interealty (MLXchange) and I have verif ied that

[Mark Lesswing]

Agreed.

Here is a recap of the problem with photos.

1) If a RETS server supports the RETS GetObject Location option, VieleRETS can
grab a URL and defer image retrieval to the end of the batch. This also
allows VieleRETS to make a high speed request, via a URL, to the MLS media
server.

2) Without GetObject Location, VieleRETS needs to create a PROXY that will
make a full RETS-based session call for each image. The PROXY includes RETS
Login, GetObject and Logout transaction. Very slow indeed as you pointed
out.

3) The change allows images to to pulled down at the same time the listing is
within the existing RETS session used for text. This is slower than talking
to a media server, but about 4X faster than the PROXY approach.

I take the blame for PROXY. I mistakenly thought anyone putting servers up
would embrace media servers for images because they are tuned for serving,
well, image s. Also, I though servers that did not support GetObject Location
would be in the minority.

On the "delta" front, the new feature will allow you to drop the practice of
looking for "open" listings only. You can ask anything that has changed.
Listings that were open will now reflect a status of "closed":)

On Thursday 26 January 2006 11:04, WOTech - Ross Chapman wrote:
> Version 1.1 will be the bomb if you can get listings from Rapattoni to
> download faster. Currently, it takes fooooorrreeeevvvvverrr when doing the
> photos. Without the photos, it goes pretty quick. And the ability to
> fetch changes since last request sounds awesome as well.
>
> Looking forward to it :D
>
> Ross Chapman
> 402.216.0286
>
> -----Original Message-----
> From: viele-de...@crt.realtors.org
> [mailto:viele-de...@crt.realtors.org] On Behalf Of Mark Lesswing
> Sent: Thursday, January 26, 2006 11:00 AM
> To: Fo r discussion on the development of viele rets
> Subject: Re: [viele-dev] Problem contacting source
>
> Brad,
>
> The best choice to trace interaction between a server and client is with a
> protocol analyzer like Ethereal.
>
> The second choice would be to turn on tracing within VieleRETS itself. It
> requires some editing, but here are the steps:
>

> 1) In {INSTALLATION}\common\rets_lite you will find exchange.php.

> > > servers. I spend a d ecent amount of troubleshooting and when I

> > > switched from POST to GET, all my problems went away.
> > >
> > > Thanks,
> > >
> > > Joshua Mills
> > > www.REAOS.com
> > > jos...@reaos.com
> > >
> > > Brad Ediger wrote:
> > >> I am trying out VieleRETS for a client and I keep getting the
> > >> message "Problem contacting source [SourceName]" at the "Define
> > >> Resource" stage of source configuration.
> > >>

> > >> The client uses Interealty (MLXchange) and I have verified that