Reconfiguring the Load Balancer when you configure multiple API Portal machines
If you are configuring multiple API Portal machines, you need to check the load balancer components on each one and ensure that the HTTPD.servername parameter is set to the correct IP address of server.
To reconfigure the load balancer component
1. Start the ACC.
2. At the command line, type show instance loadbalancer_m to see the current configuration settings of the load balancer component. For example:
ACC+ localhost>show instance loadbalancer_m
ID: loadbalancer_m state:STARTED type:com.aris.runnables.httpd.httpd-run-prod-98.0.0
classifier=runnable type=zip
Configuration parameters:
HTTPD.LimitRequestFieldSize=32768
HTTPD.access.root=granted
HTTPD.keepalive=on
HTTPD.modjk.max_packet_size=32768
HTTPD.modjk.stickySessions.abs=true
HTTPD.modjk.stickySessions.ads=true
HTTPD.modjk.stickySessions.ecp=true
HTTPD.modjk.stickySessions.processboard=true
HTTPD.modjk.stickySessions.umc=true
HTTPD.port=18101
HTTPD.servername=192.0.2.11
HTTPD.ssl.port=18102
appcontext.abs=abs
appcontext.cop=/
appcontext.ecp=collaboration
plugin.ping.search.for.processes=false
zookeeper.application.instance.host= portal01.my.org
zookeeper.connect.string=localhost:18043
3. Examine the HTTPD.servername parameter. If it needs to point to another server IP, you can change it by using the reconfigure command. To do so:
a. Stop the load balancer component:
stop loadbalancer_m
b. Change the value of the HTTPD.servername parameter and specify the new IP address:
reconfigure loadbalancer_m +HTTPD.servername=new_IP
c. Start the load balancer component:
start loadbalancer_m
Contact Support
|
Community
|
Feedback