Description of problem: Using CLI, it is possible to control websphere message server but config-properties can not be modified or created because its access-type is read-only. For example, /profile=MMPS-dev-03-profile/subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=FDSLPublishQueue/config-properties=baseQueueName:write-attribute(name=value,value=test) { "outcome" => "failed", "failure-description" => "JBAS014639: Attribute value is not writable", "rolled-back" => true } This is because the fact that baseQueueName(config-properties)' access-type is read-only but I don't see any reasons why this attritbute couldn't be writable. Is there any reasons the attribute has to be read-only? otherwise, it should be read-write. Version-Release number of selected component (if applicable): EAP 6.1 IronJacamar 1.0.17.final How reproducible: Need to setup Websphere Message Connection via JCA Then, try this above CLI command Steps to Reproduce: Actual results: { "outcome" => "failed", "failure-description" => "JBAS014639: Attribute value is not writable", "rolled-back" => true } Expected results: {"outcome" => "success"} Additional info:
Hi, I would like to know this ticket is under consideration. Could you update?
<config-property>'s are defined as part of the deployment descriptor. Only alternative is a JCA 1.6+ resource adapter which supports "supportsDynamic" - which WebSphereMQ doesn't.