Migration to GLOBAL - Frontend configuration
Supports Markdown: bold, italics, code, lists, links. Auto-saves.
No AI notes yet.
📂 Activities for this Item
➕ Add Activity
Open Activities
No open activities.
Service Requests / Work Orders
RFS-1-13005306146
Service Request
WO-RFS-1-13005306151
iNeed Text
Defined per context on the Taxonomy page.
Normalized time tracking
Last 30 days
Logged:
0:15
· Normalized:
0:15
2026-07-23
Day total:
0:15
Normalized (1) ·
0:15
-
Migration to GLOBAL - Frontend configurationLogged: 0:150:15
Time entries
0:15
-
Migration to GLOBAL - Frontend configurationVerified during cutover (2026-07-02) that the existing DPKO frontends (dfs-webapp-02, dfs-webapp-52) can reach the new GLOBAL backend (telrd-p-db-01, 10.130.72.21) directly — firewall path and DB user grant (radius) were already in place, no cybersec changes or approval needed. Repointed both frontends' main.php DB host from the old DPKO backend to the new GLOBAL backend (10.130.72.21), restarted httpd, confirmed working via Netscaler. Since the frontend can talk to GLOBAL directly, migrating the frontend app itself is unnecessary. Ticket closed.0:15 · 10:55
Meeting Notes (Project / Context)
Select a meeting to preview details.
Templates
Attachments
No attachments yet.