BMC Impact Integration Web Services server architecture

The BMC Impact Integration Web Services developer package includes the following components:

  • The BMC Impact Integration Web Services archive (ImpactManager.aar) file that provides BMC Impact Integration Web Services API for clients exchanges events and data with BMC Impact Manager cells through request and response.
  • Web Services Description Language (WSDL), an XML document that defines the data types, messages, operations, and binding protocol of this web service
  • The Axis2 distribution
  • A Tomcat web server that provides the HTTP environment and loads BMC Impact Integration Web Services.
  • UDDI help tools
  • Client samples

The following figure depicts the interaction between the BMC Impact Integration Web Services server, the BMC Impact Manager cell or cells, and the third-party client: 

BMC Impact Integration Web Services server overview 

iiws.PNG

Security considerations

BMC Impact Integration Web Services does not support WS-Security based authentication. It only supports the Transport-level security, the SSL security.

Internationalization considerations

Identify areas of your solution that must be able to support Level-1 internationalization. This level means your software must be able to deal with any non-ASCII characters from input and store them properly. If you are unsure of Level 1 internationalization requirement, review them with an internationalization architect.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*