Configuring the Integration

Verify the Rulebase Web Service Adapter Options

The integration with OPA uses web service adapters to define the connection information to the OPA server and the specific mapping required between the product and the individual OPA rulebases. The product provides a Rulebase Web Service Adapter BO (F1-OpaWebSvc). Each OPA Rulebase requires an individual web service adapter that uses this business object.

Before creating any web service adapter records, verify that the Rulebase Web Service Adapter BO has been properly configured for the installation. Each installation must configure two BO options with specific server locations related to the integration. Review the BO options to ensure they are configured. If not, the installation team can provide the appropriate values:

• Oracle Web Determinations Server Location. This is the URL of the Oracle Web Determinations server. It should be in the format http://[server-name]:[portNumber]/determinations-server/soap. For example http://opa-server-name:1000/determinations-server/soap. This is the server location that is part of any WSDL URL used to create an appropriate web service adapter for a specific rulebase.
• Oracle Policy Automation Rulebase Location. This is the server directory that includes a copy of the deployment files of the OPA rulebases supplied with the product. This is needed by the business service that generates the mapping data areas when creating a web service adapter for a rulebase.

Once the configuration of the Rulebase Web Service Adapter BO is verified, your implementers may now create specific web service adapters for each specific rulebase used by your implementation.

Configuration Required for a Sample OPA Rulebase

For any sample OPA rulebase provided by the product, most components are supplied by the product, but final steps are required by each implementation. To illustrate the details, we'll use as an example the timeliness validation algorithm for creating an appeal.

• The product supplies the rulebase. In this scenario it is called Appeal_Validation. As part of the installation of the product, the deployment files are installed on the OPA server that the product will integrate with and also copied to the rulebase location server directory described above.
• The product supplies an appropriate algorithm type that invokes the call to OPA. The algorithm type is responsible for gathering the data required as input to the OPA rulebase and includes appropriate logic based on the outcome returned by the rulebase. For example, the call to OPA may return a decision report. The algorithm may be designed to store the decision report and link the decision report ID to the appropriate entity for viewing later. In this scenario the product supplies a BO Enter plug-in for the Appeal business object's Validated state. It is called C1-AP-CHKATL . The product supplies the algorithm type. However, the algorithm requires the Web Service Adapter name as input so the product does not supply the algorithm nor is it plugged into the appeal business object.

The following points explain the additional configuration steps required by an implementer to implement a sample rulebase.

1. Determine the WSDL URL for the rulebase. The WSDL URL is composed as follows [Oracle Web Determinations Server Location]/[rulebase name]/specific?wsdl. Using the URL example above and this rulebase the WSDL URL would be http://opa-server-name:1000/determinations-server/soap/Appeal_Validation/specific?wsdl.

   Tip:

   To verify that you have composed the WSDL URL correctly, paste the composed URL into an internet browser and verify that you can access the WSDL.

2. Define a web service adapter for the rulebase using the rulebase WSDL. Refer to Understanding Web Service Adapters for details about fully creating and generating the web service adapter.
3. Create an algorithm for the appropriate algorithm type provided by the product for this particular OPA integration. The algorithm requires the web service adapter name. Depending on the specific algorithm type, there may be additional parameters required.
4. Plug the algorithm into the appropriate plug-in spot as defined by the specific integration point.