Sparx WebEA

Executive summary

WebEA is Sparx Systems’ browser-based, read-only access mechanism for viewing Enterprise Architect models through a web interface. It is intended to make selected EA repository content available to stakeholders who do not have the full EA desktop client.

WebEA should be distinguished from:

• Enterprise Architect — the modeling and authoring application.
• Pro Cloud Server — the server-side access layer that hosts or exposes EA repositories and provides services used by remote clients and web access.
• Prolaborate — a separate, richer web-based collaboration and visualization product from a third party.

Capabilities

Typical WebEA capabilities include:

• Browse published EA packages and model structures in a web browser.
• View diagrams, elements, properties, documentation, and relationships.
• Search and navigate model content without installing the EA desktop client.
• Provide stakeholder access to architecture, requirements, processes, applications, and design documentation.
• Use browser-based access for distributed teams and non-modeler audiences.
• Present a controlled, read-only view of approved repository content.
• Support links from documents, portals, or governance material into relevant model content, depending on the configured deployment.

WebEA is primarily a consumption and publication interface. It should not be treated as a full replacement for EA authoring, model governance, advanced analysis, or desktop-based configuration management.

Use cases

Architecture communication

Publish approved architecture views and supporting documentation to executives, delivery teams, and governance forums without distributing EA desktop licenses to every reader.

Requirements and traceability review

Allow business and delivery stakeholders to inspect requirements, dependencies, design decisions, and traceability relationships through a browser.

Project and delivery collaboration

Give project participants access to current model content while modelers retain control of the repository and authoring process.

Operational and service documentation

Expose application, service, infrastructure, ownership, and dependency views to operations or service-management teams. WebEA can complement—but does not itself replace—a CMDB or CSDM platform.

External or distributed stakeholder access

Provide controlled access for geographically distributed users, contractors, or review boards where installing EA is impractical.

Architecture review and approval support

Use browser-based diagrams and documentation during design reviews, portfolio reviews, and architecture governance meetings.

Product and pricing position

Is WebEA a separate product?

WebEA is generally positioned as a component/capability associated with the Sparx web-access ecosystem, rather than as a standalone SaaS service. It is not equivalent to a cloud subscription where Sparx operates the customer’s repository as a managed service.

Its availability and licensing are tied to the customer’s Enterprise Architect repository and Pro Cloud Server deployment/licensing arrangement. Confirm the current commercial entitlement with Sparx Systems or an authorized reseller because packaging and licensing can vary by Pro Cloud Server edition, release, and contract.

Does it come bundled?

Do not assume that an EA desktop license automatically includes WebEA. In a typical deployment, the required components may include:

1. Enterprise Architect licenses for model authors and administrators.
2. A repository database supported by EA and PCS.
3. Pro Cloud Server, with the edition/license that enables the required web access capability.
4. Web server/application configuration for the WebEA site.
5. Optional infrastructure, authentication, reverse proxy, TLS certificates, backup, monitoring, and support.

Public list pricing may not clearly separate WebEA from PCS licensing. Request a written quote that identifies:

• PCS edition and license quantity.
• Whether WebEA access is included or separately licensed.
• Any user, concurrent-user, repository, or deployment limits.
• Production, test, and disaster-recovery entitlements.
• Upgrade and support rights.
• Authentication or enterprise integration options.
• Professional-services and installation charges.

Requirements and prerequisites

Software and licensing

• A supported Enterprise Architect repository.
• A compatible Pro Cloud Server installation and license/edition.
• A WebEA-capable version of PCS and EA, verified against the intended deployment.
• Appropriate EA authoring licenses for users who create or maintain model content.
• A supported server operating environment for PCS and the WebEA web application.

Repository and model prerequisites

• Repository connectivity from PCS.
• A defined package structure and publishing boundary.
• Approved diagrams and documentation suitable for stakeholder consumption.
• Consistent naming, stereotypes, tagged values, and traceability conventions.
• A governance process controlling what is published and who can access it.

Network and infrastructure prerequisites

• Network reachability between the WebEA application, PCS, and repository database.
• DNS or a stable URL for users.
• TLS/HTTPS for production access.
• Firewall and reverse-proxy rules as required by the organization.
• Backup and recovery for the EA repository and configuration.
• Monitoring, logging, patching, and capacity management.

Identity and security prerequisites

• Authentication design: local, directory-backed, single sign-on, or another supported method.
• Authorization rules for repositories, packages, and users.
• Least-privilege administrative access.
• A decision on whether external users may access the service.
• Security review covering exposed diagrams, requirements, personal data, intellectual property, and model attachments.

Operational prerequisites

• Defined refresh/publication process.
• Test and production environments.
• Release and change-management procedures.
• Capacity planning for concurrent users and repository size.
• Support ownership for PCS, WebEA, the web server, database, network, and authentication.

Limitations and considerations

• WebEA is principally a web viewing/publication facility, not the full EA modeling client.
• Editing, advanced modeling, automation, and administration may still require EA desktop capabilities.
• WebEA does not inherently provide CMDB discovery, reconciliation, or CSDM governance.
• Browser exposure increases the importance of authentication, authorization, TLS, patching, and publication controls.
• The user experience and supported capabilities depend on the EA/PCS/WebEA versions and configuration.
• Product packaging and pricing should be verified directly with Sparx Systems because the available public information does not establish a universal bundle or price.

Comparison with alternatives

Procurement questions

1. Is WebEA included in the proposed PCS edition and license, or priced separately?
2. Are there limits on users, concurrent sessions, repositories, or environments?
3. Which EA, PCS, database, browser, operating-system, and web-server versions are supported?
4. What authentication and authorization methods are supported?
5. Is read-only access enforced, and what model elements or attachments can be exposed?
6. Can access be restricted by repository, package, or user role?
7. What is required for high availability, backup, disaster recovery, and upgrades?
8. Are installation, configuration, SSO, reverse proxy, and TLS services included in the quote?
9. What support and maintenance rights are included?
10. How does the proposed WebEA deployment compare with Prolaborate or a custom portal for the intended use case?

Bottom line

WebEA is best understood as a browser-based, read-only publication and stakeholder-access capability associated with Sparx Enterprise Architect and Pro Cloud Server. It is not SaaS, PaaS, or IaaS, and it is not a CMDB/CSDM integration product. Treat its licensing as PCS/EA deployment-dependent and obtain a current written quotation confirming whether WebEA is bundled or separately licensed.