WEBSOCKET RFC
Websocket RFC
Integration data via WebSocket RFC
Data integration between SAP cloud integration for data services and SAP integrated business plan (SAP IBP) for supply chain can occur through JDBC or WebSocket RFCs.
SAP IBP systems created as of version 2108 communicate with SAP Cloud Integration for data services via the WebSocket RFC, using the SAP_COM_0593 scenarios.
With this implementation, the Data Services Agent can connect directly to the staging tables and application tables in SAP IBP to integrate data between them and your on-premises system.
More about this source text.
Above you can see the data flow between SAP on-premises and SAP IBP using JDBC. The communication system uses the communication scenario SAP_COM_0035. In this, we can see that the data is transferred through CPI-DS.
Communication Scenario SAP_COM_0035 is used to trigger CPI-DS jobs from the SAP IBP application job.
In the above picture, we can see that CPI-DS is directly linked to SAP IBP and SAP complex system and JDBC is completely controlled by SAP.
Here we can see that the WebSocket RFC is directly communicates to the CPI-DS agent, not to the CPI-DS server, the data is transferred directly from the agent to the SAP IBP and by using the communication scenario SAP_COM_0593.
In this, the data service agent communicates directly with the SAP IBP HANA application layer instead of the HANA database layer, as you can see in the picture. WebSocket is a hybrid model i.e. it can be handled by both SAP and client.
Data Integration between SAP IBP and CPI-DS:
*Integration via JDBC can be seen in system version 2015 or less and the JDBC communication scenario uses SAP_COM_0035 and the communication system is managed by SAP.
*Integration via WebSocket RFC can be observed in system version 2108 or higher and WebSocket RFC uses communication scenario SAP_COM_0593 and communication system can be managed by both SAP and client.
* There are some basic steps through which you check what communication type your system uses, go to Scheme - DS WebSocket RFC Integration in Performance Communication Scenario app. If you are not getting anything then it means that your system uses a communication scenario maintained by SAP.
Reliability:
- Data load performance using WebSocket RFC was equal to or better than JDBC based solution.
- In WebSocket RFC the data is transferred from SAP ERP to DS Agent and then to SAP IBP Staging Table whereas in JDBC the data transfer takes place through CPI-DS which is why the architecture of WebSocket RFC is simpler than that of JDBC.
- Error analysis in WebSocket RFC is better than JDBC because errors in WebSocket RFC are more explanatory.
- JDBC has a time-out issue for long working hours and also data transfer limit. But in WebSocket RFC there is no such problem for time out and more data can be transferred as compared to JDBC.
Security:
- X.509 Support - X.509 authentication is a more secure method of accessing SAP HANA than username and password authentication.
See this help guide -
https://help.sap.com/doc/8f67cc54400d42fb9074f57797cad5e9/1.0.11.44/en-US/hci10_agent_en.pdf - PSE certification file generation.
- Better Security compliance with WebSocket RFC for hyperscale (Google cloud, Microsoft Azure…etc.)
As we can see that the data in JDBC, it transfers through CPI-DS and goes to the application tables of SAP IBP whereas in WebSocket RFC it transfers through DS Agent to SAP IBP.
Higher Volume:
- In JDBC we can see that there is a connection timeout of 10/15 minutes during the initial selection phase but there is no such problem in WebSocket RFC.
- Also in the WebSocket RFC there is no limit like 200/400m for data extraction in a single stream.
IBP Extraction:
IBP on HANA Cloud:
The WebSocket RFC has elasticity and is required for HANA Cloud-- Parallel execution of jobs when users work with Excel.
- Parallel execution of multiple jobs.
- Improved scalability.
Comparison of JDBC and WebSocket RFC using CI-DS:
| TOPIC | JDBC(Today) | WebSocket RFC |
|---|---|---|
| Ready for IBP hyperscale deployment(google cloud, Microsoft azure) | No | Yes |
| Architecture | Indirect Communication (Agent-CI-DS server – IBP) | Direct Communication (Agent-IBP) |
| Reliability | Challenges on timeout on CI-Ds server | More reliable connections between on-premises and cloud |
| Efforts for Customer | Agent to IBP connection to be maintained by customer | |
| Feature Parity | Same via Agent as today via server at runtime | |
| Logs and error handling | Very limited in IBP extraction scenario | More detailed logs and error explanation on IBP Application Log |
How to switch from JDBC to WebSocket RFC?
It requires a lot of testing and setup that's why it is done in waves. The only pre-requisite here is agent upgrade.
General information before switching over.
- Switch over projects will continue in waves.
- The first thing to do is to upgrade the agent before the wave starts.
- The wave starts from the first weekend of the month and will last for 1 month.
- Each customer has the option to choose which wave all systems should switch to.
- Basically we are running on agent but it is recommended that upgrade should be done 3-4 weeks before switching agent.
- Each wave has four weeks and it is planned that in four weeks, two weeks should be given to the non-production system and the remaining two weeks would be given to the production system for testing.
Waves
- Each wave has 4 weeks.
- 2 weeks’ test in non-production and production system.
- 5 weeks of overlapping waves with upgrades.
- Last date for the end of switchover is December 2022.
| Wave | Start Date | End Date | IBP Upgrade Date |
|---|---|---|---|
| Wave 1 | 01/04/2022 | 29/04/22 | |
| Wave 2 | 29/04/22 | 03/06/22 | 07/05/22 |
| Wave 3 | 03/06/22 | 01/07/22 | |
| Wave 4 | 01/07/22 | 29/07/22 | |
| Wave 5 | 29/07/22 | 02/09/22 | 06/07/22 |
| Wave 6 | 02/09/22 | 30/09/22 | |
| Wave 7 | 30/09/22 | 21/10/22 | |
| Wave 8 | 21/10/22 | 02/12/22 | 28/10/22 |
| Wave 9 | 02/12/22 | 30/12/22 |
The main problem is that if we have a problem in the middle of the switch then that's a challenge. The test can be done in a week but for better results, two weeks’ time is considered.
Important
- It is recommended that no new projects or tasks should be created in switchover and no propagation of tasks from sandbox to production as the non-production system communication scenario will be different from the production communication scenario.
- Freeze period duration can be reduced as it totally depends on the non-production system testing.
- We test in a non-production system and once this is done we continue our testing in the production system for WebSocket RFC.
Prerequisites and action items:
- Agent up-gradation should be done 2-4 weeks before the wave start date.
- The prerequisite is that the minimum agent version is CPI-DS 1.0.11 patch 42HF1 and upgrade to the latest patch DSODAGENT2112. More about this source text
- After upgrading the patch, we need to upgrade to the equivalent operating system. And if the agent version is out of date then both the hardware and the operating system need to be upgraded.
- After the agent is upgraded, the remaining three to four weeks will be given for testing.
- CPI-DS Agent 42 Patch HF01 and above Patches, Customers below Agent Native patches, request to go for the latest versions of the patches. Check out the latest patches in the following
https://launchpad.support.sap.com/#/softwarecenter/template/products/%20_APP=
00200682500000001943&_EVENT=DISPHIER&HEADER=Y&FUNCTIONBAR=N&EVENT=TREE&NE
=NAVIGATE&ENR=67838200100200019515&V=MAINT&TA=ACTUAL&PAGE=SEARCH/SAP%20D
ATA%20SERVICES%20OD%20AGENT
What are the Requirements:
| SYSTEM | NO OF DAYS REQUIRED |
|---|---|
| IBP Configuration Experts | 1 day to setup communication system |
| CPI-DS Configuration Expert | 3 to 5 days for configuration and testing of task Only technical changes, no function tests. |
| Basis Expert | 1 day for CPI-DS agent upgrade and reconfiguration. |
A survey form is sent and all the details must be filled i.e. name, email address, time zone, company, and you need to select the wave form to switch. After that SAP will send a confirmation mail regarding the switch.
As you can see the steps these are configurational setting customer need to maintain in each level.
1. The PSE certification, X-509 certification, add the server certification to PSE all these steps need to be maintained in DS agent.
Customer Configuration step -Add the Server Certificate to PSE: server certificate is required to encrypt information and provide identity assurance in your PSE file. Certificate might be included in file during agent installation & alternatively it is downloaded from browser connected to the SAP server.
2. Create communication user, create communication system, communication arrangements, etc need to be maintained in the IBP system.
3. Datastore configuration is need to be maintained in the CPI-DS system and also testing is done in the CPI-DS system.
Before doing the configuration steps SAP will activate the communication scenario. After activation mail customer can start the configuration.
PSE file is required to establish RFC connection and mandatory because of authentication.
Setting Up Data Integration in version 2108 or higher:
If the version of SAP IBP for Supply Chain is 2108 or higher, we can set up CPI-DS for data services as follows:
SAP data service guide
https://help.sap.com/viewer/product/SAP_CLOUD_PLATFORM_INTEGRATION_FOR_DATA_SERVICES
https://help.sap.com/viewer/product/SAP_CLOUD_PLATFORM_INTEGRATION_FOR_DATA_SERVICES
For more info on
authentication:https://help.sap.com/viewer/8111830769b64c99bf216ff459c2e29d/2202/en-US/b85ad29a9ff94edabe8f6ccbea271ea0.html
Setting Up a WebSocket RFC Connection:
https://help.sap.com/viewer/7d9858e1309e459093ed397c6fc40f12/1.0.11.43/en-US/bddefc0d4dcc4fb58c1c30378b9cc079.html
Customer Configuration steps for WebSocket RFC:
https://launchpad.support.sap.com/#/notes/3152253
How to connect to SAP HANA Cloud database in CI-DS:
https://launchpad.support.sap.com/#/notes/3157902
Shivam Dwivedi
SAP IBP Consultant, Baranwal Consultancy and Services (BCS), Pune, Maharashtra, India