Found 610 results for "appserver authentication adapters default"

The search executed in 0.002330254 seconds. That's fast.

Score: 0.74323344

Gitana / 3.2 / Guide / Guide / Application Server / Services / Web Content Management

Web Content Management Whether to support dynamic loading of web pages from Cloud CMS. This enables the Cloud CMS web content management solution. Here is what a full configuration set looks like: { "wcm": { "enabled": true, "cache": true, "cacheKey": { "params": { "includes": [], "excludes": [], "excludeAll": false } }, "pageCacheTTL": (24 * 60 * 60) * 1000, // 24 hours "p

Score: 0.771162

Gitana / 4.0 / Developers / Application Server / Services / Web Content Management

Web Content Management Whether to support dynamic loading of web pages from Cloud CMS. This enables the Cloud CMS web content management solution. Here is what a full configuration set looks like: { "wcm": { "enabled": true, "cache": true, "cacheKey": { "params": { "includes": [], "excludes": [], "excludeAll": false } }, "pageCacheTTL": (24 * 60 * 60) * 1000, // 24 hours "p

Score: 0.771162

Gitana / 3.2 / Guide / Guide / Features / Filename

Filename QName: f:filename Allows for nodes to retain a display-friendly and file-system compatible name for use in containment-based navigation systems such as WebDAV, FTP or the Cloud CMS document library. Nodes that are tagged with this feature can either deterministically specify their preferred filename or have one calculated for them from the node's title or _doc fields. Filenames may not contain the following special characters: .:_<>?&@!$%^()-+=\. If these characters are included, they w

Score: 0.76691043

Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Script

Script Type: script This handler lets you run a script based on the items in a workflow. The config for this handler is as follows: { "script": "my script" "mimetype": "optional script mimetype (javascript by default)" } When writing your script, you will have access to variables containing document and workflow data: workflow Current workflow workflowTask - Current workflowTask workflowData - Workflow metadata documents - Array of documents being processed by the workflow Example: Simp

Score: 0.76691043

Gitana / 4.0 / Data Engine / Aspects / Filename

Filename QName: f:filename Allows for nodes to retain a display-friendly and file-system compatible name for use in containment-based navigation systems such as WebDAV, FTP or the Cloud CMS document library. Nodes that are tagged with this feature can either deterministically specify their preferred filename or have one calculated for them from the node's title or _doc fields. Filenames may not contain the following special characters: .:_<>?&@!$%^()-+=\. If these characters are included, they w

Score: 0.76691043

Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / Script

Script Type: script This handler lets you run a script based on the items in a workflow. The config for this handler is as follows: { "script": "my script" "mimetype": "optional script mimetype (javascript by default)" } When writing your script, you will have access to variables containing document and workflow data: workflow Current workflow workflowTask - Current workflowTask workflowData - Workflow metadata documents - Array of documents being processed by the workflow Example: Simp

Score: 0.76691043

Gitana / 3.2 / Guide / Guide / UI Developers Guide / UI Views

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

Score: 0.76089156

Gitana / 4.0 / Developers / User Interface Customization / UI Views

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

Score: 0.76089156

Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Move Node

Move Node Type: moveNode This handler moves nodes that are part of a workflow's payload to a target container. The target container can be identified either by a node ID or a node path. The config for this handler is as follows: { "targetNodeId": "", "targetOffsetPath": "" } If targetOffsetPath is specified, then targetNodeId is the root node to calculate the offset against. If targetNodeId is not provided, the default repository root is used. Here is an exa

Score: 0.75894225

Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / Move Node

Move Node Type: moveNode This handler moves nodes that are part of a workflow's payload to a target container. The target container can be identified either by a node ID or a node path. The config for this handler is as follows: { "targetNodeId": "", "targetOffsetPath": "" } If targetOffsetPath is specified, then targetNodeId is the root node to calculate the offset against. If targetNodeId is not provided, the default repository root is used. Here is an exa

Score: 0.75894225

Gitana / 3.2 / Guide / Guide / Binary Files

Binary Files Cloud CMS lets you upload any kind of desktop file. The system will automatically detect the type of content that you upload and will inspect and work with the content to provide the following services: Automatic antivirus scanning to detect malicious files Extraction of metadata properties from the payload body and headers Conversion of content type to thumbnails (using image transformation) Detection and extraction of text for full-text search Execution of custom rules to further

Score: 0.75004613

Gitana / 4.0 / Data Engine / Platform / Binary Files

Binary Files Cloud CMS lets you upload any kind of desktop file. The system will automatically detect the type of content that you upload and will inspect and work with the content to provide the following services: Automatic antivirus scanning to detect malicious files Extraction of metadata properties from the payload body and headers Conversion of content type to thumbnails (using image transformation) Detection and extraction of text for full-text search Execution of custom rules to further

Score: 0.75004613

Gitana / 4.0 / Forms / Fields / Upload Field

Upload Field The upload field provides a mechanism that enables end users to upload one or more files to a server endpoint and have references to those files stored in the JSON of your form. For example, you may have an array of files in your JSON consisting of filenames to assets that are uploaded to your server - something like: { "title": "My Files", "files": [{ "filename": "/folder1/folder2/file3.jpg" }, { "filename": "/folder1/folder2/file4.pdf" }] } This fi

Score: 0.75004613

Gitana / 3.2 / Guide / Guide / Features / AWS Transcode

AWS Transcode QName: f:aws-transcode Applying this feature allows a piece of content's default attachment to be automatically transcoded from one filetype to one or more other filetypes. This is done to the specification of custom or AWS predefined presets. Once a transcoding is finished, an array of S3 paths for the transcoded files will be saved back to the content. To use this feature, you will need to have an AWS account with S3 and Amazon Elastic Transcoder setup. You will also need to conf

Score: 0.7483969

Gitana / 3.2 / Guide / Guide / 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: 0.7483969

Gitana / 4.0 / Data Engine / Aspects / AWS Transcode

AWS Transcode QName: f:aws-transcode Applying this feature allows a piece of content's default attachment to be automatically transcoded from one filetype to one or more other filetypes. This is done to the specification of custom or AWS predefined presets. Once a transcoding is finished, an array of S3 paths for the transcoded files will be saved back to the content. To use this feature, you will need to have an AWS account with S3 and Amazon Elastic Transcoder setup. You will also need to conf

Score: 0.7483969

Gitana / 4.0 / 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: 0.7483969

Gitana / 3.2 / Guide / Guide / Policies

Policies Policies can be used to run custom code or fire off actions when an event, such as creating a content item or associating a content item into the content graph, occurs. Cloud CMS provides a wide array of policies that you can hook your custom logic into. By default, Cloud CMS provides sensible and useful content policy handlers to manage the lifecycle of you content. You can wire in new policy handlers. Policy handlers include scripts and rules. These policies will trigger behaviors whe

Score: 0.7434925

Gitana / 3.2 / Guide / Guide / 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: 0.7434925

Gitana / 3.2 / Guide / Guide / Workflow / Sample Workflows / Simple Publish

Simple Publish The simple-publish workflow is provided out-of-the-box to support Publishing within Cloud CMS. { "id": "simple-publish", "title": "Simple Publish", "handlers": { "START": [{ "type": "script", "config": { "script": "workflowData.originalChangesetIds = {}; for (var i = 0; i < documents.length; i++) { workflowData.originalChangesetIds[documents[i].id] = documents[i].changesetId; }" } }] }, "nodes"

Score: 0.7434925

Gitana / 4.0 / Data Engine / Behaviors / Policies

Policies Policies can be used to run custom code or fire off actions when an event, such as creating a content item or associating a content item into the content graph, occurs. Cloud CMS provides a wide array of policies that you can hook your custom logic into. By default, Cloud CMS provides sensible and useful content policy handlers to manage the lifecycle of you content. You can wire in new policy handlers. Policy handlers include scripts and rules. These policies will trigger behaviors whe

Score: 0.7434925

Gitana / 4.0 / Data Engine / Workflow / Sample Workflows / Simple Publish

Simple Publish The simple-publish workflow is provided out-of-the-box to support Publishing within Cloud CMS. { "id": "simple-publish", "title": "Simple Publish", "handlers": { "START": [{ "type": "script", "config": { "script": "workflowData.originalChangesetIds = {}; for (var i = 0; i < documents.length; i++) { workflowData.originalChangesetIds[documents[i].id] = documents[i].changesetId; }" } }] }, "nodes"

Score: 0.7434925

Gitana / 3.2 / Guide / Guide / Features / Renditionable

Renditionable QName: f:renditionable Marks that an instance or type is to have one or more renditions. Renditions are other nodes in the branch whose content is automatically generated and kept in sync as the source node is created, updated and deleted (or has its relevant attachment modified). Configuration

Property Type Default Read-Only Description

Gitana / 3.2 / Guide / Guide / Application Server / Installation / Module Installation

Module Installation The Cloud CMS Application Server can also be run as a custom Node.js application. It is available as a Node.js module that you can require() in from npmjs.org. The server features a number of extension points that you can utilize to wire in new functionality or extend the framework. Getting Started Here is a simple example where we start up the Application Server from within a Node.js application: var server = require("cloudcms-server/server"); server.start(); The start() me

Score: 0.74323344

Gitana / 4.0 / Developers / Application Server / Installation / Module Installation

Module Installation The Cloud CMS Application Server can also be run as a custom Node.js application. It is available as a Node.js module that you can require() in from npmjs.org. The server features a number of extension points that you can utilize to wire in new functionality or extend the framework. Getting Started Here is a simple example where we start up the Application Server from within a Node.js application: var server = require("cloudcms-server/server"); server.start(); The start() me

Score: 0.74323344