Found 522 results for "gitana 4.0 developers api resources deployment-receiver"
The search executed in 0.003682549 seconds. That's fast.
Gitana / 4.0 / Developers / Application Server / Web Content ManagementWeb Content Management The Application Server provides the runtime for the Cloud CMS Web Content Management solution. Web Content Management is a term that enterprise vendors have been using for years to distinguish between the role that a CMS (content management system) plays for an organization - it may be used to collaborate around your internal documents, legal records, digital assets and many other content items in addition to your web and mobile content. Cloud CMS provides a Web Content Ma
Score: 0.85858935
|
|
Gitana / 4.0 / Content Engine / Discovery / TraversalTraversal 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: 0.85858935
|
|
Security: Grade ACloud CMS comes in two flavors - on-premise and hosted. For our hosted customers, we host 100% of Cloud CMS and take care of all of the data backup, migrations, security, load balancing and… well, everything! It’s the whole kit and kaboodle. It’s all of the DevOps and stuff solved for you. One of the fun aspects of this is keeping up with security requirements around SSL and HTTP Transport. Cloud CMS customers automatically gain the advantage of SSL for all of their communication with the Cloud
Score: 0.84653604
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Installation / Module InstallationModule 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.83931
|
|
Gitana / 4.0 / Developers / Application Server / Installation / Module InstallationModule 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.83931
|
|
Gitana / 3.2 / Guide / Guide / Templates / WorkflowWorkflow Name: workflow Property Type Description id string The ID of the workflow instance modelId string The ID of the workflow model for this instance modelVersion number The version of the workflow model for this instance state string The state of the workflow - one of the following: NOT_STARTED, RUNNING, SUSPENDED, TERMINATED timeStarted calendar The time the workflow was started timeCompleted calendar The time the workflow was completed (if completed) context object Contextual variables be
Score: 0.832397
|
|
Gitana / 4.0 / Content Engine / Templates / WorkflowWorkflow Name: workflow Property Type Description id string The ID of the workflow instance modelId string The ID of the workflow model for this instance modelVersion number The version of the workflow model for this instance state string The state of the workflow - one of the following: NOT_STARTED, RUNNING, SUSPENDED, TERMINATED timeStarted calendar The time the workflow was started timeCompleted calendar The time the workflow was completed (if completed) context object Contextual variables be
Score: 0.832397
|
|
Gitana / 3.2 / Guide / Guide / AttachmentsAttachments Cloud CMS provides support for the storage and retrieval of binary assets. These assets are stored as attachments on an object. Unlike some CMS systems which start with the binary asset, Cloud CMS considers all of your objects and content to be JSON documents. The JSON document then has N number of binary BLOBs attached to it. Each attachment has a unique name and retains information such as mimetype, filename and content length. The following kinds of objects support attachments: Co
Score: 0.83059156
|
|
Gitana / 4.0 / Content Engine / Nodes / AttachmentsAttachments Cloud CMS provides support for the storage and retrieval of binary assets. These assets are stored as attachments on an object. Unlike some CMS systems which start with the binary asset, Cloud CMS considers all of your objects and content to be JSON documents. The JSON document then has N number of binary BLOBs attached to it. Each attachment has a unique name and retains information such as mimetype, filename and content length. The following kinds of objects support attachments: Co
Score: 0.83059156
|
|
Gitana / 3.2 / Guide / Guide / 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 fields comma separated list of property names to include in query results skip a position to skip ahead to in the record set scope if "page", then only relativ
Score: 0.80548996
|
|
Gitana / 4.0 / Developers / 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 fields comma separated list of property names to include in query results skip a position to skip ahead to in the record set scope if "page", then only relativ
Score: 0.80548996
|
|
Gitana / 4.0 / Reference / Types / ApplicationApplication A Data Store Platform Application Table of Contents Overview Parent Objects Properties Methods Examples Schema An Application is a Data Store where you can store configuration related to your mobile, touch or web application. An Application Data Store provides services and objects that are you may choose to use to provide functionality and manage state for your application. This includes: User Registration Sign Up, Confirmation Emails Email Services Settings and Configuration storage
Score: 0.80248916
|
|
Gitana / 3.2 / Guide / Guide / Single Sign On (SSO) / JWTJWT This page provides a simple example of how to configure Cloud CMS for JWT. For a deeper explanation of Cloud CMS Single Sign On (SSO) and the role that JWT plays in it, please read our documentation on Single Sign On. The example provided here is pretty simple. It is put together this way to keep things simple. In practice, you'll make modifications to this approach depending upon the needs of your security and identity provider system. JWT.IO Let's generate a JSON Web Token. Open up a brows
Score: 0.78439367
|
|
Gitana / 4.0 / Developers / Authentication / Single Sign On (SSO) / JWTJWT This page provides a simple example of how to configure Cloud CMS for JWT. For a deeper explanation of Cloud CMS Single Sign On (SSO) and the role that JWT plays in it, please read our documentation on Single Sign On. The example provided here is pretty simple. It is put together this way to keep things simple. In practice, you'll make modifications to this approach depending upon the needs of your security and identity provider system. JWT.IO Let's generate a JSON Web Token. Open up a brows
Score: 0.78439367
|
|
Gitana / 3.2 / Guide / Guide / Features / ContainerContainer QName: f:container Makes a node as a container. In Cloud CMS, all nodes are essentially equivalent. There is no assumed containment model - in other words, Cloud CMS does not assume a folder structure or any kind of graph that you must adhere to. You can use associations to model any kind of relationship you would like. For example, you might have nodes that maintain only a kind of "linked" relationship to do things like link together related items for a product catalog. Another exampl
Score: 0.780268
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.733.2.73 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.73. Elastic Search Client Make sure that you are have configured Cloud CMS to connect to Elastic Searching using the condor HTTP/S client. In prior versions of Cloud CMS, an http and transport client were offered that utilized the native drivers of Elastic Search. As we've expanded our support for Elastic Search to include Amazon OpenSearch, we've moved over to using the condor driver which is built and op
Score: 0.780268
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.743.2.74 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.74. Elastic Search Client Make sure that you are have configured Cloud CMS to connect to Elastic Searching using the condor HTTP/S client. In prior versions of Cloud CMS, an http and transport client were offered that utilized the native drivers of Elastic Search. As we've expanded our support for Elastic Search to include Amazon OpenSearch, we've moved over to using the condor driver which is built and op
Score: 0.780268
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.763.2.76 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.76. Elastic Search Client Make sure that you are have configured Cloud CMS to connect to Elastic Searching using the condor HTTP/S client. In prior versions of Cloud CMS, an http and transport client were offered that utilized the native drivers of Elastic Search. As we've expanded our support for Elastic Search to include Amazon OpenSearch, we've moved over to using the condor driver which is built and op
Score: 0.780268
|
|
Gitana / 4.0 / Content Engine / Aspects / ContainerContainer QName: f:container Makes a node as a container. In Cloud CMS, all nodes are essentially equivalent. There is no assumed containment model - in other words, Cloud CMS does not assume a folder structure or any kind of graph that you must adhere to. You can use associations to model any kind of relationship you would like. For example, you might have nodes that maintain only a kind of "linked" relationship to do things like link together related items for a product catalog. Another exampl
Score: 0.780268
|
|
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: 0.780268
|
|
Gitana / 3.2 / Guide / Guide / Application Server / AuthenticationAuthentication The Authentication Service provides a full authentication framework for stateless and session-based applications. It authenticates requests against back end providers and offers interpretation and parsing of request scope information to provide Single-Sign-On (SSO). Authenticated requests will have user accounts created and synchronized within Cloud CMS either automatically or as part of a registration form process. Authenticated users have Cloud CMS connectivity state managed for
Score: 0.76708305
|
|
Gitana / 4.0 / Developers / Application Server / AuthenticationAuthentication The Authentication Service provides a full authentication framework for stateless and session-based applications. It authenticates requests against back end providers and offers interpretation and parsing of request scope information to provide Single-Sign-On (SSO). Authenticated requests will have user accounts created and synchronized within Cloud CMS either automatically or as part of a registration form process. Authenticated users have Cloud CMS connectivity state managed for
Score: 0.76708305
|
|
Programmatically create content in a folder?The Cloud CMS content API lets you work with JSON to create any kind of content you'd like. It supports any JSON structure you desire and also supports a number of special properties that you can use to make life easier for you. These special properties are: _rootNodeId - The mount node ID of the root against which relatives path are computed. By default, this is the root of the repository. In general, it isn't necessary to use this property unless you have multiple mount nodes configured. And m
Score: 0.75657755
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.773.2.77 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.77. Release Notes The release notes for this release are available here: https://gitana.io/release.html?name=3.2.77 Elastic Search Client Make sure that you are have configured Cloud CMS to connect to Elastic Searching using the condor HTTP/S client. In prior versions of Cloud CMS, an http and transport client were offered that utilized the native drivers of Elastic Search. As we've expanded our support fo
Score: 0.7342833
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.783.2.78 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.78. Release Notes The release notes for this release are available here: https://gitana.io/release.html?name=3.2.78 Elastic Search Client Make sure that you are have configured Cloud CMS to connect to Elastic Searching using the condor HTTP/S client. In prior versions of Cloud CMS, an http and transport client were offered that utilized the native drivers of Elastic Search. As we've expanded our support fo
Score: 0.7342833
|