It is the first "Version 1.0" Kepware product released in more than 12 years and represents a dedicated and coordinated effort from all departments and functions. Today, the entire PTC Kepware team achieved a major milestone by releasing ThingWorx Kepware Edge. For more information, check the respective server's documentation.Thursday, OctoIntroducing ThingWorx Kepware Edge Posted by Jeff Bates This certificate is then supplied to your third-party OPC server in a way specific to that server.
#Kepware edge download#
In the This Gateway tab, click the download link under Ignition OPC UA Client, and save the certificate somewhere to disk.The Manage Certificates page is displayed. Select OPC UA > Certificate from the left side of the page.Go to Config section in the Gateway Webpage.In these cases, you can manually download a client ticket from Ignition and supply it to the OPC server in the appropriate manner. The Ignition OPC UA server sends the client certificate to the third party OPC server when it tries to make the connection, however if the OPC server is not designed to expect these certificates then there may not be a straight forward way to accept them. The only difference may be in the way that the certificates are accepted on the server. While the above example is specific to KEPServerEX, the same concepts apply to connecting to any other third party OPC server that accepts OPC UA client connections. For more information, look into allowing "anonymous login" in KepServer's OPC UA Configuration Manager documentation. Alternatively, individual Kepware Projects can allow anonymous login. This typically means you need to specify user credentials for Ignition to use in the OPC UA server connection. When connecting to KepServer, some versions may not allow anonymous connections by default. Both the Backup Discovery URL and Backup Endpoint URL properties need to be configured.įor additional information on Failover, refer to OPC UA Client Connection Settings. The Backup properties should be used when a pair of redundant Ignition Gateways are trying to look at the same Kepware OPC UA server. To enable failover, check the box to Show advanced properties in the New OPC UA Connection Settings, set the Failover Enabled property to 'true,' and specify the Failover Endpoint. The failover Kepware OPC UA server will be used in the event the primary Kepware server goes down. The failover Kepware OPC UA server works the same as the OPC UA server with the exception that you need to have two copies of Kepware setup, preferably on different servers. Expand the KEPServer object until you find tags. To test your tag connections, go to the OPC Connections > Quick Client in the Configure section of the Gateway.The Status of your KEPServer connection should be Connected. Go back to the Config section of the Gateway, to OPC Connections > Servers.Click on the Trust button on the far right. Under the Client Security tab, you will find your new connection listed as Quarantined. In the Config section, go to the OPC UA > Security page. Again, right-click on the KEPServerEX icon on the desktop KEPServerEx is installed on, and from the menu select Reinitialize.Now the OPC Server Connections page shows the Status of Kepware to be Connected. On the OPC UA Configuration Manager window, go to the Trusted Clients tab.Ĭlick on Ignition OPC UA Client, click the Trust button, and click Close. The OPC UA Configuration Manager will appear. On the computer that KEPServer is installed on, right-click on the KEPServerEX icon on the desktop KEPServerEx is installed on, and from the menu select OPC UA Configuration. The next step is to have KEPServerEX trust the Ignition OPC UA Client. This is expected because KEPServerEX is denying access to the Ignition OPC UA Client. The connection will appear as Faulted.See the No Anonymous Token Policy Found section below. Most current installations of KEPServer require a login and will not connect without one.
#Kepware edge password#
Fill in the Username and Password if your KEPServer connection requires it.
0 kommentar(er)
