Configuring a secured channel when using Load Balancer
This topic provides information about how to configure a secured channel when using a Load Balancer for the the BMC Remedy ITSM 7.6.05: Mobility server to communicate sensitive information to and from the BMC Remedy ITSM 7.6.05 - Mobility Incident Management application and the BMC Remedy ARserver.
Configuring the Load Balancer
The following procedure provided information about configuring the load balancer:
- Configure SSL-offloading proxy
- Configure the load balancer to map the incoming DNS and SSL port to the BMC Remedy ITSM: Mobility server's IP address and port. For example:
nextgen.onbmc.com:443 -> 107.80.20.123:2088
Configuring the BMC Remedy ITSM: Mobility server
The following procedure provided information about configuring the BMC Remedy ITSM - Mobility server:
- In the services-config.xml, file configure the BMC Remedy ITSM - Mobility server to use the port that the load balancer maps to for example:
<channel-definition id="mobility-nio-amf" class="mx.messaging.channels.AMFChannel">
<endpoint url="http://{server.name}:2088/nioamf " class="flex.messaging.endpoints.NIOAMFEndpoint"/>
<server ref="mobility-nio-server"/>
<properties>
<polling-enabled>false</polling-enabled>
</properties>
</channel-definition>
<endpoint url="http://{server.name}:2088/nioamf " class="flex.messaging.endpoints.NIOAMFEndpoint"/>
<server ref="mobility-nio-server"/>
<properties>
<polling-enabled>false</polling-enabled>
</properties>
</channel-definition>
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*