[Dukesbiz]

Jeff, It is my understanding that you use VPN to make a connection to the DMS. However, once you connect to the DMS how are you gathering Data from it? Are there automated reports that are run? If so. are there version issues within particular DMS systems (If version upgrade, do you also have to update your query?". If so. this would make for a large headache from a vendor standpoint, trying to keep tabs on what system everybody is using and when their system is upgraded, etc...

Garrett

[Viracocha]

Originally Posted by Dukesbiz

We would like to identify the benefits & application to each of the following:
- ReyRey Querybuilder
- VPN Access
- Other recommended access points (Aside from becoming a Certified Interface)

Our requirements are as follows:
- RO information at time of vehicle arrival to dealer
- Vehicle Specifications
- Customer Information
- Name
- Contact Info/Preference

Would the suggested integration point be feasible for what I need?

Once again, Thank You and I look forward to future contributions by all.

Garrett

Hi Garrett.
There are two ways of doing data capture using Query Builder:

1: Create the queries and install them on a client on the customers' network. The application can be run utilizing the built in scheduler, which in essence logs in as a specified user, runs the query and dumps a flat file to a predefined folder on the client. In the past, we created a custom sql connector to encrypt and upload the data from that folder on a matching schedule to a server on our network. The pros to this method are:
i> No VPN required as all the networks I have encountered dont engage in outbound filtering of traffic
ii> Can be scheduled to run at all hours, with any frequency with little to no intervention from the dealership staff (aside from the odd reboot)
Cons:
i> You are relying on a machine existing unmolested and powered up on a clients network
ii> Hardware failures require a site visit
iii> Without a remote access client of some sort the scripts are not adjustable without a visit (ie if you need to change the data you are pulling)

2: THe second method would require you to use a VPN to connect to a client network to run a query on a locally installed eralink, obvious advantage is you can change scripts and frequency rather easily, data is gathered local on your machine. Cons are dealers sometimes dont have routers configured or able to run VPN client tunnels, may require 3rd party assistance.

[JeffSwearingen]

HI Garrett.

Thanks for your question, I don't want to hijack this thread with talk of our product.

I'd be happy to connect you with a product specialist to see if we can help you replace the Reynolds modem with SecureLink. Feel free to e-mail me and I'll get you in touch with an engineer.

Same offer goes to anyone else, along with a free trial if it looks like we can help you.

Thanks again.

Jeff

[Dukesbiz]

Thank You for the Reply! Option 1 looks like the methodology we will be taking. Is this scalable? or is it very time intensive?
A little more digging around and we will be making a decision. We would like to become an RCI vendor to eliminate most thoughts of integration issues but time and the fact that this is a new product seems to be the issue. Thanks for the input...Any additional ideas are always appreciated.

Garrett

Originally Posted by Viracocha

Hi Garrett.
There are two ways of doing data capture using Query Builder:

1: Create the queries and install them on a client on the customers' network. The application can be run utilizing the built in scheduler, which in essence logs in as a specified user, runs the query and dumps a flat file to a predefined folder on the client. In the past, we created a custom sql connector to encrypt and upload the data from that folder on a matching schedule to a server on our network. The pros to this method are:
i> No VPN required as all the networks I have encountered dont engage in outbound filtering of traffic
ii> Can be scheduled to run at all hours, with any frequency with little to no intervention from the dealership staff (aside from the odd reboot)
Cons:
i> You are relying on a machine existing unmolested and powered up on a clients network
ii> Hardware failures require a site visit
iii> Without a remote access client of some sort the scripts are not adjustable without a visit (ie if you need to change the data you are pulling)

2: THe second method would require you to use a VPN to connect to a client network to run a query on a locally installed eralink, obvious advantage is you can change scripts and frequency rather easily, data is gathered local on your machine. Cons are dealers sometimes dont have routers configured or able to run VPN client tunnels, may require 3rd party assistance.

[tracourt]

Originally Posted by iceman101

Matt,

Thanks for you help on this. Does all Reynolds and Reynolds clients use the Eralink interface? This would mean the Ip address would be found in the same places for all dealerships? I am trying to find an easy way to have dealerships locate the correct IP address of the Reynolds box so after a successful VPN type connection we could telnet to their box. Any other ideas out there?

If memory serves me well, go to Setup, Communications, Windows Sockets, then Setup. The IP will be in that window.

[umer.autojini]

Does anyone know what can be passed to ERAVehInvRequest to return more then 100 records.

[toms]

Originally Posted by mattwatson81

This looks like a call to the RCI interface?

Hi, Matt?

Do you know what RCI really is? The Post shows the schema of b2b.reyrey.com is another interface.

[toms]

After spending a few hours with forum, I found there are some experts on Reynolds DMS. Could anybody help me to answer this question?

What is RCI (Reynolds Certified Interface)? Is it a channel (interface) for third party program to talk with? Is it SOAP interface which needs fee to talk with? Finally, what kind of consequences (business and legal) to the dealer and third party service provider could be if third party program talk to ERA to get some reports without RCI?

Thanks

[Jarrett]

Disclaimer: These are my views and obviously not endorsed by any DMS provider

1) RCI (reynolds certified interface) is an opportunity for Reynolds to charge vendors to interact with dealer owned data. Ex. The higher gear group after spending some outrageous amount of money to be "RCI" enabled pulled out of the agreement and does not support RCI data interaction between ERA and their product.

To define what RCI Is: It is software installed in the ERA System that allows SOAP based calls to read,write and update the database. It is fairly easy to program against, assuming you can find the correct fields / structure. Not all database fields are represented. Arkona has a similar concept with OpenTrack and are much nicer to work with.

2) It is a SOAP interface, however my server did not need a "FEE" to talk... See post #5 against this thread

3) To answer your questions about legal consequences regarding circumnavigating RCI to commence data exchange with reynolds; I am not going to touch that with a ten foot pole.
Business consequences are simple, if your non-certified interface stops working you cant call and complain to reynolds.

Hope this helps,

If you need any addition help in data access pm me and I will get you pointed in the right direction

Jarrett

[Viracocha]

Originally Posted by toms

After spending a few hours with forum, I found there are some experts on Reynolds DMS. Could anybody help me to answer this question?

What is RCI (Reynolds Certified Interface)? Is it a channel (interface) for third party program to talk with? Is it SOAP interface which needs fee to talk with? Finally, what kind of consequences (business and legal) to the dealer and third party service provider could be if third party program talk to ERA to get some reports without RCI?

Thanks

RCI was mostly described in the above post, what Reynolds charges for is to provide the security in the data transaction. Basically you request the data through the dealers' sdcc server, which in turn passes the request to the era box. If you dont have access to the same subnet that the Reynolds server is on it would be the only way to ensure your 2 way integration works.