softwareag / apama-analytics-builder-block-sdk Goto Github PK

Returns a 404.

Could you pls. add a list of the defined categories in the documentation, e.g.

• @$blockCategory Input
• @$blockCategory Output
• @$blockCategory Logic
• @$blockCategory Calculations
• @$blockCategory Aggregates
• @$blockCategory Flow Manipulation
• @$blockCategory Utilities

Currently only these categories can be used.

AnalyticsBuilderBaseTest has a function timestamp() to set the current correlator time. Using this to set the initial time does not work well if model execution time should be an actual date. Calling self.timestamp(1693388803.554) (which will create a pseudo timestamp event &TIME) will take a very long time as the model needs to process through all the time since time 0.

Apama supports explicitly setting the time with an event like this:
f'&SETTIME({1693388803.000})'

It would be good if the test framework either had a separate function to create a $SETTIME event or if startAnalyticsBuilderCorrelator() had an optional parameter to set the initial time.

As testing blocks requires additional configuration and the use of a different base class, it would be good if Pysys had a template for such a test project.

It would be really great to be able to upload onw blocks without the need to install apama locally. Would it be possible to just zip the project and use curl to push it to the tenant

Including them is unnecessary and can lead to build issues. Can be fixed by adding ".git" and ".github" to UNSUPPORTED_FILE_TYPES.

In some cases, it can make sense to populate the state already during the $init or $validation actions if the state can be derived for the parameters and connected inputs and / or will not change afterwards (e.g. converting a human-readable parameter into a format that can be better used in the EPL implementation).

At the moment, one would have to implement this in $process and check if it has already been populated to avoid doing it every time.

This file contains a number of utility functionality (like formatting timestamps):
https://documentation.softwareag.com/onlinehelp/Rohan/Apama/v10-5/apama10-5/ApamaDoc/com/apama/cumulocity/Util.html

as a workaround you can override preInjectBlock but it would be nice if the test framework did this already:

corr.injectEPL(['TimeFormatEvents.mon'], filedir=self.project.APAMA_HOME + "/monitors") corr.injectEPL(['Cumulocity_Utils.mon'], filedir=self.project.APAMA_HOME + "/monitors/cumulocity")

the Apama Core installation:
https://techcommunity.softwareag.com/en_en/apama-downloads.html

does not include a JRE and the SDK cannot use a Java installation outside of the Apama. The SDK should use the OS JAVA_HOME as a fallback.