I need some help, kind of urgent, to answer a few questions one of our potential clients has regarding QlikView. I hope you can help me, since it is a very important customer.
Maybe you can guide me to where I can find the answers (websites, documentation, other resources) or if you can actually provide some of them for me.
Any help is greatly appreciated.
These are the questions:
1) Does the solution (QlikView) support consumption of the solution services via Web Services?
2) Does the product (QlikView) support consuming Web Services?
3) List all the Web Service standards implemented and supported by your solution (QlikView): WS-I basic profile, WS-Security, WS-Addressing, WS-ReliableMessaging, WS-BusinessActivity, etc.
4) Support for HP OpenView
5) What type of information of your solution can be monitored? Technical counters, service information or business information.
6) List any third party tools your solution can integrate to achieve better ways of monitoring
7) Support for SNMP
😎 Integration with Windows Event Log (Windows only)
9) Support for Windows Management Instrumentation (WMI - Windows only)
You may also use the SDK example to write a custom data source.
3) List all the Web Service standards implemented and supported by your solution (QlikView): WS-I basic profile, WS-Security, WS-Addressing, WS-ReliableMessaging, WS-BusinessActivity, etc.
None.
4) Support for HP OpenView
Don't know.
5) What type of information of your solution can be monitored? Technical counters, service information or business information.
Technical counters such as Memory utilization, number of users & documents can be viewed realtime via the QMC/QEMC consoles and is also logged for later analysis and trending.
The QVS/QVP components run as WIndows Services and may monitored with any tool that performs service monitoring. The QMC/QEMC consoles also provide status displays of all Qlikview services.
Business information may be monitored using Document Alerts. Triggered alerts may send emails.
6) List any third party tools your solution can integrate to achieve better ways of monitoring
I use Servers Alive http://www.woodstone.nu/salive/ to monitor services and critical path reloads (file modification time checks).
7) Support for SNMP
Yes. See the QVS Ref Guide.
😎 Integration with Windows Event Log (Windows only)
Yes, many of the logging messages are written to the Event Log.
9) Support for Windows Management Instrumentation (WMI - Windows only)
Don't know of any special WMI hooks beyond the standard windows process/service stuff.
The services provide for granular log levels. Low, Medium, High, Debug.
11) Does your solution provide any kind of console to monitor for errors?
Yes, the QMC/QEMC consoles display failed tasks with error indicators.
12) Can your solution in any way notify operators, administrators or even business users of particular events?
Email may be sent when a task fails.This is generally addressed to Operators and Administrators. Document Alerts may test for conditions in business data and send emails (or show popups) when tested conditions are satisfied.
13) Support for Centralized configuration management
The QEMC console provides a unified view for monitoring, configuring and controlling all of a site's QVS/QVP servers.
14) Support for Remote management
The QMC/QEMC consoles are web applications. They can be used from any browser that can route to the QV Server port.
15) Support for Web interface
See #14.
16) Is your solution version aware of integrating components, web services, data models, etc. And what means are provided to manage versions?
During development, autoversioning may be used to create a new backup version each time the file is saved. For server installation, there is no automatic versioning support. Different strategies are emplyoyed by different customers. Some examples: -Save time stamped backups whan promoting to production. - Export the script source to a version control system - The entire document structure may exported as XML. The XML can be retained in a file or checked in to version control.
17) Can the configuration tasks of your solution be scripted to automate the task or enable unattended scenarios?
There is support for license management and task triggering via http.
You may also use the SDK example to write a custom data source.
3) List all the Web Service standards implemented and supported by your solution (QlikView): WS-I basic profile, WS-Security, WS-Addressing, WS-ReliableMessaging, WS-BusinessActivity, etc.
None.
4) Support for HP OpenView
Don't know.
5) What type of information of your solution can be monitored? Technical counters, service information or business information.
Technical counters such as Memory utilization, number of users & documents can be viewed realtime via the QMC/QEMC consoles and is also logged for later analysis and trending.
The QVS/QVP components run as WIndows Services and may monitored with any tool that performs service monitoring. The QMC/QEMC consoles also provide status displays of all Qlikview services.
Business information may be monitored using Document Alerts. Triggered alerts may send emails.
6) List any third party tools your solution can integrate to achieve better ways of monitoring
I use Servers Alive http://www.woodstone.nu/salive/ to monitor services and critical path reloads (file modification time checks).
7) Support for SNMP
Yes. See the QVS Ref Guide.
😎 Integration with Windows Event Log (Windows only)
Yes, many of the logging messages are written to the Event Log.
9) Support for Windows Management Instrumentation (WMI - Windows only)
Don't know of any special WMI hooks beyond the standard windows process/service stuff.
The services provide for granular log levels. Low, Medium, High, Debug.
11) Does your solution provide any kind of console to monitor for errors?
Yes, the QMC/QEMC consoles display failed tasks with error indicators.
12) Can your solution in any way notify operators, administrators or even business users of particular events?
Email may be sent when a task fails.This is generally addressed to Operators and Administrators. Document Alerts may test for conditions in business data and send emails (or show popups) when tested conditions are satisfied.
13) Support for Centralized configuration management
The QEMC console provides a unified view for monitoring, configuring and controlling all of a site's QVS/QVP servers.
14) Support for Remote management
The QMC/QEMC consoles are web applications. They can be used from any browser that can route to the QV Server port.
15) Support for Web interface
See #14.
16) Is your solution version aware of integrating components, web services, data models, etc. And what means are provided to manage versions?
During development, autoversioning may be used to create a new backup version each time the file is saved. For server installation, there is no automatic versioning support. Different strategies are emplyoyed by different customers. Some examples: -Save time stamped backups whan promoting to production. - Export the script source to a version control system - The entire document structure may exported as XML. The XML can be retained in a file or checked in to version control.
17) Can the configuration tasks of your solution be scripted to automate the task or enable unattended scenarios?
There is support for license management and task triggering via http.
HP OpenView creates statistics about CPU/memory/processes/disk/network , but keeps those "inside", meaning you can report those with HP tools.
Alternatively, one can setup scheduled task so desired statistics are written to disk to (text) files. Than you load and analyse the statistics with QlikView.
