1) Did you restart the RETS server after the changes? (Mark is this required still? I forget. In the old days it was.)
2) Have you tried another client (like the awesome and free ezRETS[1]) to verify the findings?
3) Are all the metadata items like default set with sane values? (i.e. A client will never show you something with -1 in default.)
Keith
[1] I'm the main author of ezRETS, I get to do hyperbole
On Jul 5, 2011, at 7:20 AM, Orville wrote:
> When we make any changes to the mappings between our database and RETS
> through the RETS server (Variman Admin 3.2.3) and save it, although
> the metadata file is created successfully, the mapped fields are not
> visible to the Client (Rets Connector 1.0 MarketLinx). We are able to
> make a successful connection to the RETS Server so it does not seem to
> be a connection issue.
>
> Any clues would be appreciated
--
Keith T. Garner - kga...@realtors.org - 312-329-3294 - http://realtor.org/
National Association of REALTORS® - VP - Information Technology Services
> A few things come to mind...
>
> 1) Did you restart the RETS server after the changes? (Mark is this
> required still? I forget. In the old days it was.)
By default, it is, though there is a way to enable update notification
through Spring.
> [1] I'm the main author of ezRETS, I get to do hyperbole
Nothing wrong with pride in authorship!
> On Jul 5, 2011, at 7:20 AM, Orville wrote:
>
>> When we make any changes to the mappings between our database and
>> RETS
>> through the RETS server (Variman Admin 3.2.3) and save it, although
>> the metadata file is created successfully, the mapped fields are not
>> visible to the Client (Rets Connector 1.0 MarketLinx). We are able to
>> make a successful connection to the RETS Server so it does not seem
>> to
>> be a connection issue.
>>
>> Any clues would be appreciated
And, check the logs. Turn logging up to DEBUG, restart your server and
see if it reports that it is seeing the tables for your resources/
classes. You'll see a series of messages like:
-> Found metadata.xml at: /Users/admin/Documents/NAR/variman/
demo_metadata/metadata.xml
05 Jul 2011 18:12:41,945 DEBUG [ ]
org.realtors.rets.server.metadata.XmlMetadataDao
-> Merging metadata into a single XML document.
05 Jul 2011 18:12:42,545 DEBUG [ ] org.realtors.rets.server.RetsServer
-> Initializing group filter
05 Jul 2011 18:12:42,549 DEBUG [ ] org.realtors.rets.server.RetsServer
-> Setting tables for Property:COM
> I observed that the way RETS saved the first four table
> entries(ListingID,headline,AgencyID,Price ) and newly added 5th table
> entry (town) are the different.
>
> That might be the the reason of this issue of newly added field is not
> available to client.
>
> If this is the case , let us know if we had missed some RETS setttings
> that should fix the problem.
>
Did you play with the metadata model or the strict flags at all? That
last row is in a different order than the column map shows it should
be. You can try deleting it using the GUI, but if all else fails, open
the file in your favorite editor and delete the row. Then try adding
it again.
>
> Thanks !for your reply.
>
> The steps I followed :
>
> 1.Installed the variman RETS server.
> 2.Added the database properties and test the connection.
> 3.Added the user and user groups.
> 4.Enter the fields in "System" node in the Metadata tab.
> 5.Try add the "Resource" but unable to add the the resource. It was
> giving the vaildation error "ClassCount: A positive whole number."
> as strict flag is enabled by default.
> 6. I then disabled the strict flag and then added resource , class &
> tables field success fully.
Yeah, I duplicated it. Looks like there is an issue when you add your
very first class to a resource. Note that when in strict mode, the
field values are validated against what the RETS spec says they should
be ... and if you want to pass compliance, you need to be in strict
mode. But, in strict mode, the # of classes is defined as a positive
(non-zero) number. So it fails checking. You will have to turn off
strict just to get the very first class in.
It also appears that the column order is affected when in strict mode
and when not in strict mode. If you change the strict flag, you need
to select "reload metadata" to make sure things get shuffled around
properly. If you just toggle strict without that, the column ordering
appears to get messed up.
The safest way to do this is probably to turn off strict before adding
that very first class to a resource. Next, save the data. Then turn
strict back on and exit the GUI. Re-enter the GUI and then you can
continue editing.
> Hi Mark,
>
> We are using the RETS connector 1.0(v 1.1.1.6238) as Client and
> Variman Admin Server(v.3.2.3).Both are on the same machine.
> The RETS connector 1.0 does behave erratically sometimes that it does
> not connect to the RETS server on the first few tries but connects
> after multiple tries. When it failed we are getting the below message.
There are one or two clients out there that mishandle cookies and
associated authentication headers. As a result, they lose track of the
authentication "stuff" and in turn, causes Variman to disassociate the
session ID with the authentication response. The log below seems to
indicate this is one of them. Note in the Authorization header that
the "nc" is 1 ... it should only be 1 at the start of a a session.
Nothing Variman can do about that.
> Please provide us any link if any , explaining the example for
> downloading the image through the RETS connector. That would be the
> helpful.
You're asking a fundamental RETS question. See the RETS spec in
section 5.4 about the Location parameter. That determines whether or
not (if the sever supports it) you'll get the images or a URI to the
image.
As for how you do that with RetsConnector, I can't help you there. I
suggest you contact the supplier of RetsConnector.