Making other changes to APIs and web services

Your application can call or invoke standard APIs or custom APIs. This section includes information about the following types of changes:
  • Invoke standard APIs for displaying data in the UI and for saving changes made in the UI to the database.
  • Invoke customized APIs for executing your custom logic in the extended service definitions and pipeline configurations.
  • APIs use input and output XML to store and retrieve data from the database. If you don't extend these API input and output XML files, you may not get the results you want in the UI when your business logic is executing.
  • Every API input and output XML file has a DTD and XSD associated to it. Whenever you modify input and output XML, you must generate the corresponding DTD and XSD to ensure data integrity. If you don't generate the DTD and XSD for extended XML, you may get inconsistent data.
  • How to customize JAX-WS handlers for web services.
Note:
  • If you pass basic and bearer authentication type in separate requests, the request will process correctly. Passing both basic and bearer authentication type in a single request is not supported.
  • Sterling Order Management System Software supports basic, bearer, standard, and extended authentication types. If you set REST to the extended authentication type, use the YCPSSOManager custom implementation. For more information, see xapirest.properties.