Thank you for your interest in QlikView Expressor. You are correct. The Desktop version can create a deployment package which can then be used on the server side (paid version) which is an executable engine program known as etask. By default the deployment packagae is created in a directory structure where you created the workspace such as:
When combined with the other paid component - Repository (providing version control, team development and reuse) - the steps would include:
- Create the Dataflow and associated components (artifacts etc.) with Desktop
- Create the deployment package and include that Dataflow
- Commit the project - which will write all contents to the Repository
- On the machine hosting the engine (server side) you would execute a command eproject which "checks out" the project from the Repository and copies it to a file location that you define on the server
- Then you would use a command named etask with an argument list to execute the Dataflow on that server
- You can use a .bat or a .cmd file if you which to store the command and to kick it off
Please note that these steps are QlikView Expressor specific. You could combine this knowledge with the QlikView Distribution Service (Publisher) -by creating a Task to execute this Dataflow and schedule it
You can create a .QVW using the QlikView Expressor Connector - to reload the .qvw as well if you were outputting the data to a .qvx file.
In the online or installed documentation search for deployment package and the various topics will be displayed.
If you search for eproject you will get various topics here is a direct link:
Also note that this is the current integration as of version 3.7.
Please let us know if this answered your question and if you need further assistance.
The intention of the QlikView Expressor Connector is to be able to eventually stream results directly to a QV application without having to stage the data or write it to disk. This has not be implemented yet. Currently it will still write the .qvx file out to disk in addition to loading the data model into the QlikView application.
The QVEC also allows those (QlikView Designers) with access to a collection of analytical models (as I call them), available to only the QVEC, an easy and consistent way to developing metadata-driven QlikView applications. Instead of defining SQL and LOAD scripts or accessing a QVD layer - the developers can select the Dataflows that have the columns to created the business discovery application with confidence.
Without QVEC - those would need to LOAD the data directly from a .QVX file and its file path (current release) and depend on the latest one being available as of the last load executed from the publisher task.
QVEC allows those with access to create these applications and see the freshest data immediately as well.
This is great for those one off requests and reduces dependency on IT.
The overall value that QlikView Expressor provides is a method of provisioning (accessing, conforming, cleansing, reusing) data to facilitate the use of metadata driven QlikView applications.
You may want to watch these two videos to get a better idea:
http://www.youtube.com/watch?v=qKzqajbM3cU - QlikView Expressor Product Description
http://www.youtube.com/watch?v=wWr07wNShEE- QlikView Expressor QlikView Integration Demo