---
title: "Configure alternate ports for change notifications"
description: "Configure port-based settings for Aerospike Pulsar outbound change notifications to route data to multiple destinations."
---

# Configure alternate ports for change notifications

> For the complete documentation index see: [llms.txt](https://aerospike.com/docs/llms.txt)
> 
> All documentation pages available in markdown.

The `port-based-config` section allows alternate configurations based on which port received the change notification.

This is useful, for example, when you want to ship the same change notification to multiple destinations using a single connector cluster. To do this, configure XDR to ship to different ports on the same connector instance. Then set up each port to apply different configurations to dispatch the change notifications. For this you create one DC on XDR per connector port.

::: note
You can use any port between 1024 and 65335 for Aerospike, providing the port is not being used by an existing process.
:::

For any [service](https://aerospike.com/docs/connectors/streaming/pulsar/outbound/configure/service) port you can configure any or all of the following differently from the global configuration

-   [routing](https://aerospike.com/docs/connectors/streaming/pulsar/outbound/configure/routing)
-   [format](https://aerospike.com/docs/connectors/streaming/pulsar/outbound/configure/format)
-   [bin-transforms](https://aerospike.com/docs/connectors/streaming/pulsar/outbound/configure/bin-transforms)
-   [namespaces](https://aerospike.com/docs/connectors/streaming/pulsar/outbound/configure/namespaces)

### Example

This example routes records to alternate destinations based on the incoming port.

```yaml
port-based-config:

  8901:

    routing:

      mode: static

      destination: portOne
```