The webMethods Broker API allows you to disconnect a BrokerClusterPublisher without destroying the underlying Broker client objects. This is only useful if your application Broker client's life cycle is explicit-destroy as the client state for the Broker clients and all the queued events is preserved by the Broker. When the BrokerClusterPublisher reconnects to the Broker, specifying the same client ID, it can continue processing on the same client state. Disconnecting and reconnecting can be particularly useful for applications that want to do batch-style processing at scheduled intervals.