Skip to Content

CMS Cluster Member Caching After DSWS Provider Restart

ThIS sample demonstrates how to trigger CMS cluster member caching after an application server restart. It iterates over a list of known CMS cluster members and attempts to log in to each one using an empty credential set. If it is not able to connect to the CMS cluster member, it proceeds to the next one. If the login request succeeeds or if it is refused due to the invalid credentials, then the CMS cluster member is valid and the CMS cluster members are cached automatically by the DSWS provider.

View Document

Tags:
Former Member

No comments