WebHMI - Troubleshooting SOAP XMLx
Contents
1. Description Guide to troubleshooting SOAP XML communications OS Requirement Win 2000 XP Pro Server 2003 Vista Server 2008 Windows 7 General Requirement Microsoft IIS Genesis 32 Version 9 x DCOM Configuration 1 Go to Start gt Run and type dcomcnfg to open the Component Services dialog 2 Right click on Component Services gt Computers gt My Computer and select Properties Select the Default COM Security tab 3 Click on the two Edit Default buttons under Access Permissions and Launch Permissions Make sure that the following User Groups are in both sets of defaults and check the Allow boxes for all them Administrators Interactive Internet Guest Account Launch IIS Process Account Network Network Service System account NOTE Any changes to these default settings will require a reboot of your machine SOAP Wizard 1 Go to Start gt Programs gt ICONICS Tools to start the SOAP XML Wizard 2 Fill in the name or IP address of your machine and hit OK to run the Wizard 3 Hit OK to the complete dialog and you are finished with the wizard SOAP XML Channel 1 Go to Start gt Programs gt ICONICS WebHMI gt Client Configuration and click the Edit button for Option 2 2 Delete the TCP IP via channel and add a SOAP XML channel with your WebHMI Server as the mediator node 3 Set this channel as your default and save the file Channels and Hodes eR OPC2. Direct eee OFC over TCP IP Direct Channels eS OPC over SOAPAXML Direct Channels eT lt OPC over DCOM Direct Channels H OPC over SOAP AML Channel via www webhmi com default hek m webhmi com Figure 1 GenBroker Configuration SOAP XML Channel Copyright 2010 ICONICS Inc Page 1 of 1 GenBroker Setup 1 Start GenTray by going to Start gt Programs gt ICONICS Tools gt GENESIS32 Tray 2 Click on the GenTray icon in your task bar and set GenBroker as NT Service 3 Go to Control Panel gt Administrative Tools gt Services and open the properties dialog for ICONICS GenBroker 4 On the Log On tab set the service to run under an administrator account IIS Setup for Windows 2003 Server 1 Go to Control Panel gt Administrative Tools gt Internet Services Manager 2 Select Web Service Extensions and set All Unknown ISAPI Extensions to Allow IIS Setup for Vista 1 Go to Control Panel gt Administrative Tools gt Internet Information Services IIS Manager 2 Click on the Server item in the tree top level and select Features View then double click ISAPI and CGI Restrictions 3 Click Add under Actions on the right Alerts Gy ISAPI and CGI Restrictions The CGI module is not installed You can specify CGI applications that are allowed to execute but they will not be able to execute Path until the CGI module is installed Youindire Micros
3. oft NET Framework 2 0 5072 asp CA Windows Microsoft NET Framework64 w2 0 5072 Actions Use this feature to specify the ISAPI and CGI extensions that can run on the Web server Group by No Grouping Description Restriction ASP NET v2 0 5 Allowed ASP NET v2 0 5 Allowed Edit Feature Settings Help Figure 2 Adding ISAPI and CGI Restrictions 4 For the ISAPI or CGI path enter or browse C Program Files Common Files MSSoap Binaries SOAPIS30 dll Type SOAP ISAPI 3 0 into the description and check the Allow extension path to execute then click OK Firewall Notes If you use a firewall on your network check that it does not block SOAP XML traffic If it does you must make an exception to allow GenBroker and WebHMI traffic Also if Windows Firewall is turned on it is necessary to allow exceptions at least for GenBroker exe File and Printer Sharing and Web Server service TCP port 80 WebHMI Troubleshooting SOAP XML docx
Download Pdf Manuals
Related Search