Integrating TIBCO Forms with Custom Client Applications

TIBCO forms are a part of projects are deployed to the runtime.

The key top-level components that are involved in making TIBCO Forms accessible from custom client applications are as follows:

• BPM Resources component - This is a component provided by the BPM runtime. This component fulfills two functions:
  • First, it provides access to the Forms Runtime Adapter. This is a JavaScript API that client applications can load in the browser and use to render forms in their applications. See Injecting the Forms Runtime Adapter in the Browser to know about loading the forms runtime adapter.
  • Second, this component provides access to the form resources of BPM applications deployed by the user. Each form that is deployed makes use of a number of resources including: the form definition, CSS, resource bundles for localization, and JavaScript files that provide form actions as well as implementations of Business Object Model objects referenced by the form.
• BPM public web service API - BPM exposes its functionality through comprehensive work management and process management APIs, which are exposed as web services. The main services that are used in the form applications are: WorkPresentationService, PageFlowService, and BusinessServiceService.

  A client application can access the web services using either the BPM public web service API, the Java Service Connector API, or the REST API.

• Client Application - The client application is typically a web application that bundles together the non-Form UI resources that are used by the application, and a controller servlet that acts as the conduit between the browser and the BPM public web service API.

Copyright © Cloud Software Group, Inc. All rights reserved.