Error in UWL configuration for MSS in portal..

[former_member182205]

HI,

I want to configure UWL in portal so that I can see/approve leave in UWL in MSS. Please let me know how to configure the same.

When I am trying to configure the UWL in system admin> system configuration> Univerasal Worklist Administration, under that i clicked in new button to add my R/3 system, in that popup i mentioned my system alias name of R/3 system and connector as Webflow connector and remaining field i kept as empty and i clicked on save button after that when i click on Register button OR Register item type for all system than I am getting the following error, please let me know what the issue is ?

Error is:

Errors:

System SandBoxCLNT300: Wed Mar 16 09:18:38 IST 2011

(Connector) :com.sap.netweaver.bc.uwl.connect.ConnectorException:Wed Mar 16 09:18:38 IST 2011

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

SandBoxCLNT300 is the system alias of system I have created for R/3. in that system object I am using logon ticket.

Also when i try to test that system , SAP Web AS Connection AND ITS Connection connection are tested properly with green tick but the third parameter Test Connection with Connector is failing and the error is

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

Also the transaction iview i created using this system object is coming absolutely proper, than why Test Connection with Connector is failing , please let me know , might be UWL issue is related to this one..

Thanks

[siddharthrajora · Accepted solution]

Please first let us know if you have done the configuration as per

the Note 779075, Please do this and re register the work items and

let us know.

Make

Check the configuration of SAP_WebDynpro_XSS

Here is the help documentation:

http://help.sap.com/saphelp_nw70/helpdata/en/92

/a88931f2dd4631b9e8d530697d89c9/content.htm

in regards to this parameter.

IF the LeaveRequestApprover application is deployed on the SAP_Local

System, you needed the system alias of SAP_LocalSystem in the

Webdynpro Launch System value. With this setting when the user

manager clicks on the item, it will work fine.

the system SAP_Webdynrpo_XSS should have maintained the WAS properties

with the port of the portal. This is for normal working for

Leave request

"Mapping Logical Systems" in the following documentation:

http://help.sap.com/SAPHELP_NW04S/helpdata/EN/2a/7a754297fdd142e10000000

a1550b0/content.htm

and the "sap-wd-arfc-useSys" bullet point in the following

documentation:

http://help.sap.com/saphelp_sm32/helpdata/en/f4/651741f163f023e10000000a

155106/content.htm

See in bold where it mentions that "The prerequisite for this is that,

in addition to the default JCo connections, you created the new logical

system name with the Web Dynpro Content Administrator and configured it

for the required SAP system." Meaning that there needs to be a JCO

Connection for "SAP_R3_SelfServiceGenerics_MetaData" since these are

the default JCo connections. In this case I kindly ask that you create

the default metadata and model JCO connections for

SAP_R3_SelfServiceGenerics and see if that resolves the issue.

[former_member182205 · Accepted solution]

Hi Sidhharth,

Thanks for the reply, standard ESS leave app is working fine now, I added SAP_LocalSyatem in the webdynpro launch system while registering the system in UWL as my leave application is deployed in portal and not in ABAP.

But in standard leave ESS app, there is only 1 level approval, but we want to customize standard ess leave application for multiple levels of approvals, for that standard leave workflow in the backend R/3 system is copied and modified, but how to incorporte those changes in portal. we need some 3-4 level approval for that.

Do i have to make additional webdynpro java screens ?

please let me know

[siddharthrajora]

screens require no modication for multiple step approval, same screens will be resued, the only thing is required

is your WF confirguration and transition table in PTARQ, Please verify

you need reset the status of approved to sent etc

[former_member182205]

Hi Sidharth,

Do you mean, I just have to copy standard leave workflow in R/3 and modify it and make it 3 level approval in the workflow only.

and this new workflow number we have to enter in place of the standard leave workflow template number in R/3 so that this new workflow will be trigeered when user raises any leave from ess portal. and this will take care everything.

Don't we need any further webdynpro screen in portal to be created ? or just new workflow only is sufficient ?

[former_member182598]

For registering the system in UWL or for fetching the workitems, the connector test should succeed.

You can try by

1. Giving additional authorization to the user through which you are testing the connectors. I am assuming that you have a corresponding user in the backend as you have mentioned you are using logon ticket

2. Just to mention the mandatory parameters for connectors is

a.Application host ( I am assuming that you are using the dedicated application server template for creating system)

b. Logon method

c. System Type (Should be SAP_R3 if it's a R3 system)

d SAP Client

e. SAP System ID

f. SAP System number

g. Server port (This should be 32xx where xx is your system number)

Just verify these and revert if still facing issues.

Thanks

Prashant

Edited by: Kumar Prashant on Mar 16, 2011 5:55 AM

[former_member182205]

Hi Kumar,

I have created a user in portal aa_ep with administrator rights, also I created same user ID aa_ep in R/3 system with SAP_ALL rights.

Also in connector properties in system object in portal, I have mentioned the following parameters.

Application Host----

---

xyz.companyname.com:8000

Gateway Host----

---

xyz.companyname.com:8000

Gateway Service----

---

sapgw00

Remote Host Type----

---

3

Sap client----300

sap system ID................. ABC (ABC is the system ID of R/3 system)

system number----

---

00

system type--R/3

I tested it, connector test failing saying

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

Also, as suggested by you in connector property I added 1 more parameter value namely port to 3200 , as 00 is system number of R/3, and again I tested the system object, even than no luck, same error appears.

please let me know wats the issue..

[former_member182598]

HI,

take out the port from the application host

Application Host----

---

xyz.companyname.com

Clear the Gateway host property, If the application host and gateway host are same you don't need it.

Retest and let me know the result.

Thanks

Prashant