The mapping module is a self-registering server that creates the appropriate entry in the Posting Acceptor’s mapping modules registry during registration.
Inside the registry, Posting Acceptor expects to find DWORD values, names of which are the Class IDs of mappers, and the values of which are either 1 (enable) or 0 (disable). For example, the entry for the Microsoft Content Replication System (CRS) mapping module looks like this:
{66BE7352-83A0-11D0-A317-00C04FD7CFC5}:REG_DWORD:0x1
The acceptor queries each of the installed mapping modules until one of them succeeds and a physical location is returned to the acceptor. If no mapping module succeeds, the acceptor defaults to querying IIS for the physical location of the given URL. If the default also fails, the acceptor returns an error message to the client.
Posting Acceptor can be configured with one or several mapping modules to route the incoming files to the desired location. When more than one mapping module is available, you can control where the user’s content is routed depending on user permissions and setup specifications in the mapping modules.
Note
Mapping module keys are located in HKLM\Software\Microsoft\WebPost\Acceptors\CPSHost\Mappers\