iFIX Issues

DE42170: iFIX unable to write data or acknowledge alarms due to non-default Tomcat port

The secmgr.cclr.dll.config file contains an incorrect host or port.

Do the following to resolve this issue:
  1. In the Registry, find the Tomcat port in use by opening the 'Environment' value and looking for the TOMCAT_LOCATION line. The following shows that 8444 is the Tomcat port in use: 
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\
GETomcat8\Parameters 'Environment' value, 
TOMCAT_LOCATION contains the port at the end (TOMCAT_LOCATION=https://127.0.0.1:8444)
  2. Record this port number. For this example, the Tomcat port is 8444.
  3. Open the secmgr.cclr.dll.config file in the C:\Program Files (x86)\GE\iFIX folder.
  4. Type the Tomcat port in the "oauthPort" value setting, as shown below:
    ?xml version="1.0" encoding="utf-8" ?>
<configuration>
 <appSettings>
  <add key="oauthHost" value="127.0.0.1"/>
  <add key="oauthPort" value="8444"/>
  <add key="oauthEndPoint" value="oauth"/>
  <add key="strictCertificatePolicy" value="false"/>
 </appSettings>
</configuration>
  5. Restart iFIX for this change to take effect.

DE47858: Alarm Card shows partial connection () to an iFIX alarm source that is no longer installed on the Web HMI server

On systems where iFIX was uninstalled or where iFIX is installed but it is not being used as the alarm source for Web HMI, perform these steps to prevent the Alarm Gateway from trying to connect to iFIX and report a connection failure:

  1. Navigate to C:\ProgramData\Proficy\WebHMI\DataServices.
    Note: The ProgramData folder is hidden by default in Windows. You may need to change the Windows Folder Options, or type this folder directly in to the address bar of the File Explorer to navigate to it.
  2. Open the data-services-config.json configuration file in a text editor.
  3. Find the following section in this file and delete the text in bold.
    Note: Be sure to delete the comma preceding “comServers” or Web HMI cannot read the data-services-config.json file, and data and alarms will not flow in Web HMI.
    "alarmGateway": {
        "logFilePath": "%ProgramData%\\Proficy\\Logs\\",
        "traceLevel": 3,
        "stackTraceLevel": 1,
        "maxLogFileEntries": 100000,
        "maxLogFileBackups": 5,
        "logicalName": "alarms",
        "brokerHost": "localhost",
        "brokerExchange": "alarms",
        "brokerRequiresSsl": true,
        "brokerCertificate": "C:\\Program Files\\Proficy\\AlarmGateway\\ssl\\alarmGateway.p12",
        "brokerPassword": "K9Umpz3btpQlB9n6AsUOm7qvKSoE2nwpdGjQ3m4G4HIbwKkca+JiQ/mO5B3kELAE",
        "maxAlarmsPerMessage": 1000,
        "loggingFlagsForCom": 0,
         "comServers": [
            {
                "logicalName": "alarms",
                "hostName": "localhost",
                "progId": "Proficy.OPCiFIXAE.1"
            }
        ]
    }
  4. Verify the section looks like this:
    "alarmGateway": {
        "logFilePath": "%ProgramData%\\Proficy\\Logs\\",
        "traceLevel": 3,
        "stackTraceLevel": 1,
        "maxLogFileEntries": 100000,
        "maxLogFileBackups": 5,
        "logicalName": "alarms",
        "brokerHost": "localhost",
        "brokerExchange": "alarms",
        "brokerRequiresSsl": true,
        "brokerCertificate": "C:\\Program Files\\Proficy\\AlarmGateway\\ssl\\alarmGateway.p12",
        "brokerPassword": "K9Umpz3btpQlB9n6AsUOm7qvKSoE2nwpdGjQ3m4G4HIbwKkca+JiQ/mO5B3kELAE",
        "maxAlarmsPerMessage": 1000,
        "loggingFlagsForCom": 0
    }
  5. Save the file. If using Notepad, ensure data-services-config.json is not saved with a .txt extension.
  6. Restart the Alarm Gateway and GE Tomcat Server Windows services for this change to take effect.