on 01-15-2016 3:51 PM
Hi there. We have a number of Web Applications that perform basic read-only RFC calls to SAP through the .NET Connector using a basic system user login created specifically for our web apps. Occassionally, however, we create CustomDestinations using SSO to perform various write RFC functions using the actual user's SAP login.
This works great. However, I am noticing in T-Code AL08 which shows all users logged on that the Custom Destinations persist. Should we dispose of these somehow in our .NET code? Is there a safe way of disposing of the Custom Destination after it is no longer needed?
For example, should I use the Shutdown() method after the Custom Destination is finished invoking the SSO RFC? Or RemoveDestination() possibly?
Thanks!
Actually, I may just use the IDLE_TIMEOUT and IDLE_CHECK_TIME to expire the connections. That seems to work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.