updateConfigElement performs an incremental update of a single specified top-level WSConfigElement, or a single, specified sub-element. The user application does not need to provide a complete WSConfigElement; it needs to provide only the primaryKeys required to identify the target configuration element instance, and the attribute/value pairs that require update.

This Oracle Communications Session Delivery Manager SOAP API release does not provide an API to update sub-elements; as a result, updateConfigElement is used to update both top-level and sub-elements. However, users cannot use updatConfigElement to add or delete sub-elements fom an existing configuration element. Use addSubElement to add a sub-element, and deleteSubElement to delete a sub-element.

When updating a sub-element, users must provide an unambiguous path to the single target sub-element that requires update. The path consists of the ACP top-level identifier, followed by one or more sub-element types. At each path level, primaryKeys (such as ACLI object names) must be supplied to ensure unambiguous element identification. For example, the following path

sipManipulation(primaryKeys)/headerRule(primaryKeys)/elementRule(name=”rule1”)

identifies a SIP element rule to be updated.

public com.acmepacket.ems.ws.service.userobjects.WSConfigResult updateConfigElement(java.lang.String targetDevice, com.acmepacket.ems.ws.service.userobjects.WSConfigElement wsConfigElement) throws com.acmepacket.ems.ws.service.fault.AcmeConfigWSFault, com.acmepacket.ems.ws.service.fault.AcmeAdminWSFault