About NoSQL System Resources
A NoSQL system resource is a domain-level resource that defines how applications access a NoSQL database. It is targeted to servers or clusters. It owns an external descriptor containing provider settings and a JNDI binding. Applications use deployer-approved local aliases to reach that binding.
See the Jakarta NoSQL Specification for more information.
Resource Configuration and Files
NoSQL system resources are managed through NoSQLSystemResourceMBean. Each child of NoSQLSystemResourceMBean references a descriptor under DOMAIN_HOME/config/nosql whose mapped filename ends in -nosql.xml.
WebLogic Server stores the configuration data for a NoSQL system resource within an XML file. DescriptorFileName, the alias for the file path of this XML relative to the configuration directory, is established during resource creation. Absolute paths, traversal, alternate directories, null names, and malformed filenames are rejected.
The default descriptor filename is derived from the management-resource name. Its mapped filesystem form must pass filename validation. DescriptorFileName is established at creation and is read-only afterward; it is not a live provider-property edit.
The descriptor namespace is http://xmlns.oracle.com/weblogic/nosql-resource, and its schema location is http://xmlns.oracle.com/weblogic/nosql-resource/1.0/weblogic-nosql.xsd. Use supported tools to maintain the domain entry and descriptor together.
Supported Configuration Shapes
The following table distinguishes resource definitions from application references.
| Configuration | Support | Requirement |
|---|---|---|
| Global resource targeted to a server or cluster | Supported | Valid descriptor and supported provider/type |
| Packaged application reference and JNDI mapping | Supported | Complete same-scope binding |
| Packaged global NoSQL resource definition | Unsupported | Configure the global resource in the domain |
| Direct global-name or sole-visible-resource selection | Unsupported | Configure a deployer-approved binding |
| Application-provided JNoSQL mapping settings | Unsupported configuration channel | Use the managed descriptor contract |
WebLogic Server supplies the Eclipse JNoSQL provider modules for the supported NoSQL providers and the Oracle NoSQL client libraries.For MongoDB, Amazon DynamoDB, Couchbase, Apache CouchDB, Elasticsearch, and Apache Solr, you must supply the selected provider’s client JARs and any additional runtime dependencies required by its JNoSQL provider. Add these libraries to the server startup classpath on every server targeted by the NoSQL resource, and then restart each affected server.
Use library versions compatible with the Eclipse JNoSQL version supplied by WebLogic Server. Add only dependencies that WebLogic Server does not already provide. Preserve product managed Jakarta APIs, JNoSQL components, and shared libraries.
The libraries must be visible to the server class loader. Placing them only in WEB-INF/lib or DOMAIN_HOME/lib is insufficient.