In this blog, I will be describing about how to generate and test your SAP Netweaver BRM Rules web services, which are generated using the Web Service Generation Tool.
In general, you can create the business rules using either XML schema or Java class in SAP Netweaver BRMS, the business rules created with XML schema can be exposed as web service and consumed from any client application. In this blog, I will discuss about generating the web service for credit card eligibility business rule using the Web Service Generation Tool and testing the same using the WS Navigator of CE 7.1.1 system.
The WS Navigator UI in CE 7.1.1 has enhanced with lots of new features for performing the service test and creating the test scenarios.
As a first step, I will be generating the web service (.EAR file) for my credit card rules using the Web Service Generation Tool. Refer the ‘ReadMeFirst.pdf’ from the Web Service Generation Tool download (ZIP file) to know more about the usage of the tool.
Here is a sample credit card type decision table defined for the Ruleset ‘Creditcard_Approval_Rules’ in the Rule composer of SAP NetWeaver Developer Studio 7.1 EhP1.
After the successful deployment of the web service (.EAR file) into your CE 7.1.1 system. Login to your NWA and navigate to SOA Management -> Application and Scenario Communication->Single Service Administration.
Find for the Service ‘CreditCardApprovalRules’ as shown below:
Navigate to the 'WSDL' tab in the details screen:
Click on the ‘Test’ to launch the WS Navigator for testing the Credit Card Rule Service
Click on ‘Next’ to find the operations available for the service
Click on ‘Next’ to enter the input parameters for the operation
Click on ‘Next’ to execute the service. Upon the execution, system will invoke the rule processor to evaluate the conditions and return back the result from the rule set (Eligibility)
In my next blog (Consuming SAP Netweaver BRM Rules Web Service in ABAP - Part 2), I will explain about how to consume these credit card rule web service from the ABAP client.
4 Comments
