We proudly present our new PTV xServer API Version 2.12 Release. For the full list of Features and Improvements you can check the corresponding release notes here.
Here are some feature highlights of API Version 2.12:
Added support for external Java installations (64-bit Java 8 required. We recommend the use Amazon Corretto or Orcale Java). Please note that the Java Runtime Environment is no longer integrated in the PTV xServer and need to be installed separately. You find more information on the according Manual Page.
Updated the stored profiles to DataCompatibilityVersion 2 as all current maps are also based on this version. Please ensure that your profiles and map data have the same version. Otherwise the PTV xServer won’t start
The representation of the country results (Name, ISO-2, ISO-3 or license plate code) can be specified in the request
Improved the rendering performance especially when using Feature PTV_(Truck-)SpeedPatterns
Introduced a REST-API for xRoute (Note that the method is experimental)
Added support to plan precombined trips by specifying the attribute ‘groupId’ for each order and the attribute ‘orderGroupConsideration’ in the planning options. (Note that this is experimental)
Alternative depots are also supported for the methods ‘changeTours’ and ‘findChangeToursProposals’. (Note that this is experimental)
Added attribute ‘legReports’ to the element ‘TourReport’ to return information for each leg between two consecutive stops. (Note that this is experimental)
Unloading sequence support
Added stackability restrictions by ItemTypes
For on-premise solutions you can download the latest version from the Customer Area at the Developer Zone.
More Information about JAVA Support and Requirements in the xServer Manual
For cloud solutions we will provide test and production systems based on this release. The Europe test cluster already contains the PTV xServer API version 2.12 release plus all future and finished changes for the next release.
Check the General Information page to get more information about existing PTV xServer internet deployments.
Check out the highlights of the PTV xServer API Version 1.28.
Added support for external Java installations (64-bit Java 8 required, Amazon Corretto and Oracle Java recommended). Please note that the Java Runtime Environment is no longer integrated in the PTV xServer and must be installed separately. You find more Information on the according Manual Page.
Updated the stored profiles to version 2 as all current PTV maps are also based on version 2. Please ensure that your profiles and map data have the same version as otherwise the PTV xServer won’t start.
In case of inconsistent map and Feature Layer data (e.g. mixing different providers or versions by mistake) the PTV xServer won’t start.
PTV xTour Server:
Feature: Added new parameter ‘mergeTransportPointCountPerSite’ that counts all transport points at the same site as single transport point regarding the restriction ‘maxTransportPointCountPerTour’.
From the beginning of time PTV included Oracle JAVA Runtime Environment (JRE) in xServer. Oracle now changed its license policies and any updates for commercial use are only available with a paid subscription. This marks a severe change for PTV especially in the xServer context. We want to be as flexible as possible and want to provide our customers a reliable, easy to maintain product. Our learning from this was, we don’t want to be dependend on one particular JRE provider, but rather work with standard functionality, which is fulfilled by a number of providers.
What will happen?
Starting with the upcoming xServer Versions 1.28 and 2.12, PTV will not ship a JAVA JRE within its xServer products anymore. Instead it relies on a JAVA JRE provided by the operating system environment.
What are the advantages?
PTV Customers are not limited to a specific JAVA distribution – reducing potentional license fees.
You might just use an already installed JRE – reducing the number of JAVA Versions running on your System.
The Server can install security updates for JAVA independent of xServer releases keeping your system security up to date.
What will NOT change?
xServer will work just the same – it still uses JAVA to provide its services.
xServer Internet will take care of that issue for you.
Your integrations doesn’t need any ajustments and will still work and react the same.
The xserver performance will be comparable to an integrated JRE – no change in any direction is to be expected.
Things to consider
Since a JAVA RE is an additional xServer system requirement, you need to take care of that – just like any other JAVA depending software. But we worked hard to make it as simple as possible.