Problem while creating system in Portal
Iam trying to create technical system in the Portal to connect to SAP R/3 system. when i try to test the system, iam always getting the following error:
Connection failed. Make sure user mapping is set correctly and all connection properties are correct.
I tried to do the user mapping from both "Personalize" link as well as from the "User Management", but no use.
What could be the possible solution for this error?
Christian Günther replied
it would probably be very helpful for you and also for us, if you could provide some more details about your environment:
1. Is this a productional environment consisting of multiple systems or are you in a development environment, where everything is on noe host?
2. What version is your portal and the backend, is this really R/3 backend as in 4.6c?
2. Where is your SLD setup - on your central Solution Manager, standalone or not at all?
- you need the hostname and port of the SLD - ask your SAP Basis Administrators
3. please find out about connection details about your R/3 backend system - hostname, ports etc.
In case you do not have an SLD (although I'd find this rather strange) you could also create the JCo connection like this:
1. logon to your portal as Administrator
2. Navigate to System Administration -> System Configuration
3. In the portal content I suggest you create yourself a new folder in which you save your technical systems
4. Right click on your new folder and create a new system from template
5. Choose SAP System with load balancing (in case you want to use a message server)
or direct SAP system - I would use SAP system via message server
5. provide the following information:
a) The Systemname - this can be any name you want e.g. D1H_HR_Development
b) The System-ID - I usually choose the name in lower case
c) System-ID prefix - this is a prefix to identify your system in the PCD. I usually only have my company name here
6. Choose next and then open the object for editing
7. In the dropdown menu Property Category choose Connector:
Logical System Name: enter <SAP SID>CLNT<CLIENT>
Message Server: the hostname of your R/3 system where the message server (provided by central instance) runs on
Remote Host Type: 3
SAP Client: (whatever client you use)
SAP System ID: the SID of your R3 system
Server Port: Your Message server port
In case you have an 4.7 or later backend system, you would also want to enter Web AS configuration settings:
8. Choose the Web AS properties in the drop-down box
WebAS Description: same as in Logical System Name <SAP SID>CLNT<CLIENT>
WebAS Hostname: The abapa webas with FQDN and ABAP http-port: <server>:<port>
Web AS Path: /sap/bc/webdynpro/sap
Web AS Protocol: http or https that depends on your security implications
User Management properties
Authentication Ticket Type: SAP Logon Ticket
Logon Method: SAPLOGONTICKET
User Mapping Fields: I really hope for you that your users are named the same in portal and backend - in this case, you can leave this blank
User Mapping Type: Admin
If you need to have access to the ITS (internal for new systems) choose this property from the drop down list
ITS-Description: something speaking
ITS-Hostname: like above (if its internal) but also full qualified and WITH portnumber
9. Now after these settings make sure your system has at least a Default Alias.
Either enter one (you can find the option to enter System Aliases in the context menue of the system object itself) or add a system alias as requested by specific business content.
For example, depending on your specific scenario, ESS/MSS on HCM could need these Aliases:
I hope this helped a bit,