Use NoSQL Resources in a Cluster

The shipped setup targets the Administration Server. For a cluster deployment, target personNoSqlResource to the application’s cluster and deploy the application to that cluster. Every executing member must satisfy local targeting, effective binding, current-subject authorization, ownership, and provider availability.

When requests move between members, the destination performs its own checks. Provider runtimes and metrics remain server-local; there is no single cluster-wide provider object or counter.

For each executing member, perform the following checks after deployment and configuration changes.

Check	Required Result	Evidence
Applied configuration	Intended provider/type/JNDI and targets	Loaded resource configuration
Application binding	Intended global identity selected	Effective descriptors and successful deployment
Authorization and ownership	Current caller and owning deployment accepted	Allowed and denied application operations
Database access	Endpoint and deployment-specific authentication work from this member	Authorized application operation
Runtime lifecycle	Local state and lifecycle counts match the operation	Member-local metrics and sanitized failure information

Success on the source member does not grant authorization or establish provider availability on a destination member.

Inspect each member after configuration changes. Do not assume simultaneous cutover or distributed transaction semantics. Older servers without the new management/integration contracts cannot host the resource.

WebLogic Server clustering does not define Oracle NoSQL replication, backup, database failover, consistency, or service availability.