A number of parameters can be controlled by the ErgoTechConfiguration.properties (TransSECS) or the mix.properties(MIX) file. A sample, file is installed with the application. If these parameters are not present in the file, the defaults will be used.

opcua.serverhosts If present the hostnames provided will be used to create endpoints for the server
opcua.certs.dir  The root folder for all certificates.  This defaults to "security" in the folder in which the application is started
opcua.servername The name of the server. This defaults to MIXOPCServer
opcua.tcp.port The port for opc tcp connections
opcua.https.port The port for https connections
opcua.certificates.dir The folder that contains the server certificate
opcua.serverpass The password of the server certificate
opcua.trusted.cert.location The location of client certificates.  This defaults to security/security/pki.  Three folders, //issuers//, //rejected//, and  //trusted// folders contain the certificates.  Trusted client certificates should be placed in the //trusted// folder

opcua.bind.address  Additional, local, interfaces to which to bind.
opcua.securitypolicy The OPC security policy to use.  Options are: //None, Basic128Rsa15, Basic256, Basic256Sha256, Aes128_Sha256_RsaOaep, Aes256_Sha256_RsaPss// .  These options are described [[https://profiles.opcfoundation.org/profilefolder/474|in the OPC Foundation Documentation]] .  If not specified, Basic256Sha256 will be used.  Note that //None// is insecure.  The ErgoTech OPC Server will, by default, present this on the local interface (accessible only by applications running on the same host).  //Basic256//, and //Basic128Rsa15// are deprecated and not recommended for security reasons.

With the TransSECS OPCUA server deployment no additional setup is required for the TransSECS SECS/GEM server. The server is deployed in the project's OPCUA folder and can be run directly from there. The parameters above can be configured in the ErgoTechConfiguration.properties file.