Finally I could successfully launch Endeca Discover application in my Windows 7 box. Though I have done this multiple times in Linux box somehow I didn’t get it properly in Windows box in the past. I thought I should share the details for other’s benefit.
Endeca installers and version used.
- Oracle Endeca MDEX-6.4.1 (mdex_6.4.1.715066_x86_64pc-win32.exe)
- Oracle Endeca Platform Services-6.1.3 (platformservices613654721_x86_64pc-win32.exe)
- Oracle Endeca Tools and Frameworks-3.1.2 (V37717-01.zip)
- Oracle Endeca Experience Manager-2.1.2 (xmgrworkbench_2.1.2.618087_x86_64pc-win32.exe)
Note: You must download the correct version of Tools and Framework. There are two versions of Tools and Frameworks available in edelivery.oracle.com. I have used the version for Endeca Experience Manager. (V37717-01.zip)
Endeca Commerce with Experience Manager – Installation and Configuration steps.
First thing is that you should make sure that the user you used to log in to windows has got required administrator privileges like adding entry into registry and changing system environment variables.
- Install Oracle Endeca MDEX. (Normal windows wizard based installation)
- Set the ENDECA_MDEX_ROOT environment variable. (ENDECA_MDEX_ROOT=C:\Endeca\MDEX\6.4.1)
- Install the Oracle Endeca Platform Service and restart windows. (Normal windows wizard based installation)
- Unzip the V37717-01.zip file (Tools And Framework) into <<ENDECA_HOME>> (C:\Endeca)
- Open up a command prompt as administrator. (check this post to to see how to open a command prompt as administrator)
- Move to C:\Endeca\ToolsAndFrameworks\3.1.2\server\bin
- Execute install_service.bat (This should add “EndecaToolsService” into Windows Services)
- Open the windows services and start “EndecaToolsService” (to open the services type services.msc in the run window and enter)
- Install the Oracle Endeca Experience Manager. (Normal windows wizard based installation)
Verification.
There shall be six environment variables added to Windows system environment property.
- ENDECA_CONF = C:\Endeca\PlatformServices\workspace
- ENDECA_MDEX_ROOT = C:\Endeca\MDEX\6.4.1
- ENDECA_REFERENCE_DIR = C:\Endeca\PlatformServices\reference
- ENDECA_ROOT = C:\Endeca\PlatformServices\6.1.3
- ENDECA_TOOLS_CONF = C:\Endeca\ToolsAndFrameworks\3.1.2\server\workspace
- ENDECA_TOOLS_ROOT = C:\Endeca\ToolsAndFrameworks\3.1.2
There shall be three service added into windows services and all should be running.
- EndecaHTTPservice
- Endeca JCD
- EndecaToolsService
Verify that the workbench is installed properly.
Launch http://localhost:8006 (Refer Endeca documentation for username and password)
Deploying Endeca Discover reference application.
- Open up the command prompt as administrator. (check this post to to see how to open a command prompt as administrator)
- Move to C:\Endeca\MDEX\6.4.1 and run mdex_setup.bat and make sure that the path are set correctly.
- Create C:\Endeca\Apps directory if its not available already. You may choose a different location if you wish.
- Move to C:\Endeca\ToolsAndFrameworks\3.1.2\deployment_template\bin
- execute “deploy.bat –app C:\Endeca\ToolsAndFrameworks\3.1.2\reference\discover-data\deploy.xml”
- You will be promoted with few question, I think you should be able select default almost always. (see below screen grab to see what I have given)
- Move to C:\Endeca\Apps\Discover\control
- Run initialize_services.bat (Remember you must use a command window which you opened as administrator)
- Run load_baseline_test_data.bat
- Run baseline_update.bat
- Run promote_content.bat
- Launch a browser and check http://localhost:8006/discover
Screen shot of Oracle Endeca MDEX configuration.
Oracle Endeca Discover application configuration steps.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 |
C:\Endeca\ToolsAndFrameworks\3.1.2\deployment_template\bin>deploy.bat --app C:\Endeca\ToolsAndFramew orks\3.1.2\reference\discover-data\deploy.xml ------------------------------------------------------------------------------ Found version 6.1 of the Endeca IAP installed in directory C:\Endeca\PlatformServices\6.1.3. If either the version or location are incorrect, type 'Q' to quit and adjust your ENDECA_ROOT environment variable. Press enter to continue with these settings. Continue? ------------------------------------------------------------------------------ Deployment Template installation script. This script creates the directory structure for your deployment and installs configuration files and scripts into the directory structure. 09/27/2013 00:47:08 [deploy.pl] INFO: Starting deployment template installation. ------------------------------------------------------------------------------ The following app modules were specified on the command line argument: C:\Endeca\ToolsAndFrameworks\3.1.2\reference\discover-data\deploy.xml Modules may be deployed standalone or on top of a base deployment type. Do you want to install a base deployment with the specified module(s)? Install base deployment? [Y/N]: Y 09/27/2013 00:47:29 [AppDescriptorReader] INFO: Parsing application descriptor file C:\Endeca\ToolsAndFrameworks\3.1.2\reference\discover-data\deploy.xml. 09/27/2013 00:47:29 [AppDescriptorReader] INFO: Parsing application descriptor file C:\Endeca\ToolsAndFrameworks\3.1.2\deployment_template\app-templates\base_descriptor.xml. ------------------------------------------------------------------------------ Enter a short name for your application. Note: The name must conform to this regular expression: ^[a-zA-Z0-9]+$ [default: Discover] Choosing a different application name may require additional configuration on your web application. Application name: ------------------------------------------------------------------------------ Specify the path into which the application will be deployed. The specified directory must exist and cannot contain spaces. For example, to deploy into c:\apps\Discover, specify the path as c:\apps. Deployment directory: C:\Endeca\Apps ------------------------------------------------------------------------------ Specify the port on which the Endeca Application Controller is running. This is configured in the server.xml file in the workspace of the Endeca software install and should be the same for all applications deployed in this environment. Ports must be in the range 1024-65535 [default: 8888]. EAC port: 8888 09/27/2013 00:47:55 [deploy.pl] INFO: Deploying application into C:\Endeca\Apps\Discover ------------------------------------------------------------------------------ What port is the Workbench running? [Default: 8006] 8006 ------------------------------------------------------------------------------ What port should be used for the Live Dgraph? [Default: 15000] 15000 ------------------------------------------------------------------------------ What port should be used for the Authoring Dgraph? [Default: 15002] 15002 ------------------------------------------------------------------------------ What port should be used for LogServer? [Default: 15010] 15010 09/27/2013 00:48:15 [AppDescriptorReader] INFO: Parsing application descriptor file C:\Endeca\ToolsAndFrameworks\3.1.2\deployment_template\app-templates\base_descriptor.xml. 09/27/2013 00:48:15 [deploy.pl] INFO: Processing install with id 'Dgraph' 09/27/2013 00:48:16 [AppDescriptorReader] INFO: Parsing application descriptor file C:\Endeca\ToolsAndFrameworks\3.1.2\reference\discover-data\deploy.xml. 09/27/2013 00:48:16 [deploy.pl] INFO: Processing install with id 'DefaultTemplateManagerApp' 09/27/2013 00:48:18 [deploy.pl] INFO: Application successfully deployed. C:\Endeca\ToolsAndFrameworks\3.1.2\deployment_template\bin>cd C:\Endeca\Apps\Discover\control C:\Endeca\Apps\Discover\control>initialize_services.bat Setting EAC provisioning and performing initial setup... [09.27.13 00:49:06] INFO: Checking definition from AppConfig.xml against existing EAC provisioning. [09.27.13 00:49:06] INFO: Setting definition for application 'Discover'. [09.27.13 00:49:08] INFO: Setting definition for host 'AuthoringMDEXHost'. [09.27.13 00:49:08] INFO: Setting definition for host 'LiveMDEXHostA'. [09.27.13 00:49:09] INFO: Setting definition for host 'ReportGenerationHost'. [09.27.13 00:49:09] INFO: Setting definition for host 'WorkbenchHost'. [09.27.13 00:49:09] INFO: Setting definition for host 'ITLHost'. [09.27.13 00:49:09] INFO: Setting definition for component 'AuthoringDgraph'. [09.27.13 00:49:09] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgidx-output'. [09.27.13 00:49:11] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-partials-forge-ou tput'. [09.27.13 00:49:13] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-partials-cumulati ve-partials'. [09.27.13 00:49:14] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-workbench-dgraph- config'. [09.27.13 00:49:15] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgraphs-local-dgr aph-input'. [09.27.13 00:49:16] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgraphs-local-cum ulative-partials'. [09.27.13 00:49:18] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_-data-dgraphs-local-dgr aph-config'. [09.27.13 00:49:19] INFO: Setting definition for component 'DgraphA1'. [09.27.13 00:49:19] INFO: Setting definition for script 'PromoteAuthoringToLive'. [09.27.13 00:49:20] INFO: Setting definition for custom component 'WorkbenchManager'. [09.27.13 00:49:20] INFO: Updating provisioning for host 'ITLHost'. [09.27.13 00:49:20] INFO: Updating definition for host 'ITLHost'. [09.27.13 00:49:21] INFO: [ITLHost] Starting shell utility 'mkpath_-'. [09.27.13 00:49:21] INFO: [ITLHost] Starting shell utility 'mkpath_-data-workbench-temp'. [09.27.13 00:49:22] INFO: Setting definition for custom component 'IFCR'. [09.27.13 00:49:22] INFO: Updating provisioning for host 'ITLHost'. [09.27.13 00:49:22] INFO: Updating definition for host 'ITLHost'. [09.27.13 00:49:22] INFO: [ITLHost] Starting shell utility 'mkpath_-'. [09.27.13 00:49:24] INFO: [ITLHost] Starting shell utility 'mkpath_-'. [09.27.13 00:49:25] INFO: Setting definition for component 'LogServer'. [09.27.13 00:49:26] INFO: [ReportGenerationHost] Starting shell utility 'mkpath_-reports-input'. [09.27.13 00:49:27] INFO: Setting definition for script 'DaySoFarReports'. [09.27.13 00:49:27] INFO: Setting definition for script 'DailyReports'. [09.27.13 00:49:27] INFO: Setting definition for script 'WeeklyReports'. [09.27.13 00:49:28] INFO: Setting definition for script 'DaySoFarHtmlReports'. [09.27.13 00:49:28] INFO: Setting definition for script 'DailyHtmlReports'. [09.27.13 00:49:28] INFO: Setting definition for script 'WeeklyHtmlReports'. [09.27.13 00:49:28] INFO: Setting definition for component 'WeeklyReportGenerator'. [09.27.13 00:49:29] INFO: Setting definition for component 'DailyReportGenerator'. [09.27.13 00:49:29] INFO: Setting definition for component 'DaySoFarReportGenerator'. [09.27.13 00:49:29] INFO: Setting definition for component 'WeeklyHtmlReportGenerator'. [09.27.13 00:49:30] INFO: Setting definition for component 'DailyHtmlReportGenerator'. [09.27.13 00:49:30] INFO: Setting definition for component 'DaySoFarHtmlReportGenerator'. [09.27.13 00:49:30] INFO: Setting definition for script 'BaselineUpdate'. [09.27.13 00:49:30] INFO: Setting definition for script 'PartialUpdate'. [09.27.13 00:49:30] INFO: Setting definition for component 'Forge'. [09.27.13 00:49:31] INFO: [ITLHost] Starting shell utility 'mkpath_-data-incoming'. [09.27.13 00:49:32] INFO: Setting definition for component 'PartialForge'. [09.27.13 00:49:32] INFO: [ITLHost] Starting shell utility 'mkpath_-data-partials-incoming'. [09.27.13 00:49:34] INFO: Setting definition for component 'Dgidx'. [09.27.13 00:49:34] INFO: Definition updated. [09.27.13 00:49:34] INFO: Provisioning site from prototype... [09.27.13 00:49:35] INFO: Finished provisioning site from prototype. [09.27.13 00:49:35] INFO: Uploading config files to Workbench. [09.27.13 00:49:35] INFO: [ITLHost] Starting shell utility 'emgr_update_update_mgr_settings'. [09.27.13 00:49:40] INFO: Finished uploading config files to Workbench. Finished updating EAC. Importing sample content... [09.27.13 00:49:41] INFO: Checking definition from AppConfig.xml against existing EAC provisioning. [09.27.13 00:49:42] INFO: Definition has not changed. [09.27.13 00:49:42] INFO: Packaging contents for upload... [09.27.13 00:49:42] INFO: Finished packaging contents. [09.27.13 00:49:42] INFO: Uploading contents to: http://thosan-VAIO:8006/ifcr/sites/Discover/ [09.27.13 00:49:43] INFO: Finished uploading contents. [09.27.13 00:49:44] INFO: Checking definition from AppConfig.xml against existing EAC provisioning. [09.27.13 00:49:45] INFO: Definition has not changed. [09.27.13 00:49:45] INFO: Packaging contents for upload... [09.27.13 00:49:45] INFO: Finished packaging contents. [09.27.13 00:49:45] INFO: Uploading contents to: http://thosan-VAIO:8006/ifcr/sites/Discover/content [09.27.13 00:49:45] INFO: Finished uploading contents. [09.27.13 00:49:47] INFO: Checking definition from AppConfig.xml against existing EAC provisioning. [09.27.13 00:49:47] INFO: Definition has not changed. [09.27.13 00:49:48] INFO: Packaging contents for upload... [09.27.13 00:49:48] INFO: Finished packaging contents. [09.27.13 00:49:48] INFO: Uploading contents to: http://thosan-VAIO:8006/ifcr/sites/Discover/pages [09.27.13 00:49:48] INFO: Finished uploading contents. Finished importing sample content Importing editors configuration... [09.27.13 00:49:49] INFO: Checking definition from AppConfig.xml against existing EAC provisioning. [09.27.13 00:49:50] INFO: Definition has not changed. [09.27.13 00:49:50] INFO: Packaging contents for upload... [09.27.13 00:49:50] INFO: Finished packaging contents. [09.27.13 00:49:50] INFO: Uploading contents to: http://thosan-VAIO:8006/ifcr/sites/Discover/configu ration/tools/xmgr [09.27.13 00:49:50] INFO: Finished uploading contents. Finished importing editors configuration Importing media... [09.27.13 00:49:51] INFO: Checking definition from AppConfig.xml against existing EAC provisioning. [09.27.13 00:49:52] INFO: Definition has not changed. [09.27.13 00:49:52] INFO: Packaging contents for upload... [09.27.13 00:49:52] INFO: Finished packaging contents. [09.27.13 00:49:52] INFO: Uploading contents to: http://thosan-VAIO:8006/ifcr/sites/Discover/media [09.27.13 00:49:53] INFO: Finished uploading contents. Finished importing media Importing templates... Removing existing cartridge templates for Discover Setting new cartridge templates for Discover Finished setting templates Finished importing templates C:\Endeca\Apps\Discover\control>load_baseline_test_data.bat C:\Endeca\Apps\Discover\config\script\..\..\test_data\baseline\camerastore.xml.gz 1 file(s) copied. Setting flag 'baseline_data_ready' in the EAC. C:\Endeca\Apps\Discover\control>baseline_update.bat C:\Endeca\Apps\Discover\control>echo %ENDECA_MDEX_ROOT% C:\Endeca\MDEX\6.4.1 C:\Endeca\Apps\Discover\control>baseline_update.bat [09.27.13 00:50:54] INFO: Checking definition from AppConfig.xml against existing EAC provisioning. [09.27.13 00:50:54] INFO: Definition has not changed. [09.27.13 00:50:54] INFO: Starting baseline update script. [09.27.13 00:50:54] INFO: Acquired lock 'update_lock'. [09.27.13 00:50:55] INFO: [ITLHost] Starting shell utility 'move_-_to_processing'. [09.27.13 00:50:56] INFO: [ITLHost] Starting copy utility 'fetch_config_to_input_for_forge_Forge'. [09.27.13 00:50:57] INFO: [ITLHost] Starting backup utility 'backup_log_dir_for_component_Forge'. [09.27.13 00:50:58] INFO: [ITLHost] Starting component 'Forge'. [09.27.13 00:51:08] INFO: [ITLHost] Starting backup utility 'backup_log_dir_for_component_Dgidx'. [09.27.13 00:51:10] INFO: [ITLHost] Starting component 'Dgidx'. [09.27.13 00:51:32] INFO: [AuthoringMDEXHost] Starting copy utility 'copy_index_to_host_AuthoringMDE XHost_AuthoringDgraph'. [09.27.13 00:51:33] INFO: Applying index to dgraphs in restart group 'A'. [09.27.13 00:51:33] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_dgraph-input-new'. [09.27.13 00:51:34] INFO: [AuthoringMDEXHost] Starting copy utility 'copy_index_to_temp_new_dgraph_i nput_dir_for_AuthoringDgraph'. [09.27.13 00:51:35] INFO: [AuthoringMDEXHost] Starting shell utility 'move_dgraph-input_to_dgraph-in put-old'. [09.27.13 00:51:36] INFO: [AuthoringMDEXHost] Starting shell utility 'move_dgraph-input-new_to_dgrap h-input'. [09.27.13 00:51:38] INFO: [AuthoringMDEXHost] Starting backup utility 'backup_log_dir_for_component_ AuthoringDgraph'. [09.27.13 00:51:39] INFO: [AuthoringMDEXHost] Starting component 'AuthoringDgraph'. [09.27.13 00:51:50] INFO: Publishing Workbench 'authoring' configuration to MDEX 'AuthoringDgraph' [09.27.13 00:51:50] INFO: Pushing authoring content to dgraph: AuthoringDgraph [09.27.13 00:52:02] INFO: Finished pushing content to dgraph. [09.27.13 00:52:02] INFO: [AuthoringMDEXHost] Starting shell utility 'rmdir_dgraph-input-old'. [09.27.13 00:52:03] INFO: [LiveMDEXHostA] Starting shell utility 'cleanDir_local-dgraph-input'. [09.27.13 00:52:05] INFO: [LiveMDEXHostA] Starting copy utility 'copy_index_to_host_LiveMDEXHostA_Dg raphA1'. [09.27.13 00:52:15] INFO: Applying index to dgraphs in restart group '1'. [09.27.13 00:52:15] INFO: [LiveMDEXHostA] Starting shell utility 'mkpath_dgraph-input-new'. [09.27.13 00:52:17] INFO: [LiveMDEXHostA] Starting copy utility 'copy_index_to_temp_new_dgraph_input _dir_for_DgraphA1'. [09.27.13 00:52:18] INFO: [LiveMDEXHostA] Starting shell utility 'move_dgraph-input_to_dgraph-input- old'. [09.27.13 00:52:19] INFO: [LiveMDEXHostA] Starting shell utility 'move_dgraph-input-new_to_dgraph-in put'. [09.27.13 00:52:20] INFO: [LiveMDEXHostA] Starting backup utility 'backup_log_dir_for_component_Dgra phA1'. [09.27.13 00:52:21] INFO: [LiveMDEXHostA] Starting component 'DgraphA1'. [09.27.13 00:52:27] INFO: Publishing Workbench 'live' configuration to MDEX 'DgraphA1' [09.27.13 00:52:27] INFO: Pushing live content to dgraph: DgraphA1 [09.27.13 00:52:27] INFO: Finished pushing content to dgraph. [09.27.13 00:52:27] INFO: [LiveMDEXHostA] Starting shell utility 'rmdir_dgraph-input-old'. [09.27.13 00:52:28] INFO: [ITLHost] Starting copy utility 'fetch_post_forge_dimensions_to_ws_temp_di r_C-Endeca-Apps-Discover-config-script-data-workbench-temp'. [09.27.13 00:52:29] INFO: Uploading post-Forge Dimensions to Workbench. [09.27.13 00:52:29] INFO: [ITLHost] Starting shell utility 'emgr_update_set_post_forge_dims'. [09.27.13 00:52:39] INFO: [ITLHost] Starting backup utility 'backup_state_dir_for_component_Forge'. [09.27.13 00:52:40] INFO: [ITLHost] Starting backup utility 'backup_index_Dgidx'. [09.27.13 00:52:42] INFO: [ReportGenerationHost] Starting backup utility 'backup_log_dir_for_compone nt_LogServer'. [09.27.13 00:52:43] INFO: [ReportGenerationHost] Starting component 'LogServer'. [09.27.13 00:52:44] INFO: Released lock 'update_lock'. [09.27.13 00:52:44] INFO: Baseline update script finished. C:\Endeca\Apps\Discover\control>promote_content.bat [09.27.13 00:56:09] INFO: Checking definition from AppConfig.xml against existing EAC provisioning. [09.27.13 00:56:10] INFO: Definition has not changed. [09.27.13 00:56:10] INFO: Promoting IFCR content... [09.27.13 00:56:11] INFO: Finished promoting IFCR content. C:\Endeca\Apps\Discover\control> |
while running this cmd am getting error
D:\Endeca\ToolsAndFrameworks\3.1.2\deployment_template\bin>deploy.bat -app D:\En
deca\ToolsAndFrameworks\3.1.2\reference\discover-data\deploy.xml
10/13/2013 14:38:58 [deploy.pl] WARN: Unknown command line argument ûapp.
Did you miss one “-”? it should be deploy.bat –app deploy.xml
yeah i have missed one – thanks..
now i am getting following error
D:\Endeca\Apps\discover\control>initialize_services.bat
[10.14.13 04:06:16] SEVERE: Caught exception while querying for defined applicat
ion list.
Occurred while executing line 18 of valid BeanShell script:
[[
15|
16| // If the application is already defined
17| // log an error and exit with code 1
18| if (app.isDefined()) {
19| log.severe("An application already exists with the name, \"" + provOb
j.getAppName() + "\". " +
20| "Please use the '--force' option if you want to replace all
existing configuration.");
21| System.exit(1);
]]
[10.14.13 04:06:16] SEVERE: Caught an exception while invoking method ‘run’ on o
bject ‘AssertNotDefined’. Releasing locks.
Caused by java.lang.reflect.InvocationTargetException
sun.reflect.NativeMethodAccessorImpl invoke0 – null
Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException
com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript – Error executing
valid BeanShell script.
Caused by com.endeca.soleng.eac.toolkit.exception.EacCommunicationException
com.endeca.soleng.eac.toolkit.application.Application isDefined – Caught excepti
on while querying for defined application list.
Caused by org.apache.axis.AxisFault
org.apache.axis.AxisFault makeFault – ; nested exception is:
java.net.SocketException: Permission denied: connect
Caused by java.net.SocketException
java.net.PlainSocketImpl socketConnect – Permission denied: connect
D:\Endeca\Apps\discover\control>
I think this is happening because you are using a command prompt in non admin mode. Now you should remove the application and recreate it. Start all over again in a command prompt you opened up in admin mode.
Everything installed properly for me. But at the when I’m hitting the url http://localhost:8006/discover/
I’m getting Page Not Found error. What is the solution? Please post ASAP.
hi Tuhin, I assume that you are using windows. please check all the services mentioned in the post are started. (1.EndecaHTTPservice 2. Endeca 3.JCDEndecaToolsService)
All my services are running. But when trying to run Baseline Update I’m getting following error:
C:\Endeca\Apps\Discover\control>baseline_update.bat
[11.22.13 00:46:34] INFO: Checking definition from AppConfig.xml against existin
g EAC provisioning.
[11.22.13 00:46:35] INFO: Definition has not changed.
[11.22.13 00:46:35] INFO: Starting baseline update script.
[11.22.13 00:46:35] INFO: Acquired lock ‘update_lock’.
[11.22.13 00:46:35] INFO: [ITLHost] Starting shell utility ‘move_-_to_processing
‘.
[11.22.13 00:46:37] INFO: [ITLHost] Starting copy utility ‘fetch_config_to_input
_for_forge_Forge’.
[11.22.13 00:46:38] INFO: [ITLHost] Starting backup utility ‘backup_log_dir_for_
component_Forge’.
[11.22.13 00:46:39] INFO: [ITLHost] Starting component ‘Forge’.
[11.22.13 00:46:41] SEVERE: Batch component ‘Forge’ failed. Refer to component
logs in C:\Endeca\Apps\Discover\config\script\..\..\.\logs\forges\Forge on host
ITLHost.
Occurred while executing line 23 of valid BeanShell script:
[[
20|
21| // archive logs and run ITL
22| Forge.archiveLogDir();
23| Forge.run();
24| Dgidx.archiveLogDir();
25| Dgidx.run();
26|
]]
[11.22.13 00:46:41] SEVERE: Caught an exception while invoking method ‘run’ on o
bject ‘BaselineUpdate’. Releasing locks.
Caused by java.lang.reflect.InvocationTargetException
sun.reflect.NativeMethodAccessorImpl invoke0 – null
Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException
com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript – Error executing
valid BeanShell script.
Caused by com.endeca.soleng.eac.toolkit.exception.EacComponentControlException
com.endeca.soleng.eac.toolkit.component.BatchComponent run – Batch component ‘F
orge’ failed. Refer to component logs in C:\Endeca\Apps\Discover\config\script\.
.\..\.\logs\forges\Forge on host ITLHost.
[11.22.13 00:46:41] INFO: Released lock ‘update_lock’.
Please help me with the solutions. I checked the log but it was empty(forge.start)
This normally happen when you open up windows command window in non admin mode. remove the app and recreate it in admin mode command prompt.
I did all these steps, still when I open http://localhost:8006/discover-authoring/, I get unknown error page
I went to admin console, and found my MDEX was not started. I tried starting it, but I’m getting below error
An error occurred while trying to start the component: ENDECA_MDEX_ROOT is required for this component,but eac.properties does not contain a valid ENDECA_MDEX_ROOT definition.: ENDECA_MDEX_ROOT is required for this component,but eac.properties does not contain a valid ENDECA_MDEX_ROOT definition.
Please let me know how to fix this.
Run ENDECA_HOME\MDEX\6.4.1\bin\export-config.bat and ENDECA_HOME\MDEX\6.4.1\mdex_setup.bat and see if all the env variables are set.
Yes they are set properly. As you had said above, I have 6 endeca variables set
hi Avinash, Open ENDECA_HOME\PlatformServices\workspace\conf\eac.properties and see if you have com.endeca.mdexRoot=C:\\Endeca\\MDEX\\6.4.1 in it. Ideally speaking all these properties would be set correctly as part of application initialization process. If these properties are not added correctly please remove your Endeca application and recreate it.
Pingback: Oracle Endeca Commerce Overview
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
while i’m start initialize_services.bat its shows an Error
i checked log file : \..\Endeca\PlatformServices\workspace\logs\shell
> “ERROR: Could not open acquire_lock.status.”
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[03.07.14 17:35:01] INFO: Uploading config files to Workbench.
[03.07.14 17:35:01] INFO: [ITLHost] Starting shell utility 'emgr_update_update_mgr_settings'.
[03.07.14 17:35:03] WARNING: An error occurred while attempting to set instance configuration in Workbench. This action requires all locks in Workbench to be available. If the utility log includes errors associated with resource locks, ensure that users are out of Workbench and break locks in Workbench before re-running this action.
[03.07.14 17:35:03] SEVERE: Utility 'emgr_update_update_mgr_settings' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
Occurred while executing line 4 of valid BeanShell script:
[[
1|
2|
3| IFCR.provisionSite();
4| WorkbenchManager.updateWsConfig();
5|
6|
]]
[03.07.14 17:35:03] SEVERE: Caught an exception while invoking method 'run' on object 'InitialSetup'. Releasing locks.
Caused by java.lang.reflect.InvocationTargetException
sun.reflect.NativeMethodAccessorImpl invoke0 – null
Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException
com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript – Error executing valid BeanShell script.
Caused by com.endeca.soleng.eac.toolkit.exception.EacComponentControlException
com.endeca.soleng.eac.toolkit.utility.Utility run – Utility 'emgr_update_update_mgr_settings' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
=====================================================================================
And also while i'm start baseline_update.bat its shows an Error
[03.07.14 17:36:41] INFO: Uploading post-Forge Dimensions to Workbench.
[03.07.14 17:36:41] INFO: [ITLHost] Starting shell utility 'emgr_update_set_post_forge_dims'.
[03.07.14 17:36:42] SEVERE: Utility 'emgr_update_set_post_forge_dims' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
Occurred while executing line 32 of valid BeanShell script:
[[
29|
30| WorkbenchManager.cleanDirs();
31| Forge.getPostForgeDimensions();
32| WorkbenchManager.updateWsDimensions();
33|
34| // archive state files, index
35| Forge.archiveState();
]]
[03.07.14 17:36:42] SEVERE: Caught an exception while invoking method 'run' on object 'BaselineUpdate'. Releasing locks.
Caused by java.lang.reflect.InvocationTargetException
sun.reflect.NativeMethodAccessorImpl invoke0 – null
Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException
com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript – Error executing valid BeanShell script.
Caused by com.endeca.soleng.eac.toolkit.exception.EacComponentControlException
com.endeca.soleng.eac.toolkit.utility.Utility run – Utility 'emgr_update_set_post_forge_dims' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
[03.07.14 17:36:42] INFO: Released lock 'update_lock'.
==========================================================================
please reply ASAP……
Hello,
I am successfully able to open the localhost:8006/discover page after following the deployment process.
However, when I deploy a new application ‘XYZ’ (using Discover as the reference application) by following the same deployment process and try to open localhost:8006/XYZ page I get a PAGE NOT FOUND error although I am able to open the workbench port and the MDEX engine port successfully.
Can you please let me know if there are any additional steps to be followed while deploying the application apart from promote_content so that the application is visible on the UI.
Thanks !
Actually I don’t have the JCD windows service , which app I did miss?
also How to run MDEX engine if it is not running?
Importing templates…
Removing existing cartridge templates for CRS
ERROR: Could not open acquire_lock.status.
Failed to import templates.
Struggling from 5 days..
If any one knows why iam getting this error please let me know …