topic EDX Triggers Not Working Since 11 Upgrade in QlikView

EDX Triggers Not Working Since 11 Upgrade

Tue, 04 Nov 2014 12:01:19 GMT

We have recently upgraded our test environment from Qlikiview 10 to Qlikview 11 so as to evaluate the changes and confirm that existing reports and functions still work

As it stands the only functionality that has failed to work in qlikview 11 is the EDX triggers

I have done a significant amount of net research around this area but can find no article that concretely states that EDX trigger that work in QV 10 will not work in QV 11

When we attempt to fire the EDX trigger we get the following error:

17/10/2014 12:06:08-The remote server returned an error: (404) Not Found.

17/10/2014 12:06:08-Runtime exception encountered

Is this due to the existing EDX code no longer working in QV 11?

The EDX trigger we currently have implemented is an exe written in c# and as yet I can find no example of how to re-write an EDX exe in c# (the only example I can fin is for a DLL and this does not appear to translate into an exe)

Here is a code snippet from our existing EDX trigger code:

bool blnStartTask = sqlHelper.execSQL("SELECT * FROM [database].[flagtable] WHERE TRUNC(rptdate) = trunc(sysdate-1)");

//bool blnStartTask = sqlHelper.execSQL("SELECT * FROM [database].[flagtable] WHERE TRUNC(rptdate) = trunc(sysdate)");

if (blnStartTask == true)

{

//Indicates that the data migration from gold to goldmine is completed

status = true;

// Settings

string Result = "";

string QvsAddress = ConfigurationManager.AppSettings["server"];

string TaskName = ConfigurationManager.AppSettings["task"];

string EDXPassword = ConfigurationManager.AppSettings["password"];

// Create class

EDXCall Caller = new EDXCall();

// Obtain a EDX key from QVS

string EDXKey = Caller.GetEDXKey(QvsAddress);

// Call the EDX to execute the task in QVS

Result = Caller.LaunchEDX(QvsAddress, EDXKey, EDXPassword, TaskName);

//Log the result after executing the task

Logger.log(Result);

Result = Caller.CheckEDXStatus(QvsAddress, EDXKey, TaskName);

Logger.log("EDX Task Completed");

Re: EDX Triggers Not Working Since 11 Upgrade

amit_saini — Tue, 04 Nov 2014 12:06:13 GMT

Thomas,

Check this:

Re: Re: EDX trigger doesn't work after QV upgrade to 11.2 SR7

Thanks,

Re: EDX Triggers Not Working Since 11 Upgrade

Peter_Cammaert — Tue, 04 Nov 2014 12:19:04 GMT

In QV11 the interface for EDX triggers has changed completely. While in QV10 an EDX trigger would launch a direct function call to the QDS service, the whole procedure now passes through the QMS (QlikView Management Service) API, which is a different interface.

You may have to reprogram your EDX setup.

Re: EDX Triggers Not Working Since 11 Upgrade

Thu, 22 Jan 2015 15:15:08 GMT

We still have yet to resolve this issue and all suggested solution so far have directed it to documentation we have already seen and does not appear to apply to our specific situation

Can someone provide a specific example that relates to using EDX trigger in qv 11 for an exe that is dependent on a database entry to fire a Qlikview task - i.e. the trigger is there to start the Qlikview task when the data has been completely loaded into the data source table

Re: EDX Triggers Not Working Since 11 Upgrade

Thu, 22 Jan 2015 15:27:54 GMT

Hi Thomas,

Can you just upload the EDX C# Code..

Re: EDX Triggers Not Working Since 11 Upgrade

Thu, 22 Jan 2015 15:49:24 GMT

I have published the code on the qlik community site

http://community.qlik.com/docs/DOC-7811

Re: EDX Triggers Not Working Since 11 Upgrade

agomes1971 — Thu, 22 Jan 2015 16:04:30 GMT

Hi,

your code will never run.

it's lacking the service reference...

please rebuild your code

based on this

QlikView Management API - #1 Setting up a Visual Studio project

HTH

André Gomes

Re: EDX Triggers Not Working Since 11 Upgrade

agomes1971 — Thu, 22 Jan 2015 22:58:57 GMT

Hi,

and more:

The QlikView Management Service API

The QlikView Management Service (QMS) API is exposed as a web service and provides a description of its operations and data objects in WSDL available at http://<server-name>:4799/QMS/Service by default. All communication is using SOAP over HTTP.

To be able to interact with the QMS API web service, a key refered to as the "service key" must be supplied as a header of the HTTP request of each operation call, except for the GetTimeLimitedServiceKey operation which is used to retrieve such a key. This aims to prevent cross-site request forgery (CSRF), see the CSRF article at OWASP.org for more information. The HTTP header containing the service key is called X-Service-Key. For example, the header with a value can look like this:

X-Service-Key: rPnBL6zlbvNr5k2nowI919EJkkOeHsi8

Different security layers controls the access to the different operations. Most operations require membership of a local group named QlikView Management API which aims to control overall API access. Exception to this is the GetTimeLimitedServiceKey operation and EDX related operations. The second layer of security aims to control access at an operation level and involves the local groups QlikView Administrator and QlikView EDX as well as the Document Folder Administrator role. These roles are inclusive, where QlikView Administrator provides the highest access level and QlikView EDX the lowest; e.g. a Document Folder Administrator have access to operations that require QlikView EDX membership, and a QlikView Administrator have access to operations that require Document Folder Administrator membership. Each operation's documentation specifies what exact roles are required to access it.

Using the QlikView Server 11 SDK sample code

The QlikView Server 11 SDK can be installed as a part of the QlikView Server 11 installation and contains a couple of examples on how to use the QMS API. It also contains a code example on how to inject the service key into the HTTP headers of the API web service call. This example is written in C# .NET 3.5 and assumes that the application is using WCF to communicate with the API.

Re: EDX Triggers Not Working Since 11 Upgrade

agomes1971 — Fri, 23 Jan 2015 10:33:47 GMT

Hi,

have you any results yet?

Thanks

André Gomes

Re: EDX Triggers Not Working Since 11 Upgrade

Fri, 23 Jan 2015 11:43:01 GMT

Thank you Andre for your incredible level of help and we are doing our best to follow your comprehensive advice

However, we are struggling to precisely follow the step:

Add the following XML attribute to the bottom <endpoint ... /> tag of your app.config file:

CopyC#

behaviorConfiguration="ServiceKeyEndpointBehavior"

We are unsure as to precisely where in the XML of the app.config this attribute needs to go. We have tried placing it within the </endpointBehaviors> tag but this generates an error

Also you mention an attachment at the end of your post but how do we access this attachment?

Thank you

Re: EDX Triggers Not Working Since 11 Upgrade

agomes1971 — Fri, 23 Jan 2015 14:00:13 GMT

Hi,

...

</basicHttpBinding>

</bindings>

<endpoint address="http://yourserver:4799/QMS/Service" binding="basicHttpBinding"

bindingConfiguration="BasicHttpBinding_IQMS" contract="yourservicereference.IQMS"

name="BasicHttpBinding_IQMS" behaviorConfiguration="ServiceKeyEndpointBehavior"/>

I hope this helps

The attachment you just download it.

Regards

André Gomes

Re: EDX Triggers Not Working Since 11 Upgrade

agomes1971 — Fri, 23 Jan 2015 18:06:57 GMT

Hi,

So how things are going on?

Regards

André Gomes

Re: EDX Triggers Not Working Since 11 Upgrade

rwunderlich — Fri, 23 Jan 2015 19:48:06 GMT

Note that the referenced document

Using EDX in QlikView 11

contains a downloadable commandline EDX exe and complete source code. You may want to use that as a starting point.

I have customers who use the supplied commandline exe as is with their database. As long as your database can fire off commandline tasks, you can use the sample as is with parameters.

One possible stumbling block is if your database server is non-windows. The V11 EDX expects NTLM authentication. You can try to implement that in your non-windows code or implement a pass-through webservice proxy on a windows box. I used this webservice from Stefan Walther. http://qvextcalledxfromajax.codeplex.com/

-Rob

Re: EDX Triggers Not Working Since 11 Upgrade

Mon, 26 Jan 2015 15:23:09 GMT

Hi Andre,

Thanks for all your very useful help - much appreciated

I am now getting the following error when running the code:

An exception occurred: System.Exception: Document mount \\unc\some does not exist.

Does this need the file path to the source documents folder?

Also just to be clear we are connecting to an Oracle database and we do not want the task triggered from an external button - we need the code to periodically check an Oracle table for a flag that indicates the data has fully loaded and upon finding the flag automatically trigger the start of the Qlikview data load task?

Re: EDX Triggers Not Working Since 11 Upgrade

agomes1971 — Mon, 26 Jan 2015 15:43:13 GMT

Hi,

to the first question i think so because it is telling that it doesn´t exist...

Second Question: So if you want periodically it might be better to create an exe with the respective permissions to be executed...

I execute my app from web interface form.

And don't forget that you can do it a partial or full reload...

Regards

André Gomes

Re: EDX Triggers Not Working Since 11 Upgrade

agomes1971 — Wed, 28 Jan 2015 11:42:21 GMT

Hi,

when are you expect to close this thread?

Regards

André Gomes

Re: EDX Triggers Not Working Since 11 Upgrade

agomes1971 — Tue, 03 Feb 2015 16:20:20 GMT

Hi,

any more news?

Regards

André Gomes