getting started with red apps - sabre dev studio started with red apps - release 2.14.3 iii ©2011,...

Getting Started with Red Apps

Release 2.14.3

October 2016

Getting Started with Red Apps - Release 2.14.3 ii ©2011, 2016 Sabre, Inc. Proprietary and confidential. October 2016

Disclaimer:

THE SOFTWARE, SAMPLE CODES AND ANY COMPILED PROGRAMS CREATED USING THE SOFTWARE ARE

FURNISHED "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING BUT NOT LIMITED TO THE IMPLIED

WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. NO ORAL OR WRITTEN

INFORMATION OR ADVICE GIVEN BY SABRE, ITS AGENTS OR EMPLOYEES SHALL CREATE A WARRANTY OR

IN ANY WAY INCREASE THE SCOPE OF THIS WARRANTY, AND YOU MAY NOT RELY ON ANY SUCH

INFORMATION OR ADVICE. SABRE DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS

REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE SOFTWARE, COMPILED PROGRAMS CREATED

USING THE SOFTWARE, OR WRITTEN MATERIALS IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY,

CURRENTNESS, OR OTHERWISE. THE ENTIRE RISK AS TO THE RESULTS AND PERFORMANCE OF THE

SOFTWARE AND ANY COMPILED APPLICATIONS CREATED USING THE SOFTWARE IS ASSUMED BY YOU. BY

YOUR USE, YOU AGREE THAT NEITHER SABRE NOR ANYONE ELSE WHO HAS BEEN INVOLVED IN THE

CREATION, PRODUCTION OR DELIVERY OF THE SOFTWARE SHALL BE LIABLE FOR ANY DIRECT, INDIRECT,

CONSEQUENTIAL, OR INCIDENTAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS PROFITS,

BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, AND THE LIKE) ARISING OUT OF THE USE OF

OR INABILITY TO USE SUCH PRODUCT EVEN IF SABRE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH

DAMAGES. THIS SOFTWARE IS OWNED AND COPYRIGHTED BY SABRE OR ITS THIRD PARTY SUPPLIERS.

YOUR LICENSE TO UTILIZE IT CONFERS NO OWNERSHIP RIGHTS IN THE SOFTWARE OR THOSE PORTIONS

YOU MAY USE IN A PROJECT. YOU AGREE TO INDEMNIFY AND HOLD HARMLESS SABRE AND ITS

AFFILIATES FOR ANY CLAIM BROUGHT AGAINST IT BASED UPON YOUR USE OF THE SOFTWARE OR ANY

COMPILED PROGRAMS CREATED USING THE SOFTWARE.

© 2011, 2016 Sabre Inc. All rights reserved.

This documentation is the confidential and proprietary intellectual

property of Sabre Inc. Any unauthorized use, reproduction,

preparation of derivative works, performance, or display of this

document, or software represented by this document, without the

express written permission of Sabre Inc. is strictly prohibited.

Sabre and the Sabre logo design are trademarks and/or service

marks of an affiliate of Sabre Inc. All other trademarks, service

marks, and trade names are owned by their respective

companies.

Sabre Inc.

3150 Sabre Drive

Southlake, TX 76092-2199

(682) 605-1000

Getting Started with Red Apps - Release 2.14.3 iii ©2011, 2016 Sabre, Inc. Proprietary and confidential. October 2016

Contents

Figures ....................................................................................................................................................... vii

Legal Disclaimers and Red App Advisories ............................................................................................ ix

Legal Disclaimers .................................................................................................................................. ix

Red App Advisories ................................................................................................................................ x

Compliance with Red App Requirements and Standards ................................................................... x

Sabre Scan Charges ........................................................................................................................... x

Modification or Termination of Service or Red App............................................................................ xi

1 Overview of Red App Start-up .......................................................................................... 1

Sabre Red App Certified Developer Profile ............................................................................................ 1

About the Red App Developer Documentation ...................................................................................... 2

Getting Started with Red Apps ............................................................................................................ 2

Red App Help ...................................................................................................................................... 2

Red App Developer FAQs ................................................................................................................... 3

Red App Release Notes ...................................................................................................................... 3

Security Requirements for Red Apps .................................................................................................. 3

Red App Developer Guidelines ........................................................................................................... 3

Toolkit Setup Process ............................................................................................................................. 4

Technical Components in the Red App Developer Toolkit ..................................................................... 7

Red App Developer Toolkit Upgrade Strategy .................................................................................... 9

Graphical View and Sabre Profiles Plug-ins ..................................................................................... 10

Red Workspace and Sabre GDS Environments .................................................................................. 11

Development Mode ........................................................................................................................... 11

Certification........................................................................................................................................ 11

Production ......................................................................................................................................... 11

Using Your Sabre ID and Other IDs ..................................................................................................... 13

CERT ID and PCC ............................................................................................................................ 13

PROD ID and PCC ............................................................................................................................ 13

Other IDs ........................................................................................................................................... 14

Contents

Getting Started with Red Apps - Release 2.14.3 iv

©2011, 2016 Sabre, Inc. Proprietary and confidential. October 2016

Required Developer Software, Tools, and IDs ..................................................................................... 15

Technical Support ................................................................................................................................. 17

Scribe Compiler .................................................................................................................................. 176

2 Setup for Red App Development .....................................................................................20

Prerequisite Software ........................................................................................................................... 21

Downloads ......................................................................................................................................... 21

Extracting the Red App Developer Toolkit ........................................................................................ 21

Adding a Red App Target Platform....................................................................................................... 22

Configuring and Testing Your Red App Run Configuration ................................................................. 32

Setting Up a Run Configuration for Sabre Red Workspace .............................................................. 32

Using the Java Distribution from Red Workspace Installation .......................................................... 35

Setting VM arguments ....................................................................................................................... 40

Choosing Plug-ins for Your Run Configuration ................................................................................. 41

Verifying Your Red Workspace Launch Configuration ...................................................................... 43

Adding Graphical View Plug-ins to Your Target Platform ................................................................. 44

Adding Sabre Profiles Plug-ins to Your Target Platform ................................................................... 45

Installing the Red App Development Tools Software ........................................................................... 46

Verifying Development Tools Installation in Eclipse IDE .................................................................. 51

Verifying the Red App Wizards in Eclipse IDE .................................................................................. 51

Opening Red App Help from Eclipse IDE ......................................................................................... 52

Red App SDK on Mac OS .................................................................................................................... 54

Configuring SSLVPN on a Mac ......................................................................................................... 54

Running SDK ..................................................................................................................................... 56

Using TA Sharing .............................................................................................................................. 57

Known issues .................................................................................................................................... 58

Using Red App SDK Sandbox Mode .................................................................................................... 60

SDK Sandbox Mode setup ................................................................................................................ 60

Credentials ........................................................................................................................................ 60

First run ............................................................................................................................................. 60

Sample command set file .................................................................................................................. 61

3 Red App Developer Toolkit Upgrade and Maintenance .................................................71

Upgrading to a New Version of the Developer Toolkit ......................................................................... 74

Extracting a New Version of the Red App Developer Toolkit ............................................................ 74

Contents

Getting Started with Red Apps - Release 2.14.3 v


Adding a New Target Platform for an Upgraded Toolkit ................................................................... 75

Upgrading Your Red App Run Configuration ....................................................................................... 79

Upgrading to a New Version of the Development Tools ...................................................................... 81

Target Platform Maintenance Procedures ............................................................................................ 83

Passing Proxy Settings for Red Workspace in Development Mode ................................................. 83

Adding and Removing Plug-ins from a Run Configuration ............................................................... 84

Removing the Red App Target Platform from Eclipse ...................................................................... 87

Development Tools Maintenance Procedures ..................................................................................... 88

Removing the Red App Development Tools from Eclipse ................................................................ 88

Installing the Red App Development Tools After Removal ............................................................... 92

A Developer Resources – A Comprehensive List 95

Getting Started with Red Apps - Release 2.14.3 vii ©2011, 2016 Sabre, Inc. Proprietary and confidential. October 2016

Figures

1 Folder Structure of the Extracted Red App Developer Toolkit ............................................................. 22

2 Expanded Folder Structure After Installation of the Developer Toolkit ................................................ 22

3 Selecting the Workspace on the Workspace Launcher Dialog ............................................................ 23

4 Preferences Option on the Window Menu ............................................................................................ 23

5 Adding Preferences for Target Platform Plug-in Development ............................................................ 24

6 Initializing the Target Definition with Nothing ....................................................................................... 25

7 Assigning a Name to the Target Platform ............................................................................................ 26

8 Selecting a Source Directory for the Plug-ins ....................................................................................... 27

9 Selecting the Path Name for the Plug-in Directory ............................................................................... 28

10 List of Installed Plug-ins on the Preview Contents Screen ............................................................... 29

11 New Target Definition with Confirmed Quantity of Plug-ins .............................................................. 30

12 New Target Platform Definition on the Preferences Window ............................................................ 31

13 Run Menu .......................................................................................................................................... 33

14 Run Configurations Wizard ............................................................................................................... 33

15 Run Configuration for Red Apps on the Main Tab ............................................................................ 34

16 Installed JREs in Preferences ........................................................................................................... 35

17 Add JRE Dialog in Eclipse ................................................................................................................. 36

18 Add JRE Type Dialog ........................................................................................................................ 37

19 JRE Definition Screen ....................................................................................................................... 38

20 Installed Sabre Red Workspace JRE ................................................................................................ 39

21 Plug-ins for the Run Configuration on the Plug-ins Tab .................................................................... 41

22 No Detected Problems on the Validation Dialog ............................................................................... 42

23 Problems Detected on the Validation Dialog for a Run Configuration .............................................. 42

24 Sabre Red Login Dialog .................................................................................................................... 43

25 Red App Toolkit Folders .................................................................................................................... 46

26 Install Available Software Window for Development Tools ............................................................... 46

27 Choosing the Location of the devtools Folder on the Add Repository Dialog ................................... 47

Figures

Getting Started with Red Apps - Release 2.14.3 viii ©2011, 2016 Sabre, Inc. Proprietary and confidential. October 2016

28 Selecting Red App Dev Tools on Install Available Software ............................................................. 48

29 Confirming the Installation of the Dev Tools on the Install Details Window ...................................... 49

30 Review Licenses Window for Red App Dev Tools ............................................................................ 50

31 Security Warning for Installation of Red App Dev Tools Software .................................................... 50

32 Red App Wizards on the Select a Wizard Screen............................................................................. 52

33 Red App Help Integrated into Eclipse Help ....................................................................................... 53

34 Folders for Multiple Versions of the Developer Toolkit ..................................................................... 75

35 Active Target Platform on the Preferences Window ......................................................................... 76

36 Upgraded Red App Target Platform in Eclipse Preferences Window ............................................... 78

37 Upgrading Plug-ins in the Run Configuration .................................................................................... 79

38 Proxy Settings for Red Workspace on the Arguments Tab .............................................................. 83

39 Workspace and Target Platform Plug-ins in the Run Configurations Window .................................. 84

40 Installed Red App Dev Tools on the Eclipse Installation Details Window ......................................... 89

41 Uninstall Details Window in Eclipse .................................................................................................. 90

42 Removal of Red App Dev Tools from Eclipse SDK Installation Details ............................................ 91

43 Choosing a Location to Reinstall the Red App Dev Tools ................................................................ 92

Getting Started with Red Apps - Release 2.14.3 ix ©2011, 2016 Sabre, Inc. Proprietary and confidential. October 2016

Legal Disclaimers and Red App

Advisories

Legal Disclaimers

The information contained herein should be considered the confidential property of

Sabre® Holdings. This document may not be copied or distributed in whole or part

by either electronic or paper means without the express consent of Sabre.

This document is for informational purposes only. Usage is subject to the terms

imposed by the Sabre Authorized Developer Agreement.

Sabre Holdings MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS

DOCUMENT.

THE SOFTWARE, SAMPLE CODES AND ANY COMPILED PROGRAMS CREATED USING THE

SOFTWARE ARE FURNISHED "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING BUT

NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY SABRE,

ITS AGENTS OR EMPLOYEES SHALL CREATE A WARRANTY OR IN ANY WAY INCREASE THE

SCOPE OF THIS WARRANTY, AND YOU MAY NOT RELY ON ANY SUCH INFORMATION OR

ADVICE. SABRE DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS

REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE SOFTWARE, COMPILED

PROGRAMS CREATED USING THE SOFTWARE, OR WRITTEN MATERIALS IN TERMS OF

CORRECTNESS, ACCURACY, RELIABILITY, CURRENTNESS, OR OTHERWISE. THE ENTIRE RISK

AS TO THE RESULTS AND PERFORMANCE OF THE SOFTWARE AND ANY COMPILED

APPLICATIONS CREATED USING THE SOFTWARE IS ASSUMED BY YOU. BY YOUR USE, YOU

AGREE THAT NEITHER SABRE NOR ANYONE ELSE WHO HAS BEEN INVOLVED IN THE

CREATION, PRODUCTION OR DELIVERY OF THE SOFTWARE SHALL BE LIABLE FOR ANY

DIRECT, INDIRECT, CONSEQUENTIAL, OR INCIDENTAL DAMAGES (INCLUDING DAMAGES FOR

LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION,

AND THE LIKE) ARISING OUT OF THE USE OF OR INABILITY TO USE SUCH PRODUCT EVEN IF

SABRE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THIS SOFTWARE IS

OWNED AND COPYRIGHTED BY SABRE OR ITS THIRD PARTY SUPPLIERS. YOUR LICENSE TO

UTILIZE IT CONFERS NO OWNERSHIP RIGHTS IN THE SOFTWARE OR THOSE PORTIONS YOU

MAY USE IN A PROJECT. YOU AGREE TO INDEMNIFY AND HOLD HARMLESS SABRE AND ITS

AFFILIATES FOR ANY CLAIM BROUGHT AGAINST IT BASED UPON YOUR USE OF THE

SOFTWARE OR ANY COMPILED PROGRAMS CREATED USING THE SOFTWARE.

Legal Disclaimers and Red App Advisories Red App Advisories

Getting Started with Red Apps - Release 2.14.3 x


Red App Advisories

Please review the following advisories!

Compliance with Red App Requirements and Standards

Sabre Scan Charges

Modification or Termination of Service of Red App

Compliance with Red App Requirements and Standards

You must examine your Sabre® Red™ App projects to ensure that your plug-ins comply with all

Red App requirements and standards. Additionally, if you create a project that is based on the Red

App sample plug-ins, you must put the content of the Sabre® Red™ Workspace classes into your

own new classes and new packages.

Sabre will not accept or certify Red Apps with classes or packages that are taken from the Red

App sample plug-ins.

For other requirements and standards, see the topics in the "Red App Requirements and

Standards" book in the Red App help and the following additional information:

Red App Developer Guidelines

Security Requirements in Red Apps

Sabre Red Styles

Sabre Scan Charges

Both agency clients and Sabre Red App Certified Developers are billed for scan charges when

they access Sabre® GDS content through either the Sabre emulator or Sabre® Web Services in

the PRODUCTION environment.

Agency customers are billed for scan charges whenever their client Red App consumes any of the

Sabre communications services that are called by the Red App that is deployed to their Sabre Red

Workspace desktop. These scan charges are also applied to developers when they consume Sabre

GDS content during development and testing of their applications.


Getting Started with Red Apps - Release 2.14.3 xi ©2011, 2016 Sabre, Inc. Proprietary and confidential. October 2016

Three types of scan charges may be applied: basic, fare, and search. Basic type scans cost less

than fare or search type scans.

Sabre Red App certified developers may want to consider the types of scans that are associated

with the applications they are developing. This may help with client design and user interaction

by limiting the more expensive searches and caching responses.

As an example, Sabre Red App Certified Developers may impose constraints on the types of

searches that end-users can do, and the quantity of searches they can perform. Letting end-users

search for all availability and fares without specific dates is more expensive than searches based

on specific dates.

Developers may also want to cache responses whenever it makes sense, but they must also be

aware of limitations on the data that is retrieved from the Sabre GDS, such as the length of time

for which data is valid.

The Red App Developer Toolkit does not limit flexibility when it comes to creating meaningful

workflows for organizations and customers. However, there are efficient ways to build client

applications and workflows to minimize scans, which helps to minimize costs to agency clients.

For more information about scan charges, please consult your Sabre Red App Developer Contract

or contact your Sabre account manager.

Modification or Termination of Service or Red App

Sabre reserves the right to modify, suspend or discontinue the Red App Centre services or any

part thereof at any time, with or without notice to you or liability to Sabre. Additionally, you

acknowledge and agree that Sabre may suspend or deactivate any Red App which creates

technical issues, unauthorized use, any impairment of Sabre GDS (Sabre System) integrity or use

or any other user’s access to or operation of the Sabre System, including, but not limited to:

Red App stops responding

Red App causes Sabre Red Workspace or its plug-ins to freeze or shut down

Red App causes issues by using too much memory or percentage of CPU capacity

Red App causes problems or heavy traffic to Sabre server side systems

Red App uses provided API against unauthorized purpose or design

Red App creates legal compliance issues

Red App contains malicious code such as spyware

Getting Started with Red Apps - Release 2.14.3 1 ©2011, 2016 Sabre, Inc. Proprietary and confidential. October 2016

Overview of Red App Start-up

Sabre Red App Certified Developer Profile

Red App developers need the following skills and expertise to develop plug-ins and clients for

Sabre Red Workspace:

Knowledge of the Sabre Red Workspace client, the technologies that the client is built

upon, and the APIs that the client provides

Java programming

Development using the Eclipse IDE

Knowledge of extension points, OSGi services, and APIs, if you are developing plug-ins

that use Eclipse RCP functionality created by Sabre

NOTE: The technology that Red App developers choose will dictate the skill set that they need.

The preceding list describes skills for Red App developers who want to build advanced

Red Apps using Java and the most sophisticated capabilities in the Red App Developer

Toolkit.

It is not necessary for Red App developers to know about the server-side components in Red

Workspace to integrate or implement an existing application into it.

Red App developers who are planning to develop Red Apps that use cardholder or personal data

also need the following knowledge and skills, and to conform to all security requirements when

designing and developing Red Apps. For more information, see Security Requirements for Red

Apps.

Red App developers must be knowledgeable in secure coding techniques such as

OWASP.

The development of Red Apps must be based on secure coding guidelines to prevent

common coding vulnerabilities in the software development process.

1

Chapter 1 - Overview of Red App Start-up About the Red App Developer Documentation

Getting Started with Red Apps - Release 2.14.3 2


Red App developers must comply with all laws, including applicable data privacy laws

and regulations governing the collection, storage, and use of user data.

About the Red App Developer Documentation

The Red App developer documentation set consists of the documents that are described below.

How to write code for the functionality of a Red App is outside the scope of this documentation.

Getting Started with Red Apps

Information in this document includes the following:

A description of the required system, software, tools, and IDs for Red App development

Topics that explain which login credentials and environments to use for Sabre Red

Workspace and the Sabre GDS during various phases of Red App development and

testing

Procedures to set up and upgrade the Red App development environment. The

development environment includes a Red App target platform, run configuration, and

development tools software.

A comprehensive list of resources for Red App developers

If changes occur after the documentation is completed, a README file is included

within the documentation folder of the Red App Developer Toolkit. These changes may

include the discovery of bugs, omissions errors, or other changes.

Red App Help

After you complete setup of the Red App Developer Toolkit and development tools software, the

Red App developer help is integrated into Eclipse IDE help.

The Red App developer help focuses on creating wrapping plug-ins that are based on internet

technologies and Java-based technologies for Sabre Red Workspace. The procedures focus on

development using Eclipse IDE. The documentation also shows how to add communications and

services to Red Apps. Communications include synchronous services, asynchronous event

listening, and event publishing.

The "About" topics and the procedures explain important requirements. Some of these

requirements include the approved way to design and implement UI elements and technologies,

Chapter 1 - Overview of Red App Start-up About the Red App Developer Documentation



classes, methods, extension points, and properties. Many of the procedures show the easiest way

to create plug-ins using Sabre Red Workspace classes.

Important! Whether you are doing custom development or using the Red App sample plug-ins

and wizards as a basis for your own plug-ins, you are encouraged to review all

Red App requirements and standards in the Red App help, plus the discussions and

procedures in the Red App help that are related to the functionality you are

including in your Red App. This will help you ensure that your Red App meets

Sabre's requirements.

Other procedures are included for creating and securing a Red App bundle, creating plug-in

projects, and the sample plug-ins, and running the Red App wizards.

Red App Developer FAQs

The Developer FAQs include help with login credentials, resources for working in the

Certification (CERT) environment, and more.

Red App Release Notes

Release notes are provided with every release of the Red App Developer Toolkit.

Security Requirements for Red Apps

You are required to review this information to ensure that your Red App complies with all

requirements for security.


This document has general legal requirements and guidelines to help you ensure that your Red

Apps comply with Sabre's standards.

Chapter 1 - Overview of Red App Start-up For first-time Red App Developer Toolkit setup procedures, see Chapter 2, "Sabre Scribe Compiler



Toolkit Setup Process

1. Obtain the required software and tools. Sabre provides you with the IDs you need. (See

Required Developer Software, Tools, and IDs.)

2. Install or upgrade the Red App Developer Toolkit. Complete the procedures below to

setup or upgrade the following:

A Red App target platform. After you add your target platform, you have access

to all plug-ins in the Developer Toolkit that you need to develop Red Apps. Sample

plug-ins that you can import into your workspace are also included.

Run configuration for Sabre Red Workspace. A run configuration lets you

launch Red Workspace in development mode from Eclipse IDE.

Red App development tools. After you install the development tools, you can

access the Red App help and Red App wizards.

For first-time Red App Developer Toolkit setup

procedures, see Chapter 2, "Sabre Scribe

Compiler

Included as part of the native Sabre Red App Developer software tools for Eclipse IDE is a 32 bit

Sabre Scribe compiler (compatible with 64bit Windows Operating Systems).

Red App Developers can now also get access to Scribe Designer and Compiler tool as part of the

Sabre Red App Developer Toolkit, allowing them to Create/Edit & Modify Sabre Scripts and

also wrap them into Sabre Red Apps to take advantage of Sabre Red Workspace provisioning

capabilities. Scribe developers that wish to continue deploying Sabre Scripts in the legacy

method can continue using their existing process.

The Red App Developer Toolkit Scribe Designer provides the same features as the existing

Eclipse Sabre Scribe Developer. For more information on converting Sabre Scripts into Red

Apps and the benefits of integrating with the Sabre Red App technology, please visit the

integrated Eclipse Red App documentation after Installing the Red App Development Tools

Software that is required to get access to Developer Documentation and Tools, including Sabre

Scribe Compiler.




To get access to the Scribe Designer and compiler, follow the Red App Developer Toolkit Setup

process and then read the Scribe Environment Setup section.

For more information on developing Sabre Scripts, view the Sabre Scribe Resources.




Setup for Red App Development."

For Developer Toolkit upgrade procedures, see Chapter 3, "Red App Developer Toolkit

Upgrade and Maintenance."

3. Read about the following information in this document to understand Red Workspace and

Sabre emulator (Sabre host) environments, and how to use your Sabre login IDs in these

environments:

Use of Red Workspace and Sabre GDS Environments

Use of Login IDs for Development and Testing

4. After you set up your target platform and install the development tools software, open the

Red App help from within Eclipse. For guidance, refer to the help topic, "How Do I

Start?" This topic has links to other help topics where you can obtain more information.

5. Consult the Red App Developer FAQs as needed. This document is included in the Red

App Developer Toolkit. After the ZIP file is extracted, the FAQs are located in the

documentation folder.

Chapter 1 - Overview of Red App Start-up Technical Components in the Red App Developer Toolkit



Technical Components in the Red App Developer

Toolkit

The Red App Developer Toolkit includes everything that you need to set up your development

environment in Eclipse IDE and to develop Red Apps. The Toolkit includes the components that

are described in this topic.

The functionality that you can use in the Developer Toolkit is described in Red App help.

Red App Target Platform Plug-ins

The Red App target platform has the complete code base that you need to develop Red Apps. This

includes the following:

Eclipse 3.6 plug-ins that are required to run Sabre Red Workspace plug-ins

A set of required Sabre and Eclipse Foundation core and platform plug-ins that compile

and run plug-ins under development

These plug-ins enable you to run Sabre Red Workspace in development mode using

Eclipse IDE.

When you extract the Developer Toolkit ZIP file, the targetplatform folder is created

automatically. This folder includes all components of the Red App target platform.

Red Workspace in Development Mode

When you set up your Red App target platform, you also choose a workspace for your Red App

project and a run configuration using Eclipse IDE. With these tools, you develop and manage

your integrated Red App project, and execute Red Workspace in development mode.

Sample Plug-in Projects

The samples folder is created automatically when you extract the Developer Toolkit ZIP file.

This folder has archives of the sample plug-ins. (The sample plug-ins may also be referred to as

"reference" plug-ins, however, this documentation uses the term "sample" plug-in.)




Red App sample plug-ins include all files that a plug-in project needs, such as source code, XML,

and other files. Archives of the sample plug-ins are ready to import directly into Eclipse, and to

launch in Sabre Red Workspace in development mode.

For instructions about importing these samples, descriptions of the sample plug-ins, and

instructions for running each sample, see the Red App help.

Red App Development Tools and Red App Wizards

The devtools folder is created when the Red App Developer Toolkit is extracted. The Red App

development tools integrate Red App wizards and Red App help into Eclipse IDE. You can use

the wizards to create plug-in projects with minimal functionality and to create and secure a Red

App bundle.

After you set up your target platform and run configuration, you must install the Red App

development tools separately.

After installation, you can run any Red App wizards that you want and open the help files.

For descriptions of the wizards and instructions for running them, see the Red App help.

Red App Help

After you install the Red App development tools, Red App help is integrated into Eclipse IDE

help.

To access the Red App help from Eclipse IDE, choose Help > Help Contents. For more

information, see Opening the Red App Help.

JavaDocs

When the Developer Toolkit is extracted, JavaDocs are extracted to the Javadoc folder

automatically, ready to use.

redapp_schema.xsd File

The redapp.xml configuration file that you create must be validated against

redapp_schema.xsd. When the Developer Toolkit is extracted, this schema is located in the




documentation folder. For more information, see "Building a redapp.xml File" in Red App

Help.

Red App Developer Toolkit Upgrade Strategy

The Red App Developer Toolkit is upgraded to a new version periodically. When an upgrade to

this Toolkit occurs, a new version of the Red App target platform is created, along with new

versions of other toolkit components, as needed.

A new build may consist of any of the following:

New plug-ins and other files

Modified plug-ins that were included in the ZIP file from previous builds

Files from the previous release that are not modified

Some files may also be removed in the new version.

The Toolkit ZIP file for every new build is self-contained. An upgraded build has no

dependencies on previous builds. Therefore, if you did not implement a previous version of the

Red App Developer Toolkit, you can simply implement the latest version without the need to

install patches or upgrade packages.

The overall process for developers to implement a new version of the Toolkit is to extract the ZIP

file into the same parent folder in which previous Toolkit versions were extracted. In Eclipse, add

a new target platform for the new Toolkit version, and then upgrade the existing Red App run

configuration and development tools software.

When the Red App Developer Toolkit is upgraded to a new version, it is recommended that you

retain the existing Red App target platform, and add a new target platform for the upgraded

version. This is useful for several reasons:

You can use both the older and the newest development environments for testing.

If you encounter problems while you are upgrading, you will have another environment

that is operable.

It is also recommended that you retain the same workspace location for all versions.

When plug-ins are modified from one build to the next, the modifications may alter the behavior

of your existing plug-ins, therefore, you are advised to test your applications using the new

environment.




For complete information about upgrading the Red App Developer Toolkit, see Upgrading the

Developer Toolkit to a New Version.

Graphical View and Sabre Profiles Plug-ins

By adding graphical view or Sabre Profiles plug-ins into your Red App target platform, you can

build Red Apps that listen for events that are triggered by those applications in the same way that

Red Apps can listen for Sabre commands in classic view. The current events include Air

Availability, Car, Hotel, Change Work Area, FLP Path Shopping, and Gain or Loss of Focus

triggered by graphical view and Profile Data Moved to PNR triggered by Sabre Profiles.

The graphical view plug-ins and Sabre Profiles plug-ins packages is completely self-contained.

There are no dependencies on previous versions. After you complete setup of your target

platform and run configuration using the Red App Developer Toolkit, you simply download the

latest package and add it to your target platform and run configuration. When the package is

upgraded to a new version, download and install it as usual, after upgrading your target platform

and run configuration.

Chapter 1 - Overview of Red App Start-up Red Workspace and Sabre GDS Environments



Red Workspace and Sabre GDS Environments

Development Mode

After you set up your Red App target platform and run configuration in Eclipse IDE, you can

launch Red Workspace in development mode. Development mode simulates Sabre Red

Workspace.

Use Red Workspace in development mode for development, experimentation, and local testing of

your Red App. You can also run the sample Red App plug-ins and wizards.

Sabre Red Workspace in development mode embeds Sabre emulator, or classic view (this

documentation refers to classic view as Sabre emulator).

Certification

After you submit your Red App to Sabre for validation and certification, you will be notified that

your Red App is available in Sabre Red Workspace CERT. Install the CERT version of Red

Workspace to test your Red App in CERT. Installation and testing in CERT is based on approval

by Sabre.

Tip! A resource that explains the CERT environment of Sabre and CERT refreshes is available

on eservices.sabre.com. See the Red App Developer FAQs for information about

obtaining this resource.

Production

If you report that your testing in CERT is successful, Sabre requests that you test your Red App

in the PROD environment of Red Workspace. In the request, Sabre asks you to collaborate with

your beta customers to test your Red App. Sabre will load your Red App to PROD Red

Workspace and provision it to you and your beta customers in PROD.

Test your Red App in the PROD environments of Red Workspace, the Sabre GDS, or the

emulator. Your beta testers will use the PROD environments of Red Workspace to test your Red

App.

http://eservices.sabre.com/

Chapter 1 - Overview of Red App Start-up Red Workspace and Sabre GDS Environments



From Sabre emulator, you can log in to the PROD environment of the Sabre GDS. You can also

change to the CERT environment.

NOTE: Both the CERT and PROD environments of Sabre Red Workspace are available

24 hours, 7 days per week.

Chapter 1 - Overview of Red App Start-up Using Your Sabre ID and Other IDs



Using Your Sabre ID and Other IDs

After you and Sabre agree on all terms, Sabre assigns a Sabre ID and PCC. This ID grants access

to the PRODUCTION and CERT environments of Sabre Red Workspace and the Sabre GDS

(host). The Sabre ID and PCC are the same in both environments, but the passwords for each

environment differ.

CERT ID and PCC

Your CERT Sabre ID and PCC log you in to the following systems:

Sabre Red Workspace in development mode

CERT environment of the Sabre GDS from Sabre emulator

CERT Red Workspace

PROD ID and PCC

Your PROD Sabre ID and PCC log you in to the following systems and sites:

PROD environment of the Sabre GDS from Sabre emulator

PROD Red Workspace

Agency eServices (http://eservices.sabre.com). You can access resources and

also identify troubleshooting resources using this site. For more info, see Documentation

and Training on Other Technologies and the Red App Developer FAQs.

Sabre Red App Centre (http://www.sabreredappcentre.com). After you log in,

you can access the Dev Centre. The Dev Centre is one of several sections in the Sabre

Red App Centre. This documentation refers to sections on the Red App Center when a

distinction is needed, however, you always log in to the Red App Center, and then

navigate to the section that you want.

NOTES:

Sabre GDS passwords expire after 45 days without activity. To avoid automatic

expiration of your passwords, you are advised to log in to each environment of the Sabre

GDS regularly. You must also reset or change your passwords every 90 days.

For help with login credentials and using the Sabre GDS, refer to Red App Developer

FAQs. In particular, see the following sections in the FAQs: "Sabre Login Issues" and


http://www.sabreredappcentre.com/

Chapter 1 - Overview of Red App Start-up Using Your Sabre ID and Other IDs



"Sabre GDS Help." (When you extract the Red App Developer Toolkit ZIP file, the FAQs

are in the documentation folder. This document is also available on the Dev Centre.)

Other IDs

Other IDs that you may use are described as follows:

DevStream. Sabre assigns you another ID to access the Red Apps group in the DevStream

community, where you can contact other Red App Certified providers and Sabre

resources for questions or comments on developing Red Apps.

Developer Resource Center website. If you have the proper agreements to use Sabre Web

Services, you also receive a login ID for this repository.

For more information about these items, please consult your Sabre Red App Developer Contract

or contact your Sabre account manager.

Chapter 1 - Overview of Red App Start-up Required Developer Software, Tools, and IDs



Required Developer Software, Tools, and IDs

Sabre Red App Certified Developers need the following software, tools, and login credentials for

Red App development:

Installation of the Java Platform, Standard Edition 8, Update 25, 32-bit, Development Kit

(JDK 8. Update 25.).

You can download the JDK from

http://www.oracle.com/technetwork/java/javase/downloads/index.html or from the Sabre

Red App Centre Developer Resource Centre

If you use the Java distribution from the Sabre Red Workspace installation, you do not

need to install this.

Installation of Eclipse Classic 4.4.1 for the Microsoft Windows 32-bit operating platform.

You can run Eclipse Classic for the Windows 32-bit operating system from the Windows

64-bit operating system.

You can download this from http://eclipse.org/downloads or from the Sabre

Red App Centre Developer Resource Centre

The latest version of the Red App Developer Toolkit. This Toolkit includes components

for the Red App target platform, which is essential for Red App development. The Toolkit

also has sample plug-ins, the Red App Development Tools (for using the wizards), and

the Red App developer documentation. After you set up your development environment,

you launch Sabre Red Workspace in development mode from Eclipse IDE.

For installation of the toolkit and configuration of the Red App development

environment, see Chapter 2 in this document.

Login credentials with authentication to both the Certification and the Production

environments of Sabre Red Workspace and the Sabre GDS, and a Sabre PCC

A Pseudo City Code, or PCC, is Sabre's 4-character alphanumeric identifier. All Red App

developers receive a PCC as part of the existing Sabre Authorized Developer on-

boarding process.

These login credentials include a Sabre ID, password, and PCC. Production login

credentials are used to log in to eservices.sabre.com and the Sabre Red App Centre

/ Dev Centre.

Note: With the Red App SDK version 2.10 of higher installed you can start Red App

development without having Certification and Production credentials set up using

SDK Sandbox Mode which does not require any connectivity to Sabre

infrastructure and allows you to run and test your Red App against mocked Sabre

http://www.oracle.com/technetwork/java/javase/downloads/index.html

https://www.sabreredappcentre.sabre.com/RAC/Dev%20Centre.aspx

http://eclipse.org/downloads


Chapter 1 - Overview of Red App Start-up Required Developer Software, Tools, and IDs



Host and Sabre Web Services. When running SDK in Sandbox Mode you use fake

credentials and do not need a Terminal Address (use pooled TA connection mode

with empty pool name). However, final tests and certification of a Red App are

always performed on Certification environment and do require valid credentials as

well as network connectivity.

A Terminal Address (TA) with access to the Certification (CERT) environment

Installation of the CERT and Production (PROD) environments of Sabre Red Workspace

for development.

After Sabre validates and certifies a Red App, developers are required to test their app in

CERT, and to test their app later, in PROD Sabre Red Workspace.

Compliance with the minimum network requirements to connect to the Sabre GDS:

1. Sabre Virtual Private Network Connection (SSLVPN). This is a customer-supplied

Internet connection.

56 Kbps or faster (56 Kbps for a single workstation only)

Note: Ports 443 & 80 are required for Sabre Red Workspace. Write permission is

required to the etc directory (host and lmhost files) for the Sabre VPN.

2. Private Connection. This is a dedicated connection to Sabre.

Business to Business VPN (B2BVPN)

Legacy Frame Relay

Managed Network Services (Frame or DSL)

Vendor Access Room connections

Note: Ports 443, 80, 389, 30030, 30031, 30032, and 30051 must be open for the

Workspace communication processes to work properly.

Sabre Red App Certified Developers who want to develop applications that consume

Sabre Web Services must have previously acquired credentials and a Sabre Web Services

developer license agreement. Additionally, downline agreements may be required to

allow agencies to run the apps that are built to consume Sabre Web Services depending

on the services that are consumed.

Access to eservices.sabre.com. Your Production Sabre GDS login credentials also

grant you access to eServices.

A Code Signing Certificate to sign a Red App bundle. The certificate must be valid for a

minimum of 30 days, starting from the date that Sabre validates your Red App. Obtain a

digital certificate from a certificate authority that Sabre supports. Sabre supports the

following vendors:

Verisign

Chapter 1 - Overview of Red App Start-up Technical Support



Thawte

Xramp (Trustwave)

Comodo Group

Technical Support

For help with the Red App Developer Toolkit, send e-mail to second level support at the

following address: [email protected]. This includes help downloading the Toolkit,

setting up and upgrading the Red App development environment, and installing and upgrading

the Red App Development Tools.

To report bugs, documentation errors, or other issues with the Red App Developer Toolkit, send

e-mail to the following address: [email protected]

For help with login credentials, PINs, working in the CERT environment of the Sabre GDS, and

locating your regional software support desk, see the Red App Developer FAQs.

mailto:[email protected]

mailto:[email protected]


Sabre Scribe Compiler













Scribe Compiler.




Chapter 2 - Setup for Red App Development Sabre Scribe Compiler



Setup for Red App

Development

The Red App development environment consists of Eclipse IDE, Java JDK, a Red App target

platform, Red App run configuration, and Red App development tools software.

The procedures in this chapter are for first-time installation of the Red App Developer Toolkit.

You are required to complete all steps in each part, in their order of presentation.

This chapter is organized into the following parts.

1. Prerequisite Software. Eclipse IDE, the Java JDK, Red App Developer Toolkit, and

optionally, graphical view plug-ins are required to use Eclipse IDE and Java upon which

your target platform and coding are based.

2. Adding Your Red App Target Platform. These steps let you use the functionality in the

Developer Toolkit and import the Red App sample plug-ins.

3. Configuring and Testing Your Red App Run Configuration. These steps let you launch

Sabre Red Workspace in development mode from Eclipse IDE, run the Red App sample

plug-ins, and do local testing of your Red App. After you configure your run

configuration, it is optional to add graphical view plug-ins to your target platform.

4. Installing the Red App Development Tools Software. You must install this to access the

Red App Developer Toolkit help, run Red App wizards and access to the Sabre Scribe

Compiler!

2

Chapter 2 - Setup for Red App Development Prerequisite Software



Prerequisite Software

Downloads

Ensure that you have fulfilled the requirements in Required Developer Software, Tools, and IDs.

Before you configure the Red App development environment, download and install the

following:

JDK 1.8. Update 25 32-bit or the Java distribution from the Sabre Red Workspace

installation.

Eclipse Classic. Red App Developer Toolkit since release 2.13.0 supports Eclipse Classic

version 4.4.1 for the Microsoft Windows 32-bit operating system.

The latest version of the Red App Developer Toolkit

(Optional) If you require graphical view during development of your Red App, you must

download the plug-ins separately. The URL to download the graphical view package is

on the Dev Centre. (http://www.sabreredappcentre.com)

(Optional) If you require Sabre Profiles during development of your Red App, you must

download the plug-ins separately. The URL to download the Sabre Profiles package is on

the Dev Centre. (http://www.sabreredappcentre.com)

All required resources (Eclipse, Java, Red App Red App Developer Toolkit)are available from or

from the Sabre Red App Centre Developer Resource Centre

Extracting the Red App Developer Toolkit

1. Create a parent folder on your local drive for the Developer Toolkit.

NOTE: You will also use this parent folder to upgrade to new versions of the Toolkit.

2. Download the Developer Toolkit ZIP file to the parent folder. In Figure 1, the parent

folder is SDK, located in C:\SDK.

3. Extract the contents of the Developer Toolkit ZIP file. Be sure to retain folder names.




Chapter 2 - Setup for Red App Development Adding a Red App Target Platform



1 Folder Structure of the Extracted Red App Developer Toolkit

When you extract the ZIP file into the parent folder, the archive program automatically creates a

new sub-folder that has the following naming convention: RedApp_0.5. The archive program

also creates another set of sub-folders for the files. (See Figure 2.)

2 Expanded Folder Structure After Installation of the Developer Toolkit

Continue with Adding Your Red App Target Platform.

Adding a Red App Target Platform

After you extract the Red App Developer Toolkit, complete the following procedure.

1. Create a folder for your workspace on your local drive. You will continue to use this

folder for your workspace whenever you upgrade the Red App Developer Toolkit to a new

version.

2. Open Eclipse.




3. On the Workspace Launcher dialog, set the location for your workspace. Click Browse,

and navigate to the folder that you created for your workspace. Select the folder and then

click OK. (See Figure 3.)

3 Selecting the Workspace on the Workspace Launcher Dialog

4. From the Window menu, choose Open Perspective > Other > Plug-in Development.

Click OK.

5. From the Workbench menu bar, choose Window > Preferences. (See Figure 4.)

4 Preferences Option on the Window Menu

Eclipse displays the Preferences window where you will set preferences for your target

platform.




6. In the Preferences panel, expand Plug-in Development, and then select Target

Platform. The Target Platform window replaces the General Preferences window.

(See Figure 5.)

5 Adding Preferences for Target Platform Plug-in Development

7. Click Add to start the New Target Definition wizard. (See Figure 6.)




6 Initializing the Target Definition with Nothing

8. Select Nothing: Start with an Empty Target Definition from the Initialize the Target

Definition with list.

9. Click Next. Eclipse displays the Locations tab on the Target Content screen.

(See Figure 7.)




7 Assigning a Name to the Target Platform

10. In the Name field, type a name for your Red App target platform. Whenever you develop

plug-ins for Sabre Red Workspace, this is the target platform that you will use.

Tip: You may want to choose a name that describes the purpose of the target platform, for

example, "RedApp."

11. On the Locations tab, click Add to open the Add Content dialog. (See Figure 8.)




8 Selecting a Source Directory for the Plug-ins

12. Select Directory.

13. Click Next to open the Add Directory screen. (See Figure 9.)




9 Selecting the Path Name for the Plug-in Directory

14. In Location, click Browse. Navigate to the path of the Red App targetplatform

folder. (For this path, refer to Step 3 in Extracting the Red App Developer Toolkit. On the

dialog, click OK to accept the location.

Tip: On the Add Directory screen, whenever you add a new version of the Red App target

platform, choose the path of the targetplatform folder for the new version of the Red

App Developer Toolkit.

15. On the Add Directory screen, click Next to display the Preview Contents screen.

(See Figure 10.)




10 List of Installed Plug-ins on the Preview Contents Screen

Your list of plug-ins should be similar to the list in Figure 10.

16. When you are done reviewing the plug-ins on Preview Contents, click Finish.

The New Target Definition dialog displays your new target definition. (See Figure 11.)




11 New Target Definition with Confirmed Quantity of Plug-ins

Note: Plug-ins will be added to the Red App target platform continually. Therefore, whenever

the Red App target platform is upgraded, the quantity of plug-ins increases.

Confirm that you have a minimum of 100 plug-ins in the directory that you selected.

17. You are done defining your target platform. On the New Target Definition dialog, click

Finish.

Eclipse displays the Preferences window again with your target platform.

(See Figure 12.)




12 New Target Platform Definition on the Preferences Window

18. On the Target Definitions list, select the check box that is adjacent to your new target

definition.

19. Click Apply to apply the changes.

20. Click OK to close the Preferences window.

Continue with Configuring and Testing Your Red App Run Configuration.

Chapter 2 - Setup for Red App Development Configuring and Testing Your Red App Run Configuration



Configuring and Testing Your Red App Run

Configuration

A run configuration consists of settings that you define for a particular development project. The

settings include your runtime workspace, runtime environment, and parameters for running or

debugging your plug-ins in the workspace. You can use the Java distribution from Sabre Red

Workspace for your run configuration. (It is also possible to define multiple run or launch

configurations.)

Complete the following procedures in the order below to set up a run configuration for the

runtime workspace, program, and JRE. The procedures are divided into the following parts:

Setting Up a Run Configuration for Sabre Red Workspace

Using the Java Distribution from Red Workspace Installation

Choosing Plug-ins for Your Run Configuration

Verifying Your Red Workspace Launch Configuration

(Optional) Adding Graphical View Plug-ins to Your Target Platform

(Optional) Adding Sabre Profiles Plug-ins to Your Target Platform

(Optional) Passing Proxy Settings for Red Workspace in Development Mode

Setting Up a Run Configuration for Sabre Red Workspace

1. From the Workbench menu bar, choose Run. (See Figure 13.)




13 Run Menu

2. Choose Run Configurations. Eclipse opens the Run Configurations wizard.

(See Figure 14.)

14 Run Configurations Wizard




3. From the panel on the left, right-click Eclipse Application, and then choose New.

Eclipse creates a default run configuration, which the Main tab displays. (The run

configuration for Eclipse is shown in Figure 15.)

15 Run Configuration for Red Apps on the Main Tab

4. In the Name field, type a name for your run configuration. You will use this configuration

name whenever you want to run or debug any of your plug-ins in Sabre Red Workspace.

Tip: Use a name that distinguishes this run configuration from run configurations for your

other projects.

5. In the Program to Run group, select Run a Product.

6. From the drop-down list, select com.sabre.edge.app.product.

7. In the Java Runtime Environment group, select Java 1.8 from Runtime JRE.

8. For Java Executable, select default.




Using the Java Distribution from Red Workspace Installation

Configure your run configuration to use the Java distribution from the Sabre Red Workspace

installation.

9. On the Main tab, click Installed JREs. (See Figure 16.)

16 Installed JREs in Preferences

Eclipse displays a list of your Java runtime environments. (See Figure 17.)




17 Add JRE Dialog in Eclipse

10. Click the Add button to open the Add JRE Type dialog. (See Figure 18.)




18 Add JRE Type Dialog

11. For JRE type, select Standard VM.

12. Click Next to display the JRE Definition screen. (See Figure 19.)




19 JRE Definition Screen

13. Next to the JRE home field, click Directory. Navigate to your Sabre Red Workspace

installation directory, and then select the Pulse Explorer\jre directory path.

The typical path where you can find this directory follows:

C:\program Files\Sabre Red Workspace\Pulse Explorer\jre

14. In the JRE Name field, type a name for your Sabre Red Workspace JRE.

15. Click Finish to display the Installed JREs screen. (See Figure 20.)




20 Installed Sabre Red Workspace JRE

Your SRW JRE should appear in the list.

16. Select the check box next to your SRW Java Runtime name, and then click OK.

When you are done, the Runtime JRE field on the Main tab is changed to your Sabre Red

Workspace JRE. Eclipse now uses the SRW Java Runtime at runtime during development.




Setting VM arguments

We are recommending configuring the following VM arguments in your launch configuration, as

the same are set used by Sabre Red Workspace:

-Xms128m

-Xmx512m

-Dosgi.parentClassloader=ext

Using them will make your development environment consistent with production version.

Setting the “parentCLassloader” VM argument in Run Configuration allows the usage of

Extended class loader.




Choosing Plug-ins for Your Run Configuration

17. Click the Plug-ins tab. (See Figure 21.)

21 Plug-ins for the Run Configuration on the Plug-ins Tab

18. From the Launch With list, select Plug-ins Selected Below Only.

Eclipse automatically selects the appropriate plug-ins in the Target Platform group in the

Plug-ins list.

19. If you have plug-ins in your Workspace group, Eclipse displays your plug-ins. Select the

plug-ins that you want to launch in Sabre Red Workspace.




20. Select the Include Optional Dependencies When Computing Required Plug-ins check

box.

21. Select the Add New Workspace Plug-ins to This Launch Configuration

Automatically check box.

22. Before you launch the Sabre Red Workspace application, click Validate Plug-ins. Plug-in

validation verifies that you selected all necessary dependencies.

If Eclipse successfully verifies the dependencies, the Validation dialog displays a

message that no problems were detected. (See Figure 22.)

22 No Detected Problems on the Validation Dialog

If Eclipse finds missing dependencies, the Validation dialog describes the problems it

finds. (See Figure 23.)

23 Problems Detected on the Validation Dialog for a Run Configuration




23. To repair the problems automatically, click OK. The Plug-ins tab is opened on the Run

Configurations wizard. (See Figure 21.)

24. On the Plug-ins tab, click Add Required Plug-ins.

25. Click Apply to save your changes.

26. Click Run to launch Sabre Red Workspace.

If you have successfully set up your run configuration, the Sabre Red Workspace login dialog is

displayed. (See Figure 24.)

What to Do Next

Verify that you can launch Sabre Red Workspace from Eclipse IDE

Verifying Your Red Workspace Launch Configuration

27. To log in to Red Workspace in development mode, use your CERT Sabre login

credentials. (For information about Sabre IDs, see Using Your Sabre IDs and Other IDs.)

24 Sabre Red Login Dialog

You are done setting up your Red App development environment.




What to Do Next

(Optional) Add graphical view plug-ins

(Optional) Add Sabre Profiles plug-ins

(Optional) Add proxy settings to your run configuration to launch Sabre Red Workspace

in development mode.

(Required) Install the Red App development tools software. These tools lets you use the

Red App wizards to create basic plug-ins AND open the Red App developer help!

You can find a description of the Red App wizards and general instructions for running

them in the Red App help.

Adding Graphical View Plug-ins to Your Target Platform

After you set up your Red App target platform and a Sabre Red Workspace run configuration, you

can add graphical view.

28. Log in to the Sabre Red App Center (http://www.sabreredappcentre.com), and then click

the Dev Centre link.

29. Download the graphical view package to the parent folder for your target platform. This

is the folder that you created in Step 1 in Extracting the Red App Developer Toolkit.

30. Extract the files from the graphical view package to this parent folder.

Extracting the files adds a new folder with the name targetplatform_gv

automatically. This child folder contains the graphical view application and plug-ins.

31. Open Eclipse, and then choose Window > Preferences.

32. Choose Plugin Development > Target Platform.

33. Select your Red App target platform, and then click Edit.

34. Choose Add, and then select Directory.

35. For location, navigate to the targetplatform_gv folder.

36. Click Finish.

In the preceding steps, you added a new Red Apps run configuration for Sabre Red Workspace.





What to Do Next

Install the Red App development tools. These tools lets you use the Red App wizards to create

basic plug-ins AND open the Red App developer help!

You can find a description of the Red App wizards and instructions for running them in the Red

App help.

Adding Sabre Profiles Plug-ins to Your Target Platform

After you set up your Red App target platform and a Sabre Red Workspace launch configuration,

you can add Sabre Profiles.

37. Log in to the Sabre Red App Center (http://www.sabreredappcentre.com), and then click

the Dev Centre link.

38. Download the Sabre Profiles package to the parent folder for your target platform. This is

the folder that you created in Step 1 (Extracting the Red App Developer Toolkit).

39. Extract the files from the Sabre Profiles package to this parent folder.

Extracting the files adds a new folder with the name targetplatform_sp

automatically. This child folder contains the Sabre Profiles plug-ins.

40. Open Eclipse, and then choose Window > Preferences.

41. Choose Plugin Development > Target Platform.

42. Select your Red App target platform, and then click Edit.

43. Choose Add, and then select Directory.

44. For location, navigate to the targetplatform_sp folder.

45. Click Finish.

In the preceding steps, you added a new Red Apps run configuration for Sabre Red Workspace.


Chapter 2 - Setup for Red App Development Installing the Red App Development Tools Software



Installing the Red App Development Tools

Software

These instructions show how to install the Red App development tools software.

When you are done, the Red App wizards and Red App Developer Toolkit help are automatically

integrated into Eclipse IDE.

Before you begin, set up your Red App development environment. The development

environment includes the Red App target platform and a Sabre Red Workspace run configuration.

If you installed the Red App Developer Toolkit correctly, your devtools folder should be like

Figure 25.

25 Red App Toolkit Folders

1. Open Eclipse. Choose Help > Install New Software. (See Figure 26.)

26 Install Available Software Window for Development Tools

2. On the Available Software window, click Add.

3. On the Add Repository dialog, click Local. (See Figure 27.)




27 Choosing the Location of the devtools Folder on the Add Repository Dialog

4. On your local drive, navigate to the folder with the Red App Developer Toolkit. Select the

devtools folder, and click OK to accept the location.

5. In the Name field on the Add Repository dialog, type a name for the Red App

development tools that is meaningful to you. This name helps you to identify these tools

in Eclipse. It is displayed on the list of available software sites. Click OK.

Tip: To see the list of software sites, choose Help > Install New Software > Available

Software Sites.

6. On the Install Available Software window, expand Red App Dev Tools. (See Figure 28 .)




28 Selecting Red App Dev Tools on Install Available Software

7. Select the check box that is next to Red App Dev Tools. Click Next.

The Install Details window lists the software that will be installed. This is the name that you

assigned to your repository. (See Figure 29.)




29 Confirming the Installation of the Dev Tools on the Install Details Window

8. Click Next again.

The Review Licenses window displays the licensing agreement. (See Figure 30.)




30 Review Licenses Window for Red App Dev Tools

9. Review the licensing agreement. In order to proceed, accept the agreement, and then click

Finish.

Eclipse displays a Security Warning dialog. (See Figure 31.)

31 Security Warning for Installation of Red App Dev Tools Software

10. On the Security Warning dialog, click OK.




After Eclipse is done downloading and installing the new software, the Software Updates

dialog prompts you to restart Eclipse.

11. For the changes to become effective, click Restart Now.

After Eclipse is restarted, you are presented with the Workspace Launcher dialog.

12. Choose or confirm the location of the workspace for your target platform. Click OK to

accept the location.

What to Do Next

Verify dev tools installation

Verify the Red App Wizards

Open the Red App Help

Verifying Development Tools Installation in Eclipse IDE

You can review the Installed Software page.

On the workbench main menu, choose Help > About Eclipse SDK.

On the About Eclipse SDK dialog, click Installation Details.

On the Installed Software tab in the Installation Details window, the Name list should

display Red App Dev Tools. The software version is also displayed. For an example, see

Figure 40.

Verifying the Red App Wizards in Eclipse IDE

You can verify that the Red App wizards are available.

On the File Menu on the Eclipse workbench main menu, choose New > Other.

The Select a Wizard screen should display the "Red App Development" entry.

When you expand Red App Development, a list of Red App wizards appears. (See

Figure 32.)




32 Red App Wizards on the Select a Wizard Screen

Opening Red App Help from Eclipse IDE

After you set up or upgrade your Red App target platform and the Red App development tools,

you can open the Red App developer help from Eclipse IDE.

1. To open Red App help, choose Help > Help Contents from the Eclipse workbench menu.

Red App Help appears in the Eclipse SDK Help window. (See Figure 33.)




33 Red App Help Integrated into Eclipse Help

If you want to search the help files, you can limit the scope to Red App Help.

2. On the Eclipse Help window, click the Scope link.

3. In the Select Scope dialog, choose Show Only the Following Topics, and click New.

4. On the New Scope dialog, type a name for the scope, for example, Red App Help, and

choose Red App Help from the list. Click OK to close the dialog.

5. Click OK again.

Tip! You can add another scope that includes all help, if you wish.

What to Do Next

Create a plug-in project. You have the following options:

Import a Red App sample plug-in

Run a Red App wizard to create a basic plug-in project or add functionality to an

existing plug-in

Run the Eclipse new plug-in project wizard to create an empty project

For these procedures, see the topics in the "Plug-in Projects" book in the Red App Help.

Chapter 2 - Setup for Red App Development Red App SDK on Mac OS



Red App SDK on Mac OS

In version 2.10 of Red App SDK we introduced additional archive containing Target Platform for

supporting Mac OS. You must download a version targeted for your operating system.

NOTE: Mac OS support for Red App SDK is limited and suffers from several known issues

(listed below in this chapter). The Red App SDK on Mac OS can be used for

development, but you should always test your Red App on Win32 environment before

submit to Red App Centre.

After downloading and installing Eclipse platform and setting up the Red App Target Platform

for Mac OS (procedure similar to what has been described for Win32 in previous chapters)

several additional steps described below are needed to get Red App SDK up and running. Red

App Target Platform for Mac OS is available in Red App SDK inside targetplatform.mac

directory.

Configuring SSLVPN on a Mac

To use SSLVPN, add the following aliases to the lo0 interface by executing commands with root

permissions every time when the system is started:

sudo ifconfig lo0 alias 127.0.0.36









Adding aliases for SSLVPN automatically

We suggest creating a script for launchctl, which will execute automatically whenever the system

starts. The procedure follows.

1. Create the following script:




#!/bin/bash










2. Set executable permissions for the script file:

chmod +x SCRIPT_NAME.sh

3. Create a descriptor file for launchctl:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"

"http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>Label</key>

<string>local.network.aliases</string>

<key>ProgramArguments</key>

<array>

<string>/absolute/path/to/your/SCRIPT_NAME.sh</string>

</array>

<key>RunAtLoad</key>

<true/>

</dict>

</plist>

NOTE: The descriptor must have an absolute path set to your script.

4. Save it as

/Library/LaunchDaemons/local.network.aliases.plist

5. Change the file owner to root or otherwise launchctl cannot execute your script with root

permissions:




sudo chown root


6. Load your to launchctl to execute with root permissions:

sudo launchctl load –w


7. Log out/in or call:

launchctl start local.network.aliases

NOTE: launchctl will add network aliases for all users on this machine.

Running SDK

Sabre provides a separate version of RedApp SDK on a Mac. The only configuration change is

adding a VM parameter –d32 to force Eclipse for using 32-bit Java:




Using TA Sharing

On a Mac, only Java TA Sharing is supported. Perform the following steps to enable it:

1. In Red App SDK open Tools > Options > Sabre System > Connection

2. Select Java TA share

3. Select Terminal Services

4. Type a port number greater than 1023, otherwise TA Sharing will not run.

NOTE: This setup is required for a Mac only, on Windows TA Sharing works fine for all ports.




Known issues

1. Scribe IDE is not supported on Mac OS. You should uncheck it when installing RedApp

Dev Tools:

2. Legacy TA Sharing is not working on a Mac OS, so please use Java TA Sharing instead.

3. Focus is moved to the Emulator view after some actions (such as clicked buttons Cancel

or OK in com.sabre.redapp.example.swt).

4. LauncherBar items disappear when clicked. Also some LauncherBar items disappear for

the first time after Sabre Red Workspace is started (elements are visible again after you

minimize and maximize SRW window).




5. Broken layout for Favorite menu.

6. While clicking on some SRW elements, white blinking may occur.

7. Sabre Emulator might hang after many quick clicks.

8. Red Apps built using the Qik Developer technology is not supported on Mac OS so

neither Qik samples nor Graphical View plug-ins will work on Mac OS.

9. In MAC OS Red Apps will render Web Red Apps using Webkit bundle with Safari.

Developers should always test your Red App on Win32 environment before submit to

Red App Centre, that in this case will render using Internet Explorer Web Toolkit.

Chapter 2 - Setup for Red App Development Using Red App SDK Sandbox Mode



Using Red App SDK Sandbox Mode

Red App SDK Sandbox Mode is a feature that allows running and testing a Red App in isolated

environment – without connectivity to Sabre infrastructure or real Sabre credentials. It may be

useful as a temporary approach when your Sabre credentials are not set up yet and wanting to

test the Red App SDK prior to developing a real Red App or when you need to test your Red App

in specifically hard to reproduce on real environment scenarios. Sandbox Mode allows you to

emulate any Host response as well as any Sabre Web Service response. In Sandbox Mode you

configure Agent Profile information (like ID, language, email address).

SDK Sandbox Mode setup

Prerequisites

com.sabre.edge.platform.optional.sandbox plugin needs to be added to

your Target Platform and Run Configuration.

Run Configuration

Follow all steps for regular configuration and add the following:

-Dredapp.fake.session=true

to VM arguments section on Arguments tab.

Credentials

As there is no connection to Sabre infrastructure no credentials are needed, however you still

will see login screen when running Platform in Sandbox Mode. To get pass it simply enter any 6-

digit Agent id, non-empty password and any 4-character PCC.

First run

First run is required to extract sample XML file with sets of commands and responses. It will be

located in your run configuration workspace in:




.metadata\.plugins\com.sabre.edge.platform.optional.sandbox\reso

urces\default_emulator.xml.

Your run configuration workspace is by default in the same folder as your eclipse workspace.

Sample command set file

Red App SDK comes with a set of sample command/response test cases that you can change and

extend providing responses that you expect for certain command. Command set file contains 3

sections: one for host communication (both emulator and direct), one for SWS and one for agent

profile data.

Host communication

<host-configuration>

<commandset id="001">

<command content="1KRKDFW">

<response>

<content>SIGN IN A</content>

</response>

<response delay="5000">

<content>SECOND RESPONSE</content>

</response>

</command>

</commandset>

</host-configuration>

Communication with Host is defined in this section. All commands should be defined in the

same <commandset> tag, currently only one commandset tag is supported. Responses are

defined within <content> tag. You can define one or many responses for a command. If delay

attribute is defined for response it will be delivered after provided number of milliseconds.

Multiple responses will be delivered in order they appear in file.

SWS communication

<sws-configuration>

<actionset id="001">

<action content="OTA_AirAvailLLSRQ">

<response>

<content>




<![CDATA[

<test>TEST SWS RESPONSE</test>

]]>

</content>

</response>

</action>

</actionset>

</sws-configuration>

SWS communication is based on actions. You can define one XML answer for each action.

Response is defined in <content> tag. Remember to put your xml content in <![CDATA[

]]> tag.

Agent profile information

<profile-configuration>

<agent-id>AGENT_ID</agent-id>

<agency-name>AGENCY NAME</agency-name>

<pcc>PCC</pcc>

<language>LANGUAGE</language>

<country>COUNTRY</country>

<region>REGION</region>

<username>USERNAME</username>

<email>[email protected]</email>

</profile-configuration>

In this section you can provide agent information that would be available with

IAgentProfileService.

Chapter 2 - Setup for Red App Development Sabre Scribe Environment Setup



Sabre Scribe Environment Setup

The below section explains how to setup of your Scribe environment to create and modify native

Sabre Script files (*.SST) to generate Scribe compiled files that can be deployed to Sabre Red

Workspace as native legacy Scripts or wrapping as Sabre Red Apps.

Close all Perspectives - From the Menu, click ‘Window -> Close All Perspectives’

Open a ‘Scribe’ Perspective and Click on the icon to open a perspective:




Select ‘Scribe’ and click ‘OK’

Create a new Scribe Project

Highlight the ‘Project Explorer’ tab




With the ‘Project Tab’ still highlighted, click on ‘File -> New -> Project’ from the menu:

Highlight “General -> Project” and click ‘Next’

Input the desired name of the Project and click ‘Finish’




The new project name will now display in the Project Explorer tab:

Scribe Settings

Configure the compiled path - for each scribe project the developer will have the option to select

where the compiled scripts (.SCC file) are created.

In the Project Explorer tab, highlight the desired Scribe project:




With the desired Scribe project highlighted in the Project Explorer tab, click ‘File -> Properties’:




The ‘Properties for FirstScribeProject’ windows will appear. Select ‘Scribe properties’ on the

left. Make sure the check box for ‘Enable specific project settings’ is checked on. Enter the

desired directory in the ‘Compiled scripts directory’ box, then click ‘OK’:

Creating your first Scribe script

With the desired Scribe project highlighted in the Project Explorer tab, click on ‘File -> New ->

Scribe Script’:




Input the name of the script and click ‘Finish’

A new tab will open for editing the script, and the script will appear in the Project Explorer tab

under the applicable project name:


Red App Developer Toolkit

Upgrade and Maintenance

Before you can upgrade to a new version of the

Red App Developer Toolkit, you must have

installed a previous version. For first-time

installation, complete all procedures in

Chapter 0, "Sabre Scribe Compiler













Scribe Compiler.




3

Chapter 3 - Red App Developer Toolkit Upgrade and Maintenance Before you can upgrade to a new version of the Red App Developer Toolkit, you must have installed a previous version. For first-time installation, complete all procedures in Chapter 0, "Sabre Scribe Compiler



Chapter 3 - Red App Developer Toolkit Upgrade and Maintenance Before you can upgrade to a new version of the Red App Developer Toolkit, you must have installed a previous version. For first-time installation, complete all procedures in Chapter 0, "Sabre Scribe Compiler



Setup for Red App Development."

To upgrade your Red App Developer Toolkit to the latest version, complete all steps in this

chapter in the order in which they are shown. The procedures are organized into the following

parts:

Upgrading to a New Version of the Developer Toolkit

Upgrading Your Red App Run Configuration

Upgrading to a New Version of the Development Tools. You must install or upgrade to a new

version to get the updated Red App help in the latest Developer Toolkit!

This chapter also includes the following maintenance procedures:

Red App target platform maintenance

Red App development tools maintenance

Chapter 3 - Red App Developer Toolkit Upgrade and Maintenance Upgrading to a New Version of the Developer Toolkit



Upgrading to a New Version of the Developer

Toolkit

This procedure is organized into the following sections:

Extracting a New Version of the Red App Developer Toolkit

Adding a New Target Platform for an Upgraded Toolkit

Before you begin, obtain the latest version of the Red App Developer Toolkit from the Dev

Centre. (http://www.sabreredappcentre.com)

Extracting a New Version of the Red App Developer Toolkit

NOTE: Remember to retain the same workspace location in Eclipse that you created when you

set up your target platform. See Adding a Red App Target Platform.

1. Download the ZIP file and place it in the parent folder that you established for Red Apps

when you set up your development environment. (Refer to Step 1 in Extracting the Red

App Developer Toolkit.)

Do not delete any of the sub-folders that contain the previous versions of the Red App

Developer Toolkit.

2. Close Eclipse.

3. Using WinZip or a similar tool, select the Red App Developer Toolkit ZIP file in the

parent folder.

4. Right-click the ZIP file, and then choose Extract to here.

Be sure to retain the folder structure when you extract the file.

If you are using a different archive tool, extract the ZIP file within the same parent folder.





The process of extracting the ZIP file automatically creates a new sub-folder and names

the sub-folder with the upgraded version of the Developer Toolkit. (See Figure 34.)

34 Folders for Multiple Versions of the Developer Toolkit

In the example, RedApp_0.6 is the sub-folder with the upgraded version of the toolkit. This

sub-folder contains additional sub-folders for the contents of the toolkit. Note that folders for the

workspace and run configuration are also shown in Figure 34.

Adding a New Target Platform for an Upgraded Toolkit

5. Open Eclipse. From the Launch Workspace dialog, choose the location of your

workspace. This must be the folder that you created for your workspace in Step 1 of

Adding a Red App Target Platform. In this example, the location is

C:\sdk\workspace.

6. On the Eclipse workbench menu bar, choose Window > Preferences.




7. From the list on the left, expand Plug-in Development, and then select Target Platform.

A list of your target platforms appears in the Target Definitions panel on the right. (See

Figure 35.)

35 Active Target Platform on the Preferences Window

Eclipse should display Active next to your Red App target platform. In the example, the name of

the target platform is RedApp.

8. Click Add.

9. In Adding the Red App Target Platform, complete Step 8 through Step 20.




When you are done adding and verifying the plug-ins, Eclipse displays your new target

platform configuration, which should be similar to the following:

When your new target platform is added, your screen should be similar to Figure 36.




36 Upgraded Red App Target Platform in Eclipse Preferences Window

What to Do Next

Continue with Upgrading Your Red App Run Configuration.

Chapter 3 - Red App Developer Toolkit Upgrade and Maintenance Upgrading Your Red App Run Configuration



Upgrading Your Red App Run Configuration

10. From the workbench menu bar, choose Run > Run Configurations. The Main tab on the

Run Configurations wizard is opened.

11. On the left, select the run configuration that you are upgrading, and then open the Plug-

ins tab. In the example, the name of the run configuration is RedAppRun. (See

Figure 37.)

37 Upgrading Plug-ins in the Run Configuration

12. Select all of the following:

Launch With Plug-ins Selected Below Only

All plug-ins in the Target Platform group on the Plug-ins list

Include Optional Dependencies When Computing Required Plug-ins check box

Chapter 3 - Red App Developer Toolkit Upgrade and Maintenance Upgrading Your Red App Run Configuration



Add New Workspace Plug-ins to This Launch Configuration Automatically check

box

NOTE: If you plan to install new versions of the graphical view plug-ins, be sure to select all

plug-ins in the Target Platform group to ensure that the new graphical view plug-ins are

included.

You can also select the plug-ins in the Workspace group that you want to launch in Sabre

Red Workspace.

13. To ensure that you selected all necessary dependencies, validate the plug-ins for their

dependencies. Click Validate Plug-ins.

If Eclipse successfully verifies the dependencies, the Validation dialog displays a

message that no problems were detected.

If Eclipse finds missing dependencies, the Validation dialog describes the problems it

finds.

14. To repair the problems automatically, click OK.

15. On the Plug-ins tab on the Run Configurations wizard, click Add Required Plug-ins.

16. Click Apply to apply your changes.

17. Close the Preferences window.

You are done upgrading your Red App development environment.

What to Do Next

(Optional) Verify that you can launch Red Workspace in development mode from Eclipse

IDE.

(Optional) Upgrade graphical view communications in your Red App target platform and

run configuration.

(Optional) Pass proxy settings in your run configuration to launch Sabre Red Workspace

in development mode.

(Required) Upgrade the Red App Development Tools. These tools enable the use of Red

App wizards and Red App help.

Chapter 3 - Red App Developer Toolkit Upgrade and Maintenance Upgrading to a New Version of the Development Tools



Upgrading to a New Version of the Development

Tools

When you install a new version of the Red App Developer Toolkit, it is typically installed to a

new location. For example, assume that the location of the previous version of the Toolkit and

development tools is C:/sdk/RedApp_0.5/devtools. The new location for the new version

is C:/sdk/RedApp_0.6/devtools.

To install a new version of the Red App development tools, complete the following steps:

1. Add a new location.

Open Eclipse. Choose Help > Install New Software.

On the Available Software window, click Add.

On the Add Repository dialog, click Local.

Navigate to the folder on your local drive where you extracted the new version of

the Red App Developer Toolkit. Select the devtools folder, and click OK to accept

the location.

2. Remove the old location from Eclipse.

On the Available Software window, click the Available Software Sites link.

On the Available Software Sites window, select only the location of the previous

version of the devtools folder. This is the version that you want to remove.

Click Remove. Confirm the removal of the location, and click OK. Eclipse

removes the pointer to the location, while retaining the files on your local drive.

From the Work With list, select the new location of the devtools folder.

Tip: If you get errors about a duplicate location, go to the Available Software Sites link

again. On the Available Software Sites window, select the new location with the

devtools folder for the upgraded Red App version, and click OK. Do not click the Add

button.

Continue with the installation of the new version.

3. Install the Red App Dev Tools from the new location.

Complete the remaining steps for installation. See Steps 6 – 12 in Installing the Red App

Development Tools.

Chapter 3 - Red App Developer Toolkit Upgrade and Maintenance Upgrading to a New Version of the Development Tools



What to Do Next

Open the Red App Help

Verify installation of upgraded Dev Tools, Red App wizards, and the new version of the

Red App help

Chapter 3 - Red App Developer Toolkit Upgrade and Maintenance Target Platform Maintenance Procedures



Target Platform Maintenance Procedures

This section includes the following optional procedures:

Passing Proxy Settings for Red Workspace in Development Mode

Adding and Removing Plug-ins from a Run Configuration

Removing the Red App Target Platform from Eclipse

Passing Proxy Settings for Red Workspace in Development

Mode

The following procedure shows you how to store proxy settings in your run configuration. These

settings are the same settings that are in the proxy settings window in Sabre Red Workspace.

Eclipse uses these settings every time you launch Red Workspace from Eclipse IDE in

development mode. These settings are not stored or used in CERT or PROD.

1. Open your run configuration in Eclipse IDE.

2. On the Arguments tab, type the arguments with your values in the Program Arguments

field. (See Figure 38.)

Use the following syntax:

–argument value

A list of arguments that Red Apps supports follows:

proxy.host, proxy.port, proxy.user, proxy.password, proxy.domain

38 Proxy Settings for Red Workspace on the Arguments Tab




Adding and Removing Plug-ins from a Run Configuration

You can add or remove plug-ins from a run configuration. Plug-ins that you add to the Red App

target platform from your workspace are available in Sabre Red Workspace, and plug-ins that

you remove from your workspace are not available.

Caution: Because of plug-in dependencies, do not remove plug-ins from the Target

Platform group. Removing a plug-in from the Red App target platform may cause

your plug-ins either to become inoperable or to malfunction.

1. From the Workbench menu bar, choose Run > Run Configurations. Eclipse opens the

Run Configurations window.

2. From the panel on the left, select the run configuration to which you want to add or

remove plug-ins.

3. Click the Plug-ins tab. (See Figure 39.)

39 Workspace and Target Platform Plug-ins in the Run Configurations Window




The tab lists the plug-ins that are in the workspace and in the target platform.

Next, follow the steps either to add a plug-in or to remove a plug-in.

Adding a Plug-in to the Run Configuration

1. From the Workspace group, select the check box that is adjacent to the plug-in.

2. Click Add Required Plug-ins.

3. When you add new plug-ins, be sure to validate that the dependencies are met. Repeat

Steps 22 through 26 in Choosing Plug-ins for Your Run Configuration.

Removing a Plug-in from the Run Configuration

Caution: Because of plug-in dependencies, do not remove plug-ins from the Target

Platform group. Removing a plug-in from the Red App target platform may cause

your plug-ins either to become inoperable or to malfunction.

1. In the Workspace group, remove the selection from the check box that is adjacent to the

plug-in to be removed.

Omit the steps for validating plug-ins.

2. If the Apply button is available, click Apply.

3. Click Run to launch Sabre Red Workspace.

4. To log in, use your Sabre login credentials.




Tips on Toolbar Icons for Run Configurations

This topic provides tips that are related to run configurations. The behavior of the Run and debug

buttons depends on how you defined your launch operation preferences. (For more information

about launch operation preferences, consult the Eclipse documentation on Eclipse's website at

www.eclipse.org.)

Run Icon ( )

Click the down arrow next to the Run icon to either

launch the most recent application or to launch the selected resource.

Debug Icon ( )

Click the down arrow on the Debug icon to either

launch the most recent application in debug mode or to launch the selected

resource.

http://www.eclipse.org/




Removing the Red App Target Platform from Eclipse

This procedure removes the Red App target platform from Eclipse and your local drive

Note: Use Eclipse to remove the target platform before you remove any files from your local

drive. If you do not remove the target platform from Eclipse first, Eclipse displays errors

when you try to access components that used the target platform.

1. On the Eclipse workbench menu bar, choose Window > Preferences.

2. Expand Plug-in Development, and select Target Platform.

3. On the right, select the target platform that you want to delete, and click Remove.

4. Click Apply, and then click OK.

5. On your local drive, delete the targetplatform folder for the version that you

removed in Eclipse.

In the example in the preceding figure, to remove the Red App target platform for version 0.5,

you would delete the targetplatform folder in the RedApp_0.5 path.

Chapter 3 - Red App Developer Toolkit Upgrade and Maintenance Development Tools Maintenance Procedures



Development Tools Maintenance Procedures

This section consists of the following procedures:

Removing the Red App Development Tools from Eclipse

Installing the Dev Tools after Removal

Removing the Red App Development Tools from Eclipse

1. Open Eclipse. Choose Help > About Eclipse SDK.

2. On the About Eclipse SDK dialog, click Installation Details. (See Figure 40.)




40 Installed Red App Dev Tools on the Eclipse Installation Details Window

On the Installed Software tab in the Installation Details window, the Name list should display

Red App Dev Tools.

3. Select Red App Dev Tools.

4. Click the Uninstall button.

5. On the Uninstall Details window, select the name Red App Dev Tools. (See Figure 41.)




41 Uninstall Details Window in Eclipse

6. Click Finish.

7. After Eclipse is done removing the installed software, the Software Updates dialog

prompts you to restart Eclipse. Click Restart Now.

After Eclipse is restarted, Eclipse displays the Workspace launcher dialog.

8. Either choose or confirm the path of your workspace for your target platform.

Verify that the software is no longer installed. Confirm that the Package Explorer and

Installation Details do not include the Red App Development Tools.

9. Open Eclipse. Choose Help > About Eclipse SDK.

10. On the About Eclipse SDK dialog, click Installation Details. (See Figure 42.)




42 Removal of Red App Dev Tools from Eclipse SDK Installation Details

The Red App Dev Tools entry should be removed from the Installed Software tab.




Installing the Red App Development Tools after Removal

If you remove the Red App development tools from Eclipse, you can easily install the tools

again.

1. Open Eclipse. Choose Help > Install New Software. (See Figure 43.)

43 Choosing a Location to Reinstall the Red App Dev Tools

2. On the Available Software screen, do not add a local location again. Choose the location

from the Work With list.

3. Complete the remaining steps for installation. See Steps 7 – 12 in Installing the Red App

Development Tools.




Tip: Alternatively, you can click Available Software Site on the Install Available Software

window. Remove the location that you added previously.

When you are done, verify that Red App Dev Tools software is installed.

4. Choose Help > Install New software.

5. Click the What Is Already Installed link.

Eclipse displays the SDK Installation Details window. If you installed the Red App Dev Tools

successfully, the tools should be listed on this window.


Developer Resources – A

Comprehensive List

Together, the Red App Developer Toolkit, Sabre, and external organizations provide resources for

Red App developers. These resources include development tools, documentation, standards

organizations, support, and training.

Information about how to create the functionality of Red Apps using Sabre technologies is

outside the scope of this document; however, Sabre does provide training and documentation on

using Sabre technologies. With the exception of Sabre GDS training and other courses on

Agency eServices (eServices), you must either purchase licenses or sign a licensing agreement in

order to download documentation for Sabre technologies, such as Sabre Scribe, Qik Developer,

and Sabre Web Services.

Agency eServices

Documentation, training, and other resources are available on Agency eServices at

http://eservices.sabre.com. Access to eServices requires your PROD Sabre ID.

Categories of particular interest are the following:

Sabre GDS, Sabre Red Workspace, graphical view, Qik Developer, Sabre Scribe, and

Format Finder

You can also find your Regional Software Support Desk contact information and the PIN for

your PCC. For this information, see the Red App Developer FAQs.

A


Appendix A - Developer Resources – A Comprehensive List Graphical View



Dev Centre

This secure section on the Sabre Red App Centre (http://www.sabreredappcentre.com) is

dedicated to Red App developers. After you log in on the Red App Centre, the Dev Centre link is

displayed. You can obtain the latest release of the Red App Developer Toolkit, developer

resources, and upload your Red App bundle. If you wish to design a new Red App, you also

submit a new proposal on the Dev Centre.

DevStream - Red App Developer Community

As Sabre Red App Certified Developers, you can use DevStream to participate in a technical

forum and obtain support from the development community. Team members from Sabre's Red

Apps project also monitor and participate in this group. When your application to become a Red

App developer and Red App proposal are approved, you receive login credentials for DevStream.

These credentials are different from your login to Sabre Red Workspace and the Sabre GDS. To

log in to DevStream, visit the following URL:

http://devstream.cubeless.com/account/login

Eclipse

For downloads and online documentation, visit http://www.eclipse.org.

For supported versions of Eclipse Classic IDE, see Required Developer Software, Tools, and

IDs.

Graphical View

If you want to create Red Apps that run in a graphical view editor or listen for graphical view

events, download the graphical view plug-ins from the Dev Centre, and add these plug-ins to

your Red Apps run configuration in Eclipse IDE. For information, see "Graphical View Plug-ins"

and "Adding Graphical View Plug-ins to Your Target Platform."

You can also refer to the following resource on eServices.sabre.com: Sabre Red Workspace in

Graphical View. Choose Products > Product A-Z.


http://devstream.cubeless.com/account/login

http://www.eclipse.org/


Appendix A - Developer Resources – A Comprehensive List PCI



Internationalization or i18n

For information about the definition that is the basis for internationalization of Red Apps and

Sabre Red Workspace, visit the following URL:

http://plone.org/documentation/kb/i18n-for-developers

Java

For downloads and help with Java, visit http:\\java.com.

For the supported versions of the JDK, see Required Developer Software, Tools, and IDs.

JavaDocs

When you set up your Red App target platform, JavaDocs are automatically extracted to the

Javadoc folder and ready to use.

OWASP

All Red Apps must comply with secure design and coding standards. In addition, Red Apps that

handle cardholder or personal data must comply with other industry standards, such as the Open

Web Application Security Project: https://www.owasp.org/index.php

PCI

Red Apps must conform to PCI data security standard PCI DSS 2.0.

To obtain more information about the PCI Security Standards Council and to obtain copies of the

standard, visit https://www.pcisecuritystandards.org/.

http://plone.org/documentation/kb/i18n-for-developers

http://java.com/

https://www.owasp.org/index.php

https://www.pcisecuritystandards.org/

Appendix A - Developer Resources – A Comprehensive List Red App Developer FAQs



Qik Developer

You must either purchase a license or sign a licensing agreement in order to download Sabre Qik

Developer documentation.

Information about using Qik Developer is outside the scope of Red App developer

documentation. If you want to create scripts, refer to the following resource on

eServices.sabre.com: Sabre Qik Developer User Guide.

Choose Products > Product A-Z.

The Red App help has topics on wrapping Qik apps as Red App plug-ins, and adding

communications and other services.

redapp_schema.xsd File

The Red App Developer Toolkit includes the redapp_schema.xsd schema file that you must

use to ensure that your redapp.xml file is well-formed and valid. When you extract the

Developer Toolkit ZIP file, this schema is located in the documentation folder.

Information about creating a redapp.xml file is in the Red App help.

Red App Developer FAQs

For help with login credentials, PINs, working in the CERT environment of the Sabre GDS,

locating your regional software support desk, and other resources and troubleshooting tips of

interest to developers, see the Red App Developer FAQs. These FAQs also include other useful

information about Eclipse IDE, Sabre Red Workspace, and the Developer Toolkit.

The Developer FAQs are in the documentation folder of the Red App Developer Toolkit and

they are also published on the Dev Centre in Developer Resources.


Appendix A - Developer Resources – A Comprehensive List Red App Help




Red App Developer Guidelines describes the general requirements for Red Apps in the areas of

functionality, metadata, trademarks, privacy, legal requirements, and more. Your Red Apps must

comply with the stated requirements. Obtain this document on the Dev Centre. This document is

subject to change periodically, so please check the Dev Centre for updates. (Log in on

http://www.sabreredappcentre.com.)

Red App Development Tools and Red App

Wizards

The Red App development tools consist of wizards that you can use to quickly create plug-in

projects with minimal functionality and a wizard that creates your Red App bundle for you. After

you install the development tools software, review descriptions of the wizards, and then run any

wizard to create the type of plug-in project that you want.

For a description of the Red App wizards and instructions for running them, see the Red App

help. For instructions on installing and upgrading the development tools, see the applicable

sections in Chapters 0 and 3.

Red App Help

The Red App help includes information about the functionality in the Red App Developer Toolkit

that you can use to wrap apps as plug-ins for Sabre Red Workspace, add communications, and

add services to a Red App. The "About" topics and the procedures topics explain important

requirements. Some of these requirements include the approved way to design and implement UI

elements and technologies, classes, methods, extension points, and properties. Many of the

procedures show the easiest way to create plug-ins using Sabre Red Workspace classes.

You are also encouraged to review all Red App standards and policies in the Red App help, to

ensure that your Red App complies with Sabre requirements.

The help system also has procedures to create and secure your Red App bundle, create plug-in

projects, run the sample plug-ins, and execute the Red App wizards.


Appendix A - Developer Resources – A Comprehensive List Sabre Red Styles



After you install and set up a Red App target platform and development tools software, the help

is integrated into Eclipse IDE help.

Red App Sample Plug-ins

The Developer Toolkit has a variety of sample plug-ins, sometimes referred to as reference plug-

ins, which you can import directly into your workspace in Eclipse IDE. Each archive includes all

files and resources that a plug-in needs, such as source code, plugin.xml, MANIFEST.MF, and

more. These plug-ins are comparable to "sample code" because you can use them to learn how to

create plug-ins for Sabre Red Workspace.

For a description of the sample plug-ins and instructions for importing them into your Eclipse

workspace, see the Red App help.

Red App Security Requirements

This information is organized into sections that describe requirements for secure coding

practices, handling of cardholder and personal data, certification testing, and developer skills that

you need to create compliant Red Apps. For this information, see "Developer Resources" on the

Dev Centre. (Log in on www.sabreredappcentre.com.)

Sabre Global Distribution System

For help with the Sabre GDS, refer to the following resources on eServices.sabre.com:

Working in the CERT System. Either choose Training > Quick References > Workflow

Efficiency Tools > Productivity Tools or search for "CERT System".

Signing in to the Sabre System

Agency eServices has more resources for working with the Sabre system.

Sabre Red Styles

The Sabre Red Style Guide provides both general design guidelines for Red Apps and specific

requirements for using specific technologies. Adherence to these guidelines will give your Red

App the look and feel of Sabre Red, and enable your Red App to pass the certification criteria for



Appendix A - Developer Resources – A Comprehensive List Sabre Red Workspace Agency Administration Tools User Guide



Sabre Red styles. Note that meeting the stated criteria does not necessarily guarantee that Sabre

will certify your Red App.

The Sabre Red style sheets are intended for websites that are integrated into Sabre Red

Workspace. This ZIP file includes style sheets, images, JavaScripts, and examples.

These resources are available on the Dev Centre (www.sabreredappcentre.com).

Sabre Red Workspace

You can obtain the following resources about Sabre Red Workspace on eservices.sabre.com. The

following are some of the resources that are of interest to Red App developers:

Agency Administration Tools User Guide

Navigating Sabre Red Workspace Quick Reference. This document describes the

navigation, widgets, tabs, tools, and menus on the Sabre Red Workspace GUI. It also

explains the purpose of each grouping on the launcher bar.

Sabre Red Workspace in Graphical View - Student Guide

Choose Products > Product A-Z > S, and then select Sabre Red Workspace.

Sabre Red Workspace Agency Administration

Tools User Guide

To grant an end-user access to a Red App in the PROD environment of Sabre Red Workspace for

testing, or to enable a Red App for agency users, either your agency administrator or another

person needs access to the Sabre Red Workspace Agency Admin Tool. The User Guide for this

tool explains how to "turn on" or enable a product in Red Workspace. This Guide is available on

Agency eServices on http://eservices.sabre.com.




Appendix A - Developer Resources – A Comprehensive List Sabre Web Services and the Developer Resource Centre



Sabre Scribe

You must either purchase licenses or sign a licensing agreement in order to download Sabre

Scribe documentation.

Information about creating Sabre Scribe scripts is outside the scope of Red App developer

documentation. If you want to create Sabre Scribe scripts, refer to the following resources on

eServices.sabre.com.

Sabre Scribe Scripting Reference Guide

Sabre Scribe Scripting Guide

Choose Products > Product A-Z.

The Red App help has topics on wrapping Sabre Scribe apps as Red App plug-ins, and adding

communications and other services.

Sabre Web Services and the Developer Resource

Centre

Documentation and other artifacts for Sabre Web Services, such as the WSDL and schema

documents for the request and response payloads, are available to subscribers in the Developer

Resource Center (https://drc.sabre.com). Access to this repository requires special login

credentials.

If you have the proper agreements and license to use Sabre Web Services, you receive a login ID

for the Developer Resource Center.

For more information about the requirements for using Sabre Web Services, see your Sabre

account manager.

The Red App help has topics on calling Sabre Web Services from a Red App.


https://drc.sabre.com/

Appendix A - Developer Resources – A Comprehensive List Training on eServices



Training on eServices

Some training courses are available on eServices in the Training section.

Information about how to create the functionality of Red Apps using Sabre technologies, such as

Qik Developer or Sabre Web Services, is outside the scope of the Red App developer

documentation. Sabre does, however, provide some training and documentation without

purchasing a contract or a license.

Use your PROD Sabre ID to log in to Agency eServices (eservices.sabre.com).



getting started with red apps - sabre dev studio started with red apps - release 2.14.3 iii ©2011,...

Documents