Testing the Data Relationship Management Web Services Using Oracle Enterprise Manager

To test the Web Services using Oracle Enterprise Manager:

1. Ensure that the Oracle Data Relationship Management Web Service has an Oracle Web Services Manager security policy attached. A local or global policy can be attached.

   For example: oracle/wss_username_token_service_policy

   Note:

   You can have only one policy at a time attached to the Data Relationship Management Web Service. After changing the security policy, you may need to restart the WebLogic target server to which the Data Relationship Management Web Service is deployed.

2. In Enterprise Manager, select the domain to which the Data Relationship Management Web Service is deployed, then select Web Services/Test Web Service from the domain context menu or the WebLogic Domain menu in the right pane. .
3. Enter the WSDL for the Data Relationship Management Web Service in the WSDL text box.

   For example: http://localhost:28080/oracle-epm-drm-webservices/DrmService?wsdl

4. From Operation, select an operation; for example getSysPrefs.
5. On the Request tab, select WSS Username Token and enter a username and password with which to authenticate.

   Note:

   The user must exist in the security realm for the WebLogic domain and in Oracle Hyperion Shared Services.

6. Expand Input Arguments, from the drop-down list select XML View, and paste the following soap header argument (exactly as formatted) before the "<soap:Body xmlns:ns1="http://drm.webservices.epm.oracle">" tag.

   When copying the argument below, there cannot be a line break or space between tags/elements.

   <soap:Header>
   <AppParameters xmlns="http://drm.webservices.epm.oracle">
   <serverUrl xmlns="http://drm.webservices.epm.oracle">http://localhost:5240/Oracle/Drm/APIAdapter</serverUrl>
   <sessionParams xmlns="http://drm.webservices.epm.oracle">ProductVersion=11.2.0,CultureName=en-US,UICultureName=en-US, TimeZoneID=Eastern Standard Time</sessionParams>
   </AppParameters>
   </soap:Header>
   

   Considerations

   • An AppParameters element must occur in the header for the message to process correctly at the Data Relationship Management and Oracle Data Relationship Governance Web services.

   • When using Stateful Sessions in the Data Relationship Management and Data Relationship Governance Web services, the SessionMaintainParams element must occur before the AppParameters element in the SOAP header, otherwise, the Stateful Session ID will not be recognized and will not be processed.

   • Required parameters must be populated for the selected Data Relationship Management operations otherwise an error occurs.

7. In the soap header argument in step 6, modify the serverUrl to the appropriate host name and port for the Data Relationship Management API adapter.
8. Click Test Web Service.

   Note:

   If successful, the Response tab includes the response from the Web Service. If unsuccessful, an error message is displayed.

9. After testing is complete, re-attach the required production policy.