Found 197 results for "application-server usage configuration"

The search executed in 0.0 seconds

Docker / Configuration

Configuration API Server Encrypting Properties

Score: 13.776322

API / Data Types / Billing Provider Configuration

Billing Provider Configuration Type billingProviderConfiguration Datastore Type application Supports authorities, permissions, transfer If this sounds familiar, it's because it's exactly what Cloud CMS uses to supports its own subscription plans for Cloud CMS customers. Just as we bill our customers for metered usage of the platform, you are free to pass those costs downstream to your own clients. And you can use the very same technical capabilities and facilities to do so. Cloud CMS offers bill

Score: 11.894726

Docker / Configuration / API Server

API Server The Cloud CMS API Server is a Java application that launches inside of a Java Servlet Container. The Java application surfaces a REST API as well as backend services and DAOs to support connectivity to Mongo DB, Elastic Search and a slew of Amazon services including S3, SNS, SQS, Route 53, Cloud Front and more. Properties File Cloud CMS is primarily configured via a properties file that is auto-detected and loaded when the underlying Spring Framework starts up. This properties file is

Score: 9.968005

Docker / Maintenance / Health Check / Load Balancers

Health Check / Load Balancers In a production configuration of Cloud CMS, you will want to have a load balancer (LB) in front of both your API and UI clusters. You should have one load balancer for the API cluster and one load balancer for the UI cluster. Each load balancer is responsible for receiving requests from the outside world and efficiently distributing those requests to the N servers that make up each cluster. Load balancers use a number of strategies to try to determine which servers

Score: 7.2650566

Command Line

Command Line The Cloud CMS command-line client gives developers a way to work with their Cloud CMS tenant projects, applications, data stores and other resources from the command line. The CLI (command-line client) is a Node.js based command line tool that is very easy to use and available at no charge. Note: A valid Cloud CMS subscription is required to connect to Cloud CMS with the command-line client. This subscription can be a paid subscription or a free trial account. Getting Started To get

Score: 6.274147

Application Server / Authentication / Adapters / Default

Default The default request adapter parses simple header and cookie information. It is generic adapter that can be used to interrogate the most common elements in an HTTP request. Configuration Here are all of the properties that may be configured: { "adapters": { "{adapterId}": { "type": "default", "config": { "header": "{headerName}", "cookie": "{cookieName}", "trusted": false } } } } Th

Score: 5.6639075

Cloud CMS Architecture

Cloud CMS has two clusters that we run for customers who host apps with us. One cluster is for the "app server" tier (* and the other is the "API" tier ( The app server cluster consists of Node.js servers, and the API is a Java-backend that is stateless and implements the full REST API: As such, the API doesn't manage connections directly. Any invocation to it is a one-shot where each request contains everything needed to assert the user's identity and proceed wit

Score: 5.2000237

API Max Heap recommendation

What is the recommended Xmx value for running the API service? The 2GB setting on the On-Premise "quickstart" distribution is a default for development usage. In production, we recommend putting as much memory as you can. Essentially, the API should use as much memory as is allocated to the API docker container. We usually ask customers to consider an M class large instance type (something on the order of 7.5GB of RAM per API). The UI can use considerably less. For the UI, a 2GB allocation is fi

Score: 4.9840713

AWS loadbalancer healthchecks

For AWS LB healthchecks, we recommend the following path off the API: /healthcheck This route hands back a 200 if the API server is healthy. It determines whether it is healthy by checking a few statistics such as the amount of free memory, the amount of free disk space, network connectivity, file handle usage, CPU utilization and more. If it returns a non-200, then that serves as a signal that the server is in some sort of degraded state and should be rolled over (which elastic scaling groups w

Score: 4.801844

Application Server / Authentication / Adapters / JWT

JWT The JWT request adapter is similar to the default adapter in that it lets you pull a JWT token from either a named header or a cookie. JWT stands for JSON Web Token. JSON Web Tokens are an open, industry standard RFC 7519 method for representing claims securely between two parties. You can read more about them at [](the official JWT web site). Configuration Here are all of the properties that may be configured: { "adapters": { "{adapterId}": { "type": "jwt",

Score: 4.752415

Content Modeling / Behaviors

Behaviors Cloud CMS lets you wire in behaviors behind your content models so that rules automatically execute when your content is touched. Content editors work with simple forms to create content that conforms to your defined content models. When that content is created, updated or deleted, it automatically triggers policies (or events) which you use to bind in custom behaviors. In this way, the developers can wire up behaviors and the editorial team never needs to know about it. Furthermore, b

Score: 4.2993126

Application Server / Services / Cache

Cache The Cache Service is responsible for providing an application server cache that all processes, whether local or distributed, have access to for non-transactional caching. Objects stored in the cache are eventually available to other members of the cluster (if there are any), no matter whether running on the same server or on other servers in the cluster. Modes The Cloud CMS Application Server can run in one of three modes: single node cluster multiple nodes (on a single process) sticky-clu

Score: 4.247531


Auditing Cloud CMS provides a built-in audit system that automatically logs the activity between users and content through API service methods. The audit system produces an audit trail consisting of audit records that document the access of every user, content object and service method. Audit records are created automatically if they are enabled for your tenant and for the repository against which the operation occurs. Auditing is only available for on-premise, Docker customers. How to Enable Au

Score: 3.9421344

Single Sign On (SSO)

Single Sign On (SSO) Cloud CMS offers Single Sign On (SSO) Enterprise support that provides ways for users to log in using their existing business accounts. It makes it possible for your users to authenticate to Cloud CMS without having to remember or type in their credentials every time. Cloud CMS offers two Enterprise SSO features - SAML 2.0 and JWT. These are two popular SSO mechanisms that work with many commercial and open-source identity providers including: Microsoft Active Directory Fede

Score: 3.800393

Docker / Maintenance / Repository Compression

Repository Compression Cloud CMS content is stored within a Repository. A Repository differs from other types of data stores in that it provides Copy-On-Write mechanics using Changeset-driven versioning. Every time you create, update or delete content within a repository, those adjustments are written onto a new Changeset. Changesets are layered automatically and provide a stack of differences that, over time, allow you to scroll back to any moment in time to see a perfect capture of every modif

Score: 1.9853791


Authentication Cloud CMS supports authentication via the industry standard OAuth 2.0 protocol. OAuth 2.0 is a well-recognized standard that enables client code to connect to Cloud CMS in a secure and safe fashion. This means that authorization can be achieved in such a way that client and user credentials (secret keys) are never publicly exposed. Channel-level encryption is provided by HTTPS and HTTP POST payloads are utilized to avoid exposure of credentials via request parameters or logging fa

Score: 1.808845

Modules / Create a Module / Config Service

Config Service The configuration service evaluates a series of conditional configuration blocks and determines which blocks to keep in composing a final configuration document for the user interface. The configuration document consists of blocks that define JSON structures that are to be merged into a final JSON configuration that powers the user interface. The configuration service executes two phases - evaluate and merge. It essentially looks like this: [block1] --> --> [config1]

Score: 1.7370783

Application Server / Services / Config

Config The Configuration Service loads JSON rules for the current application and composes them into a JSON configuration document that is served back. The Configuration Service considers JSON rules that are defined at application level as well as the project, platform and user level. { "config": { "remote": { "enabled": , "appKey": "" } } }

Score: 1.6939518

User Interface / UI Views

UI Views Customized changes to the user interface configuration can be introduced through the use of UI Config documents. UI Config documents are JSON documents that contain one or more configuration blocks. The UI Config configuration blocks are loaded after the standard configuration document and therefore have the opportunity to either extend or override the base configuration. UI Configs are scoped either to the platform or to the project. As such, you can use UI Config objects to customize

Score: 1.6577653

Modules / Create a Module / Bindings / Menus - Manage Context

Menus - Manage Context The manage-context key defines the left-hand menu options for the platform and project management pages. To populate the manage-context section, your configuration snippet should look like this: { "manage-context": { "items": [] ] } Default Configuration The default UI configuration for the Platform management pages looks a bit like this: { "manage-context": { "items": [{ "key": "platform/manage", "title": "Manage Platfor

Score: 1.6479672

Application Server / Services / Notifications

Notifications The Notifications service is responsible for receiving messages from the outside world. These are frequently transmitted via a message queue or broker and signal the cluster that it should take some action to update its state. This may include things like invalidating caches or re-syncing content. Essential Configuration { "notifications": { "enabled": , "type": "", "configuration": { ...configuration } } } There ar

Score: 1.6401231

Releases / Actions

Actions You can optionally configure Actions that execute when a release goes live. Some actions support variables. The following variables are always available: release - a JSON object of the release along with all metadata about the release releaseId - the ID of the release object branchId - the ID of the release branch snapshot - the ID of the snapshot that was generated after merge The following Actions are supported: Send Email Fire Web Hook For each action, you need to provide a configurat

Score: 1.6377405

Modules / Create a Module / Bindings / Menus - Workflow Context

Menus - Workflow Context The workflow-context key defines the left-hand menu options for the Workflow pages. To populate the workflow-context section, your configuration snippet should look like this: { "workflow-context": { "items": [] ] } Default Configuration The default UI configuration for the Workflow pages looks a bit like this: { "workflow-context": { "items": [{ "key": "workflow", "title": "Workflow", "order": 1000,

Score: 1.6285691

Forms / Fields / CK Editor

CK Editor ID: ckeditor The ckeditor field renders the popular CKEditor HTML control. This offers a fully-featured HTML editor on top of a string schema type. It is ideal for situations where you wish to provide your editorial team with the ability to edit HTML visually and offers a large range of plugins and behaviors that you can customize. For basic information of what is possible in terms of configuring this field type, please view the Alpaca Forms documentation for the CKEditor field. Config

Score: 1.6273109

Modules / Create a Module / Bindings / Menus - My Preferences Context

Menus - My Preferences Context The mypreferences-context key defines the left-hand menu options for the My Preferences pages. To populate the mypreferences-context section, your configuration snippet should look like this: { "mypreferences-context": { "items": [] ] } Default Configuration The default UI configuration for the Platform my preferences pages looks a bit like this: { "mypreferences-context": { "items": [{ "key": "platform/mypreferences",

Score: 1.6246572