SAP Customer Checkout Manager migration to a new server
A German version of the blog post can be found here.
In this blog post, you will learn the basics needed to migrate an SAP Customer Checkout Manager (CCOm) installation to another server. This includes the prerequisites and the fundamental steps to follow.
What information and access are required?
What steps should be followed?
?
Information and Access
First, ensure that the required access and connection data mentioned above are available. Without the admin password and hash key used during the initial configuration, the migration as described here will not be possible. Useful information about the currently used version, database connection, and the database schema can be found in CCOm under Configuration/Information.
Avoid deviations between the old and new installations whenever possible.
Next, a copy of the CCOm database should be made, which can also be deployed on a new server if necessary. A backup of the Apache Tomcat folder (e.g., under C:\Program Files\Apache Software Foundation\Tomcat 9.0_Tomcat9_FP19) should also be created.
The ccos.war file (e.g., C:\Program Files\Apache Software Foundation\Tomcat 9.0_Tomcat9_FP19\webapps\ccos.war) and the "CustomerCheckout Central Server" folder (e.g., C:\SAP\CustomerCheckout Central Server) should be transferred to the new server.
In the next step, the CCOm installation is performed as usual, choosing the same port as in the old installation. The ccos.war file from the old server can be used, or a new file can be downloaded. It is important to choose the same version (same feature pack) as in the CCOm installation on the old server.
领英推荐
Procedure
The migration should generally not take place during active operations. Plan sufficient time outside of business hours for the migration. Additionally, it is advisable to test the process in a test environment first.
Start by stopping the CCOm on the old server, which can be done via the services.?
Initial Configuration
During the initial configuration, the connection data for the corresponding database is selected, and a user with read and write permissions who can create a new schema (e.g., Admin/sa) is entered.
If the "CustomerCheckout Central Server" folder is not replaced, it is not necessarily required to use the same database user as in the original initial configuration. However, since this folder contains, for example, the images of the quick selection, a replacement is recommended. The schema name, on the other hand, must have the same name as in the original installation on the old server (e.g., CCOS).?
Check the box "Automatically create schema (if non-existent)" to allow the database schema to be recreated initially.
Now use the same admin password and hash key as in the original CCOm installation on the old server:
Click OK and wait until the message appears indicating that the configuration was successful. You can check or confirm that the installation has been carried out correctly by logging in to CCOm.
Now, shut down Apache Tomcat again (e.g., via services), replace the new "SAP Customer Checkout Central Server" folder with the one copied from the old server (if using the same database user as in the initial configuration), and swap out the previously copied database.
Finally, restart CCOm via services and verify after logging in that all data (customers, users, items, receipts, etc.) is available. Don't forget to enter the new connection data in the POS system under Configuration/Integration/SAP Customer Checkout Manager.
Autor: Tilman Gosch