cliu/ci-server-engineer
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ci-server-engineer/.claude/skills/data-access/SKILL.md
cliu 547e5606cd Add RDBMS data exposure task to the data-access skill (tested in R1.05 only) 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-02 14:47:33 +10:00

3.5 KiB
Raw Blame History

name description
data-access CI Server R1.03 ACCESS Service: OPC UA, OPC DA, OPC A&E and ODBC. Use when the user wants to connect CI Server to an OPC UA server (OPC UA client line, station, subscription, points, certificates, node IDs, browse), let another application read CI Server data over OPC UA, OPC DA or OPC A&E (CI Server as OPC server, OPC visible / read / write, port 34493, endpoints, security policy, trusting client certificates, UaExpert), check why an OPC connection fails (BadCertificateUntrusted, BadSecurityChecksFailed, item stays NOT INIT), configure DCOM or DCOM tunnelling for OPC Classic, use ODBC / SimbaClient / SQL on datasets, or check the ODBC server (odbsrv, port 1583, SSL certificate), or copy item values and timestamps into Microsoft SQL Server with RDBMS data exposure (dbc.sup, DEM_CONNECTION, DBCSND, DBCDEM, DATA_EXPOSURE_DF, data exposure aggregation interval AGG_INTERVAL, ITEM_VALUES, SQL login, DSS-E-FLT_SYN_ERR). Sources IM 36K10L45-01EN, IM 36K10E20-01EN, IM 36K10G10-01EN ch. 10.

Data access: OPC, ODBC and RDBMS data exposure (R1.03; RDBMS exposure tested in R1.05 only)

Background: knowledge/manuals/IM36K10L45-01EN.md (ODBC, OPC DA/A&E/UA client and server, setup files), IM36K10E20-01EN.md (Engineering Module forms, certificates, PubSub). Equipment lines/stations/points in general: skill equipment.

Rules:

  • Run system-check first; follow the user's chosen way of working.
  • Trusting certificates is the user's decision. Show the certificate (folder, file name, common name) and let the user trust it (Engineering Module or moving the file); do not move certificate files yourself.
  • Making items OPC visible / writable exposes them to every OPC client on the network: only with the user's approval, and prefer read-only.
  • Never connect a CI Server OPC DA or A&E client to the same node's (or a DURM-connected node's) DA/A&E server: deadlock (manual §5.3). The OPC UA loopback is fine.
  • Changing opxsys.sup, opxuas.sup, odbsrv.sup or ServerConfig.xml needs admin rights and a restart: hand it to the user (skill portal-setup, task change-setup-file.md).
  • The same applies to dbc.sup (RDBMS data exposure). SQL Server changes (mixed mode, logins, jobs) are on another system: only with the user's and the SQL Server owner's agreement.
Task File Status
OPC UA client to an OPC UA server (sample: loopback to CI Server's own server): line, station, subscription, points, certificate exchange, node IDs, browse via dataset tasks/opcua-client.md verified
Make CI Server data available to OPC clients (OPC visible / Read / Write); CI Server OPC UA server endpoints, node IDs, certificates tasks/opcua-client.md §1, §5 verified (UA); DA/A&E from docs
Read-only checks: ACCESS processes, ports, OPC UA server config and PKI, ODBC server state tasks/access-checks.md verified
OPC DA / A&E client and server, DCOM, DCOM tunnelling L45 summary §3–§5 from docs (DA loopback not allowed)
ODBC with SimbaClient L45 summary §1 from docs; ODBC server not running on the test system (ISS-008)
OPC UA alarms (external alarms), methods, PubSub L45 §6, E20 §2–§4 from docs
RDBMS data exposure to SQL Server: SQL login, dbc.sup DEM_CONNECTION, DATA_EXPOSURE_DF (filter syntax), item aggregation interval, checks, table behaviour, SQL-side retention tasks/rdbms-exposure.md tested in R1.05 only (ITEM_VALUES); ITEM_HISTORY / ITEM_INPUTS not tested