Create A New JMS Connection Factory
/management/weblogic/{version}/edit/resourceGroupTemplates/{name}/JMSSystemResources/{name}/JMSResource/connectionFactories
Add a new JMS connection factory to this collection.
Request
- application/json
-
name: string
The name property of the instance in the collection.
-
version: string
The version of the WebLogic REST interface.
-
X-Requested-By: string
The 'X-Requested-By' header is used to protect against Cross-Site Request Forgery (CSRF) attacks. The value is an arbitrary name such as 'MyClient'.
Must contain a populated JMS connection factory model.
object
-
defaultTargetingEnabled(optional):
boolean
Default Value:
false
Specifies whether this JMS resource defaults to the parent module's targeting or uses the subdeployment targeting mechanism.
When set to true, this resource implicitly inherits the targeting of its parent module. When set to false, this resource gets targeted based its subdeployment's targets, if one is specified.
-
id(optional):
integer(int64)
Read Only:
true
Return the unique identifier of this bean instance.
-
JNDIName(optional):
string
The global JNDI name used to look up a connection factory within a clustered JNDI namespace.
In a clustered environment, this name is propagated to the entire cluster. If you want the JNDI name to be bound only on the local server, and not propagated to the rest of the cluster, then use the
Local JNDI Name
setting.If not specified, then the connection factory is not bound into a clustered JNDI namespace.
-
localJNDIName(optional):
string
The local JNDI name used to look up the connection factory within the JNDI namespace of the server where the connection factory is targeted. In a clustered environment, this name is bound only on the local server instance and is not propagated to the rest of the cluster.
If not specified, then the connection factory is not bound into the local JNDI namespace.
-
name(optional):
string
Read Only:
true
Constraints
- legal null
-
notes(optional):
string
Optional information that you can include to describe this named JMS descriptor bean.
JMS module saves this note in the JMS descriptor file as XML PCDATA. All left angle brackets (<) are converted to the xml entity
<. Carriage returns/line feeds are preserved.)>
- Note:
If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.
-
subDeploymentName(optional):
string
Gets the name of the sub-deployment to use when targeting this entity
Entities are targeted using a sub-deployment with this name. The targets of the sub-deployment will be the targets of this entity.
-
Admin: basic
Type:
basic
Description:A user in the Admin security role.
-
Deployer: basic
Type:
basic
Description:A user in the Deployer security role.