This blog post informs you about how to install multiple SAP Customer Checkout manager in the same machine, and how to update/upgrade them.
This blog focuses on SAP Customer Checkout manager only. For SAP Customer Checkout kindly read this blog LINK .
When you download SAP Customer Checkout manager from SMP you get a .zip file and you extract the content of this zip file. It contains ccos.war and .manifest file(digital signature).
You follow our documentation for SAP Customer Checkout manager installation LINK or the screenshot based guide in PartnerEdge LINK to install SAP Customer Checkout manager.
As a result
you have a tomcat installed, the tomcat service has a name(can be verified in Windows Services), the tomcat service is running on a PORT (default port is 8080 – and this can be verified in the URL of SAP Customer Checkout manager),
by default configuration data about SAP Customer Checkout manager is stored in the location “C:SAPCustomerCheckout Central Server”, and
by default a database is created in the SAP HANA/MS SQL system where all data is stored,
If you want to have 1 more SAP Customer Checkout manager installed, then the following points needs to be taken care of. First i mention the main points and then i will inform you how to influence that.
1. Install a new tomcat however provide a different name to the tomcat service compared to last one.
2. While installing tomcat, select a different port to run the tomcat.
3. Provide some specific parameter to the new tomcat, so that it knows that the configuration file should not be created in the location “C:SAPCustomerCheckout Central Server” but the location provided in the parameter and
4. Provide a different database name during configuration so that data is stored accordingly.
Point 1 and Point 2
While installing tomcat as in the screenshot, i changed the default values for the port numbers (example: 8080 is replaced with 9080) and changed the default value of the Windows Service Name from Tomcat8 to Tomcat8TEST and continue with the installation.
Point 3
Before you copy SAP Customer Checkout manager war file in tomcat webapps folder, you need to specify in tomcat, some parameters. These parameters are read by SAP Customer Checkout manager to decide where to put the configuration files. If no parameter is specified, then a default location “C:SAPCustomerCheckout Central Server” is chosen. However since this default location is already used by the 1st installation, we need to specify the configuration file location for this installation via these parameters.
To specify the parameter you start the file as high-lighted in the screenshot. For me based on my naming convention it is Tomcat8TESTw.exe in the folder “C:Program FilesApache Software FoundationTomcat 8.5_Tomcat8TESTbin” and select the tab “Java”. In the “Java Options” along with the existing data you copy these parameters. As the name suggests, the first 2 decides the configuration and storage file path and others specify memory allocation etc. Click on apply and i will also recommend to re-start the tomcat service so that you are sure that these changes have taken effect.
-DFILE_STORAGE_PATH=C:SAPSAPCcomTEST
-DCONFIG_FILE_PATH=C:SAPSAPCcomTEST
-XX:PermSize=1024M
-XX:MaxPermSize=2048M
Now you can again continue as mentioned in our documentation, and copy the ccos.war file in the webapps folder of this new tomcat installation files.
Point 4
The configuration page will open in the new port that you specified. In the configuration based on the database driver you select, you are required to enter the information. Only important thing from a second SAP Customer Checkout manager installation perspective is that you specify a different database name/database schema name.
Example
For SAP HANA, you should specify a different schema name in the field “Database schema name”.
For MS SQL you should specify a different Database name in the field “Database connection string”.
For Apache it does not matter, because the folder itself is different. The folder where the database is stored is the tomcat installation folder. Since these are 2 different folders, there is no name conflict.
With these steps, you have 2 SAP Customer Checkout manager installed in the same system. Each one is running on its own tomcat and a specific port.
Upgrade is simple, you need to follow the steps as mentioned in our documentation. Basically replace the .war file in the webapps folder of the tomcat you want to upgrade. You will need to upgrade each SAP Customer Checkout manager 1 by 1.
If you want to install a third SAP Customer Checkout manager, you need to repeat the same steps. Remember that there should not be a conflict in PORT numbers and tomcat service names.
Also if multiple SAP Customer Checkout manager are running in the same system at the same time, the hardware requirements for the system is added up accordingly.
In this extensive blog, you have learnt how to install multiple SAP Customer Checkout manager in the same machine, and how to update/upgrade them.
Hope you enjoyed the blog. Best of luck with your SAP Customer Checkout journey.
Feel free to comment and give feedback about the blog.
About me:
My name is Bikash Bansal. I work for SAP SE, Germany. My current role is of Product Owner for SAP Customer Checkout.
You can find more blogs from me about SAP Customer Checkout here .
