Generate Web service for a BRF Plus application
Generating web service for a BRF+ Function.
We can generate web service for a BRF+ function in local $tmp package or Development Package with workbench and customization request.
The generation tool for web services and RFC-enabled function modules helps an application developer as well as a third-party user to process the rules defined in BRFplus. The tool helps to create web services and function modules in a highly automated fashion with minimal interaction.
Generating web service with Local $tmp Package:
Choose your function and click on Generate web service. Here we are generating web service for CATEGORY function in Z_AGE_CALCULATION application. Click on Generate web service.
Popup will display and enter the required details as shown in the below screen shot. Click on Generate button.
ZAGE_CALCUL web service successfully generated.
Go to SE80
Open local objects ($TMP)
You can find the generated web services under Enterprise Services folder.
Choose your web service & Process. So web-service has been created and active. To test the service click on execute button.
The following screen will be appeared. Enter the AGE.
Check the service is activated at the SICF level or not. Enter the service and execute.
Make sure that the service is active service
Provide search pattern(web service name) & click on go.
Choose the service & click on apply selection
Click on configuration tab and create Endpoint.
Specify the setting as specified in the following screen and click on save.
Go to overview
Click on Open WSDL document for selected binding or service
Click on Open Web Service navigator for selected binding
Click on Display selected Binding’s or Service’s WSDL URL
The following URL will be generated
Now web service has been generated successfully. So you can access this service from any plat form.
Testing web service using SOAP UI:
Open SOAP UI tool and specify the WSDL URL in the initial WSDL field and choose ok. If you want different project name you can enter.
Click on request1 provide credentials(log on details)
Thanks for reading…..