Problem

-- whenever Interchange is restarted, all the containers previoulsy deployed from MS are automatically removed

2016-10-06 17:27:41,247 - INFO [MapProxy_forceDeployContainers] (FileSystemDeployer.logInfo:939) - Removed MapContainer

{name='ORDERS_IN_D93A_Jeeves_ORDERS_IN_', version=16, id='baca6844-a482-4866-8e47-9b162a6f0a1d', shortDescription='null', longDescription='', generatedBy='null', generationDate='2016-10-06T14:56:06Z', mapStages=0, directoryName='null', zipFileName='null', location=null', deployedDate='0}

- when deploying the flows from MS, the deployment appears to be successfully (no error in MS). The container is seen by Integrator (Integrator deployment list), but it is not seen by Interchange : it is not present in container/cache, deploy or reject), and it is not listed when using the command mapProxyDeployer list. but the maps are properly executed at runtime

so it is like the container was only deployed on Integrator

- no error in the CN logs when deploying the flows

- the table B2BIMAPCONTAINERS does not contains the flows that were deployed (it contains only the native detectors and envelopers)

- when running a mapProxydeployer FORCE_SYNC, the customer containers are removed (because they are present in Integrator but not in Interchange, so the missing container are removed)

Resolution

* check the Runtime Servers type of the server where the flows are deployed in Mapping Services

* on B2bi, type must B2Bi, not Integrator

* if the type is Intgerator, the flows will be deployed on Integrator only, and B2bi will behave as described in the description above