Archive for the author ·

Serge

·...

Installing TIBCO on Windows Failover Cluster – part 2

no comments

1-2-1Continued from part 1. The following installation process must be done on the both nodes. The first step when you installing TIBCO SOA products is TIBCO Runtime Agent (TRA) installation. As TIBCO doesn’t have x64 TRA yet, I have to use 32 bit installer on my 64 bit system: TIB_tra-suite_5.6.0_win_x86_32.exe. At this time, 5.6 is the latest minor release of TRA.

After welcome screen, I will scroll down and accept license agreement, next read notes and select custom install. List of products included in the TRA package will appear on the screen. You may suggest that on production server is no need to install designer, but it is not so, I’m faced with the dependence of certain components, such as TIBCO SmartMapper, from its designer libraries. My suggestion is install full suite. Next step is specify default installation home that will be used for all TIBCO products. I prefer to use “D:\tibco” folder. Some next steps allow me to install documentations for components and the last screen before files copying is installation preview and confirmation.

After all files are copied, will be offered the opportunity to install an additional database JDBC driver. You can use this opportunity to install an additional driver or do it later manually like me. After that installation summary screen will appear and installation will be finished.

Now it is time to install TRA patch release. The latest is 5.6.1, file is TIB_tra-suite_5.6.1_win_x86.exe. Patch release is not includes all TRA files, so it must be installed after latest minor release. Installation looks very similar to TRA installation, but is is update only: next, next, next, finish.

Installing TIBCO ActiveMatrix BusinessWorks is not more difficult than installing Runtime Agent. At this time minor version is 5.7, file name is TIB_bw-simple_5.7.0_win_x86.exe. After welcome screen, I will scroll down and accept license agreement, read notes and look at detected an established installation home – “D:\tibco” in my case. Custom setup type helps me make sure I install all the components. Installation preview screen do the same thing. After short files copying process TIBCO BusinessWorks installation will be finished.

Installing patch release 5.7.1 is even easier. File is TIB_bw-simple_5.7.1_win_x86.exe. Next, accept, next, next, next, finish.

As x64 EMS is available, I will use latest 64 bit version 5.1.3 in TIB_ems_5.1.3_win_x86_64_vc8.zip archive. To install TIBCO EMS from version 5 new TIBCOUniversalInstaller will be used. By the way, this new installer is also used to install TIBCO Rendezvous from version 8 if you need install it as complete standalone product not as limited TRA part. Looks like TIBCO decided to switch all the products in this new installer. Package distributed as zip file and size increased twice compare to old binary installer package. For me old installer was lighter than new. Fundamental change in the new installer is that now we can specify different installation environments and it helps to install and manage many instances of same product on one host.

Then I will select custom installation as usual to install full set. If you install TIBCO EMS on MS Windows platform, installer will install EMS as a system service. Next question will be concerning service startup type: manual or auto. Let it be manual, in fact it doesn’t matter in my case as I will remove this default service and install it later a little differently. On the next screen pre-install summary will be displayed and after press to “install” button TIBCO EMS installation process will be completed.

The last main product to install is TIBCO Administrator. The latest version at this time is 5.6.0 and I will install from TIB_tibcoadmin-epe-simple_5.6.0_win_x86_32 as it only 32 bit version available. Installation is very simple: accept license agreements, read notes, look at gray read-only installation folder name as it is old installer again, select custom type and leave administrator binaries and its documentation checked. After confirmation, installation process will be completed.

TIBCO Domain Utility will be started automatically. Do not close this window, I will continue with domain creation in the part 3.

Installing TIBCO on Windows Failover Cluster – part 1

7 comments

1-1-0This is divided into four parts description of installation process of TIBCO domain on Windows 2008 R2 Failover Cluster. The aim of this is to get running on two hosts fault-tolerant TIBCO domain which contain two TIBCO EMS servers. Each TIBCO EMS server is running as cluster application and use cluster disk for data store. This solution helps to get fault-tolerant TIBCO EMS design and there is no need to have shared volumes, which is expensive solution and not available on the Windows platform yet (CSV is recently appeared exclusion made for Hyper-V). The final configuration shown in the TIBCO Administrator screenshot on the right, where is S-TST01-TIB01 is the first node and S-TST02-TIB01 is the second node. TIBCO Administrator is running on each node as master/secondary pair. Test application is running on the same hosts as fault-tolerant group in active/standby mode. But the most interesting part of domain is TST00-TIB01 – cluster service which acting as virtual host where both EMS servers live in TIBCO domain. I will explain from the beginning.

1-1-1First of all I’m going to prepare two nodes cluster. Base software is MS Windows Server 2008 R2 Enterprise Edition. Here are two disk connected to both cluster nodes. In my case storage system connected to servers via iSCSI interface. Two volumes were prepared: one small 5G will be act as cluster quorum disk, second large 50G will be used for clustered application data store. Both are raw volumes at this time.

1-1-2I’m going to put both volumes online and initialize it. If you will do it like me, do it only on one node! After this step I can create NTFS file system on quorum disk. Start “New Simple Volume Wizard”, let it to use whole disk, assign drive letter, I prefer “Q” for quorum, then perform a quick format with default settings.

1-1-3I suppose that both my nodes are ready for failover cluster. But the best practice to check it before. So, I will start cluster validation process. Here a lot of steps for testing cluster core resources availability such as network and storages. During testing, access to shared volumes will be checked from both nodes. After completion of testing, validation report will be generated. In my case warning message was received as my network adapter has no redundancy: between my servers only one network path and it will be a single point of failure. In production cluster it is better to avoid things like this, I will correct this before going to production.

1-1-4As all other things were good, I’m ready to create failover cluster. I just start “Create Cluster Wizard” and add the names of all the servers that I want to have in the cluster. Then type the cluster name. After confirmation, cluster creation and configuration process will be running. When cluster will be formed, summary message and final report will be generated. Everything looks very good in my case, so I’m ready to prepare storage for cluster data disk. In future, it will be used as storage for TIBCO EMS and TIBCO Hawk. The steps are the same as for quorum disk: “New Simple Volume Wizard”, drive letter assign, let it be “T” for TIBCO, NTFS quick format.

1-1-5After that my storage is available as cluster resource and I’m prepared to create cluster resources that will be used for TIBCO services. I will start with “Create Empty Service or Application” action, then rename this new service to TST00-TIB01 and add client access point with the same name: TST00-TIB01. IP address will be assigned automatically by DHCP. Then it’s time to add storage to this service. I will select my available Cluster Disk 1.

1-1-6 Last step is bring this service group online. At this point of time both nodes are ready for TIBCO software installation. I will continue from this point in the part 2.