Console commandsSkip to main contentToggle navigationSelect versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveToggle navigationStriim Cloud 4.2.0 Select versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveprintToggle navigationStriim Cloud 4.2.0 Console commandsPrevNextConsole commandsUsing the console in the web UIAt the bottom of the Console page, enter a command, then click Execute.The command's output will appear above.If a command requires a file as an argument, upload it as described in Manage Striim - Files. Specify the path as UploadedFiles/<user name>/<file name>, for example, UploadedFiles/MyUserName/MyApp.tql.In this release, SELECT commands (ad-hoc queries) are not supported in the web console.Using the console in a terminal or command promptIf Striim is installed in /opt, the command to run the console is:/opt/Striim/bin/console.sh -c <cluster name>In Windows, if Striim is installed in c:\striim, the command to run the console is:\striim\bin\console -c <cluster name>NoteFor the Windows command prompt, set the font to Consola, Lucida Console, or another monospace font that has box-drawing characters.The following switches may be used:-c <cluster name>: the name of the cluster to connect to (if omitted, will default to the current user name)-f <path><file name>.tql: a TQL file containing commands to run when console starts (if not specified from root, path is relative to the Striim program directory)-H false: if HTTPS has been disabled, use this to connect to Striim using HTTP-i <IP address>: if the system has multiple IP addresses, specify the one for the console to use-p <password>: the password to use to log in (if omitted, you will be prompted after the console connects)-S <IP address>: the IP address of the Striim server (the value of ServerNodeAddress in startUp.properties; required if HTTP has been disabled)-t <port>: specify the HTTP port if not 9080-T <port>: specify the HTTPS port if not 9081-u <user name>: the user to log in as (if omitted, you will be prompted after the console connects)The following commands are intended primarily for use at the command line rather than in .tql application files. DDL and component reference and ad-hoc queries may also be entered at the command line.@@<path>/<file name>.tql [passphrase=<passphrase>];Run the commands in the specified TQL file (typically all the commands required to create an application). If not specified from root, path is relative to the Striim program directory. If the TQL was exported with a passphrase (see Exporting applications and dashboards), specify it with the passphrase option. Note that if the file contains DDL defining an application, the name will be defined by the CREATE APPLICATION statement, not the TQL file name.Exporting applications and dashboardsDEPLOYDeploys an application in the Created state. See Managing deployment groups.DESCRIBEDESCRIBE <namespace>.<object name>;Returns all properties of the specified component, application, or flow. DESCRIBE CLUSTER; returns the cluster name, information about the metadata repository, and license details. EXPORTEXPORT APPLICATION { ALL | <namespace>.<application name>,... } [TO "<path>" [passphrase="<passphrase>"]];Exports applications as TQL files. Specify either ALL to export all applications or a list of applications separated by commas. See Encrypted passwords for discussion of passphrases. If you do not specify a path, files will be saved to the striim directory.Except for applications in the current namespace when the command is run, component names in the exported TQL will include their namespaces. Remove those before importing the TQL into a different namespace.EXPORT <stream name>;See Reading a Kafka stream with an external Kafka consumer.HISTORYHISTORY;Lists all commands previously entered in the current console session.LISTLIST { <component type> };Returns a list of all objects of the specified type.LIST LIBRARIES;Lists currently loaded open processors (see Loading and unloading open processors).LOAD / UNLOADSee Loading standalone sources, caches, and WActionStores, or Creating an open processor component.METERUsage-based metering continuously tracks resource consumption by the apps in a Striim cluster. You can use this information to track your usage breakdowns at an app and adapter level. With Striim Cloud, you can also view usage rate information that can help you track how you will be billed for usage charges.Show billing and metering cycle informationMETER CYCLE -billing;Lists the billing cycles.METER CYCLE -metering <billingId>;Lists the metering cycles for the billing cycle billingId.Show usage informationMETER USAGE -summary;Lists the usage summaries for all billing cycles.METER USAGE -byapp <billingId>;Lists the usage and consumption for all applications in the billing cycle billingId.METER USAGE -bycycle -app <appId | appName>;Lists the usage and consumption for the application appId/appName in all billing cyclesMETER USAGE -current;Lists the usage and consumption for all adapters in the current billing cycle.METER USAGE -current -app <appId | appName>;List the usage and consumptions for all adapters in the application appId/appName and the current billing cycle.METER USAGE -itemized <billingId>;List the usage and consumptions for all adapters in the billing cycle billingId.METER USAGE -itemized <billingId> -app <appId | appName>;List the usage and consumptions for all adapters in the application appId/appName and the billing cycle billingIdbillingId.Show consumption informationMETER CONSUMPTION -aggregated <billingId> <itemId>;List the consumptions for all components in the billing cycle billingId and the adapter itemId.METER CONSUMPTION -aggregated <billingId> <itemId> -app <appId | appName>;List the consumptions for all components in the billing cycle billingId, the adapter itemId and the application appId/appName.METER CONSUMPTION -drilled <billingId> -component <componentId | componentName>;List the consumptions for the component componentId/componentName in the billing cycle billingId drilled down to the metering cycles.Show usage rate informationThe METER RATE commands apply to Striim Cloud with its usage-based billing. Rates are not applicable to Striim Platform. Usage has two parts:Consumption usage: Consumptions from the flow components are converted to usage based on a predetermined formula for their consumption types.  Feature usage: Usage for each subscribed add-on feature is calculated by applying an acceleration factor on top of the total consumption-based usage.METER RATE -adapter;List the usage rates and acceleration factors for different adapter tiers.METER RATE -storage;List the usage rates for storage consumptions.METER RATE -feature;List the usage accelerator factors for the features.METER RATE -item <itemId>;List the metering rate and unit for the usage item itemId.Show applications, adapters and componentsMETER LIST -app;Lists the metered applications.METER LIST -adapter;Lists all adapters.METER LIST -adapter -used;List the used and metered adapters.METER LIST -component;List the metered components, active and dropped.METER LIST -component -active;List the metered components, active only.Show configurationMETER CONFIG -kafka;Describes the configuration of the internal Kafka cluster used by persistent streams.MONITORSee Using the MON command.PREVIEWPREVIEW <namespace>.<CQ name> { INPUT | OUTPUT | INPUTOUTPUT } [LIMIT <maximum number of events>]Returns current input and/or output events for the specified CQ. If you do not specify value for LIMIT, the command will return a maximum of 1000 input events and/or 1000 output events.NoteThe CQ must be running before you execute the PREVIEW command.Each event in the command's output includes:Source: name of the component that emitted the event (either one of the components in the FROM clause of the CQ or the CQ itself)IO: I for input or O for outputAction: added or removedServer: name of the server executing the specified CQData: the event payloadFor example, the command PREVIEW Samples.PosData5Minutes inputoutput limit 1; will return something similar to:Processing - preview samples.CsvToPosData inputoutput limit 1
Source:"Samples.CsvStream",IO:"I",Action:"added",Server:"S192_168_7_91",
Data:"[[COMPANY 366761, 9XGDirhiN2UPnJ9w5GqmISM2QXe1Coav3Fq, 0558659360821268472, 6,
20130312174714, 0615, USD, 8.42, 8641415475152637, 61064, Polo],
{FileOffset=0, RecordEnd=49798966, RecordOffset=49798836, FileName=posdata.csv,
RecordStatus=VALID_RECORD}]"
Source:"Samples.CsvToPosData",IO:"O",Action:"added",Server:"S192_168_7_91",
Data:"[9XGDirhiN2UPnJ9w5GqmISM2QXe1Coav3Fq, 2013-03-12T17:47:14.000-07:00, 17, 8.42, 61064];"
QUIESCEQUIESCE <namespace>.<application name> [CASCADE];Pauses all sources.Flushes out all data in process. This can result in partial batches of events, such as a 100-event window emitting a batch of only 20 events, or a five-minute window emitting a one-minute batch, which may result in functions such as COUNT and SUM returning anomalous results outside of the normal range. Pattern matching CQs may also return anomalous results.After all data is flushed, records all information required for recovery, if it is enabled (see Recovering applications).Stops the application. Its status will be QUIESCED.If you specify the CASCADE option, any downstream applications that consume events from the specified application via persisted streams will also be quiesced.NoteIf when you start an application for the first time it reads from a persisted stream that was previously quiesced, it will start reading the stream after the point at which it was most recently quiesced. Similarly, if an application was offline when an upstream application was quiesced, when it gets to the quiesce command in the persisted stream it will quiesce.The primary uses for QUIESCE are to flush out remaining data at the end of a data set and to create a recovery checkpoint with no data in process prior to using ALTER on an application with recovery enabled (see ALTER and RECOMPILE).Due to long-running open transactions, OracleReader may be unable to pause within 30 seconds, in which case the application and all its sources will resume as if the QUIESCE command had not been issued.To support QUIESCE with OracleReader, see Creating the QUIESCEMARKER table for Oracle Reader.REPORTSeee Using the REPORT START / STOP command.RESUMEWhen an application is in the TERMINATED state and the condition that caused it to terminate has been corrected, RESUME <application name>; will attempt to resume operation from the point where the application terminated. Data may be lost if recovery was not enabled (see Recovering applications).SELECTQueries a WActionStore. See Browsing data with ad-hoc queries.SHOWShow current stream outputSHOW <namespace>.<stream name>;Returns the output of a stream. Press Ctrl-D to end.Show open transactions in Oracle ReaderWith OracleReader, SHOW can also be used for Viewing open transactions.Show checkpoint historySee Recovering applications.Recovering applicationsShow OJet status and memory usageSee Runtime considerations when using OJet.STARTSTART <namespace>.<application name>;Starts the specified application.STATUSSTATUS <server name>;Lists all applications deployed or running on the specified server.STATUS <namespace>.<application name>;Returns the status of the specified application. See Application states.STOPSTOP <namespace>.<application name>;Stops a running application and, if recovery is enabled, writes recovery checkpoints. If recovery is enabled and  the application was not dropped after it was stopped, recoverable sources will restart from the point immediately after the last written events (see Recovering applications). If recovery is not enabled, any data currently being processed will be lost.The Stop command is also available when an application is in the Starting state. This can be useful when an application is stuck in the Starting state and you want to stop and debug it rather than waiting for it to time out and revert to the Deployed state.UNDEPLOYUndeploys a deployed application. See Managing deployment groups.The Undeploy command is also available when an application is in the Deploying state. This can be useful when an application is stuck in the Deploying state and you want to stop and debug it rather than waiting for it to time out and revert to the Created state.UNLOADSee Loading standalone sources, caches, and WActionStores, or Creating an open processor component.USAGEUSAGE [<namespace>.<application name>];Lists sources and how much total data each has acquired. If you do not specify an application name, USAGE; lists all sources for all applications.In this section: Console commandsUsing the console in the web UIUsing the console in a terminal or command prompt@DEPLOYDESCRIBEEXPORTHISTORYLISTLOAD / UNLOADMETERShow billing and metering cycle informationShow usage informationShow consumption informationShow usage rate informationShow applications, adapters and componentsShow configurationMONITORPREVIEWQUIESCEREPORTRESUMESELECTSHOWSTARTSTATUSSTOPUNDEPLOYUNLOADUSAGESearch resultsNo results foundWould you like to provide feedback? Just click here to suggest edits.PrevNextSee how streaming data integration can work for
						you.Schedule a
						DemoDownload © 2023 Striim, Inc. All rights reserved. Last modified: 2023-05-31

Console commands


Web UI GuideSkip to main contentToggle navigationSelect versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveToggle navigationStriim Cloud 4.2.0 Select versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveprintToggle navigationStriim Cloud 4.2.0 Web UI GuidePrevNextWeb UI GuideWeb UI OverviewThe left portion of the main menu at the upper left corner of the Striim web UI allows you to navigate to the UI's various pages. An administrator will see the seven choices shown above. Users with limited permissions may see fewer choices.The right portion of the main menu lets you view the documentation in HTML or PDF format (see www.striim.com/docs for the latest update), view alerts, see information about Striim or your user account, contact support, or log out.When you have alerts, the Alert (bell) icon will display a number. Click the icon to see a list of the alert. The alerts above are from the PosApp sample application.At the bottom of the web UI is the Message Log.Home pageStriim's home page appears when you log in. This page gives you a summary of system status, alerts for any potential problems, and quick access to some of the resources you most recently accessed. What you see on this page will depend on your roles; click Customize Homepage to change it.Alert Manager pageSee Sending alerts about servers and applications.App Wizard pageSee Creating an application using a template.Apps pageAll currently created, deployed, and running applications for which you have read permission appear on the Apps page. The search box at the top allows you to find apps by name, status, and/or namespace.Click Create New to create an app from scratch or by importing TQL. For more information on creating apps, see Fundamentals of TQL programming, Creating apps using templates, Creating and modifying apps using the Flow Designer, and Creating or modifying apps using Source Preview.NoteWhen importing a TQL file, the web browser process must have all necessary privileges on the file. For example, in a Linux environment, if the files are owned by root, and you are logged in as another user, you may be able to select the files for import but they will not actually be created.The entry for each application shows its current state (see Application states), some performance data, and icons for its sources and targets. States are color-coded: gray for Created, blue for Deployed, Stopped, or Quiesced, green for Running, red for Terminated or Halt, and so on. The namespace is displayed below the name of the application.Application statesUse the ... menu to deploy, start, monitor, stop, undeploy, or drop an application, export it to a TQL file, move it to a group, or view it in the Flow Designer (see Modifying an application using the Flow Designer). The choices on the menu vary depending on the application's status: for example, Start appears only when the status is Stopped, and Drop appears only when the status is Created. Depending on your permissions, some menu choices may not appear.If an application halts or terminates due to an error you can fix without undeploying it, such as by restarting an external source that has gone down, you may use the Resume command to continue after resolving the problem.Optionally, personalize your Apps Page by grouping applications. To create a group, select Move to a group from the  ... menu, enter a name for the group, and click Save. Alternatively, select multiple apps to act on at once using their checkboxes. Once you have created a group, use the same command to add additional applications. Click the up and down arrows to reorder groups, the pencil to rename or add a description, ∨ to collapse a group, > to expand, and ⓧ to delete a group (the apps will not be deleted).To export an application to a TQL file, select ... > Export. Alternatively, select multiple apps using their checkboxes, then click Export (on the right, just below the search box.Console pageSee Using the console in the web UI.Create App pageSee Creating an app using the Flow Designer, Creating apps using templates, or Creating apps by importing TQL.Creating apps using templatesDashboards pageAll currently loaded dashboards appear on the Dashboards page. Click a dashboard tile to view it. (If the associated application is not running, you will see errors.)To import or create a new dashboard, click Add Dashboard. Use the ... menu to rename, edit, or delete a dashboard (depending on your permissions, some menu choices may not appear). The Export command appears at the top right when you edit the dashboard.For more information, see Viewing dashboards and Dashboard Guide.Flow Designer pageSee Creating and modifying apps using the Flow Designer.Manage Striim - FilesThis page lets you upload and download files to and from Striim.To upload a fileSelect Manage Striim > Files > Upload FIle.Select the directory to which you want to upload the file.Drag and drop the file onto the dialog (or click Browse, navigate to the file, and double-click it), then click Done.To download a previously uploaded fileSelect Manage Striim > Files.Fine the file and click its Download File link.Manage Striim - Metadata ManagerThe Metadata Manager lets you browse all existing components you have permission to view. You may filter the list by namespace, application, and type. You may also view the Metadata Manager while in the Flow Designer, which can be useful when you want to copy settings from a component in another application or flow.Manage Striim - Property SetsThis page lets you create the property sets required for Sending alerts from applications using the web UI.Manage Striim - Property VariablesThis page lets you create property variables using the web UI. See CREATE PROPERTYVARIABLE for more information.Manage Striim - VaultsThis page lets you manage vaults using the web UI. See Using vaults for more information.Using vaultsMessage LogThe Message Log appears at the bottom of all web UI pages. Any errors in your applications or dashboards will appear here, along with notifications of various common events, including, among others:systemall system apps are running (after server start)adaptersevents:first event received (after application start)millionth event received10-millionth event receivedconnections:initial connection establishedretrying connectionreconnection successfulconnection failed, application haltedDatabase Reader: initial load completedtargets when schema evolution is enabled (see Handling schema evolution)DDL operation propagatedDDL operation ignoredunsupported DDL operation, application quiesced or haltedCDC readersall metadata has been fetchedwhen schema evolution is enabled (see Handling schema evolution)DDL operation capturedDDL operation ignoredunsupported DDL operation, application quiesced or haltedOracle Readerout-of-order SCN encounteredtotal open transactions has exceeded 10,000transaction buffer has started spillover to diskMetadata Manager pageSee Manage Striim - Metadata Manager.Monitor pageSee Monitoring using the web UI.My FilesSee Manage Striim - Files.Source Preview pageThe Source Preview page allows you to create sources and caches by browsing available data files of certain types. See Creating sources and caches using Source Preview.Users pageAdministrators (members of the Global.admin group) can access the Users page to perform the tasks described in Managing users, permissions, and roles.In this section: Web UI GuideWeb UI OverviewHome pageAlert Manager pageApp Wizard pageApps pageConsole pageCreate App pageDashboards pageFlow Designer pageManage Striim - FilesManage Striim - Metadata ManagerManage Striim - Property SetsManage Striim - Property VariablesManage Striim - VaultsMessage LogMetadata Manager pageMonitor pageMy FilesSource Preview pageUsers pageSearch resultsNo results foundWould you like to provide feedback? Just click here to suggest edits.PrevNextSee how streaming data integration can work for
						you.Schedule a
						DemoDownload © 2023 Striim, Inc. All rights reserved. Last modified: 2023-03-01

Web UI Guide


Dashboard GuideSkip to main contentToggle navigationSelect versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveToggle navigationStriim Cloud 4.2.0 Select versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveprintToggle navigationStriim Cloud 4.2.0 Dashboard GuidePrevNextDashboard GuideThe web UI's Dashboards can visualize application data in various ways. Run the PosApp and MultiLogApp sample applications to see some examples and follow the instructions in the Hands-on quick tour to create one.In this section: Search resultsNo results foundWould you like to provide feedback? Just click here to suggest edits.PrevNextSee how streaming data integration can work for
						you.Schedule a
						DemoDownload © 2023 Striim, Inc. All rights reserved. Last modified: 2023-03-02

Dashboard Guide


Dashboard rules and best practicesSkip to main contentToggle navigationSelect versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveToggle navigationStriim Cloud 4.2.0 Select versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveprintToggle navigationStriim Cloud 4.2.0 Dashboard GuideDashboard rules and best practicesPrevNextDashboard rules and best practicesYou must follow these rules when creating or editing a dashboard:Before creating a dashboard, deploy the application. Otherwise the field-selection menus in the dashboard property dialogs will be empty.Create the dashboard in the same namespace as the application.Include the namespace in query names (for example, MyWorkspace.q1).End SELECT statements with a semicolon.We also recommend these best practices:Before creating a visualization, create any drill-down pages it will link to, so you will be able to select the drill-down page(s) in the visualization properties.If the dashboard UI gets too much data it may become unresponsive, so write your SELECT statements to minimize the amount of data sent to the visualization. For example, for a bar chart showing totals by state, select sum(Count) as Count, State from Samples.MerchantActivity group by State; will send the visualization only one pair of Count and State values for each of the 50 states.If there are multiple applications in the same namespace, start the query name with the application name (for example, Samples.MyAppMyQuery), unless the query is shared by multiple apps.In this section: Search resultsNo results foundWould you like to provide feedback? Just click here to suggest edits.PrevNextSee how streaming data integration can work for
						you.Schedule a
						DemoDownload © 2023 Striim, Inc. All rights reserved. Last modified: 2017-01-10

Dashboard rules and best practices


Visualization types and propertiesSkip to main contentToggle navigationSelect versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveToggle navigationStriim Cloud 4.2.0 Select versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveprintToggle navigationStriim Cloud 4.2.0 Dashboard GuideVisualization types and propertiesPrevNextVisualization types and propertiesThis section describes the various types of visualizations that may be used in dashboards and properties you use to configure each type.Properties common to multiple visualization typesNote If the visualization configuration  dialog's properties display no fields,  that means something is wrong with its query, or the application has not been deployed.Data Retention Type: Select All to include all data from the query, or Current to include only the most recent. "All" is not supported for pie / donut charts as they would quickly become unreadable.Group By: If specified, each value for this field will be visualized as a single point, bar, or slice. This setting interacts with Data Retention Type as follows:Data Retention TypeGroup BybehaviorAllunspecifiedone new chart element for each value (for example, ever more bars are added to a chart)Allspecifiedone chart element per Group By categoryeach new value for a category is added to the element (for example, a vertical bar gets ever higher) Currentunspecifiedonly one chart element, which is updated for each new value (this setting would make sense for a gauge, which displays only a single value)Currentspecifiedone chart element per Group By categoryeach new value for a category updates the element (for example, a vertical bar goes up and down) The following shows the effect of the various combinations of Data Retention Type and Group By on a bar chart as each of four values (represented by red, yellow, green, and blue) is added.Color By: If specified, values from this field will populate the legend and (unless overridden by conditional colors) the color of chart elements.Data Series + / Delete series : For scatter plots and bar, line, pie and donut charts, adds or removes a data series.Series Alias: When you have defined multiple series, use this to define custom colors. These strings are also used for the legend labels, if any. See the line chart on the PosApp "Company details" page for an example.NoteIf you define multiple series, leave Group By unspecified.Type (for X and Y axes): select Linear or Logarithmic for numerical values, DateTime for time values, or Category for text values (for example, CompanyName)Filter settings - Visible: If enabled, when the visualization's data is being filtered, a pop-up will appear showing the filter criteria. See Creating links between pages.Time Field: A field of type DateTime to use when filtering by time (see Viewing dashboards). If not specified, filters will use WAction start time.Polling: See Defining dashboard queries.Drill Down and Page Filters: See Creating links between pages and Making visualizations interactive.Tooltip Configuration: Use this to defines which values will appear when you hover the mouse pointer over a map or chart point, slice, or bar. Check Show All to display all values selected by the query or click Add Another as many times as necessary to select individual fields.Add a conditional color: Allows you to manually select colors based  on JavaScript expressions, such as field_name=="value". For example:The seriesAlias variable may be used to manually assign colors to series based on their Series Alias settings. For example, from the line chart on the Company details page in the PosApp sample application's dashboard:The above settings produce this result:Show Legend: Check to display a legend of the Color By values in the visualization.Maximum number of values to show / Maximum number of series to show: A series is an element in a visualization that may include one or more values. For example, in the line chart above, there are four series (the four lines) and 40 values (the number of points per line). If you specify a Group By field, the number of distinct values in that field is the number of series.The maximum number of values is per series, so, for example, if for the chart above it was set to 20, each of the four lines would have 20 points. The oldest value and the series that was updated least recently will be removed from the visualization as necessary to keep within the maximums.Be sure you set these maximums high enough to display all the desired values. For example, in the map on the main page of PosAppDash, Maximum number of series to show needs to be at least 423 (the number of merchants), but Maximum number of values to show can be 1, since only one point is shown for each merchant.Regardless of this setting, each visualization can display a maximum of about 2000 values.Bar chartSet the Y (vertical) axis to the field containing the values that will control the height or length of the bars.Set the X (horizontal) axis to the field containing the labels for the bars and set the axis type to Category.For example, here are the settings for the horizontal bar chart on PosApp's main dashboard page:Here are the settings for the same chart but with vertical bars:See Properties common to multiple visualization types for information on the other settings and an example of how to create a stacked bar chart using Group By.Choropleth mapThis is a beta preview feature. To run a sample application, copy the Choropleth directory from .../Striim/docs to .../Striim/samples, run Samples/ChoroplethDemo.tql, and view the ChoroplethDemoDash dashboard. See www.highcharts.com/docs/maps/getting-started for more information.Column range chartThis is a variation on a Bar chart. The Value Type, Low Value Field, and High Value Field properties control the start and end points for the bars and the labels for axis on which the values are plotted. The low and high value fields must match the Value Type setting.GaugeA gauge is similar to a bar chart with a single bar. It visualizes a single numeric value on a 180-degree gauge. The query for a gauge will typically use an aggregate function such as MIN, MAX, or LAST to select a single value from the input field. See the See the PosApp "Company details" page for an example.Units is a text label for the gauge. Set the Minimum to zero or whatever other number is appropriate and Maximum at least as high as the maximum expected value. These values appear as labels below the left and right ends of the gauge.By default, the color changes gradually from green near the minimum to yellow in the middle and red at the maximum. You may set colors manually by defining Thresholds, but they will still change gradually. For example, the gauge above has a threshold of 60 for green and 100 for red, so with a value of 71 the gauge is yellowish-brown.Minimum, Threshold, and Maximum values may be defined using field names, optionally including formulas such as HistoricalAverage * 0.25 or HistoricalAverage * 2.Heat mapIn a heat map, the X and Y axis fields define a grid, with the squares of the grid colored based on the values of the Z axis. If the Label Cells option is checked, the Z values will appear in the cells.See Properties common to multiple visualization types for information on the other settings.IconAn icon can display various icons based on conditions (see the discussion of Add a conditional color in Properties common to multiple visualization types). The above properties, from the PosApp company details page, display a plus sign, minus sign, or check mark corresponding to the merchant's current status.For a visual guide to the hundreds of available icons, see: https://fontawesome.com/v4/cheatsheet/LabelA label is a simple text block. Use labels to add headings or explanations to your dashboards. A label does not have a query, so if you wish to include data from the application in the text, use a Value visualization instead.Label: the text to be displayedText: select desired text colorBackground: select desired background color (red slash on black is transparent)Heading Type: select one of the predefined text label types shown below:Leaflet mapThis is similar to the Vector map, but when you zoom in the map includes place names, streets, and street names.Longitude and Latitude: the fields containing the values to use to plot the map pointsValue: the field containing the values that will control the map point colors and sizesMin Bubble Size and Max Bubble Size: the range of sizes for the map pointsView Zoom: set to 1 to show the whole map, or higher to zoom inView Center Longitude and View Center Latitude: When View Zoom is specified, these settings control where the map is centered.Tiles URL: The web server from which the map gets its detail data. This should typically be left at its default, http://{s}.tile.osm.org/{z}/{x}/{y}.png.See Properties common to multiple visualization types for information on the other settings.Line, scatter, bubble, and area chartsSet the Y (vertical) axis to the values that will control the vertical position of the dots and the X (horizontal) axis to the field that will control the horizontal position.In line charts, Upper Bound and Lower Bound let you specify the range the chart. Set Lower Bound to 0 for a zero baseline.A bubble chart is identical to a scatter chart except there is a third axis, Z, that controls the size of the bubbles, so the chart can visualize data from three fields.See Properties common to multiple visualization types for information on the other settings.By default, area charts are like line charts, but the area below the line is filled in.If you change the Stacking option to Stacked, the areas are stacked like this:If you change the Stacking option to Percent Stacked, the areas are shown as portions of 100%:Pie and donut chartsSet the X (horizontal) axis to the field containing the labels for the pie slices and set the axis type to Category.Set the Y (vertical) axis to the field containing the values that will control the size of the pie sizes. The type may be Linear or Logarithmic.See Properties common to multiple visualization types for information on the other settings.TableA table displays values in a grid. Optionally, it may contain a search box.Category: If specified, the table will contain only one row for each value of the specified field. If you want to aggregate values, you must do that in the query.Show Headers: The first row will contain the column's Label string.Show Lines: Shows or hides the table grid.Rows per page: the number of rows to display at a time (note that if you add too many rows to fit in the query frame, the bottom rows will be cut off and not display)Column configuration: Defines the columns in the table. Click Add another to add sets of properties for each column in the table.Label: String to display in the header, if it is enabled.Sort Order: By default, columns appear in the order specified. You may use this property to rearrange them. Columns will appear from left to right in their sort order from low to high.Source Field: Field to provide the values.Icons configuration: Adds icons to rows based on the specified expressions. You could use this, for example, to show a thumbs-up icon for expected values and a thumbs-down icon for out-of-bounds values. The expression syntax is the same as for conditional colors.See Properties common to multiple visualization types for information on the other settings.ValueA value is a relatively open-ended visualization type that can be used to add almost any valid HTML to a dashboard.A value visualization does not require a query. Define a query only if you want to use data from the application in conditional expressions or include data in the value (as in the examples below).When you add a new value visualization, click Add a conditional template.Expression: If you have only one conditional template, set to true (this setting is case-sensitive, True will not work).If you have multiple conditional templates, use this field to determine which condition is used based on field values. For example:Text: select desired text colorBackground: select desired background color (red slash on black is transparent)Heading Type: select one of the predefined text label types shown below, or leave blank to format using CSS in the Template field:Template: Enter an HTML string to define what the value will display. To include a value from a query alias in the string, put its alias in double brackets. For example, from MultiLogApp:The template for that label is:
Unusual Activity    {{ cnt }} WActions
The query is SELECT COUNT(*) AS cnt FROM UnusualActivity; which returns a single value representing the total number of WActions in the UnusualActivity WActionStore as the alias cnt.Vector mapA vector map plots points on a simple world map using the latitude and longitude values in the data. See PosApp for an example of using Zip codes to look up latitude and longitude in a cache.Longitude and Latitude: the fields containing the values to use to plot the map pointsValue: the field containing the value that will control the map point colorsView Zoom: leave blank or set to 1 to show the whole map, or enter a digital fraction (such as .5) to zoom inX Offset and Y Offset: When View Zoom is less than 1, these settings control where the map is centered. The range for X Offset is 0 (maximum west) to 10000 (maximum east). The range for Y Offset is -10000 (maximum north) to 10000 (maximum south). With X Offset set to 1400 and Y Offset set to -7700, the map will be centered on the United States. With X Offset 5300 and Y Offset -7750, it will be centered on Turkey.See Properties common to multiple visualization types for information on the other settings.Word cloudThis visualization displays text strings in various sizes proportional to a specified field value. For example, in the data for the above visualization of the top ten all-time best selling singles, the strings are the names of songs, and the values are the number of copies sold.Word Text: the field containing the stringsWord Size: the field containing the values that will  word sizesMaximum number of values to show: Set this to a value larger than the total number of occurrences of all words to be displayed or the size of the words will be based on an unpredictable subset of the events.See Properties common to multiple visualization types for information on the other settings.In this section: Visualization types and propertiesProperties common to multiple visualization typesBar chartChoropleth mapColumn range chartGaugeHeat mapIconLabelLeaflet mapLine, scatter, bubble, and area chartsPie and donut chartsTableValueVector mapWord cloudSearch resultsNo results foundWould you like to provide feedback? Just click here to suggest edits.PrevNextSee how streaming data integration can work for
						you.Schedule a
						DemoDownload © 2023 Striim, Inc. All rights reserved. Last modified: 2023-03-01

Visualization types and properties


Working with dashboardsSkip to main contentToggle navigationSelect versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveToggle navigationStriim Cloud 4.2.0 Select versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveprintToggle navigationStriim Cloud 4.2.0 Dashboard GuideWorking with dashboardsPrevNextWorking with dashboardsAdding visualizations to a dashboardThe following instructions will create bar and donut charts. Before following these instructions, make sure PosApp is loaded in the Samples workspace, deployed, and running. (See the Hands-on quick tour for an introduction to creating dashboards.)From the top menu, select Dashboards > View All Dashboards, then click PosAppDash. The dashboard's main page appears.At the top right, click Edit this page (the pencil icon).At the left of the page, select the Pages tab, then click + to add a new page.Select the visualizations tab, then drag the Bar visualization icon into the workspace and drop it. This creates a bar chart.At the top of the chart, click Edit Query the (< > icon). The query editor opens.In the Name field, enter Samples.MyQuery. In the SELECT statement field, edit the query to read select count(*) as Count, Category from MerchantActivity group by Category; (you can copy and paste from this document), being sure to end with a semicolon. This will select only the data needed for the chart: the count of WActions for each category and the category names. Click Save Query.To open the visualization editor, click Configure (the pencil icon) or double-click anywhere in the chart.Set Group By and Color By to Category, the vertical axis to Count, the horizontal axis to Category, and the horizontal axis Type to Category, then click Save visualization. (The Category in the Type menu is a chart property, not the name of a field.) The chart appears in the workspace.Drag the Donut visualization icon into the workspace and drop it to create a donut chart.This chart will use the same query as the bar chart: click the Edit Query button, click in the Name field, select Samples.MyQuery, and click Save Query.Click the Configure button, set the options as you did for the bar chart, and click Save visualization.Defining dashboard queriesOnce you have added a new visualization to a dashboard, the next step is defining its query. Until you do this, the drop-down field menus in the visualization editor will be empty.For example, the query for the PosApp donut chart above is:select count(*) as Count, Status from MerchantActivity group by Status;This results in four Count values representing the number of merchants with each status. The Count values control the size of the slices and the Status values provide the labels.NoteWhen you save a query, the previous version is overwritten, and there is no record of it within Striim. Thus, if you are making substantial changes, it is a good idea to give the query a new name so as to preserve the original, or to copy the original and paste it in a text editor.NoteThe dashboard page- and visualization-level filters (see Dashboards page) are available only when querying a WActionStore that is persisted to Elasticsearch (see CREATE WACTIONSTORE).By default, dashboard queries are executed only once, when the visualization is loaded. To update the data, refresh the browser to reload the visualization.To have the a query update continuously, enable polling in the visualization properties. (This property is hidden if the query contains AND PUSH). The query will then be re-run every five seconds, or, if the query takes longer, as soon as it completes.When querying a WActionStore, the following additional syntax is available:SELECT ... FROM <WActionStore>
[
{ <integer> { SECOND | MINUTE | HOUR } |
  JUMPING <integer> { SECOND | MINUTE | HOUR } |
  <integer> { SECOND | MINUTE | HOUR } AND PUSH }
] ...[<time period>] without JUMPING or AND PUSH returns data for the specified period and does not update until you reload the page.[JUMPING <time period] immediately returns data for the specified time period and runs the query again at the same interval. For example, SELECT * FROM MerchantActivity [JUMPING 1 MINUTE] returns data for the past minute and then runs the query again every minute, so you always have one minute's worth of data that is never more than one minute old.[<time period> AND PUSH] returns data for the specified time period and adds more data every time an event is added to the WActionStore. For example, SELECT * FROM MerchantActivity [15 MINUTE AND PUSH] returns data for the past 15 minutes and adds new events indefinitely. Old data is not removed until you reload the page.Do not specify both JUMPING and AND PUSH.It is essential, particularly when using AND PUSH, to include LIMIT and ORDER BY clauses in the query to avoid overloading the dashboard with more data than it can display.Any WHERE, GROUP BY, HAVING, ORDER BY, or LIMIT clause must follow the ]. When PUSH is specified, polling is disabled.The SAMPLE BY clause (see CREATE CQ (query) may be useful when a visualization contains too many data points. For example, consider this chart using PosApp data with the query  SELECT * FROM MerchantActivity ORDER BY time:CREATE CQ (query)The dashboard shows as much of the data as it can hold, which is only the last half hour. If you change the query to  SELECT * FROM MerchantActivity ORDER BY time SAMPLE BY count, the dashboard can show 3-1/2 hours of data:Creating links between pagesTo create a drill-down link similar to the one that leads from the Main page to the "Company details" page in PosAppDash:If it does not exist already, create the target page (the page to be linked to).Switch to the source page (the page with the link), select the visualization that will contain the drill-down link, and click Configure (the cog icon).Under Drill Down Configuration, check Enabled.From the Page drop-down, select the target page.Under Page Filters, click Add Another.In Source FIeld, select the field you want to use to select the data to be shown in the drill-down. For example, in PosApp, if you wanted to drill down from a map point for more information about a merchant, you would select MerchantId.In Id, enter an alias to refer to the source field in the drill-down visualization's query. For example, for MerchantId, you might enter mid.If you need more than one source field for the drill-down visualization's query, add additional page filters.Save the visualization.Return to the target page, create a query if it does not exist already, or click the existing query's cog icon.Enter a SELECT statement using the Id(s) you defined in the source visualization and save the query. For example, to create a line chart of Count by StartTime and a table containing merchant details for the PosApp map drill-down described above, you might use this:SELECT CompanyName, Count, StartTime, City, State, Zip FROM
Samples.MerchantActivity WHERE MerchantID=:mid ORDER BY StartTime;Enter a SELECT statement using the Id(s) you defined in the source visualization and save the query. For example, to create a line chart of Count by StartTime and a table containing merchant details for the PosApp map drill-down described above, you might use this:If one does not already exist, create a visualization in the query, then click Done.Return to the source page and click whatever is associated with the drill-down. For example, for a line chart or map, click a point. The drill-down visualization should appear, populated with the data defined by the Source Field value for the point you clicked.Making visualizations interactiveDrill-downs can be used within a single page to filter data interactively. For example, the PosApp visualization below can be filtered by clicking on the pie-chart labels:If you click the WARM label of the right-hand pie chart, the map and heat map display only data for merchants currently in that category:This interactivity is defined by setting the drill-down configuration in the pie charts, then using their Id values as in the queries for the two other visualizations. The drill-down configurations are:visualizationdrill-down configurationStatus (left) pie chartPage: Interactive HeatMap Id: status Source field: StatusCategory (right) pie chartPage: Interactive HeatMap Id: category Source field: CategorySince these visualizations are on the Interactive HeatMap page, the drill-down filters the data without switching to another page.The US map's query is:select * from Samples.MerchantActivity [15 minute and push] where (:status
IS NULL or (Status = :status)) and (:category IS NULL or (Category = :category))
group by merchantId;When the page is first loaded, the :status and :category values are null, so the map displays all data. When you click the WARM label, the :category value is set to WARM, and the map updates accordingly.To clear the filter and return to viewing all data, click Clear All (next to the funnel icon at left).To explore this more, run PosApp and go to the Interactive HeatMap page.Embedding a dashboard page in a web pageUse the Embed command to generate HTML code for an iframe you can use to display a Striim dashboard page in a web page. Embedded dashboard pages include both page-level and visualization-level search and search and filter controls.The embedded dashboard will not require a Striim login. Instead, it uses a special user account with READ permission on the dashboard's namespace and SELECT permissions on the dashboard, its queries, and related the CQs, streams, and WActionStores.Log in as admin or another user with the Global.admin role.Go to the dashboard page you want to embed and click Embed.The exact permissions that will be granted to the special user account are displayed. Click I Agree to create the user account.Enter the desired width, height, and border width for the iframe, then click Copy.Paste the iframe in the appropriate location in the web page's HTML.Preview the web page (the Striim application must be running) and adjust the iframe's properties as necessary.In this section: Working with dashboardsAdding visualizations to a dashboardDefining dashboard queriesCreating links between pagesMaking visualizations interactiveEmbedding a dashboard page in a web pageSearch resultsNo results foundWould you like to provide feedback? Just click here to suggest edits.PrevNextSee how streaming data integration can work for
						you.Schedule a
						DemoDownload © 2023 Striim, Inc. All rights reserved. Last modified: 2023-03-02

Working with dashboards


Installation and upgradesSkip to main contentToggle navigationSelect versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveToggle navigationStriim Cloud 4.2.0 Select versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveprintToggle navigationStriim Cloud 4.2.0 Installation and upgradesPrevNextInstallation and upgradesTo install or upgrade Striim Platform, see Installation and configuration.To deploy Striim Cloud, see Deploying and managing Striim Cloud.Deploying and managing Striim CloudTo upgrade Striim Cloud, see Upgrading Striim Cloud.In this section: Search resultsNo results foundWould you like to provide feedback? Just click here to suggest edits.PrevNextSee how streaming data integration can work for
						you.Schedule a
						DemoDownload © 2023 Striim, Inc. All rights reserved. Last modified: 2023-06-09

Installation and upgrades


Configuring remote hostsSkip to main contentToggle navigationSelect versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveToggle navigationStriim Cloud 4.2.0 Select versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveprintToggle navigationStriim Cloud 4.2.0 Configuring remote hostsPrevNextConfiguring remote hostsThis section of the documentation describes various ways to configure remote hosts to send data to Striim.In this section: Search resultsNo results foundWould you like to provide feedback? Just click here to suggest edits.PrevNextSee how streaming data integration can work for
						you.Schedule a
						DemoDownload © 2023 Striim, Inc. All rights reserved. Last modified: 2022-05-12

Configuring remote hosts


Striim Forwarding Agent installation and configurationSkip to main contentToggle navigationSelect versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveToggle navigationStriim Cloud 4.2.0 Select versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveprintToggle navigationStriim Cloud 4.2.0 Configuring remote hostsStriim Forwarding Agent installation and configurationPrevNextStriim Forwarding Agent installation and configurationThe Striim Forwarding Agent is a stripped-down version of the Striim server that can be used to run sources locally on a remote host. For more information, see Using the Forwarding Agent.To install the Forwarding Agent when you deploy Striim from the AWS Marketplace, contact Striim support.Striim Forwarding Agent system requirementsmemory: 256MB to 1GB depending on adapter usedfree disk space: 500MB (free disk space must never drop below 10%)supported operating systems: any 64-bit version of Linux, Mac OS X, or Microsoft Windowssupported Java environments:recommended: 64-bit Oracle Java SE 8 JRE (JDK required to use HTTPReader or SNMPParser)also supported: 64-bit OpenJDK 8 JREfirewall: the following ports must be open:port 5701 inbound for TCP (Hazelcast): if 5701 is in use, Hazelcast will use 5702; if both 5701 and 5702 are busy, it will use 5703; and so onport 9081 outbound for TCP (HTTPS) for authentication with the Striim cluster; alternatiely, to use port 9080, set striim.cluster.https.enabled=false in agent/conf/agent.conf.ports 49152-65535 outbound for TCPAny driver required by a source that will run on the Agent must be installed in Agent/lib. See Installing third-party drivers in the Forwarding Agent.The Forwarding Agent gets its license from the Striim cluster. It does not need to be specified on the remote host where the agent is installed.Running the Forwarding Agent as a processUsing a supported web browser, log into Striim at <DNS name>:9080 with username admin and the admin password you specified when creating the Striim server.Select Help > Download Agent and save Striim_Agent_4.2.0.zip  to an appropriate location.  If you can not download it directly to the  host, download it to your local system and use scp to copy it to the host.Unzip the file. If you used scp to copy the file to the host, use ssh to log into the host and unzip it.Follow the instructions in Configuring the Forwarding Agent.To start the agent, make sure the Striim cluster the Agent will connect to is running, open a shell terminal, command prompt, or ssh session, change to the Agent directory, and enter bin/agent.sh or, in Windows, bin\agent.bat.Once you have successfully started the agent and connected to Striim, you may delete the .zip file.To stop the agent, switch to the command prompt in which it is running and press Ctrl-C.Running the Forwarding Agent as a service in CentOSLog in to Linux.Download striim-agent-4.2.0-Linux.rpm.Install the package: sudo rpm -ivh striim-agent-4.2.0-Linux.rpm. By default, the agent is installed in /opt/striim/agent/.Follow the instructions in Configuring the Forwarding Agent.Make sure the Striim server is running, then:For CentOS 6, enter sudo start striim-agent.For CentOS 7, enter:sudo systemctl enable striim-agent
sudo systemctl start striim-agentTo verify that the agent connected to the server, look on the Monitoring page (see Monitoring using the web UI).Running the Forwarding Agent as a service in UbuntuLog in to Linux and run sudo su to switch to root.Download striim-agent-4.2.0-Linux.deb.Install the package: dpkg -i striim-agent-4.2.0-Linux.deb. The agent is installed at /opt/striim/agent.Follow the instructions in Configuring the Forwarding Agent.Make sure the Striim server is running, then:for Ubuntu 14.04, enter start striim-agentfor Ubuntu 16.04 or later, enter systemctl enable striim-agent && systemctl start striim-agentTo verify that the agent connected to the server, look on the Monitoring page (see Monitoring using the web UI).Running the Forwarding Agent as a service in WindowsThis requires Windows PowerShell 5.0 or later.Follow the instructions in Running the Forwarding Agent as a process, but do not start the agent.Start Windows PowerShell as administrator and run the script Agent\conf\windowsAgent\setupWindowsAgent.ps1. Note that if you are in the windowsAgent directory, to run the script you must include the path: .\setupWindowsAgent.ps1.The message Error in OpenSCManager is of no concern if the script completes successfully.Start the Striim Agent service manually, or reboot to verify that it starts automatically.To uninstall the service, stop it, then run this batch file:Agent/conf/windowsAgent/yajsw_agent/bat/uninstallService.batConfiguring the Forwarding AgentBefore starting the agent, you must:If running Striim Cloud, Contact Striim support to get the sys password, striim.cluster.clusterName, and striim.node.servernode.address.Run agent/bin/aksConfig.sh or aksConfig.bat. When prompted, enter a password for the agent's local keystore and the sys password (used to authenticate the agent when it connects to the Striim cluster).Install any third-party drivers required by the readers that will run in the Forwarding agent (see Installing third-party drivers in the Forwarding Agent). No drivers are bundled with the Forwarding Agent.Edit agent/conf/agent.conf to specify the agent's settings, as follows:Always required: for the striim.cluster.clusterName property value, specify the cluster to connect to. Cluster names are case-sensitive.Always required: for the striim.node.servernode.address property value, specify the server's IP address or fully-qualified domain name. If the agent may connect to multiple servers, specify them all, separated by commas.If the system on which the agent is running has more than one IP address, specify the one you want the agent to use as the value for the striim.node.interface property.By default, the agent will join the Agent deployment group. If you wish to change that, specify another deployment group as the value for the striim.cluster.deploymentGroups property. If the specified deployment group does not exist, it will be created automatically. When multiple agents on different remote hosts will be used by the same source, they must belong to the same deployment group.When using Striim Cloud:Connect the system running the Forwarding Agent with Striim Cloud using a VPN tunnel.In agent.conf, add striim.node.isSaaS=trueIn Striim Cloud, open the Console and enter set SYSTEMPROP='striim.node.serverDomainName,<IP address>', replacing <IP address> with the Striim Cloud-side IP address for the VPN tunnel.Installing third-party drivers in the Forwarding AgentThis section describes installation of the third-party drivers required to use some adapters.Install the HP NonStop JDBC driver in a Forwarding AgentThis driver must be installed in every Forwarding Agent that will read from HP NonStop SQL/MX.CautionDo not install drivers for multiple versions of SQL/MX on the same Striim server. If you need to write to multiple versions of SQL/MX, install their drivers on different Striim servers and run each version's applications on the appropriate Striim server(s).Follow the instructions in the "Installing and Verifying the Type 4 Driver" section of HPE NonStop JDBC Type 4 Driver Programmer's Reference for SQL/MX for the SQL/MX version you are running to copy the driver .tar file from the HP NonStop system with the tables that will be read to a client workstation and untar it. Do not install the driver.Copy the t4sqlmx.jar file from the untarred directory to Agent/lib.Stop and restart the Forwarding Agent (see Starting and stopping the Forwarding Agent).Install the MariaDB JDBC driver in a Forwarding AgentThis driver must be installed in every Forwarding Agent that will read from MariaDB.Download mariadb-java-client-2.4.3.jar from http://downloads.mariadb.com/Connectors/java/connector-java-2.4.3.Copy that file to Agent/lib.Stop and restart the Forwarding Agent (see Starting and stopping the Forwarding Agent).Install the MemSQL JDBC driver in a Forwarding AgentMemSQL uses MySQL's JDBC driver. See Install the MySQL JDBC driver in a Forwarding Agent.Install the Microsoft JDBC Driver in a Forwarding AgentThis driver must be installed in every Forwarding Agent that will read from Microsoft SQL Server, Azure SQL Database, or Azure Synapse.That driver is not bundled with the Forwarding Agent, so to read from those sources, you must install one of the drivers.CautionDo not install both versions of the driver in the same Striim server or Forwarding Agent.For SQL Server 2008:Download the Microsoft JDBC Driver 6.0 for SQL Server .gz package from https://www.microsoft.com/en-us/download/details.aspx?id=11774 and extract it.Copy enu/jre8/sqljdbc42.jar to agent/lib.Stop and restart the Forwarding Agent (see Starting and stopping the Forwarding Agent).For all other versions:Download the Microsoft JDBC Driver 7.2 for SQL Server .gz package from https://www.microsoft.com/en-us/download/details.aspx?id=57782 and extract it.Copy enu/mssql-jdbc-7.2.2.jre8.jar to agent/lib.Stop and restart the Forwarding Agent (see Starting and stopping the Forwarding Agent).Install the MySQL JDBC driver in a Forwarding AgentThis driver must be installed in every Forwarding Agent that will read from MySQL.Download the Connector/J 8.0.27 package from https://downloads.mysql.com/archives/c-j/ and extract it.Copy mysql-connector-java-8.0.27.jar to Agent/lib.Stop and restart the Forwarding Agent (see Starting and stopping the Forwarding Agent).Install the Oracle Instant Client in a Forwarding AgentThe Oracle Instant Client version 21c must be installed and configured in the Linux host environment of every Forwarding Agent that will run OJet.Download the client from https://download.oracle.com/otn_software/linux/instantclient/211000/instantclient-basic-linux.x64-21.1.0.0.0.zip and follow the installation procedure provided by Oracle for the operating system of the Forwarding Agent host.Edit Agent/conf/agent.conf and add the NATIVE_LIBS property to specify the Instant Client path, for example, NATIVE_LIBS=/usr/local/instantclient_21.1.Stop and restart the Forwarding Agent (see Starting and stopping the Forwarding Agent).Install the Oracle JDBC driver in a Forwarding AgentThis driver must be installed on each Forwarding Agent that will read from Oracle.Download ojdbc8.jar from oracle.com.Save that file in agent/lib.Stop and restart the Forwarding Agent (Starting and stopping the Forwarding Agent).Install the PostgreSQL JDBC driverThe PostgreSQL JDBC driver is bundled with Striim Platform and Striim Cloud, but must be installed on each Forwarding Agent that will read from PostgreSQL.Download the PostgreSQL JDBC 4.2 driver from jdbc.postgresql.org/download/.Copy it to agent/lib.Stop and restart the Forwarding Agent (Starting and stopping the Forwarding Agent).Install the Snowflake JDBC driverThis driver is must be installed in every Forwarding Agent that will write to Snowflake.Download the Snowflake JDBC driver version 3.13.15 (snowflake-jdbc-3.13.15.jar) as described in Downloading / Integrating the JDBC Driver.Copy the downloaded .jar file to Agent/lib.Stop and restart the Forwarding Agent (Starting and stopping the Forwarding Agent).Install the Teradata JDBC driver in a Forwarding AgentThis driver is must be installed in every Forwarding Agent that will read from Teradata.Download the Teradata JDBC .tgz or .zip package from http://downloads.teradata.com/download/connectivity/jdbc-driver and extract it.Copy tdgssconfig.jar and terajdbc4.jar to agent/lib.Stop and restart the Forwarding Agent (see Starting and stopping the Forwarding Agent).Testing the Forwarding AgentYou may use this application (the sample data is installed with the agent) to verify that the agent is working:CREATE APPLICATION agentTest;

CREATE FLOW AgentFlow;
CREATE SOURCE CsvDataSource USING FileReader (
  directory:'SampleData',
  wildcard:'PosDataAgentSample.csv',
  positionByEOF:false)
PARSE USING DSVParser (
  header:Yes,
  trimquote:false)
OUTPUT TO CsvStream;
END FLOW AgentFlow;

CREATE FLOW ServerFlow;
CREATE TARGET t USING FileWriter( filename:'AgentOut')
FORMAT USING DSVFormatter ()
INPUT FROM CsvStream;
END FLOW ServerFlow;

END APPLICATION agentTest;Deploy AgentFlow in the Agent group and ServerFlow and agentTest in the Default group. Then run the application and verify that AgentOut.00 has been written to the Striim program directory.Starting and stopping the Forwarding AgentTo start a Forwarding AgentIf the agent was installed as a service:In CentOS 6 or Ubuntu 14.04:sudo start striim-agentIn CentOS 7 or Ubuntu 16.04 or later:sudo systemctl start striim-agentTo start the agent as a process, run Agent/bin/server.bat in Windows or Agent/bin/server.sh in OS X or Linux.To stop a Forwarding AgentIf the agent is running as a service:In CentOS 6 or Ubuntu 14.04:sudo stop striim-agentIn CentOS 7 or Ubuntu 16.04 or later:sudo systemctl stop striim-agentIn Windows (using PowerShell as an administrator):service-stop "Striim Agent"
If the agent is running as a process, press Ctrl-C in the terminal running agent.bat or agent.sh.Upgrading Forwarding AgentsStop the agent (see Starting and stopping the Forwarding Agent).Uninstall the agent:If the agent is running as a process, stop the process, copy agent.conf and any drivers you added to agent/lib to another location, and delete the agent directory.If the agent is running as a service in CentOS, open a terminal and run rpm -e striim-agent.If the agent is running as a service in Ubuntu, open a terminal and run dpkg --remove striim-agent.If the agent is running as a service in Windows, stop the Striim Agent process, copy agent.conf and any drivers you added to agent/lib to another location, then run Agent/conf/windowsAgent/yajsw_agent/bat/uninstallService.bat.Install the new version of the agent as described in the "Running the Forwarding Agent" topic appropriate for your environment. If running the agent as a process or as a service in Windows, use the backed-up copy of agent.conf, and before starting the agent copy any backed-up drivers to agent/lib. (If using rpm or dpkg, these files are preserved.)Updating the sys user password on the Forwarding AgentIf the sys user's password changes, use the following command to update the password (required to connect to a Striim cluster) on the agent:agent/bin/aksConfig.sh  -p <new password>Enabling agent failoverWhen a flow in an application with recovery enabled is deployed ON ONE (see DEPLOY APPLICATION) in a deployment group with more than one agent, and that agent goes down, Striim will automatically deploy the flow on another agent in the deployment group. The flow will continue running on the other agent even after the original agent comes back up.In this section: Striim Forwarding Agent installation and configurationStriim Forwarding Agent system requirementsRunning the Forwarding Agent as a processRunning the Forwarding Agent as a service in CentOSRunning the Forwarding Agent as a service in UbuntuRunning the Forwarding Agent as a service in WindowsConfiguring the Forwarding AgentInstalling third-party drivers in the Forwarding AgentInstall the HP NonStop JDBC driver in a Forwarding AgentInstall the MariaDB JDBC driver in a Forwarding AgentInstall the MemSQL JDBC driver in a Forwarding AgentInstall the Microsoft JDBC Driver in a Forwarding AgentInstall the MySQL JDBC driver in a Forwarding AgentInstall the Oracle Instant Client in a Forwarding AgentInstall the Oracle JDBC driver in a Forwarding AgentInstall the PostgreSQL JDBC driverInstall the Snowflake JDBC driverInstall the Teradata JDBC driver in a Forwarding AgentTesting the Forwarding AgentStarting and stopping the Forwarding AgentUpgrading Forwarding AgentsUpdating the sys user password on the Forwarding AgentEnabling agent failoverSearch resultsNo results foundWould you like to provide feedback? Just click here to suggest edits.PrevNextSee how streaming data integration can work for
						you.Schedule a
						DemoDownload © 2023 Striim, Inc. All rights reserved. Last modified: 2023-03-02


Apache Flume integrationSkip to main contentToggle navigationSelect versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveToggle navigationStriim Cloud 4.2.0 Select versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveprintToggle navigationStriim Cloud 4.2.0 Configuring remote hostsApache Flume integrationPrevNextApache Flume integrationOn the system running Flume:1. Extract striim_FlumeWebActionSink_....tgz on the system running Flume.2. Save the following as flume/conf/flume-env.sh (replace ... with the correct path):JAVA_OPTS="-Xms512m -Xmx1024m"
FLUME_CLASSPATH="/.../WebActionSink/lib/*"If you are setting up the sample application, return to Using Apache Flume and continue with step 2.3. Create a configuration such as flume/conf/waflume.conf, as described in Using Apache Flume. Alternatively, add the properties to an existing .conf file.4. Start Flume, specifying the configuration file:bin/flume-ng agent --conf conf --conf-file conf/waflume.conf --name agent -Dflume.root.logger=INFO,consoleIn this section: Search resultsNo results foundWould you like to provide feedback? Just click here to suggest edits.PrevNextSee how streaming data integration can work for
						you.Schedule a
						DemoDownload © 2023 Striim, Inc. All rights reserved. Last modified: 2017-01-10

Apache Flume integration


collectd configurationSkip to main contentToggle navigationSelect versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveToggle navigationStriim Cloud 4.2.0 Select versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveprintToggle navigationStriim Cloud 4.2.0 Configuring remote hostscollectd configurationPrevNextcollectd configurationBefore an application can use the CollectdParser, the following properties must be set in collectd.conf:LoadPlugin syslog
LoadPlugin aggregation
LoadPlugin cpu
LoadPlugin df
LoadPlugin disk
LoadPlugin interface
LoadPlugin load
LoadPlugin memory
LoadPlugin network
LoadPlugin rrdtool
LoadPlugin swap
LoadPlugin uptime
<Plugin "aggregation">
  <Aggregation>
    Plugin "cpu"
    Type "cpu"
    GroupBy "Host"
    GroupBy "TypeInstance"
    CalculateNum false
    CalculateSum false
    CalculateAverage true
    CalculateMinimum false
    CalculateMaximum false
    CalculateStddev false
  </Aggregation>
  <Aggregation>
    Plugin "memory"
    Type "memory"
    GroupBy "Host"
    GroupBy "TypeInstance"
    CalculateNum false
    CalculateSum false
    CalculateAverage true
    CalculateMinimum false
    CalculateMaximum false
    CalculateStddev false
  </Aggregation>
  <Aggregation>
    Plugin "swap"
    Type "swap"
    GroupBy "Host"
    GroupBy "TypeInstance"
    CalculateNum false
    CalculateSum false
    CalculateAverage true
    CalculateMinimum false
    CalculateMaximum false
    CalculateStddev false
  </Aggregation>
</Plugin>
<Plugin df>
	MountPoint "/"
	IgnoreSelected false
	ReportReserved false
	ReportInodes false
</Plugin>
<Plugin disk>
	Disk "/^[hs]d[a-f][0-9]?$/"
	IgnoreSelected false
</Plugin>
<Plugin network>
	<Server "127.0.0.1">
	</Server>
</Plugin>
<Plugin "swap">
	ReportByDevice false
	ReportBytes true
</Plugin>Replace 127.0.0.1 with the UDPReader's IP address.  If the UDPReader's port setting is not 25826, specify it as well:<Plugin network>
  Server "192.168.0.42" "25827"
</Plugin>See collectd.org for more information.Multiple remote hosts may send data to the same UDPReader source.In this section: Search resultsNo results foundWould you like to provide feedback? Just click here to suggest edits.PrevNextSee how streaming data integration can work for
						you.Schedule a
						DemoDownload © 2023 Striim, Inc. All rights reserved. Last modified: 2017-01-10

collectd configuration


SNMP configurationSkip to main contentToggle navigationSelect versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveToggle navigationStriim Cloud 4.2.0 Select versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveprintToggle navigationStriim Cloud 4.2.0 Configuring remote hostsSNMP configurationPrevNextSNMP configurationThis sample snmpd.conf will cause SNMP to collect system information and send it to the receiver of the sample application discussed in SNMPParser.rocommunity  public
# Default SNMPV3 user name
agentSecName disman
# Creating user, this user will be used by 'monitor' process to fetch system metrics.
createUser disman MD5 sercrt@1
# Setting user to have read only access to system metrics.
rouser disman auth
# SNMPV1 trap destination.
trapsink 10.1.10.114:15021 public
# Instruct agent to monitor disk space
disk / 50%
# Instruct agent to monitor CPU load.
load 1 1 1
# Setting up monitoring job to send alert/trap message.
monitor -S -D -r 5 -i sysName.0 -i hrSystemDate.0 -i sysUpTime.0 -o ifIndex
  -o ifSpeed -o ifHighSpeed  -o ifPhysAddress -o ifInOctets -o ifInUcastPkts -o ifInDiscards
  -o ifInErrors -o ifOutOctets -o ifOutUcastPkts -o ifOutDiscards -o ifOutErrors
  -o ifOperStatus "Interface Details" ifOutOctets 0 0Multiple remote hosts may be configured to send to the same trap destination.In this section: Search resultsNo results foundWould you like to provide feedback? Just click here to suggest edits.PrevNextSee how streaming data integration can work for
						you.Schedule a
						DemoDownload © 2023 Striim, Inc. All rights reserved. Last modified: 2018-01-26

SNMP configuration


GlossarySkip to main contentToggle navigationSelect versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveToggle navigationStriim Cloud 4.2.0 Select versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveprintToggle navigationStriim Cloud 4.2.0 GlossaryPrevNextGlossarytermdefinition / notesadaptersee Source and Targetcachesee CacheCDCsee Change Data Capture (CDC)clustersee Concepts Guidecomponenta Cache, Continuous query (CQ), Source, Stream, Subscription, Target, WActionStore, or Windowcontext streamsee WAction and WActionStorecontext typesee WAction and WActionStoreCQsee Continuous query (CQ)data typesee Typeeventsee Eventflowsee Flowindexsee WAction and WActionStorejumpingsee WindowKafka streamsee Kafka streamsnamespacesee TQL programming rules and best practices, Using namespaces, and Managing users, permissions, and rolesnodein the context of monitoring or deployment groups, a Striim server or Forwarding Agent that is part of a Striim cluster (see Monitoring Guide and Managing deployment groups)objectin the context of console commands or permissions, an application, flow, or componentquerysee Continuous query (CQ)rolesee Managing users, permissions, and rolessizesee Windowslidingsee Windowsourcesee Sourcestreamsee Streamsubscriptionsee Subscriptiontargetsee TargetTungsten Query Language (TQL)see Fundamentals of TQL programmingWActionStoresee WAction and WActionStorewindowsee WindowIn this section: Search resultsNo results foundWould you like to provide feedback? Just click here to suggest edits.PrevNextSee how streaming data integration can work for
						you.Schedule a
						DemoDownload © 2023 Striim, Inc. All rights reserved. Last modified: 2022-07-13

Glossary


Typographical and syntax conventionsSkip to main contentToggle navigationSelect versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveToggle navigationStriim Cloud 4.2.0 Select versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveprintToggle navigationStriim Cloud 4.2.0 Typographical and syntax conventionsPrevNextTypographical and syntax conventionsIn TQL and console-command syntax descriptions, the following conventions are used:Monospace indicates text to be typed into the console or a web UI dialog.Bold indicates a menu item, button name, or other web UI element that you select or click.Braces indicate you must choose one of two or more elements separated by vertical bars. For example, LIST { ROLES | USERS } means the available commands are LIST ROLES and LIST USERS.Angle brackets indicate elements you must replace. For example, you would replace <application name> with the name of a specific application.Square brackets indicate optional elements in a command. For example, MON [<application name>] means you may use the command MON by itself or followed by the name of an application.An ellipsis indicates that you may optionally specify multiple items. For example, fields=<field name>,... means you may specify multiple field names separated by commas, such as fields=city,state,zip. Similarly, <field name>:$IN$  <value>~... indicates that you may specify multiple field values separated by tildes, such as State:$IN$ California~Missouri~Nevada.In this section: Search resultsNo results foundWould you like to provide feedback? Just click here to suggest edits.PrevNextSee how streaming data integration can work for
						you.Schedule a
						DemoDownload © 2023 Striim, Inc. All rights reserved. Last modified: 2017-01-10

Typographical and syntax conventions


Release notesSkip to main contentToggle navigationSelect versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveToggle navigationStriim Cloud 4.2.0 Select versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveprintToggle navigationStriim Cloud 4.2.0 Release notesPrevNextRelease notesThe following are the release notes for Striim Cloud 4.2.0.Changes that may require modification of your TQL code, workflow, or environmentStarting with release 4.2.0, TRUNCATE commands are supported by schema evolution (see Handling schema evolution). If you do not want to delete events in the target (for example, because you are writing to a data warehouse in Append Only mode), precede the writer with a CQ with the select statement SELECT * FROM <input stream name> WHERE META(x, OperationName) != “Truncate”; (replacing <input stream name> with the name of the writer's input stream). Note that there will be no record in the target that the affected events were deleted.Handling schema evolutionIf you are using MSJet, Contact Striim support for additional files required to resolve known issue DEV-37025.MongoDB Reader no longer supports MongoDB versions prior to 3.6.MongoDB Reader reads from MongoDB change streams rather than the oplog. Applications created in earlier releases will continue to read from the oplog after upgrading to 4.2. To switch to change streams:Export the application to a TQL file.Drop the application.Revise the TQL as necessary to support new features, for example, changing the Connection URL to read from multiple shards.Import the TQL to recreate the application.Databricks Writer's Upload Policy's default eventcount value has been increased from 10000 to 100000 (see Databricks Writer properties).Customer-reported issues fixed in release 4.2.0DEV-11526: Oracle Reader hangs after network outageDEV-19035: unable to drop the JMSReader applicationDEV-22094: PostgreSQL Reader > DAtabase Writer with Oracle fails on timestamp with time zoneDEV-25489: Oracle Reader not checking supplemental loggingDEV-26693: Incremental Batch Reader with PostgreSQL error with TIMESTAMPTZDEV-27618: Mongo CosmosDB Writer is slow for initial loadDEV-28054: LEE does not show correct values when the app contains an open processorDEV-28500: GGTrail Reader not capturing ROWID in before imagesDEV-28534: alert manager SMTP reset issueDEV-28785: can't view Apps pageDEV-29264: REPORT LEE fails with com.webaction.wactionstore.Utility.reportExecutionTime errorDEV-29970: web UI message log missing messagesDEV-30476: high memory usage when GG Trail Reader processes large LOB dataDEV-31352: after making some changes in Flow Designer and dropping the app, the web UI hangsDEV-31423: error in UpgradeMetadataReposOracleTo4101.sqlDEV-31579: notification issueDEV-31993: MySQL Reader fails on a DDL change to a table not specified in the Tables propertyDEV-32268: PostgreSQL Reader issue with non-lowercase schemasDEV-32275: MongoDB Reader timed out after 10000 ms while waiting to connectDEV-32632: MS SQL Reader > Database Writer with SQL Server missing eventsDEV-33086: MongoDB Reader can't read from MongoDB version 5.0.13DEV-33166: Databricks Writer "This request is not authorized to perform this operation using this permission"DEV-33426: Databricks Writer "table not found" error when table existsDEV-33510: MongoDB CDC sending Insert operation as Update operationDEV-33543: exported TQL has stream and router DDL out of orderDEV-34346: MongoDB Reader with SSL > S3Writer crashDEV-34365: MariaDBReader does not halt when when binlog file is not presentDEV-34399: Role tab of User page in web UI is blankDEV-34551: GG Trail Reader uses old an old TDR record to create type and app crashes with ColumnType mismatchDEV-34623: Azure Synapse Writer "Incorrect syntax near 'PERCENT'"DEV-34725: PostgreSQL Reader > Database Writer with PostgreSQL JSON operator errorDEV-34768: unable to run setupOjet due to missing ojdbc-21.1.jarDEV-34874: cannot enable CDDL Capture with Start Time/ Start PositionDEV-34926: UI slowDEV-34966: Database Reader converting NULLs to 0 when selecting from int (unsigned) columnsDEV-35054: Oracle Reader SQLIntegrityConstraintViolationException: Column 'FILENAME' cannot accept a NULL value.DEV-35096: Alert Manager: email address with special characters not acceptedDEV-35164: Apps page keeps reloading after dropping appDEV-35195: ADLS Gen2 Writer error "Component Type: TARGET. Cause: null"DEV-35196: Issues when receiving alert mail during app crashDEV-35349: BigQueryWriter in streaming mode "Could not parse '2023-03-01 12:41:16.216614+00' as a timestamp"DEV-35379: Database Reader with SQL Server "Error occured while creating type for table, Problem creating type"DEV-35405: OJet firstSCN issueDEV-35428: MySQL Reader ignores DDL if there is a space before the schema name in the Tables stringDEV-35429: can't deploy app with router component after upgradeDEV-35481: MS SQL Reader > Database Writer with Oracle NO_OP_UPDATE exceptionDEV-35548: HTTP Reader is binding to non-SSL portDEV-35581: exceptions not showing up in exception storeDEV-35654: property variable created in the web UI doesn't work in appDEV-35790: BEFORE() function issueDEV-35881: Snowflake Writer "Timestamp '2023-01-01 ��:��:��.000000000 ' is not recognized"DEV-35974: Alert Manager page is blankDEV-35994: All vaults lost after restarting Striim Platform or Striim CloudDEV-36135: app goes into quiesce state every time it is restartedDEV-36157: Database Reader with MySql or MariaDB "Error occured while creating type for table {xxx.xxx}"DEV-36158: OJet issue when table has both primary and unique keysDEV-36166: MariaDB "Out of range value for column 'asn' : value 4220006002 is not in class java.lang.Integer range"DEV-36307: "invalid bytecode org.objectweb.asm.tree.analysis.AnalyzerException" when starting StriimDEV-36308: upgrade fails with "metadataDB field is not set to one of the options derby, oracle, or postgres"DEV-36352: MariaDB Reader > DatabaseWriter with MySQL "java.lang.Integer cannot be cast to java.lang.Short"Resolved issuesThe following previously reported known issues were fixed in this release:DEV-29579: Databricks Writer cannot be used in WindowsDEV-31993: control characters in DDL statements cause application to haltKnown issues from past releasesDEV-5701: Dashboard queries not dropped with the dashboard or overwritten on importWhen you drop a dashboard, its queries are not dropped. If you drop and re-import a dashboard, the queries in the JSON file do not overwrite those already in Striim.Workaround: drop the namespace or LIST NAMEDQUERIES, then manually drop each one.DEV-8142: SORTER objects do not appear in the UIDEV-8933: DatabaseWriter shows no error in UI when MySQL credentials are incorrectIf your DatabaseWriter Username or Password values are correct, you will see no error in the UI but no data will be written to MySQL. You will see errors in webaction.server.log regarding DatabaseWriter containing "Failure in Processing query" and "command denied to user."DEV-11305: DatabaseWriter needs separate checkpoint table for each node when deployed on multiple nodesDEV-17653: Import of custom Java function failsIMPORT STATIC may fail. Workaround: use lowercase import static.DEV-19903: When DatabaseReader Tables property uses wildcard, views are also readWorkaround: use Excluded Tables to exclude the views.Third-party APIs, clients, and drivers used by readers and writersAzure Event Hub Writer uses the azure-eventhubs API version 3.0.2.Azure Synapse Writer uses the bundled SQL Server JDBC driver.BigQuery Writer uses google-cloud-bigquery version 2.3.3.Cassandra Cosmos DB Writer uses cassandra-jdbc-wrapper version 3.1.0Cassandra Writer uses cassandra-java-driver version 3.6.0.Cloudera Hive Writer uses hive-jdbc version 3.1.3.CosmosDB Reader uses Microsoft Azure Cosmos SDK for Azure Cosmos DB SQL API 4.29.0.CosmosDB Writer uses documentdb-bulkexecutor version 2.3.0.Databricks Writer in AWS uses aws-java-sdk-sts version 1.11.320, aws-java-sdk-s3 version 1.11.320 , and aws-java-sdk-kinesis version1.11.240.Derby: the internal Derby instance is version 10.9.1.0.Elasticsearch: the internal Elasticsearch cluster is version 5.6.4.GCS Writer uses the google-cloud-storage client API version 1.106.0.Google PubSub Writer uses the google-cloud-pubsub client API version 1.110.0.HBase Writer uses HBase-client version 2.4.13.Hive Writer and Hortonworks Hive Writer use hive-jdbc version 3.1.3.The HP NonStop readers use OpenSSL 1.0.2n.JMS Reader and JMS Writer use the JMS API 1.1.Kafka: the internal Kafka cluster is version 0.11.0.1.Kudu: the bundled Kudu Java client is version 1.13.0.Kinesis Writer uses aws-java-sdk-kinesis version 1.11.240.MapR DB Writer uses hbase-client version 2.4.10.MapR FS Reader and MapR FS Writer use Hadoop-client version 3.3.4.MariaDB Reader uses maria-binlog-connector-java-0.2.3-WA1.MariaDB Xpand Reader uses mysql-binlog-connector-java version 0.21.0 and mysql-connector-java version 8.0.27.Mongo Cosmos DB Reader, MongoDB Reader, and MongoDB Writer use mongodb-driver-sync version 4.8.2.MySQL Reader uses mysql-binlog-connector-java version 0.21.0 and mysql-connector-java version 8.0.27.Oracle: the bundled Oracle JDBC driver is ojdbc-21.1.jar.PostgreSQL: the bundled PostgreSQL JDBC 4.2 driver is version 42.4.0Redshift Writer uses aws-java-sdk-s3 1.11.320.S3 Reader and S3 Writer use aws-java-sdk-s3 1.11.320.Salesforce Reader uses the Force.com REST API version 53.1.0.Salesforce Writer: when Use Bulk Mode is True, uses Bulk API 2.0 Ingest; when Use Bulk Mode is False, uses the Force.com REST API version 53.1.0.Snowflake Writer: when Streaming Upload is False, uses snowflake-jdbc version.3.13.15; when Streaming Upload is True, uses Snowflake Ingest SDK 1.0.2-beta.5.Spanner Writer uses the google-cloud-spanner client API version 1.28.0 and the bundled JDBC driver is google-cloud-spanner-jdbc version 1.1.0.SQL Server: the bundled Microsoft SQL Server JDBC driver is version 7.2.2.In this section: Release notesChanges that may require modification of your TQL code, workflow, or environmentCustomer-reported issues fixed in release 4.2.0Resolved issuesKnown issues from past releasesThird-party APIs, clients, and drivers used by readers and writersSearch resultsNo results foundWould you like to provide feedback? Just click here to suggest edits.PrevNextSee how streaming data integration can work for
						you.Schedule a
						DemoDownload © 2023 Striim, Inc. All rights reserved. Last modified: 2023-06-16

Release notes


Striim Platform features not currently available in Striim CloudSkip to main contentToggle navigationSelect versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveToggle navigationStriim Cloud 4.2.0 Select versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveprintToggle navigationStriim Cloud 4.2.0 Striim Platform features not currently available in Striim CloudPrevNextStriim Platform features not currently available in Striim Cloudmulti-server clusters and failoverthe schema conversion utility (initial load wizards with Auto Schema Creation are supported in both Striim Platform and Striim Cloud)using environment variables in adapter propertiesreading from SQL Server 2008 directly, without using a Forwarding Agentwriting to SQL Server 2008using Active Directory authentication with Azure SQL Database, Azure Synapse, or SQL Serverthe SysOut adapterusing LDAP authenticationreading log filesfile lineagemonitoring using JMXcreating custom Java functionsIn this section: Search resultsNo results foundWould you like to provide feedback? Just click here to suggest edits.PrevNextSee how streaming data integration can work for
						you.Schedule a
						DemoDownload © 2023 Striim, Inc. All rights reserved. Last modified: 2022-09-08


Contact Striim supportSkip to main contentToggle navigationSelect versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveToggle navigationStriim Cloud 4.2.0 Select versionStriim Cloud 4.2.0 (current release)Striim Platform 4.2.0 (current release)Striim Cloud 4.1.2Striim Platform 4.1.2Striim Cloud 4.1.0Striim Platform 4.1.0Striim documentation archiveprintToggle navigationStriim Cloud 4.2.0 Contact Striim supportPrevContact Striim supportSelect Create ticket from the  menu, fill out the Contact Support form, and click Submit.In this section: Search resultsNo results foundWould you like to provide feedback? Just click here to suggest edits.PrevSee how streaming data integration can work for
						you.Schedule a
						DemoDownload © 2023 Striim, Inc. All rights reserved. Last modified: 2023-06-02

Contact Striim support


Documentation | Striim                                                   Products  Striim Cloud Striim Platform Striim for BigQuery Striim For Databricks Striim for Snowflake          Striim CloudA fully managed SaaS solution that enables infinitely scalable unified data integration and streaming.     Striim PlatformOn-premise or in a self-managed cloud to ingest, process, and deliver real-time data.       Striim for BigQuery     Striim for Databricks     Striim for Snowflake        Pricing      Pricing that is just as flexible as our products         Learn More            Solutions  Striim on AWS Striim Cloud Striim and Microsoft Azure Databricks and Striim Striim and Snowflake Financial Services Retail and CPG Striim Solutions for Healthcare and Pharmaceuticals Striim Solutions for Travel, Transportation, and Logistics Striim Solutions for Manufacturing and Energy Striim Solutions for Telecommunications Striim Technology Striim Media         TECHNOLOGIES        AWSDeliver real-time data to AWS, for faster analysis and processing.     Google CloudUnify data on Google Cloud and power real-time data analytics in BigQuery.      Microsoft AzureQuickly move data to Microsoft Azure and accelerate time-to-insight with Azure Synapse Analytics and Power BI.       DatabricksUnleash the power of Databricks AI/ML and Predictive Analytics.     SnowflakeFulfill the promise of the Snowflake Data Cloud with real-time data.            INDUSTRIES       Financial Services     Retail & CPG     Healthcare & Pharma     Travel, Transport & logistics     Manufacturing & Energy     Telecommunications     Technology     Media         Pricing  Pricing          Unbeatable Price Performance.Flexible Models for Every Business.          Connectors  Data Sources and Targets          ConnectorsStriim can connect hundreds of source and target combinations. View a complete list.          Resources  Learning Blog Community Events Support Documentation         LEARN     BlogRead the latest blogs from our experts      LearningSearch all our latest recipes, videos, podcasts, webinars and ebooks        CONNECT     EventsFind the latest webinars, online, and face-to-face events     The Striim CommunityStay up to date on new product updates & join the discussion.       SUPPORT     Support & ServicesLet Striim’s services and support experts bring your Data Products to life     DocumentationFind the latest technical information on our products         Company  About Careers Customers Partners Striim Newsroom Contact         About StriimLearn all about Striim, our heritage, leaders and investors     CareersLooking to work for Striim? Find all the available job options     CustomersSee how our customers are implementing our solutions       PartnersFind out more about Striim's partner network     NewsroomFind all the latest news about Striim      Contact UsConnect with the experts at Striim         Free Trial      X          View a Demo           Free Trial                     Welcome to Striim Documentation      Welcome to Striim! Find the links below to your product and access all relevant documentation.                             Striim Cloud      All your documentation needs for our fully-managed Cloud SaaS solution                   Striim Platform      All your documentation needs for our self-hosted solution                   Striim for BigQuery      All your documentation needs for Striim for BigQuery                   Striim for Databricks      All your documentation needs for Striim for Databricks                   Striim for Snowflake      All your documentation needs for Striim for Snowflake                   Striim for StreamShift      All your documentation needs for StreamShift                  ×            ×  Loading...                             Products Striim Platform Striim Cloud Striim for BigQuery Google Cloud Microsoft Azure Databricks Snowflake AWS    Products Striim Platform Striim Cloud Striim for BigQuery Google Cloud Microsoft Azure Databricks Snowflake AWS          Data Mesh Real Time Operations Data Modernization Digital Customer Experience Data Fabric Real-Time Analytics Industries    Data Mesh Real Time Operations Data Modernization Digital Customer Experience Data Fabric Real-Time Analytics Industries          Documentation Blog Recipes Resources Videos Support Events Community    Documentation Blog Recipes Resources Videos Support Events Community          Customers Partners Pricing Connectors Compare Contact    Customers Partners Pricing Connectors Compare Contact          Company Newsroom Careers Ethics Hotline    Company Newsroom Careers Ethics Hotline                     Copyright©2012-2023 Striim | Legal | Privacy Policy         We're Hiring                           Linkedin      Facebook      Twitter      Youtube      Rss                               Products Use Cases  Data Modernization Operational Analytics Customer 360 Data Mesh Multi-Cloud Data Fabric Digital Customer Experience Industries   Connectors Resources  test   Company    Products Use Cases  Data Modernization Operational Analytics Customer 360 Data Mesh Multi-Cloud Data Fabric Digital Customer Experience Industries   Connectors Resources  test   Company

Documentation | Striim