Endeca 'InitDataStore.grf' failed

Hi All,
I am new to Endeca Extensions for EBS.
I need to load some custom data to be loaded to Endeca Data Store, for that initially I am trying to create Data store by running "InitDataStore.grf' graph which is failing with below log..
Element [1331002769234:InitDataStore]-Phase 0 can't be initialized.
        at org.jetel.graph.TransformationGraph.init(TransformationGraph.java:465)
        at org.jetel.graph.runtime.EngineInitializer.initGraph(EngineInitializer.java:260)
        at com.cloveretl.server.c.h.f(Unknown Source)
        at com.cloveretl.server.c.h.a(Unknown Source)
        at com.cloveretl.server.c.h.executeGraph(Unknown Source)
        at com.cloveretl.server.c.j.executeGraph(Unknown Source).............
Caused by: WEB_SERVICE_CLIENT0 ...FAILED !
        at org.jetel.graph.Phase.init(Phase.java:162)
        at org.jetel.graph.TransformationGraph.init(TransformationGraph.java:463)
        ... 55 more
Caused by: Unable to establish Web Service proxy.
        at com.opensys.cloveretl.component.WebServiceClient.initializeWSMessenger(WebServiceClient.java:685)
        at com.opensys.cloveretl.component.WebServiceClient.init(WebServiceClient.java:252)
        at org.jetel.graph.Phase.init(Phase.java:157)
        ... 56 more
Caused by: com.opensys.cloveretl.component.ws.exception.WSMessengerConfigurationException: Unable to establish WSDL analyzer.
        at com.opensys.cloveretl.component.ws.proxy.AsyncMessenger.init(AsyncMessenger.java:179)
        at com.opensys.cloveretl.component.WebServiceClient.initializeWSMessenger(WebServiceClient.java:683)
        ... 58 more
Caused by: com.opensys.cloveretl.component.ws.exception.WSDLAnalyzeException: Unable to read WSDL file from location 'http://localhost:7770/ws/control?wsdl'.
        at com.opensys.cloveretl.component.ws.WSDLAnalyzer.<init>(WSDLAnalyzer.java:400)
        at com.opensys.cloveretl.component.ws.proxy.AsyncMessenger.init(AsyncMessenger.java:176)
        ... 59 more
Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: Wsdl not found http://localhost:7770/ws/control?wsdl
        at oracle.j2ee.ws.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:289)
        at oracle.j2ee.ws.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:278)
        at com.opensys.cloveretl.component.ws.WSDLAnalyzer.<init>(WSDLAnalyzer.java:376)
        ... 60 more
Note: I have my Endeca Server is located in different machine and I am trying to run this graph from Clover Server / Clover Client and getting the above error.
Could anyone please help me to resolve this error?
Thanks,
Harish

If you are running Integrator workbench from a different machine to Endeca Server, can you review your workspace.prm file and check the settings for ENDECA_SERVER_HOST etc.?

Similar Messages

Endeca Utility 'backup_log_dir_for_component_AuthoringDgraph' failed

I am getting error when i am executing baseline update script on windows. The forge is happening fine after which the script is throwing error.
[06.25.14 21:04:38] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[06.25.14 21:04:39] INFO: Definition has not changed.
[06.25.14 21:04:39] INFO: Starting baseline update script.
[06.25.14 21:04:39] INFO: Acquired lock 'update_lock'.
[06.25.14 21:04:39] INFO: [ITLHost] Starting shell utility 'cleanDir_processing'.
[06.25.14 21:04:40] INFO: [ITLHost] Starting shell utility 'cleanDir_forge-output'.
[06.25.14 21:04:41] INFO: [ITLHost] Starting shell utility 'cleanDir_dgidx-output'.
[06.25.14 21:04:42] INFO: [ITLHost] Starting shell utility 'move_-_to_processing'.
[06.25.14 21:04:44] INFO: [ITLHost] Starting copy utility 'fetch_config_to_input_for_forge_Forge'.
[06.25.14 21:04:45] INFO: [ITLHost] Starting backup utility 'backup_log_dir_for_component_Forge'.
[06.25.14 21:04:46] INFO: [ITLHost] Starting component 'Forge'.
[06.25.14 21:04:55] INFO: [ITLHost] Starting backup utility 'backup_log_dir_for_component_Dgidx'.
[06.25.14 21:04:56] INFO: [ITLHost] Starting component 'Dgidx'.
[06.25.14 21:05:11] INFO: [AuthoringMDEXHost] Starting shell utility 'cleanDir_local-dgraph-input'.
[06.25.14 21:05:12] INFO: [AuthoringMDEXHost] Starting shell utility 'rmdir_dgraph-input-old'.
[06.25.14 21:05:13] INFO: [AuthoringMDEXHost] Starting copy utility 'copy_index_to_host_AuthoringMDEXHost_AuthoringDgraph'.
[06.25.14 21:05:14] INFO: Applying index to dgraphs in restart group 'A'.
[06.25.14 21:05:14] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_dgraph-input-new'.
[06.25.14 21:05:16] INFO: [AuthoringMDEXHost] Starting copy utility 'copy_index_to_temp_new_dgraph_input_dir_for_AuthoringDgraph'.
[06.25.14 21:05:17] INFO: [AuthoringMDEXHost] Starting shell utility 'move_dgraph-input_to_dgraph-input-old'.
[06.25.14 21:05:18] INFO: [AuthoringMDEXHost] Starting shell utility 'move_dgraph-input-new_to_dgraph-input'.
[06.25.14 21:05:19] INFO: [AuthoringMDEXHost] Starting backup utility 'backup_log_dir_for_component_AuthoringDgraph'.
[06.25.14 21:05:20] SEVERE: Utility 'backup_log_dir_for_component_AuthoringDgraph' failed.
Occurred while executing line 5 of valid BeanShell script:
2|
3|    AuthoringDgraphCluster.cleanDirs();
4|    AuthoringDgraphCluster.copyIndexToDgraphServers();
5|    AuthoringDgraphCluster.applyIndex();
6|
7|    LiveDgraphCluster.cleanDirs();
8|    LiveDgraphCluster.copyIndexToDgraphServers();
[06.25.14 21:05:20] SEVERE: Error executing valid BeanShell script.Occurred while executing line 28 of valid BeanShell script:
25|        Dgidx.run();
26|
27|        // distributed index, update Dgraphs
28|        DistributeIndexAndApply.run();
29|
30|        WorkbenchManager.cleanDirs();
31|        Forge.getPostForgeDimensions();
[06.25.14 21:05:20] 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.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 runInParallel - Utility 'backup_lo
g_dir_for_component_AuthoringDgraph' failed.
[06.25.14 21:05:20] INFO: Released lock 'update_lock'.
In the AuthoringDgraph log it is showing below message.
FATAL
06/25/14 14:39:40.954 UTC (1403707180954)
DGRAPH
{dgraph,baseline}
Rapid updates are not supported for datasets that do not have a record specification model specified in the record spec file.
Stemming should be enabled for 1 languages

Hello,
I believe there are two different issues that may be occurring here, so we can start with the easiest one first, the error message in AuthoringDgraph. The error message is being triggered as it can't find a property within your records that has been flagged as a Record Specifier (aka Record Spec or RecSpec). In the Endeca world, this is similar to what a Primary Key on a table would accomplish in a relational database. These Record Specs are used in many ways for record retrieval, but it's not neccessary to have one put in place.
If you don't specify a property to be a Record Spec, than Endeca will create one for you. However - and this is where the error message comes in - you cannot perform updates to the data, known as a Partial Update. Since Endeca hasn't been told what property will uniquely represent a specific record, it can't receive updates to update/delete them. That's where the "Rapid Updates" comes into play.
There are two choices for this, firstly specify a property as a Record Spec, either through Developer Studio, or through the IOC/CSV overrides if you're using the product catalog integration method (what ATG uses to send data to Endeca). The second option is to disable Rapid Update (partial updates) functionality in your index - you'll need to comment out references to "partial" directories in the various Dgraph XML configurations in your config/scripts directory. However, that does go against Endeca Best Practices which are to always have a Record Spec.
And now onto the second issue, the error with the "backup_log_dir_for_component_AuthoringDgraph" script. This isn't an uncommon type of error, and may be unrelated to the issue above. The usual culprits for this are permission errors, inability to obtain a lock, etc. These scripts are run by the EAC and not the application, so are stored in a different location.
Firstly, find the installation directory for Platform Services on your system. Inside it should be a logging directory, and you're looking for workspace/logs/utility/<appName>.backup_log_dir_for_component_AuthoringDgraph.txt inside there. Open up that file, and it should help to clarify what the issue is - if not, then please post it's contents here and we can delve deeper.
Best,
- Jeff

Getting the below error when running the Baseline.grf for the first time

I am getting the below error when running the Baseline.grf for the first time.
Appreciate your support in resolving it.
Error below:
INFO [main] - *** CloverETL framework/transformation graph, (c) 2002-2012 Javlin a.s, released under GNU Lesser General Public License ***
INFO [main] - Running with CloverETL library version 3.2.1 build#63 compiled 04/01/2012 12:53:21
INFO [main] - Running on 4 CPU(s), OS Windows 7, architecture amd64, Java version 1.6.0_20, max available memory for JVM 901120 KB
INFO [main] - Loading default properties from: defaultProperties
INFO [main] - Graph definition file: graph/Baseline.grf
INFO [main] - Graph revision: 1.114 Modified by: mkressirer Modified: Thu Apr 12 13:27:18 EDT 2012
INFO [main] - Checking graph configuration...
INFO [main] - Graph configuration is valid.
INFO [main] - Graph initialization (Baseline)
INFO [main] - [Clover] Initializing phase: 0
INFO [main] - [Clover] phase: 0 initialized successfully.
INFO [main] - register MBean with name:org.jetel.graph.runtime:type=CLOVERJMX_1306871483270_0
INFO [WatchDog] - Starting up all nodes in phase [0]
INFO [WatchDog] - Successfully started all nodes in phase!
INFO [RUN_GRAPH1_0] - Running graph ./graph/InitDataStore.grf in the same instance.
INFO [RUN_GRAPH1_0] - Checking graph configuration...
INFO [RUN_GRAPH1_0] - Graph configuration is valid.
INFO [RUN_GRAPH1_0] - Graph initialization (InitDataStore)
INFO [RUN_GRAPH1_0] - [Clover] Initializing phase: 0
WARN [RUN_GRAPH1_0] - WS messenger cleanup failed.
java.lang.NullPointerException
     at org.apache.axis2.client.Stub.cleanup(Stub.java:134)
     at com.opensys.cloveretl.component.WebServiceClient.free(Unknown Source)
     at org.jetel.graph.Phase.free(Phase.java:487)
     at org.jetel.graph.TransformationGraph.freeResources(TransformationGraph.java:681)
     at org.jetel.graph.TransformationGraph.free(TransformationGraph.java:955)
     at org.jetel.graph.runtime.PrimitiveAuthorityProxy.executeGraph(PrimitiveAuthorityProxy.java:149)
     at org.jetel.component.RunGraph.runGraphThisInstance(RunGraph.java:511)
     at org.jetel.component.RunGraph.runSingleGraph(RunGraph.java:409)
     at org.jetel.component.RunGraph.execute(RunGraph.java:302)
     at org.jetel.graph.Node.run(Node.java:414)
     at java.lang.Thread.run(Thread.java:619)
WARN [RUN_GRAPH1_0] - Some graphs wasn't executed (because graph "./graph/InitDataStore.grf" finished with error).
WARN [RUN_GRAPH1_0] - Some graph(s) finished with error.
ERROR [WatchDog] - Graph execution finished with error
ERROR [WatchDog] - Node RUN_GRAPH1 finished with status: ERROR caused by: Graph './graph/InitDataStore.grf' failed!
ERROR [WatchDog] - Node RUN_GRAPH1 error details:
org.jetel.exception.JetelException: Graph './graph/InitDataStore.grf' failed!
     at org.jetel.component.RunGraph.execute(RunGraph.java:324)
     at org.jetel.graph.Node.run(Node.java:414)
     at java.lang.Thread.run(Thread.java:619)
INFO [WatchDog] - [Clover] Post-execute phase finalization: 0
INFO [WatchDog] - [Clover] phase: 0 post-execute finalization successfully.
INFO [WatchDog] - Execution of phase [0] finished with error - elapsed time(sec): 2
ERROR [WatchDog] - !!! Phase finished with error - stopping graph run !!!
INFO [WatchDog] - -----------------------** Summary of Phases execution **---------------------
INFO [WatchDog] - Phase# Finished Status RunTime(sec) MemoryAllocation(KB)
INFO [WatchDog] - 0 ERROR 2 20132
INFO [WatchDog] - ------------------------------** End of Summary **---------------------------
WARN [exNode_0_1306871483270_RUN_GRAPH1] - Attempt to unregister non-registered thread in the ContextProvider.
./graph/InitDataStore.grf: Execution of graph failed! Error during graph initialization: Phase 0 can't be initilized.
INFO [WatchDog] - WatchDog thread finished - total execution time: 2 (sec)
INFO [main] - Freeing graph resources.
ERROR [main] - Execution of graph failed !

It can't find an Endeca specific class when running via the clover command line utility. Thus, the classpath being set in that shell script is not incorporating the .jar files where the endeca-specific classes are packaged. I would start by adding an line to see what your classpath is set to. There are actually already some lines of shell script in clover that you can uncomment to see what .jars are getting loaded:
#echo $CLOVER_LIB/*
for i in $CLOVER_LIB/*.jar $CLOVER_LIB/*.zip; do
     LOCAL_CLASSPATH="$LOCAL_CLASSPATH:$i"
done;
#for i in `ls $CLOVER_LIB/*.jar`; do
#echo $i
#done;
You could also echo LOCAL_CLASSPATH to see what is getting set there. At the end of the day, you will need the endeca-specific jars to load which can be found here: /Endeca/Discovery/2.3.0/Integrator/plugins/com.endeca.latitude_1.0.0/*
HTH,
Dan
http://branchbird.com

Unable to use endeca-cmd against the running Endeca Server

Hello Endeca forum,
I'm working in a client environment in which I can see that the Endeca Server is running:
1. Going to a browser on the server itself, I can see a positive result page when I go to http://localhost:7770/admin/<datasource>?op=ping
2. When I'm in the linux server and do a "ps -ef | grep "start", I see that there is a process running the server with "-Djetty.port=7770"
3. Studio running on the same server has datasources pointing at localhost:7770 (and Studio is showing data)
However, when I go to the endeca-cmd and try to create a new datasource ("./endeca-cmd create-ds <new_datasource_name>"), I see the following error:
"*Error contacting the Endeca Server localhost:7770: com/endeca/opmodel/opSupport/MkMdexRunner*"
I get the same error if I try to use a graph in Data Integrator with the "Create Data Store" component (taken from the quickstart InitDataStore.grf, but pointing to the client's Endeca Server).
Running "./endeca-cmd version" gives me an equally cryptic error:
"*Error contacting the Endeca Server localhost:7770: com/endeca/mdex/admin/_1/Admin*"
Has anyone seen this before?
I'm starting to think that this may be a strange environment issue, but I can't figure why I'd be able to see the server running through other means, but fail to interact with the server using endeca-cmd.
Thanks,
Jerome

Hey Brett,
Good points. Unfortunately, I can't install SoapUI on the client's server (where the Endeca Server is running), but I was able to run a graph that tries to create a dgraph on it (which is an HTTP call to the createDataStore operation). This call resulted in the same error that I saw when invoking "endeca-cmd create-ds". However, the failure of the graph gives me a little more in the form of a partial stack trace...
org.apache.axis2.AxisFault: com/endeca/opmodel/opSupport/MkMdexRunner
at org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvocationWorker.run(OutInAxisOperation.java:451)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
... which doesn't really tell me anything.
Is there a place where I can see logs for the Endeca Server? Might be able to get a little more from a full stack trace...
I know that dgraph logs are at…
<OEID_installation>/Server/2.3.0/endeca-server/logs
But obviously these don’t hold anything about the dgraph that I’m trying to create.
Thanks,
Jerome

Endeca config service URLs

I am trying to load an attribute schema into an Endeca 7.5.1.1 server (EID 3.0) and seem unable to correctly configure the WebServiceClient component as described in Chapter 4 of the Integrator User's Guide.See the Web Service Request section on page 55:
<config-service:configTransaction
xmlns:config-service="http://www.endeca.com/MDEX/config/services/types/1/0">
<config-service:OuterTransactionId>${OUTER_TRANSACTION_ID}</config-service:OuterTransactionId>
<config-service:updateProperties
xmlns:mdex="http://www.endeca.com/MDEX/XQuery/2009/09">
$xmlString
</config-service:updateProperties>
</config-service:configTransaction>
I am unable to connect to either URL listed above. I'm getting the Oracle McAfee Web Gateway Cannot Connect message. Both of my Endeca servers are inside the firewall.
I also can't connect to this URL that I see referenced on the web (same error): http://www.endeca.com/MDEX/config/services/config/2010
Below is the tail of the (very long) log file. Apologies for the long post. Any help would be much appreciated.
2013-07-12 00:27:58,845 INFO 127465 [WatchDog] Transaction RunGraph   ENDECA_TRANSACTION_RUN_GRAPH0                    RUNNING
2013-07-12 00:27:58,845 INFO 127465 [WatchDog] %cpu:..
2013-07-12 00:27:58,845 INFO 127465 [WatchDog] UniversalDataReader    DATA_READER0                                 FINISHED_OK
2013-07-12 00:27:58,845 INFO 127465 [WatchDog] %cpu:..                          Out:0            1           0      0       0
2013-07-12 00:27:58,845 INFO 127465 [WatchDog] ---------------------------------** End of Log **--------------------------------
2013-07-12 00:28:00,215 INFO 127465 [ENDECA_TRANSACTION_RUN_GRAPH0_127465] kill graph; runId=127467
2013-07-12 00:28:00,221 INFO 127465 [ENDECA_TRANSACTION_RUN_GRAPH0_127465] ./graph/load_rss_pdr.grf: Execution of graph failed! org.apache.axis2.AxisFault: Read timed out
Details:
com.opensys.cloveretl.component.ws.exception.SendingMessageException: org.apache.axis2.AxisFault: Read timed out
        at com.opensys.cloveretl.component.ws.proxy.AsyncMessenger.sendInOutMessage(AsyncMessenger.java:657)
        at com.opensys.cloveretl.component.ws.proxy.AsyncMessenger.sendPayload(AsyncMessenger.java:580)
        at com.opensys.cloveretl.component.WebServiceClient.sendAndProcessResponse(WebServiceClient.java:597)
        at com.opensys.cloveretl.component.WebServiceClient.execute(WebServiceClient.java:395)
        at org.jetel.graph.Node.run(Node.java:453)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.axis2.AxisFault: Read timed out
        at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
        at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:203)
        at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:76)
        at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:400)
        at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:225)
        at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:438)
        at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
        at org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvocationWorker.run(OutInAxisOperation.java:442)
        ... 3 more
Caused by: java.net.SocketTimeoutException: Read timed out
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.read(SocketInputStream.java:129)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
        at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)
        at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106)
        at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116)
        at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1413)
        at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973)
        at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)
        at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)
        at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
        at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
        at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
        at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
        at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:557)
        at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:199)
        ... 9 more
2013-07-12 00:28:00,221 WARN 127465 [ENDECA_TRANSACTION_RUN_GRAPH0_127465] Some graph(s) finished with error.
2013-07-12 00:28:00,221 ERROR 127465 [ENDECA_TRANSACTION_RUN_GRAPH0_127465] Graph './graph/load_rss_pdr.grf' failed! Error running internal sub graphs
2013-07-12 00:28:00,242 INFO 127465 [ENDECA_TRANSACTION_RUN_GRAPH0_127465] Rolled back transaction ID 'transaction'
2013-07-12 00:28:00,242 ERROR 127465 [WatchDog] Graph execution finished with error
2013-07-12 00:28:00,243 ERROR 127465 [WatchDog] Node ENDECA_TRANSACTION_RUN_GRAPH0 finished with status: ERROR caused by: Graph './graph/load_rss_pdr.grf' failed!
2013-07-12 00:28:00,243 ERROR 127465 [WatchDog] Node ENDECA_TRANSACTION_RUN_GRAPH0 error details:
org.jetel.exception.JetelException: Graph './graph/load_rss_pdr.grf' failed!
        at org.jetel.component.RunGraph.execute(RunGraph.java:345)
        at com.endeca.clover.adapters.transaction.TransactionRunGraph.execute(TransactionRunGraph.java:253)
        at org.jetel.graph.Node.run(Node.java:453)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)
2013-07-12 00:28:00,243 INFO 127465 [WatchDog] [Clover] Post-execute phase finalization: 0
2013-07-12 00:28:00,243 INFO 127465 [WatchDog] [Clover] phase: 0 post-execute finalization successfully.
2013-07-12 00:28:00,244 INFO 127465 [WatchDog] Execution of phase [0] finished with error - elapsed time(sec): 600
2013-07-12 00:28:00,244 ERROR 127465 [WatchDog] !!! Phase finished with error - stopping graph run !!!
2013-07-12 00:28:00,244 INFO 127465 [WatchDog] -----------------------** Summary of Phases execution **---------------------
2013-07-12 00:28:00,244 INFO 127465 [WatchDog] Phase#            Finished Status         RunTime(sec)    MemoryAllocation(KB)
2013-07-12 00:28:00,244 INFO 127465 [WatchDog] 0                 ERROR                            600            615552
2013-07-12 00:28:00,244 INFO 127465 [JobFinalizer_127465] Finalisation
2013-07-12 00:28:00,244 INFO 127465 [WatchDog] ------------------------------** End of Summary **---------------------------
2013-07-12 00:28:00,244 INFO 127465 [WatchDog] WatchDog thread finished - total execution time: 600 (sec)
2013-07-12 00:28:00,249 INFO 127465 [JobFinalizer_127465] Finished Status: ERROR
2013-07-12 00:28:00,249 INFO 127465 [JobFinalizer_127465] RunTime: 600 s

Answered my own question. From the Dev Guide:
xmlns:config="http://www.endeca.com/MDEX/config/services/types/2/0

Installing Oracle E-Business Suite Extensions for Oracle Endeca, Release 12.1.3.4

Hi,
Here i am Installing Oracle E-Business Suite Extensions for Oracle Endeca, Release 12.1.3.4
Reference Document: Installing Oracle E-Business Suite Extensions for Oracle Endeca, Release 12.1.3.4 (Doc ID 1562372.1)
After the integration while login to endeca server with ebs user.
while clicking the application "The data source for this component is currently unavailable" error showing.
Please help me to fix this issue.
Regards
Kumar

Hi,
While checking the load data its showing error in clover url.
We got error like this.
Graph 'sandbox://Common/graph/FullLoad.grf' failed!
And we followed the document for this issue Endeca graphs failing (Doc ID 1549013.1)
Please help me to fix this issue.
Regards
Kumar

Oracle E-Business Suite Extensions for Oracle Endeca, Release 12.1.3.4 Installation

Hi All,
Previously we installed Oracle Extension for Endeca 2.3 for ChRM Claims on Linux Server but showing something went wrong with it. Now we are planning to install/upgrade with its recent version. Our main approach is also include the "budget dashboard" on EBS. For these we are referring the article id 1562372.1 for installation.
So is these good approach to de-install version which we installed previously and re-installed the complete set installation with recent version? QuickInstall package i.e E-Business Suite Extensions for Oracle Endeca, Release 12.1.3.4 Generic V39077-01.
E-Business Suite Extensions Oracle Endeca Server Quick Install for Linux x86-64 V39078-01.
Is there any effect on EBS if we do so?
Because we installed different patches for previous installation and as per the doc id 1562372.1 we need to apply some more different patches for these installation.
Or Is there any approach to to upgrade E-Business Suite Extensions Oracle Endeca which we installed previously?
Please help me to regarding these I am very new to these.
Thanks & Regards
Rahul

Hi,
While checking the load data its showing error in clover url.
We got error like this.
Graph 'sandbox://Common/graph/FullLoad.grf' failed!
And we followed the document for this issue Endeca graphs failing (Doc ID 1549013.1)
Please help me to fix this issue.
Regards
Kumar

Installing Oracle E-Business Suite Extensions for Oracle Endeca, Release 12.2 V5(Doc ID 1614014.1) postSetup.sh script missing

Hi,
I am working on Oracle EBS and OEID integration for iprocurement. Followed the Installing Oracle E-Business Suite Extensions for Oracle Endeca, Release 12.2 V (Doc ID 1614014.1).
But not able to find the postSetup.sh script at /u01/Oracle/quickInstall path which is use to perform following task:
1. Create JNDI: Create JNDI data source for Oracle Endeca Studio Portal and Clover to obtain a connection to the Oracle
2. Create DD: Create a default data domain profile for the dgraph processes to tune the performance of the integrator graphs.
I think this script is missing from the Oracle E-Business Suits Extensions for Oracle Endeca Server Quick Install for linux installable:
Please suggest.
Please refer doc id 1614014.1 page 9 step 5,6 of b) Perform post-setup steps.
Thanks,
Dipti

Hi,
While checking the load data its showing error in clover url.
We got error like this.
Graph 'sandbox://Common/graph/FullLoad.grf' failed!
And we followed the document for this issue Endeca graphs failing (Doc ID 1549013.1)
Please help me to fix this issue.
Regards
Kumar

Create Custom data_domain in Oracle E-Business Suite Extensions for Oracle Endeca

Hi all
I integrated EBS with Oracle Endeca information discovery with the help of the following document Installing Oracle E-Business Suite Extensions for Oracle Endeca, Release 12.2 V4 (Doc ID 1574273.1).
I am little aware to create custom data loading using endeca integrator.
I need to know is there any possibility to create custom data_domain using Integrator in Oracle E-Business Suite Extensions for Oracle Endeca.
Using the webs ervices data domains are created in the Endeca server.
Below mentioned port numbers are displayed in the doc.
7001 Oracle Endeca WL Managed Server
7002 Oracle Endeca WL Domain Admin Server
7004 Oracle Endeca Studio UI WL Managed Server
7005 Oracle Endeca Integrator WL Domain Admin Server
7006 Oracle Endeca Integrator Server UI WL Managed Server
7011-8011 Oracle Endeca Server Internal Data Domains
webservices url will be like http://hostname:port/endeca-server/ws/admin Like.
I need to know the port number for this url. Kindle help me regarding this webservices
Kindly suggest me ASAP.
Thanks in advance.

Hi,
While checking the load data its showing error in clover url.
We got error like this.
Graph 'sandbox://Common/graph/FullLoad.grf' failed!
And we followed the document for this issue Endeca graphs failing (Doc ID 1549013.1)
Please help me to fix this issue.
Regards
Kumar

Query on EBS Extensions for Oracle Endeca Release 12.1 V5

Dear Team
Can you please clarify the below query on Endeca,
After installing Endeca, I ran Full Graph Load for EAM module as per the document - Installing Oracle E-Business Suite Extensions for Oracle Endeca, Release 12.1 V5 (Doc ID: 1683053.1)
EBS Database mount point was filled up while it is running. Will Endeca data be stored in EBS database itself, if so how can we estimate the free space required for each product.
Regards
Charan

Hi,
While checking the load data its showing error in clover url.
We got error like this.
Graph 'sandbox://Common/graph/FullLoad.grf' failed!
And we followed the document for this issue Endeca graphs failing (Doc ID 1549013.1)
Please help me to fix this issue.
Regards
Kumar

Error in Payables(ap) : FullLoadConfig.grf in EBS Extension

Hi,
I am trying to execute Payables (ap) : FullLoadConfig.grf in EBS Extension for Oracle Endeca from http://endeca.oracle.com:7006/clover/runGraphs.jsp#
but not able to execute it sucessfully.
(while iReceivables (ar) graph from FIN module properly works)
(Instance is created on VMware-Oracle Ent. Linux R6)
PFA log file
Please provide solution
Regards,
Anand
error.log
2014-12-11 17:18:11,714 WARN 97927 [RUN_LOAD_DATA_FULL_97927] Some graph(s) finished with error.
2014-12-11 17:18:11,737 ERROR 97927 [WatchDog] Graph execution finished with error
2014-12-11 17:18:11,741 ERROR 97927 [WatchDog] Node GRAPH_FAILED_RAISE_ERROR finished with status: Error occurred in nested transformation: ERROR caused by: Message: Transform failed! caused by: org.jetel.ctl.TransformLangExecutorRuntimeException: Interpreter runtime exception on line 7 column 7 - Exception raised by user: ./graph/LoadDataFull.grf - Graph ./graph/CheckAgingProfile.grf failed!
Details:
org.jetel.exception.JetelException: Graph ./graph/CheckAgingProfile.grf failed!
at org.jetel.component.RunGraph.execute(RunGraph.java:280)
at org.jetel.graph.Node.run(N
2014-12-11 17:18:11,742 ERROR 97927 [WatchDog] Node GRAPH_FAILED_RAISE_ERROR error details:
org.jetel.exception.TransformException: Message: Transform failed! caused by: org.jetel.ctl.TransformLangExecutorRuntimeException: Interpreter runtime exception on line 7 column 7 - Exception raised by user: ./graph/LoadDataFull.grf - Graph ./graph/CheckAgingProfile.grf failed!
Details:
org.jetel.exception.JetelException: Graph ./graph/CheckAgingProfile.grf failed!
at org.jetel.component.RunGraph.execute(RunGraph.java:280)
at org.jetel.graph.Node.run(N
at org.jetel.component.CTLRecordTransformAdapter.transformOnError(CTLRecordTransformAdapter.java:85)
at org.jetel.component.Reformat.execute(Reformat.java:263)
at org.jetel.graph.Node.run(Node.java:453)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
Caused by: org.jetel.ctl.TransformLangExecutorRuntimeException: Interpreter runtime exception on line 7 column 7 - Exception raised by user: ./graph/LoadDataFull.grf - Graph ./graph/CheckAgingProfile.grf failed!
Details:
org.jetel.exception.JetelException: Graph ./graph/CheckAgingProfile.grf failed!
at org.jetel.component.RunGraph.execute(RunGraph.java:280)
at org.jetel.graph.Node.run(N
at org.jetel.ctl.TransformLangExecutor.visit(TransformLangExecutor.java:1816)
at org.jetel.ctl.ASTnode.CLVFRaiseErrorNode.jjtAccept(CLVFRaiseErrorNode.java:30)
at org.jetel.ctl.TransformLangExecutor.executeAndCleanup(TransformLangExecutor.java:2564)
at org.jetel.ctl.TransformLangExecutor.visit(TransformLangExecutor.java:1453)
at org.jetel.ctl.ASTnode.CLVFBlock.jjtAccept(CLVFBlock.java:32)
at org.jetel.ctl.TransformLangExecutor.executeFunction(TransformLangExecutor.java:2437)
at org.jetel.ctl.TransformLangExecutor.executeFunction(TransformLangExecutor.java:2494)
at org.jetel.component.CTLRecordTransformAdapter.transformImpl(CTLRecordTransformAdapter.java:96)
at org.jetel.component.CTLRecordTransformAdapter.transform(CTLRecordTransformAdapter.java:77)
at org.jetel.component.Reformat.execute(Reformat.java:261)
... 4 more
2014-12-11 17:18:11,755 WARN 97927 [exNode_97927_1340062310906_LOG_ERROR_MESSAGE] LOG_ERROR_MESSAGEthread interrupted, it will interrupt child threads
java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at java.lang.Thread.join(Thread.java:1266)
at org.jetel.component.Trash.executeWithoutWriter(Trash.java:276)
at org.jetel.component.Trash.execute(Trash.java:239)
at org.jetel.graph.Node.run(Node.java:453)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
2014-12-11 17:18:11,758 ERROR 97927 [LOG_ERROR_MESSAGE_97927.InputThread#0] 201: thread forcibly aborted
java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:503)
at org.jetel.graph.DirectEdge.fillReadBuffer(DirectEdge.java:204)
at org.jetel.graph.DirectEdge.readRecordDirect(DirectEdge.java:170)
at org.jetel.graph.Edge.readRecordDirect(Edge.java:365)
at org.jetel.component.Trash$InputReader.run(Trash.java:482)
2014-12-11 17:18:11,767 ERROR 97927 [WatchDog] !!! Phase finished with error - stopping graph run !!!

Looks like you missed a configuration step in the Oracle E-Business Suite Extensions for Oracle Endeca Integration and System Administration Guide I've paraphrased below from the guide:
You must set the profile option AP: Endeca Aging Template. This profile option (AP_EID_AGING_TEMPLATE) set at the site level enables you to set your own aging template for Endeca reports. The profile option displays a list of all the aging templates defined in payables which are active. You can select any one template for use. Important: If this profile is not set, then Full Load Graph cannot run for Payables during the Endeca Installation and Configuration process.

Regarding number of nodes in endeca cluster

Hi,
I have a question regarding number of nodes in the endeca server cluster.
Our solution contains one data domain running in a endeca cluster with two nodes.
Endeca server documentation recommends to run the cluster with atleast 3 nodes however our solution can't accomdate another server straight away.
Can anyone please suggest what are the implication of running the cluster with two nodes like
1. Can the cluster still serve the request if one node goes down?
2, How the leader promoting works if a node goes down?
Thank you,
regards,
rp

Hi rp,
You can definitely start with two nodes and then add another Endeca Server node later, if needed. It is recommended to run a cluster of three, for increased availability.
Here are some answers to you questions about the cluster behavior:
Q: Can the cluster still serve the request if one node goes down?
A: Quoting from this portion of the Endeca Server Cluster Guide > How enhanced availability is achieved:
Availability of Endeca Server nodes
In an Endeca Server cluster with more than one Endeca Server instance, an ensemble of the Cluster Coordinator services running on a subset of nodes in the Endeca Server cluster ensures enhanced availability of the Endeca Server nodes in the Endeca Server cluster.
When an Endeca Server node in an Endeca Server cluster goes down, all Dgraph nodes hosted on it, and the Cluster Coordinator service (which may also be running on this node) also go down. As long as the Endeca Server cluster consists of more than one node, this does not disrupt the processing of non-updating user requests for the data domains. (It may negatively affect the Cluster Coordinator services. For information on this, see Availability of Cluster Coordinator services.)
If an Endeca Server node fails, the Endeca Server cluster is notified and stops routing all requests to the data domain nodes hosted on that Endeca Server node, until you restart the Endeca Server node.
Let's consider an example that helps illustrate this case. Consider a three-node single data domain cluster hosted on the Endeca Server cluster consisting of three nodes, where each Endeca Server node hosts one Dgraph node for the data domain. In this case:
If one Endeca Server node fails, incoming requests will be routed to the remaining nodes.
If the Endeca Server node that fails happens to be the node that hosts the leader node for the data domain cluster, the Endeca Server cluster selects a new leader node for the data domain from the remaining Endeca Server nodes and routes subsequent requests accordingly. This ensures availability of the leader node for a data domain.
If the Endeca Server node goes down, the data domain nodes (Dgraphs) it is hosting are not moved to another Endeca Server node. If your data domain has more than two nodes dedicated to processing queries, the data domain continues to function. Otherwise, query processing for this data domain may stop until you restart the Endeca Server node.
When you restart the failed Endeca Server node, its processes are restarted by the Endeca Server cluster. Once the node rejoins the cluster, it will rejoin any data domain clusters for the data domains it hosts. Additionally, if the node hosts a Cluster Coordinator, it will also rejoin the ensemble of Cluster Coordinators.
Q: How the leader promoting works if a node goes down? See part of the answer above. Also, this: (from the same topic, but later in text)
Failure of the leader node. When the leader node goes offline, the Endeca Server cluster elects a new leader node and starts sending updates to it. During this stage, follower nodes continue maintaining a consistent view of the data and answering queries. When the node that was the leader node is restarted and joins the cluster, it becomes one of the follower nodes. Note that is also possible that the leader node is restarted and joins the cluster before the Endeca Server cluster needs to appoint a new leader node. In this case, the node continues to serve as the leader node.If the leader node in the data domain changes, the Endeca Server continues routing those requests that require the leader node to the Endeca Server cluster node hosting the newly appointed leader node.
Note: If the leader node in the data domain cluster fails, and if an outer transaction has been in progress, the outer transaction is not applied and is automatically rolled back. In this case, a new outer transaction must be started. For information on outer transactions, see the section about the Transaction Web Service in the Oracle Endeca Server Developer's Guide.
Failure of a follower node. When one of the follower nodes goes offline, the Endeca Server cluster starts routing requests to other available nodes, and attempts to restart the Dgraph process for this follower node. Once the follower node rejoins the cluster, the Endeca Server adjusts its routing information accordingly.
You may ask, why do you need three nodes then? This is to achieve the high availability of the cluster services themselves.
Quoting:
If you do not configure at least three Endeca Server nodes to run the Cluster Coordinator service, the Cluster Coordinator service will be a single point of failure. Should the Cluster Coordinator service fail, access to the data domain clusters hosted in the Endeca Server cluster becomes read-only. This means that it is not possible to change the data domains in any way. You cannot create, resize, start, stop, or change data domains; you also cannot define data domain profiles. You can send read queries to the data domains and perform read operations with the Cluster and Manage Web Services, such as listing data domains or listing nodes. No updates, writes, or changes of any kind are possible while the Cluster Coordinator service in the Endeca Server cluster is down — this applies to both the Endeca Server cluster and data domain clusters. To recover from this situation, the Endeca Server instance that was running a failed Cluster Coordinator must be restarted or replaced (the action required depends on the nature of the failure).
Julia

ConfigManager.updateWsDimensions() failed

Hi all,
Anyone got the following error:
[08.27.12 09:16:29] SEVERE: Utility 'emgr_update_set_post_forge_dims' failed. Re
fer to utility logs in [ENDECA_CONF]/logs/shell on host ITLHost.
Occurred while executing line 42 of valid BeanShell script:
39| if (ConfigManager.isWebStudioEnabled()) {
40| ConfigManager.cleanDirs();
41| Forge.getPostForgeDimensions();
42| ConfigManager.updateWsDimensions();
43| }
44|
45| // archive state files, index
[08.27.12 09:16:29] 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.utility.Utility run - Utility 'emgr_update_set_pos
t_forge_dims' failed. Refer to utility logs in [ENDECA_CONF]/logs/shell on host
ITLHost.
from the logs in the [ENDECA_CONF]/logs/shell, it said:
ERROR: Failed to set app config. Make sure you can connect to http://DEMO-002:8006.
ERROR: Failed to set resources for Endeca instance "ContentAssemblerRef": Failed to delete file C:\Endeca\Workbench\workspace\state\emanager\instances\ContentAssemblerRef\resources\FORGEOUTDIMS.xml.gz
it seems the FORGEOUTDIMS.xml.gz file is locked by Endeca Tools Service and I cannot delete it.
So how can i run baseline_update.bat?
Thank you.

Kaido,
I have investigated the issue more in detail. And this is what we found :
If we run the script without the credssp parameter then we recieve a random access denied.
If we run the script with the credssp parameter then the session gets in a broken state because the powershell.exe crashed right at the time we use new-cmsitesystemserver.
At the same time we see in the app log the powershell.exe crash
Just to make it more confusing : if you precreate the new site system using the sccm console and you rerun the script ( with the credssp parameter ) then the crash does not happen and you recieve a nice message stating that the object allready exists.
If we run the new-cmsiteserversystem on the primary site server , started from the console then we have the same issue ( powershell crashes ). Can anyone confirm the issue when running the new-cmsitesystemserver directly on the PSS ? ( using CU2 )

Attempt to unregister non-registered thread in the ContextProvider

Hi,
I am running the baseline graph on Endeca integrator 2.3. While running the baseline graph I am getting the following error
INFO [main] - *** CloverETL framework/transformation graph, (c) 2002-2012 Javlin a.s, released under GNU Lesser General Public License ***
INFO [main] - Running with CloverETL library version 3.2.1 build#63 compiled 04/01/2012 12:53:21
INFO [main] - Running on 4 CPU(s), OS Windows 7, architecture amd64, Java version 1.6.0_20, max available memory for JVM 1818624 KB
INFO [main] - Loading default properties from: defaultProperties
INFO [main] - Graph definition file: graph/Baseline.grf
INFO [main] - Graph revision: 1.127 Modified by: alsukuma Modified: Tue Jan 28 14:37:06 IST 2014
INFO [main] - Checking graph configuration...
INFO [main] - Graph configuration is valid.
INFO [main] - Graph initialization (Baseline)
INFO [main] - [Clover] Initializing phase: 0
INFO [main] - [Clover] phase: 0 initialized successfully.
INFO [main] - [Clover] Initializing phase: 1
INFO [main] - [Clover] phase: 1 initialized successfully.
INFO [main] - [Clover] Initializing phase: 2
INFO [main] - [Clover] phase: 2 initialized successfully.
INFO [main] - [Clover] Initializing phase: 3
INFO [main] - [Clover] phase: 3 initialized successfully.
INFO [main] - [Clover] Initializing phase: 4
INFO [main] - [Clover] phase: 4 initialized successfully.
INFO [main] - [Clover] Initializing phase: 5
INFO [main] - [Clover] phase: 5 initialized successfully.
INFO [main] - register MBean with name:org.jetel.graph.runtime:type=CLOVERJMX_1306871483270_0
INFO [WatchDog] - Starting up all nodes in phase [0]
INFO [WatchDog] - Successfully started all nodes in phase!
INFO [RUN_GRAPH1_0] - Running graph ./graph/admin/InitDataStore.grf in the same instance.
INFO [RUN_GRAPH1_0] - Checking graph configuration...
INFO [RUN_GRAPH1_0] - Graph configuration is valid.
INFO [RUN_GRAPH1_0] - Graph initialization (InitDataStore)
INFO [RUN_GRAPH1_0] - [Clover] Initializing phase: 0
INFO [RUN_GRAPH1_0] - Messenger configuration context loaded.
INFO [RUN_GRAPH1_0] - Axis2-specific client dispatcher established for service >control< based on WSDL document.
INFO [RUN_GRAPH1_0] - Axis2 modules engaged for client dispatcher.
INFO [RUN_GRAPH1_0] - WS-Policy expressions processed.
INFO [RUN_GRAPH1_0] - Message validation on request is disabled.
INFO [RUN_GRAPH1_0] - Message validation on response is disabled.
INFO [RUN_GRAPH1_0] - Asynchronous messenger initilized for operation '{http://www.endeca.com/endeca-server/control/1}control#controlPort#createDataStore'.
INFO [RUN_GRAPH1_0] - Messenger configuration context loaded.
INFO [RUN_GRAPH1_0] - Axis2-specific client dispatcher established for service >control< based on WSDL document.
INFO [RUN_GRAPH1_0] - Axis2 modules engaged for client dispatcher.
INFO [RUN_GRAPH1_0] - WS-Policy expressions processed.
INFO [RUN_GRAPH1_0] - Message validation on request is disabled.
INFO [RUN_GRAPH1_0] - Message validation on response is disabled.
INFO [RUN_GRAPH1_0] - Asynchronous messenger initilized for operation '{http://www.endeca.com/endeca-server/control/1}control#controlPort#dataStoreStatus'.
INFO [RUN_GRAPH1_0] - Messenger configuration context loaded.
INFO [RUN_GRAPH1_0] - Axis2-specific client dispatcher established for service >control< based on WSDL document.
INFO [RUN_GRAPH1_0] - Axis2 modules engaged for client dispatcher.
INFO [RUN_GRAPH1_0] - WS-Policy expressions processed.
INFO [RUN_GRAPH1_0] - Message validation on request is disabled.
INFO [RUN_GRAPH1_0] - Message validation on response is disabled.
INFO [RUN_GRAPH1_0] - Asynchronous messenger initilized for operation '{http://www.endeca.com/endeca-server/control/1}control#controlPort#startDataStore'.
INFO [RUN_GRAPH1_0] - Messenger configuration context loaded.
INFO [RUN_GRAPH1_0] - Axis2-specific client dispatcher established for service >control< based on WSDL document.
INFO [RUN_GRAPH1_0] - Axis2 modules engaged for client dispatcher.
INFO [RUN_GRAPH1_0] - WS-Policy expressions processed.
INFO [RUN_GRAPH1_0] - Message validation on request is disabled.
INFO [RUN_GRAPH1_0] - Message validation on response is disabled.
INFO [RUN_GRAPH1_0] - Asynchronous messenger initilized for operation '{http://www.endeca.com/endeca-server/control/1}control#controlPort#attachDataStore'.
INFO [RUN_GRAPH1_0] - [Clover] phase: 0 initialized successfully.
INFO [RUN_GRAPH1_0] - register MBean with name:org.jetel.graph.runtime:type=CLOVERJMX_1331002769234_805
INFO [WatchDog] - Starting up all nodes in phase [0]
INFO [WatchDog] - Successfully started all nodes in phase!
INFO [WatchDog] - [Clover] Post-execute phase finalization: 0
INFO [WatchDog] - [Clover] phase: 0 post-execute finalization successfully.
INFO [WatchDog] - ----------------------** Final tracking Log for phase [0] **---------------------
INFO [WatchDog] - Time: 28/01/14 14:38:04
INFO [WatchDog] - Node                   ID         Port      #Records         #KB aRec/s   aKB/s
INFO [WatchDog] - ---------------------------------------------------------------------------------
INFO [WatchDog] - Verify Data Store      WEB_SERVICE_CLIENT1                          FINISHED_OK
INFO [WatchDog] - %cpu:..                          Out:0            0           0      0       0
INFO [WatchDog] -                                   Out:1            1           0      0       0
INFO [WatchDog] - Check Fault Detail     PARTITION1                                   FINISHED_OK
INFO [WatchDog] - %cpu:..                           In:0            1           0      0       0
INFO [WatchDog] -                                   Out:0            1           0      0       0
INFO [WatchDog] - Build WS Attach Req    BUILD_WS_ATTACH_REQ                          FINISHED_OK
INFO [WatchDog] - %cpu:..                           In:0            1           0      0       0
INFO [WatchDog] -                                   Out:0            1           1      0       0
INFO [WatchDog] - Attach Data Store      WEB_SERVICE_CLIENT3                          FINISHED_OK
INFO [WatchDog] - %cpu:..                           In:0            1           1      0       0
INFO [WatchDog] -                                   Out:0            0           0      0       0
INFO [WatchDog] -                                   Out:1            1           0      0       0
INFO [WatchDog] - Check Fault Detail     PARTITION2                                   FINISHED_OK
INFO [WatchDog] - %cpu:..                           In:0            1           0      0       0
INFO [WatchDog] -                                   Out:0            0           0      0       0
INFO [WatchDog] -                                   Out:1            1           0      0       0
INFO [WatchDog] - Do nothing             TRASH0                                       FINISHED_OK
INFO [WatchDog] - %cpu:..                           In:0            0           0      0       0
INFO [WatchDog] -                                    In:1            0           0      0       0
INFO [WatchDog] -                                    In:2            1           0      0       0
INFO [WatchDog] - Build WS Create Req    BUILD_WS_CREATE_REQ                          FINISHED_OK
INFO [WatchDog] - %cpu:..                           In:0            0           0      0       0
INFO [WatchDog] -                                   Out:0            0           0      0       0
INFO [WatchDog] - Create Data Store      WEB_SERVICE_CLIENT0                          FINISHED_OK
INFO [WatchDog] - %cpu:..                           In:0            0           0      0       0
INFO [WatchDog] - Check Response State   CHECK_RESPONSE_STATE                         FINISHED_OK
INFO [WatchDog] - %cpu:..                           In:0            0           0      0       0
INFO [WatchDog] -                                   Out:0            0           0      0       0
INFO [WatchDog] -                                   Out:1            0           0      0       0
INFO [WatchDog] - Start Data Store       WEB_SERVICE_CLIENT2                          FINISHED_OK
INFO [WatchDog] - %cpu:..                           In:0            0           0      0       0
INFO [WatchDog] - ---------------------------------** End of Log **--------------------------------
INFO [WatchDog] - Execution of phase [0] successfully finished - elapsed time(sec): 0
INFO [WatchDog] - -----------------------** Summary of Phases execution **---------------------
INFO [WatchDog] - Phase#            Finished Status         RunTime(sec)    MemoryAllocation(KB)
INFO [WatchDog] - 0                 FINISHED_OK                        0             34859
INFO [WatchDog] - ------------------------------** End of Summary **---------------------------
INFO [WatchDog] - WatchDog thread finished - total execution time: 0 (sec)
INFO [RUN_GRAPH1_0] - Running graph ./graph/config/LoadPreDataConfig.grf in the same instance.
INFO [RUN_GRAPH1_0] - Checking graph configuration...
INFO [RUN_GRAPH1_0] - Graph configuration is valid.
INFO [RUN_GRAPH1_0] - Graph initialization (LoadPreConfig)
INFO [RUN_GRAPH1_0] - [Clover] Initializing phase: 0
INFO [RUN_GRAPH1_0] - [Clover] phase: 0 initialized successfully.
INFO [RUN_GRAPH1_0] - [Clover] Initializing phase: 1
INFO [RUN_GRAPH1_0] - [Clover] phase: 1 initialized successfully.
INFO [RUN_GRAPH1_0] - [Clover] Initializing phase: 2
INFO [RUN_GRAPH1_0] - [Clover] phase: 2 initialized successfully.
INFO [RUN_GRAPH1_0] - register MBean with name:org.jetel.graph.runtime:type=CLOVERJMX_1338400039337_554
INFO [WatchDog] - Starting up all nodes in phase [0]
INFO [WatchDog] - Successfully started all nodes in phase!
INFO [RUN_GRAPH1_554] - Running graph ./graph/config/PreData/LoadInitialAttributes.grf in the same instance.
INFO [RUN_GRAPH1_554] - Checking graph configuration...
INFO [RUN_GRAPH1_554] - Graph configuration is valid.
INFO [RUN_GRAPH1_554] - Graph initialization (LoadConfiguration)
INFO [RUN_GRAPH1_554] - [Clover] Initializing phase: 0
INFO [RUN_GRAPH1_554] - Mapping type set to MAP_NAMES
INFO [RUN_GRAPH1_554] - Mapping type set to MAP_NAMES
WARN [RUN_GRAPH1_554] - WS messenger cleanup failed.
java.lang.NullPointerException
at org.apache.axis2.client.Stub.cleanup(Stub.java:134)
at com.opensys.cloveretl.component.WebServiceClient.free(Unknown Source)
at org.jetel.graph.Phase.free(Phase.java:487)
at org.jetel.graph.TransformationGraph.freeResources(TransformationGraph.java:681)
at org.jetel.graph.TransformationGraph.free(TransformationGraph.java:955)
at org.jetel.graph.runtime.PrimitiveAuthorityProxy.executeGraph(PrimitiveAuthorityProxy.java:149)
at org.jetel.component.RunGraph.runGraphThisInstance(RunGraph.java:511)
at org.jetel.component.RunGraph.runSingleGraph(RunGraph.java:409)
at org.jetel.component.RunGraph.execute(RunGraph.java:302)
at org.jetel.graph.Node.run(Node.java:414)
at java.lang.Thread.run(Thread.java:619)
./graph/config/PreData/LoadInitialAttributes.grf: Execution of graph failed! Error during graph initialization: Phase 0 can't be initilized.
WARN [RUN_GRAPH1_554] - Some graphs wasn't executed (because graph "./graph/config/PreData/LoadInitialAttributes.grf" finished with error).
WARN [RUN_GRAPH1_554] - Some graph(s) finished with error.
WARN [RUN_GRAPH1_554] - Attempt to unregister non-registered thread in the ContextProvider.
ERROR [WatchDog] - Graph execution finished with error
ERROR [WatchDog] - Node RUN_GRAPH1 finished with status: ERROR caused by: Graph './graph/config/PreData/LoadInitialAttributes.grf' failed!
ERROR [WatchDog] - Node RUN_GRAPH1 error details:
org.jetel.exception.JetelException: Graph './graph/config/PreData/LoadInitialAttributes.grf' failed!
at org.jetel.component.RunGraph.execute(RunGraph.java:324)
at org.jetel.graph.Node.run(Node.java:414)
at java.lang.Thread.run(Thread.java:619)
INFO [WatchDog] - [Clover] Post-execute phase finalization: 0
INFO [WatchDog] - [Clover] phase: 0 post-execute finalization successfully.
INFO [WatchDog] - Execution of phase [0] finished with error - elapsed time(sec): 0
ERROR [WatchDog] - !!! Phase finished with error - stopping graph run !!!
INFO [WatchDog] - -----------------------** Summary of Phases execution **---------------------
INFO [WatchDog] - Phase#            Finished Status         RunTime(sec)    MemoryAllocation(KB)
INFO [WatchDog] - 0                 ERROR                              0             21549
INFO [WatchDog] - 1                 N/A                                0                 0
INFO [WatchDog] - 2                 N/A                                0                 0
INFO [WatchDog] - ------------------------------** End of Summary **---------------------------
INFO [WatchDog] - WatchDog thread finished - total execution time: 0 (sec)
./graph/config/LoadPreDataConfig.grf: Execution of graph failed! null
WARN [RUN_GRAPH1_0] - Some graphs wasn't executed (because graph "./graph/config/LoadPreDataConfig.grf" finished with error).
WARN [RUN_GRAPH1_0] - Some graph(s) finished with error.
WARN [RUN_GRAPH1_0] - Attempt to unregister non-registered thread in the ContextProvider.
ERROR [WatchDog] - Graph execution finished with error
ERROR [WatchDog] - Node RUN_GRAPH1 finished with status: ERROR caused by: Graph './graph/config/LoadPreDataConfig.grf' failed!
ERROR [WatchDog] - Node RUN_GRAPH1 error details:
org.jetel.exception.JetelException: Graph './graph/config/LoadPreDataConfig.grf' failed!
at org.jetel.component.RunGraph.execute(RunGraph.java:324)
at org.jetel.graph.Node.run(Node.java:414)
at java.lang.Thread.run(Thread.java:619)
INFO [WatchDog] - [Clover] Post-execute phase finalization: 0
INFO [WatchDog] - [Clover] phase: 0 post-execute finalization successfully.
INFO [WatchDog] - Execution of phase [0] finished with error - elapsed time(sec): 0
ERROR [WatchDog] - !!! Phase finished with error - stopping graph run !!!
INFO [WatchDog] - -----------------------** Summary of Phases execution **---------------------
INFO [WatchDog] - Phase#            Finished Status         RunTime(sec)    MemoryAllocation(KB)
INFO [WatchDog] - 0                 ERROR                              0             21929
INFO [WatchDog] - 1                 N/A                                0                 0
INFO [WatchDog] - 2                 N/A                                0                 0
INFO [WatchDog] - 3                 N/A                                0                 0
INFO [WatchDog] - 4                 N/A                                0                 0
INFO [WatchDog] - 5                 N/A                                0                 0
INFO [WatchDog] - ------------------------------** End of Summary **---------------------------
INFO [WatchDog] - WatchDog thread finished - total execution time: 0 (sec)
INFO [main] - Freeing graph resources.
ERROR [main] - Execution of graph failed !
Kindly help
Thanks

java.lang.NullPointerException
at org.apache.axis2.client.Stub.cleanup(Stub.java:134)
at com.opensys.cloveretl.component.WebServiceClient.free(Unknown Source)
It looks like there is a problem with your Web Services Client component.   Check the configuration of this component.
RLJII

ATG Endeca CRS Integration baseline_update.bat fails

Hi,
I have deployed the CRS through cim.bat and after that I am trying to run the following scripts and fails with the below errors.
I am able to deploy the dicsover application that comes with the Endeca.
Here are the steps I am trying to do after deploying through CIM.
F:\Endeca\apps\CRS\control>load_baseline_test_data.bat
F:\Endeca\apps\CRS\control>baseline_update.bat
F:\Endeca\apps\CRS\control>load_baseline_test_data.bat
F:\Endeca\apps\CRS\config\script\..\..\test_data\baseline\data.txt
1 file(s) copied.
Setting flag 'baseline_data_ready' in the EAC.
F:\Endeca\apps\CRS\control>baseline_update.bat
[03.27.13 10:55:13] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[03.27.13 10:55:14] INFO: Definition has not changed.
[03.27.13 10:55:14] INFO: Starting baseline update script.
[03.27.13 10:55:14] INFO: Acquired lock 'update_lock'.
[03.27.13 10:55:14] INFO: [ITLHost] Starting shell utility 'move_-toprocessing'.
[03.27.13 10:55:15] INFO: [ITLHost] Starting copy utility 'fetch_config_to_input_for_forge_Forge'.
[03.27.13 10:55:16] INFO: [ITLHost] Starting backup utility 'backup_log_dir_for_component_ConfigurationGeneratorForge'.
[03.27.13 10:55:17] INFO: [ITLHost] Starting component 'ConfigurationGeneratorForge'.
[03.27.13 10:55:35] INFO: [ITLHost] Starting copy utility 'CopyRecsearchConfig'.
[03.27.13 10:55:35] INFO: [ITLHost] Starting backup utility 'backup_log_dir_for_component_Forge'.
[03.27.13 10:55:36] INFO: [ITLHost] Starting component 'Forge'.
[03.27.13 10:55:41] INFO: [ITLHost] Starting backup utility 'backup_log_dir_for_component_Dgidx'.
[03.27.13 10:55:42] INFO: [ITLHost] Starting component 'Dgidx'.
[03.27.13 10:55:43] SEVERE: Batch component 'Dgidx' failed. Refer to component logs in F:\Endeca\apps\CRS\config\script\..\..\.\logs\dgidxs\Dgidx on host ITLHost.
Occurred while executing line 53 of valid BeanShell script:
50|
51| Dgidx.archiveLogDir();
52|
53| Dgidx.run();
54|
55|
56|
[03.27.13 10:55:43] 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.component.BatchComponent run - Batch component 'Dgidx' failed. Refer to component logs in F:\Endeca\apps\CRS\config\script\..\..\.\logs\dgidxs\Dgidx on host ITLHost.
[03.27.13 10:55:43] INFO: Released lock 'update_lock'.
Error in the Log file Dgidx.log
============================================================================
=== DGIDX: Version = "6.4.0.692722"
=== Start Time : Wed Mar 27 10:55:42 2013
=== Arguments : "F:\Endeca\MDEX\6.4.0\bin\dgidx.exe -v --compoundDimSearch --lang en --out F:\Endeca\apps\CRS\logs\dgidxs\Dgidx\Dgidx.log --dtddir F:\Endeca\MDEX\6.4.0\conf\dtd --tmpdir F:\Endeca\apps\CRS\data\temp F:\Endeca\apps\CRS\data\forge_output\CRS F:\Endeca\apps\CRS\data\dgidx_output\CRS"
=== Current Directory : F:\Endeca\apps\CRS
=== Host : ABONDALA-US2
=== Exec Path : F:\Endeca\MDEX\6.4.0\bin\dgidx.exe
============================================================================
Language/collation in use is English (collation=endeca)
WARN     03/27/13 15:55:42.950 UTC (1364399742949)     DGIDX     {dgidx,baseline}     Lexer/OLT log: level=-1: 2013/03/27 10:55:42 | INFO | Enabling log callback
No application configuration specified. Using "F:\Endeca\apps\CRS\data\forge_output\CRS" as the application configuration prefix.
============================================================================
=== DGIDX: Starting phase "Read raw dimensions, properties, and records"
=== Current Time : Wed Mar 27 10:55:42 2013
=== Total Elapsed : 0.0110 seconds
=== User CPU Time : 0.0156 seconds
=== System CPU Time : 0.0468 seconds
=== Memory Usage : 18.23 MB
============================================================================
Parsing XML dimensions data with validation turned on
Parsing project file "F:\Endeca\apps\CRS\data\forge_output\CRS.xml" (project="CRS")
XMLParser: Reading dimensions, dvals, and synonyms from file "F:\Endeca\apps\CRS\data\forge_output\\CRS.dimensions.xml"
ERROR     03/27/13 15:55:42.958 UTC (1364399742957)     DGIDX     {dgidx,baseline}     Internal error while decompressing input stream: null
FATAL     03/27/13 15:55:42.958 UTC (1364399742957)     DGIDX     {dgidx,baseline}     Fatal error at file , line 0, char 0; Message: An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=F:\Endeca\apps\CRS\data\forge_output\\CRS.dimensions.xml
WARN     03/27/13 15:55:42.958 UTC (1364399742957)     DGIDX     {dgidx,baseline}     Lexer/OLT log: level=-1: 2013/03/27 10:55:42 | INFO | Disabling log callback
Is this issue ""F:\Endeca\apps\CRS\data\forge_output\\CRS.dimensions.xml" file path. I am running on windows 7 and even tried giving the paths with back slash instead of forward slash. Not sure where to debug this issue. Please let me know if anyone has encountered this error.
environment.properties
LANGUAGE_ID=en
EAC_PORT=8888
HOSTNAME=localhost
#CAS settings
CAS_ROOT=F:/Endeca/CAS/3.1.1
CAS_HOST=localhost
CAS_PORT=8500
CAS_CLIENT_ID=FORGE
# PATH_SEP_VARNAME: for platform-independence, determine at runtime instead of build time:
PATH_SEP_VARNAME=${path.separator}
# CAS library directory for loading the jars to use in the record store commandline util into the class path
RS_JAVA_LIB_DIR=F:/Endeca/CAS/3.1.1/lib/recordstore-cmd/
# CAS recordstore-forge-adapter jar loads all necessary record store client dependencies through manifest file
CAS_RS_CLASSPATH=F:/Endeca/CAS/3.1.1/lib/recordstore-forge-adapter/recordstore-forge-adapter-3.1.1.jar
# Forge needs record store libraries as well as Spring to load record store adapter configuration files
FORGE_CLASSPATH=${CAS_RS_CLASSPATH}${PATH_SEP_VARNAME}./config/lib/java/spring-2.5.6.jar${PATH_SEP_VARNAME}./config/lib/java/eacToolkit-3.1.1.jar${PATH_SEP_VARNAME}./config/lib/java/spring-delegate-adapter-1.0.1.jar${PATH_SEP_VARNAME}./config/script${PATH_SEP_VARNAME}.
# Forges running FCM need to both read from record stores and run the FCM, ifdi-fcm.jar includes dependencies via manifest
FORGE_FCM_CLASSPATH=${FORGE_CLASSPATH}${PATH_SEP_VARNAME}./config/lib/java/ifdi-fcm-1.0.0.20121016.jar
Thanks for the help.
Thanks
Anil.
Edited by: user552512 on Mar 27, 2013 9:08 AM

That definitely doesn't look right - by default it would be reading the file data\forge_output\dimensions.xml, but you are getting a carriage return and CRS.dimensions.xml? Have you modified the Dimension Adapter and/or Indexer Adapter in your pipeline? The default settings are:
-- Dimension Adapter --
Format = XML - Internal
URL = dimensions.xml (so relative to the pipeline.epx)
Custom Compression Level = unchecked (if this is checked then URL will become dimensions.xml.gz)
-- Indexer Adapter --
URL = ../../data/forge_output/
Regards
Michael

Endeca 'InitDataStore.grf' failed

Similar Messages

Maybe you are looking for