Enabling data export and import through message queues
Before you use the integration framework to exchange data with an external application, you configure some components that are needed for inbound and outbound communication. You configure system properties, end points, publishing channels and integration controls, external systems, message queues, and cron tasks. You might need to make other configurations to export and import data.
If you are using JMS message queues, you obtain them from a JMS provider, such as IBM® MQ. If you are using Kafka message queues, you obtain a Kafka provider and configure the connection to it.
Other tasks include understanding the object structures and child components that you plan to use for message content, optionally setting up message templates, and setting up API keys if you plan to use machine-to-machine integration.
Procedure
- Obtain and configure the messaging queue provider.
- Register the provider in Maximo® Manage.
- Register either the JMS queus or the Kafka topics in Maximo Manage.
- Create an external system for the provider.
- Register the JMS queues or the Kafka topics with the external system.
- Configure the external sytem for sequential or continuous processing or for enabled events.
- For JMS processing, register the queues and connection factories in the
server.xml file for Maximo Manage in WebSphere® Application Server Liberty. If you are already using a supported JMS provider, use the same JNDI name as the JNDI name that you use in Maximo Manage. For more information about configuring the server.xml file, see Enabling JMS messaging for Liberty in the WebSphere Application Server Liberty documentation.