TransXChange
Publisher
The TXC TransXChange Publisher is a stand-alone software tool that can be used to publish TransXChange compliant XML documents into a format that is easy to read and print. It also includes an option that will apply additional integrity checks to documents so that you can use it as a diagnostic tool to check they are consistent with various additional business rules.
The TXC TransXChange Publisher is available as an executable that can be run on your own computer. The latest version is available here.
Examples of the TransXChange Publisher's output can be seen here (2.4).
See the ReadMe below for a list of changes to each version of the publisher.
- Installing the Publisher.
- Running the Publisher.
- Run time Options -
- Desktop GUI with help
- Command Line.
- Downloads
- FAQs
Prerequisites for Running the TransXChange Publisher
1. Hardware
Publishing timetables is a computationally intensive process in terms of both memory usage and processor cycles and requires a computer with sufficient resources. Recommended minimum for a PC would be a 1.5 GHz processorand 512M of memory.
Note that the amount of memory allowed to the Publisher can be configured - see Controlling publisher memory.
For Release v2.4_1 at least a MP size of at least 1024M is required - This is the default setting shipped with the Publisher
2. Operating System
The TransXChange Publisher is designed to run on Microsoft Windows platforms (Windows 2000, XP, etc). (It should run on any computing platform with support for the Java runtime, but only Windows is officially supported at this time.)
3. Java Environment JRE.
To run the publisher on your machine, you must first have installed the required version of the Java Runtime Environment (JRE) version. It is available free from http://java.sun.com/download.html.
Typically the Publisher will require the version of the run time current at the time of its creation, for example 2.1_1 requires JRE 1.4.2 or later, 2.4_0 requires JRE 6.1 or later. See downloads below for required version.
If you are unsure of your current Java version, do the following:
- Open a command prompt
- Type "java -version"
- If you have Java correctly installed, you should see a message telling you the current version of Java.
If you are do not have a sufficient version of the JRE installed you will not be able to run the publisher.
The default amount of memory configured for your Java VM may need to be increased. see Controlling publisher memory.
4. Adobe Acrobat Reader
To view and print the pdf documents produced by the Publisher, you must have the Acrobat reader installed on your machine. The reader is available free from Adobe.
5. Broadband Internet Connection
The enhanced version of the publisher (2.2a_1 and higher) includes some optional route map publishing features that require a broadband (512kbs or higher) internet connection. This is also required to read the on-line help text.
6. Firewall configuration
The route map publishing features access two we services. Your firewall must permit access to the domains from which these services run.
Installing the TransXChange Publisher
The TX TransXChange Publisher can be downloaded and installed as follows:
- Download the publisher by clicking on the link below, and saving the file to a directory on your machine. The file is a self-extracting zip.
- Make sure you have the required version of Java Runtime Environment (JRE) version installed.
- Unzip the publisher distribution into a directory on your machine. You should see a list of files including those needed to run the publisher.
- TX TransXChangePublisher.exe runs the desktop version of the publisher:
- publish.bat runs the publisher from the command line (Deprecated).
- The documents directory includes some sample documents you can use to try out the publisher.
The distribution package includes a local copy of the TransXChange Schema files: these are used to validate documents before publishing them. Note that the publisher ignores any schema location reference in a document being published and uses this local copy of the schema instead.
Configuring for a Proxy environment
The map publishing options of the publisher require an online internet connection to fetch stop and map data. If you are in a secure environment that requires use of a proxy, you may need to Configure your Proxy settings in order to use the map publishing.
Running the TransXChange Publisher
- Running the TransXChange Enhanced Publisher from the Desktop GUI
- Running the TransXChange Publisher from the Command line
Downloading the TransXChange Publisher
Status |
Date of issue |
Download of ZIP |
Prerequisite Java Runtime Environment |
Contact |
|
|---|---|---|---|---|---|
Current with support for 2.4 schema.. Bing Maps Support |
15/12/2011 |
Zip of TransXChange Publisher 2.4_2 ( 160 Mb). Updated with fixes See Release notes. Note the publisher may take several minutes to start. You may need to revise revise your Firewall settings to allow access to the Bing services. |
JRE version 6.1 or later. TXC Schemas: 2.1, 2.4 See also help |
||
Current with support for 2.4 schema.. Bing Maps Support |
18/11/2011 |
Zip of TransXChange Publisher 2.4_1 ( 160 Mb). Updated See Release notes. Note the publisher may take several minutes to start. You may need to revise revise your Firewall settings to allow access to the Bing services. The minimum JavaVM memory requirements have been increased. |
JRE version 6.1 or later. TXC Schemas: 2.1, 2.4 (2.2a support is deprecated. ) See also help |
|
|
| Current with support for 2.4 schema. MultiMap (Deprecated after 2011.11.18). |
20/08/2011 |
Zip of TransXChange Publisher 2.4_0 (205 Mb). Updated Note the publisher maytake several minutes to start. |
JRE version 6.1 or later TXC Schemas: 2.1, 2.4 (2.2a support is deprecated )See also help |
|
|
20/03/2011 |
See Release notes. Note the publisher may take several minutes to start. |
JRE version 6.1 or later TXC Schemas: 2.1, 2.4 (2.2a support is deprecated ).See also help |
|
||
Superceded |
20/08/2010 |
See Release notes. |
TXC Schemas: 2.1, 2.2a, 2.4b |
|
|
| 2.4a_2 | Superceded |
16/04/2010 |
See Release notes. |
TXC Schemas: 2.1, 2.2a, 2.4a |
|
Last 2.1 Supports 2.1 & 2.2a schemas |
21/09/2009 |
See Install & Release notes. |
JRE version 6.0 or later TXC Schemas: 2.1, 2.2a |
||
2.2a_11 |
superceded |
10/07/2009 |
See Install & Release
notes |
JRE version 6.0 or later. TXC Schemas: 2.1, 2.2a |
|
2.2a_10 |
superceded |
06/02/2009 |
See Release notes |
JRE version 6.0 or later |
|
2.2a_9 |
superceded |
12/01/2009 |
See Release notes |
||
2.2a_8 |
superceded |
19/09/2008 |
See Release notes |
||
2.2a_7 |
superceded |
06/03/2008 |
See Release notes |
||
2.2a_6 |
superceded |
06/03/2008 |
See Release notes |
||
2.2a_5 |
superceded |
27/02/2008 |
See Release notes |
||
2.2a_4 |
superceded |
06/12/2007 |
See Release notes |
||
2.2a_3 |
superceded |
29/10/2007 |
See Release notes |
||
2.2a_2 |
Internal release | 03/08/2007 | |||
| 2.2a_1 | superceded |
11/05/2007 | See Release
notes Known Issues |
||
2.1_5 |
superceded |
22/02/2007 |
|||
2.1_1 |
superceded Last 2.1 release |
30/09/2005 | Zip of TransXChange Publisher 2.1_1 (13.8MB). |
JRE version 1.4.2 or later TXC Schemas: 2.1 |
|
2.0_2 |
superceded Last 2.0 Release |
23/05/2005 |
|||
2.0_1 |
superceded |
18/03/2005 |
|||
2.0f_4 |
Beta |
24/11/2004 |
|||
2.0f_3 |
Beta |
23/11/2004 |
|||
2.0f_2 |
Beta |
08/11/2004 | Release Notes | ||
2.0f_1 |
Beta |
27/10/2004 |
|||
2.0e_2 |
Beta |
07/09/2004 |
|||
2.0e_1 |
Beta |
27/08/2004 |
|||
2.0d_1 |
Alpha |
25/06/2004 |
Page last updated: 2011/12/15
