PrintVis, along with Sabre's proprietary Wide Format addon is the flexible and powerful solution for you. PrintVis is a print industry specific addon with a hyper-flexible estimating and quoting module unique in the MIS world. It is integrated directly into Microsoft Dynamics, the world-renowned ERP system for mid-market businesses. If you would like to install Sabre Red Workspace, please visit www.sabreredworkspace.com or contact the Sabre Technical Support desk. (.) (.)fees might apply. .Check that the Sabre print Module (SPM/SJPM) is running and displayed in the System Tray (bottom right corner of screen). If the ICON does not appear, contact the Sabre support desk at 1-866-334-7551 for assistance, select Option 2. Possible Services that provide Sabre connectivity; OSG, OFEP, and HSSP. You can select the SABRE Communication submenu of the File menu (Figure 2. File Menu) to bring up the SABRE Communication Setting window to choose different settings. From the following SABRE Communication Setting window, you can select the session for CCSAPI.
MySabre™ API
Software Release 2.4
Frequently Asked Questions
April, 2008
© 2008 Sabre Inc. All rights reserved.
Question: How can I obtain technical support for working with the MySabre API?
Answer: Technical support for working with the MySabre API can be obtained as follows:
Note
If you are reporting Production or other critical issues, please contact the Sabre Software Help Desk by telephone. Do not send email.
Telephone 24 x 7
800-678-9460 (USA)
682-605-5570 (Canada)
598-2-518-6020 (International)
Or call your regional Sabre software help desk
Currently, Email is monitored Monday through Friday, from 06:00 to 15:45 CST.
Email is monitored Monday through Friday, from 0300 to 18:45 CST.
1.Question: How do applications use MySabre API to intercept and modify commands?
Answer: To tell MySabre API which commands to intercept, applications first register command prefixes using SabreEmulatorMarkup. Applications then use the functions or methods in SabreNotifyAndSend to send the modified commands to the Sabre® global distribution system (Sabre® system).
2.Question: How does SabreNotifyAndSend differ from SabreEmulatorMarkup?
Answer: With SabreNotifyAndSend, applications listen to all commands, all responses, or both. With SabreEmulatorMarkup, applications can intercept commands or mark up responses.
3.Question: Can applications receive SDS messages from the Sabre system through MySabre API?
Answer: Yes. If applications send commands requesting SDS-type responses, MySabre API returns SDS response messages.
4.Question: Can applications receive XML-formatted messages from the Sabre system through MySabre API?
Answer: No. All responses come directly from the Sabre system, so no XML transformation is processed. Therefore, applications cannot request XML-type message. If you need to work with XML messages, you may want to consider using Sabre® Web Services.
5.Question: Can applications use masks with MySabre API?
Answer: Completing masks from the Sabre system is not supported. However, applications have the following option when building their own masks:
1.Build an empty mask.
2.Complete the mask with data.
3.Send the completed mask to the Sabre system.
6.Question: Can applications continue to function with MySabre API when agents are using the back-up Emulator?
Answer: Yes, MySabre API provides full support and functionality for third party applications and end users when the back-up Emulator is running. End users can continue to work in the Emulator and use third party applications.
7.Question: Is there a test environment for MySabre API?
Answer: No. All customer development is against the production Sabre® system. Therefore, scan charges are applied in accordance with customer contracts. PNRs created while testing applications must also be cancelled.
8.Question: When MySabre API is updated, do I need to update my application?
Answer: No. All updates are backward compatible with the previous version of the API. To use new functionality, however, you must update your application.
9.Question: If connectivity to the Sabre system is the only requirement for a third party application, that is, the particular standalone application has no need for interaction with the MySabre Emulator, can the application use MySabre API?
Answer: No. It is recommended that you consider using Sabre Web Services.
10.Question: How can I identify the emuapi.dll version?
Answer: Select the emuapi.dll file (found in the default Windows directory) and right click. From Properties, choose the Version tab.
11.Question: Is MySabre API a COM object, and can it be registered using regsvr32.exe?
Answer: No. The current release of MySabre API is not a COM object and cannot be registered with regsvr32.exe.
12.Question: How can I force the release of the DLL?
Answer: In Task Manager, end all Internet Explorer instances (IEEXPLORE.EXE) and application processes.
13.Question: Can I sign in to the Sabre system using MySabre API?
Answer: Yes. For an example, see the sample C program, sendMaskSample.c, in the MySabre API SDK.
14.Question: Does MySabre API support multiple applications running Markup on the same desktop?
Answer: MySabre API now supports multiple applications running Markup on the same desktop, as long as the applications are not attempting to markup the same transaction. If more than one Application on the same desktop attempts to register the same or overlapping command prefixes in order to markup transactions, subsequent registration attempts will be rejected. The command all should not be registered by any application when more than one application using markup is running.
15.Question: When using MySabre API Notify and Send functionality to send commands that have multiple responses, and requesting that responses not be displayed in the Emulator, why do I still see the second and later responses?
Answer: With Notify and Send functionality, the option to not display the response only applies to the very next response received from the Sabre system. If all responses must be hidden, use the MySabre API TA Sharing functionality, with its additional level of control, instead.
16.Question: Will TA Sharing work without MySabre Emulator running first?
Answer: No, MySabre Emulator must be running first.
17.Question: What happens if I close the browser or visit some other web site, causing the MySabre emulator to be unloaded while an application has the TA locked?
Answer: The application loses the TA lock when it automatically reverts to the MySabre Emulator. This will result in an error condition the next time the application attempts to use the previously locked connection, upon which the application should request the lock again.
18.Question: Will TA Sharing functionality work with applications using EBCDIC?
Answer: No, TA Sharing functionality supports applications using ASCII or Unicode only.
19.Question: Can I still use other MySabre Portal functionality when the TA is locked by the application?
Answer: It depends. Many features of the MySabre portal require interaction with the Sabre system and these try to lock the TA when they need to do so, but cannot proceed if the TA lock is held by another application.
20.Question: How can I tell by looking at the Emulator if an application has the TA locked?
Answer: The Emulator Status bar will display the message ‘TA Locked By External Application.’ In addition, any Notify and Send commands (including ‘SendCommandToEmulator’ and ‘SendMessageToEmulator’) sent by the application will display on the Emulator, but will not be sent to Sabre.
21.Question: When sendMsg (for native code) or send (for Java) is used during TA Sharing to send a message to the Sabre host where multiple responses are expected, does receiveMsg (for native code) or getResponseMessage /getResponseString (for Java) need to be called more than once in order to receive all the responses from the Sabre host?
Answer: Yes. The receiveMsg (for native code) or getResponseMessage / getResponseString (for Java) must be called the same number of times as the number of responses expected.
22.Question: How does the new TA Sharing functionality differ from the TA Sharing option solicited during the MySabre installation process?
Answer: The TA Sharing option solicited during install is used to support existing Legacy Sabre applications (such as Sabre Print Module), whereas the new TA Sharing capability is for third party developers and end users to be able to lock and make use of the Emulator TA in order to have temporary, exclusive access to the Sabre host.
23.Question: Can the MySabre API listen for and react to an entry made by a Sabre Scribe Script?
Answer: No, the API is actually disabled when Sabre Scribe is running, so the API application does not ‘see’ the script-generated activity. Interactions between scripts and API applications are difficult to coordinate and debug – it is recommended that the customer port the script’s functionality into the API application and do all of their automation in a single place instead.
24.Question: What is the difference between an 8000 error and an 8001 error?
Answer: An 8000 error indicates a General failure to update API files, while an 8001 error indicates a Failure to update API files because the previous files could not be released and deleted.
25.Question: Can Multiple Applications using MySabre API Markup component on the same desktop register the same or overlapping commands in order to markup transactions?
Answer: No, Multiple Applications on the same desktop may use the MySabre API Markup component to register command prefixes and markup responses to those commands only if those commands are different and non-overlapping.
26.Question: If two Applications have different commands correctly registered and are running Markup on the same desktop and one application finishes and unregisters, will the other Application continue to Markup correctly?
Answer: Yes.
27.Question:MySabre™ agent booking portal cannot upgrade the DLL on my machine. I get a message telling me to contact the Sabre Software Help Desk. Why can't MySabre agent booking portal upgrade the DLL?
Answer: When a new MySabre API DLL release becomes available, MySabre agent booking portal attempts to upgrade the DLL on the end user’s machine with the newest release. MySabre API broadcasts an event instructing the application to release the DLL so it can be replaced. If the application is not programmed to release the DLL, MySabre agent booking portal will not be able to change the DLL and therefore, MySabre API will not function. The DLL cannot be replaced if an application is still holding on to it; this causes a sharing violation error. The application must first release the DLL.
28.Question: My application cannot find the MySabre API DLL. A null value is returned by the LoadLibrary function.
Answer: The emuapi.dll file must exist in the default Windows directory or customer-specified custom directory (Please see Chapter 1 of the Programmer Reference Manual for instructions.) The DLL file is automatically downloaded to the workstation when the MySabre Emulator is configured correctly. Please follow the steps below to automatically download the latest release of the emuapi.dll file.
oInstall MySabre agent booking portal on the workstation. Installation instructions are available on the Web site at the following URL:
ohttps://my.sabre.com
oOn the MySabre Emulator menu, choose Options and then Configuration.
oOn the Configuration dialog, select the MySabre API check box.
oClick on OK.
oClick on the Sign out link for the update to take effect.
oLog in to MySabre agent booking portal again.
The file should be installed in the proper directory.
29.Question: Can I call MySabre API functions from within my callback function?
Answer: No, you cannot make function calls to any MySabre API functions from within callback functions. Third party applications must start a new thread to invoke other API function calls.
30.Question: Has MySabre API been tested and certified to work with the Microsoft® .NET platform?
Answer: Yes. MySabre API supports application development with Microsoft .NET Framework 1.1 and 2.0. The MySabre API DLL and Visual Basic® .NET sample projects were opened, compiled, and run by Microsoft Visual Studio® .NET 2003 with no issues.
31.Question: What versions of Microsoft .NET Framework does MySabre API support?
How To Install Sabre Print Module On Macbook Pro
Answer: MySabre API supports applications written with .NET Framework 1.1 and 2.0.
32.Question: Has MySabre API been tested with projects written in Visual Basic?
Answer: MySabre API supports applications written with Microsoft Visual Basic .NET only. Earlier versions of Visual Basic are not supported.
33.Question: Does MySabre API support third party applications written in Java?
Answer: Yes, Java is supported.
34.Question: Does MySabre API support Java applets?
Java applets are supported by MySabre API only if the applet is running in a browser process that is in a separate instance from the browser being used by the MySabre agent booking portal. It is critical that the applet client unloads the msapiUtil.DLL each time it terminates, such as when browsing to a different URL or closing browser. Otherwise, could get in a situation where subsequent launch of applet client is unable to load the DLL, because a previous instance failed to unload it properly. This will then require closing IE and launching a new IE instance in order to resolve the issue.
Microsoft Internet Explorer can be configured to use a new process each time it is launched by setting BrowseNewProcess = yes in the following Registry key:
HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerBrowseNewProcess
We recommend standalone applications, and suggest deploying applications with Java Web Start.
35.Question: Does MySabre API support Java 1.6?
Yes, MySabre API is certified for Java 1.6 with this Release (2.4) of MySabre.
36.Question: How do I clear Cache?
LOGGING IN MySabre API - PROBLEM TROUBLESHOOTING
Sometimes users may face problems with getting into MySabre and loading the 'green screen' successfully. This information is to remind everyone that the first action we should take is clearing the system cache and JAVA plug-in cache as well. If clearing all cache memory does not help, one can look into Java console or turn to help desk.
Clearing WIN cache:
START / Control Panel / Internet Options / Delete Files... / checkbox 'Delete all offline content' should be checked / OK
Clearing JAVA cache:
START / Control Panel / Java (or Java Plug-in) / Cache / Delete Files / OK
For latest Java plug-in installation:
START / Control Panel / Java (or Java Plug-in) / on 'General' tab push the 'Settings' button in 'Temporary Internet Files' section / Use the 'Delete Files...' button / Check all available checkboxes / OK
Please note you need to close out of internet explorer before clearing jar cache if you have attempted to log in and failed. This will prevent the plugin from locking those jars as they are in use. (It also does not hurt to look for iexplore processes in Task Manager, as sometimes IE does not die gracefully)
Also, please be aware that after clearing these caches, when you contact the system there will be approximately 3 megs of jar files and web content to pull down. This may cause a noticeable delay depending on your connection speed.
37Question: Should MySabre API Markup work with Point and Click?
MySabre API Markup will work with Point and Click as long as the Background of the Point and Click fields are marked up. The foreground must remain unchanged.
38.Question: Does MySabre API support Windows Vista?
Yes. Installing Windows Vista on top of existing Operating Systems: Please note: MySabre API customers who install Vista on top of an existing operating system (i.e., XP), must manually delete the emuapi.dll file (that may have been created) from the C:WINDOWS folder. After running the Windows Vista Update, the latest emuapi.dll file will be created in C:SABRE. The file must be deleted from C:WINDOWS to prevent a conflict between the two files. All future updates to the dmuapi.dll for Vista will be to the C:SABRE folder.
Using MySabre API on top of Vista Operating System: Developers and End Users using MySabre API on the Windows Vista operating system, please note: The WinVistaUpdate.exe file writes to the registry to place the emuapi.dll file in the C:SABRE folder and sets the path in the Environment Variables to that folder. Users who may have installed MySabre API prior to MySabre Release 10.1 (December 8, 2007) did have a 0KB emuapi.dll file in C:WINDOWS but this file is now removed automatically. No further action is necessary
How To Install Sabre Print Module On Linux
39.Question: Is it possible to configure the location of log files to a specific drive on the PC rather than having the log files automatically be placed on the desktop
Yes, Release 2.4 of MySabre API adds this capability. Please see the API Programmer Manual Chapter 7, under Java Interfaces to MySabreAPI, SabreApiClient, pages 107-109.