Development

Can anyone develop AOP Modules?

Yes, in principle. AOP uses standard protocols and the SDKs are publicly documented. However, before a Module can connect to a productive WinGuard system, a few prerequisites must be met:

1. Module code: A globally unique identifier in the form companyName.ModuleName, assigned and managed by Advancis.
2. Per-module key pair: For each Module, Advancis provides a dedicated private/public key pair. The private key remains in the Module (for example, in the source code), and the public key is contained in that Module’s LIC file.
3. Module license (LIC file): An XML-based license file (.lic) that describes what API functions the Module is allowed to use. In production, this Module license must be signed by Advancis. During development, an unsigned LIC file can be used as long as the WinGuard instance has a developer license enabled.

→ See Licensing for LIC file structure and details.

What is an AOP App, and what kinds of clients are there?

In AOP terminology:

• The AOP App (e.g., a WinGuard station) acts as the server. It provides the IPC bus and hosts the core API services.
• Any software that connects to the AOP App is a client. A client that only consumes the API without registering its own services is called a pure client.
• A client that also registers and provides its own services is called an Extension (or component in the full sense).

Common types of Extensions/clients:

→ See Component Model and Device Adapter Concepts.