Hello,
I'm testing UA Gateway to use with a OPC DA 2.0 server. The server has been connect but the items value are always 0.
I'd like to try to enforce the use of DA 2.0 version. In [Installation Directory]/uagateway.config.xml (in a Windws 7 x 64 is C:\Program Files (x86)\UnifiedAutomation\UaGateway\bin), I try to change the parameter
<ForceDa2Browsing>false</ForceDa2Browsing> to true but it seems not work.
Please someone can confirm that this parameter is supported and work like I expect?
Thank You
Giuseppe
ForceDa2Browsing
Moderator: uagateway
- Support Team
- Hero Member
- Posts: 3072
- Joined: 18 Mar 2011, 15:09
Re: ForceDa2Browsing
Hi Giuseppe,
If the server does support only OPC DA 2.0x, UaGateway will automatically use only OPC DA 2.0 functionality.
The ForceDa2Browsing configuration option is a hidden configuration option to force OPC DA 2 browsing even if the server supports OPC DA 3.0 browsing. The OPC DA 3.0 browsing is much more efficient than DA 2 browsing and is therefore used if supported by the server. But some server indicate support but the functionality does not work. For such server we have the hidden configuration option.
If you send a log file of UaGateway to support@unifiedautomation.com we can have a look into your issue.
Best Regards,
Unified Automation Support Team
If the server does support only OPC DA 2.0x, UaGateway will automatically use only OPC DA 2.0 functionality.
The ForceDa2Browsing configuration option is a hidden configuration option to force OPC DA 2 browsing even if the server supports OPC DA 3.0 browsing. The OPC DA 3.0 browsing is much more efficient than DA 2 browsing and is therefore used if supported by the server. But some server indicate support but the functionality does not work. For such server we have the hidden configuration option.
If you send a log file of UaGateway to support@unifiedautomation.com we can have a look into your issue.
Best Regards,
Unified Automation Support Team
-
- Jr. Member
- Posts: 4
- Joined: 14 Mar 2014, 15:53
Re: ForceDa2Browsing
Hello,
thank you for the answer.
The OPC Server has been corrected about his regitration like DA 2.0 and now the comunication with UA Gateway is ok from this point of view.
But there is the limit that both UA Gateway and OPC Server should be executed in same session or the datachanged events not arrive to UA Gateway.
At the moment I've resolved it executing also the OPC Server like a windows service with the same account of UA Gateway service, but can happen that the OPC server has been executed with another account in a desktop session.
Is there any way to allow data exchange from the OPC DA applications (OPC UA Gateway like OPC DA client and the OPC DA Server) in different sessions?
Thanks for your help.
Giuseppe
thank you for the answer.
The OPC Server has been corrected about his regitration like DA 2.0 and now the comunication with UA Gateway is ok from this point of view.
But there is the limit that both UA Gateway and OPC Server should be executed in same session or the datachanged events not arrive to UA Gateway.
At the moment I've resolved it executing also the OPC Server like a windows service with the same account of UA Gateway service, but can happen that the OPC server has been executed with another account in a desktop session.
Is there any way to allow data exchange from the OPC DA applications (OPC UA Gateway like OPC DA client and the OPC DA Server) in different sessions?
Thanks for your help.
Giuseppe
- Support Team
- Hero Member
- Posts: 3072
- Joined: 18 Mar 2011, 15:09
Re: ForceDa2Browsing
Hello Guiseppe,
yes there is a way of executing the UaGateway and the DAServer with two different user context/credentials. The UaGateway is prepared for that, and we tried to make the handling as easy as possible.
The UaGateway runs as a "NT-Service" but has user credentials of a certain user assigned to this service (hence it is not running under the "service" context, like typicall services would do). The user credential assignment is done within the general tab of the Administration Dialog of the UaGateway. We typically recomment to pick and choose a local administrator account for this, because this accoun will require "logon service rights").
Secondly, during first startup the UaGateway creates a special UserGroup on the machine. This group (the "UaGatewayUsers") is automatically entered into all relevant DCOM security settings. The group originally will only contain the user/context of the user you have assigned for the UaGateway-Service.
Now, if your underlying DA Server is executed under different user/credentials (e.g. some local user "john") you don't need to mess arround with DCOM settings, you just need to add "john" to the group of "UaGatewayUsers" (because this group is already set up correctly) and all the permissions for exchanging data are set.
UaGateway and underlying DA Servers may run under different user/credentials or may even run on different machines (even though we don't recommend it, as this may cause some extra administrative work maintaining all the users and group).
Best Regards
Support Team
yes there is a way of executing the UaGateway and the DAServer with two different user context/credentials. The UaGateway is prepared for that, and we tried to make the handling as easy as possible.
The UaGateway runs as a "NT-Service" but has user credentials of a certain user assigned to this service (hence it is not running under the "service" context, like typicall services would do). The user credential assignment is done within the general tab of the Administration Dialog of the UaGateway. We typically recomment to pick and choose a local administrator account for this, because this accoun will require "logon service rights").
Secondly, during first startup the UaGateway creates a special UserGroup on the machine. This group (the "UaGatewayUsers") is automatically entered into all relevant DCOM security settings. The group originally will only contain the user/context of the user you have assigned for the UaGateway-Service.
Now, if your underlying DA Server is executed under different user/credentials (e.g. some local user "john") you don't need to mess arround with DCOM settings, you just need to add "john" to the group of "UaGatewayUsers" (because this group is already set up correctly) and all the permissions for exchanging data are set.
UaGateway and underlying DA Servers may run under different user/credentials or may even run on different machines (even though we don't recommend it, as this may cause some extra administrative work maintaining all the users and group).
Best Regards
Support Team