Publishing the BMC Remedy AR System functionality as a web service
Web services provide a simple, platform-agnostic method for application integration. By using standard messaging protocols and service definitions to support computer-to-computer interaction over a network, web services allow application integration regardless of the hardware or software platforms and independent of the programming languages in which the applications are written.
You publish a web service to make BMC Remedy AR System functionality available over the web by creating a web service object, associated forms, and optional workflow. BMC Remedy AR System developers can use a web service to make BMC Remedy AR System operations, such as submit, modify, and query, available to other applications. Web services that are published in BMC Remedy AR System can be very basic, such as creating a record in the BMC Remedy AR System server database, or more complex, such as processing a purchase order that spans multiple BMC Remedy AR System forms.
You consume a private or public web service to obtain external information for use in a BMC Remedy AR System application by creating a form and an associated filter that uses a Set Fields action.
The following sections provide information about using web services with BMC Remedy AR System. They describe how to publish the BMC Remedy AR System functionality as a web service and how to invoke external web services to exchange data between BMC Remedy AR System and web service applications.
- AR System and web services introduction
- Web service standards
- Predefined BMC Remedy AR System web services
- Forms and field mappings for web services
- Basic and custom web services
- Creating web service clients
- Setting up the environment for web services
- Publishing a web service
- Registering a web service
- Consuming a web service
- Mapping web service data
- Using join forms in web services
- Web service operation types
- Web service scenarios
- XML editing introduction
- Supported schema constructs and web service limitations
- SOAP headers and authentication