Publisher shim
Request/reply discovers broker IDs and URLs
Entity affinity + rendezvous selects Broker A, B, or C
Subscriber shim
Maintains consumers on active brokers
Delivers by entity key · ACK after processing
Process health
Membership
SDKPerf test environment
The authenticated button runs the complete 100-message source → native Go shims → SDKPerf consumer test. No terminal is required. SDKPerf is optional JCSMP/SMF test tooling and is not part of production startup.
SDKPerf CLI examples
Prerequisites: Java, the official SDKPerf Java download, and private values exported as SDKPERF_CMD, SMF_URL, SDKPERF_USERNAME, VPN, and SDKPERF_PASSWORD. Start the subscriber first.
Direct broker smoke test — bypasses the shims
"$SDKPERF_CMD" "-cip=$SMF_URL" "-cu=$SDKPERF_USERNAME@$VPN" "-cp=$SDKPERF_PASSWORD" -mt=persistent -stl=swlb-sdkperf/direct-smoke -md
"$SDKPERF_CMD" "-cip=$SMF_URL" "-cu=$SDKPERF_USERNAME@$VPN" "-cp=$SDKPERF_PASSWORD" -mt=persistent -ptl=swlb-sdkperf/direct-smoke -mn=100 -mr=25 -msa=256 -ped=2
Managed end-to-end source/sink: the same verified SDKPerf flags target the dedicated ingress topic and durable result queue, but the authenticated workflow also runs the required Go adapter and connects it to the already-running shims. These two commands alone are not an end-to-end run.
"$SDKPERF_CMD" "-cip=$SMF_URL" "-cu=$SDKPERF_USERNAME@$VPN" "-cp=$SDKPERF_PASSWORD" -mt=persistent -sql=swlb-neutral-20260928.sdkperf.results -md -nsr
"$SDKPERF_CMD" "-cip=$SMF_URL" "-cu=$SDKPERF_USERNAME@$VPN" "-cp=$SDKPERF_PASSWORD" -mt=persistent -ptl=swlb-neutral-20260928/sdkperf/ingress -mn=100 -mr=25 -msa=256 -ped=2
Recent generic events
| Time | Group | Event ID | Entity | Duplicate |
|---|