 |
About The Programming
Interfaces |
|
|
Actuate offers three interfaces
|
|
About API features |
|
|
The Actuate ActiveX controls, Requester API, and
Report server API each provide different features and levels of access to
Actuate reports
|
|
Choosing which API to use |
The
following topics are to be considered when choosing the appropriate API.
|
|
|
|
When to use Actuate ActiveX
Controls |
|
Actuate ActiveX controls are the easiest to
implement when you want to embed. Actuate reporting into your Windows. It is the optimal choice if you
are developing
an application with these requirements:
- Environment-
Windows based application, either new or existing
-
Feature
set-view, execute, and print reports with the Desktop ActiveX control,
view and print reports with the Viewer ActiveX Control
-
Development
resources
|
| Learn
Actuate |
| We have come up |
| with two training sections for
Actuate. |
 |
| Actuate professional
& programming with Actuate. |
|
|
|
|
|
When to use Requester API |
|
It is a choice for the client to run his applications
on different platforms and operating systems. Often client applications
use the Actuate Viewer in connection with the Requester API for viewing
and navigating reports. The capability of the Requester API to access the
attributes and values of report parameters is an important
feature. |
|
|
When to use Report Server API
|
|
It is a powerful interface for accessing the Report
Server functionality. With the Report Server API, we can integrate the
Actuate reporting features into your existing applications and automate
high volume or routine reporting tasks. |
|
|
Accessing the API
|
|
The Report Server API is written in C++. It includes library, header and executable files shipped with
actuate. While running the report the application accesses the API through a DLL interface.
|
|
|
Compiler requirements
|
|
To build an application using the Report Server API
we needed one of the following compilers:
|
|
|
Report Server API Architecture |
|
The Report Server is actually a number of servers,
such as the connection server, request server, administration server,
persistent object server and operation servers. To work with the servers
we need an awareness of the properties, requests, schedules, events and
messages. The developers need a good understanding of the class hierarchy
because the Report server interface is object oriented.
|
|
|
