Overview of the CMDB web services
The CMDB Web Services Infrastructure component is divided into the following components:
- Web Services Infrastructure- The modified Apache Axis2 stack.
- CMDB Core Web Services- CMDB Core Web Services
All CMDB 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.
CMDB Web Services and clients
CMDB Web Services 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 CMDB Web Services and Apache Axis2 infrastructure.
CMDB 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 the Atrium web services container pod: /opt/bmc/AtriumCoreWS/wsc/wsregistryapi.
The CMDB web service is deployed as an expanded web application archive from the /opt/bmc/AtriumCoreWS/wsc/atriumws<majorversion> directory. For example, /opt/bmc/AtriumCoreWS/wsc/atriumws2105