Analytic Builder custom block not showing after successful upload

matiur.rahman · May 26, 2023, 9:41am

Product/components used and version/fix level are you on: APAMA Analytics Builder

Detailed explanation of the problem: I have created a custom analytics block following [u]https://tech.forums.softwareag.com/t/analytics-builder-block-sdk/237850[/u], however after successful upload to Calculation block category, I am not able to see the newly uploaded block in the block selection pane. please help

Error messages / full error message screenshot / log file: NA

Is your question related to the free trial, or to a production (customer) instance? production (partner) instance

Have you installed all the latest fixes for the products and systems you are using? Yes

Harald_Meyer · May 28, 2023, 8:44am

Hi,

did you make sure to restart Apama? This is not done by default but there is a --restart parameter:

github.com

SoftwareAG/apama-analytics-builder-block-sdk/blob/rel/10.16.0.x/doc/030-BuildingExtensions.md

# Building a block into an extension

Once a block is written in EPL, it can be packaged into an "extension". Extensions are **.zip** files that can be used to add blocks to the Analytics Builder runtime. Analytics Builder is deployed within Cumulocity IoT, and extensions are stored in the inventory. The extensions are only read when the Apama-ctrl microservice inside Cumulocity IoT is started, so the service must be restarted to make use of a new block. Restarting the microservice will lose state in any running models or custom EPL applications running in that tenant. This SDK provides a command line utility called `analytics_builder` which is available in the root directory of the SDK. This can be used to build an extension or list an extension or manage an extension in a Cumulocity IoT installation. You must navigate out of the model editor to the model manager and back to the editor to expose the new blocks after uploading an extension.

Most of the `analytics_builder` commands use a `--input` argument which specifies the path to a directory. All files except **.log**, **.classpath**, **.dependencies**, **.project**, **.deploy**, **.launch**, **.out**, and **.o** found under that directory will be included, and message files matching **\*-messages.json** or named **messages.json** will be used for the runtime messages.

The `analytics_builder` script is run from an Apama command prompt (on Windows, run **Apama Command Prompt** from the Start Menu group of your Apama installation; on Linux, source the `apama_env` script). **Note:** You must place the script in a directory that does not have any spaces in its full path. 

The `analytics_builder` script takes a two-word command, followed by any arguments required by the command. Available commands are:

* `build extension --output <path to zip file>`

  Build an extension, generating a local **.zip** file. For example:

  ```bash
  analytics_builder build extension --input samples/blocks --output sample-blocks.zip
  ```

* `build extension --cumulocity_url <url> --username <user> --password <password> --name sample-blocks`

This file has been truncated. show original

If you did restart, can you check the apama-ctrl microservice log for any errors after startup?

matiur.rahman · May 28, 2023, 8:44am

There was a mistake in the $blockCategory as there is difference in the Category Shown on the Analytic Builder page and actual mapping as
The following table lists the allowed values for @$blockCategory and the category names that are shown in the model editor’s palette:

Value	Name in the palette
Input	Input
Output	Output
Logic	Logic
Calculations	Calculation
Aggregates	Aggregate
Flow Manipulation	Flow Manipulation
Utilities	Utility

system · November 24, 2023, 8:44am

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.