event raised when server has been successfully registered on the local discovery server
event raised when server registration has been successfully renewed on the local discovery server
event raised when server has been successfully unregistered from the local discovery server
event raised after the server has raised an OPCUA event toward a client
event raised when the server received a request from one of its connected client. useful for trace purpose.
event raised when the server send an response to a request to one of its connected client. useful for trace purpose.
event raised when a new secure channel is opened
event raised when a new secure channel is closed
event raised when the server refused a tcp connection from a client. ( for instance because too any connections)
event raised when a OpenSecureChannel has failed, it could be a invalid certificate or malformed message
false if anonymous connection are not allowed
the maximum number of concurrent sessions allowed on the server
the maximum number for concurrent connection per end point
the user manager
the maximum number of subscription that can be created per server
Sets or gets the default captureRejection value for all emitters.
This symbol shall be used to install a listener for only monitoring 'error'
events. Listeners installed using this symbol are called before the regular
'error'
listeners are called.
Installing a listener using this symbol does not change the behavior once an
'error'
event is emitted, therefore the process will still crash if no
regular 'error'
listener is installed.
construct a service Fault response
if requestExactEndpointUrl is set to true the server will only accept createSession that have a endpointUrl that strictly matches one of the provided endpoint. This mean that if the server expose a endpoint with url such as opc.tcp://MYHOSTNAME:1234, client will not be able to reach the server with the ip address of the server. requestExactEndpointUrl = true => emulates the Prosys Server behavior requestExactEndpointUrl = false => emulates the Unified Automation behavior.
The server build info
total number of bytes read by the server since startup
total number of bytes written by the server since startup
the number of connected channel on all existing end points
the number of sessions currently active
The number of active subscriptions from all sessions
true if the server has been initialized
is the server auditing ?
the publishing interval count
the number of request that have been rejected
the number of session activation requests that have been rejected
The type of server
the number of sessions that have been aborted
Number of transactions processed by the server since startup
get one of the possible endpointUrl
Initialize the server by installing default node set.
and instruct the server to listen to its endpoints.
const server = new OPCUAServer();
await server.initialize();
// default server namespace is now initialized
// it is a good time to create life instance objects
const namespace = server.engine.addressSpace.getOwnNamespace();
namespace.addObject({
browseName: "SomeObject",
organizedBy: server.engine.addressSpace.rootFolder.objects
});
// the addressSpace is now complete
// let's now start listening to clients
await server.start();
set all the end point into a state where they do accept connections note: this method is useful for testing purpose
shutdown all server endpoints
the timeout (in ms) before the server is actually shutdown
Initiate the server by starting all its endpoints
set all the end point into a state where they do not accept further connections
note: this method is useful for testing purpose
Generated using TypeDoc
emitted when the server is trying to registered the LDS but when the connection to the lds has failed serverRegistrationPending is sent when the backoff signal of the connection process is raised