Develop a Web Service Connector
A connector framework web service connector can be implemented in Java, .NET, PHP, or any language that can create a SOAP web service.
A system integrator need not implement all the web service actions described by the connector framework. The following table shows valid combinations of actions for a web service connector that conforms to the Intelligent Advisor connector framework.
| Service | Actions | Pre-requisites | Minimum connector framework version | When to implement | Further information |
|---|---|---|---|---|---|
| Metadata | CheckAlive | 12.0 | Always | Check Whether a Web Service Connector Is Online | |
| Metadata | GetMetadata | CheckAlive | 12.0 | If you need to:
|
Understand How to Expose Application Metadata |
| Data | Load, Save | CheckAlive, GetMetadata | 12.0 | To Load/Save application data from web interviews | Understand How to Load and Save Application Data |
| Data | SetCheckpoint, GetCheckpoint | CheckAlive | 12.2.2 | To enable automatic save and resume of in-progress web interviews | Develop a Connection to Save, Store and Retrieve Checkpoint Data |
| Data | ExecuteQuery | CheckAlive | 12.2.9 | To load data during an interview that matches specified query parameters | Load Application Data During an Interview |
Tip: As a debugging aid during development of a web service connector, you can view the current metadata response by temporarily switching a connector framework web service connection to a static metadata connection. By modifying the static metadata, you can experiment with the metadata response that will provide the desired mapping experience in Oracle Policy Modeling. This can also be useful if you want to provide policy authors with mapping options that are closer to the final ones you will provide, while you are still developing a web service connector.
When developing a web service connector be sure to take into consideration the following:
- Security and user authentication, to ensure only permitted data is returned or updated
- Localization (region, language, timezone) of the metadata into required languages
- User-based license compliance, if it will be used for interviews licensed on a per user basis