[/map {"- map/map "}) [/map/topicref {"- map/topicref "}) [/map/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicmeta/navtitle {"- topic/navtitle "}) Introduction (navtitle][/map/topicref/topicmeta/linktext {"- map/linktext "}) Introduction (linktext][/map/topicref/topicmeta/shortdesc {"- map/shortdesc "}) This section describes the stage at which you take control of the operation and maintenance of your application powered by the Oracle Endeca Server. (shortdesc] (topicmeta][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Taking ownership of your implementation (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Taking ownership of your implementation (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) As a system administrator, you take ownership of the Oracle Endeca Server implementation at a certain stage. This topic describes the context in which you will perform administrative tasks to maintain the stable operation of a properly functioning implementation. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Overview of administrator tasks (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Overview of administrator tasks (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) This topic provides a brief overview of the administrator tasks described in this guide. (shortdesc] (topicmeta] (topicref] (topicref] [/map/topicref {"- map/topicref "}) [/map/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicmeta/navtitle {"- topic/navtitle "}) Oracle Endeca Server as a Java Application (navtitle][/map/topicref/topicmeta/linktext {"- map/linktext "}) Oracle Endeca Server as a Java Application (linktext][/map/topicref/topicmeta/shortdesc {"- map/shortdesc "}) This section provides an overview of the Oracle Endeca Server Java application and describes administration and configuration tasks for it. (shortdesc] (topicmeta][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Overview of Oracle Endeca Server application (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Overview of Oracle Endeca Server application (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The Endeca Server is a Java application hosted in the WebLogic Server container that manages the Endeca data domains. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) The EndecaServer.properties file (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) The EndecaServer.properties file (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) A configuration file, EndecaServer.properties, sets global parameters for Endeca Server, such as the default locations of mandatory files and directories. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Using a data directory on a different drive (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Using a data directory on a different drive (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The endeca-data-dir parameter in the EndecaServer.properties file allows you to specify a different drive for the data domain's index. On Windows, for example, your WebLogic Server and Endeca Server installations can be on drive C, while the data domain indexes can be created on drive D. They can also be placed on a shared file system, as in a clustered environment. The default drive is the same one on which the Endeca Server application directory is installed. You can also change the data directory for existing data domains. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Starting Endeca Server (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Starting Endeca Server (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Starting the Oracle Endeca Server application makes it available for WebLogic Server clients. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Stopping Endeca Server (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Stopping Endeca Server (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Stopping the Oracle Endeca Server application makes it unavailable for WebLogic Server clients. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Restarting WebLogic Server without stopping Endeca Server (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Restarting WebLogic Server without stopping Endeca Server (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If you shut down WebLogic Server while the Endeca Server is running, when you restart WebLogic Server, the Endeca Server goes into a transient state. The state resolves automatically after a timeout. To avoid the transient state of the Endeca Server, before you stop the WebLogic Server, stop the Endeca Server application running in it. (shortdesc] (topicmeta] (topicref] (topicref] [/map/topicref {"- map/topicref "}) [/map/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicmeta/navtitle {"- topic/navtitle "}) Endeca Server Command Reference (navtitle][/map/topicref/topicmeta/linktext {"- map/linktext "}) Endeca Server Command Reference (linktext][/map/topicref/topicmeta/shortdesc {"- map/shortdesc "}) This section describes the commands of the endeca-cmd command-line interface. (shortdesc] (topicmeta][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) About the endeca-cmd utility (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) About the endeca-cmd utility (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The Endeca Server has a command-line interface that lets you control nodes in the Endeca Server cluster, data domains hosted in the Endeca Server cluster, and the data domain nodes. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Command global options (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Command global options (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The Endeca Server command interface has several global options that allow you to specify the host, port, and context root of the Oracle Endeca Server, and enable the interface for SSL. (shortdesc] (topicmeta][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Global options for host, port, and context root (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Global options for host, port, and context root (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Three global options allow you to specify the host name, port number, and context root information for the Endeca Server. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Global options for SSL (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Global options for SSL (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) These global options are used to support SSL-enabled communications with an Oracle Endeca Server running over SSL. (shortdesc] (topicmeta] (topicref] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Endeca Server node operations (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Endeca Server node operations (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) These commands operate on Endeca Server nodes, by allowing you to specify the node profile that will be used by each Endeca Server node in the cluster, obtain the node profile that is currently configured, delete an Endeca Server node, list nodes, and obtain the status of the cluster and its nodes. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Data domain profile operations (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Data domain profile operations (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) These commands operate on Endeca data domain profiles. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Data domain operations (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Data domain operations (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) These commands operate on Endeca data domains. For example, they allow you to create data domains and return information about their status. (shortdesc] (topicmeta] (topicref] (topicref] [/map/topicref {"- map/topicref "}) [/map/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicmeta/navtitle {"- topic/navtitle "}) Managing Data Domains (navtitle][/map/topicref/topicmeta/linktext {"- map/linktext "}) Managing Data Domains (linktext][/map/topicref/topicmeta/shortdesc {"- map/shortdesc "}) This section describes how to add or delete data domains, change the number of data domain nodes, and do other maintenance tasks, such as copying, importing, enabling, and monitoring a data domain. (shortdesc] (topicmeta][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) The Endeca data domain and the Dgraph process (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) The Endeca data domain and the Dgraph process (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The Endeca Server application services requests for one or more Endeca data domains. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Adding, removing, changing and updating data domains (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Adding, removing, changing and updating data domains (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can create a new data domain, clone an existing data domain, change the number of data domain nodes, and update the data domain to use another data domain profile. (shortdesc] (topicmeta][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Adding a new data domain (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Adding a new data domain (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You add a data domain with the endeca-cmd create-dd name command, where name is the name of your data domain. Running this command is equivalent to using the createDataDomain operation in the Manage Web Service request. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Removing a data domain (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Removing a data domain (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You remove a data domain with endeca-cmd delete-dd name, or with the deleteDataDomain request of the Manage Web Service. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Cloning an existing data domain (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Cloning an existing data domain (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can add a new data domain that replicates an existing one with the endeca-cmd clone-dd name command, or with the cloneDataDomain operation of the Manage Web Service. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Adding nodes to a data domain (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Adding nodes to a data domain (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) To rescale, or add Dgraph nodes to a running data domain, use the endeca-cmd rescale-dd command, or the rescaleDataDomain operation of the Manage Web Service. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Updating a data domain (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Updating a data domain (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You update a data domain with the endeca-cmd update-dd name --dd-profile-name command, where name is the name of your data domain, and the --dd-profile-mame option specifies the data domain profile you want to use (this option is required). Running this command is equivalent to using the updateDataDomain operation in the Manage Web Service request. (shortdesc] (topicmeta] (topicref] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Importing, exporting, enabling, or disabling data domains (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Importing, exporting, enabling, or disabling data domains (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can import, export, enable, and disable data domains. (shortdesc] (topicmeta][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Exporting and importing a data domain (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Exporting and importing a data domain (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Exporting a data domain takes a snapshot of the data domain's index files, which is useful for backups. Importing a data domain lets you create a new data domain based on an exported index. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Enabling a data domain (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Enabling a data domain (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Enabling a data domain is a means of starting all Dgraph processes serving this data domain. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Disabling a data domain (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Disabling a data domain (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Disabling a data domain is a means of stopping the data domain nodes (the Dgraph processes) serving this data domain. (shortdesc] (topicmeta] (topicref] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Monitoring and backing up data domains (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Monitoring and backing up data domains (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can list data domains, their host names and ports, monitor their status, and obtain information about the data domain's index, number of records, and other statistics. You can also back up an index file for a running data domain. (shortdesc] (topicmeta][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Obtaining information about data domains (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Obtaining information about data domains (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can list one or more data domains using endeca-cmd list-dd, or the operations from the Manage Web Service. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Monitoring the data domain health (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Monitoring the data domain health (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Use the endeca-cmd get-dd-health to check the health of the data domain and list the status of the Dgraph nodes, including details about each Dgraph process that is not running. Alternatively, you can use the getDataDomainHealth request of the Cluster Web Service. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Checking the status of the data domain nodes (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Checking the status of the data domain nodes (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) A quick way of checking the health of a Dgraph node in the data domain is to get its status from the Endeca Server. Use the endeca-cmd get-dd-status command, or the getDataDomainStats from the Manage Web Service, to obtain information about the size of the data domain's index, the number of indexed records, and the Dgraph statistics page. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Backing up the index (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Backing up the index (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) To back up a data domain's index, take a snapshot of the index files by exporting them. You can later restore the index to this particular state. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Collecting debugging information (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Collecting debugging information (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Before attempting to debug an issue with the data domain, collect the following information. (shortdesc] (topicmeta] (topicref] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Other tasks and characteristics of data domains (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Other tasks and characteristics of data domains (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can issue cache warming operations to the data domain's Dgraph processes, and configure session affinity for data domains. You can also learn how to connect to the data domains, how to load data, and how different types of data domains behave, such as read-only, idle, or oversubscribed data domains. (shortdesc] (topicmeta][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Endeca Server memory consumption (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Endeca Server memory consumption (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The Endeca Server query performance is dependent on many characteristics of your specific deployment, such as query workload, query complexity, data domain configuration, and the characteristics of the loaded records, as well as the size of the data domain's index. In view of these characteristics, a hardware sizing must be performed prior to deployment, to assess memory consumption and other hardware needs of your deployment. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) About using control groups (cgroups) for data domains (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) About using control groups (cgroups) for data domains (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) On Oracle Enterprise Linux 6 (Red Hat Enterprise Linux Server release 6), Endeca Server has a new option to use cgroups to limit the total memory usage of Dgraph processes hosted on the machine. Control groups (also known as cgroups) is a kernel resource-controlling feature of the Linux 6 operating system. They provide a way to define and allocate the system resources to one or more specific processes, while controlling, at a high-level, the utilization of these resources, and ensuring that the processes do not consume excessive resources. In this way, cgroups help avoid situations where the hosting machines run out of memory for their functioning and are forced to shut down due to their hosted applications taking over all available resources on the machine. (shortdesc] (topicmeta][/map/topicref/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Enabling cgroups for the data domain (navtitle][/map/topicref/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Enabling cgroups for the data domain (linktext][/map/topicref/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If the Endeca Server is deployed on Linux 6, you can enable utilization of cgroups for the Endeca Server application and its processes, by making the required changes in the EndecaServer.properties configuration file, on each Endeca Server node hosting a data domain, and then running the specially-provided setup_cgroups.sh script located in $DOMAIN_HOME/EndecaServer/bin directory of your Endeca Server deployment. (shortdesc] (topicmeta] (topicref] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Read-only data domains (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Read-only data domains (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) When defining a data domain profile, you can specify whether the data domain should be created as read-only. Having a read-only data domain is useful in the development environment or for demonstration purposes — a read-only data domain does not allow changes to its index, but lets the application users issue read-type queries, such as regular search and navigation queries. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Auto-idling and oversubscribing behavior of data domains (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Auto-idling and oversubscribing behavior of data domains (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Data domain profiles define two important aspects of data domain behavior — automatic idling and oversubscribing. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Issuing cache warming requests to the Dgraph (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Issuing cache warming requests to the Dgraph (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) In a running data domain, you can issue a request to warm up the cache of its Dgraph processes. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Configuring session affinity for data domains (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Configuring session affinity for data domains (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) When receiving client requests, the Endeca Server cluster routes them to the arbitrary Endeca Server nodes hosting the appropriate data domains. Optionally, you can configure your data domain profile to utilize session affinity for request routing. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) About connecting Web browsers to data domains (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) About connecting Web browsers to data domains (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) For security reasons, you should never allow user Web browsers to connect directly to the machine hosting the Endeca Server and the Endeca data domains. (shortdesc] (topicmeta] (topicref] (topicref] (topicref] [/map/topicref {"- map/topicref "}) [/map/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicmeta/navtitle {"- topic/navtitle "}) Dgraph Administrative Tasks (navtitle][/map/topicref/topicmeta/linktext {"- map/linktext "}) Dgraph Administrative Tasks (linktext][/map/topicref/topicmeta/shortdesc {"- map/shortdesc "}) This section describes the Dgraph flags, and the administrative operations for the Dgraph process. It also describes the Dgraph index merge policy and managing the Dgraph core dump files. (shortdesc] (topicmeta][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Dgraph flags (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Dgraph flags (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The Oracle Endeca Server starts the Dgraph process for each data domain node in the data domain cluster. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Administrative operations for the Dgraph (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Administrative operations for the Dgraph (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Use administrative operations to check Dgraph statistics, enable or disable diagnostic flags, without having to stop a running Dgraph. This section lists the supported administrative URLs, describes the functions of each URL, and defines the syntax of those URLs. (shortdesc] (topicmeta][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Syntax of administrative operations (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Syntax of administrative operations (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Administrative operations utilize the following syntax. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) List of administrative operations (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) List of administrative operations (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Administrative (or admin) operations listed in this topic allow you to control the behavior of the Dgraph processes in a data domain. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) help (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) help (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) /admin/datadomain?op=help returns the usage page for all of the administrative operations. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) flush (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) flush (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) /admin/datadomain?op=flush flushes the Dgraph cache. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) logroll (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) logroll (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) /admin/datadomain?op=logroll forces a query log roll. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) merge (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) merge (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) /admin/datadomain?op=merge forces a merge, and (optionally) changes the merge policy of a running Dgraph. In a data domain cluster of Dgraph nodes, this command is routed to the leader node of the data domain cluster where it is processed. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) ping (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) ping (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) /admin/datadomain?op=ping checks the aliveness of a Dgraph and returns a lightweight message. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) stats (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) stats (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) /admin/datadomain?op=stats returns the Dgraph Sever Statistics page. Note that this page is intended for use by Oracle Endeca Support only. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) statsreset (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) statsreset (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) /admin/datadomain?op=statsreset resets the Dgraph Server Statistics page. (shortdesc] (topicmeta] (topicref] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Managing the index merge policy for the data domain (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Managing the index merge policy for the data domain (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) This section describes how to set and manage a merge policy for each Endeca data domain. (shortdesc] (topicmeta][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Using a merge policy for incremental index updates (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Using a merge policy for incremental index updates (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) A merge policy determines how frequently the Dgraph process of the Endeca data domain merges incremental update generations in its index files, for a specific data domain. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Types of merge policies (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Types of merge policies (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can set the merge policy to one of two settings: balanced or aggressive. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Setting the merge policy (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Setting the merge policy (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can programmatically set the merge policy for the data domain by updating the Global Configuration Record. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Retrieving the merge policy (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Retrieving the merge policy (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can retrieve the Global Configuration Record to see the current setting for the merge policy. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Changing the merge policy (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Changing the merge policy (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The URL /admin/dataDomainName?op=merge command can be used to change the merge policy of a running Endeca data domain. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Forcing a merge (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Forcing a merge (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The URL /admin/dataDomainName?op=merge command can also be used to force a merge. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Linux unlimit settings for merges (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Linux unlimit settings for merges (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) For purposes of generation merging, it is recommended that you set the ulimit -v and -m parameters to unlimited. (shortdesc] (topicmeta] (topicref] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Managing Dgraph core dump files (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Managing Dgraph core dump files (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) In the rare case of a Dgraph crash, the Dgraph writes its core dump files on disk. (shortdesc] (topicmeta][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Managing Dgraph crash dump files on Windows (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Managing Dgraph crash dump files on Windows (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) On Windows, all Dgraph crash dump files are saved on disk by default. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Managing Dgraph core dump files on Linux (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Managing Dgraph core dump files on Linux (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) It is recommended to use the ulimit -c unlimited setting for the Dgraph process core dump files. Non-limited core files contain all Dgraph data that is resident in memory (RSS of the Dgraph process). (shortdesc] (topicmeta] (topicref] (topicref] (topicref][/map/topicref {"- map/topicref "}) [/map/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicmeta/navtitle {"- topic/navtitle "}) Endeca Server Logging (navtitle][/map/topicref/topicmeta/linktext {"- map/linktext "}) Endeca Server Logging (linktext][/map/topicref/topicmeta/shortdesc {"- map/shortdesc "}) This section describes three categories of logging in the Endeca Server: the logging of the Endeca Server Java process in the WebLogic Server domain, the Endeca data domain logging, and the Dgraph process logs. (shortdesc] (topicmeta][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Endeca Server logs (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Endeca Server logs (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Endeca Server uses Oracle Diagnostic Logging (ODL) for logging and its messages are written to WebLogic Server logs. (shortdesc] (topicmeta][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Log entry format (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Log entry format (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) This topic describes the format of Endeca Server log entries, including their message types and log levels. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Setting log levels (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Setting log levels (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The WebLogic Scripting Tool allows you to change log levels on the Endeca Server loggers. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Creating log handlers for debugging (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Creating log handlers for debugging (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) When you are debugging an Endeca Server problem, it is useful to create a log handler that only handles Endeca Server loggers and writes to an individual log file. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Customizing the HTTP access log (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Customizing the HTTP access log (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can customize the format of the default HTTP access log. (shortdesc] (topicmeta] (topicref] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Data domain logs (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Data domain logs (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The Endeca Server is responsible for keeping each Endeca data domain up and running, and therefore constantly monitors each data domain. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Dgraph request log and stdout/sterr log (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Dgraph request log and stdout/sterr log (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Any Dgraph node in a data domain creates two logs. (shortdesc] (topicmeta][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Identifying Dgraph connection errors (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Identifying Dgraph connection errors (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) If the Dgraph standard out log contains connection broken messages, although it may look like the problem occurred with the Dgraph, the actual cause of the problem is usually a broken connection between the server that hosts the front-end application and the server that hosts the Dgraph. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) List and syntax of configuration operations (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) List and syntax of configuration operations (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Use configuration (or config) operations to modify logging information for the Dgraph within the Endeca Server. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Logging variables for the Dgraph process (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Logging variables for the Dgraph process (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can use logging variables with configuration operations. This lets you obtain detailed information about Dgraph processing, to help diagnose unexpected application behavior or performance problems, without stopping and restarting the Dgraph or requiring a configuration update. (shortdesc] (topicmeta][/map/topicref/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Logging variable operation syntax (navtitle][/map/topicref/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Logging variable operation syntax (linktext][/map/topicref/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Dgraph logging variables are toggled using the /config/ddomain?op=log-enable&name=<variable-name> and /config/ddomain?op=log-disable&name=<variable-name> operations. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) List of supported logging variables (navtitle][/map/topicref/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) List of supported logging variables (linktext][/map/topicref/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The following table describes the supported logging variables that you can use with related config operations to toggle logging verbosity for specified features. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) log-enable (navtitle][/map/topicref/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) log-enable (linktext][/map/topicref/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The log-enable operation turns on verbose logging. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) log-disable (navtitle][/map/topicref/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) log-disable (linktext][/map/topicref/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The log-disable operation turns off verbose logging. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) log-status (navtitle][/map/topicref/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) log-status (linktext][/map/topicref/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The log-status operation returns a list of all logging variables with their values (true or false). (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) help (navtitle][/map/topicref/topicref/topicref/topicref/topicmeta/linktext {"- map/linktext "}) help (linktext][/map/topicref/topicref/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) /config/dstore?op=help returns the usage page for all of the config operations. (shortdesc] (topicmeta] (topicref] (topicref] (topicref] (topicref] [/map/reltable {"- map/reltable "}) [/map/reltable/relheader {"- map/relheader "}) [/map/reltable/relheader/relcolspec {"- map/relcolspec "}) (relcolspec][/map/reltable/relheader/relcolspec {"- map/relcolspec "}) (relcolspec] (relheader] [/map/reltable/relrow {"- map/relrow "}) [/map/reltable/relrow/relcell {"- map/relcell "}) [/map/reltable/relrow/relcell/topicref {"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta {"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle {"- topic/navtitle "}) List of administrative operations (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext {"- map/linktext "}) List of administrative operations (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Administrative (or admin) operations listed in this topic allow you to control the behavior of the Dgraph processes in a data domain. (shortdesc] (topicmeta] (topicref] (relcell][/map/reltable/relrow/relcell {"- map/relcell "}) [/map/reltable/relrow/relcell/topicref {"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta {"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle {"- topic/navtitle "}) help (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext {"- map/linktext "}) help (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc {"- map/shortdesc "}) /admin/datadomain?op=help returns the usage page for all of the administrative operations. (shortdesc] (topicmeta] (topicref] [/map/reltable/relrow/relcell/topicref {"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta {"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle {"- topic/navtitle "}) flush (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext {"- map/linktext "}) flush (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc {"- map/shortdesc "}) /admin/datadomain?op=flush flushes the Dgraph cache. (shortdesc] (topicmeta] (topicref] [/map/reltable/relrow/relcell/topicref {"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta {"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle {"- topic/navtitle "}) logroll (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext {"- map/linktext "}) logroll (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc {"- map/shortdesc "}) /admin/datadomain?op=logroll forces a query log roll. (shortdesc] (topicmeta] (topicref] [/map/reltable/relrow/relcell/topicref {"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta {"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle {"- topic/navtitle "}) merge (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext {"- map/linktext "}) merge (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc {"- map/shortdesc "}) /admin/datadomain?op=merge forces a merge, and (optionally) changes the merge policy of a running Dgraph. In a data domain cluster of Dgraph nodes, this command is routed to the leader node of the data domain cluster where it is processed. (shortdesc] (topicmeta] (topicref] [/map/reltable/relrow/relcell/topicref {"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta {"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle {"- topic/navtitle "}) ping (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext {"- map/linktext "}) ping (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc {"- map/shortdesc "}) /admin/datadomain?op=ping checks the aliveness of a Dgraph and returns a lightweight message. (shortdesc] (topicmeta] (topicref] [/map/reltable/relrow/relcell/topicref {"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta {"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle {"- topic/navtitle "}) stats (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext {"- map/linktext "}) stats (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc {"- map/shortdesc "}) /admin/datadomain?op=stats returns the Dgraph Sever Statistics page. Note that this page is intended for use by Oracle Endeca Support only. (shortdesc] (topicmeta] (topicref] [/map/reltable/relrow/relcell/topicref {"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta {"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle {"- topic/navtitle "}) statsreset (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext {"- map/linktext "}) statsreset (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc {"- map/shortdesc "}) /admin/datadomain?op=statsreset resets the Dgraph Server Statistics page. (shortdesc] (topicmeta] (topicref] (relcell] (relrow] [/map/reltable/relrow {"- map/relrow "}) [/map/reltable/relrow/relcell {"- map/relcell "}) [/map/reltable/relrow/relcell/topicref {"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta {"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle {"- topic/navtitle "}) merge (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext {"- map/linktext "}) merge (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc {"- map/shortdesc "}) /admin/datadomain?op=merge forces a merge, and (optionally) changes the merge policy of a running Dgraph. In a data domain cluster of Dgraph nodes, this command is routed to the leader node of the data domain cluster where it is processed. (shortdesc] (topicmeta] (topicref] (relcell][/map/reltable/relrow/relcell {"- map/relcell "}) [/map/reltable/relrow/relcell/topicref {"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta {"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle {"- topic/navtitle "}) Managing the index merge policy for the data domain (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext {"- map/linktext "}) Managing the index merge policy for the data domain (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc {"- map/shortdesc "}) This section describes how to set and manage a merge policy for each Endeca data domain. (shortdesc] (topicmeta] (topicref] (relcell] (relrow] (reltable][/map/reltable {"- map/reltable "}) [/map/reltable/relheader {"- map/relheader "}) [/map/reltable/relheader/relcolspec {"- map/relcolspec "}) (relcolspec][/map/reltable/relheader/relcolspec {"- map/relcolspec "}) (relcolspec] (relheader] [/map/reltable/relrow {"- map/relrow "}) [/map/reltable/relrow/relcell {"- map/relcell "}) [/map/reltable/relrow/relcell/topicref {"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta {"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle {"- topic/navtitle "}) List of supported logging variables (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext {"- map/linktext "}) List of supported logging variables (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The following table describes the supported logging variables that you can use with related config operations to toggle logging verbosity for specified features. (shortdesc] (topicmeta] (topicref] (relcell][/map/reltable/relrow/relcell {"- map/relcell "}) [/map/reltable/relrow/relcell/topicref {"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta {"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle {"- topic/navtitle "}) log-enable (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext {"- map/linktext "}) log-enable (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The log-enable operation turns on verbose logging. (shortdesc] (topicmeta] (topicref] [/map/reltable/relrow/relcell/topicref {"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta {"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle {"- topic/navtitle "}) log-disable (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext {"- map/linktext "}) log-disable (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The log-disable operation turns off verbose logging. (shortdesc] (topicmeta] (topicref] [/map/reltable/relrow/relcell/topicref {"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta {"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle {"- topic/navtitle "}) log-status (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext {"- map/linktext "}) log-status (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The log-status operation returns a list of all logging variables with their values (true or false). (shortdesc] (topicmeta] (topicref] [/map/reltable/relrow/relcell/topicref {"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta {"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle {"- topic/navtitle "}) help (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext {"- map/linktext "}) help (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc {"- map/shortdesc "}) /config/dstore?op=help returns the usage page for all of the config operations. (shortdesc] (topicmeta] (topicref] (relcell] (relrow] (reltable] (map]