Emman Sun
Emman Sun

Reputation: 405

WSO2 APIM 2.0 Clustering deployment with traffic manager cluster

From the document, for traffic manager, except publisher will use HTTPS to communicate with traffic manager, others used thrift and jms. so for thrift & jms related URL:

connectionfactory.TopicConnectionFactory = amqp://admin:admin@clientid/carbon?brokerlist='tcp://<Traffic-Manager-host>:5676'
topic.throttleData = throttleDat

<ThrottlingConfigurations>
        <EnableAdvanceThrottling>true</EnableAdvanceThrottling>
        <DataPublisher>
            <Enabled>false</Enabled>
            <Type>Binary</Type>
            <ReceiverUrlGroup>tcp://<Traffic-Manager-host>:9611</ReceiverUrlGroup>
            <AuthUrlGroup>ssl://<Traffic-Manager-host>:9711</AuthUrlGroup>
        ……………………
        </DataPublisher>
        <PolicyDeployer><ServiceURL>https://<Traffic-Manager-host>:9443/services/</ServiceURL>
        ……………………
        </PolicyDeployer>
        ………………
        <JMSConnectionDetails>
            <Enabled>false</Enabled>
            <ServiceURL>tcp://<Traffic-Manager-host>:5672</ServiceURL>
        <JMSConnectionDetails>
        …………………
</ThrottlingConfigurations>

Can we config any of the traffic manager host in traffic manager cluster in gateway/publisher/store/key manager?

Upvotes: 1

Views: 494

Answers (1)

Bee
Bee

Reputation: 12502

You can do it like this.

<ReceiverUrlGroup>{tcp://127.0.0.1:9612},{tcp://127.0.0.1:9613} </ReceiverUrlGroup>
<AuthUrlGroup>{ssl://127.0.0.1:9712},{ssl://127.0.0.1:9713}</AuthUrlGroup>

You can find several patterns of traffic manager deployments in this blog.

Upvotes: 1

Related Questions