Properties

The software version of the ISM server.

The ISM server’s fully qualified uniform resource identifier (URI): that is, its name or location on the utility’s network.

The communication protocol and security authentication type used on your organization’s network for communication between the FDM server and the ISM server.

• HTTPS using Windows Authentication.
• NET.TCP using Windows Authentication.
• NET.TCP using Certificate Authentication.

If you select this mode, you must also enter a certificate subject (preferred method) or certificate thumbprint, and select a store name and store location.

The name of the ISM server. This is a required field and must be entered whether the ISM Service Account is a Domain or Local user.

The ISM server port number through which FDM communicates with ISM.

Applies only if Communication Protocol is set to NET.TCP usingCertificate Authentication.

If the certificate specified below was issued to a computer other than the one on which ISM is installed, enter the DNS of that computer here.

This is the Log On user for the Itron Security Manager service.

(Applies only if Communication Protocol is set to HTTPS using Windows Authentication or NET.TCP using Windows Authentication.)

The service account and the domain of the service account, using the following format:

serviceaccount@domain.com

This is the FDM Tools Application Server certificate.

Important: The FDM Service Account must have full access to the certificate.

(Applies only if Communication Protocol is set to NET.TCP using Certificate Authentication.)

The location of the certificate store. Either of the following are acceptable, but "Local Machine" is the typical choice.

• Current User. Contains certificates specific to the currently logged user.
• Local Machine. Contains certificates shared by all users.

The name of the store in which the certificate is maintained. Select the appropriate store name from the list of predefined .NET Framework store names. The typical Store Name is "My."

This is the FDM Tools Application Server certificate.

For security, Itron suggests using the Thumbprint.

Important: Within the characters of the thumbprint are extra hidden characters. Any copying method, including the button labeled "Copy Thumbprint" captures the extra characters and the pasted string is not valid. You must manually type the string of characters exactly the way they appear onscreen.

The number of days (1-7) after the FDM server retrieves pending key exchanges and/or secure commands from ISM that the keys/commands become stale. Keys and secure commands remain valid for seven days after the ISM issues them, at which point they expire. The more time that passes before FSRs use them on the intended devices, the less time remains before the commands expire.

Days Before Stale lets you define the point at which FDM considers secure commands to be stale. It tells the FDM server how long it should let the commands remain unused before it deletes them and retrieves new ones from ISM. If FDM is unable to communicate with ISM, it can still use the stale commands until they expire. For example, if this setting is 4 (the default) and if the FDM server already holds secure commands for a particular device from the ISM, FDM will not request new commands until after four days have passed since it got the existing commands.

This makes it possible for the FDM server to send the same secure command for the same device to multiple handhelds without having to communicate with the ISM each time.

The Days Before Stale setting therefore also determines the minimum number of days keys and secure commands are valid after the mobile application receives them. A setting of 4 means secure commands will always be valid for at least three days (and up to seven days, depending on when the original request for the commands was made) before they expire.

The number of endpoints that the secure devices list file can contain. ISM sets a maximum limit of 2500 devices.