Install the JSON Agent

Normally you would download the JSON Agent installer from the Synergex Resource Center but to simplify the workshop a copy of the installer is already present on your Linux server:

~/installers/sip-json-agent-1.0.0-1.el9.x86_64.rpm

Now it is time to install the Streaming Integration Platform JSON Agent:

sudo dnf install -y ~/installers/sip-json-agent-1.0.0-1.el9.x86_64.rpm

On the workshop system you can use the shortcut:

sip install json

As the installation proceeds you will see messages like this:

===============================================================================
 Streaming Integration Platform: JSON AGENT
===============================================================================

By installing this product you accept the terms of the Synergex Product License
agreement (PLA) which can be viewed at:

https://www.synergex.com/wp-content/uploads/2022/08/SDE_PLA_CURRENT-1.pdf

  Using configuration data from /etc/sysconfig/sip.conf
   - Service name  : sip-json-agent
   - User account  : sip-service
   - User group    : sip-service
   - Dflt profile  : default
   - HTTPS port    : 5128

  Installing       : sip-json-agent-1.0.0-1.el9.x86_64                                                                                                                                                                                                   1/1
  Running scriptlet: sip-json-agent-1.0.0-1.el9.x86_64                                                                                                                                                                                                   1/1

  Starting service

 The Streaming Integration Platform JSON AGENT has been installed.

 If you are using Configuration Server and configured the environment before
 starting this installation, and provided information about the environment
 by using /etc/sysconfig/sip.conf then the JSON agent should already be up
 and running.

 If you are not using Configuration Server you will need to manually provide
 configuration files by creating a directory with the lowercase name of the
 profile that you wish to use in /etc/synergex/sip and also copy the necessary
 configuration files to that directory. The necessary configuration files are:

  - MasterConfig.json
  - ServerConfig-JSONAgent.json

 If you change anything in the configuration you must restart the service:

    sudo systemctl restart sip-json-agent

 To check the status of the service:

      sudo systemctl status sip-json-agent

 To view the service log:

      sudo journalctl -u sip-json-agent

===============================================================================


  Verifying        : sip-json-agent-1.0.0-1.el9.x86_64                                                                                                                                                                                                   1/1

Installed:
  sip-json-agent-1.0.0-1.el9.x86_64

Complete!

Because you are using Configuration Server and pre-configured the environment, the agent should have successfully started.

Confirm the agent is running by viewing its log

sudo journalctl -u sip-json-agent

On the workshop system you can also use the shortcut:

sip log json

You should see something like this:

Oct 09 12:39:09 sipws systemd[1]: Started Streaming Integration Platform JSON Agent.
Oct 09 12:39:09 sipws bash[128505]: ===============================================================================
Oct 09 12:39:09 sipws bash[128505]: Streaming Integration Platform: JSON Agent
Oct 09 12:39:09 sipws bash[128505]: ===============================================================================
Oct 09 12:39:10 sipws bash[128505]: Bootstrap mode:         Configuration Server
Oct 09 12:39:10 sipws bash[128505]: Configuration server:   https://sipws:5121
Oct 09 12:39:10 sipws bash[128505]: Configuration cache:    /etc/synergex/sip/default
Oct 09 12:39:10 sipws bash[128505]: Profile name:           default
Oct 09 12:39:10 sipws bash[128505]: --------------------------------------------------------------------------------
Oct 09 12:39:10 sipws bash[128505]: Requesting authentication token from Configuration Server
Oct 09 12:39:10 sipws bash[128505]: Downloading master configuration from Configuration Server
Oct 09 12:39:10 sipws bash[128505]: Downloading server configuration from Configuration Server
Oct 09 12:39:10 sipws bash[128505]: --------------------------------------------------------------------------------
Oct 09 12:39:10 sipws bash[128505]: Admin UI port:       5128
Oct 09 12:39:10 sipws bash[128505]: Local database:      /etc/synergex/sip/json-agent/json-agent.db
Oct 09 12:39:10 sipws bash[128505]: Kafka brokers:       sipws:9092
Oct 09 12:39:10 sipws bash[128505]: Input topic (CDC):   DEFAULT_CDC/0
Oct 09 12:39:10 sipws bash[128505]: Output topic (JSON): DEFAULT_CDC_JSON/0
Oct 09 12:39:10 sipws bash[128505]: Replicated files:    9/9
Oct 09 12:39:10 sipws bash[128505]: TLS certificate:     /etc/synergex/sip/json-agent/json-agent-sipws.pfx
Oct 09 12:39:12 sipws bash[128505]: 20261009-123912 READY

The JSON Agent does not maintain a replica data set, it simply consumes messages from the main CDC topic, transforms the data into JSON format, and re-posts a new message to a different topic. Because of this there is no concept of restoring snapshots or bringing a local replica data set up to date; the fact that you see the READY message means that the agent is up and running.

Problems?

If the Agent is not running, seek assistance from a workshop facilitator.