Optimise your address management with AddressServer to achieve considerable cost savings for your organisation and enjoy significant time and resource savings.

Best suited to large organisations using a variety of applications on a wide range of systems and platforms, AddressServer provides a unique opportunity to centralise address lookups to a single location, creating a multitude of benefits for all users. When deployed within a large user environment, AddressServer is designed to replace the standard distributed deployment of Address Management Software with minimal impact on existing customer systems.

By achieving a common result across all address related data, the need for multiple PAF licences can be greatly reduced, potentially creating substantial savings.


  • Drop-in dynamic libraries, within identical APIs, will replace existing libraries to provide a seamless interface with AddressServer.

  • A simple interface that is both hardware and software agnostic is achieved through the management of all datasets within a centralised web service. This can be called over any network using standard protocols.

  • AddressServer can handle any input dataset that can be formatted into a Hopewiser Master Address File (MAF) Including: Australia Post PAF, PSMA G-NAF and Z GeoPAF.

  • International Data, including UK Royal Mail PAF.

  • Full technical support offsite and onsite, for installation of AddressServer and migration of existing systems to the AddressServer solution, providing maximum reliability.

  • Data updates occur in one location

  • Single point of control for production updates

  • Run multiple servers for failure protection and redundancy

  • Accessible over any modern network

  • Local installation within your enterprise or hosted pay-per-click basis


  • Cost savings through reduced licence fees

  • Reduction in overheads and installation costs

  • Migration of existing applications and systems

  • Hardware and software agnostic

  • Includes a web management interface

  • Professional pre and post installation support

  • Future proof scalable solution

1. Why can I not get a response from my AddressServer?

The likelihood is that the AddressServer service you are attempting to use has not started fully and correctly. First point of investigation should be to interrogate the catalina.log and localhost.log files under the servlet container 'logs' sub-folder, and the system.log file within the 'system' sub-folder. These should detail (SEVERE) errors in starting the various AddressServer services and give some indication of the problem.

2. Why don't I have security.properties and valid.properties files in my AddressServer release?

These are licensing files imparted by Hopewiser Technical Support and set to be in keeping with the agreed licensing period in place per client / host combination. They do not form part of the standard release. The servlet container will need to be restarted for these property files to become effective.

3. Why do I get 'Security validation failure - checksum mismatch' reported?

The AddressServer is licensed via 2 AddressServer property files contained within the servlet container /conf/addrsvr sub-folder. The implication here is that these do not correlate. Send these to the Hopewiser Support team for guidance and assistance on this front.

4. Why do I get 'Security validation failure - hostname mismatch' reported?

The AddressServer is licensed via 2 AddressServer property files contained within the servlet container /conf/addrsvr sub-folder. The implication here is that the hostname provided and implemented in the security.properties file is not as per that detected in attempting to start the AddressServer. The values in brackets following the error message detail the actual (detected) hostname followed by that read from the configuration in attempting the host validation.


5. How do I update my AddressServer?

This should be relatively straight-forward given that AddressServer installed / to be installed versions are not too far apart. Please ensure that the service is stopped and that all past service WAR files and the associated folders within the 'webapps' folder are removed before implementing new ones. Contact Hopewiser Technical Support for further guidance.

6. I am using the servlet container 'startup' script but get errors. Why?

The servlet container (Tomcat by default) startup script should be run from the folder above the bin folder this sits in (as there are relative paths within that are otherwise made to be incorrect). Return to the tomcat root folder and run with this command which includes the sub-directory - 'bin/startup.bat'.

7. What are Dataset Aliases used for?

Dataset Aliases provide a means of updating data (usually monthly or quarterly), testing offline if required, then putting live without any disruption to service for the user. Use of a Dataset Alias means that you can switch a user reference without having to take the service offline or make client-side changes.