EDI Migration

An INUBIT 7.2 system can be migrated to an INUBIT 8.0 system using the system backup archive. Here, the INUBIT 7.2 system is the source system and the INUBIT 8.0 system is the destination system.

If you use EDI functionality on the source system, it contains a number of EDI artifacts, e.g., rules, templates, metadata, schemas, value lists (so called EDI qualifier), and EDI ID lists. Except the EDI ID lists the other EDI artifacts have a fixed storage position on the source system. Hence, these artifacts can be included in the system backup automatically.

EDI ID lists are deposed in one or more files that can be stored in arbitrary directories on the source system. For that reason, EDI ID lists are not included in the system backup and passed to the destination system.

To migrate the EDI ID lists the following steps are to be performed manually:

Prerequisites

The paths of all EDI ID lists existing on the source system are well known. The EDI ID list files are always named as ListOfGeneratedEDIIds.xml.
You have permission to access the EDI ID list files.
The source system’s system backup is available as ZIP archive.

Proceed as follows

Extract the system backup archive into a temporary directory.
In the temporary directory create the subdirectory ../conf/edi/id.
Copy the edi_id_backup.xml template from the directory <inubit-installdir>/inubit/bin/migration to the subdirectory ../conf/edi/id just created. This template serves as a container for all EDI ID list files of the source system. You can validate the XML file against the XML schema file <inubit-installdir>/inubit/bin/migration/edi_id_backup.xsd.
Edit the edi_id_backup.xml file just created. The edi_id_backup.xml file contains the following initial XML structure:
```
<?xml version="1.0" encoding="UTF-8"?>
<EDI_ID_BACKUP>
   <CACHE_ENTRY>
      <KEY></KEY>
      <VALUE>
         
      </VALUE>
   </CACHE_ENTRY>
   
</EDI_ID_BACKUP>
```
1. Set the content of the <KEY> element:
  
  The value is equivalent to the path to the EDI ID list files. This path is made up of the first parameter (file) of the external XSLT function misc:getNextIdForEDIMsg(file,type,text), that is used to request an EDI ID in the XSLT module, and the fixed file name ListOfGeneratedEDIIds.xml. This is necessary to ensure backward compatibility to existing INUBIT 7.2 workflows as well as to localize the EDI ID list in the INUBIT 8.0 cache.
  
  Examples:
  
  An EDI ID list is located directly in the tomcat work directory in INUBIT. The function that is used to get the EDI ID list is the following: misc:getNextIdForEDIMsg('.','VDA4938','ZF'). The following example shows the resulting path:
  
  Windows: <KEY>.\ListOfGeneratedEDIIds.xml</KEY> Linux:` <KEY>./ListOfGeneratedEDIIds.xml</KEY>`
2. Set the content of the <VALUE> element and insert the content of the EDI ID list file into this element.
  
  You must not change the XML structure of the source file.
  
  You must not insert the XML Header <?xml version="1.0" encoding="UTF-8"?> of the EDI ID list file.
  
  VALUE-example:
  <IDs> <ListOfCreatedIDs> <MSGS> <MSG_myType_myPartner>  <LastID>7</LastID>  </MSG_myType_myPartner> </MSGS> </ListOfCreatedIDs> </IDs>
3. If you have a further EDI ID list, insert a new <CACHE_ENTRY> element and repeat the steps a and b for this EDI ID list.
  
  There must exist exact one <CACHE_ENTRY> element for each EDI ID list of the source systems.
Save the file edi_id_backup.xml.
Create a new ZIP archive from the temporary directory with the system backup archive created in step 1.

When creating the new ZIP archive, you must retain the directory structure of the primary ZIP archive.

The edi_id_backup.xml file will be validated during the migration process at run-time.

→ Now, the archive created this way serves as basis for the migration process.