Found 158 results for "api api content-services api content-services query"

The search executed in 0.0 seconds

API Keys

API Keys For information on API Keys, please visit the Cloud CMS - API Keys Developer Page.

Score: 102.7168

API

API The Cloud CMS API consists of an HTTP/HTTPS endpoint that uses OAuth 2.0 authentication. It supports both REST concepts and asynchronous data operations. You can access this API using any of our drivers as well as curl or any HTTP client library. Our API provides functionality that covers all aspects of content production, publishing and presentation. 100% of the functionality of Cloud CMS is accessible from the API, including: Content Models, Creation and Editing Workflow, Scheduled Publish

Score: 91.73698

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

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

Actions

Actions Cloud CMS provides an Action framework that lets you kick off Actions that perform content operations on your behalf. Actions are units of work that are typically fired off as a result of an event handler or listener. For example, you might register an Action that triggers when a piece of content is updated or when a workflow task transitions. The Action might do something like Send an Email or Fire off a Web Hook. The Cloud CMS Action framework aspires to provide complete units of work

Score: 33.64998

API / Tree

Tree Content that is organized into folders can be retrieved using the Tree API. The Tree API lets you pull back an entire path-based folder and file structure of content within a single API call. The API call lets you specify a root node, a maximum depth to traverse down the path structure, paths that should be automatically expanded and query terms for filtering of root nodes. The Tree API is deal to support a variety of cases including: retrieval of multiple deeply-nested paths within a singl

Score: 31.08205

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

Find

Find The Cloud CMS Find Service lets you discover and retrieve content using combinations of its three primary content retrieval mechanisms. These mechanisms are: Query (powered by Mongo DB) Search (powered by Elastic Search) Traversal (provides Graph Traversal) A "Find" operation provides a way for you to execute a single API lookup that runs one or more of the above and composes them into a single result set. How it Works When you make a "Find" call, you provide a recipe containing at least on

Score: 24.919708

Application Server / Tags / @query

@query Queries for nodes and makes those nodes available to the template. Parameters parameter required description type the type of node to query for (definition QName) sort the field to sort on sortDirection the direction to sort in (either 1 for ascending or -1 for descending) limit the number of records to return skip a position to skip ahead to in the record set scope if "page", then only relatives related to the current page will be returned as specifies the name of the resultsvariable (by

Score: 21.11309

Search / Query String Reference

Query String Reference Cloud CMS lets you search for your content using either a text-based query string or a JSON block. These two methods are fairly equivalent for most typical operations. They provide two ways to express a search operation that will execute within Elastic Search. They are expressions of the Elastic Search DSL. This portion of the documentation goes into some of things you can do with the former, textual representation of an Elastic Search query string. In Cloud CMS, you can t

Score: 17.386728

How to Retrieve content by their document library path

You can retrieve content by their document library path using the CMS API using the Node API. For example, you can paginate through the children of a node using this call: http://api.cloudcms.com/docs#!/node/get_repositories_repositoryId_branches_branchId_nodes_nodeId_children GET /repositories/{repositoryId}/branches/{branchId}/nodes/{nodeId}/children?path={path} In this case, you would set "nodeId" to the value "root" to indicate the root node. And then use "path" to describe the offset. If yo

Score: 10.218662

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

Supporting large binary files

Cloud CMS offers a few different ways for you to store files - including storing them in S3 (recommended) or even on a local partition (such as an NFS mount). In our SaaS offering, everything is stored in S3 automatically and when you install on-premise, you can configure this to your preference. See this documentation page under Binary Storage: https://www.cloudcms.com/documentation/docker/configuration/api-server.html We definitely can handle large binary files in the 10's or 100's of megabyte

Score: 9.481691

Docker / Kits

Kits Cloud CMS ships a number of pre-built kits containing Docker configuration files to help you get start. These kits are built from customer feedback to provide the most commonly requested scenarios. They can be used straight away or at the very least can serve as a useful reference. To download the Cloud CMS Docker Kits, please visit our Docker download page. Kits All of the Docker kits utilize Docker and Docker Compose. In each kit, you'll find a docker-compose.yml file which describes the

Score: 8.969813

GraphQL

GraphQL Cloud CMS supports query via GraphQL. GraphQL is offered as a core API that sits alongside the Cloud CMS REST APIs. GraphQL is an open-source data query and manipulation language specification that is widely used across many CMS systems, servers and clients. GraphQL is offered so as to make it even easier for developers to quickly integrate and work with content inside of Cloud CMS. In Cloud CMS, all GraphQL calls are scoped to a branch. Each branch has its own GraphQL SDL schema that is

Score: 8.774313

How to limit the fields that come back in a query

Query API calls like http://api.cloudcms.com/docs#!/node/post_repositories_repositoryId_branches_branchId_nodes_query support a parameter named _fields which defines an object specifying the node properties you want to include in the result set for matching nodes. For example in the following query I want the title, subTitle and slug fields returned: { "_type":"my:article", "_fields":{ "title":1, "subTitle":1, "slug":1 } } The result set would look something like the

Score: 8.594578

User Interface / Projects / Configure Search

Configure Search You can configure the project search page to show different filter controls on the left hand side by adding some properties to your project JSON descriptor. These controls ultimately feed into a Cloud CMS node API find call that has the following structure: { "query": ... query block into MongoDB, "search": ... search block into Elastic Search } The following customization block can be added to your project's JSON descriptor: { ..., "search": { "showContentTypes"

Score: 8.486868

Getting Started

Getting Started Welcome to the Cloud CMS Documentation center. Cloud CMS is an API-first content management system that provides everything you need on the back end to power web sites and mobile applications. Cloud CMS makes it easy for your business users to create, manage and publish amazing content to your users! You are reading the Getting Started guide. To learn more about Cloud CMS and what it does, select from the links provided below or use the tree on the left-hand side. We offer severa

Score: 8.457903

Traversal

Traversal Content in Cloud CMS is stored in a graph-like structure that consists of nodes and associations. Nodes are entities in the graph and associations are the relationships (the lines between points in the graph). As such, when working with content in Cloud CMS, you'll often find it useful to employ these structures in terms of your content model. Your content can be spread out between nodes and associations equally so that both the entities and the relationships hold JSON properties that

Score: 8.200717

Docker / Kits / OEM

OEM The OEM kit provides a way for developers, integrators, partners and those who are embedded Cloud CMS in custom solutions to build and test extensions. These extensions include UI extensions as well as API extensions in the form of Java / Spring beans. The kit consists of the following services: ui api mongodb elasticsearch These are connected like this: Running Use the following commands: docker-compose build --force-rm docker-compose up And then open a browser to: http://localhost To acces

Score: 8.143797

Application Server / Tags / @queryOne

@queryOne Supports all of the same mechanics as the @query tag but keeps only the first result. Parameters parameter required description type the type of node to query for (definition QName) sort the field to sort on sortDirection the direction to sort in (either 1 for ascending or -1 for descending) limit the number of records to return skip a position to skip ahead to in the record set scope if "page", then only relatives related to the current page will be returned as specifies the name of t

Score: 8.093784

How can I retrieve content for a tree view?

The Cloud CMS API offers a number of convenience API methods that go beyond basic CRUD and bulk content operations. Among these methods are those that allow you to retrieve content from your repository branch in a tree-friendly format. A tree-organized format means that the data comes back in a such a way as to make it easy to load into front-end tree controls. Typical front-end tree controls requires the ability to load a "snapshot" of the tree as a starting point as well as iteratively grow or

Score: 8.012635

Application Server / Authentication / Providers / LinkedIn

LinkedIn Cloud CMS provides integrated authentication and single-sign-on (SSO) with LinkedIn. This page describes the authentication provider available for the Cloud CMS Application Server that enables your mobile or web applications as well as the Cloud CMS user interface or API to authenticate against LinkedIn. For more information on Authentication within the App Server, see App Server Authentication / SSO. LinkedIn API Keys You will need to configure a LinkedIn application and have the follo

Score: 7.9563684

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

Docker / Kits / Quickstart

Quickstart The Quickstart kit defines the following services: ui api mongodb elasticsearch These are connected like this: Running Use the following commands: docker-compose build --force-rm docker-compose up And then open a browser to: http://localhost To access the API directly: https://localhost:8080 docker-compose.yml version: "2" services: ui: build: ./ui networks: - cloudcms depends_on: - api env_file: - ./ui/ui.env ports: - "80:80" api:

Score: 7.833477