cancel
Showing results for 
Search instead for 
Did you mean: 

UWL error for ABAP Webdynpro Applications

Former Member
0 Kudos

Hi All,

We have developed few Abap webdynpro Applications for our ESS Implimentation which were having Approval Procedures.

and created Iviews for both the Request Application and Approaval Application

both are working fine while tested from Iview Preview.

we have created two systems in Enterprise portal

1.ECCCLNT120

WAS Host name: EPDEV:50000

2.ECCCLNT120_ABAP

WAS Host name: ECCDEV:8000

The first system (ECCCLNT120 ) is used for Standard Applications (Java Applications like Leave Approval, Travel Approval, Claims ..)

The second system (ECCCLNT120_ABAP) is used to create ABAP Webdynpro Application Iviews.

UWL configuration is done using the first system(ECCCLNT120 )

and all workflow Approval process for standard(java) applications are working fine.

Here the Issue is ABAP Webdynpro Approval Applications when tried to execute from the UWL is throwing 404 error.

Please suggest.

Warm Regards

Hari Sankar M

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi hari,

Check ur system allises of the backend object ,weather SAP_ITS_XSS and SAP_WebDynpro_XSS are there or not . If not add that alise .

SAP_WebDynpro_XSS this alise is for SAP EP system itself.

Thanks

Surekha.

Former Member
0 Kudos

hi,

Approval process for standard applications are workine because you registered ECCCLNT120 in UWL.

Try to register ECCCLNT120_ABAP in UWL and check for WebDynpro ABAP applications are working..

it may work..

Regards

sowmya

Former Member
0 Kudos

Hi,

You need 1 connector for each system/alias. You can create a new connector for the ECCCLNT120_ABAP system (in System Administration > System Configuration > UWL & Workflow > UWL Administration).

Regards,

Pierre

Former Member
0 Kudos

Hi Pierre,

Thanks for the prompt reply,

I have tried to create another connector for the next system

it's throwing two warning messages

1.System alias ECCCLNT120_ABAP for connector WebFlowConnector is connected through the existing system alias ECCCLNT120. The connection is added in an inactive state Custom XML configurations containing references to system alias ECCCLNT120_ABAP will be ignored

2.Could not verify if the backend of system ECCCLNT120_ABAP is configured for optimized delta pull

and its not giving an option for registering the new connector.

Warm Regards

Hari Sankar M

Former Member
0 Kudos

hi

Try to deactivate the first connector with system alias ECCCLNT120 and Register the uwl system with ECCCLNT120_ABAP.

you are getting error because you are trying to create another connector which is pointing to same system.

we can't register morethan one uwl system which are pointing to the same backend system.

Regards

sowmya

Former Member
0 Kudos

Hi,

This is weird, the first warning is the kind of error you have when you create 2 connectors for the same system (a system and a copy of this system for instance).

Are you sure the "Web AS Host Name" property is not the same for both systems?

Regards,

Pierre

Former Member
0 Kudos

Hi All,

We have deleted one system and configured the UWL with the existing system ECCCLNT120.

now the connection tests are working fine all UWL Registration error gone.

but still the problem persists for Abap webdynpro Applications its throwing Portal Administrator error while opening from the UWL of Approver

Warm Regards

Hari Sankar M

Edited by: Hari Sankar M on Jul 20, 2009 8:45 AM

Former Member
0 Kudos

Hi Hari

We are experiencing the same issue. Did you manage to get this resolved?

Thanks,

Jon