While removing an Endeca application, do not simply remove the Endeca
application directories or delete EAC state directories
(ENDECA_CONF/state/eac*) from in the file system.
This leaves application artifacts, which can cause naming conflicts when creating a new project with the same name. Clients running Oracle ATG Commerce, having random Endeca application artifacts can interfere with Commerce Reference Store installation and with indexing functionality.
To completely remove an Endeca application follow below steps:
Step 1: Remove APP using runcommand
<Endeca-app-dir>\control\ runcommand.sh|bat --remove-app
CRS\control\runcommand.sh|bat --remove-app
Step 2: Drop the corresponding Record stores from CAS
Check names of application record stores registered in CAS.
$CAS_ROOT\bin>component- manager-cmd.bat/.sh list-components
Remove the record stores corresponding to your Endeca application. The record store names will be prefixed with the application name.
For example:
$CAS_ROOT/bin>component- manager-cmd.bat/.sh delete-component -n myAppName_en_data
$CAS_ROOT/bin>component- manager-cmd.bat/.sh delete-component -n myAppName_en_schema
$CAS_ROOT/bin>component- manager-cmd.bat/.sh delete-component -n myAppName_en_prules
$CAS_ROOT/bin>component- manager-cmd.bat/.sh delete-component -n myAppName_en_dimvals
Step 3: Finally, remove the Endeca application directory from the file system
This leaves application artifacts, which can cause naming conflicts when creating a new project with the same name. Clients running Oracle ATG Commerce, having random Endeca application artifacts can interfere with Commerce Reference Store installation and with indexing functionality.
To completely remove an Endeca application follow below steps:
Step 1: Remove APP using runcommand
<Endeca-app-dir>\control\
CRS\control\runcommand.sh|bat --remove-app
Step 2: Drop the corresponding Record stores from CAS
Check names of application record stores registered in CAS.
$CAS_ROOT\bin>component-
Remove the record stores corresponding to your Endeca application. The record store names will be prefixed with the application name.
For example:
$CAS_ROOT/bin>component-
$CAS_ROOT/bin>component-
$CAS_ROOT/bin>component-
$CAS_ROOT/bin>component-
Step 3: Finally, remove the Endeca application directory from the file system
Don't forget to remove the last-mile-crawls as well. Here's an Oracle Commerce document on this whole procedure
ReplyDeletehttps://docs.oracle.com/cd/E69533_01/CRS.11-3/CSAInstall/html/s0306removingtheeacapplicationsandcas01.html