AggreGate's user interfaces can work under any operating system and in all popular browsers. However, there are several cases when that's not enough:
- If you want to pull data from the AggreGate core and inject it into your existing corporate portal which already serves as a front end for many other systems, such as ERP or CRM.
- When you want something unusual to be displayed in the user interface but don't want to deal with developing custom UI components in the Java programming language. This is a rare case since AggreGate widgets provide hundreds of highly customizable components that can be combined into very complex hierarchical layouts, as well as the UI component SDK.
In these cases, you can entirely cease using the AggreGate Unified Console and Web Desktop as operator interfaces, reserving them solely for system administration.
Your corporate portal can connect to AggreGate servers directly. It will load necessary data to enrich its dynamic web pages and initiate control actions upon the portal user requests.
Technically, there are several ways of integration:
- If your portal is based on the Java platform, AggreGate Java SDK can be used to communicate with the servers.
- For portals based on .NET technologies (such as ASP.NET), AggreGate .NET API can be used.
- In all other cases, e.g. for corporate sites based on PHP or similar technologies, web services and other supported protocols do the trick, allowing communicating with the server by using standards implemented for almost all development platforms.