Mid Server - how to do failover when the Data Source type is JDBC?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
As per subject, let's say I have 2 mid servers - A and B handling different data sources and integrations, and A will be down for an upcoming maintenance, so I will need to use server B to handling the work done by server A.
But as per the documentation - https://www.servicenow.com/docs/r/servicenow-platform/mid-server/t_ConfigureAMIDServerCluster.html
MID Server clusters
MID Server clusters enable multiple MID Servers with the appropriate capabilities to be grouped together for load balancing and fail-over protection.
External data sources
For performance and reliability reasons, these data sources should not be used with MID Server clusters. These external data sources should only be used with dedicated MID Servers.
LDAP
Export sets
JDBC data sources
Note: If a MID Server in a cluster fails, the failover MID Server restarts processing from the beginning of the ECC queue task, even if much of the information from the JDBC data source was already returned. This may produce duplicate data. To prevent duplicate data, use dedicated (non-clustered) MID Servers for LDAP, export set, and JDBC data sources.So what should be the correct failover process for JDBC Data Sources mid servers?
0 REPLIES 0
