Troubleshooting the Maximo Manage enterprise system integration and data export

Resolving The Problem

Before you begin troubleshooting, review the online product documentation in IBM Knowledge Center and troubleshooting and known issues articles for Maximo Application Suite. 

• Integrating Maximo Manage with Maximo Application Suite applications
• Maximo Health product documentation
• Maximo Predict product documentation 
• Troubleshooting and known issues for Maximo Application Suite 

Review the following sections for additional troubleshooting information. In all cases, ensure that the latest interim fixes for your Maximo Manage enterprise system, the IoT Connector, and the Maximo integration framework are installed.

Errors occur for field lengths or attributes when data is exported.

When you export data from a Maximo Manage enterprise system into Maximo Health or Maximo Predict, if field length or attribute errors occur and the data cannot be exported, unique attributes exist in your Maximo Manage enterprise system or the export contained data that is not supported or used by default in Maximo Health or Maximo Predict. 

An attribute is considered unique if it does not exist in Maximo Health or Maximo Predict or if the attribute does exist but is not completely identical in both the application and in the Maximo Manage enterprise system. If your Maximo Manage enterprise system includes one or more industry solutions or an add-on, that system likely includes attributes that Maximo Health and Maximo Predict do not have. For example, the Y attribute might exist in both systems, but the field length of the attribute in the Maximo Manage enterprise system is different than the field length of the attribute in Maximo Health. In this case, the Y attribute is considered a unique attribute.

Additionally, some Maximo attributes are not, by default, used in Maximo Health or Maximo Predict. For example, asset data is used, but service address data for those assets is not used. If you do not restrict service address attributes for ASSET object, in the MHASSET object structure, errors occur when asset data is exported.

To resolve the problem, either restrict the attributes, synchronize the attributes, or, if the attribute or data type is unsupported by default, before you export the data, create an associated integration framework to support the data. For example, you might create an object structure, a publish channel, and a processing class in both the Maximo Manage enterprise system and in Maximo Health.

For more information about restricting and synchronizing attributes, see step 7 in Preparing the systems for Maximo Health or Maximo Predict 8.1. You can complete these same steps to restrict or synchronize attributes for 8.0. 

Linear asset data is not exported

When you export asset data, preventive maintenance (PM) data, work order data, or other data that is related to linear assets into Maximo Health or Maximo Predict, errors occur because linear asset data cannot be exported. Before you export asset, preventive maintenance, or work order data, restrict fields that are related to linear assets.

For example, if you integrated with a Maximo Manage enterprise system, complete the following steps:

1. In the Maximo Manage enterprise system, from the Start Center, in the Object Structures application, open the related object structure.
2. In the More Actions menu, select the Exclude/Include Fields action.
3. In the Source Objects for table, select the related object.
4. In the Persistent Fields table, select the Exclude checkbox for the fields that represents the linear asset attribute.
5. Click OK.
6. Save the record.

Timeout occurs during data export

When you export data into Maximo Heath or Maximo Predict, a timeout can occur before the data is exported. Performance might be improved by completing one or more of the following tasks:

• Exporting data in smaller batches. If you are using the Data Export button, you can use a WHERE clause to limit the number of records that you are exporting.
• Update the CONNECTTIMEOUT property for the endpoint that you used. When you configure the Maximo Manage enterprise system for integrating with Maximo Health or Maximo Predict, you use either the HEALTHXML or the HEALTHJSON endpoint. To update the property, in the endpoint record, in the Value field for the property, specify a timeout value in milliseconds. Ensure the Allow Override checkbox is selected and that your changes are saved.
• If you are using JSON, update the value for the mxe.oslc.maximportcount system property. You might improve performance by changing the limit to a smaller number. For more information, see step 1 in Configuring the Maximo Manage enterprise system for Maximo Health or Maximo Predict.