Single FSC configuration

An installation of Teamcenter provides a single FSC that mounts a single volume, a typical use for small deployments. Adding two additional volumes creates the basic two-tier Teamcenter FMS configuration shown in the following figure. FSC roles The single FSC in this diagram fulfills the volume server and configuration server roles. The FSC does not provide file caching, as it has direct access to all the volumes. FCC roles The FCC provides file caching (as always in both two-tier and four-tier configurations). Client configuration All clients are configured to retrieve the initial bootstrap configuration information from FSC1, which assigns all clients to FSC1 for file access. FMS primary configuration file (FSC_HOME/fmsmaster_fsc-ID.xml) This file is served by FSC1. See the FSC_HOME/fmsmaster.xml.template file for all available elements. Key points of this file include: fmsenterprise element This statement contains a definition of FSC defaults, FCC defaults, FSC1 and its assigned volumes. This statement also includes an ID attribute which must match the unique identifier for the database. fscdefaults element Specifies where the FSC read and write cache files are stored. These defaults are used by any additional FSCs installed in the future. fccdefaults element Specifies the default location of the user's cache. fscGroup element Defines the FSC group. All FSCs must belong to one, and only one, FSC group. fsc element Defines the FSC identifier and configures the FSC. In the following example, the address of FSC1 is 146.122.40.99:4444. Dot notation is used in this example for simplicity. DNS names may also be used, such as csun17.ugs.com:4444. volume element Several volumes are defined for FSC1. Each volume must have an entry under FSC1. The volume statements also specify the root directory for each volume. The volumes can be either local disk volumes, or mounted volumes on the network. While paths specified for the volume typically match the traditional Teamcenter path for the volume for a small deployment, FSCs can be installed on any box as needed and file paths may depend on mount points provided on that box. Thus the path need not match the traditional Teamcenter volume path. You can use the backup_xmlinfo utility to generate the volume IDs. clientmap element Specifies that all clients on 146 prefixed network addresses are assigned to FSC1. A sample of the primary configuration file for this configuration is: Copy FSC configuration file (FSC_HOME/fsc.xml) This file is small in this example, containing the minimum required statements for an fsc.xml file, and does not define or override any FSC or FCC defaults. See the FSC_HOME/fsc.xml.template file for all available elements. Key points of this file in this configuration are: fscmaster element Specifies that the FSC reads the file directly from disk out of the FSC launch (working) directory. Note that the file name may be specified in the launch command as the fms.config property. fsc element Specifies the FSC ID for this installed FSC. This FSC ID is used to refer to the FSC definition provided in the FMS primary configuration file. For example: Copy FSC1 FCC configuration file (FMS_HOME/fcc.xml) This file is small in this example, containing only the bootstrap address for the FSC configuration server which allows the FCC configuration to be downloaded. See the FMS_HOME/fcc.xml.template file for all available elements. Key points of this file in this configuration are: parentfsc element This statement identifies which parent FSC to use for the initial configuration download. FCC cache location All windows clients contain an FCC cache located as specified by the FCC_CacheLocation XML attribute. All users with cache size parameters are based on the default coded values since there were no default settings in the FMS primary or FSC configuration files. Assigned FSC The assigned FSC is FSC1, as specified in the FMS primary configuration file. A sample of the FCC configuration file for this configuration is: Copy