Standard UWL configuration error?

[Former Member]

I have trouble in configuring standard UWL system registration.

When I register the UWL to one of the existing R/3 SAP_ECC_HumanResources system alias I get below error

Error in loading configuration for system SAP_ECC_HumanResources:com.sap.netweaver.bc.uwl.UWLException:

(Connector) :com.sap.netweaver.bc.uwl.connect.ConnectorException:

: No User mapping set up for user USER.R3_DATASOURCE.<USERNAME> system :SAP_ECC_HumanResources

User :<USER.R3_DATASOURCE.VUMMITIS> getting data from system : <SAP_ECC_HumanResources >: JCO error in reading configuration:com.sap.netweaver.bc.uwl.connect.ConnectorException:

: No User mapping set up for user USER.R3_DATASOURCE.<USERNAME> system :SAP_ECC_HumanResources

NOTE: I have replace actual username with <USERNAME> in the above error message.

The Portal user and backend user have same id and using SAPLoginTicket authentication.

Is the above error mean I have no authorisation to call WF RFC functions or some basic authentication issue.

Thanks

Praveen

[Former Member · Accepted solution]

Hi,

The error clearly states that User Mapping is missing.

Can you please let me know what did u mention for the property log method of your system SAP_ECC_HumanResources.

If you have mentioned Log On Ticket,you have to configure your ECC to accept log on tickets.

If you have mentioned User Mapping,then you have to provide user/pwd using personalize.

I feel this is the only thing which got missed

[Former Member · Accepted solution]

Hi Santhosh,

The system authentication ticket type is "SAP Logon Ticket" and System type is "SAP_R3" and Logon Method is "UIDPW".

Our user are configured in ABAP system and we use same UID for Portal and backend, I have access to RFC also. There is no need for user mapping but still I don't know why it's erroring for user mapping.

Please let me know if you need any more information to understand more.

Thanks

Praveen

I have even tried with SAP_ALL access in the backend but still no luck.

Edited by: Praveen11 on Jul 2, 2009 6:23 AM

[Former Member · Accepted solution]

Hi Praveen,

As you say Logon Method is "UIDPW",then you should definitely need User Mapping.

Try to provide your R3 user in user mapping and register the sytem again,you will not face this error

Or change Logon Method as "SAPLOGONTICKET" to make sure you log on to back end using log on tikcets.

[Former Member · Accepted solution]

Hi Santhosh,

I tried that before but I got different error, anyway here is the error log. This time the logon method is SAPLOGONTICKET

System SAP_R3_Workflow:

(Connector) :com.sap.netweaver.bc.uwl.connect.ConnectorException:

(Connector) :com.sap.portal.connectivity.destinations.PortalDestinationsServiceException:User is missing credentials for connecting to alias SAP_R3_Workflow. Contact your system administrator.

Thanks

Praveen

Edited by: Praveen11 on Jul 2, 2009 6:37 AM

You might see a different system alias in this error message because I created a completely new system object just for workflows to connect to R3.

[Former Member · Accepted solution]

Praveen,

did the system pass the connection tests?

go to system administration-system configuration-select the system and select connection tests from the dropdown.

go to system administration-support-sap application-sap transaction-select the system and give some tcode and see whether you are able to connect to backend without username/password

Thanks

Bala Duvvuri

[Former Member · Accepted solution]

Hi Bala,

When I ran connection test before it worked, but now it's not working and following message appears

SAP Web AS Connection

Results (I'm only copy pasting failed message for some reason the message is getting scrambled without new line)

The Web AS ping service http://<hostname>/sap/bc/ping was not pinged successfully. If the ping service is not activated on the Web AS, you can try to call the ping service manually.

An HTTP/S connection to http://<hostname>/sap was not obtained successfully; this might be due to a closed port on the Firewall.

Test Connection with Connector

Test Details:

The test consists of the following steps:

1. Retrieve the default alias of the system

2. Check the connection to the backend application using the connector defined in this system object

Results

Retrieval of default alias successful

Connection failed. Make sure that Single Sign-On is configured correctly

When I tried running transaction from support, I get

[EXCEPTION]

com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Application URL ':///sap(ZT1BazFqTzQxTnZSZUNBbVExQ0ZOeU5RLS1tdVRpeWl1ZUZKMzhHYjhINXZFSkt3LS0=)/bc/gui/sap/its/webgui' is not valid! Please check the protocol and host entries for system 'SAP_R3_Workflow'.

Edited by: Praveen11 on Jul 2, 2009 6:49 AM

Edited by: Praveen11 on Jul 2, 2009 6:50 AM

Edited by: Praveen11 on Jul 2, 2009 6:52 AM

[Former Member · Accepted solution]

Hi ,

What is the ITS path you provided,try providing the following value for ITS path

/sap/bc/gui/sap/its/webgui

Also provide ITS host name properly.

Also From Support while testing,can you try using SAP GUI for windows as GUI type instead of SAP GUI for html.

And let us know the problem you face?

[Former Member · Accepted solution]

I think Log on ticket configurations are not done properly,I would suggest you try providing User Mapping and check the issues first

[Former Member · Accepted solution]

ITS had nothing, I configured ITS as you said and correct WEBAs properties and tested connection, everything tested successfully.

Then I went into support and tried to kick off SU01 transaction with SAP GUI for Windows instead of SAP gui for HTML, I got below message

hostname "<myhostname>" unknown

check your application server name

I also saw a splash screen of SAP GUI for windows but didn't open at all.

Thanks

Praveen

[Former Member · Accepted solution]

I don't what happened transaction are working now for SAP Gui for HTML but it's prompting for username and password before showing transaction screen. So this means SAPLogon ticket is not setup correctly?

Thanks

Praveen

[Former Member · Accepted solution]

Praveen,

Now that you have entered ITS parameters SAP GUI for HTML is working properly.

I wanted to chck regarding SAP GUI for windows and asked u to check.

thats fine. If SAP GUI for Html works then you go head and register UWL system now.

As it is asking user name and pwd, Log on tickets is not configured properly.

For now,you can make Logon Method as UID PW and provide mappping details and test from support Thsi shud work.

Once you confirm this go ahead register for UWL system.. Hope it is clear

[Former Member · Accepted solution]

Santhosh,

I'll make the logon method as UIDPW for the system object that I created. What about Authentication ticket type, currently it's "SAP Logon ticket", can I leave it as is?

Can you please point me where exactly I do this user mapping? Just to be sure.

Thanks

Praveen

[Former Member · Accepted solution]

I did user mapping for system that I created (i.e. SAP_R3_Workflow) but still getting same error

User is missing credentials for connecting to alias SAP_R3_Workflow

What have I missed here?

[Former Member · Accepted solution]

Yes.you can leave that as is for now...

Mention User Mapping Type property to admin,user

This means user mapping can be done by the logged in User from Personalize link in mast header or administrator can be do the same from User Administration.

You can follow any of the two ways..

[Former Member · Accepted solution]

Can you try making Authentication ticket type to be as default value instead of log on ticket. And see if u get the same error

[Former Member · Accepted solution]

Try giving Full permissions to your system object for the users accessing the system.

Make sure end user is also ticked for Every one group

Check this link

/thread/1068992 [original link is broken]

[Former Member · Accepted solution]

OK, I have user admin access so I did user mapping to the system.

I make auth type default which is nothing, still same error.

There must be something simple that I'm missing here.

Praveen

[Former Member · Accepted solution]

yes...As i said earlier try providing full permissions for your system object

[Former Member · Accepted solution]

Gave full control to the system object permission but no luck again.

[Former Member · Accepted solution]

That should be defintely is due to permissions..

Can you post the permissions u gave for the system? Try giving permissions to every one group and check

[Former Member · Accepted solution]

Hi Santhosh,

I found that there is something wrong with SAPLogonTicket method for system object. So we have to fix the SAPLogonTicket first and then come to UWL. So I'm closing this thread for now and shall raise another thread if I still have UWL issue after SAPLogonTicket issue is resolved.

One of Bala's post helped me do testing on running transactions from SAP Support, which always pops up for UID/PWD. Let me resolve that SAPLogonTicket issue first between Portal and R3.

Thanks for eveyrones help.

Praveen.

Edited by: Praveen11 on Jul 3, 2009 5:58 AM