This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

To view the latest version, select the version from the Product version menu.

BMC Atrium Core Web Services architecture

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.

Related topic

Getting started with BMC Atrium Core Web Services

Was this page helpful? Yes No Submitting... Thank you