Sso, rfc, ws

hi,
i wanted to ask you, how to setup single sign on authentication between two abap SAP systems. My infrastructure looks like this: portal -(single sing on login)-> sapGUI abap system(NW 7.1) -(RFC)-> other abap system.
how should I setup the rfc calls (destinations, profile parameters, certificates ... ) to use single-sign on ticket created on portal?
and i also need to use the sso ticket to authenticate the user while calling web service. How should the setup look like (soamanager setup of the service, setup of the system ... ) ?
thanks, i would appreciated any help
(edit)
solution was is setup of the calling system, profile parameters login/create_sso_ticket and login/accept_sso_ticket
Edited by: Martin Gabris on Jun 2, 2009 3:57 PM
Edited by: Martin Gabris on Jun 2, 2009 4:00 PM

Hello,
You have to apply note 505296 - first issue and set snc/permit_insecure_start to 1
I hope this helps you.
Regards,
Blanca

Similar Messages

SSO between EP and ECC-- JCo RFC Provider- Error-- JCO_ERROR_SERVER_STARTUP

Hello Everyone
I am setting Up SSO between my EP 7.0 and my ECC 6.0 system. During the phase JCO RFC PRovider i am giving the following values:
The following was done;
1. start Visual Administrator -> Service : Choose JCo RFC Provider
2. Created JCo RFC provider:
Program ID: SAPJ2EE_Port
Gateway host: EPDEV ( host of my EP System)
Gateway service: sapgw00
Server Count 5
Application Server Host: ERP6 ( Host of my ECC System)
System Number: 00
Client: 000
Language: EN
User: SAPJSF
Password: ..
When i click on SET i am getting the error " ERROR When ADDING TO BUNDLE" Check LOG FOR DETAILS".
I checked the DEFAULTTRACE.TRC and get the following MEssage :
Date , Time , Message , Severity , Category , Location , Application , User
03/01/2011 , 3:33:30:101 , Error changing bundle SAPJ2EE_PORT , Error , /System/Server , com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.addBundle(BundleConfiguration conf) , , Administrator
03/01/2011 , 3:33:30:085 , com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Tue Mar 01 03:33:30 PST 2011.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 1 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=SAPJ2EE_PORT GWHOST=EPDEV GWSERV=sapgw00
ERROR       partner 'EPDEV:sapgw00' not reached
TIME        Tue Mar 01 03:33:30 2011
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -10
MODULE      nixxi.cpp
LINE        2823
DETAIL      NiPConnect2
SYSTEM CALL connect
ERRNO       10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER     1
I have configured my SLD as well. Any suggestions. Please Advise.

Hi Ahmed,
Please do check the validity of the certificate.
Please do cross check these steps again.
1.     Transaction u2013 STRUSTSSO2 (Trust Manager for Logon Ticket)
2.     Double Click Owner certificate. It gets reflected under the certificate tab.
3.                  Choose Format Binary
4.                  Choose File Path.
5.                  Enter the File Name
6.                 saved in local drive.
You can import into portal as x.509 certificate.
check this thread -
Certificate no longer has signature (use restriction)
Renew certificate via SAP MarketPlace, and install from tcode slicense. If you are working on a trial version, there is a SAP license request application form. Fill the form with the hardware key. you will get the new license via email. Install using slicense. Then try exporting the certificate.
Thanks,
Divya
Edited by: Divya V on Mar 10, 2011 11:25 AM

How to access BW RFC FM as web service from Enterprise portal using SSO

We have developed a custom remote function module in our BW system. We are accessing this function module as a webservice from a java class we have written. This java class access the BW webservice and formats the output. We created a webservice on top of this java class and deployed on the Enterprise Portal. SSO is setup between EP and BW systems. So when i make call to the BW RFC webservice, i would like to make use of SSO setup between EP and BW instead of hardcoding the user id and password while calling the webservice. Please advise on how to achive this.
Thanks for the help.
Thanks
Hari
Edited by: Hari Krishna Nalluri on Mar 19, 2008 12:41 PM

Hi,
Go to webserive perspective -> WebService Configuration -> Expand config node->Security-> Select HTTP Authentication and check Use SAP logon tickets option.
Ashutosh

RFC error while using SSO

Hi experts,
We tried to configure SSO using logon tickets on our EP 6.0 SP 16 system.
We created JCO RFC destinations in portal server giving the SAP target system's host name and service. Similarly, we created a new TCP/IP connection in the R/3 also with the same details.
We finished all the other procedures like importing and exporting portal certificates into R3 server.
Finally, when we tried to access the system from portal, the following error mesage is shown.
The following error text was processed in the system SER : An invalid type handle was passed to the RFC API.
The error occurred on the application server sapsbox_SER_10 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Function: AC_FLUSH_CALL_INTERNAL of program SAPLOLEA
Function: AC_FLUSH_CALL of program SAPLOLEA
Function: AC_SYSTEM_FLUSH of program SAPLOLEA
Form: HANDLE_FLUSH_PBO of program SAPFGUICNTL
Form: %_CTL_OUTPUT of program SAPMSSYD
Module: %_CTL_OUTPUT1 of program SAPMSSYD
Does any one know why this is happening?
Did we miss out anything??
Please help
Thanks alot
Shobin

An ABAP runtime error ("RABAX") has occured.
You should analyze the problem in the ABAP system running ABAP transaction ST22. Well, obviously you've managed to call an ABAP function module, so it's not an authentication issue ...

Problem in RFC as JCO changed from user/password to SSO

Hi all
Initially i was using CO with user/password properties but now it has been changed to SO.
In my webdynpro project there are 3 RFC Models being used.
Out of which 2 are working fine and giving the desired results but 1 RFC works fine on the R/3 side but from the webdynpro side it does not work just displays bapireturn - "Not successful".
As the properties of the JCO changes to USer/password , the RFC works fine giving the desired results
Plz let me know wht cld be the problem
Thanks and Regards

Vindhya,
With SSO, the details of the user who's logged in goto R/3 and thus determines if the user has authorizations to run this RFC. This user could be different from the user you were using previously without SSO.
Meaning, this time, with SSO, the user is you whereas the user for user/pwd is someone else and you dont have authorizations to run the RFC??
And another thing, even if you can successfully run that RFC logging into R/3, your userid may not have RFC authorizations (which is required to do a RFC call). IF thats the case, you need to talk to your security/basis guys.
Lemme know if that could be the case in your situation.
Rajit
Message was edited by:
Rajit Srinivas

Call RFC from EJB using SSO

Can anyone point me in the right direction on the best practice for calling an RFC using SSO from an EJB?
When using the local interface for the EJB, the only solution I see is to pass the authenticated IUser instance from the portal component to the EJB business method through the method signature.
I am guessing that there is a better way to get access to an authenticated user in the EJB container.

Thanks for the reply.
Actually I was able to solve the problem last night. To get SSO to work in my local EJBs I created an RFC destination in the destination service using the visual administrator. I then used the destination service at runtime to pull the system definition from the J2EE system definitions store instead of the portal system landscape definitions and my connection object was created as expected.
Here is the code to create the connection in my EJB business method:
//get the user
IUser user = UMFactory.getUserFactory().getUserByUniqueName(this.myContext.getCallerPrincipal().getName());
// get the destination service
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sapportals.portal.prt.registry.PortalRegistryFactory");
InitialContext context = new InitialContext(env);
IDestinationsService destinationsService =
(IDestinationsService) context.lookup(IDestinationsService.SERVICE_JNDI_NAME);
// define a destination filter to restrict to the RFC defined destinations
DestinationFilter destinationFilter1 =
new DestinationFilter(DestinationFilter.SOURCE_J2EE_DESTINATION_SERVICE, DestinationFilter.TYPE_SAP);
// get a user specific connection
IConnection connection = destinationsService.getConnection(user, "ECC", destinationFilter1);

JCo 3.0 - RFC call from EJB with SSO

Hello,
I am trying to call abap using JCo 3.0 from EJB (NW CE 1.0). I have configured destination on server with authentication method to use SAP Logon tickets. But when I call my EJB method that looks like this:
JCoDestination dest=JCoDestinationManager.getDestination("RFCCallTest");
JCoRepository repo=dest.getRepository();
JCoFunction f= repo.getFunction("ZMG_RET_NAME");
JCoParameterList in=f.getImportParameterList();
in.setValue(0, "param1");
f.execute(dest);
I get an exception when executing the first line of code:
Message: Exception occurred during lookup of RFC Destination RFCCallTest: No SAP logon ticket found
Category: /System/Security
Location:com.sap.security.core.server.destinations.provider.DestinationsProviderFrame.getDestinationProperties()
When I change the destination authentication method to Technical user it works well.
SSo between the servers works.
This scenarion also works when I use older JCo implementation (2.x)
BR
Viktor

Hi Bill,
I too faced the same problem for quite some time on SP9. I thought it was the adapter problem that persisted ...but it was not !!
After importing the RFC structure into XI, if the name of the imported RFC program is renamed/changed on R/3 side, then you will get the same error "lookup of binding via CPA-cache failed for AdapterType RFC, AdapterN."
So make sure that RFC program name on the R/3 side was not changed/renamed after you have imported the RFC structure into XI.
If the RFC program name had changed, make sure you reimport the RFC structure to avoid this problem.
Regards,
Sridhar

RFC Destination from CE is unwantedly using SSO

Hi,
Our developers are testing some services from Service Browser in CE 7.11 system. They are using the RFC Destination SAP_ECC which we have created from NWA --> Configuration Management --> Security --> Destinations.
In this RFC, we have given the details of the backend ECC system and also selected the user type as "Technical User" and provided a user/password. Pinging the destination from here works just fine.
But, when one of our services from Service Browser calls this destination SAP_ECC to access the backend system, then the call is not connecting to the backend using the technical user supplied in the destination, but is trying to use SSO. Thus the user being passed is not the technical user but the user of the developer who is calling the service. The error message says:
This system rejects all logons using SSO tickets
We do not have any intention of using SSO here.
Can someone suggest how to figure out why SSO is coming into picture and what can we do to elimincate this issue?
Thanks,
Shitij

set the sso parameters in the backend.

SAP RFC & Access Manager & SSO

Hello,
I need to design an SSO solution in an heterogenous architecture. I think about Sun Access Manager (AM) and its Policy Agents (PA). There are some SAP (ABAP based) systems, which are communicate using SAP Remote Function Call (RFC) protocol. There's no way how to turn it to different protocol.
One of the customer's requests is to authenticate SAP systems together using SSO.
And my question is: Is it possible to install PA in that environment and SSO the RFC protocol? If yes, how to pass through SAP systems original SSO token?
Thanks a lot.
Pat

Hello,
I need to design an SSO solution in an heterogenous architecture. I think about Sun Access Manager (AM) and its Policy Agents (PA). There are some SAP (ABAP based) systems, which are communicate using SAP Remote Function Call (RFC) protocol. There's no way how to turn it to different protocol.
One of the customer's requests is to authenticate SAP systems together using SSO.
And my question is: Is it possible to install PA in that environment and SSO the RFC protocol? If yes, how to pass through SAP systems original SSO token?
Thanks a lot.
Pat

Error in Web Srvice while SSO to RFC in the ECC system

Hello Folks,
I am creating an Web Service out of EJB to connect to ECC with an SSO(Logon ticket) based Modeldata JCo for which I get an error (Log provided below). When I create the Modeldata JCO with UserID/Pass it works fine.
Error Line : IWDJCOClientConnection client = WDSystemLandscape.getJCOClientConnection("WD_MODELDATA_TEST_SSO");
Error Message :
HTTP/1.1 200 OK
Connection: close
Server: SAP J2EE Engine/7.01
Content-Type: text/xml; charset=UTF-8
Date: Mon, 27 Feb 2012 04:41:07 GMT
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" ><SOAP-ENV:Body><rpl:ConnectResponse xmlns:rpl='urn:TestSSOProjectWSVi'><rpl:Response>
com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:152)
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:160)
     at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.getJCOClientConnection(WDSystemLandscape.java:41)
     at com.test.TestSSOProject.TestSSOProjectEJBBean.Connect(TestSSOProjectEJBBean.java:51)
     at com.test.TestSSOProject.TestSSOProjectEJBLocalLocalObjectImpl0_0.Connect(TestSSOProjectEJBLocalLocalObjectImpl0_0.java:103)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:331)
     at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
     at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
     at SoapServlet.doPost(SoapServlet.java:51)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for 'WD_MODELDATA_TEST_SSO'
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:649)
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:476)
     at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:242)
     at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:227)
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:129)
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150)
     ... 29 more
Caused by: com.sap.tc.webdynpro.services.sal.um.api.WDUMException: No client user defined for the current request (no regular Web Dynpro request as ITask is null.
     at com.sap.tc.webdynpro.serverimpl.core.um.AbstractClientUserFactory.getCurrentUser(AbstractClientUserFactory.java:48)
     at com.sap.tc.webdynpro.services.sal.um.api.WDClientUser.getCurrentUser(WDClientUser.java:67)
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:582)
     ... 34 more
   </rpl:Response></rpl:ConnectResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
Edited by: Prasanna Joshi on Feb 27, 2012 1:43 PM

Hi All,
Please suggest if anyone has faced similar error and any possible solution.
Any help would be highly appreciated.
Thanks
Vishno
> Hi All,
>
> We have 3.5 Web Reports running in Production. We
> are on NW2004s platform.
> The web reports have a WBS Element hierarchy in the
> 1st column.
> On expanding this hierarchy it throws an error
> message "<b>An error has occured
> during loading. Please look in upper frame for
> further information</b>". However
> there is no further explanation of the message.
> Seems its happening because of
> high data volume.
>
> Please suggest if I need to set any memory
> parameters. If so how.
> In SMICM I have increased the timeout for HTTP
> service to a high value (6000).
> There are similar threads posted previously but no
> solution.
> Any help will be highly appreciated.
>
> Thanks
> Vishno.

RFC and SSO Configuration

Hi guys,
Is it possible to configure RFC and OSS connection between to sap systems that they are not on the same domain?
Thanks

Hi Reza,
I believe it should work. Pls check this also;
http://help.sap.com/saphelp_nw04/helpdata/en/b8/9ba340fa432b54e10000000a1550b0/content.htm
Thanks and Regards,
Shyam.

Get SSO Ticket from RFC call

Hi,
i want to connect to a SAP Portal Webservice with a widget, after i used the SAP Widget Foundation to execute some RFC calls.
I wonder if there is a possiblitity to get the mysapsoo2 ticket from the SAP RFC response, which i can use than for connecting to the portal.
Thank you very much for your help!
Best regards
Jochen

Hi Jochen,
Are you wanting to make the service call directly from the Widget? Can you use the foundation for the service call and reuse the credentials from there?
Regards
John

The difference between SSO/NSF(GR) and NSR

Hello
I have question about the differnce between SSO/NSR(GR) and NSR.
In my understanding SSO/NSR is stateful switchover from Active to Backup
Mainly take over teh startup configuration and FIB TCAM table and so on.
But this protocol need to re-establish the routing table and topology database etc.
But if NSR functions when stateful switchover happens then it takes over routing table
and toplogy database etc. right?
If so, I think BGP peer down/up (flapping) , OSPF/EIGRP neighbor state change does not happen right?

ITS is used for accessing R/3 through browser....to implement SSO from Portal to access backend R/3 systems over ITS you need to follow certains step ...
1. Create RFC Destination in J2EE Engine RFC JCo Provider
2. Create RFC Destination in the R/3 Transaction: SM59
3. Maintain Portal Server Settings for the Portal
4. Maintain Single Sign-On in the R/3 System
5. Export R/3 Certificate to the Portal System
6. Import R/3 Certificate to the Portal
7. Create R/3 System in the Portal
8. Configure User Management in the Portal
9. Export Portal Certificate from Portal
10. Import Portal Certificate to the R/3 System
11. Set Up Repository Manager for R/3 in the Portal
12. Maintain User management as SAP Logon Ticket in the Portal
Hope I have answered your query in proper way.......
If you want step by step details pl s let me know
Swapnil

Issuer of sso ticket is not authorized SAP gui logon

Hello,
Would you please brief me how to enable SSO between two ABAP systems for NWBC.
We are not able to browse from source system to target system in NWBC, a logon prompt of second system is displayed for each browser session.
What I did.
Certified the server certificates with CA.
Imported the certificate CA into ABAP and browser as well.
Exchanged the certificates of both systems to each other strust store.
RFC connections between those two ABAP systems are working fine , without logon prompts.
HTTPS is working fine in browser without prompting for any certificate.
After examining the trace using fiddler debugger,
MYSAPSSO2 cookie is created and the same is being passed on to next system.
It seems /its/webgui is not able to decrypt/receive this mysapsso2 cookie.
SSL Server standard is certified by root CA in both abap systems and the root CA is added to strust store.
ACL list is maintained for each in both systems.
Issue has been resolved. ACL list is client dependent. So, entries are maintained in the desired client.
Now, no more logon prompt .

Hi Michael,
Thanks for you rhelp
But this is not the problem.
We found something strange in two environments.
In BW Development (this is OK), the certified in ACL is showing:
BWD 200 CN=BWD, OU=I0020274560, OU=SAP Web AS, O=SAP Trust Community, C=DE
In BW Quality (isn´t OK), the certified in ACL is showing:
BWQ 300 CN=BWQ (only this)
Can be this the problem? If yes, how can I solve?
Thanks
Carlos

Program not registered - RFC to J2EE (local machine)

I have a local install of WAS on my laptop using MSSQL 2000. I am trying to integrate local portal into a BI system.
1. I completed SLD configuration of local J2EE
2. As part of local SLD config I specified a BW7 system as data supplier
- entered BW7 host & gateway
- kept default settings for "configure data supplier targets" (i.e: sld/active=TRUE)
3. In Visual composer I successfully triggered SLD data transfer
4. In Visual Composer I specified a JCo RFC Provider to the BW7 system I want to access.
5. If I go to BW7 and goto tcode SMGW -> GOTO -> Logged on client, I see 2 pair of entries for JCo RFC provider
with the following settings
- system type: Registered Server (REGISTER_TP)
- state: connected
- LU name & Host Name = J2EE Host name w/ last 4 characters truncated. Only first 8 characters appear.
- TP Name: 2 entries = SLD_UC & 2 entries = SLD_NUC. So a total of 4 connections. My understanding is that TP Name is supposed to = Registered Server Program
6. In BW7, I have an RFC w/ Registered Server Program setting and program ID = JCo RFC Provider program ID
7. In BW7 RFC & JCo RFC the host & gateway settings are the same, they both refer to the BW7. THIS IS THE PART WHERE I AM UNSURE. I would have thought that the host & gateway settings of BW7 RFC would refer to Local J2EE engine. AND I DON'T KNOW WHAT THE GATEWAY IS FOR LOCAL J2EE.
8. In BW7 when I try to test the RFC, I get errors:
- Logon Connection Error
- program <...> not registered / CPIC-CALL: 'ThSAPOCMINIT' Tran
- ERROR: program <...> not registered
- DETAIL: TP <...> not registered
- COMPONENT: SAP-Gateway
- MODULE: gwr3cpic.c
- RETURN CODE: 679
- SUBRC: 0
- RELEASE: 700
- VERSION: 2
9. I completed step 1 & 2 of RSPOR_SETUP
- Step 1 <Create RFC Destination in J2EE engine> messages:
No Authorization to SMGW
Profile parameter login/create_sso2_ticket is not set to 2
Check of RFC destination <...> with RFC_READ_TCPIP_DESTINATION successful
- Step 2 <Create RFC destination to Portal> messages:
No Connection
Option Send SSO tickets not active (see documentation)
RFC CALL RFC_PING, destination <...> failed with sy-subrc =2
There a little something missing. Hope u gurus can help, lost a weekend over this.

Hello,
we get the same message (program ... not registered, COMPONENT: SAP-Gateway) in sm59, when checking the TCP/IP connection. We got it, after we changed the user name in the Visual Administrator.
Does anyone know with which tool and where the program can be registered. (The connection has no user name (connection by SAP ticket)).
Best regards,
Thomas

Sso, rfc, ws

Similar Messages

Maybe you are looking for