SAP Knowledge Base Article - Public

3408234 - CPM for PI migration example

Symptom

According to SAP Note #3331807 - "SAP Cloud Print Manager for Pull Integration 800 Patch 0 / Patch 1", the CPM for PI (Cloud Print Manager for Pull Integration) will use LiteDB for internal data.

If a CPM for PI version older than 800/0 will be upgraded to 800/0 version or later, a migration will be needed to move internal data into LiteDB.

This SAP KBA show an example about the migration steps.

*Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.*

Environment

  • S/4HANA Cloud, all versions
  • CPM for PI (Cloud Print Manager for Pull Integration), as of version 800/0

Resolution

The following steps display the migration of CPM for PI from version 770/4 to version 800/3.

  1. Download the CPM for PI installer file from https://me.sap.com/softwarecenter (and there from "SUPPORT PACKAGES AND PATCHES" -> "By Alphabetical Index (A-Z)" -> "C" -> "SAP CLOUD PRINT MANAGER").
     
  2. In the Windows Start Menu search for the "Services" app, and start it:

     
  3. Stop the Service of CPM for PI:

     
  4. Open the downloaded installation file:

     
  5. After a short initialization, the Installation welcome screen appears:

    Press "Next".
     
  6. No changes are needed in the selection window:

    Press "Next".
     
  7. If needed, the installation directory can be changed here, otherwise, the default can be used:

    In any case, press "Next".
     
  8. Installation begins. If installation successfully concluded, this screen appears:

    Remark: The installation itself took less than 30 seconds for the writer of this KBA Article.
    Press "Close" to exit the Installer.
     
  9. Do not start the Service of CPM for PI yet.
    Instead, in the Windows Start Menu start the CPM for PI program with Administrative rights:

     
  10. A welcome screen displays the changes:

    Simply press the "Close" button.
     
  11. The popup for migration appears:

     
  12. In this case, the relevant Windows Administrator user was already available in the "Service User" drop-down list.
    After selecting this user from the drop-down list, all fields were automatically filled - except for the "Password" field, which had to be manually filled:

     
  13. After providing the password and pressing the "Migrate" button, the actual migration begins.
    Migration finished once the "Migration done" popup is displayed:

    Remark: The migration itself took less than 3 seconds for the writer of this KBA Article with a small number of Cloud Systems and Print Queues.
     
  14. After pressing the "OK" button in the above popup, the CPM for PI appears:

    Press "Yes" to start the Service of CPM for PI.

Finally, CPM for PI can be used as usual.

See Also

SAP Note #3331807 - "SAP Cloud Print Manager for Pull Integration 800 Patch 0 / Patch 1"

Keywords

Cloud Print Manager for Pull Integration migration, Migrating Cloud Print Manager for Pull Integration, CPM for PI migration, Migrate CPM for PI, Cloud Print Manager migration, Migrate Cloud Print Manager , KBA , BC-CCM-PRN , Print and Output Management , BC-CCM-PRN-OM-PQ , S/4HANA Output Management Print Queues , BC-CCM-PRN-OM-PM , S/4HANA Output Management Print Manager , How To

Product

SAP S/4HANA Cloud Public Edition all versions ; SAP S/4HANA Cloud all versions