Found 152 results for "api content-services transfer"

The search executed in 0.001 seconds

Transfer

Transfer Cloud CMS supports transfer (import and export) for all data stores and objects. Transfer allows you to export your data into Archives. An Archive is a ZIP file which contains a manifest file that fully describes the contents of the ZIP. Archives are automatically stored within Vaults. Transfer lets you import existing archives into new data stores. This lets you quickly restore the state of previous projects or reuse previous projects within new endeavors. You can download archives at

Score: 36.84415

API Keys

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

Score: 34.024025

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

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

Publishing

Publishing Content Types Example Publishing Setup Lifecycle States Preview Servers Publications Workflow

Score: 17.409336

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

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

Sync from one environment to another

Within Cloud CMS sync capabiities are generally referred to as the "transfer system". They allow you to export individual objects, data stores or even collections of these as an archive (ZIP) within a vault. You can then move those archives to storage for backup or move them to new Cloud CMS server instances for restoration or replication. We have support for transfer within our API, our drivers and also within the user interface. The latter is useful in that you can script it pretty effectively

Score: 6.2835846

Publishing / Preview Servers

Preview Servers Before your changes go to Live website i.e. on the Production mode, to discover problems and fix them right away you can set up the Preview Servers and review the content changes instantly. You can look at the default Preview Servers under Manage Project : The default servers are Authoring and Production and are setup to a sample URL which can be modified with your website URL or some API or an Application. To add your Custom Server, you can click on Add Preview Server and set-up

Score: 5.169084

API / Data Types / Identity

Identity Type identity Datastore Type directory Supports authorities, permissions, transfer

Score: 4.3281994

API / Data Types / Plan

Plan Type plan Datastore Type registrar Supports authorities, permissions, transfer

Score: 4.3281994

API / Data Types / Settings

Settings Type settings Datastore Type application Supports authorities, permissions, transfer

Score: 4.3281994

API / Data Types / Tenant

Tenant Type tenant Datastore Type registrar Supports authorities, permissions, transfer

Score: 4.3281994

API / Data Types / Archive

Archive Type archive Datastore Type registrar Supports authorities, permissions, transfer TODO

Score: 4.3189783

API / Data Types / Auto Client Mapping

Auto Client Mapping Type autoClientMapping Datastore Type webhost Supports authorities, permissions, transfer

Score: 4.291551

Publishing / Content Types

Content Types Cloud CMS lets you customize the Publishing Behavior and the Workflow Per Content Type. You can now Enable/Disable the Preview and Publishing buttons for each Content Type. Customize Publishing Behavior Per Content Type You can disable the Publishing Behavior like Preview button or the Publishing buttons for all the Content types whose content or data you do not want to publish. To Disable the Publishing behaviors of the Content Types: Go to Project Go to Manage Project Go to Publi

Score: 3.8876822

Publishing / Publications

Publications Publications tell the system whenever content on the "master" branch goes into the "live" state, it should be pushed out to the deployment target. Once you Add a Publication to the Project, the content from the Selected Branch will be published to the Selected Deployment Target and its Lifecycle State will change to Live. To Add Publication: Go to Manage Project Publication Settings Click on Publications Click on Add a Publication Select the Branch whose content you wish to deploy t

Score: 3.7600195

Publishing / Workflow

Workflow Cloud CMS lets you define your own Workflows and choose them for the Publish and Unpublish activities. Each activity like Publish and Unpublish will have a Workflow Model which will have a set of instructions on how the contents should be routed during each activity. The default Workflow models we use for the Publish activity is Simple Publish and for the Unpublish activity is Simple Unpublish. You can add your own Workflows and customize your publish and unpublish activities.

Score: 3.6404743

API / Data Types / Platform

Platform Configuration As with all data stores, this data store maintain a configuration document that contains system and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others are writable. You can adjust the writable properties to modify the behavior and characteristics of the directory. The following table presents you

Score: 3.6404219

Publishing / Lifecycle States

Lifecycle States Cloud CMS contains four content Lifecycle States during the Publishing process of a content. These define the state of the Content in the Publishing Lifecycle. Each state will have an ID, Title and a Preview Endpoint The four states in the Publishing lifecycle are : - None - Draft - Live - Archived You can look at the lifecycle states as follows: Each state has a Preview Endpoint which can be defined or modified under Preview Servers. These gives a chance to instantly preview th

Score: 3.4228256

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

API / Patching

Patching Cloud CMS supports the use of HTTP Patch (RFC 5789) along with JSON Patch (RFC 6902) to describe atomic updates to content objects. This allows for lighter JSON payloads by only requiring property-level differences to be sent over the wire instead of full document payloads. JSON Patch supports many property operations including add, remove, move and copy as well as insertion within arrays and key/field manipulation for objects. The HTTP Patch method is invoked like this: PATCH /reposito

Score: 3.0838623

API / Data Types / Scheduled Work

Scheduled Work Type scheduledwork Datastore Type platform Supports authorities, permissions, transfer Configuration A scheduled work item has a configuration that informs the Cloud CMS cluster-wide timer how to trigger them, based on what frequency and what settings are provided for their described actions. You can adjust this confirmation at any time and supply it when you create, update or query for scheduled work items. The following table shows the configuration properties: Property Type Def

Score: 3.0540855

API / Data Types / Client

Client Type client Datastore Type application Supports authorities, permissions, transfer Configuration Clients maintain a configuration that you can adjust or consult as you create, update and query for them. The following table presents you the configuration properties. Property Type Default Read-Only Description key text (auto-generated) Read-Only The authentication grant key. secret text (auto-generated) The authentication grant secret. scope array ["api"] An array of strings that define the

Score: 2.8799112

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