Starting this week we offer a document describing the installation and configuration of PTV xServer add-on AJAX Maps (PTV AJAX Maps Servlet).
Have you already registered for “PTV xServer Performance Tuning“? For further information please note our post dated January 12, 2012.
[Edit 25.01.2012] See presentation of webinar
On Tuesday, January 24, 2012 the webinar “PTV xServer Performance Tuning” will take place from 15:00 – 16:00 CET. The session will cover the following topics:
- Basic deployment scenarios for optimizing the performance
- Checking hardware requirements
- Configuring PTV xServer for optimal performance
- Optimizing the client
- Performance monitoring and analysis
- Get your own benchmarks using the PTV xServerRequestRunner
Regsiter here to receive the session ID. If you already registered for past sessions, you will automatically receive the ID few days before the webinar.
With this tool you can easily create and maintain distance matrices based on PTV xDima Server. The tool supports the complete lifecycle of distance matrices:
- createDima / deleteDima
- calculateDistanceTable / deleteDistanceTable
- cancelCalculation / getCalculationProgress / unlockDima
- getLocations / getDimaProfile
- getDistPeriod / setDistPeriod
- importDima / exportDima
… the first official tutorial for PTV Developer Components in YouTube.
Watching the video you will find a lot of meaningful instructions for installing PTV Developer Components.
- How to install PTV xServer and PTV Maps?
- What additional keys do I need to run PTV xServer?
- Do I have to configure something?
- Can I start PTV xServer as services?
- How can I check that PTV xServer run correctly?
Use the video to find the answers! We would be pleased to receive your feedback about the video. Do you think it is a proper instrument to enhance our software documentation?
We would like to extend the manuals explaining typical use cases. This should be a comfortable guide (easy to listen) to learn more about the use of our developer components.
Please post a comment, write in our forum or send an email! It’s up to you if PTV speeds up the efforts to create more videos showing different use cases in the context of geo-services, field force optimization, trip planning, track and tracing, navigation and a lot more.
Dr. Michael Nutto
Product Manager of PTV Developer Commponents
All ancient PTV MapServer versions result in a registry-based integration of the PTV MapServer-COM-DLLs. When the installation is complete, the new PTV MapServer version is also available to all other applications using it – many customers maintain a map&guide and an own developed application on their own system.
A real disadvantage of this system-wide PTV MapServer installation is the risk of overwriting the configuration of an already existing PTV MapServer-application, which is highly bounded to its own PTV MapServer version. This behaviour results into the so-called DLL-hell.
Commonly a PTV MapServer update should not cause any problems, because the PTV MapServer interface is kept downwards compatible – but due to its huge amount of functionality, its semantic behaviour may change unintentionally from time to time. So, the opportunity to provide an application with its own dedicated and tested PTV MapServer is preferable.
To achieve this goal, the PTV MapServer SDK 5.6 supports a technology called “win32 side-by-side”. With Windows XP, Microsoft introduced this technology. Central point is an application specific manifest, which is an XML file matching a predefined schema (further details can be seen in http://msdn2.microsoft.com/en-us/library/aa375632.aspx). Inside, it refers to all COM-DLLs used by this application, especially their locations in the filesystem. To make these DLLs only known to the application, a subfolder of the application exe can be used.
To provide a convenient way for a registry-free installation, the PTV MapServer InstKit Setup contains a manifest with all existing PTV MapServer-DLLs. The references of these DLLs all link to a subfolder named PTV.Logistics.MapServer, to where the InstKit setup copies these DLLs. This happens, if an exe-path is specified in the command line of the InstKit setup:
setup.exe -s -ptv:Path"c:/programs/MyCompany/MyApplication.exe"
Please pay attention for a correct specification of the parameter -ptv:Path: Spelling mistakes result in a registry-based installation, which is apparently not desired. Also the “-characters have to be used, independently of existing spaces inside the pathname.
If the spelling is correct, the InstKit-setup
- copies all PTV MapServer-DLLs to the folder c:/programs/MyCompany/PTV.Logistics.MapServer, whereat no COM registration is performed. So, these DLLs remain unknown to other applications.
- copies and renames the application-specific manifest to c:/programs/MyCompany/MyApplication.exe.manifest. This naming convention (appending .manifest at the end of the exe-filename) is mandatory for a correct functioning. This application-specific manifest only contains a reference to a PTV MapServer specific manifest in the PTV.Logistics.MapServer folder.
This approach offers the opportunity to aggregate other third-party-DLLs in the same manner by simply adding <assemblyIdentity>keys in the application’s manifest:
MyApplication.exe.manifest ... <dependency> <dependentAssembly> <assemblyIdentity name="PTV.Logistics.MapServer" version="184.108.40.206" type="win32" processorArchitecture="x86"/> <assemblyIdentity name="ThirdPartyLTDFolderName" version="220.127.116.11" type="win32" processorArchitecture="x86"/> </dependentAssembly> </dependency> ...
Please be aware, that the manifest-mechanism is based on the Microsoft-COM technology itself, it is not implemented by the PTV MapServer.
Information and contact data for questions concerning PTV MapServer: