Skip to Main Content
AVEVA™ Products Feedback Portal

Welcome to our new feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, select the product of your interest in the left column. Then take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas will first be moderated before they are made visible to other users of this portal.

This page is for feedback for specific AVEVA solutions, excluding PI Systems and Data Hub. For links to these other feedback portals, please see the tab RESOURCES below.

Status Future consideration
Created by Nina NICHOLLS
Created on Feb 1, 2023

Make the diagnostic webservice public



[Problem Summary]

Customer has been using the GetActiveSessions method in the Diagnostics web service through HTTP in 6.5. Most Ampla web service end points are available through both HTTP and NET.TCP. However, since their upgrade to 8.1, they have not been able to use it anymore because only the NET.TCP end point is available for Diagnostics web service and that the Diagnostics web service through NET.TCP does not seem to be configured properly for actual use

[Reproduced in-house (Sydney GSC)]

YES


[Steps to Reproduce]

Use Visual studio, add WCF Web Service Reference:

Only the net.tcp end point is available as it can be seen in the Citect.Ampla.ServiceModel.Services.config file and it's not usable in Ampla's default configuration.


<add baseAddress="net.tcp://localhost/Ampla/Diagnostics/2007/07/Tcp" />


[Workaround]

none


[What is the impact to Customer/s]

Customer cannot use the GetActiveSessions method in the Diagnostics web service for their internal audit purpose



For more info on the primary case, please visit:


https://gcsservicecloudutils.azurewebsites.net/casedetails?casenumber=960234850

  • Attach files