The default method for sending data to the Enterprise Historian is using Store and Forward (SaF) Technology. The technology consists of two web services that communicate with each other through a specified port. With SaF, each Logger is paired with a "Sender Service" that will buffer data passed into it and forward it to a specified “Receiver Service”, paired with an Enterprise Historian, when the connection is available.
Status
Session - A unique name beginning with the Sender source followed by the Sender session name.
Connected - Date/Time when the session last made a connection with the Sender session.
Tags - Total tags included in the session.
Writes/Sec - TVQs per second being written to the Historian.
TVQs - TVQs written since the last connection with the Sender session.
Properties - Tag properties sent since last connection. There are usually about 6 properties per tag. The Sender will only send properties when a session is created, not after a reconnect.
Annotations - Count of annotations being sent through a custom sender client. Not used by the Canary Labs Logger.
Error Count - Number of errors logged since the session was created.
Last Error - The last Receiver error logged to the Message log for each session.
Status bar - Receiver statistics
Sessions - Total number of current sessions.
Tags - Total number of tags from all sessions.
Redundant Tags - Visible only if redundant tags exist. Shows the number of duplicate tags being written to the same DataSet. By logging the same tags from 2 locations to the same DataSet assures the data will be written if 1 location goes down. This requires the timestamps be normalized to the same interval from both log sessions.
Writes - Total TVQs for all existing sessions.
Writes/Sec - Current TVQs for all sessions being written to Historian.
Version - Version information of the Canary SaF Receiver Service.
Redundant
By logging the same tags from 2 locations to the same DataSet assures the data will be written if 1 location goes down. This requires the timestamps be normalized to the same interval from both log sessions. The Redundant tab is only visible if redundant tags exist in the Receiver sessions.
Session - A unique name beginning with the Sender source followed by the Sender session name.
Tag - The tag name. This will show the same tag on 2 lines coming from 2 Sender sessions.
Configuration
Endpoints - The following endpoints addresses are provided for local and remote access.
Net.Pipe - Anonymous (Local Only) - Anonymous pipes provide interprocess communication on a local computer. This endpoint is always enabled and provides any interactive user access.
Net.TCP - Username - The Sender will try the Anonymous endpoint first. If it is not enabled then the Sender will try this secure endpoint using the credentials specified in the Sender credentials consisting of an Identity name and GUID. The default remote port number of 55256 can be changed if it conflicts with existing applications.
Net.TCP - Anonymous - Checking the Anonymous endpoint will allow any Sender to connect. A Sender outside a firewall could still be forced to use the secure endpoint by only opening the secure port 55256 for access. The default remote port numbers of 55255 can be changed if it conflicts with existing applications.
Certificate (Username) -
Info... - Launches the Certificate properties dialog. Enabled when the secure, Username endpoint is enabled.
Store Name -
| Member name | Description |
|---|---|
| AddressBook | The X.509 certificate store for other users. |
| AuthRoot | The X.509 certificate store for third-party certificate authorities (CAs). |
| CertificateAuthority | The X.509 certificate store for intermediate certificate authorities (CAs). |
| Disallowed | The X.509 certificate store for revoked certificates. |
| My | The X.509 certificate store for personal certificates. |
| Root | The X.509 certificate store for trusted root certificate authorities (CAs). |
| TrustedPeople | The X.509 certificate store for directly trusted people and resources. |
| TrustedPublisher | The X.509 certificate store for directly trusted publishers. |
Find Type -
| Member name | Description |
|---|---|
| FindByApplicationPolicy | The findValue parameter for the Find method must be a string representing either the application policy friendly name or the object identifier (OID, or Oid) of the certificate. For example, "Encrypting File System" or "1.3.6.1.4.1.311.10.3.4" can be used. For an application that will be localized, the OID value must be used, because the friendly name is localized. |
| FindByCertificatePolicy | The findValue parameter for the Find method must be a string representing either the friendly name or the object identifier (OID, or Oid) of the certificate policy. The best practice is to use the OID, such as "1.3.6.1.4.1.311.10.3.4". For an application that will be localized, the OID must be used, because the friendly name is localized. |
| FindByExtension | The findValue parameter for the Find method must be a string describing the extension to find. The object identifier (OID) is most commonly used to direct the Find method to search for all certificates that have an extension matching that OID value. |
| FindByIssuerDistinguishedName | The findValue parameter for the Find method must be a string representing the issuer distinguished name of the certificate. This is a more specific search than that provided by the FindByIssuerName enumeration value. Using the FindByIssuerDistinguishedName value, the Find method performs a case-insensitive string comparison for the entire distinguished name. Searching by issuer name is a less precise search. |
| FindByIssuerName | The findValue parameter for the Find method must be a string representing the issuer name of the certificate. This is a less specific search than that provided by the FindByIssuerDistinguishedNameenumeration value. Using the FindByIssuerName value, the Find method performs a case-insensitive string comparison using the supplied value. For example, if you pass "MyCA" to the Find method, it will find all certificates with the issuer name containing that string, regardless of other issuer values. |
| FindByKeyUsage | The findValue parameter for the Find method must be either a string representing the key usage or an integer representing a bit mask containing all the requested key usages. For the string value, only one key usage at a time can be specified, but the Find method can be used in a cascading sequence to get the intersection of the requested usages. For example, the findValue parameter can be set to "KeyEncipherment" or an integer (0x30 indicates "KeyEncipherment" and "DataEncipherment"). Values of the X509KeyUsageFlags enumeration can also be used. |
| FindBySerialNumber | The findValue parameter for the Find method must be a string that represents the serial number of the certificate as displayed by the certificate dialog box, but without the spaces, or as returned by theGetSerialNumberString method. |
| FindBySubjectDistinguishedName | The findValue parameter for the Find method must be a string representing the subject distinguished name of the certificate. This is a more specific search than that provided by the FindBySubjectNameenumeration value. Using the FindBySubjectDistinguishedName value, the Find method performs a case-insensitive string comparison for the entire distinguished name. Searching by subject name is a less precise search. |
| FindBySubjectKeyIdentifier | The findValue parameter for the Find method must be a string representing the subject key identifier in hexadecimal, such as "F3E815D45E83B8477B9284113C64EF208E897112", as displayed in the UI. |
| FindBySubjectName | The findValue parameter for the Find method must be a string representing the subject name of the certificate. This is a less specific search than that provided by the FindBySubjectDistinguishedNameenumeration value. Using the FindBySubjectName value, the Find method performs a case-insensitive string comparison using the supplied value. For example, if you pass "MyCert" to the Find method, it will find all certificates with the subject name containing that string, regardless of other subject values. Searching by distinguished name is a more precise search. |
| FindByTemplateName | The findValue parameter for the Find method must be a string representing the template name of the certificate, such as "ClientAuth". A template name is an X509 version 3 extension that specifies the uses of the certificate. |
| FindByThumbprint | The findValue parameter for the Find method must be a string representing the thumbprint of the certificate. |
| FindByTimeExpired | The findValue parameter for the Find method must be a DateTime value in local time. For example, you can find all the certificates that will be valid until the end of the year by eliminating the results of a Findoperation for FindByTimeExpired of the last day of the year from the results of a Find operation forDateTime.Now. |
| FindByTimeNotYetValid | The findValue parameter for the Find method must be a DateTime value in local time. The value does not have to be in the future. For example, you can use FindByTimeNotYetValid to find certificates that became valid in the current year by taking the intersection of the results of a Find operation forFindByTimeNotYetValid for the last day of last year with the results of a Find operation forFindByTimeValid of DateTime.Now. |
| FindByTimeValid | The findValue parameter for the Find method must be a DateTime value in local time. You can useDateTime.Now to find all the currently valid certificates. |
Subject Name - Name of the certificate subject.
Senders - The Senders sub-tab of Configuration provides control over secure (Net.TCP - Username) Sender connections from remote locations.
Allow - The Allow panel displays Sender credentials of Senders granted access to connect to the Receiver through the Net.TCP - Username endpoint.
Deny - By selecting an existing Sender from the list an Administrator can deny the Sender from connecting to the Receiver. This will move the credentials to the Deny panel where they can be removed or allowed again.
Deny - When a secure Sender connection is received it automatically goes into the Deny panel where an Administrator must allow for data to be passed through or remove it.
Allow - After selecting a credential from the Deny panel, clicking the Allow button will grant this Sender a secure connection.
Remove - After selecting a credential from the Deny panel clicking the Remove button will clear it from the list of Senders requesting a secure connection.
Refresh - The Deny panel does not update automatically. You must click the Refresh button to see any Senders requesting a secure connection.
Comments
0 comments
Article is closed for comments.