Release Notes for GPM.NET Note:

Transcription

1 Release Notes for GPM.NET This document provides release notes for patch release of Galileo Print Manager.NET (GPM.NET). It also provides previous release notes for versions , 1.5, 1.4, and Galileo Print Manager.NET version provides enhancements to functionality. It operates within the Microsoft.NET Framework and is supported on the following platforms: 32-bit and 64-bit Windows 7 plus Service Pack 1 (SP1) 64-bit Windows 8.1 (not Windows RT) 32-bit and 64-bit Windows 10 Windows Server 2008 R2 Windows Server 2012 and 2012 R2 Note: If you experience connectivity issues, install Microsoft.NET With this release, all previous versions of GPM and GPM.NET are retired. GPM.NET replaces all previous versions, whether installed on 32- or 64-bit operating systems. GPM.NET is the only supported version; all previous versions are no longer supported. Page 1

2 Release Notes: Functional Updates Update Detailed Description Associated Help General Provide the ability to more efficiently add form codes to an existing PDF to Printer device configuration. Previously, in order for users to add form codes to an existing PDF to Printer device configuration, they had to delete the driver, re-add it, and add the previous and additional form codes to it. With this release, a new Edit button was added to the Device Drivers tab on the GPM.NET Configuration window. This button is displayed only when a PDF to Printer device is selected. It accesses a new Edit Device wizard dialog box. This dialog box enables the user to easily add form codes to the device configuration. PDF to Printer Driver (German Market) Page 2

3 Restrict device names to include only alpha and space characters (not numeric or special characters). Remove paper size selection from PDF to Printer device configuration. This release allows only alpha characters and space characters to be used in device names for newly-added devices. Numeric characters and special characters (such $, &, and?) are not allowed. Previously configured devices will retain the device names originally specified. Adding and Configuring Device Drivers With this release, the Paper Size field is removed from the second Add Device wizard dialog PDF to Printer box for PDF to Printer devices. (It also does not appear on the new Edit Device wizard dialog Driver (German box.) In addition, the Supported Documents field on the Device Drivers tab of the Market) GPM.NET Configuration window no longer displays the paper size value. Appropriately display decimal characters for form code pagination settings based on computer regional settings. This release ensures that decimal characters for form code pagination settings are displayed appropriately based on computer regional settings. For example, the decimal character in a height or width setting, or in an X- or Y-offset setting, will be a period (.) or a comma (,) depending on the regional setting on the computer. PDF to Printer Driver (German Market) Page 3

4 Release Notes: Functional Updates Defect Fixes The following defects were fixed in this release: GPM.NET ignored the Diagnostics setting in the GPM_Service.exe.config file, resulting in host PNR data being logged continuously on the client machine, regardless of a "true" or "false" setting. Some MIRs remained on the host queue and were not processed by GPM.NET. This occurred because these MIRs, which tended to be larger, would be split into multiple packets of data by either the network or the host itself. GPM.NET was not able to process these multi-packet MIRs. Page 4

5 Release Notes: 1.5 Functional Updates Update Detailed Description Associated Help Defect Fixes The following defects were fixed in this release: MIR GTID linkage kept going down while GPM.NET was connected. The GPM.NET service name appeared as "Service1" rather than "Galileo Print Manager.NET" in Microsoft's Windows Event Viewer. General Support double-digit ordinals for Itinerary drivers (GPDS host). Previously, printing failed and GPM.NET issued an error when using an Itinerary driver with an ordinal greater than 9. This issue was reported for GPDS only. GPM.NET now supports double-digit ordinals for Itinerary drivers. Adding and Configuring Device Drivers Page 5

6 Release Notes: 1.4 Functional Updates Update Detailed Description Associated Help Defect Fixes The following defect was fixed in this release: General Itinerary Driver print jobs produced output with blank, missing, or misformatted pages. Applies to both Galileo and Apollo. Standardize the GPM.NET user interface for consistency. With this release, the user interfaces for both the GPM.NET installation process and the application are standardized for consistency. These changes primarily affect the name of the GPM.NET application, which displays in various windows, dialog boxes, menu options, messages, and so forth. Both "Galileo Print Manager.NET" and "GPM.NET" are used. For example, the names of the following windows have changed: The Print Manager Status window is now GPM.NET Status The Print Manager Configuration window is now GPM.NET Configuration Most GPM.NET help system topics affected Installation Provide silent install option for GPM.NET. With this release, users requiring GPM.NET to be installed without requiring user interaction can now perform a silent install of GPM.NET from the Windows command line. Silent Installation Install.NET Framework Previously, GPM.NET required Microsoft.NET Framework 4.0. With this release, GPM.NET requires Microsoft.NET Framework The GPM.NET installation process automatically installs Microsoft.NET Framework if it is not installed already on the computer that hosts GPM.NET. Installing Galileo Print Manager.NET Page 6

7 Create a The Welcome screen of the GPM.NET Setup Wizard now includes a hyperlink to the "Installing Galileo hyperlink in the Print Manager.NET" topic in the help system. This topic includes a procedure that guides a user GPM.NET Setup through the GPM.NET installation process. Wizard to the installation procedure in the help system. Installing Galileo Print Manager.NET Host Configurations Support Notify Proxy on port 443. To allow some customer networks to work with the Travelport Notify Proxy, which tells GPM.NET to retrieve GPDS data when available, support for connecting to port 443 (SSL) has been added. If a customer network only allows true HTTP data to flow on TCP/IP port 80 connections (GPDS notifications are not HTTP), GPM.NET will not be able to automatically retrieve and process new print requests when available. In this situation, the new feature that allows the use of port 443 instead should resolve this issue. Adding and Configuring Host Connections Page 7

8 Change the "Misconfigured" host connection status message to "No Devices". Support RAW connections for LCN host handlers. Device Driver Configurations Previously, if a user configured a host, but did not configure any devices, a "Misconfigured' status message appeared in the Connection Status field for the corresponding host row in the Print Manager Status window's Host Connections grid. This status message is now changed to "No Devices" to indicate that even though a host has been configured, no devices have been configured for use. Note: With this release, the name of the Print Manager Status window changed to GPM.NET Status. Status Messages Previously, GPM.NET always used a Secure Socket Layer (SSL) connection to send and receive data Adding and Configuring with both Galileo and Apollo LCN host handlers. Some agencies required an alternate way to access Host Connections the Travelport network (for instance, using the actual Galileo SSL Tunnel software in "Gateway Mode") and could not have the connection from GPM.NET encrypted via SSL connection. GPM.NET now provides a way to use a RAW connection instead of an SSL connection. For assistance, contact GPM.NET Technical Support. Support paper bin selection in the PDF to Printer device driver (German Market). Allow hyphens and underscores in MIR directory path when configuring the MIR to Disk device driver. Previously, paper bin/source selections made in the Bin field in GPM.NET's Add Device wizard dialog box for the PDF to Printer device driver (German Market) did not work properly. Selections were ignored, and print jobs were sent to the printer's default bin instead. This release of GPM.NET supports paper bin/source selections in the Bin field. For more information, see the notes for step 5 in the "PDF to Printer Driver (German Market)" topic's main procedure. Previously, when specifying a directory path in the MIR Directory field in GPM.NET's Add Device wizard dialog box for the MIR to Disk device driver, hyphens and underscores were not allowed in directory names (for example, C:\MIR-1). This release of GPM.NET allows hyphens and underscores in directory names specified in the MIR Directory field. PDF to Printer Driver (German Market) MIR to Disk Page 8

9 Verify that font sizing works properly for the PDF to Printer device driver (German Market). Some GPM.NET users had unexpected output results when using the PDF to Printer device driver (German Market). Specifically, font sizes printed larger than expected. After testing, Travelport has determined that no font-size issues related to GPM.NET occur; functionality works as designed. To avoid unexpected results when printing forms, ensure that any changes made to the PaginationSettings.xml file are accurate and without error. Configuring Additional Form Codes for PDF to Printer Device Drivers (German Market) Support page scaling for PDF to Printer device driver (German Market). Previously, the PageScaling element in the PaginationSettings.xml file did not work properly. This element, in conjunction with the new ScalePercentage element, now provides page-scaling functionality for the PDF to Printer device driver (German Market). Configuring Additional Form Codes for PDF to Printer Device Drivers (German Market) Support form code 6064 for the PDF to Printer device driver (German Market). GPM.NET now supports form code 6064 in GPM.NET's PaginationSettings.xml file. When configuring a PDF to Printer device driver (German Market), you can specify this form code in the Add Device wizard dialog box's Form Code field. Pagination settings for form code 6064 are: PageScaling = False AutoRotateCenter = False XOffset = 3.7 (in millimeters) YOffset = 0.5 (in millimeters) Note: Form height and width are not declared for this form code. PDF to Printer Driver (German Market) Configuring Additional Form Codes for PDF to Printer Device Drivers (German Market) Page 9

10 Change name Previously, users could access GPM.NET's Export Configurations feature by selecting File > Export in of Export menu the Print Manager Configuration window. The name of this menu option is now Export option on Configurations. GPM.NET Configuration window to Export Configurations. Configuration Window Note: With this release, the name of the Print Manager Configuration window changed to GPM.NET Configuration. Page 10

11 Add message Before this release, GPM.NET overwrote previously-exported configuration files without warning during Export whenever the Export Configurations feature was used (File > Export in the Print Manager Configurations Configuration window). The user now receives the following message: process that asks whether to overwrite configuration files if they exist already. Configuration Window Note: With this release, the name of the Print Manager Configuration window changed to GPM.NET Configuration. Verify that host print function commands (Pcommands) work properly with GPM.NET. Some GPM.NET users had unexpected output results when issuing P- commands to print booking files from the Galileo host's terminal window. After testing, Travelport has determined that no issues related to GPM.NET occur; functionality works as designed. The "Galileo and Apollo Print Functions (P- Commands)" topic provides a quick reference of print functions (P- commands) for Galileo and Apollo. These functions enable you to print Galileo Booking File (BF) or Apollo Passenger Name Record (PNR) information from the host's terminal window. Galileo and Apollo Print Functions (P- Commands) Page 11

12 Add configuration options to Driver.config file for Itinerary Driver. Some GPM.NET users encountered the following issues when printing itineraries: Margins on printed itineraries shifted down and right unexpectedly Lines were missing on printed multi-page Ticket Invoice Numbering System (TINS) reports and itineraries Lines appeared in the header area of printed itineraries To correct these issues, this release of GPM.NET provides more configuration options for Itinerary Driver in the Driver.config file to enable users to adjust the format of printed itineraries. These configurations have default settings that have been optimized for general itinerary printing. The "Itinerary Driver" topic includes an "Overriding Default Print Settings for Itinerary Drivers" section that explains how to override the default configuration settings in the Driver.config file. Itinerary Driver Page 12

13 Add configuration options to the user interface for itinerary Driver. With this release, GPM.NET provides the following new configuration settings in GPM.NET's Add Device wizard dialog box for Itinerary Driver: Lines Per Page Top Margin Left Margin Characters Per Line Line Spacing Font Name Font Size Itinerary Driver These configuration settings offer greater control over printed itinerary output. The "Itinerary Driver" topic describes these settings in detail. Page 13

14 The Device Drivers tab for Itinerary Driver in the GPM.NET Configuration window also shows the new configuration settings: Note: With this release, the name of the Print Manager Configuration window changed to GPM.NET Configuration. Page 14

15 GPM.NET Service Monitor Automatically start GPM.NET at computer restart or reboot. Previously, GPM.NET would not start automatically when the computer was restarted or rebooted. The user would have to start the application manually. Now GPM.NET starts automatically when the computer is restarted or rebooted. Service Monitor Display process count in the Configured Devices grid in the GPM.NET Status window. Previously, GPM.NET did not display to the user the number of tickets processed by configured device drivers since GPM.NET was last started. The GPM.NET Status window now shows this count in the new Processed column in the Configured Devices grid. Notes: The processed number also includes the number of tickets that were processed, but failed to print. With this release, the name of the Print Manager Status window changed to GPM.NET Status. Page 15

16 Ensure that GPM.NET recovers and functions normally when serial port or printer errors are resolved. GPM.NET users experienced the following issues when printing tickets or itineraries: Incorrect or corrupt serial port drivers on computer crashed GPM.NET Printer errors crashed GPM.NET A single device failure impeded the operation of all other configured GPM.NET devices With this release, the GPM.NET-related issues were fixed in the code. In most situations now, resolving issues with serial ports, printers, or other configured devices will ensure that printing continues normally. However, you should restart the host queue if printing does not occur. For instructions on restarting the host queue, see the "Restarting the Host Queue" topic. Restarting the Host Queue Create menu options within GPM.NET to access the help system. Support "Ticket Printer" as type of printer GTID in GPM.NET (for Apollo ATB printers). Support Test Print functionality for Apollo ATB Printer device. With this release, GPM.NET provides access to the GPM.NET help system in three places within the application: In the Windows notification area (at the far right of the Windows taskbar), right-click the GPM.NET Service Monitor icon ( ), and then select Help > GPM.NET Help. In the GPM.NET Status window, select Help > GPM.NET Help. In the GPM.NET Configuration window, select Help > GPM.NET Help. Previously, GPM.NET did not support "Ticket Printer" as a type of printer GTID for Apollo ATB printers. This caused problems with issuing tickets or downloading PECTABs to the printer. GPM.NET now supports the "Ticket Printer" type. Previously, GPM.NET did not print a test ticket on an Apollo ATB Printer device when a user clicked the Test Print button in the Configured Devices area of the Print Manager Status window. GPM.NET now prints the test ticket as it did in the former GPM application. Caution: Using Test Print functionality can affect ticket stock management because one ticket is consumed for each test. Note: With this release, the name of the Print Manager Status window changed to GPM.NET Status. Service Monitor Issues Related to Galileo or Apollo Page 16

17 Show full GPDS Host GTID names in the Configured Devices grid in the GPM.NET Status window. Previously, GPM.NET's Print Manager Status window showed truncated GTID names for GPDS hosts in the Selected Host Association field in the Configured Devices grid. Now GPM.NET shows full GPDS Host GTID names. Note: With this release, the name of the Print Manager Status window changed to GPM.NET Status. Help System Explain how to resolve difficulties issuing ATB tickets or downloading PECTABs on Apollo ATB printers. Explain that MIRs can be sent to Windows DFS Share or SMB Share if using Active Directory. Users experienced difficulties issuing ATB tickets or downloading PECTABs to Apollo ATB printers. This issue is likely caused by GPM.NET serial port device settings that do not match the ATB printer's internal settings. The "Issues Related to Galileo or Apollo" topic includes an "Issuing Tickets or Downloading PECTABs on Apollo ATB Printer Fails" section that explains how to resolve this issue. Users were unable to send MIRs to Windows DFS Share via Universal Naming Convention (UNC) name or mapped drive. They also could not send MIRs to Windows SMB Share via mapped drive. This occurred because a computer was using Windows Workgroups to connect instead of Active Directory. For more information, see the "MIR to Disk" topic. Issues Related to Galileo or Apollo MIR to Disk Page 17

18 Describe setting up account permissions to access network printers. Some users were unable to print to configured network printers. This occurred because the account on which GPM.NET ran did not have the required permissions to access the network printers. To address this issue, the GPM.NET help system includes topics that explain how to set up account permissions. For an Active Directory Domain environment, see the "Configuring Network Printer Permissions" topic. For a Windows Workgroup environment, see the "Printing to a Network Printer in a Workgroup Environment" topic. Configuring Network Printer Permissions Printing to a Network Printer in a Workgroup Environment Explain that a user account with administrative privileges is required to install and run GPM.NET. Explain how to resolve lost tickets when errors occur during printing for GPDS. Users must be logged on with administrative privileges to install GPM.NET. Also, because GPM.NET runs as a Windows service, the GPM.NET service account must have administrative privileges. This is essential for GPM.NET to automatically start and function when you boot, reboot, or restart your computer. For this reason, Travelport recommends that you set up a user account with administrative privileges that is dedicated to GPM.NET use. For more information, see the "Installing Galileo Print Manager.NET" topic. Users lost tickets from the queue when errors were received while attempting to print GPDS-delivered tickets. It was determined that lost tickets occur because of printer issues or GPM.NET configuration issues at the agency. GPDS does not store tickets after GPM.NET retrieves them for printing. If printing fails, the queue becomes inhibited and the lost ticket cannot be retrieved for printing. The lost ticket must be resent to GPDS. If a ticket is lost, subsequent tickets sent by GPDS remain on the queue and are not lost. This behavior works as designed. The "Issues Related to GPDS" topic includes a "Losing Tickets When Errors Occur During Printing for GPDS" section that explains how to resolve this issue. Installing Galileo Print Manager.NET Issues Related to GPDS Describe the Form Code parameter for PDF to Printer driver configuration. The GPM.NET help system describes the Form Code field in GPM.NET's Add Device dialog box for the PDF to Printer driver (German Market). The numeric form code identifies the form type. PDF to Printer Driver (German Market) Page 18

19 Explain that GPM.NET does not display printer dialog boxes because it runs as a Windows service. Because GPM.NET runs as a Windows service, it does not run on the User Interface level of the operating system. Therefore, it does not display dialog boxes. Because of this, if a user selects a PDF Writer, a Microsoft XPS Document Writer, or some other printer that requires user input, that dialog box might not appear. The "PDF to Printer Driver (German Market)" topic includes this information. PDF to Printer Driver (German Market) Add a topic to The GPM.NET help system includes a "Creating PDF Files" topic that describes using a third-party PDF the help system application to create PDF files and setting up an itinerary device driver to print them. about creating PDF files and setting up an itinerary driver to print them. Add a topic to The GPM.NET help system includes a "NULL Driver" topic that describes configuring a NULL device the help system driver. A NULL driver enables the processing of redundant documents without generating output. Any about print requests that are sent to the NULL driver are deleted permanently. configuring a NULL driver. Creating PDF Files NULL Driver Describe the Export Configurations feature in GPM.NET. Users can export GPM.NET's Host.config and Driver.config files to a specified location on the computer by selecting File > Export Configurations in the GPM.NET Configuration window. Before uninstalling GPM.NET for any reason, exporting these files can be useful to preserve the configurations. Also, users can export these files so that the configurations can be used on multiple machines. For more information, see the "Exporting GPM.NET Host and Driver Configuration Files" section in the "Using the GPM.NET Configuration Window" topic. Configuration Window Page 19

20 Describe how to manually copy host and driver configuration files to the GPM.NET application folder. If users export the host and driver configuration files (Host.config and Driver.config) to save copies of them or to modify settings, they can manually copy them to the GPM.NET application folder so that GPM.NET uses their settings. For more information, see the "Copying GPM.NET Host and Driver Configuration Files to the GPM.NET Application Folder" section in the " Configuration Window" topic. Configuration Window Describe how to use actual data from Apollo or Galileo hosts to test printing. The Test Print button on the GPM.NET Status window validates that GPM.NET can communicate with the selected device driver by sending print output to the device. This test does not produce print output that represents actual output from the host. It only produces test output that validates communication with the device driver. However, the "Testing Driver Configurations with Host Print Data" topic describes how to use actual data from Apollo or Galileo hosts to test printing on devices. Testing Driver Configurations with Host Print Data Page 20

21 Release Notes: and Earlier Functional Updates Update Associated Help NULL and OPTAT drivers added. Resolved an issue where additional ACK characters were being sent to ATB devices. Added a column to the Status Panel to show processed jobs. Added a check in the Status Panel to warn if no devices are configured. Enhancements to MIR driver to better support file contention scenarios that might occur when software, such as backoffice systems, also access MIRs. Resolved an issue with the Status Panel that might have caused excessive memory usage. Resolved an issue in the MIR driver that could have stopped LMT queue processing in certain scenarios. NULL Driver OPTAT Driver MIR to Disk MIR to Disk Fixed an exception in Configuration Edit when user modified existing Ordinal Number and then tabbed or clicked on another field. BOOTP error configuration messages. Adding and Configuring Device Drivers Status Messages Page 21

22 Update Added logic to check if user is an administrator on their machine and if not does not allow said user to run the Configuration application or stop or restart the service. These changes are due to the fact that you need to install as an administrator for GPM.NET. Associated Help Configuring GPM.NET Resolved an issue where the Service Monitor was not displaying Host and Device Information. Resolved an issue that prevented GPM.NET from connecting to an LCN host. Adding and Configuring Host Connections Resolved an issue where an additional backslash character was incorrectly added to the GPM.NET configuration for PDF drivers. Added a visual cue to the System Tray icon for when the service is stopped. The icon will now be grayed out when the service is not running. Adding and Configuring Device Drivers Service Monitor Accuracy of the Host connection status in the Status Panel has been improved. There were previously certain scenarios where the status did not represent the actual state. Resolved an issue in the Itinerary driver where the top and left margins were being incorrectly calculated. Test Print logic now gives feedback as to the success or failure of the test. Itinerary Driver Page 22

23 Update Associated Help The ability to change the Paper Size is now part of the Configuration setup for PDF drivers. The functionality works the same as the Source (Bin). You set the value for each item and then click Add to add the specific form code. If you have existing drivers that do not have the Paper Size it will now default to A4 instead of Letter. Adding and Configuring Device Drivers PDF driver screen has been modified to switch the order of the configuration file (PaginationSettings.xml) and the entering of the form codes. This enables you to use the default PaginationSettings.xml or supply an alternate file, which will then be used to load the form codes and when printing. When selecting an LCN host on the Service Status panel, the corresponding GTIDs are now displayed for the devices. Resolved an issue where incomplete MIR files were being written. Resolve an issue with the Itinerary driver where etickets were printed over more pages than required. Adding and Configuring Device Drivers MIR to Disk Itinerary Driver Page 23