Using the FCC assignment mode element to override default client mapping behavior

A client mapping is a list of assignedfsc elements appropriate for a particular client’s IP address and/or domain name. The assignedfsc element is found in the fmsmaster_fscid.xml file. Static client mapping is not always appropriate, because it is possible for a client to change network contexts without changing its IP address or domain name. Example A user takes a company laptop from the office to a hotel room. The FMS server cache (FSC) is inaccessible because the client has moved outside the company firewall. To access company data from the public side of the firewall, the user must use a different FSC server (or at least a different access address) than the server used in the office. Example A user takes a company laptop from the office to a remote location. At the remote location, the client continues accessing data over a WAN, using the client mapped assignedfsc elements, even though the data is now more readily accessible from an FSC in a local satellite office. This is inefficient, as the WAN connection is slower than accessing the data from the FSC servers in the same office. It is possible, but inconvenient, to reconfigure the clientmap elements in the fmsmaster_fscid.xml file for each client machine (and propagate dynamic changes to several clientmap settings throughout the entire FMS system) each time a Teamcenter client is relocated on the network. It is more efficient to change the default assignment mode setting (in the fcc.xml file) from clientmap to parentfsc. clientmap With this setting, FCC data requests are routed to the assignedfsc elements specified within the clientmap section of the fmsmaster_fscid.xml configuration file. The FCC downloads the list of assignedfsc elements from the parentfsc element when it starts. An assignedfsc element represents an FMS server that distributes Teamcenter data to clients that have no direct access to the FSCs serving the origin volume. Each clientmap section typically contains one to three assignedfsc elements. The assignedfsc elements represent FMS cache or data servers. parentfsc Use this setting when the default client mapping setting is not efficient. With this setting, the parentfsc list is used as the assignedfsc list. FCC data requests are routed to the list of parentfsc elements specified in the fcc.xml configuration file. A parentfsc element represents an FSC server that distributes FMS configuration settings to clients upon request. Each fcc.xml file typically contains one to three parentfsc elements. The following fcc.xml sample code illustrates an appropriate assignment mode setting for a client in a hotel room. Copy The following fcc.xml sample code illustrates an appropriate assignment mode setting for a client in a remote satellite office. Copy Note For legacy client mapping, use the iptoparent setting in the fcc.properties file: Copy com.teamcenter.fms.clientcache.iptoparent=false The default setting is true, which causes the FCC to send its IP to the parentfsc list. The FSC maps the FCC client by the IP as determined at the client. Setting iptoparent to false inhibits the client IP on the parentfsc client mapping request. The FSC maps the FCC client by the IP address on which the request arrives at the parentfsc. This is often an IP router, firewall, or proxy server at the parent FSC's location.