Skip Navigation

About Website Integration Using a Custom Implementation

If your website does any of the following, provide your own implementation of an editor:

  • Listens for browser events

  • Dynamically determines a URL at runtime

  • Uses complex business logic to handle the life cycle of the browser editor

  • Customizes the browser editor itself, for example, the editor displays more than a browser, such as a static image or a change in the title

With a custom implementation, you write your own editor wrapper and Java code, and use your own classes. You also write your own event listener and define the behavior of your Red App, including focus behavior.

When a website is integrated in a plug-in, the website is a standalone tool with the following characteristics:

  • A website is embedded in an editor (or tab).

  • A website can be based on HTML.

        On the server side, a website can be based on Java technologies, for example, servlets or JSP. A website can also be based on other technologies, such as Microsoft .NET Framework or PHP. From the perspective of Red Apps, all of these technologies are HTML.

        Websites with an applet cannot be integrated in Sabre Red 360. Instead, wrap applets as Swing apps.

  • End-users select a menu entry to launch a website in a dedicated tab.

  • A website can interact with other Red Apps in Sabre Red 360. Red Apps can use any of the SRWRuntime communications services by requesting authorization to use communications services in redapp.xml and authenticating in the Java code.

    • A website extends the capabilities that are available to end-users of Sabre Red 360.

Agency eServices is an example of a website that is integrated as a plug-in. End-users can launch an editor that navigates immediately to and renders the website in a tab within the workspace.

If you want to use default browser editor or view classes that are available in the Sabre Red 360 Software Development Kit, see About Website Integration Using Default Implementations.