This could lead to an unexpected behaviour in a multi user context with multiple threads (race conditions. So there seems to be no other option than maintaining a seperate repository user (a user that needs no permission in SAP except for fetching repository information) and configure it in the application.Ĭhanging the logon information inside the JCODestination would be another option but this won't work for us, because changing the information of the JCoDestination requires to trigger the DestinationDataEventListener which notifys the JCoDestinationManager and the JCoDestinationManager would invalidate the existing JCoDestination and create a new one. Just guess what most of our users use for login? MYSAPSSO2 tickets. I know about the workaround to maintain a repository user, but this will only work for users with username + password or certificates but not for MYSAPSSO2 tickets. Why the hell does the JCoCustomDestination#getRepository() not pass the configured JCoCustomDestination.UserData for retrieving the JCoRepository to the underlying JCoDestination? If this behaviour is intended, why does JCoCustomDestination#getRepositoryUser() return my configured user although this logon is not used for fetching the JCoRepository? When I'm trying to check this via JCoCustomDestination#getRepositoryUser() my configured username is returned. But in fact they are (in JCoCustomDestination.UserData). The detailed error message tells me that neither logon information (username + password) nor a certificate is provided. I'm getting the error: Initialization of repository destination 'ABAP' failed. Now I'm getting some trouble when I try to execute JCoCustomDestination#getRepository() which fetches the JCoRepository (meta data) for the underlying JCoDestination. JCoCustomDestination#ping() works just fine, if the JCoCustomDestination.UserData object was filled correctly.
Due to the fact that the JCoDestination objects do not contain any logon data, I have to use JCoCustomDestination objects with different logon informations. The DestinationDataProvider works just fine and I'm able to get my JCoDestinations from the JCoDestinationManager. I implemented a custom DestinationDataProvider and registered it in the JCo Environment.
I've read the SAP JCo3 JavaDoc and development went just fine until I encountered an issue when I'm trying to get repository data from an JCoCustomDestination. I'm currently working on an SAP external project which aimes to get data from SAP via SAP JCo3.
0 kommentar(er)
