You can set up your Kablink Teaming installation so that remote applications—which often run on other server machines—provide HTML for segments of Teaming pages. Using this customization method gives you several advantages:
Provides more control over the format and content than using Teaming designers or JSP files.
Allows customization designers to work primarily within a familiar development environment (for example, using PHP or Perl) instead of requiring them to do most of their work within the Teaming environment.
Protects the customization from the effects of any future updates to the Teaming source code.
Eliminates the risk of implementing a customization that destabilizing the base product.
This topic includes the following sections:
NOTE:This chapter presents a “hello world” example application that you can implement quickly on your Kablink Teaming server, using the Eclipse build environment and Tomcat. The registration and application sections assume use of this example application. For more information about the example application, see Section 3.3, Creating a Remote Application.