Clustering_QlikView_Server_8_using_Microsoft_Windows_Server_2003_Clustering_Service__final

					QlikView Enterprise Solutions

Clustering QlikView Server 8 using Microsoft
Windows Server 2003 Clustering Service




Version:     1.0
Date:        2012-08-15
Author(s)    BMW




”A best practice is a technique or methodology that, through experience and re-
search, has proven to reliably lead to a desired result.”
Contents
Contents .........................................................................................................2
Clustering QlikView Server 8 using Windows Server 2003 Microsoft
Clustering Service ...........................................................................................3
  Overview .....................................................................................................3
  Setting up the cluster...................................................................................4
    Cluster account ........................................................................................4
    Setting up the NICs..................................................................................5
    Connecting to the SAN ..........................................................................11
    Create the cluster ..................................................................................14
  Cluster IIS .................................................................................................22
    MSDTC ..................................................................................................22
    Install IIS Components...........................................................................29
    Create IIS resources ..............................................................................35
    Verify IIS cluster and failover .................................................................41
  Install QlikView Server components ..........................................................42
    Create new folders.................................................................................42
    QlikView Server Setup ...........................................................................43
    IIS configuration .....................................................................................46
    QlikView Server configuration ................................................................48
    Second node .........................................................................................50
    Create QVS resources...........................................................................51
    Verify QVS failover ................................................................................54
    IIS configuration (second node) .............................................................54
    Verify connectivity ..................................................................................55
Appendix .......................................................................................................56
  How to set up an iSCSI target on a Linux host ..........................................56
    Before you begin:...................................................................................56
    Installing Ubuntu Linux 8.04 LTS Server Edition ...................................57
    Configure network..................................................................................57
    Setting up the iSCSI Target ...................................................................58
    Verify connectivity from Windows Server 2003 ......................................60
Clustering QlikView Server 8 using Windows Server 2003
Microsoft Clustering Service

This white-paper will describe step-by-step how to set-up and configure QlikView
Server 8.5 in a two node cluster using Microsoft Clustering Service. The setup will be
an active-passive fail-over cluster. The first section will focus on configuring the two
servers that should be part of the cluster and setting up the cluster (if you already got
a working cluster, this part can be skipped). The following section will describe how to
configure Microsoft Internet Information Server (IIS) as a resource in the cluster. The
last sections will go through the installation process of QlikView Server and adding
this as a cluster resource.

Overview
The following is an overview of the test environment used in this example. The two
servers that should be part of the cluster are both running Windows Server 2003 En-
terprise and are part of the same domain. Three NICs are added on each server.
Two will be used by the Clustering Service (Public and Private heart-beat) and the
third NIC will be used for iSCSI connection to the Storage Area Network (SAN). Two
LUN's are configured on the iSCSI target, one for the Quorum disk (used by Cluster-
ing Service) and one for data storage (QlikView documents).

Configuration of the iSCSI target is out of the scope of this white-paper. However if
you want to try the set-up in a test-environment, see the appendix "How to set up an
iSCSI target on a Linux host".


Picture of infrastructure
                                 iSCSI SAN


                    2.2.2.x

 clusternode1                                                    clusternode2


                               Private (heartbeat)
                                 192.168.100.x




                10.2.2.50     Clustering Service     10.2.2.60


                                  10.2.2.100




                                                                                      [3]
Setting up the cluster
Cluster account
The Clustering Service requires a domain user account that is a member of the Local
Administrators group on each node. This account should be dedicated only to run-
ning the Clustering Service.

In this example the domain user account
will be named "clusvc". Make sure to
check User Cannot Change Password
and Password Never Expires when cre-
ating the account:




Add the account to the Local Administra-
tors group on each node:




                                                                                 [4]
Setting up the NICs
Before configuring the NICs, make sure both nodes are members of the same do-
main. Each node needs a minimum of two network cards; one for the Public network
through which outside clients access the clustered application and one for the Private
network (heartbeat) used for cluster node-to-node communication.

In this example a third NIC will be configured as well to connect to the Storage Area
Network (SAN).

Table of NIC-settings.
    Node         Public    Private             iSCSI
                 NIC       NIC                 NIC
    clusternode1 10.2.2.50 192.168.100.10      2.2.2.10
    clusternode2 10.2.2.60 192.168.100.20      2.2.2.20


Start by configuring all the NICs on the computer that will act as the first node in the
cluster according to the table above, before moving on to the second node.


Public NIC
    Right-click the Public NIC and
     select Properties.
    On the General tab, make sure
     Internet Protocol (TCP/IP) is
     selected and press Properties.
    Configure the Public NIC with a
     static IP address. The following
     values will be used in this exam-
     ple.
    Press OK to close the dialog
    Right-click the Public NIC and
     rename the NIC to "Public".




                                                                                       [5]
Private NIC
The Private network is used for heartbeat communication between the nodes in the
cluster. This network should only be used for cluster communication.

    Right-click the Private NIC and se-
     lect Properties.
    On the General tab, disable Client
     for Microsoft Networks and File
     and Printer Sharing for Microsoft
     Networks. This will make sure that
     no non-cluster data is transmitted
     over the NIC.
    On the General tab, make sure In-
     ternet Protocol (TCP/IP) is select-
     ed and press Properties.




    Configure the Private NIC with a
     static IP address. Leave the gate-
     way empty.




                                                                               [6]
 Press Advanced...
 On the DNS tab, disable Register
  this connection's addresses in
  DNS.




 On the WINS tab, disable Net-
  BIOS and LMHOSTS.
 Press OK to close the dialog.
 Right-click the Private NIC and
  rename the NIC to "Private".




                                     [7]
iSCSI NIC
To be able to connect to the SAN in this example, one additional NIC needs to be
configured with a static IP address.

    Right-click the iSCSI NIC and
     select Properties.
    Disable Client for Microsoft
     Networks and File and Printer
     Sharing for Micrsoft Networks.
    Configure a static IP address in
     the same way as with the Private
     NIC.
    Press Advanced... and make
     the same changes as with the
     Private NIC:
         on the DNS tab, disable
          Register this connec-
          tion's addresses in DNS.
         on the WINS tab, disable
          NetBIOS and LMHOSTS.
    Right-click the NIC and rename
     the NIC to "iSCSI".



The final configuration should look like this:




                                                                                   [8]
Configure a binding order for the networks on the nodes
Configure the binding order for the networks by opening Network Connections and
go to Advanced - Advanced Settings... in the toolbar:




Make sure you have the following order:

      Public
      iSCSI SAN (in this example)
      Private
      Other NICs (if any)




                                                                                  [9]
Second node
Configure all the NICs on the second node in the same way as you did on the first
node:

Public NIC
      Static IP : 10.2.2.60
      Subnet: 255.255.255.0
      Gateway: 10.2.2.3
      DNS: 10.2.2.4

Private NIC
      Static IP: 192.168.100.20
      Subnet: 255.255.255.0
      Disable Client for Microsoft Networks
      Disable File and Printer Sharing for Microsoft Networks
      Disable Register this connection's addresses in DNS
      Disable NetBIOS and LMHOSTS

iSCSI NIC
      Static IP: 2.2.2.20
      Subnet: 255.255.255.0
      Disable Client for Microsoft Networks
      Disable File and Printer Sharing for Microsoft Networks
      Disable Register this connection's addresses in DNS
      Disable NetBIOS and LMHOSTS


Verify connectivity and Name resolution
Before continuing, make sure to verify the communication both on the Private and
Public networks (and SAN if used). Do this by pinging all IP addresses from each
node. You should be able to ping all IP addresses, locally and on the remote nodes.

To verify the name resolution, ping each node from a client using the node's machine
name ("clusternode1" and "clusternode2" in this example). It should only return the IP
address for the Public network.

Do not continue setting up the cluster if you can't verify connectivity! Make
sure that you made the correct settings according to the Table of NICs above.




                                                                                    [10]
Connecting to the SAN
In our example Microsoft iSCSI Initiator will be used to connect to the iSCSI storage
array using Ethernet NICs. Windows Vista and Windows Server 2008 includes the
iSCSI Initiator out-of-the-box. For Windows Server 2003, the initiator needs to be
downloaded and installed on each node. You can download the iSCSI Initiator here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=12cb3c1a-15d6-4585-
b385-befd1319f825&displaylang=en

Install the initiator using the default settings.

Configuring the iSCSI Initiator
    Start with the first node and open
     the iSCSI Initiator.
    Go to the tab Discovery.
    Press Add and enter the IP ad-
     dress for your iSCSI target
     (2.2.2.1 in this example).
    Go to the tab Targets and press
     Log On...Make sure you check
     Automatically restore this con-
     nection when the system re-
     boots.
    Close the iSCSI Initiator.




                                                                                   [11]
Initialize the new drives
You need to initialize the new drives found on the iSCSI target.

    Right-click My Computer and select Manage. This will open up Computer
     Management.
    Select Storage - Disk Management.You will be prompted that Windows found
     new drives that need to be configured. Make sure you select Basic and not Dy-
     namic. Clustering Service is not supported on Dynamic disks.
    Create a new primary partition on each drive. Select a drive letter that would be
     appropriate for each LUN (Q: for the Quorum disk and E: for data storage in
     this example).
    Format the disks using NTFS and add appropriate volume labels (Quorum for
     Q: and Data for E:).




    Verify that you can write to both disks by creating a text-file named clus-
     ter1.txt on disk E: and disk Q:.




                                                                                   [12]
Second node
    Shut down the first node to be able to configure iSCSI Initiator on the second
     node.
    If not already done, download and install the Initiator on the second node.
    Configure the iSCSI Initiator in the same way as you did on the first node. The
     iSCSI target in our example is 2.2.2.1.
    Right-click My Computer and select Manage to open Computer Management.
    Select Storage - Disk Management and verify that you can see the two LUNs
     from the iSCSI target. There is no need to format or initialize the disks on the
     second node. However you need to assign a drive letter for each disk. Make
     sure you assign the same letters as you did on the first node (Q: for Quorum
     and E: for Data).
    Verify that you can access both drives and that the text-file (cluster1.txt)
     created before can be accessed. Create a new text-file, cluster2.txt to veri-
     fy that you can write to each disk from the second node.
    Shut down the second node and restart the first node. Verify that the text-file
     cluster2.txt is present on each disk.

Now it's time to create and set up the cluster.




                                                                                 [13]
Create the cluster

First node
   On the first node go to Start - Administrative Tools - Cluster Administrator.
   Select Create new cluster and press OK to start the Cluster wizard.




   Press Next on the welcome screen.
   Select a name for the cluster, for example "QVSVCluster", then press Next.
   Verify that the name of the first node (clusternode1) is selected and press Next.
    The cluster wizard will analyze the computer to verify that it meets the require-
    ments for being part of a cluster. If no errors occur, press Next when the wizard
    has finished the analysis.
   On the next screen you will be prompted for an IP address. This IP address will
    be used for cluster management / administration. It is not the IP address used
    by clients to connect to resources (for example QlikView Server) in the cluster.
    Enter a valid IP address. In this example IP address 10.2.2.100 will be used for
    cluster management.




   Press Next.




                                                                                 [14]
 Next, enter the credentials for the Cluster Service account created in the begin-
  ning of this paper (clusvc) and press Next.




 In the next dialog, press Quorum... and verify that the quorum disk (Disk Q:)
  has been identified. If any other disk has been identified as the quorum disk,
  change it to Disk Q: and press OK.
 Press Next to have the Cluster wizard create the resources for the cluster.

 When the wizard has finished, the Cluster Administrator console will launch.
  Expand the Groups node and verify that two groups are created.

 Cluster Group including:
     Cluster IP Address
     Cluster Name
     Disk Q:

 Group 0 including:
     Disk E:




 Right-click Group 0 and rename it to "Disk Group 1".

                                                                                 [15]
Second node
   Start the second node if it is not already running.
   Open Cluster Administrator on the second node (Start - Administrative Tools -
    Cluster Administrator).
   In the Open Connection to Cluster dialog select Add nodes to cluster and
    input the name of the cluster (QVSVCluster).




   Press OK. This will start the Add Nodes wizard.
   Press Next on the welcome screen.
   In the Select Computers dialog verify that the second node (clusternode2) is
    selected and press Add.




   Press Next and wait for the wizard to finish analyzing the cluster.




                                                                               [16]
 In the Cluster Service Account dialog verify that the Cluster Service account
  (clusvc) is selected and input the password for the account.




 Press Next to finish the wizard. After the wizard has finished you should have
  two nodes in the cluster.




                                                                              [17]
Configure Private network (hearbeat)
   Open Cluster Administrator if not
    already open (Start - Adminis-
    trative Tools - Cluster Admin-
    istrator).
   Expand the node Cluster Con-
    figuration - Networks.
   Right-click the Private network
    and select Properties.
   Make sure that Enable this
    network for cluster use is
    checked and select Internal
    cluster communications only
    (private network).
   Press OK.




Configure Public network
   Right-click the Public network
    and select Properties.
   Make sure Enable this network
    for cluster use is checked and
    select All communications
    (mixed network).
   Press OK.




                                        [18]
Configure network priority
   Right-click the cluster name (QVSCLUSTER) and select Properties.
   On the Network Priority tab make sure that Private network is listed first, fol-
    lowed by the Public network. This ensures that the Clustering Service will try to
    communicate on the private network first, then on the public network.




   Press OK.




                                                                                 [19]
Verify and test failover
    Open Cluster Administrator on the first node (Start-Administrative Tools -
     Cluster Administrator).
    Expand the Cluster Group and verify that the first node (clusternode1) is the
     owner of all resources.




      Verify disk Q: and disk E: are accessible on the computer.
      Create a file, clusternode1.txt on disk E:
      Right-click Cluster Group and select Move Group.
      Verify the owner of all resources in the group changes to the second node
        (clusternode2).




                                                                                   [20]
 Right-click Disk Group 1 and select Move Group.
 Verify that the owner of Disk E: changes to the second node (clusternode2).




 On the second node (clusternode2) verify that you can access drive Q: and
  drive E: and that you can see the file previously created on the E: drive
  (clusternode1.txt).

 Go back to the first node (clusternode1) and the Cluster Administrator console.
 Expand the Cluster Group and right-click the Cluster Name resource. Select
  Initiate Failure. Do this four times to initiate a failure.




 The Cluster Group should fail and move back to the first node (clusternode1).
 Do the same with the Disk E: resource in Disk Group 1 to change the owner
 from the second node (clusternode2) back to the first node (clusternode1). Now
 all resources should be back on the first node (clusternode1).

                                                                                [21]
Cluster IIS
Some components of QlikView Server requires a web server, for example Microsoft
IIS. Follow the instructions below to set up IIS in a cluster before installing QlikView
Server. This will make sure that all web components of QlikView Server will be in-
stalled correctly.

MSDTC
QlikView Server does not rely on Microsoft Distributed Transaction Coordinator
(MSDTC), but if you ever plan to implement web applications that use transactions,
you need to enable Network DTC Access before installing IIS. If you know that
MSDTC will never be used, this section can be skipped.

Enable DTC network access
    On the first node (clusternode1) go to Start - Control Panel - Add or Remove
      Programs.
    Select Add/Remove Windows Components.
    Select Application Server and press Details...
    Check Enable network DTC access and press OK.




    Press Next and Finish to close the Windows Components Wizard.
   Repeat the above on the second node (clusternode2).




                                                                                      [22]
Create MSDTC cluster resources
MSDTC IP Address resource
   Open Cluster Administrator (Start - Administrative Tools - Cluster Adminis-
     trator).
   Right-click Disk Group 1 and select New - Resource.
   Give the resource a descriptive name, such as MSDTC IP.
   Select IP Address in the Resource type drop-down.
   Make sure Group is set to Disk Group 1.




   Press Next.
   Verify that both nodes are included as Possible owners:




   Press Next.

                                                                             [23]
 Do not select any dependencies:




 Press Next.

 On the TCP/IP Address Parameters select an IP Address for the resource. In
  this example, we will select 10.2.2.193/255.255.255.0. This will be the IP ad-
  dress for the MSDTC.
 Make sure the network is set to Public:




 Press Finish.




                                                                               [24]
MSDTC Network Name resource
     Right-click Disk Group 1 and select New - Resource.
     Give the resource a descriptive name, for example MSDTC Network Name.
     Select Network Name from the Resource type drop-down.
     Make sure Group is set to Disk Group 1.




   Press Next.

   Verify that both nodes are included as Possible owners:




   Press Next.




                                                                              [25]
 On the Dependencies dialog select MSDTC IP and press Add ->.




 Press Next.

 In the Network Name Parameters dialog enter MSDTC-Net-Name:




 Press Finish.




                                                                 [26]
MSDTC Resource
   Right-click Disk Group 1 and select New - Resource.
   Give the resource a descriptive name, for example MSDTC Resource.
   Select Distributed Transaction Coordinator from the Resource type drop-
     down.
   Make sure Group is set to Disk Group 1.




   Press Next.

   Verify that both nodes are included as Possible owners:




   Press Next.


                                                                          [27]
 In the Dependencies dialog add:
      -   Physical disk (E:)
      -   MSDTC Network Name resource




 Press Finish.
 Right-click Disk Group 1 and select Bring Online.




                                                      [28]
Install IIS Components
    On the first node (clusternode1) go to Start - Control Panel - Add or Remove
      Programs.
    Select Add/Remove Windows Components.
    Select Application Server and press Details...
    Select Internet Information Services (IIS) and press Details...
    From the list, check the following components:

          -   Common Files
          -   Internet Information Services Manager
          -   World Wide Web Services




    Press OK and then Finish to close Windows Components Wizard.

Repeat the steps above on the second node (clusternode2) to install IIS.




                                                                              [29]
Create new web folder
   On the first node (clusternode1) make sure "clusternode1" is the owner of Disk
    Group 1 and the E: drive is accessible. If not, move the group to the first node.
   Open Windows Explorer and create a new folder on the E: drive. Name it
    Inetpub.
   Create a subfolder in Inetpub. Name the folder wwwroot. This will be the root-
    folder for the clustered IIS web site.




   Go to C:\Inetpub\wwwroot.
   Copy the file iisstart.htm from C:\Inetpub\wwwroot to
    E:\Inetpub\wwwroot.




                                                                                  [30]
Setup a new clustered web site
Change Default Website IP address
   Open Internet Information Service Manager (Start - All Programs - Adminis-
    trative Tools).
   Expand CLUSTERNODE1 - Web Sites.
   Right-click Default Web Site and select Properties.
   On the Web Site tab select the IP address for the node from the drop-down list.
    In our example 10.2.2.50 will be selected.




   Press Apply, then OK to close the dialog.




                                                                               [31]
Create new web site
     Right-click Default Web Site and select New - Web Site...
     Press Next on the welcome screen.
     Type a description, for example Clustered Web Site. Press Next.
     Leave the default IP Address and Port Settings. Press Next.
     Set the path for the Web Site Home Directory to E:\Inetpub\wwwroot.




   Press Next.
   On the Web Site Access Permissions dialog check Read and Run scripts
    (such as ASP).Press Next and Finish to close the wizard.




                                                                            [32]
   Right-click the new website (Clustered Web Site) and select Properties.
   On the Documents tab press Add...
   Type iisstart.htm in the textbox and press OK.




   Click Apply and OK to close the dialog.

Enable Active Server Pages
   Select Web Service Extensions and enable Active Server Pages.




                                                                              [33]
Setup second node
   Open Cluster Administrator.
   Right-click Disk Group 1 and select Move Group to move the group to the se-
    cond node (clusternode2).
   Make sure you can access disk E: and repeat the task "Change Default Web-
    Site IP" on the second node. Make sure the IP address on the Default Web Site
    for the second node is set to the IP address of the node (in this example
    10.2.2.60).




   Repeat the task "Create new web site" on the second node. Set the home direc-
    tory to E:\Inetpub\wwwroot and check Read and Run scripts (such as
    ASP) when creating the web site.
   Select Web Service Extensions and enable Active Server Pages.




                                                                              [34]
Create IIS resources
Before you begin, open Cluster Administrator and verify that both groups (Cluster
Group and Disk Group 1) are running on the first node (clusternode1). Right-click the
group Disk Group 1 and select Rename. Change the name to "Cluster QVS".

IIS IP Address resource
    In the Cluster Administrator right-click the group Cluster QVS and select New
       - Resource.
    Give the resource a descriptive name, for example IIS/QVS IP Address.
    Select IP Address in the Resource type drop-down.
    Make sure Group is set to Cluster QVS.




    Press Next.
    Verify that both nodes are included as Possible owners:




    Press Next.

                                                                                 [35]
 Do not select any dependencies:




 Press Next.

 In the TCP/IP Address Parameters, select an IP Address for the resource.
  This will be the IP address used by clients to connect to the clustered IIS/QVS
  resource. In this example, we will select 10.2.2.69/255.255.255.0.
 Make sure the network is set to Public:




 Press Finish.




                                                                               [36]
IIS IP Network Name resource
     Right-click the group Cluster QVS and select New - Resource.
     Give the resource a descriptive name, for example IIS/QVS Name.
     Select Network Name from the Resource type drop-down.
     Make sure Group is set to Cluster QVS.




   Press Next.

   Verify that both nodes are included as Possible owners:




   Press Next.



                                                                        [37]
 In the Dependencies dialog add IIS/QVS IP Address.




 Press Next.

 In the Network Name Parameters dialog enter QVSCLUSTER. This will be the
  network name used by clients to connect to the IIS/QVS resource.




 Press Finish.




                                                                       [38]
IIS Server Instance resource
     Right-click the group Cluster QVS and select New - Resource.
     Give the resource a descriptive name, for example IIS Resource.
     Select Generic Script from the Resource type drop-down.
     Make sure Group is set to Cluster QVS.




   Press Next.

   Verify that both nodes are included as Possible owners.




   Press Next.



                                                                        [39]
 On the Dependencies dialog add Disk E:, then IIS/QVS IP Address and the
  IIS/QVS Name.




 Press Next.

 On the Generic Script Parameter dialog enter
  C:\WINDOWS\system32\inetsrv\clusweb.vbs.




 Press Finish.

 Right-click the group Cluster QVS and select Bring Online.



                                                                            [40]
Verify IIS cluster and failover
    In Cluster Administrator right-click the IIS Resource and select Initiate Fail-
     ure. Do this four times and verify that the resource group is moved to the se-
     cond node (clusternode2).
    Right-click the group Cluster QVS and select Move Group. This should move
     the group back to the first node (clusternode1).
    Open Internet Explorer and go to the URL for the clustered web site
     (http://QVSCLUSTER). You should see the "Under Constructions" start page.
    In Cluster Administrator right-click the group Cluster QVS and select Move
     Group. This should move the group to the second node (clusternode2).
    Verify in Internet Explorer that the URL http://QVSCLUSTER is still accessible.
    Move the group Cluster QVS back to the first node (clusternode1).




                                                                                  [41]
Install QlikView Server components
Make sure the group Cluster QVS is active on the first node
(clusternode1) and verify that you can access the E: drive.

Create new folders
Before starting the installation program for QlikView Server, some addi-
tional folders needs to be created on the shared E: drive.

QlikView Documents
This will be the root-folder for QlikView documents accessible via
QlikView Server. In this example the folder will be named
"QlikViewDocuments".

    Open Windows Explorer and create the folder on the E: drive
      (E:\QlikViewDocuments).

QvPrint
This folder will be used for printing and Export/Send to Excel from Ja-
va/ZFC clients.

    Go to the root-folder previously created for the clustered web site
      (E:\Inetpub\wwwroot) and create a folder named "QVPrint"
      (E:\Inetpub\wwwroot\QvPrint).

QvsDocuments
This folder will be used when generating ZFC/Ajax pages from QlikView
Server.

    Go to the root-folder for the clustered web site
      (E:\Inetpub\wwwroot) and create a folder named
      "QvsDocuments" (E:\Inetpub\wwwroot\QvsDocuments).




                                                                     [42]
QlikView Server Setup
   Start the installation program for QlikView Server on the first node
    (clusternode1). Press Next on the welcome screen and accept the
    License Agreement.
   In the Destination Folder and Installation Customization dialog
    keep the default Destination Folder. This will install the QlikView
    Server service on the local hard drive (C:).
   Uncheck Install all features.




   Press Next.




                                                                    [43]
Select Features
    In the Select Features dialog, leave the default values except for:

          o QlikView Http Server
             Make sure QlikView HTTP Server is omitted by selecting
             Entire feature will be unavailable from the drop-down
             menu.

          o QlikView Server Example documents
             Change the default location to the new folder created pre-
             viously on the shared drive (E:\QlikViewDocuments).




    Press Next.

Note: One could argue about placing the Webpages and QlikView
Server Client files on the shared drive (E:\Inetpub\wwwroot). How-
ever, doing this will prevent any update of QlikView Server in the future
without bringing down the service on the active node, which defeats the
purpose of high availability of the service.




                                                                     [44]
Select website
    Select Clustered IIS Web Site for installing and configuring web
     components on the clustered IIS web site:




    Press Next.

    Finish the installation.




                                                                   [45]
IIS configuration
   Open Internet Information Services Manager and go to the Clus-
    tered IIS Web Site node.
   Verify that virtual folders have been created successfully and that
    the path for each folder is correct. In this example it will look like:




   QvPrint should point to the sub-folder created previously on the
    shared E: disk, so right-click QvPrint in the right pane and select
    Delete. This will delete the virtual folder QvPrint from the web
    site.
   Refresh the view (F5) and verify that the sub-folder QvPrint is
    now visible.




                                                                        [46]
Activate QlikView HTTP Tunnel
   Click on Web Service Extensions and select Add a new Web
    service extension in the right pane.
   Give the extension a descriptive name, e.g. QlikView HTTP Tun-
    nel.
   Press Add... and locate the QVStunnel.dll (C:\Program
    Files\QlikView\Server\QvTunnel\QVSTunnel.dll).
   Make sure Set extension status to Allowed is checked.




   Press OK.




                                                                [47]
QlikView Server configuration
   Open QlikView Server Management Console and register
     QlikView Server.
   Press Start to start the service.

Document Folder
   Go to the tab Folders and verify that Document Folder is set to
    the shared E: drive (E:\QlikViewDocuments\):




                                                                 [48]
Printing
   Go to the tab Web Folders.
   Change the URL to /QvPrint/.
   Change Folder to the QvsPrint folder previously created on the
    shared E: drive (E:\Inetpub\wwwroot\QvPrint).

Ajax Pages
   Change Folder to the QvsDocuments folder previously created on
    the shared E: drive (E:\Inetpub\wwwroot\QvsDocuments).




   Press Apply.




                                                                 [49]
Second node
Before creating the resource for the QlikView Server service in the clus-
ter, install QlikView Server on the second node (clusternode2).

    Start the installation program for QlikView Server.
    In the QlikView Server Setup dialog, make sure to uncheck In-
     stall all features.
    On the Select Features dialog, uncheck:
          - QlikView HTTP Server
          - QlikView Server Example documents




    Finish the installation and go back to the first node (clusternode1).
     Do not start the service!




                                                                      [50]
Create QVS resources
Open Cluster Administrator and verify that both groups (Cluster
Group and Cluster QVS) are online on the first node (clusternode1).

QVS Instance resource
      Right-click the group Cluster QVS and select New - Resource.
      Give the resource a descriptive name, for example QVS Resource
      Select Generic Service from the Resource type drop-down.
      Make sure Group is set to Cluster QVS.




    Press Next.

    Verify that both nodes are included as Possible owners:




    Press Next.


                                                                      [51]
 In the Dependencies dialog add IIS Resource.




 Press Next.

 On the Generic Service Parameters dialog enter
  "QlikviewServer" as the Service name. Note: There is no space in
  the name "QlikviewServer":




 Press Next.




                                                               [52]
 In the Registry Replication dialog add the root registry key
  "SOFTWARE\QlikTech\QlikViewServer\".
 This will ensure that all settings in the registry will be replicated to
  the second node in case of a failure.




 Press Finish to close the wizard.

 Right-click QVS Resource and select Bring Online.




                                                                       [53]
Verify QVS failover
   Right-click group Cluster QVS and select Move Group.
   Go to the second node (clusternode2) and open QlikView Server
      Management Console.
   Verify that the service is running.
   Verify that the Documents Folder path (on the Folders tab)
    matches the path previously set up on the first node
    (E:\QlikViewDocuments).
   Verify that the settings on the Web Folders tab have been repli-
    cated correctly as well.

IIS configuration (second node)
   Open Internet Information Services Manager on the second
    node (clusternode2) and expand Web Sites - Clustered Web
    Site.
   Right-click QvPrint in the right pane and select Delete.
   Refresh the pane (F5) and verify that the sub-folder QvPrint is
    now visible.

Activate QlikView HTTP Tunnel
   Click on Web Service Extensions and select Add a new Web
    service extension in the right pane.
   Give the extension a descriptive name, e.g. QlikView HTTP Tun-
    nel.
   Press Add... and locate the QVStunnel.dll (C:\Program
    Files\QlikView\Server\QvTunnel\QVSTunnel.dll).
   Make sure Set extension status to Allowed is checked.




   Press OK.


                                                                  [54]
Verify connectivity
    Open Internet Explorer on the local node and go to
     http://qvscluster/qlikview/.
    Verify that all pages are loaded correctly.
    Open Internet Explorer on a client machine and go to
     http://qvscluster/qlikview/.
    Verify that all pages are loaded correctly.
    Verify each client type and also try to print/export if using Ja-
     va/ZFC.
    Shut down the first node (clusternode1). Make sure shared re-
     sources falls over to the second node (clusternode2).
    Repeat the steps above to verify connectivity from the client to
     IIS/QVS, now running on the second node.

This completes the installation and configuration of QlikView Server in a
fail-over cluster.




                                                                         [55]
Appendix

How to set up an iSCSI target on a Linux host
This is a quick step-by-step instruction on how to setup an iSCSI Target
Server hosted on a Ubuntu Linux 8.04 Server. This is not a full instruc-
tion on how to configure the iSCSI Target Server for a production envi-
ronment, but a quick and easy way of having an iSCSI solution when for
example testing Windows Clustering Service in Windows Server
2003/2008.
The setup will be based on a Ubuntu Linux 8.04 Server running as a
virtual server in VMWare for testing purposes.

Before you begin:
Make sure to create a virtual machine with a total of 3 virtual hard disks.
The first disk should be large enough to hold the operating system. The
second disk should be approx. 1GB in size and will be added to the
iSCSI target to be used as a quorum disk when testing Windows Clus-
tering Service. The third disk will be added to the iSCSI target and used
for data storage:




                                                                       [56]
Installing Ubuntu Linux 8.04 LTS Server Edition
Do a normal installation of the Ubuntu Linux Server or do a minimum
installation if you're used to Linux. This will make the installed footprint
smaller which requires less patching and makes the attack surface
smaller.

Update the server using:

  -    sudo apt-get update
  -    sudo apt-get upgrade

Install iSCSI Target using:

   -   sudo apt-get install iscsitarget

Configure network
Configure the network card to use a static IP address. In this example,
the iSCSI Target will be configured on the address 2.2.2.1.

      Type sudo pico /etc/network/interfaces.
      Change the eth0 interface to:

       auto eth0
       iface eth0 inet static
       address 2.2.2.1

      Exit pico (CTRL+X) and save the file.
      Restart the network using sudo /etc/init.d/networking restart.
      Check the IP address by typing ifconfig. The inet addr for eth0
       should be 2.2.2.1.




                                                                          [57]
Setting up the iSCSI Target
     Verify the disks installed with sudo fdisk -l. There should be
      three devices, sda (OS), sdb (quorum disk) and sdc (data stor-
      age):




     Open the config-file for the iSCSI Target by typing sudo pico
      /etc/ietf.conf.
     As this will only be for testing purposes, we don't bother about
      authentication to access the iSCSI target. Instead configure your
      Target name. This should be in the format iqn.YYYY-
      MM.com.domain:name. The server will not be part of any do-
      main in this example, so you can give it any name you like, for
      example iqn.2008-09.local.iscsi:storage.disk1.




                                                                    [58]
   Modify the LUNs to have the paths you want to export. In our ex-
    ample LUN 0 (Quorum) will be /dev/sdb and LUN1 (Data stor-
    age) will be /dev/sdc. You could also give an alias for each LUN:




   Exit pico (CTRL+X) and save the file.
   Restart the iSCSI Target by typing sudo /etc/init.d/iscsitarget
    restart.




                                                                 [59]
Verify connectivity from Windows Server 2003
Now you should be able to connect to the iSCSI Target from Windows
Server 2003, using Microsoft iSCSI Initiator and point to the address
2.2.2.1:




Note: You need to download and install Microsoft iSCSI Initiator when
running Windows Server 2003. You can download it here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=12cb3c1a-
15d6-4585-b385-befd1319f825&displaylang=en
Note: You need to add and configure a NIC on the Windows Server
2003 machine to be able to connect to the subnet hosting your iSCSI
Target (2.2.2.1)




                                                                   [60]

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:14
posted:8/15/2012
language:English
pages:60