This article shows how to install, configure, and run JDBCMK in meshIQ 12.1.

JDBCMK is used to create, upgrade, and manage database objects across meshIQ platform components, including Core, Manage, Scheduler, Data Service, and Track.

What Changed in 12.1

From core, jdbcmk moved to a separate package. Install it on one of the servers that can access the required databases. If Pinot objects are required, ensure access to the Pinot REST API and Kafka brokers.

From 12.1, jdbcmk supports all products:

Core (Permits)

Scripts for permits tables moved from WGS (11.3 and earlier):

• {meshiq_platform}/sql-scripts/nsqjdbcmk/permitsv3_*.sql →
  {meshiq_platform}/sql-scripts/core/core-permits-sqls/core-permits_*.sql

Manage (WGS and Manage)

Renamed and moved SQL scripts compared to 11.3 and lower releases:

• WGS:
  • {meshiq_platform}/sql-scripts/nsqjdbcmk/apwmq_*.sql →
    {meshiq_platform}/sql-scripts/manage/wgs-sqls/wgs_*.sql
• Manage:
  • {meshiq_platform}/sql-scripts/nsqjdbcmk/permitsv3_*.sql →
    {meshiq_platform}/sql-scripts/manage/manage-sqls/manage_*.sql

Scheduler (Core and Quartz) – Newly Added

• Core:
  {meshiq_platform}/sql-scripts/scheduler/ap-sched-sqls/ap_sched_*.sql
• Quartz:
  {meshiq_platform}/sql-scripts/scheduler/quartz-sqls/quartz_*.sql

Data Service – Newly Added

• DB:
  {meshiq_platform}/sql-scripts/ds/ds-sqls/ds_*.sql
• Kafka topics for Pinot:
  {meshiq_platform}/sql-scripts/ds/ds-pinot/kafka_topics.properties
• Pinot:
  {meshiq_platform}/sql-scripts/ds/ds-pinot/pinot_tables.properties
  • schemas/, tableconfigs/

Track – Newly Added

• {meshiq_platform}/sql-scripts/track/track-sqls/track_*.sql

Installation

While jdbcmk moved from core installation, install it manually using Package Manager (pkgman):

• DBUtils-Plugin (db-utils-12.1.pkg)
  Main DB utils package. Contains required libraries, jdbcmk executables, product scripts, and sample property files.
• DBUtilsRP-Plugin (db-utils-rp-12.1.pkg)
  Resource package containing properties files. Install once to avoid overriding custom configurations.

Run JDBCMK

Commands

• Windows:

{meshiq_platform}/sql-scripts/jdbcmk.bat

• Unix:

{meshiq_platform}/sql-scripts/jdbcmk.sh

Interactive Mode

CLI Mode

Common Options

• ? or -? – Usage screen
• 0 or -quit – Exit application
• -t – Enable tracing
• -d [ds] – Set SQL delimiter (default #)
• -f – Force execution
• -u – Run upgrade
• -c [cpf] – Custom property file
• -qp [qp] – Quartz table prefix
• -p [p] – Encrypt password

Core Commands Execution

Configuration

Before executing the commands, create or modify the following file:

{meshiq_platform}/sql-scripts/core/core.properties

The following table lists the required properties. For additional optional properties, refer to the corresponding .properties file.

Interactive Menu

CLI Mapping

Manage / WGS Commands Execution

Configuration

Before executing the commands, create or modify the following file:

{meshiq_platform}/sql-scripts/manage/manage.properties

The following table lists the required properties. For additional optional properties, refer to the corresponding .properties file.

Interactive Menu

CLI Mapping

Scheduler Commands Execution

Configuration

Before executing the commands, create or modify the following file:

{meshiq_platform}/sql-scripts/scheduler/scheduler.properties

The following table lists the required properties. For additional optional properties, refer to the corresponding .properties file.

Interactive Menu

CLI Mapping

Data Service Commands Execution

Configuration

Before executing the commands, create or modify the following file:

{meshiq_platform}/sql-scripts/ds/ds.properties

The following table lists the required properties. For additional optional properties, refer to the corresponding .properties file.

Interactive Menu

CLI Mapping

Customize Kafka Topics Required for Pinot Configuration

Before executing the commands, create or modify the following file. You can copy it from the sample file:

{meshiq_platform}/sql-scripts/ds/kafka_topics_customize.properties

You can define default configuration for all topics:

To define configuration for a specific topic, use the prefix kafka.topic.{topic_name}.

For example, for pinot-alert-topic:

Before executing the commands, create or modify the following file:

{meshiq_platform}/sql-scripts/ds/ds.properties

Track Commands Execution

Configuration

Before executing the commands, create or modify the following file:

{meshiq_platform}/sql-scripts/track/track.properties

The following table lists the required properties. For additional optional properties, refer to the corresponding .properties file.

Interactive Menu

CLI Mapping

Run SQL Script

Interactive Menu

CLI Mapping