System jobs and run history only — inventory / host-facts crawls when registered.
| Job id | Next run | Trigger | Function | Source |
|---|---|---|---|---|
Open this tab to load jobs… | ||||
| Run id | Job id | Scheduled (UTC) | Finished (UTC) | OK | Summary |
|---|---|---|---|---|---|
— | |||||
| Name ⇅ | OS ⇅ | Version ⇅ | Last Logon ⇅ | Status ⇅ |
|---|
| Name ⇅ | Type ⇅ | SQL ⇅ | Env ⇅ | CST ⇅ | Cert expiry ⇅ |
|---|
1 — Dev drop — available versions
Devs drop release zips here. Helix lists this folder via UNC from eci-prod-data, then you pick a version to copy onto eci-prod-data. If stage finds a problem, use Remove from eci-prod-data to delete that release and its prepare slots before importing a fix.
Naming: a release zip or folder must start with R and at least six digits, for example R20261106.zip or R20261106_WebAPI.zip. Helix cannot download a zip named any other way (such as 20261106_WebAPI.zip); ask the dev to rename it on the drop.
- Dev drop (UNC)
- —
- Same path by IP
- —
| Version | Name | Type | Size | Modified (UTC) | |
|---|---|---|---|---|---|
| Loading available versions from dev drop… | |||||
2 — Refresh stage databases
Restore production database backups onto stage SQL, then run the sanitize script. Run manually before a stage code roll when databases need to match production.
—
3 — Target environment
Choose stage or production before you prepare components and roll. The same environment applies to prepare (step 4) and roll (step 5).
—
—
4 — Extracted builds (on eci-prod-data)
After download, web/service folders are published under E:\Powershell\Code as - new prepare slots. SQL and CDN stay in the version extract folder — select the release and use the SQL/CDN checkboxes, then prepare at the bottom of this section.
—
Release folders
| Version | Manifest | Prepared | Rolled | Components | Modified (UTC) | Actions |
|---|
Release components (SQL / CDN) — from extracted version folder
Pick the active release above. SQL copies scripts to C:\temp\{version} on Prepare and runs *.sql in numeric order on Roll. CDN merges CDN_update into the image server on Prepare.
| Component | Source folder | Status | |
|---|---|---|---|
| Select a release folder with a manifest. | |||
Prepare slots (- new on eci-prod-data) — select components to stage
| Folder | Modified (UTC) |
|---|
Local zip copies
| File | Size | Modified (UTC) |
|---|
5 — Roll prepared code
After step 4 completes, check what is prepared on each card below. The selected card is what Roll prepared code rolls; click the other card to switch. Roll now or schedule for later.
Prepared for roll
Prepared components are tracked on eci-prod-data. Clear only updates that tracker; use it when - new folders were removed on the servers by hand.
This rolls to PRODUCTION. Components about to roll:
—
Type PRODUCTION to confirm.
Scheduled rolls
Pending rolls run automatically at the scheduled local time. Recent completed rolls are kept for reference.
| Status | When (your time) | Target | Components | Scheduled by |
|---|
Run Jenkins
QA
Runs the Jenkins pipeline eci.EcinteractivePlus - Post Deployment Sanity - Pipeline against stage or production without deploying anything. Helix starts the pipeline, polls Jenkins until it finishes and shows the result below. Rolls and rollbacks do not run it.
| Environment | Result | Jenkins build | Duration | Run by | When (your time) |
|---|---|---|---|---|---|
| Loading QA results… | |||||
Roll back to previous version
Each roll leaves the previous version beside the live folder as - old.
That copy survives only until the next roll of the same component replaces it, so
check first. Rolling back stops the service or IIS on the host, swaps the folders,
and starts it again — the rolled code becomes the new - old, so you can
re-apply it.
| Component | Server | Live path | Previous version |
|---|
Run logs
Written on the portal host by each prepare and roll, newest first. Download one to read it locally — the whole run is in there, including what the summary above collapses.
| When (your time) | Phase | Environment | Size |
|---|
Application services
Catalog from deploy config. Most components restart via IIS (W3SVC); OMS and OMS+ use their Windows services.
| Component ⇅ | Env ⇅ | Server ⇅ | Code path ⇅ | Service / IIS ⇅ | Status ⇅ | Startup ⇅ | Actions |
|---|---|---|---|---|---|---|---|
| Loading service catalog… | |||||||
Upload a .config, .json, or .txt file
onto the live folder for any catalog service and keep a timestamped backup.
Recycle IIS or restart the Windows service only when you check that box.
Rollback lists those backups and restores the one you pick.
Select environment and service.
Only .config, .json, or .txt. The server file name matches the upload.
Sends to you when the update or restore finishes. Add more addresses, comma-separated.
Download current config
Reads the live file from one server and saves it to your machine. Nothing on the server changes and no service is touched. The contents are not displayed here — open the file locally. Downloads are recorded in the audit log with the file, environment and server.
| File | Modified (your time) | Size |
|---|
Upload one or more .pfx files. Helix reads each certificate here, finds the
HTTPS bindings that match its hostnames from the websites inventory, and shows you exactly
what would change before anything is sent. Bindings are never created — a certificate whose
hostname has no binding is reported instead of guessed at.
File names are not used — the hostnames come from inside each certificate.
Sends to you when the run finishes. Add more addresses, comma-separated.
—
Search for a site, then apply. Confirm before IIS, DNS, or allowlist changes.
Virtual directories
301 to shop.ecinteractiveplus.com/####. Confirm the folder in the modal.
| Path | Live where | Actions |
|---|---|---|
| Open this tab to load catalog VDs. | ||
Custom sites (CNAME)
CST CNAMEs → ec-echo-cst.ecinteractiveplus.com.
| Site | Points to | Live where | Actions |
|---|---|---|---|
| Open this tab to load DNS records. | |||
Punchouts
Same Workers KV allowlist the Worker already reads. Helix only adds, lists,
searches, or deletes process IDs. Paste IDs from the site query (or a CSV with
a ProcessId column).
| Process ID in allowlist | Actions |
|---|---|
| Open this tab to load the allowlist. | |
Website
—
Server
—
| Started | Window | Requested by | Status | |
|---|---|---|---|---|
| Loading… | ||||
