Skip to content
PDF

Crosser

Crosser designs and develops streaming analytics and integration software for edge, on-premise or cloud. The Crosser platform enables real-time processing of streaming or batch data for Industrial IoT, data transformation, analytics, automation and integration. The Crosser platform consists of two core parts.

  • Crosser Cloud is the heart of the platform where all design and orchestration takes place. It is a multi-tenant SaaS service hosted by Crosser but also exists in an on-premise version that customers can run on a private cloud, inside the internal firewall.

  • Crosser Node is the real-time engine that customers install where they need it and anywhere a Docker container can be used.

Refer to the official Crosser homepage for more information on Crosser.

Requirements for usage with Nerve Blue

To use Crosser with Nerve Blue, a Crosser Cloud account is required. Use one of the provided test options or get in touch with Crosser directly:

Getting started

The Crosser workload is pre-configured in the Nerve Management System as part of the delivery so that the application can be used once the account for the Crosser Cloud is set up. Follow the steps below to finalize the configuration. The pre-configured workload is set up with the following settings:

Setting Value
Name Crosser
Release name 2.2.4
DOCKER IMAGE From Registry is selected with an Image path and login credentials to the Docker image.
Port settings Protocol
TCP

Host Port
1883

Container Port
1883
Container name Crosser_latest
Network name bridge
  1. Log in to the Nerve Management System. Note that the initial login credentials can be found in the customer profile.

  2. Select Workloads in the navigation on the left.

    !Workloads

  3. Select the Crosser workload.

  4. Select the latest version on the right to edit the settings of the version.

    !Edit version

  5. Log in to Crosser Cloud.

  6. Select Nodes in the navigation at the top.
  7. Select the Register Nodes tab.
  8. Enter a name for the node in the field.

    !Enter node name

  9. Select + Add. A notification saying Successfully added Edgenode appears below when the registration is successful.

  10. Select Show Credentials to display the NodeID and the Access Key. They are needed for the configuration of the Crosser workload.

    !Show credentials

  11. Switch back to the Management System.

  12. Select + next to New environment variable.
  13. Enter the following values:

    Field Value
    Env. variable SecurityConfiguration__Credentials__NodeId
    Variable value Enter the value next to Id in the Crosser Cloud credentials window.
  14. Select + next to New environment variable again.

  15. Enter the following values:

    Field Value
    Env. variable SecurityConfiguration__Credentials__AccessKey
    Variable value Enter the value next to Access Key in the Crosser Cloud credentials window.

    !Environment variables

  16. Select Update.

Onboarding more nodes to Crosser Cloud

In order to onboard further nodes to Crosser Cloud, a new version of the Crosser workload has to be created in the Management System.

  1. Select Workloads in the navigation on the left.
  2. Select the Crosser workload from the list of workloads.
  3. Click the plus symbol on the right. The settings from the latest version are automatically filled in.

    !Add new workload version

  4. Switch to Crosser Cloud.

  5. Select Nodes in the navigation at the top.
  6. Select the Register Nodes tab.
  7. Enter a name for the node in the field.

    !Enter node name

  8. Select + Add. A notification saying Successfully added Edgenode appears below when the registration is successful.

  9. Select Show Credentials to display the NodeID and the Access Key.

    !Show credentials

  10. Switch back to the Management System.

  11. Replace the value of the SecurityConfiguration__Credentials__NodeId environment variable with the new value of Id in the Crosser Cloud credentials window.
  12. Replace the value of the SecurityConfiguration__Credentials__AccessKey environment variable with the new value of Access Key in the Crosser Cloud credentials window.

    !Change variable values

  13. Update the Name of the version.

    Note

    Choose the name of the node in Crosser Cloud for easy identification of the workload version.

  14. Click Save to save the new version of the workload.

  15. Select Update.

Deploying the Crosser workload

After configuring the Crosser workload in both the Managament System and Crosser cloud, follow the instructions below to deploy the Crosser workload to a Nerve Node in order to start using Crosser with Nerve Blue.

  1. In the Management System select Deploy in the navigation on the left.
  2. Select the orange Docker tab. A list of Docker workloads will appear below.

    !Select Docker

  3. Select Crosser in the list of workloads. A list of versions of this workload will appear to the right.

  4. Select the corresponding version of the workload that is connected to a node in the Crosser Cloud.

    !Select Crosser version

  5. Select Next in the lower-right corner.

  6. Tick the checkbox next to the node that Crosser shall be deployed to.
  7. Select Next in the lower-right corner.

    !Select Nerve Node

  8. Select Deploy to execute the deployment.
    Optional: Enter a Deploy name above the Summary of the workload to make this deployment easy to identify. A timestamp is filled in automatically.

    !Deployment

The deployment should now be visible at the top of the deployment log. Click the log entry of the deployment to see a more detailed view.

To confirm if the workload has been deployed successfully, select Nodes in the navigation on the left. Select the corresponding node in the node tree and confirm if the orange Crosser workload tile is showing underneath the bar graph. The workload should show the status STARTED.

!Management System result

To confirm if the workload has been successfully connected to the Crosser Cloud, select Nodes in the navigation at the top. The node appears in the Active nodes list and is marked with a check mark in the Status column.

!Crosser result