Striim 3.10.3 documentation

Configuring the Forwarding Agent

Before starting the agent, you must:

  1. 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).

  2. Install any third-party drivers required by the readers that will run in the Forwarding agent (see Installing third-party drivers). Note that the PostgreSQL and SQL Server drivers bundled with the Striim server must be installed manually in the Forwarding Agent.

  3. 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.

  • To change the agent's log level, see Setting the log levels.

  • If the HTTPS port is not 9081, see Configuring HTTP and HTTPS.Configuring HTTP and HTTPS

  • When Striim is running in Amazon EC2, specify the server's IPv4 Public IP address (displayed on the EC2 instance's Description tab) as the value for the  property.

  • When Striim is running in Azure, specify the server's DNS name (displayed on the Essentials tab for the Striim VM) as the value for the striim.node.servernode.address property.

  • When Striim is running in Google Cloud, specify the server's IP address as the value for the striim.node.servernode.address property. (Note that you should change the public IP address for the virtual machine running Striim from Ephemeral to Static or it will change every time the VM is restarted. See Promoting an ephemeral external IP address for instructions.)

  • When the Striim cluster is not discoverable using multicast UDP (for example, if it is running in Amazon EC2), specify the server's IP address or fully-qualified domain name as the value for the striim.node.servernode.address property. If the server's Hazelcast port is not the default 5701, include that as well (for example, 192.0.2.21:5702).

  • When the Striim cluster is Using TCP/IP instead of multicast UDP, specify a comma-delimited list of server IP addresses or ranges, for example, ‑S "192.0.2.0-7,192.0.2.21", as the value for the striim.node.servernode.address property.

  • When the Striim cluster and Forwarding Agent are on different private networks linked by VPN with a NAT gateway, you cannot specify the server's IP address as the value for striim.node.servernode.address since it is not reachable by the agent. To work around this, create a DNS name for the Striim server that resolves to a different IP address in each environment.

    For example, say that in the Striim cluster's network the DNS name striim.mycompany.com resolves to 192.0.2.101 and on the Forwarding Agent's network it resolves to 192.51.100.25. On each server in the Striim cluster, edit /etc/hosts and add 192.0.2.101 striim.mycompany.com and in startUp.properties set ServerFQDN=striim.mycompany.com. On the agent system, edit /etc/hosts and add 192.51.100.25 striim.mycompany.com. Restart the server(s), then restart the agent.