Add multiple back-end servers to the same junction
To increase high availability of the resources protected by ISAM, we can junction multiple replica back-end servers to the same junction point. There can be any number of replica servers mounted at the same point.
- Multiple back-end servers added to the same junction point must be replica servers with identical (mirrored) Web document spaces.
- Multiple back-end servers added to the same junction point must use the same protocol.
- Do not add dissimilar servers to the same junction point.
- WebSEAL uses a least busy algorithm to determine which back-end replica server has the fewest number of request connections and forwards any new request to that server.
Steps:
Steps
- Create the initial junction. For example:
pdadmin> server task web1-webseald-cruz create -t tcp -h server1 /sales
- Add an additional back-end server replica. For example:
pdadmin> server task web1-webseald-cruz add -h server2 /sales
- From the primary ISAM server Web space, test the access to pages belonging to the junctioned servers. We must be able to access these pages (subject to permissions) and the pages must appear consistent. If a page cannot be found occasionally, or if it changes occasionally, it means that page was not replicated properly.
- Check the document exists and is identical in the document tree of both replicated servers.
Parent topic: Technical notes for using WebSEAL junctions