AppControl Docs
  • Introduction
  • Overview
    • Features
    • Product architecture
      • AppControl Repository
      • Policy Checks
    • Initial set up
      • AppControl User
      • Install package
      • Configure system
      • Add apps
      • Add users
      • Give permissions
    • User Roles & Access
    • Getting Started
      • Platform Administrator
      • App Owner
      • App Administrator
      • Developer
  • Dashboards
    • Platform
    • Alerts
    • App
      • Log Rule
    • Policies
      • Compare Revisions
    • Releases
      • Create Release
    • Tasks
      • Task Assignment
      • Task Details
    • Insights
      • Components
      • Reports
      • Users
      • Logs
  • Administration
    • Policies
    • Pipelines
      • Approval
      • Backup
      • Build
      • Call API
      • Check Policy
      • Deploy
      • Deploy Configuration
      • Notification
      • Start / Stop
    • Tasks
    • App Groups
    • Access Groups
    • System
      • Accounts
      • Notifications
      • System Status
      • System Logs & Tools
      • System Configuration
      • Repository
        • Log Solution
      • Product License
      • Management API
      • Mendix Configuration
    • Feedback
  • Checks
    • APIs
      • Published APIs must use authentication
    • App
      • Project security level
      • Project security enabled
      • Demo users enabled
      • Anonymous users enabled
      • Strong password policy
      • Default admin username changed
      • Anonymous user access restricted
      • Default admin user restricted
      • Use strong hash algorithm
      • Check user role security for consistency
      • Restrict users to a single session
      • Perform strict page URL checks
      • Project naming standards
    • Components
      • Components with vulnerabilities
      • Mendix runtime version age
      • Mendix runtime support status
      • Non platform supported components
      • Max component age
      • Average age components
      • Use latest version of Marketplace module
      • Use latest version of Marketplace widget
      • Use latest version of Mendix
      • Limit number of Java libraries
      • Limit number of widgets
      • Use minimum Mendix runtime version
    • Constants
      • Do not expose constants to client
    • Development
      • Last commit to production
      • Last commit to project
      • Project documentation standards
      • Project organization standards
      • Project logging standards
    • Domain Model
      • Default member access rights restricted
      • Use read only attributes in XPath constraints
      • Anonymous users can only change own data
      • Anonymous users cannot change unlimited length strings
      • Domain model standards
      • Anonymous user access restricted
      • Naming standards - Domain Model
      • Documentation standards - Domain Model
    • Enumerations
      • Naming Standards - Enumerations
    • Microflows
      • Incorrect date format
      • Incorrect empty string check
      • Empty variable used
      • Apply entity access when generating documents
      • Use inherited entities from System module
      • Web service calls with templates should be escaped
      • Naming Standards - Microflows
      • Logging Standards - Microflows
      • Documentation Standards - Microflows
    • Pages
      • Attributes in data views should be editable
      • Naming Standards - Page Flows
      • Documentation Standards - Pages
  • Support
    • Docs
    • Feedback
    • Tickets
    • Releases
    • System Status
    • User Details
Powered by GitBook
On this page
  1. Overview

Product architecture

PreviousFeaturesNextAppControl Repository

Last updated 2 months ago

AppControl is an add-on solution for organizations that use Mendix. AppControl enables organizations to manage large landscapes of Mendix applications based on centralized policies and standards.

Although the Mendix Platform provides many different features and services, organizations using Mendix at scale often have additional requirements that can't be met by the basic Mendix Platform offering. Additionally, for organizations that don't use the Mendix Cloud for hosting, most of the standard Mendix Platform features are simply not available.

AppControl is delivered as a Mendix application package (.MDA file). This package can be deployed to any Mendix server (public cloud or private cloud).

The illustration below shows the basic components of AppControl and how they communicate with each other:

  • AppControl. This is a Mendix application that you deploy to a licensed Mendix server. Blue Storm does not provide a Mendix license. You must install a AppControl product license that you purchase from Blue Storm. This server does all app monitoring and processing of app data.

  • AppControl Insights Repository. This is a web service provided by Blue Storm and is included as part of your AppControl subscription. This contains information about Mendix Marketplace components, Mendix runtimes, vulnerabilities, and log solutions. This service is called regularly by AppControl to update its list of known components and what their current status is.

  • Hosting Platforms. This is where you host your Mendix applications. Most Mendix customers use the Mendix Cloud, but this could also be your own private cloud hosted in Azure or AWS, or local hosting on Windows or Linux servers. AppControl polls hosting platforms for the list of hosted apps, environments, and their current status. AppControl supports commonly used hosting platforms, and it is possible for Blue Storm to develop connectors for custom clouds.

  • App Repositories. There is where you store your app project files. Most Mendix customers use Team Server, but this could also be your own private GIT or SVN server. AppControl scans your repositories for a list of revisions for each of your apps. Additionally, AppControl downloads and scans various project files to check if they are compliant with your policies.

MxOM Product Architecture
Drawing