Adapter Administration

This content describes the configuration and management of Adapters. It is intended for database administrators and application developers. Adapters enable clients to manage data from virtually any data source, and on any operating system, through the use of SQL statements. This content is intended for all users who have configured any of the supported adapters for their use.

Key Features

The following Key Features are introduced in Release 8.2:

• Adapter for Apache Drill. Apache Drill is a query engine for data managed by Hadoop in HDFS or Mapr-FS, a variety of NoSQL databases including HBase and MapR-DB, MongoDB, and other data sources. Drill can use Hive metadata or derive metadata from self-describing data files.
• Adapter for Apache Phoenix to Access HBase. Apache Phoenix provides SQL read/write access to Apache HBase (and MapR-DB) a NoSQL database distributed with Hadoop.
• Adapter for EXASol ODBC. The Adapter for EXASol ODBC provides read/write access to data stored in an EXASOL in-memory database is available on Windows and RH Linux. The adapter uses the EXASolution ODBC driver API.
• Adapter for Google BigQuery. The Adapter for Google BigQuery is used to load data into the Google BigQuery environment and report against the information residing in the Google BigQuery environment.
• Adapter for MariaDB. The Adapter for MariaDB provides read/write access to data stored in the open source MariaDB database using the MariaDB Connector/J.
• Adapter for Rstat Predictive Analytics. The Adapter for RStat Predictive Analytics allows RStat models to be deployed from the Reporting Server Console, in addition to model deployment from App Studio. A Master File and Access File are also created for the deployed model, enabling access through a Master File Join or the function DB_LOOKUP().
• Adapter for Esri ArcGIS. The Adapter for Esri ArcGIS provides access to the Esri cloud for the purposes of drawing maps and demographic layers. It also returns geographic data from the following WebFOCUS functions that retrieve geometry data and geocode addresses:
  • GIS_DISTANCE, which calculates the distance between two geometry points.
  • GIS_DRIVE_ROUTE, which returns the driving route between two geometry points.
  • GIS_GEOCODE_ADDR, which returns the geometry point for a full address.
  • GIS_GEOCODE_ADDR_CITY, which returns the geometry point for an address, city, and state.
  • GIS_GEOCODE_ADDR_POSTAL, which returns the geometry point for an address and postal code.
  • GIS_GEOMETRY, which builds/converts a JSON geometry object given a geometry type, WKID (Well-Known ID) spatial reference and a initial JSON geometry.
  • GIS_IN_POLYGON, which given a geometry point and a polygon definition, returns the value 1 (TRUE) if the point is in the polygon or 0 (FALSE) if is not.
  • GIS_LINE, which given two geometry points or lines, builds a JSON line defining a geometry line.
  • GIS_POINT, which given a WKID (Well-Known ID) spatial reference, longitude, and latitude, returns a JSON point defining a geometry object.
  • GIS_SERVICE_AREA, which calculates the geometry area with access boundaries within the given time or distance from the provided geometry point.
  • GIS_SERV_AREA_XY, which calculates the geometry area with access.