Table of Contents

Search

  1. Preface
  2. Introduction to Business Entity Services
  3. EJB Business Entity Service Calls
  4. REST Business Entity Service Calls
  5. REST APIs for Data Director
  6. SOAP Business Entity Service Calls
  7. Cross-reference Records and BVT Calculations Services
  8. Supporting Corporate Linkage Service
  9. External Calls to Cleanse, Analyze, and Transform Data
  10. Appendix A: Using REST APIs to Add Records
  11. Appendix B: Using REST APIs to Upload Files
  12. Appendix C: Using REST APIs to Manage Reports

Step 1. Understand and Deploy the Example Web Service

Step 1. Understand and Deploy the Example Web Service

The BESExternalCall example includes a WSDL file and the Java files with custom logic that the external calls use. Review the files in the example. To use the example, build and deploy the
.ear
file to the application server that runs the MDM Hub.
When you design external calls, first develop the custom logic in the framework of the external service. Then create the WSDL file that defines the external services, operations, methods, and data types that the service methods exchange. Ensure that the WSDL file uses the request and response types that are defined in the
bes-external-call.xsd
file.
  1. To understand the requirements for the request and response types, review the
    bes-external-call.xsd
    file.
  2. To understand the implementation of the request and response types for the example web service, review the
    custom-logic-service.wsdl
    file.
  3. To understand the custom logic the example web service uses, review the Java files in the Resource Kit.
  4. To build the example
    .ear
    file, use the
    build.xml
    file with an ANT build tool.
    For more information about building the EAR file, see the
    Multidomain MDM Resource Kit Guide
    .
  5. Deploy the
    bes-external-call.ear
    file to the application server that runs the MDM Hub.
    For more information about deploying the EAR file, see the
    Multidomain MDM Resource Kit Guide
    .

0 COMMENTS

We’d like to hear from you!