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
  2. Initial set up

Install package

PreviousAppControl UserNextConfigure system

Last updated 4 months ago

AppControl is delivered as a Mendix application package (.MDA file). To use AppControl you will need to download the package and deploy it to a licensed Mendix Cloud node or a Mendix server running in your private cloud.

Step 1: Prerequisites

Before installing AppControl make sure you have the following:

  • A licensed Mendix Cloud (minimum size 'S', preferably size 'M') or private cloud node where you can deploy the AppControl package.

  • If you have firewalls between the node where you will deploy AppControl and the Internet, make sure the following ports are open:

    • https://teamserver.sprintr.com:443

    • https://svn.home.mendix.com:443

    • https://git.api.mendix.com:443

    • https://deploy.mendix.com:443

    • https://support.bluestorm.io:443

  • A registered account in the Blue Storm Customer Portal. This will be provided to you by Blue Storm.

Step 2: Download package

Login to the Blue Storm customer portal (), browse to 'Releases', and download the latest release. AppControl is delivered as a Mendix MDA package file.

Step 3: Deploy package

Depending on your hosting platform, upload the AppControl MDA package to your Mendix server. Afterwards, perform the steps below:

  1. Configure the following constants:

  • MxOM_Core.EncryptionKey : Use a random 32 character key, and never change it.

  • MxOM_Core.APIUser : API user name provided by Blue Storm.

  • MxOM_Core.APIPassword : API password provided by Blue Storm.

  • MxOM_Core.AuthenticationService : The authentication service to be used for logging into MxOM. Possible values are:

    • LOCAL : Local user accounts only.

    • MENDIX_SSO : Use Mendix SSO for authentication.

    • SAML : Use SAML for authentication.

  • Logging.LogHistoryDays : 60

  1. Configure the following custom runtime settings:

    • com.mendix.core.ProcessedTasksCleanupAge : 86400000

  2. Enable all scheduled events that start with ‘MxOM’ and the event 'Logging.CleanupDataLogging'.

  3. Start the server and login using MxAdmin.

  4. If you configured MxOM to use SSO for authenticating users, configure SSO from the Administration > Accounts page.

  5. Create a new administrator user and give this user the ‘PlatformAdministrator’ role. Login as the new user.

https://support.bluestorm.io/