Skip to Content

Introduction

The Duet client retrieves business data from Web Service calls to the Duet AddOn component. Depending on which Duet scenarios (like Leave Management, Time Management etc.) you are actually using, one or more of the listed Web Services will be called by the Duet client. These calls are transparent to the enduser, but the result of their execution is what makes the difference between seeing data and not seeing data in your Duet client. Performing those Web Service calls will tell you if your communication destinations work as expected (for example the connection between the Duet AddOn and the backend system(s)) as well as if the customizing for the respective Duet scenario is in place. In contrast to my other blog Checklist of activities for the Duet client installation which talks about general landscape tests, this blog is all about testing some of the Duet scenario Web Services using your browser in order to see whether you are able to retrieve business data. Here we go…

The Organization Management Web Service

The Organization Management Web Service is called in order to retrieve data for the Team Management scenario. Hence, in order to test it, you need to go to the AddOn server’s Web Service Navigator using your browser. Then choose the Web Service OrgManagementWS and go to Test in order to execute the Web Service method getTeamAndMembersDetails for the manager’s team information or getColleagueDetails for the information about the employee colleagues. When prompted for a username and password, enter your backend username and password.

image image image

The AddOn server will call the ERP system in order to retrieve the desired information. Note that the response of this Web Service call does not contain the actual contact objects; if the system finds that there are new contacts to be sent to your Duet client, it will do so by using the Item Handler service to send those new outlook items to your inbox. On the ERP side, a so called book keeping table is updated for your userid. In case of Team Management, this table is called /OSP/T_TEAMD5BKT. So if you execute this Web Service method and new entries are added to /OSP/T_TEAMD5BKT, something has been sent to your Duet client.

image

If this test fails (meaning the response contains a flag success=false or technicalError=true) you need to check the trace file of the AddOn server’s J2EE engine. If a Duet client is not getting a proper response from the OrgManagementWS, it will not display any team management related objects like colleagues as outlook contacts.

The Report Management Web Service

The Report Management Web Service is called in order to retrieve the so called report templates for the Report Management scenario. Hence, in order to test it, you need to go to the AddOn server’s Web Service Navigator using your browser. Then choose the Web Service ReportingFacadeWS and go to Test in order to execute the Web Service method getAdminReportCatalog for the employee’s report templates. When prompted for a username and password, enter your backend username and password.
image image image

The AddOn server will call the ERP system in order to retrieve the desired information. Note that the response of this Web Service call does not contain the actual report templates; if the system finds that there is new information (new report templates) to be sent to your Duet client, it will do so by using the Item Handler service to send new outlook items to your inbox asynchronously. On the ERP side, a so called book keeping table is updated for your userid. In case of Report Management, this table is called /OSP/T_REPMD5BKT. So if you execute this Web Service method and new entries are added to /OSP/T_REPMD5BKT, something has been sent to your Duet client.

image

If this test fails you need to check the trace file of the AddOn server’s J2EE engine. If a Duet client is not getting a proper response from the ReportingFacadeWS, it will not display or update any report template catalogues in your outlook inbox.

The Time Management Web Service

The Time Management Web Service is called in order to retrieve the project codes that you can track time on. Hence, in order to test it, you need to go to the AddOn server’s Web Service Navigator using your browser. Then choose the Web Service TimeManagementFacadeWS and go to Test in order to execute the Web Service method getTaskPaneF4HelpXML. When prompted for a username and password, enter your backend username and password.
image image

In contrast to the Web Services OrgManagementWS and ReportingFacadeWS, the TimeManagementFacadeWS response contains the actual data, in this case project codes to track time to.

image

If this test fails you need to check the trace file of the AddOn server’s J2EE engine. If a Duet client is not getting a proper response from the TimeManagementFacadeWS, it will not display any project codes in the time tracking action pane.

The Leave Management Web Service

The Leave Management Web Service is called in order to retrieve general leave management data. Hence, in order to test it, you need to go to the AddOn server’s Web Service Navigator using your browser. Then choose the Web Service LeaveManagementFacadeWS and go to Test in order to execute the Web Service method getLeaveInfo. When prompted for a username and password, enter your backend username and password. image image

You should get a result looking like this:

image

If this test fails you need to check the trace file of the AddOn server’s J2EE engine. If a Duet client is not getting a proper response from the LeaveManagementFacadeWS, it will not display the default approver name and things like this in the action pane.

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Guillaume GARCIA
    Thank you so much for these Duet Weblogs, they are really useful. Keep on writink some more ! 🙂

    I had a few questions:
    1) Is it possible/easy to add some new Web Services for the client to call?
    1bis) If yes, is it easy to implement the Duet client part (in .Net) ?

    2) As Web Services, are they reusable – let’s say – in a non-Duet scenario (ERP only, Java->SAP…)?

    Thanks again.

    Best regards,
    Guillaume

    (0) 
    1. Stefan Gustafsson Post author
      Hi,

      currently there is no official concept of changing the existing scenarios in any way. There will be something called Workflow pattern which allows customers to build their own Approve/Reject scenarios though.

      Concerning the reusability, I don’t think those facade WebServices are menat to be reused; you might wanna look at the ESA services for specifc tasks you wnat to execute.

      If you are interested in any specific topics for Duet BLOGS, just add them as comments here.

      Stefan

      (0) 

Leave a Reply