Manage a Resource with REST

Use authenticated HTTPS and the server’s supported management API version. Follow its edit session, header, response, and activation task contract. The REST API reference supplies exact endpoints and payloads.

The following table applies the REST workflow to personNoSqlResource. Use the Jakarta Data and NoSQL code sample’s person_catalog database, WLS_NOSQL_ENDPOINT value, and Administration Server target.

Stage	Management Action	Expected Verification
Discovery	Locate the NoSQL collection and supported create action	Applicable collection and operations
Creation	Create personNoSqlResource in the edit configuration	Pending resource entry
Configuration	Set provider/type, JNDI, default flag, properties, and targets	Intended non-secret pending values
Protected input	Supply required credentials through protected fields	Supported protected representation
Activation	Save and activate the edit	Successful task or actionable validation failure
Runtime inspection	Inspect each target server’s NoSQL runtime	Applied state and lifecycle metrics
Application verification	Invoke an authorized bound application	Lazy provider construction and database operation
Update/removal	Apply a classified edit or removal	Documented application impact and recovery

A successful configuration response does not establish database connectivity. Distinguish request validation, activation failure, provider construction failure, authorization denial, and terminal application invalidation.