IBM Support

Image Services supports Microsoft Windows Servers in cluster environments

News


Abstract

This document provides guidelines for installing and configuring IBM FileNet Image Services 4.1.2 or 4.2.0 in Microsoft Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019 and Windows Server 2022 cluster environments.

Content

Guidelines for Image Services High Availability cluster
  1. To install Image Services on a Windows cluster environment, the OS-specific users (fnsw) and groups (fnadmin, fnop, and fnusr) must be created on the local machine.
    Add local users (Administrator, fnsw) and Domain users (<Domain>\Administrator, <Domain>\fnsw) to these groups.
    Create <Domain>\fnsw user on the domain controller with full Domain Administrator Rights.
  2. The \fnsw_loc, \fnsw\dev\1, and MSAR directories must be present on shared drives.
  3. After installing IS Software on node 2, add <Domain>\fnsw user to Shared drive directories such as \fnsw\dev\1, \fnsw_loc\sd\conf_db and MSAR and restart IS Software.
    To add a user, navigate to Folder > Properties > Security > Add <Domain>\fnsw user and provide full control permission to it.
  • On Node 2, User may face following permission-related errors if <Domain>\fnsw user is not added to Shared Drive directories.
    1. No Transient Database on this Server while opening CSM_tool.
      IS elog shows below error.
      2017/01/30 16:19:13.032 79, 0, 5 HGEPI0005E <fnsw> ds_init (5016.5072.61 0x1398.13d0) ... [CRITICAL] CNF: Can't open pagecache file; Rec#: 49 Cmd: ' E:\fnsw\dev\1\cache0 0 102400
      Check permissions of cache0 file (\fnsw\dev\1\cache0). <Domain>\fnsw user must be added to permission entries of the file.
    2. All of the dtp processes, ds_init processes, committal processes (bes_commit, fbc_commit. rmt_commit, etc.) are not running after Start of IS software.
      IS elog shows below error.
      2017/01/30 16:52:15.482 63, 0, 7 HGECK0007E <fnsw> ds_init (4896.1408.25 0x1320.580). Can't open checkpoint file, errno = 13
    3. Check permissions of snt.chkpt file (\fnsw_loc\sd\snt.chkpt). <Domain>\fnsw user must be added to permission entries of the file.
4. Automatic start of Image Services (using Enable Autostart Image Services Processes) is not supported on cluster environment.
  1. To start Image Services automatically after failover, write a batch script.
  2. Before running the Image Services startup, ensure that RDBMS is running.
  3. Schedule the batch script execution at startup of machine using Windows Task Scheduler on both nodes and restart machine after scheduling it.
    The attached zip file (WindowsClusterSampleBatch.zip) contains a sample batch script to start Image Services automatically after the failover in Cluster Environment.

    WindowsClusterSampleBatch.zipWindowsClusterSampleBatch.zip

    In the sample script, E: is the shared drive on which fnsw_loc is located and MSSQL$NEWSQL2012 is MS SQL Server 2012 Service.
  4. Modify the batch script according to your cluster environment setup.
Notes:
  1. Do not choose Enable Auto Start IS processes to Yes while running fn_setup on both the nodes.
  2. Do not choose Reset file permissions of IS Software to Yes while running fn_setup on Node 2 of the cluster.
  3. Include the Windows cluster IP address and NCH domain IP address in \etc\hosts file on IDM Desktop machine.
    Here is an example entry for a Windows Cluster (TESTCLUSTER (IP – 9.195.20.202) and IS Domain (ClusterDomain).
    9.195.20.202 TESTCLUSTER TESTCLUSTER.TESTDOMAIN.COM
    9.195.20.202 ClusterDomain ClusterDomain-filenet-nch-server.

[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVUD","label":"FileNet Image Services"},"ARM Category":[{"code":"a8m50000000Cdy8AAC","label":"FileNet Image Services"}],"ARM Case Number":"","Platform":[{"code":"PF033","label":"Windows"}],"Version":"4.1.2;4.2.0"}]

Document Information

Modified date:
14 October 2022

UID

swg21998344