When FileNet® Image Services and Content Platform Engine are in separate physical locations and the systems communicate across a WAN, you can improve the performance of document retrievals by creating an IBM® FileNet Image Services cache on the Content Platform Engine server or on a server in the same site at which Content Platform Engine runs.
Many businesses have a main office where most of their business is conducted and satellite offices that are spread around the world. For example, a company might have its home office in Chicago and satellite offices in Seattle, Los Angeles, Houston, Atlanta, and New York. A Content Federation Services for Image Services system in Chicago can be configured to communicate across a Wide Area Network (WAN) with Content Platform Engine servers in any of the satellite locations. Consider the following scenarios:
The FileNet Image Services system is remote from the Content Platform Engine server. In addition, a FileNet Image Services cache is collocated on a Content Platform Engine server or is configured on the same local network.
The FileNet Image Services CSM cache and Content Platform Engine can be installed on the same server or separate servers that are at the same physical site. Use this configuration whenever the FileNet Image Services system is in a physically remote site. There are significant savings in avoiding round trips across the WAN for repeated queries.
When the FileNet Image Services system and the Content Platform Engine server are on the same local area network, collocating an FileNet Image Services cache on the Content Platform Engine server does not have the same advantage that it does with remote caching.
If the FileNet Image Services CSM cache is configured either on a separate server from Content Platform Engine or collocated with one of the Content Platform Engine servers, the savings applies only to the particular Content Platform Engine server that is collocated with the FileNet Image Services CSM cache. Because other Content Platform Engine servers in the cluster need to access the CSM cache on that separate server, they do not reap the same benefit as the collocated Content Platform Engine server.