ABAP SDK for Azure integration with SLT about abap-sdk-for-azure HOT 11 CLOSED

Hi Krishna, Sorry for not closing this already. Please go ahead and close this request, appreciate your response on this. Puneet Jhari Data Architect t: 03 8623 8323 m: 04 158 555 49 e: [email protected]<mailto:[email protected]> From: Krishna Chandra Dash <[email protected]> Sent: Thursday, 30 April 2020 1:02 AM To: microsoft/ABAP-SDK-for-Azure <[email protected]> Cc: Puneet Jhari <[email protected]>; Mention <[email protected]> Subject: Re: [microsoft/ABAP-SDK-for-Azure] ABAP SDK for Azure integration with SLT (#48) Hi @puneetjhari<https://github.com/puneetjhari> @microsoft/abapsdk<https://github.com/orgs/microsoft/teams/abapsdk> - Can this issue be closed? As its related to one of the requirements related to SDK usage in SLT system. Thanks, Krishna — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#48 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGDEE5MT7XVNN7YNECBF5HLRPA6ORANCNFSM4JQJPRUQ>. *********************************************************************** This email is intended solely for the use of the addressee and may contain information that is confidential or privileged. If you receive this email in error please notify the sender and delete the email immediately. ***********************************************************************

Hi Leo, Sorry for not replying earlier as I was on personal leave since last week. Yes, we got it to work at the end for Azure Event Hub and Azure Storage using the SLT SDK BADI that has been provided by SAP. To be honest, we have not yet tried parallel loads using SLT SDK, however, the way we have treated the authentication is by using a Managed Identity and generating an access token from Azure AD. We then stored this access token in SLT cluster memory since it expires after every 24 hours, with each data transfer, we retrieve the access token if within 23 hours else generate a new one and store it again. This helps with the performance of the data transfer as well. Not sure if I have answered your query, please reach out if you need further details. Puneet Jhari Data Architect e: ***@***.******@***.***> From: leofrederiksen ***@***.***> Sent: Monday, 17 January 2022 11:47 PM To: microsoft/ABAP-SDK-for-Azure ***@***.***> Cc: Puneet Jhari ***@***.***>; Mention ***@***.***> Subject: [EXTERNAL] Re: [microsoft/ABAP-SDK-for-Azure] ABAP SDK for Azure integration with SLT (#48) Hi, just an update. The SLT SDK is working fine with the Azure Event Hub integration. You just have to get the payload information from SLT into the XSTRING format, and send the data. Use the sample code provided by Azure SDK. And use the generated Methods from SAP to get the replicated data into internal tables. Only issue we have is using parallel load for SLT, i.e. 2 different tables are loaded in parallel. Here we are getting "Error in Importing SAS Key" during replication. If we start the process again, the data is moved to Event Hub. We are still trying to figure out where in the code from Microsoft we are getting the issue. We have the same issue in 3 different installation. However, running with a single job, it is working well. — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/microsoft/ABAP-SDK-for-Azure/issues/48*issuecomment-1014482110__;Iw!!F8kG8IHFARY!LP8aUneClTX1k4V-YHVH5pUEyiJUUkIL_DP8RSodppkWc0yjMuchC9J3YCH1sA$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AGDEE5LGEGBMK6ZEPO3URGTUWQFSPANCNFSM4JQJPRUQ__;!!F8kG8IHFARY!LP8aUneClTX1k4V-YHVH5pUEyiJUUkIL_DP8RSodppkWc0yjMuchC9IwiMJAgQ$>. Triage notifications on the go with GitHub Mobile for iOS<https://urldefense.com/v3/__https:/apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!F8kG8IHFARY!LP8aUneClTX1k4V-YHVH5pUEyiJUUkIL_DP8RSodppkWc0yjMuchC9Id5QPcZw$> or Android<https://urldefense.com/v3/__https:/play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!F8kG8IHFARY!LP8aUneClTX1k4V-YHVH5pUEyiJUUkIL_DP8RSodppkWc0yjMuchC9I8plzpSw$>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>> *********************************************************************** This email is intended solely for the use of the addressee and may contain information that is confidential or privileged. If you receive this email in error please notify the sender and delete the email immediately. ***********************************************************************

Hi Puneet Thanks for your reply. I am a little curious about "stored this access token in SLT cluster memory" Do you mind sharing some details on how you did this? This might help us with the issue we are facing. And give some feed-back to Microsoft. Thanks. /Leo Leo Frederiksen Principal Expert, Big Data & Advanced Analytics LoB [cid:logo-aktuell-125px_6ba9b42e-08bc-42a1-ba38-61fcfafc7017.png] ***@***.*** Tel: +45 21411683 | NTT DATA Business Solutions A/S Erhvervsbyvej 11 – DK-8700 Horsens, Denmark www.nttdata-solutions.com<https://nttdata-solutions.com/dk/?utm_source=email-footer&utm_medium=email&utm_campaign=footer-tracking> [cid:linkedin_09158298-7604-45ad-8890-54343212f390.png]<https://www.linkedin.com/company/ndbs-nordics> [cid:youtube_a42e585a-df37-40b1-9deb-38c4678f051f.png] <https://www.youtube.com/channel/UCO7Ywj4gJzEYupf79H6_pvg> [cid:twitter_dce71918-7635-4f5b-b235-2dd004939547.png] <https://twitter.com/NDBS_Nordics> [cid:facebook_4949bd78-72be-4043-bb9a-53c935827a86.png] <https://www.facebook.com/NTTDATABusinessSolutionsNordics> [cid:instagram_460814f9-14a2-4d93-badf-c0ac7feffb3d.png] <https://www.instagram.com/ndbs_nordics/> This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, then you have received this email in error. If this is the case please advise the sender by replying promptly to this email and then permanently delete this email and any attachments without any use, dissemination, printing, copying or forwarding. Copyright NTT DATA Business Solutions. All rights reserved From: puneetjhari ***@***.***> Sent: 19. januar 2022 04:39 To: microsoft/ABAP-SDK-for-Azure ***@***.***> Cc: leofrederiksen ***@***.***>; Comment ***@***.***> Subject: Re: [microsoft/ABAP-SDK-for-Azure] ABAP SDK for Azure integration with SLT (#48) Hi Leo, Sorry for not replying earlier as I was on personal leave since last week. Yes, we got it to work at the end for Azure Event Hub and Azure Storage using the SLT SDK BADI that has been provided by SAP. To be honest, we have not yet tried parallel loads using SLT SDK, however, the way we have treated the authentication is by using a Managed Identity and generating an access token from Azure AD. We then stored this access token in SLT cluster memory since it expires after every 24 hours, with each data transfer, we retrieve the access token if within 23 hours else generate a new one and store it again. This helps with the performance of the data transfer as well. Not sure if I have answered your query, please reach out if you need further details. Puneet Jhari Data Architect e: ***@***.******@***.***<mailto:***@***.******@***.***>> From: leofrederiksen ***@***.***<mailto:***@***.***>> Sent: Monday, 17 January 2022 11:47 PM To: microsoft/ABAP-SDK-for-Azure ***@***.***<mailto:***@***.***>> Cc: Puneet Jhari ***@***.***<mailto:***@***.***>>; Mention ***@***.***<mailto:***@***.***>> Subject: [EXTERNAL] Re: [microsoft/ABAP-SDK-for-Azure] ABAP SDK for Azure integration with SLT (#48) Hi, just an update. The SLT SDK is working fine with the Azure Event Hub integration. You just have to get the payload information from SLT into the XSTRING format, and send the data. Use the sample code provided by Azure SDK. And use the generated Methods from SAP to get the replicated data into internal tables. Only issue we have is using parallel load for SLT, i.e. 2 different tables are loaded in parallel. Here we are getting "Error in Importing SAS Key" during replication. If we start the process again, the data is moved to Event Hub. We are still trying to figure out where in the code from Microsoft we are getting the issue. We have the same issue in 3 different installation. However, running with a single job, it is working well. — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/microsoft/ABAP-SDK-for-Azure/issues/48*issuecomment-1014482110__;Iw!!F8kG8IHFARY!LP8aUneClTX1k4V-YHVH5pUEyiJUUkIL_DP8RSodppkWc0yjMuchC9J3YCH1sA$%3E, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AGDEE5LGEGBMK6ZEPO3URGTUWQFSPANCNFSM4JQJPRUQ__;!!F8kG8IHFARY!LP8aUneClTX1k4V-YHVH5pUEyiJUUkIL_DP8RSodppkWc0yjMuchC9IwiMJAgQ$%3E. Triage notifications on the go with GitHub Mobile for iOS<https://urldefense.com/v3/__https:/apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!F8kG8IHFARY!LP8aUneClTX1k4V-YHVH5pUEyiJUUkIL_DP8RSodppkWc0yjMuchC9Id5QPcZw$%3E or Android<https://urldefense.com/v3/__https:/play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!F8kG8IHFARY!LP8aUneClTX1k4V-YHVH5pUEyiJUUkIL_DP8RSodppkWc0yjMuchC9I8plzpSw$%3E. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***<https://urldefense.com/v3/__https:/github.com/microsoft/ABAP-SDK-for-Azure/issues/48*issuecomment-1014482110__;Iw!!F8kG8IHFARY!LP8aUneClTX1k4V-YHVH5pUEyiJUUkIL_DP8RSodppkWc0yjMuchC9J3YCH1sA$%3E,%20or%20unsubscribe%3chttps:/urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AGDEE5LGEGBMK6ZEPO3URGTUWQFSPANCNFSM4JQJPRUQ__;!!F8kG8IHFARY!LP8aUneClTX1k4V-YHVH5pUEyiJUUkIL_DP8RSodppkWc0yjMuchC9IwiMJAgQ$%3E.%20%0bTriage%20notifications%20on%20the%20go%20with%20GitHub%20Mobile%20for%20iOS%3chttps:/urldefense.com/v3/__https:/apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!F8kG8IHFARY!LP8aUneClTX1k4V-YHVH5pUEyiJUUkIL_DP8RSodppkWc0yjMuchC9Id5QPcZw$%3E%20or%20Android%3chttps://urldefense.com/v3/__https:/play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!F8kG8IHFARY!LP8aUneClTX1k4V-YHVH5pUEyiJUUkIL_DP8RSodppkWc0yjMuchC9I8plzpSw$%3E.%20%0bYou%20are%20receiving%20this%20because%20you%20were%20mentioned.Message%20ID:%20***@***.******@***.***>>> *********************************************************************** This email is intended solely for the use of the addressee and may contain information that is confidential or privileged. If you receive this email in error please notify the sender and delete the email immediately. *********************************************************************** — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/microsoft/ABAP-SDK-for-Azure/issues/48*issuecomment-1016049970__;Iw!!B0kNdk3R__Efj5F6ERhD!9Zf6Yi-hMEfDLHmi3rQIFZe8Mqqwv5d4xtZpArsv67UqwTV37sWlllDYrcoZL3gmaR6LLI3ED1N8TrlVUVW7y2-XwsanldvQhw$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AXJXMZLZABJKWTSHEOA6DGLUWYW43ANCNFSM4JQJPRUQ__;!!B0kNdk3R__Efj5F6ERhD!9Zf6Yi-hMEfDLHmi3rQIFZe8Mqqwv5d4xtZpArsv67UqwTV37sWlllDYrcoZL3gmaR6LLI3ED1N8TrlVUVW7y2-XwsYUuBb4Tw$>. Triage notifications on the go with GitHub Mobile for iOS<https://urldefense.com/v3/__https:/apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!B0kNdk3R__Efj5F6ERhD!9Zf6Yi-hMEfDLHmi3rQIFZe8Mqqwv5d4xtZpArsv67UqwTV37sWlllDYrcoZL3gmaR6LLI3ED1N8TrlVUVW7y2-XwsZrII64rA$> or Android<https://urldefense.com/v3/__https:/play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!B0kNdk3R__Efj5F6ERhD!9Zf6Yi-hMEfDLHmi3rQIFZe8Mqqwv5d4xtZpArsv67UqwTV37sWlllDYrcoZL3gmaR6LLI3ED1N8TrlVUVW7y2-XwsYYTRgsRg$>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>