Description
The IBM Maximo listeners allows users to monitor and read new records from IBM Maximo system.
Configuration
To add the IBM Maximo listener to a stream, follow the steps below:
- Ensure you have a use case open in the stream designer, this can be a new use case or an existing use case
- From the toolbox on the left expand the Listeners option and scroll down until you can see “IBM Maximo”
- You can also use the search in the header to find the stream object quickly
- Click and drag the IBM Maximo listener from the toolbox onto the canvas
- Rename the listener by clicking into the text button on the action bar
- Save the Stream by clicking the save button in the action bar
- Hover over the icon for the stream object until it turns orange and then double click to open the configuration page
- You can optionally use the configure option on the action bar once you have selected the specific stream object and then clicking this option
- Configuration options
- The drop-down allows you to associate this stream object with a specific collection. The default option is derived from the default specified against the specific use case and is generated left as the same option. If you do need to change it to another collection make the change by selecting the new collection in the drop-down.
- Enter a value for the Polling Interval (the interval at which new records are accessed/checked for, in seconds)
- Enter Authentication Details
- Enter the Maximo Url
- Enter the Username
- Enter the Password
- Select Authentication Method from drop-down list
- Enter Object Settings
- Select Maximo Object from drop-down list
- Select one or more Output Properties from drop-down list
- Enter Unique ID/Timestamp Details
- Select Unique ID from dropdown list
- Click Apply on the action bar, and then save the stream using the save button.
Limitations
Only reading basic properties of Maximo objects
Release Notes
Version: | 3.02 |
Released: | 04-March-2019 |
Release Notes: | Updated help URL |
Version | Released | Release Notes |
3.01 | 13-Aug-2018 | Added error endpoint. |
3.0 | 12-July-2018 | Initial Release. |