Displaying both ABAP webdynpro and Java Webdynpro tasks in the UWL

[Former Member]

Hi,

We have two an issue when trying to get the UWL to process two different types of workflow tasks : ABAP webdynpro and Java webdynpro.

Examples of these tasks are:

TS12300097 u2013 LeaveRequestApprover u2013 Java Webdynpro

TS17900100 - ASR_PROCESS_EXECUTE u2013 ABAP webdynpro

We have two backend systems configured

SAP_ECC_Financials u2013 This has the WAS host pointing to the java stack (xxx:50000)

SAP_ECC_Workflow u2013 This has the WAS host pointing to the ABAP stack (xxx.80xx)

In transaction SWFVISU all the tasks which use Java webdynpro have been configured to use the u2018Javau2019system (SAP_ECC_Financials) using the SYSTEM_ALIAS parameter

In the UWL configuration the system SAP_ECC_Workflow has been registered

In addition to this all u2018Javau2019 tasks have had an extra UWl config XML created to ensure that the SYSTEM_ALIAS is set to SAP_ECC_Financials

The system SAP_ECC_Workflow has been re-registered

The UWL cache has been cleared

However when we try to launch the java webdynpro tasks the system is trying to access the ABAP stack (It is still trying to access the Web AS location for the system SAP_ECC_Workflow even though the system alias was specified as SAP_ECC_Financials )

The ABAP webdynpro tasks (in this case a HCM process and form) are launched correctly

If we try the reverse (i.e register the Java system SAP_ECC_Financials and change the SYSTEM_ALIAS parameter for the ABAP webdynpro tasks to system SAP_ECC_Workflow) then the reverse happens. The java tasks can be launched and the ABAP tasks cannot.

Does anyone have a solution to this problem. Surely other people have implemented both ABAP and Java webdynpro workflows?

Any help much appreciated

Andrew

[Former Member]

Hey guys.

Before you try working with the tasks, make sure you correct the paths to the applications through SWFVISU.

Some of the standard tasks have the wrong path to the applications and that's the reason why they can't be found.

The real path to the apps starts with sap.com while some of the tasks refer to com.sap...

So make sure you correct that first.

Brgds, Caroline

[Former Member]

Hello Andrew,

We have a similar kind of issue here..

We set the visualization type of task TS17900100 as Java Webdynpro.

But we try executing the execute workitem link in the inbox, we are getting the error stating "requested deployable object 'sap.com/pa_asrformstep' and application 'asr_process_execute' are not deployed on the server" .

Please can you help or can you let us know the solution for your issue..

Thanks

Sushmitha

[Former Member]

Looks like your java task has a conflict in some other xml. LeaveApprove is part of standard MSS, there would be reference of your task in some MSS xml (standard delivered) which you might have to comment.

Basically remove the conflict of your task.

Vishal

[pramod_gopisetty1]

Hello,

As you said you set the properties is SWFVISU that is right.

The only thing you need to do is register the system and modify the UWL Config (.XML) file to point to the system alias you want to.

to do that navigate to

System Administration - System Configuration - UWL - and register a system and then download the XML file and modify the file accordingly (i.e. for the work item you mentioned make sure the application type is mentioned properly in the SWFVISU transaction and in the config file the system alias name is given properly) once done with the changes upload the configuration to Portal with High Priority, since this will overwrite the other config files.

Hope this helps.

Cheers-

Pramod

[Former Member]

Thanks a lot for all your replies..

The workitem type registration has been done already, but still it doesn't work..

But here is the actual problem...

There is a link 'Execute Workitem' in the inbox of the approver, or the second level manager...

In the leave application, when we click on this link it is taking to the portal as the task is the Webdynpro Java application task. Whereas, when using ABAP webdynpro application task, it is taking to R/3 - which means that the user cannot access this link without R/3 access. The users are given only portal access, they don't have access to backend R/3.

The requirement is that the link has to take the user to portal directly instead of R/3 - i.e it should ask only for the portal id and password.

Since it was working fine with leave application, I changed the task to Java webdynpro task, but I think the Java Webdynpro application is not deployed in the server.

Please can anybody suggest.

Best Regards,

Sushmitha