IBM Support

Application Export/Import Vs Data Export/Import

Technical Blog Post


Abstract

Application Export/Import Vs Data Export/Import

Body

Application Export/Import Data Export/Import
  • This functionality works directly from applications.
  • Though it relies on the object structure component of Integration Framework but no other Integration components like Publish Channels, End Points, and JMS Queues are needed to be configured.
  • The application export and import is done synchronously without the use of JMS Queues.
  • No applications out of the box are pre-configured with import and export capabilities.
  • This functionality can be enabled from the select action menu of the object structure application.
  • This Export and Import Process will have the option to save the data in either XML file or flat delimited file format.
  • During enablement of this functionality the value in the maximum count field limits the number of rows that can be exported or imported during a single execution.
  • After the functionality is enabled in object structure application, security access need to be granted to it through Security Groups Application.
  • After granting the security access, logoff and re-login is needed in order for the application export and import icons to appear on tool bar of the associated application.
  • For application export if the user is on the list tab of the application, the query that is current on the list tab will drive what content is exported.  If the user is on the other tab of the application and the export is initiated then that specific record is exported.
  • When the user start the export, a dialog window appears that allows the user to save the file to a folder location of their choice.
  • For application import the user needs to select the type of file and specify the location of the file to import.
  • The import preview will allow the users to validate the data prior to loading.
  • During application import if the load encounters errors, no data is loaded as the file is processed as a single transaction with a single commit.
  • Data Export feature is used to perform bulk export of message data from the Integration Framework to an External System.
  • The process is associated with each publish channel and its associated external system so both should be enabled before initiating the process.
  • The Export Condition is optional and is used to filter the desire content and to limit the amount of data being exported.
  • The process performs the standard outbound processing on the result set of the export condition for the selected publish channel.
  • The exported data in the message form is dropped into the outbound queue of the associated external system and then processed from the queue to the configured endpoint.
  • Data Import feature is used to load data from either XML or Flat files to update the Maximo database.
  • The process is associated with Enterprise Service and its associated External System so both should be enabled before initiating the process.
  • For importing flat files the Enterprise Service Object Structure must support flat file structures, the Support flat File Structure check box on the associated object structure should be selected in the Object Structure application.
  • To validate the sample data before importing and committing to the database, the Import Preview option can be used.
  • The imported data in the message form is dropped into the inbound queue of the associated external system and then processed from the inbound queue to the application objects for updating.

 

 

[{"Business Unit":{"code":"BU005","label":"IoT"}, "Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""}]

UID

ibm11133319