Installing BWC 5.2 (IC 7.1) Server/Repository in High Availability Mode
Article ID: KB0090371
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessWorks Workflow | - |
| Not Applicable | - |
Description
Resolution:
Installing BWC 5.2 (IC 7.1) Server/Repository in High-Availability Mode
BWC 5.2 (IC 7.1) introduced High-Availability feature with this release and the following are the steps needed to achieve HA setup for WFServers and RepoServers.
Installation Steps for BWC FT:
Machines:
Machine1 (Primary)
Machine2 (Secondary)
Installing Primary BWC 5.2 Server on Machine1:
- Installer options:
Server Type : Primary
WF Server Name: BWCFT_Primary
RepoServer Name: BWCFT_Primary
Repo Port: 9001
Repo Dir: \\<MachineName>\<Directory> (Shared drive with right access privileges from both machines)
- After the installation, start Server Manager (C:\tibco\bwc\5.2\server\BWCFT_Primary\bin\icstart.exe), Click "Configure" button, Added Server Group Name: BWCFT (On unix this is done using server/<>/Config/IcServer.srv file the property IC_SERVER_GROUP)
- Start IcServer and IcRepo services.
- Launch BatchRegistry (C:\tibco\bwc\5.2\apps\pcgui\Bin\batreg.exe) and log in as icdba.
>list repository;
Command: LIST REPOSITORY
Command Status: Success.
D Repository (*Default) Type Location Partition
- ---------- --------- ---- -------- ---------
* 00000016000004630000000B00000403 5 BWCFT_Primary \\hpakhan\ICREPO
- Change Repo Location to Server Group Name: BWCFT
>update repository 00000016000004630000000B00000403 set location BWCFT;
>list repository;
Command: LIST REPOSITORY
Command Status: Success.
D Repository (*Default) Type Location Partition
- ---------- --------- ---- -------- ---------
* 00000016000004630000000B00000403 5 BWCFT \\hpakhan\ICREPO
- Shutdown both IC Server and IC Repo. Edited C:\tibco\bwc\5.2\server\BWCFT_Primary\config\icrepdaemon.config.
REPOSITORY-NAME=BWCFT (from BWCFT_Primary to BWCFT)
- Start both IC Server and IC Repo and test with BatchRegistry and PC GUI, all works fine and then Stop both IC Server and IC Repo.
Installing Secondary BWC 5.2 Server on Machine2:
- Installer options, select custom selection of components and select WF Server and NOT Repo server.
Server Type : Secondary
Primary WF Server Name: BWCFT_Primary
Secondary WF Server Name: BWCFT_Secondary
- After the installation go to Server Manager (C:\tibco\bwc\5.2\server\BWCFT_Secondary\bin\icstart.exe) Click "Configure" button, Add Server Group Name: BWCFT
- Start BWC 5.2 installer again, selected custom components and this time selected Repo Server only.
- Installer options:
RepoServer Name: BWCFT_RepoSecondary (can't give BWCFT_Secondary as name because a directory for Sec WF Server is already existing and installer fails)
Repo Port: 9001
Repo Dir: \\<MachineName>\<Directory>
- Started WF components on Machine1 (Primary WF Server, Primary Repo Server) and on Machine2 (Secondary WF Server, Secondary Repo Server).
- Tested using BatchRegistry and PC GUI and all works fine and then stopped WFServer/RepoServer.
Admin Domain is running on Machine1 and checked Admin domain and hawk agent is running.
- Add Machine2 to the Admin Domain. Run DomainUtility on Machine2 and add the machine to Admin Domain on Machine1.
- Run DomainUtility on Machine1 and add WFServer/RepoServer to Admin Domain.
- Run DomainUtility on Machine2 and add WFServer (Secondary) and RepoServer to Admin Domain.
- Edit C:\tibco\bwc\5.2\server\BWCFT_RepoSecondary\config\icrepdaemon.config. REPOSITORY-NAME=BWCFT (from BWCFT_RepoSecondary to BWCFT)
- Test starting both the WF Server and Repo Server from Machine1 and Machine2 using Admin GUI and make sure it is successful.
- Make sure WF User Sync from Admin is successful and exporting WF processes from Designer and Admin GUI all works.
Notes:
In icrepdaemon.config the REPOSITORY-NAME needs to be the same on both installations. They also should be pointing to the same repository directory location.
In other words, in order for you to enable the HA group for the RepServer, the "secondary" Wf Repos Server must have the same name as the primary and must also point to the same location.
Also note that the primary and secondary Wf Servers must have different names, but have HA enabled by being given the same Group name. In a nutshell, the HA config for Wf Repos Server is done differently than it is for Wf Server. You need to make sure to configure the HA group for the Wf Server Server PRIOR to doing any registration via the DomainUtility. Otherwise, the DomainUtility will only recognize the Wf Server Server as an "out of the box" standalone configuration. If the Wf Server Server group has been configured, the DomainUtility is smart enough to recognize this.
The value of REPOSITORY-NAME is NOT necessarily the same as the name that is given to the repository server installation. You are prompted for a name to assign to the repository, which is what you would see in the windows registry and is also the name that is given to the directory in which the repository is created.
This name not the same as the value of the REPOSITORY-NAME found in the icrepdaemon.config.
Installing BWC 5.2 (IC 7.1) Server/Repository in High-Availability Mode
BWC 5.2 (IC 7.1) introduced High-Availability feature with this release and the following are the steps needed to achieve HA setup for WFServers and RepoServers.
Installation Steps for BWC FT:
Machines:
Machine1 (Primary)
Machine2 (Secondary)
Installing Primary BWC 5.2 Server on Machine1:
- Installer options:
Server Type : Primary
WF Server Name: BWCFT_Primary
RepoServer Name: BWCFT_Primary
Repo Port: 9001
Repo Dir: \\<MachineName>\<Directory> (Shared drive with right access privileges from both machines)
- After the installation, start Server Manager (C:\tibco\bwc\5.2\server\BWCFT_Primary\bin\icstart.exe), Click "Configure" button, Added Server Group Name: BWCFT (On unix this is done using server/<>/Config/IcServer.srv file the property IC_SERVER_GROUP)
- Start IcServer and IcRepo services.
- Launch BatchRegistry (C:\tibco\bwc\5.2\apps\pcgui\Bin\batreg.exe) and log in as icdba.
>list repository;
Command: LIST REPOSITORY
Command Status: Success.
D Repository (*Default) Type Location Partition
- ---------- --------- ---- -------- ---------
* 00000016000004630000000B00000403 5 BWCFT_Primary \\hpakhan\ICREPO
- Change Repo Location to Server Group Name: BWCFT
>update repository 00000016000004630000000B00000403 set location BWCFT;
>list repository;
Command: LIST REPOSITORY
Command Status: Success.
D Repository (*Default) Type Location Partition
- ---------- --------- ---- -------- ---------
* 00000016000004630000000B00000403 5 BWCFT \\hpakhan\ICREPO
- Shutdown both IC Server and IC Repo. Edited C:\tibco\bwc\5.2\server\BWCFT_Primary\config\icrepdaemon.config.
REPOSITORY-NAME=BWCFT (from BWCFT_Primary to BWCFT)
- Start both IC Server and IC Repo and test with BatchRegistry and PC GUI, all works fine and then Stop both IC Server and IC Repo.
Installing Secondary BWC 5.2 Server on Machine2:
- Installer options, select custom selection of components and select WF Server and NOT Repo server.
Server Type : Secondary
Primary WF Server Name: BWCFT_Primary
Secondary WF Server Name: BWCFT_Secondary
- After the installation go to Server Manager (C:\tibco\bwc\5.2\server\BWCFT_Secondary\bin\icstart.exe) Click "Configure" button, Add Server Group Name: BWCFT
- Start BWC 5.2 installer again, selected custom components and this time selected Repo Server only.
- Installer options:
RepoServer Name: BWCFT_RepoSecondary (can't give BWCFT_Secondary as name because a directory for Sec WF Server is already existing and installer fails)
Repo Port: 9001
Repo Dir: \\<MachineName>\<Directory>
- Started WF components on Machine1 (Primary WF Server, Primary Repo Server) and on Machine2 (Secondary WF Server, Secondary Repo Server).
- Tested using BatchRegistry and PC GUI and all works fine and then stopped WFServer/RepoServer.
Admin Domain is running on Machine1 and checked Admin domain and hawk agent is running.
- Add Machine2 to the Admin Domain. Run DomainUtility on Machine2 and add the machine to Admin Domain on Machine1.
- Run DomainUtility on Machine1 and add WFServer/RepoServer to Admin Domain.
- Run DomainUtility on Machine2 and add WFServer (Secondary) and RepoServer to Admin Domain.
- Edit C:\tibco\bwc\5.2\server\BWCFT_RepoSecondary\config\icrepdaemon.config. REPOSITORY-NAME=BWCFT (from BWCFT_RepoSecondary to BWCFT)
- Test starting both the WF Server and Repo Server from Machine1 and Machine2 using Admin GUI and make sure it is successful.
- Make sure WF User Sync from Admin is successful and exporting WF processes from Designer and Admin GUI all works.
Notes:
In icrepdaemon.config the REPOSITORY-NAME needs to be the same on both installations. They also should be pointing to the same repository directory location.
In other words, in order for you to enable the HA group for the RepServer, the "secondary" Wf Repos Server must have the same name as the primary and must also point to the same location.
Also note that the primary and secondary Wf Servers must have different names, but have HA enabled by being given the same Group name. In a nutshell, the HA config for Wf Repos Server is done differently than it is for Wf Server. You need to make sure to configure the HA group for the Wf Server Server PRIOR to doing any registration via the DomainUtility. Otherwise, the DomainUtility will only recognize the Wf Server Server as an "out of the box" standalone configuration. If the Wf Server Server group has been configured, the DomainUtility is smart enough to recognize this.
The value of REPOSITORY-NAME is NOT necessarily the same as the name that is given to the repository server installation. You are prompted for a name to assign to the repository, which is what you would see in the windows registry and is also the name that is given to the directory in which the repository is created.
This name not the same as the value of the REPOSITORY-NAME found in the icrepdaemon.config.
Issue/Introduction
Installing BWC 5.2 (IC 7.1) Server/Repository in High Availability Mode
Feedback
Yes
No
Powered by
