Like what you see? Have a play with our trial version.

Error rendering macro 'rw-search'

null

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Data can be retrieved from any source via file access, API access, or data that is embedded in the connector itself. Most implementations are expected to make use of web service APIs, third-party web applications, and SAAS providers. 

 

 

Implementation Overview

Implementation is done by extending Yellowfin’s third-party java interface. 

...

A metadata class is also required. This will allow for a connection wizard to be defined, and prompt the end user for the required parameters to make a connection to the third-party source. This is an implementation of a JDBCMetaData class. 

 

IDE Integration / Classpath

The definitions for the required Yellowfin classes are available in the following libraries from a standard Yellowfin installation. These are located in the /appserver/webapps/ROOT/WEB-INF/lib/ directory of the installation. 

  •  i4-core.jar 
  •  i4-mi.jar 

 

These are dependencies that are required to compile a connector plugin for Yellowfin. Referencing these libraries in an IDE will also allow for code-completion and function lookups while editing. 

 

General Workflow

Here is an outline for creating a custom connector:

...