Configuring the probe

After installing the probe you need to make various configuration settings to suit your environment.

The following table lists the probe's features. For each feature, the table lists the properties you use to set up that feature, and the section in this guide that shows you how to set up the feature.

Some features are mandatory for all installations. For those features set the properties to the correct values or verify that their default values are suitable for your environment. The remaining features are optional depending on which ones you want to use.

Table 1. Configuring the probe
	Feature	Properties	See
Mandatory features:
	OPC UA connection information The information needed to correctly populate the header of each request message that the probe sends.	RequestHeaderRequest Handle RequestHeaderReturn Diagnostics RequestHeaderTimeout Hint	OPC UA communications information
	SOAP connection information The information needed to connect the OPC UA session endpoint (the device or EMS) with the web service SOAP interface.	EndpointHttpHost EndpointHttpPort EndpointSessionService Name OPCSessionName MaxResponseMessageSize RequestedSessionTimeout	Connecting to the OPC UA server
	Notification retrieval information The information needed to retrieve notification information	AcknowledgeAlarm RequestedPublishing Interval MaxNotificationsPer Publish RequestedLifetimeCount RequestedMaxKeepAlive Count ResyncInterval MonitoredItemsConfig File	Notification retrieval and synchronization
	ObjectServer host name	Server	ObjectServer information
Optional features:
	Reconnection policy Specifies whether the probe attempts to reconnect to the OPC UA endpoint following a communications failure.	RetryCount RetryInterval	Reconnection and probe backoff strategy
	Inactivity policy Specifies whether the probe disconnects from the OPC UA endpoint following a period of inactivity.	Inactivity	Inactivity
	Data Stream Capture Allows you to capture the stream of raw data from the target device and store it in a file.	StreamCapture StreamCaptureFilepath	Data stream capture
	Peer-to-peer failover pair Allows you to set up two probes to act as a failover pair to improve availability. If the master probe should stop working, the slave probes takes over until the master is available once more.	MessageLog Mode PeerHost PeerPort PidFile PropsFile RulesFile	Peer-to-peer failover functionality
	Use a sample server Allows you to use a sample server.	EndpointHttpHost EndpointHttpPort EndpointHttpService EndpointHttpTns EndpointSessionService Name OPCSessionName MaxResponseMessageSize RequestedSessionTimeout	Using the OPC Foundation sample server
	Running multiple instances of the probe Allows you to run two or more instances of the probe on a single host machine.	Name MessageLog PidFile PropsFile RulesFile	Running multiple probes
	Running the probe as a Windows service	None	Running the probe as a Windows service