How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Oracle WebLogic Server JMS API

Manage JMS servers, system resources, queues, and connection factories

Oracle WebLogic Server JMS API is one of 33 APIs that Oracle WebLogic Server publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 5 JSON Schema definitions.

Tagged areas include JMS. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a JSON-LD context, tutorials, and 5 JSON Schemas.

This API exposes 17 operations across 10 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 3 base URLs: http://localhost:7001/management/weblogic/latest, http://{host}:{port}/management/weblogic/{version}, https://{host}:{port}/management/weblogic/latest.

17 operations 10 paths 17 schemas 1 DELETE10 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
http://localhost:7001/management/weblogic/latest
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Oracle WebLogic Server JMS API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • basicAuth — HTTP Basic authentication using WebLogic Server credentials. Users must have appropriate roles (Admin, Operator, Deployer, or Monitor).

Paths & Operations 17

Across 10 paths, the API surfaces 17 operations — 1 DELETE, 10 GET, 6 POST. Each is listed below with its method, path, parameters, and response codes.

JMS 17

Manage JMS servers, system resources, queues, and connection factories

GET
/edit/JMSServers
Oracle WebLogic Server List all JMS servers
listJMSServers → 200
POST
/edit/JMSServers
Oracle WebLogic Server Create a JMS server
createJMSServer 1 param body → 201
GET
/edit/JMSServers/{jmsServerName}
Oracle WebLogic Server Get a JMS server configuration
getJMSServer 1 param → 200
DELETE
/edit/JMSServers/{jmsServerName}
Oracle WebLogic Server Delete a JMS server
deleteJMSServer 2 params → 204
GET
/edit/JMSSystemResources
Oracle WebLogic Server List all JMS system resources
listJMSSystemResources → 200
POST
/edit/JMSSystemResources
Oracle WebLogic Server Create a JMS system resource
createJMSSystemResource 1 param body → 201
GET
/edit/JMSSystemResources/{jmsResourceName}/JMSResource/connectionFactories
Oracle WebLogic Server List JMS connection factories
listJMSConnectionFactories 1 param → 200
POST
/edit/JMSSystemResources/{jmsResourceName}/JMSResource/connectionFactories
Oracle WebLogic Server Create a JMS connection factory
createJMSConnectionFactory 2 params body → 201
GET
/edit/JMSSystemResources/{jmsResourceName}/JMSResource/uniformDistributedQueues
Oracle WebLogic Server List JMS uniform distributed queues
listJMSDistributedQueues 1 param → 200
POST
/edit/JMSSystemResources/{jmsResourceName}/JMSResource/uniformDistributedQueues
Oracle WebLogic Server Create a JMS uniform distributed queue
createJMSDistributedQueue 2 params body → 201
GET
/edit/JMSSystemResources/{jmsResourceName}/subDeployments
Oracle WebLogic Server List JMS sub-deployments
listJMSSubDeployments 1 param → 200
POST
/edit/JMSSystemResources/{jmsResourceName}/subDeployments
Oracle WebLogic Server Create a JMS sub-deployment
createJMSSubDeployment 2 params body → 201
GET
/edit/fileStores
Oracle WebLogic Server List all file stores
listFileStores → 200
POST
/edit/fileStores
Oracle WebLogic Server Create a file store
createFileStore 1 param body → 201
GET
/JMSServers
Oracle WebLogic Server APIs List all JMS server metrics
getJMSServers → 200401
GET
/JMSServers/{jmsServerName}
Oracle WebLogic Server APIs Get JMS server metrics
getJMSServersByJmsServerName 1 param → 200401404
GET
/JMSServers/{jmsServerName}/destinations
Oracle WebLogic Server APIs List JMS destinations
getJMSDestinations 1 param → 200401404

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are JMSServerMetrics (11 properties), JMSDestinationMetrics (11 properties), JMSServer (7 properties), JMSServerCreateRequest (5 properties). Each schema is shown below with its type and property counts.

JMSDistributedQueue
object
3 properties
FileStoreCreateRequest
object
3 properties 1 required
JMSSubDeployment
object
2 properties
JMSSystemResourceCreateRequest
object
2 properties 1 required
JMSServerCreateRequest
object
5 properties 1 required
Link
object
3 properties
FileStore
object
4 properties
JMSConnectionFactoryCreateRequest
object
2 properties 1 required
JMSSystemResource
object
4 properties
JMSConnectionFactory
object
3 properties
JMSDistributedQueueCreateRequest
object
2 properties 1 required
Identity
object
1 property
JMSServer
object
7 properties
JMSSubDeploymentCreateRequest
object
2 properties 1 required
JMSDestinationMetrics
object
11 properties
JMSServerMetrics
object
11 properties
Error
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

oracle-weblogic-jms-api-openapi.yml Raw ↑

Other APIs Oracle WebLogic Server publishes across the network.

WebLogic WLST (WebLogic Scripting Tool) API
WebLogic JMX API
Oracle WebLogic Server Application Deployment API
Oracle WebLogic Server Application Deployments API
Oracle WebLogic Server Application Runtime API
Oracle WebLogic Server Clusters API
Oracle WebLogic Server Data Sources API
Oracle WebLogic Server Deployment Configuration API
Oracle WebLogic Server Deployment Lifecycle API
Oracle WebLogic Server Domain Configuration API
Oracle WebLogic Server Domain Runtime API
Oracle WebLogic Server Edit Session API
Where this information came from

This is an independent, third-party profile of Oracle WebLogic Server JMS API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.