Introduction: -
Please refer Part 1 of this blog post if not already, before going through this article. I have shared the link for the same in the reference section. Part 1 will provide the required technical background for the CC server installation.
I will be explaining the CC 2020 Core server setup in this article.
Core server consists of below services.
- Dispatcher
- Guider
- Updater
- Rater
- Taxer
- Bulkloader
As per SAP standard, in a multi-host landscape,
- Dispatcher and Guider should be deployed in one host(Global Host).
- Rater, Updater, Taxer and Bulkloader on separate hosts.
- Core Database on a separate host.
As part of my POC, I have setup all Core services on one VM and HANA DB on another VM.
Installation Steps: -
Choose System SIDs: -
- HANA SID : CCD
- HANA Installation number : 02
- Core Server SID : ACB
- Core Server instance numbers :
- Guider : 00
- Rater : 01
- Dispatcher : 02
- Updater : 03
Note: You can use any instance number between 00 - 99 for the services and hana db.
Download HANA DB and CC Installation Software: -
- Download HANA 2.0 software from SAP marketplace.
- SAP Marketplace -> Software downloads -> Installations & Upgrades -> By Alphabetical index -> H -> HANA Platform Edition -> HANA platform edition 2.0 -> Installation
- Download CC 2020 software from SAP marketplace.
- SAP Marketplace -> Software downloads -> Installations & Upgrades -> By Alphabetical index -> C -> Convergent Charging -> Convergent Charging 2020 -> Installation
Download JCE Jurisdiction Policy files archives
- SAP Marketplace -> Software downloads -> Support Packages and Patches -> SAPCRYPTOLIB -> COMMONCRYPTOLIB 8 -> select OS as Linux x86_64
Define a File system for HANA DB and CC system in Linux VM: -
# |
Mount Point |
Storage Type |
Storage (GB) |
1 |
/usr/sap |
SAS |
32 |
2 |
/hana/data |
SSD |
64 |
3 |
/hana/log |
SSD |
32 |
4 |
/hana/shared |
SAS |
128 |
- CC VM: -
- OS : SLES 15 SP1
# |
Mount Point |
Storage Type |
Storage (GB) |
1 |
/usr/sap |
SAS |
32 |
2 |
/sapmnt |
SAS |
32 |
3 |
/workingDirectory |
SAS |
32 |
- workingDirectory: It is used by the instances of the Core Server to store data files resulting from business operations. It should be shared in all hosts where Core server instances are installed.
- Note: Above sizing is taken for POC only. For productive systems, you will have to do the sizing of the HANA DB and CC server as per the number of users and data size.
Install HANA DB and CC Core server
Install HANA DB:-
- There are good articles available for HANA installation, so I am not going much on the HANA installation part. Please follow those and complete the HANA DB installation.
- Create a user in HANA DB using sql command or by using HANA studio.
- Assign Roles : CONTENT_ADMIN, MODELING, PUBLIC
- Assign Privileges : EXPORT, IMPORT
- Disable the expiration of the user password.
Install CC Core server.
- Install JVM
- Setup below environment variables
- SAPCC_JAVA_HOME= <SAP_JAVA_PATH>
- NI_USEIPv6=1, if this host uses IPV6
- SAP_IPv6_ACTIVATE=1, if this host uses IPV6
- Run Sapinst from root user and setup Core Server.(The images used below are all from my POC installation.
- Select Convergent Charging -> Install-> Core Server - First Step, This is the first step of installing Core server. You can use Core Server - Add Instances for installing services on different hosts.
- Provide Core server SID.
- update the <sid>adm password
- Run the prerequisite check
- For Core server, we can go with a temporary license as well. For this POC, I selected temporary license. It is not recommended for productive usage.
- Select source DB
- Update the hana db host details along with user, we have created in hana db during the initial stage
- mode: select multiple container and update HANA SID and port. For a single tenant, the port number will be 3<db instance number>15.You can select single container also if there is only one tenant in your DB.
- Select the path of the workingDirectory
- You can update the CA introscope agent host and port if you have already setup. This is not mandatory and can add later also.
- You can update the SLD url if already setup. This is not mandatory and can add later also.
- Security: You can enable the usage of encryption for the communication channels. This is recommended for productive systems. I have disables as this is a POC setup.
- Update the password of CC master user user 'admin'. admin is the super user for CC.
- Select appropriate tax framework as per the country and business verticals. I selected VAT. It may vary for others.
- Select the integration scenario. I choose stand alone as this was for POC purpose only. You will have to select at least option 2(billing and invoices in SAP Convergent Invoicing) to test various scenarios.
- Update the instance numbers of the Core server services. I selected only Dispatcher, Guider, Updater and Rater. You can select Taxer and Bulkloader as well.
- Host and port details for web services
- Complete installation
Post Installation Activities
- License: Use the setup tool inside core Server instance to install permanent license.
SAP MC system status
Login to Core Server
- Use the core_tools.sh in /usr/sap/Core_tools to launch the Core server
- Enter user as admin and the password
Conclusion: -
Completed the CC2020 Core server setup with services Dispatcher, Updater, Guider and Rater. Always make sure to apply permanent license before the temporary license expires. Sometimes system will through communication error while logging in. This happens when dispatcher is down. you can use admin+ tool in the above path to check the status of each services from OS level. I will be explaining all the tools available in CC2020 in a separate post. In Part 3, I will be explaining the BART server setup for CC2020.
Reference: -
- All the images used in this article are taken from the POC project by running sap SWPM tool.
- https://help.sap.com/doc/feb35a826117431fba7b6c87af8c1686/2020.0/en-US/Installation_and_Maintenance_...
- Part 1 : SAP Convergent Charging 2020 FP0 Installation with HANA 2.0 Database- Part 1- Overview | SAP Blogs