This article outlines the new ways that properties can be edited on IBM Integration Bus v10 objects now that MBX is no longer available.
Web UI
In IIB v10 the web UI replaces the functionality of MBX. One of the capabilities that has been added to the web UI to achieve this is the ability to edit properties on an integration node, integration server and on a message flow.
Editing the properties is as simple as selecting the resource from the tree view and then selecting the edit button in the top-right corner.
The editable properties are then listed in a table with a button on each row that allows the property to be edited.
It is possible to edit one or many properties before saving the changes and you will be warned if you try to close the edit panel without saving your changes.
The properties listed for the resources have been increased so that the set available for editing match the set that were available in MBX. These include component properties on an integration node, resource manager properties on an integration server and user-defined properties on a message flow.
REST API
New REST calls have been implemented so that properties can be viewed and edited. The calls allow editing of single properties or a group of properties with a single call.
Items in italics should be replaced with the values that you want to work with.
Integration node APIs
apiv1/properties
– PUT with a JSON array of properties allows setting of a group of properties on the execution group. The group can contain one or many properties.
apiv1/properties
– GET returns a list of properties of the EG and components.
apiv1/properties/property name?value=new value
– PUT allows setting of a single named property on the node
apiv1/components
– GET views all components
apiv1/components/component name
– GET views named component
apiv1/components/component name/properties
– GET views the named components properties
apiv1/components/component name/properties/property name?value=new value
– PUT allows setting of a single named property on the component
Integration server APIs
apiv1/executiongroups/eg name/properties
– PUT with a JSON array of properties allows setting of a group of properties on the execution group. The group can contain one or many properties.
apiv1/executiongroups/eg name/properties
– GET returns a list of properties of the EG and resource managers.
apiv1/executiongroups/eg name/properties/property name?value=new value
– PUT allows setting of a single named property on the execution group
apiv1/executiongroups/eg name/resourcemanagers
– GET views all resource managers
apiv1/executiongroups/eg name/resourcemanagers/RM name
– GET views named resource manager
apiv1/executiongroups/eg name/resourcemanagers/RM name/properties
– GET views named resource managers’s properties
apiv1/executiongroups/eg name/resourcemanagers/RM name/properties/property name?value=new value
– PUT allows setting of a single named property on the resource manager
Message Flow APIs
apiv1/.../messageflows/flowName/properties
– PUT with a JSON array of properties allows setting of a group of properties on the flow. The group can contain one or many properties.
apiv1/.../messageflows/flowName/properties/propertyName?value=new value
– allows setting of a single named property on the flow
N.B the URI to identify the message flow will change depending on the location of the flow when it is deployed to the server e.g. inside an application or library.