Found 234 results for "appserver tags search"
The search executed in 0.002013668 seconds. That's fast.
Using the JavaScript driver to run an elasticsearch queryThe Cloud CMS REST API allows for elasticsearch queries against a branch. The API endpoint is POST /repositories/{repositoryId}/branches/{branchId}/nodes/search The payload is a JSON object containing a top-level property called "search" which wraps the elasticsearch DSL query. The JavaScript driver exposes this call on the Branch object using the searchNodes() methods. Examples: 1) Search for nodes containing the keyword "hello" in any property: req.branch(function (err, branch) { branch.trap(f
Score: 2.0599647
|
|
Gitana / 3.2 / Guide / Guide / Features / IndexableIndexable 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: 2.053986
|
|
Gitana / 4.0 / Data Engine / Aspects / IndexableIndexable 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: 2.053986
|
|
WCM and CachingIn Dust, there is the notion of a context which has a stack running underneath it. As you drill down into tags, a new context is pushed that can write new context variables as well as access previous variables from previous stack frames. What we're doing in cloudcms-server is providing a dependency tracker so that each tag gets to declare the output (the HTML that was generated) and the set of dependencies that it depended on in order to generate the output. As an example, a query might run an u
Score: 2.0447638
|
|
Gitana / 3.2 / Guide / Guide / Supported StacksSupported Stacks Cloud CMS certifies certain supported stacks for on-premise Cloud CMS 3.2 installations. This information is relevant to customers who run Cloud CMS 3.2 on-premise and manage their own Elastic Search and MongoDB database tiers. This information is not applicable to SaaS customers since Cloud CMS runs that infrastructure for hosted subscribers. The following links provide detailed information on the combinations of operating systems, databases, application servers, bundled compon
Score: 2.0012162
|
|
Gitana / 4.0 / Self Managed / Supported Stacks / OverviewSupported Stacks Gitana certifies certain supported stacks for on-premise Gitana 4.x installations. This information is relevant to customers who run Gitana 4.x on-premise and manage their own Elastic Search and MongoDB database tiers. This information is not applicable to SaaS customers since Gitana runs that infrastructure for hosted subscribers. The following links provide detailed information on the combinations of operating systems, databases, application servers, bundled components and thi
Score: 2.0012162
|
|
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: 2.0000763
|
|
Enterprise Data Engine - GitanaEnterprise Data Engine - Gitana Status Releases Registry Blog Cloud CMS Platform Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Enterprise Data Engine Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Automate Automate your content creation and approval flows while taking advantage of AI services to enhance
Score: 1.9838026
|
|
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: 1.9066052
|
|
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: 1.9066052
|
|
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: 1.9066052
|
|
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: 1.8712192
|
|
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: 1.8712192
|
|
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: 1.8563288
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.753.2.75 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.75. 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: 1.8540142
|
|
Gitana / 3.2 / Guide / Guide / GraphQLGraphQL 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: 1.845165
|
|
Gitana / 4.0 / Data Engine / Discovery / GraphQLGraphQL 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: 1.845165
|
|
Gitana / 3.2 / Guide / Guide / Docker / Maintenance / UpgradesUpgrades 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: 1.8389205
|
|
Gitana / 4.0 / Self Managed / Maintenance / UpgradesUpgrades 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: 1.8389205
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / NodeNode Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} Configuration The node configuration contains system and custom properties. You can write your own properties as you see fit. However, system properties sho
Score: 1.8292692
|
|
Gitana / 4.0 / Data Engine / API / Data Types / NodeNode Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} Configuration The node configuration contains system and custom properties. You can write your own properties as you see fit. However, system properties sho
Score: 1.8292692
|
|
Gitana / 3.2 / Guide / Guide / Docker / KitsKits 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: 1.8168286
|
|
Gitana / 4.0 / Self Managed / Kits / OverviewKits 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: 1.8168286
|
|
Recommended environmentThis is a big subject and, as you know, there are many ways to set things up to be robust. That said, some practices are better than others. I can relate at least what we do and what we've seen customers do. First, I'd recommend thinking of Cloud CMS as black box application that runs on top of MongoDB, Elastic Search (both of which can be thought of as databases) and a binary storage provider. Cloud CMS is a stateless application whose setup is actually quite simple. It doesn't maintain any sta
Score: 1.8015139
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.793.2.79 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.79. Release Notes The release notes for this release are available here: https://gitana.io/release.html?name=3.2.79 Support for ARM-64 With version 3.2.79, we are proud to announce official support for ARM aarch64 architectures. This provides our customers with a choice of chip architectures to deploy on. The demand for ARM has increased as performance testing has shown a 20% better performance while being
Score: 1.7882459
|