ABAP Webdynpro as a Client Proxy

[STALANKI]

Depicts the steps required to configure an ABAP Webdynpro as a client proxy. Question me, Why an integration experts need to use ABAP Webdynpro for a client proxy? Have the answer!

I have been asked by the customer to provide an application that can pull up the employee information from SAP and 5 legacy systems based on search term that will be fed by her. The user is from MI team and she does not want to login to SAP nor see the ABAP SE38 Screens. Immediately solution that I bestowed her is to use ABAP Webdynpro that allows her to search the information by shielding her logging onto various systems. Objective is to make the customers happy, Isn’t it?

Do you agree with me that learning ABAP Webdynpro and using it as a client proxy will be beneficial to you as an integration expert? If you disagree then please abort then the blog might not be useful for you.

I assume that you know how to create ABAP Webdynpro components, views, context structures and bind the UI elements to the context structure of the view.If you don’t know then it is not a danger. Read this series Unleashing ABAP Webdynpro for generating XSD in SAP XI-Episode 3.

I am going to take the same interface that is provided by ravi in the blog ABAP Proxies in XI(Client Proxy) for simplicity with the only difference being the files is simulated only when user enters the employee number, employee name and department name and press simulate file.I donot discuss the configuration and mapping details here as they remain exactly same. You need to just plug an ABAP Webdynpro in place of a proxy.
Steps Required :
1 .Create a Webdynpro Component ZABAPWDClientProxy.
2. Create ContextStruture as shown below.

3. Create View InitialView and create 7 UI elements Label for Employee Number, Label for Employee Name, Label for Department Name, InputTextbox for Employee Number, InputTextbox for Employee Name, and InputTextbox for Department Name and Simulate file button that triggers the proxy. After creating the UI elements, bind them to the context structures and associate event SIMULATEFILE to the button.

4. Now paste the source code provided below in the method SIMULATEFILE by selecting action tab.
data prxy type ref to zblogco_proxy_interface_ob.create object prxy.data it type  zblogemp_profile_msg1.wd_context->get_attribute( exporting name  = 'CEMPNO'  importing  value = it-emp_profile_msg-empno ).wd_context->get_attribute( exporting name  = 'CENAME'  importing  value = it-emp_profile_msg-emp_name ).wd_context->get_attribute( exporting name  = 'CDEPTNAME'  importing  value = it-emp_profile_msg-department_name ).try. call method prxy->execute_asynchronous      exporting        output = it.   .  catch cx_ai_system_fault .    data fault type ref to cx_ai_system_fault .    create object fault.    write <li-emoji id="lia_confused-face" title=":confused_face:"></li-emoji> fault->errortext.endtry.
5. Create Webdynpro application and feed in the sample data and you can see the file in the folder you configured if your configuration is correct.