# 9. Advanced

Deeper configuration for operators who are comfortable editing files and understanding cloud uploads. Everyday tasks still belong in the Dashboard, Folders, and Settings chapters.

# Configuration files

Beside the executable you will find:

File	Role
`appsettings.json`	Base defaults
`appsettings.Production.json`	Production overrides (typical for the Windows service)
`appsettings.Development.json`	Local / console development

The service reads the environment from DOTNET_ENVIRONMENT or ASPNETCORE_ENVIRONMENT (default Production when installed as a service).

Edit carefully. Keep a backup. Restart the service after changing these files.

# WebMonitoring port and binding

Default dashboard port is 55000, often bound to localhost.

If the service is running but the browser cannot connect, Windows may need an HTTP URL reservation for the service account — see Troubleshooting.

Changing the port requires updating config and any URL reservation / firewall rules.

# S3 / Totum presigned URL settings

Uploads go through Totum’s Presigned URL service and then to S3. Production config typically includes a PresignedUrlClient section and provider settings under:

Plugins:FileTransferCoordinator:Providers:S3

Important ideas (names may vary slightly by version):

Setting	Purpose
Base URL	Presigned URL API endpoint
API key	Authentication to that API
Default bucket / region	Where objects land if not overridden
Multipart threshold	Files at or above this size use multipart upload
Multipart part size	Size of each part
Multipart resumption	Resume large uploads after crashes
Timeouts	Must be long enough for large files

Folder configurations supply bucket and prefix per folder; they must be consistent with what your credentials allow.

# Large files and crash recovery

For large files, TotumService can:

Split uploads into parts
Persist progress
Resume after a service restart

If an upload stalls for many hours with no progress, stale multipart uploads may be aborted (configurable “stale hours”). That is intentional cleanup, not random data loss of completed objects.

Operational tip: for big files, watch Active Transfers and Database Explorer rather than assuming failure after one minute.

# Unity / media monitoring

Separately from folder monitoring, Media Monitoring can locate Unity persistent data (for example mediaitems.json / metricsitems.json) under user profiles. Media Upload Processor watches those files for changes.

These paths are influenced by company/product names in config (TotumService / MediaMonitoring sections). Tune them when devices use non-default Unity company or product names.

# Concurrent uploads and retries

Two layers matter:

Folder monitor — how many folder-originated uploads at once; stability wait; folder-level retries
Transfer coordinator — global concurrent transfers; coordinator retry policy

Raising concurrency speeds throughput but increases load on disk, CPU, and network. Change one knob at a time.

# Logging

Dashboard — recent buffer
Log files — under logs\ when file logging is enabled
Windows Event Log — Application log, source TotumService (production)

Increase detail temporarily when diagnosing, then return to normal levels so disks do not fill.

# Security notes for operators

Treat appsettings.Production.json as secret (API keys).
Prefer least privilege if you move off Local System.
The dashboard is local by default; exposing it on the network requires deliberate security (TLS, auth, firewall) — not covered as a turnkey feature here.
Delete after upload permanently removes local files — train staff accordingly.

# API access

Swagger UI: http://localhost:55000/docs

Useful for automation and support, not required for normal folder setup.

# Next step

Troubleshooting →