Learning about BMC Web Services
The BMC Atrium Core Web Services and the BMC Remedy AR System Web Services are not the same features and do not serve the same purpose. BMC Remedy AR System enables AR applications to provide access and control to their forms through web services by exposing and managing a form through web services.
BMC Remedy AR System uses Apache Axis whereas BMC Atrium Core Web Services uses Apache Axis2. You can register BMC Remedy AR System Web Services if the UDDI registry is installed and its information is configured in BMC Remedy AR System. For more information, see Integrating in the BMC Remedy AR System documentation.
BMC Atrium Core Web Services are based on Axis2 version 1.5 and expose all (or almost all) the public APIs available from BMC Atrium Core, including reconciliation, normalization, and BMC Atrium CMDB APIs. BMC Atrium Core Web Services also exposes other web services that register with the Apache jUDDI Registry Server, such as Impacted Services.
All BMC web services register with a central service registry (the Apache jUDDI Server) that makes them available to other services and clients.
The following figure shows how web services are published and requested through the Apache jUDDI Registry Server.
BMC web services and clients
BMC Atrium Core Web Service Infrastructure runs on a modified Apache Axis2 infrastructure. Other BMC web services run on their own application servers but publish to the Apache jUDDI Server. A consuming client finds the available services in the Apache jUDDI Server and then invokes the services using web interfaces.
The following figure shows the BMC Atrium Core Web Services and Apache Axis2 infrastructure in more detail.
BMC Atrium Core Web Services and Apache Axis2 infrastructure
The Apache jUDDI Registry Server depends on the database specified during the Web Services installation as the repository for UDDI data. The database must be running before the Apache jUDDI Registry Server is started.
The Apache jUDDI Server is implemented as a collection of web services and is deployed as a WAR file (uddi.war ) on the web application server.
- The Apache jUDDI Server utilities and sample scripts are located in $ATRIUMCORE_HOME/wsc/wsregistryapi.
The Atrium Web Service is deployed as an expanded web application archive from the $ATRIUMCORE_HOME/wsc/atriumws90 directory.
BMC Atrium Web Services and Infrastructure
The table below provides information that you need to get started with the BMC Atrium Web Services and Infrastructure.
Describes the BMC Atrium Core Web Services Infrastructure which uses Apache Axis2, including modifications.
Describes the UDDI Registry which uses Apache jUDDI, including modifications, enhancements, and unsupported features.
Explains how to do the following tasks:
Describes how to back up and restore the UDDI Registry.
Describes the default security settings for BMC Atrium Core Web Services, which you can customize for secure data transmission.
Explains the relationship between the BMC Atrium Core Web Services and the BMC Remedy AR System Web Services.
Provides guidelines for creating interfaces and publishing to the UDDI Registry.
Describes the web services and the security features.