Skip to Content

Many Seeburger EDI-Adapter-Users also utilize the Professional Message Tracking either as a daily tracking tool, to be able to look at original EDI-data or as the basis to hand over the EDI-files to a “Longterm Archiving Solution”.

With the new PI 7.31 being available along with the new version 2.2 of the Seeburger EDI-Adapters I have received several questions regarding upgrades of PMT and regarding the possible move of PI to a different server.

Use case:

This document describes on a high level the required steps to migrate all data that has been stored via PMT to a newly installed system, so that your historic data can also be viewed from the new environment.

Important Remarks/Limitations:

  • If you are upgrading your server but all components/database are the same as before, the procedure can be different
  • If you use specific groups /clientIDs, stylesheets or other viewer templates, additional steps need to take place to also take over this information
  • This document does not replace the installation-guidelines provided by Seeburger along with the MessageTracking-DVDs

1. Install the PMT on the new server according to the Installation Guide delivered on the DVD  (document SAP_xiinstallation_en.pdf )

    

The steps are described in more detail in the Installation-Documentation

Since Version 2.1.3 the name of the files to be deployed are

  • SeeXIMessageArchiving.sca
  • SeeFileStoreModulePI.sca

Remark:

Before the following step (export) is executed, it should be verified, that all relevant MT-jobs are stopped

(Archiver, Consolidator, Reorganisation) along with the messagearchiving-application in NWA.

It is also advisably to stop all Sender-Channels (or adapters) during the export, so that no new entries are made to the MT-database during the export

2. Export the following 3 tables from the existing PMT – database

  • tBISMT_Workflow
  • tBISMT_Documents
  • tBISMT_Documents2

Remark:

If PMT is connected to a Longterm Archiving Solution, additional tables need to be exported (with the references to the archiving system/status)

3. Copy content and grant access to the folder that contains  Professional Message Tracking attachments
    (for example in path  /usr/sap/<SAPSID>/SYS/global/seeburger/filestore) from source system to destination system

    The correct path is specified in the parameter  BISMT_MSGDIR

Remark:

Before the following step (import) is executed, it should be verified, that all relevant MT-jobs are stopped

(Archiver, Consolidator, Reorganisation) along with the messagearchiving-application in NWA.

It is also advisably to stop all Sender-Channels (or adapters) during the import, so that no new entries are made to the MT-database during theimport procedure.

4. Import the content of the previously exported 3 tables to the new database

  • tBISMT_Workflow
  • tBISMT_Documents
  • tBISMT_Documents2

5. Configure the following settings in the SAP config tool

(taken from installation-doc)

For setting the “mode”, you should make sure that the same mode is used on the new system than has

previously been unsed in the existing environment,e.g.

Mode 1:

(directory names correspond directly to the first 4 digits of the workflow ID)

Mode 2:

(directory names are determined by using calculated hash-value)

Please verify the specified mode by checking example messages in the folder mentioned under point 3

or preferably by checking this parameter in the config tool of the current environment.

(this is important to make sure that previous data can be accessed with newer MT versions)

6. Verify that the MessageTracking is properly started

(screenshot taken from PI 7.31)

7. Check if Message Tracking attachments are accessible through the Message Tracking search screens.

Remark:

The steps 2-4 can also be repeated multiple times (e.g. once during the installation…and then again during the “Go Live” of the new system, to make sure it has also the latest data from the old system included)

Feedback:

Since there might be different steps to be executed depending on the used databases, I have not provided any specific description on that part but usually rely on the DB-Administrators to perform the export/import in the correct way.

If you have any specific questions, further comments or useful hints/remarks, please provide them in the comment-section and I will incorporate them to the blog.

Outlook:

I am planning also to write additional blogposts around MessageTracking on different topics like

  • include SAP status messages in PMT
  • using Agenda tables for setting dynamic values in outgoing channels


To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Former Member

    That is very helpful blog Stefan.

    Can you please list the steps to migrate Message Tracking users, Search Profiles and some additional MT modules like Masterdata and Reporting?

    Regards

    Naycho

    (0) 
  2. Former Member

    Hi,

    It is very useful information…I have one issue with

    • tBISMT_Workflow

    One of the UDF in message mapping is accessing the table mentioned above…

    the input it is taking is the message ID and output is the GLN number…

    Could you please let me know where i can maintain these entries in SEEBURGER…

    (0) 

Leave a Reply