Found 18 results for "manual topics indexes"

The search executed in 0.001 seconds

Branches / Custom Indexes

Custom Indexes Cloud CMS internally maintains indexes to improve the speed of your data lookups across all data store types. In most cases, there is no need to concern yourself with these as they deliver optimal performance. With respect to content repositories, however, Cloud CMS allows you to define custom database indexes on a per-branch basis. These custom indexes add to the default set that Cloud CMS automatically maintains. Each branch and/or snapshot maintains its own "tip" collection tha

Score: 17.645605

Mitigating the OWASP Top 10

An explanation of how Cloud CMS addresses each of the Top 10 OWASP topics: Mitigating-the-OWASP-Top-10.pdf

Score: 7.87638

Query

Query Cloud CMS provides SQL-like, structured query for all of your content. The platform uses MongoDB under the hood to store the JSON for your content. MongoDB offers a powerful, unmatched query engine so that you can execute complex lookups of your content to support both your editorial and runtime application needs. The platform also offers "composite" query operations which let you layer MongoDB queries on top of Elastic Search DSL searches and traversals around node objects. Cloud CMS auto

Score: 7.2138596

Actions / Start Workflow

Start Workflow ID: startWorkflow Starts a workflow with the given node placed into the payload. Configuration Property Type Required Default Description model text true The ID of the workflow model to be used. swimlanes object false Identifies principals to be assigned into workflow swimlanes. The structure is: { "swimlane1": ["domainId1/principalId1"], "swimlane2": ["domainId2/principalId2"] } runtime object false Allows for manual specification of runtime properties including applica

Score: 6.6986904

Features / Indexable

Indexable QName: f:indexable Informs a node of how it should be indexed. Cloud CMS maintains multiple indexes including a search index, a database index and special indexes for things like path-based retrieval. By default, all n:node instances have the f:indexable feature applied to them. The default behavior is for search to be enabled and for search-indexes to be updated synchronously upon a write. Nodes that are indexed for search will take a little extra time on write (create or update) sinc

Score: 6.652189

Application Server / Services / Broadcast

Broadcast The Broadcast service is responsible for relaying messages to members of the application server cluster. It provides an essential publish and subscription service so that application server members can broadcast messages, receive messages and subscribe to topics and events that occur throughout the system. Essential Configuration { "broadcast": { "enabled": , "type": "", "config": { ...configuration } } } There are two

Score: 6.1573853

Docker / Maintenance / Upgrades

Upgrades This document provides technical guidance for upgrades. Upgrade to Cloud CMS Version 3.2 The Elastic Search version in this release has been updated from 1.7.1 to 6.2.4. Steps to follow to set up Docker 3.2: Download the Docker release 3.2 here. Download the Zip or Tar file of Elastic Search 6.2.4 here and then Unzip the package. Unzip the Docker release package, Create a new folder and paste the kit you use from the package. You can also replace your existing kit with the new release's

Score: 5.66521

Branches

Branches Cloud CMS stands apart from just about every other content management product on the market in that it offers a versioning model that is based around changesets. It is inspired by Git or Mercurial and provides a changeset versioning system that captures every touch - every create, update or delete - that you make. Nothing is ever lost. Every data operation is fully transactional with every transaction payload is fully captured into its own changsets. Transactions span multiple documents

Score: 5.3321066

Search

Search Any content you put into Cloud CMS is automatically indexed for full-text and structured search. This lets your editorial teams instantly search for content and find the things they're looking for. Under the hood, Cloud CMS uses Elastic Search and makes available to your editorial users and developers the full syntax of the Elastic Search Query DSL. This allows you to execute simple searches as well as more complex queries that take into account term and phrase matching, nested operations

Score: 4.7716603

Modules / Create a Module / Actions

Actions Cloud CMS provides a large number of actions that can be bound to links sections within configuration blocks. This allows you to customize dropdowns, button toolbars and action links at various places within the user interface. It also provides a way for you to override action implementation classes for your own users. For a list of these actions, see Actions on the lower left-hand menu. account change-password addon install-addon uninstall-addon applications delete_applications new_appl

Score: 4.529837

How do I search for nested content?

Cloud CMS maintains two indexes that are of interest for finding things. The primary index is the MongoDB index - against which you can run any query you can dream up using the MongoDB DSL. The secondary index is the Elastic Search index - against which you can run any search you can dream up using the Elastic Search DSL. For information all kinds of really powerful stuff you can do with this, see: https://www.cloudcms.com/documentation/content-services/query.html https://www.cloudcms.com/docume

Score: 4.1138616

User Interface / Locking

Locking Cloud CMS locking is a "data lock" approach which is a transactional lock is taken out when the write of multiple documents begins. This is a transactional lock in the sense that it blocks other write operations against those documents and fails entirely with rollback if any of the documents fail individually. We have transactional writes for multiple documents. We have a changeset-driven versioning model where each transaction writes onto it's own changeset. N number of documents may wr

Score: 4.0842752

What is the reason for "Failed to index node"?

If you scan your log entries and see "Failed to index node", this indicates that Elastic Search failed to update its index for a node. Cloud CMS tells Elastic Search to updates its index whenever a node is created or updated. When a node is deleted, Cloud CMS tells Elastic Search to remove the node from its index. This error message means that Elastic Search failed to update the index and therefore the index wasn't updated. If you open up the error, you may see further information that indicates

Score: 3.6210618

API / Data Types / Changeset

Changeset Type changeset Datastore Type repository Supports authorities, permissions, transfer In this sense, a branch can be thought of as a stack of changesets. There is a root changeset (where the branch starts) and a tip changeset (where the branch ends). Everything in-between constitutes the changeset history of the branch. This portion of the API therefore is largely for advanced users. The Cloud CMS API lets you dig in and poke around at the changeset history of branches to do things like

Score: 2.9187982

Releases

Releases Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team the ab

Score: 2.4921129

User Interface / Releases

Releases Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team the ab

Score: 2.4921129

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: 1.4834822

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: 0.8318252