Uploading Files
Uploading files
The uploader guides you through the process of uploading a BIRT design (.rptdesign) or BIRT document (.rptdocument) to BIRT iHub. If you did not provide the location of your JDBC drivers when you installed F-Type, you will be prompted to exit the uploader and copy them to your BIRT iHub installation. You must then restart iHub. If your report design requires additional resources, you may upload them to BIRT iHub without exiting the uploader. Once you have uploaded all the required files, you can explore BIRT iHub's features, including interactive viewing, sharing, scheduling, exporting to Excel, and integration into web applications.
To bypass the uploader and go directly to the BIRT iHub Visualization Platform, click Exit to BIRT iHub.
Detecting and uploading report resource files
The uploader automatically detects the supporting files required by a report design and prompts you to upload these files to the Encyclopedia volume or to the file system on which BIRT iHub is installed.
The uploader detects the following files automatically. You then upload these files to the volume without exiting the uploader:
1 .Common resources
Libraries
Properties files
JavaScript files
.JAR files
CSS files
Image files used in style.background, reportitem.background, and image items
Report designs that are the targets of a hyperlink
2 .Resources used in custom plug-ins, for example images and hyperlink targets defined in charts
3 .Resources used in data sources:
Excel file in Excel data source
CSV file in flat file data source
XML, schema, and WSDL files in web services data source
XML and schema files in XML data source
Database drivers and custom plug-ins must be uploaded to the file system on the computer on which BIRT iHub is installed. The uploader prompts you to exit and copy the following files to the file system manually:
JDBC drivers
ODA plug-ins
Custom plug-ins
Before uploading an ODA plug-in, you must do the following:
Remove the dependencies on org.eclipse.ui and org.eclipse.core.runtime.
Remove the class Activator and change the activation setting.
If you do not take these steps, the report that uses the ODA plug-in will not run on BIRT iHub.
The uploader does not prompt you to upload the following files:
Resources in scripts and embedded designs
Resources in Java classpath
Resources in local absolute paths
Disabling user experience tracking
As you work with F-Type, Actuate tracks the following activities:
Product activation
Login to BIRT iHub Visualization Platform
Running a transient design
Running a persistent design
Creating a schedule
Launching the Viewer
Launching the Interactive Viewer
Viewing and downloading documents in any supported format: PDF, Excel, Word, PowerPoint
Launching, creating, editing, and saving a dashboard
Launching, creating, editing, and saving a design in Report Studio
Launching the Administration Console
Disabling user experience tracking
Enabling user experience tracking
If you would like to disable user experience tracking, you must add the following parameter definition in %ihub_home%\web\iportal\WEB-INF\web.xml:
<context-param>
<param-name>DISABLE_PING</param-name>
<param-value>true</param-value>
</context-param>
Then restart the Actuate iHub3 service.