Hello Perumal A,
In the coming weeks more information such as a FAQ, Datasheet, Demonstration videos and tutorials will be made available on QlikView Expressor (QVE).
In the mean-time - I will answer your questions directly:
1. What is QlikView Expressor?
QVE - is the name of the product offering provided by QlikTech which comprises of two distinct products:
a) QlikView Governance Dashboard (QVGD) - available here. This is a free product that contains a QlikView Dashboard (.QVW file) and run-time processing components (powered by QlikView Expressor technology) that will retro-actively scan a QlikView deployment(s) and display various metrics about the depolyment(s). It is intended to be largely used by IT and other technical staff to gain visibility and insight to help them answer those questions that pertain to "What is going on in my QV deployment?". The overall value and benefit of the QVGD is to allow those to take actions on their finding such as instituting best practices and applying Data Governance to their QV environment.
Some examples of the questions answered include:
- What QVD files/fields are/are not being used?
- How many QlikView applications exist in my deployment?
- What data is or is not being used and by which QV apps?
- Which expressions/labels are being used the most (recurring / overlapping)?
- What and how many of each sheet objects are being used?
- What sources of data are being accessed?
b) QlikView Expressor Desktop / Server - comprises of 4 components. A design environment - QVE Desktop, a version control and team development Repository, a server side Engine so created content can be deployed and executed on a server (QV Server / Publisher) and the QlikView Expressor Connector
There are 3 versions of QVE, a free Desktop edition (similar to QlikView Personal), Standard and Enterprise (each varies slight on some features and number of cores)
QVE Desktop - would be used to create a Dataflow that can graphically and visually provision (access, conform, cleanse, etc.) data for QlikView. There are components to access data, cleanse, transform and control its flow and output to QlikView and other target systems. This tool is largely important because it defines and captures the source, target and business rule metadata along the way which can be reused in other projects and reused amongst multiple QlikView applications. It can help reduce QV scripting in certain cases and offers a repeatable way of defining meta-driven QlikView applications. It provides an easy to use interface that most QlikView developers will feel comfortable with.
The Repository allows the storage and version control of what I call the design-time model components used to create the Dataflow. (connections, schemas, business rules, templates, etc.)
The Server (engine component known as etask.exe) - will just execute what is created on the QV Server / Publisher machines.
2. What are the uses of QlikView Expressor within QlikView
In summary - both product offerings enable a method to discover the QlikView deployment, apply data governance, increase reuse and facilitate the creation of metadata driven QlikView applications across the entire QV enviroment.
When creating QlikView applications there are few ways one can provide data to QV. One can provide direct access to the data via its connectors to databases, files and web services directly in the QlikView application (.QVW) - then use SQL and LOAD scripts to further transform the data needed for the application. Others can perform the same functions however without the graphical visualization components and just use the Connectors, SQL and LOAD scripts to access, conform, cleanse the data to create a QV .QVD file (QlikView Data layer) - then other applications can use that QVD file if needed. These processes can be scheduled and refreshed as needed using QlikView Publisher (Distribution Service and its task manager)
Due to the extremely friendly and fun design environment that QV offers, anyone can rapidly create content to answer those business questions easily. What happens with these methods when QV deployments start to grow is that usually multiple versions of the rules, metrics, column definitions may exists or are defined differently across similar applications, possibly creating a conflict in what data is correct and reducing the confidence in the data, therefore delaying decisions. These "rules" can be defined in the UI sheet objects as well as the LOAD scripts. Possibly when creating these applications there may not be a good way to reuse or share commonly used business rules and expressions that have been defined. The QlikView Governance Dashboard can help identify these areas of concerns and QVE can help define a reusable and consistent method of provisioning the data for those QlikView applications as the environment continues to grow.
3. How do you connect QlikView to QlikView Expressor
QlikView Expressor - in version 3.7 currently can output data to a QlikView .QVX format. This can then be used as a data source file within QlikView application design. With the addition of the QlikView Expressor Connector (QVEC) - you can source data directly from the QVE Dataflow without having to explicitly reference the .QVX file from a LOAD script. The QVEC allows you to access what is similar to a metadata repository. "Deployment Packages" defined within QVE projects can be accessed and expose all the Dataflows that will be used to provision data for the QlikView application.
These two videos will also help position its capabilities and additional features:
Let me know if you need anything else.
The doc is located here: QlikView Expressor Documentation - this is the archive location as we are no longer selling or releasing new versions of QlikView Expressor - so there will not be any updated doc on this - I don't think the information that I provided in this discussion is actually in the help doc as I have laid it out - so to speak. This page states it all best.