xTour Internet: different Tripduration with same request

[columbs]

Hello everybody,

we are using the xTour server on the internet and with the same request (via raw request runner) we get sometimes

Code: Select all

totalTourPeriod="39208" (i.e. ~10 hours)

and sometimes

Code: Select all

totalTourPeriod="49028" , i.e. ~14 hours 

.
If I run the request on my local xTour server, and I get always totalTourPeriod="39208" . When I change the request from profileName="dimaCar" to profileName="dimatruck" then I get a trou period of almost 14 hours.

My question is: why sometimes use xTour internet the truck profile, although we put in the request to use profileName="dimaCar"?
We have solved our problem (at least we believe to have solved) using deleteBeforeUsage="true" .
Is it possible that different account may use the same dima with ID=1? Or the dima 1 for account x is not the same as for account y?

Thank you in advance abd best regards!
Sebastiano

[Bernd Welter]

Hello Sebastiano,

please provide the request within an answer here - I'd like to ensure that I fully understood the requests meaning before I forward anything to some other moderators. Furthermore we need the URL of the service you use - in case of a configuration topic.

Best regards from Germany,
Bernd

[columbs]

Hello Bernd,

I guess I have found a possible explanation.
We use following URL:
https://xtour-eu-n-test.cloud.ptvgroup. ... quest.html
for some reason we have two accounts (one test and one prod?). both have the same username, but they have different passwords.
My supposition is that DiMa with ID=2 for account 1 is not the same as Dima with ID=2 for account 2. Can you confirm that?

The other issue is: that "profileName="dimaCar"" is ignored, if the previously calculated dima with the same ID has another profile and you don't delete the dima before the usage.

Best regards from the Switzerland,
Sebastiano

[Bernd Welter]

Hello Sebastiano,

sounds valid to me:
The distance matrix storage is related to the username (tenant) and both systems (test / prod) are separated.
So the creation of the two distance matrices could cause the difference. No problem in case of high performance routing (deterministic!) but with traditional routing.

Furthermore:
If the dimaID of a tenant exists and is not deletedBefore the routing profile will be equal to the one used during creation time of the dima.

Best regards,
Bernd

[columbs]

Hello Bernd,
thank you very much for the explanation!

Best regards,
Sebastiano