Table of Contents
Advertisement
Section 4 Visualization and Data Access
When the History DA Server and Client PC are in different domain
When the History DA Server and Client PC are in different domain, first, ensure that
to setup a 'Trust Relationship' between both domains. Please contact your system
administrator for configuring the 'Trust Relationship' between domains.
Workgroup to Domain Environment
This scenario is a little bit complicated as compared to what we have seen in case,
when both Server and Client PCs are either in Workgroup or Domain Environment.
Make sure that when one PC is in domain and other is in workgroup, the workgroup
cannot authenticate domain user account.
So to make the Workgroup and Domain environment inter-operate, ensure to have
local user account defined in both Server and Client PC. Following are important
points to consider:
•
•
ODBC Interface
ODBC stands for Open Data Base Connectivity. It is a standard for accessing
different database systems. Any application can use ODBC to query data from a
database, regardless of the platform it is on or DBMS it uses. It is a connection that
is created to define a connection between a computer and a database stored on the
same or another system.
The History provides ODBC Connectivity via the ODBC Interface option available
with the History Database. Queries can be made to various tables available in the
database to achieve the required results.
Configuring Excel Data Source
The History database can be exported to MS Excel using the ODBC Interface. For
exporting the Historical Data, a Data source has to be defined in MS Excel.
2PAA107563-600 B
OPC Server must run as a local user account. This local user account should be
available in both Server and Client PC with same username and password.
OPC Client must run as a local user account on the client PC and that same
local user account must exist on the OPC Server PC with the same username
and password.
Workgroup to Domain Environment
49
Hide quick links:
Advertisement
Table of Contents
