ci-server-engineer/.claude/skills/portal-setup/SKILL.md
cliu 84181711b8 Add phase 4 CI Portal setup and Setup File Editor summaries, portal-setup skill
- Summaries of IM 36K10R10 (CI Portal Setup) and IM 36K10R20 (Setup File Editor),
  checked against the installed setup files and the Setup File Editor GUI
- New skill portal-setup: read a setup file, check web access for CI View,
  change a setup file safely (verified with a port change and restore)
- Manual vs software differences logged as ISS-012 to ISS-017; installed
  software taken as the reference

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-30 16:41:02 +10:00

39 lines
2.4 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
name: portal-setup
description: >-
CI Server R1.03 CI Portal, CI View and setup files. Use when the user wants to read, check
or change a setup file (.sup) or use the Setup File Editor, write setup file metadata
(!KEYWORD, !TAB, !ARG), choose between CI Portal and CI View, set up a CI Portal node
(dur.sup host node, copying displays), check the Remote Connect web page or web ports
(8080/8443), or tune the operator interface, Engineering Module or Edit Module
(jwuiisg.sup, jhmiset.sup, jwuiged.sup) and the WFL processes (wflidi, wfladi, wflcdi,
wflgdi, wfla_display), e.g. display cache time, flow control, alarm overview event types.
Sources IM 36K10R10-01EN and IM 36K10R20-01EN.
---
# CI Portal and setup files (R1.03)
Background: `knowledge/manuals/IM36K10R10-01EN.md` (CI Portal Setup: processes, CI Portal vs
CI View, every user-interface setup file and keyword) and
`knowledge/manuals/IM36K10R20-01EN.md` (Setup File Editor and metadata keywords).
Remote Connect installation and firewall: skill `installation-security`.
Rules:
- Run the `system-check` skill first.
- Reading setup files is always allowed. Changing one alters CI Server behaviour after the
next restart: follow the user's chosen way of working, back up the file first, and
confirm before restarting CI Server. In *prepare only* mode, write the changed file to
the user's chosen folder and give the deploy steps.
- Normally only the logon method needs changing in the user-interface setup files; treat
other changes as tuning.
| Task | File | Status |
|---|---|---|
| Read a setup file: active settings and keyword help | `tasks/read-setup-file.md` | verified (read-only) |
| Change a setup file safely (back up, edit, restart, verify, restore) | `tasks/change-setup-file.md` | verified |
| What the Setup File Editor shows for a file (tabs, fields, Changed status) | `tasks/read-setup-file.md`, R20 summary §2 | verified (compared in the GUI) |
| Login method / login control (moved to `dssana.sup`) | not covered yet (ISS-017) | — |
| Check web access for CI View (ports, Remote Connect page, `DEPLOY` folder) | `tasks/check-web-access.md` | verified (read-only) |
| Choose CI Portal or CI View; set up a separate CI Portal node | R10 summary §2–3 | from docs (needs a second node) |
| Operator interface does not show a changed display/item (cache) | R10 summary §1 | from docs |
| Write metadata for a custom setup file | R20 summary §3 | from docs |