Performing System Operations with the EAC

This section discusses operational tasks related to your Endeca application. It focuses on the recommended practice of using the Deployment Template to interact with the EAC, but mentions alternative methods of performing some tasks. It also lists essential administrative information related to EAC operations, such as pointers to EAC logs.

Options for provisioning the application
Provisioning is the task of defining the location and configuration of the Endeca resources (such as Forge, Dgidx and one or more Dgraphs) that control your Endeca application to the EAC.
Options for running system operations
You can run system operations using two alternative approaches—scripts that utilize the Deployment Template, or your own scripts provisioned in the EAC Admin Console of the Endeca Workbench.
Checking the status of EAC components
You can use several methods to check the status of your application's components that are provisioned to the EAC, such as Dgidx, Forge, and Dgraph.
Avoiding defunct EAC processes
On UNIX systems, the ps command may report a number of defunct EAC-originated processes. This is known and expected EAC behavior and it does not necessarily indicate a problem.
EAC memory usage
This topic outlines recommendations for optimizing EAC memory usage. For example, if a server is running more than one MDEX Engine and more than one EAC agent, you may encounter performance problems due to multiple EAC agent processes having a large memory footprint (amount of RAM consumed by the EAC agent processes).
Deployment Template and Endeca Workbench interaction
This topic summarizes information about Deployment Template and Endeca Workbench interaction.
Archiving the Dgraph log files
Your Dgraph files are archived automatically once you run a baseline update script with the Deployment Template. In addition, if you prefer to archive Dgraph files on a more granular basis, you can create a custom Deployment Template script that stops the MDEX Engine process, archives the Dgraph log files and restarts the Dgraph.
Releasing locks set by the Deployment Template in the EAC
In some instances, you may find it necessary to manually release locks that the Deployment Template scripts have put in the EAC on a particular component.
Removing components from your configuration
To remove inactive components you can use several options — stop and remove them in the Deployment Template, run initialize_services, use eaccmd, or use the EAC Console of Endeca Workbench.
Determining the state of the EAC with service URLs
You can use the following service URLs to determine whether the EAC Central Server or EAC Agent is running.
Logs for the EAC Central Server
Aside from log files associated with specific EAC components, utilities, and scripts, the EAC Central Server and its services generate log files in their workspace directories.
Changing the IP address for the EAC Central Server machine
This topic describes how to change the IP address of an EAC Central Server machine, in an environment featuring remote MDEXHost machines, where the AppConfig.xml files use host names rather than IP addresses for the machines.