Support
Product/vendor support
Luciad documentation indicates technical support and product update guidance through vendor/customer services channels.
Internal support model for CCR
L1 Support
- validate application reachability
- validate map loads
- confirm browser/network issues
- basic user access issue triage
L2 Support
- service endpoint validation
- Studio checks
- configuration review
- authentication and role mapping review
- logs and Actuator checks
L3 / Engineering
- Spring Security customization
- custom integration code
- performance tuning
- upgrade failures
- data model/service publication issues
CCR wording
Support responsibilities are split across application operations, service administration, and engineering escalation.
Example Section for “How Real-Time Works” in the CCR
In the LuciadFusion–LuciadRIA solution, real-time behavior is not handled by a single platform toggle. LuciadFusion provides the secure publication and management of geospatial services and internal asynchronous event handling, while LuciadRIA implements browser-side live visualization using application-driven refresh logic such as WebSocket-fed updates or repeated service/store queries.
Short CCR Summary Table
| Section | What to state |
|---|---|
| Architecture | Fusion server + Studio + service endpoints; RIA browser client; reverse proxy/HTTPS |
| Install | license, profiles, DB, datastore, app setup, connectivity validation |
| Configure | security, auth type, roles, service exposure, DB, threads, port |
| User Types | admin, data manager, consumer, anonymous/public |
| Integration | WMS/WFS from Fusion into RIA with sample code |
| Upgrade | backup, migrate YAML/config, validate DB and service compatibility |
| Monitor | logs, Actuator, endpoint health, Liquibase/db state |
| Support | L1/L2/L3 operational ownership and escalation |
| Real-time | RIA-side live updates; Fusion-side async service platform/event handling |
---