Changes for page CoAP ShowRunner to ShowRunnerCLC™ Setup Instructions

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -20,9 +20,6 @@
20	20	11. Define the remote system
21	21	11. Setup auth for the remote system
22	22	11. Save the configuration
23		-1. Verify successful communications with the following commands:
24		-11. On host, verify the client shows up as a web session: ##sradmin sh web sess##
25		-11. On client, verify the session with the host: ##sr sh lwapi cli br##
26	26
27	27	===== Host processor (LWAPI Server) Setup (e.g. DIN-AP3 @ 10.44.5.91) =====
28	28
...	...	@@ -30,9 +30,9 @@
30	30
31	31	1. If 3-series, Enable Authentication [##authentication on##] or SSL [##ssl self##] if not already enabled.  4-Series have authentication enabled by default.  User Page Auth should be turned off on 4-series.
32	32	1. Enable LWAPI
33		-From Console (v 3.011 or later; processor will automatically restart):
	30	+From Console (v 3.011 or later):
34	34	## sr lwapi enable true##
35		-In Config (@ root level; reloading the configuration is required):
	32	+In Config (@ root level):
36	36	## "LwApiEnable": true,
37	37	"LwApiSecurityLevel": "Auth",##
38	38	1. Create an API User and record the Key and Secret.  User group must have //LWAPI //role and //Execute //permissions.  This allows the  //Lightweight API Users// group has been created for this purpose:
...	...	@@ -47,7 +47,7 @@
47	47
48	48	===== Client processor (LWAPI Client) Setup (e.g. DIN-AP4) Version 3.011 or newer =====
49	49
50		-Steps 1-3 always needed. **Note:** host and client processors must be able to communicate with each other to use this method (i.e. the network must be configured and both processors must have SHOWRUNNER™ program and configuration loaded).
	47	+Steps 1-3 always needed.
51	51
52	52	1. Define remote system in the config:
53	53	## {