topic Re: Qlikview Server and Publisher activities.. in QlikView

Qlikview Server and Publisher activities..

Fri, 20 Nov 2020 18:02:30 GMT

Hi All,

Could you please let me know,

Developer perspective,

In Qlikview Server and Publisher Administration and Maintenance activities?.

Regards,

Raja.

Re: Qlikview Server and Publisher activities..

Mon, 10 Feb 2014 02:41:46 GMT

Hi QV Experts,

Could you please share your idea.

Regards,

Raja

Re: Qlikview Server and Publisher activities..

chiru_thota — Mon, 10 Feb 2014 03:45:11 GMT

Following information may be helpful up to some extent.

General Admin tasks :

(1) Install/Configure server products (Development, Testing, Production environments)
(2) Create and deploy server packages
(3) QEMC tasks
(4) Coordinate upgrades
(5) Coordinate Change Management
(6) Fallback processes to back off of unstable versions included maintaining prior versions of SW and data
(7) Performance Monitoring & Incident Monitoring

QEMC :

Mounting folders where we have QVWs

Creating tasks and publishing QVWs to Access Point

Implementing server level security if required.

Publisher :

Deploying QlikView applications to thousands of users easily and securely

Distributing QlikView reports in PDF format to unlimited users via email

Thanks,

Chiru

Re: Qlikview Server and Publisher activities..

Mon, 10 Feb 2014 05:15:07 GMT

Thanks chiranjeevi ,

Please gives me some more information.

Re: Qlikview Server and Publisher activities..

Mon, 10 Feb 2014 05:58:49 GMT

Hi,

Qlikview server acts as a webserver hosting your documents and qlikview publisher will help you to split files and send emails and section access go through the qlikview server and publisher manuals

Re: Qlikview Server and Publisher activities..

Mon, 10 Feb 2014 06:05:49 GMT

Hi Raja,

To add to the points that chiranjeevi has already mentioned, please find below for few more:

1) If you are using web applications, creating EDX triggers tasks to make dashboard dynamic.

2) Deploying QVW files to server and taking care of the paths for both server and publisher.

3) Creating reload task, scheduling the jobs.

4) Document distribution in publiser

5) Section Access in publisher

6) May need to work with IIS integration if it is .net web application.

7) You can refer to server/publisher manuals for more details.

Hope this helps!

Thanks,

Sai