Log file ljs_trace.log does no longer exist but is still mentioned in the documentation

[mbeykirch]

Issue description

It seems that the former log file ljs_trace.log has been renamed to ssc_core.trc. However, it is still mentioned in the documentation.

It would also have been nice to mention such changes in the release information - that is why release information exists.

Feedback Type (Optional)

clarity

Page Title on SAP Help Portal (prefilled)

Troubleshooting

Page URL on SAP Help Portal (prefilled)

https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/cloud-connector-troubleshooting?q=ljs_trace.log

[sap-doc-bot]

Thank you for your valuable feedback contribution, @mbeykirch! So that we can recognize your contribution in the SAP Community, please check your SAP Community user ID (this is a number) in your personal settings page and share it with us in a reply to this comment. Make sure you just include the number in the reply.

Your user ID is displayed as follows:

Change display name for User ID N

where N is your user ID. For example, 53 is the user ID of the user 'qmacro'.

Please note that we are currently refactoring our profile and badge system on the SAP Community, and will start assigning badges again when that's complete.

[Frank1Mueller]

Dear Martin,

thanks a lot for pointing this out. We updated the content accordingly.

Best regards
Frank

[mbeykirch]

1456923 From: sap-doc-bot[bot] ***@***.***> Sent: Tuesday, May 14, 2024 5:31 PM To: SAP-docs/btp-connectivity ***@***.***> Cc: Beykirch, Martin ***@***.***>; Mention ***@***.***> Subject: Re: [SAP-docs/btp-connectivity] Log file ljs_trace.log does no longer exist but is still mentioned in the documentation (Issue #5) Thank you for your valuable feedback contribution, @mbeykirch <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmbeykirch&data=05%7C02%7Cmartin.beykirch%40sap.com%7Cd905e81a60b34262ed4c08dc742aca84%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C638512974340228441%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=Jk6Clqxrdfi44NwEexVxcvrInpjsViHsLc1Oy5GJguc%3D&reserved=0> ! So that we can recognize your contribution in the SAP Community <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSAP-docs%2Fcontribution-guidelines%2Fblob%2Fmain%2Fdocs%2Frecognition.md&data=05%7C02%7Cmartin.beykirch%40sap.com%7Cd905e81a60b34262ed4c08dc742aca84%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C638512974340241646%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=JrPSZo37SS6%2FiHPM1uHGzaB6V1RynCr5BExlEzqMoLE%3D&reserved=0> , please check your SAP Community user ID (this is a number) in your personal settings page <https://community.sap.com/t5/user/myprofilepage/tab/personal-profile> and share it with us in a reply to this comment. Make sure you just include the number in the reply. Your user ID is displayed as follows: Change display name for User ID N where N is your user ID. For example, 53 is the user ID of the user 'qmacro' <https://community.sap.com/t5/user/viewprofilepage/user-id/53> . Please note that we are currently refactoring our profile and badge system on the SAP Community, and will start assigning badges again when that's complete. — Reply to this email directly, view it on GitHub <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSAP-docs%2Fbtp-connectivity%2Fissues%2F5%23issuecomment-2110536686&data=05%7C02%7Cmartin.beykirch%40sap.com%7Cd905e81a60b34262ed4c08dc742aca84%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C638512974340250859%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=DL1CFI8NeCtWdOqhqSqTWkFghSJp1aqP7ulEw7e3NIc%3D&reserved=0> , or unsubscribe. You are receiving this because you were mentioned. <https://github.com/notifications/beacon/BGWEX4SCVYH7EDN4CHHQHW3ZCIUZNA5CNFSM6AAAAABHWINGCCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT5ZQ564.gif> Message ID: ***@***.*** ***@***.***> >