This documentation applies to the 8.0 version of BMC Atrium Core, which is in "End of Version Support." You will not be able to leave comments.

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

Registering the Service Context web service for BMC applications

BMC Atrium Service Context sends and receives data through the Mid Tier. Therefore, to share data with BMC Atrium Service Context, each BMC application must register a web service in the Atrium web services registry.

  • BMC AR System based applications use the AR System Web Services Registry form. 
  • Other applications, use the web services registry client APIs.

For BMC Remedy IT Service Management (BMC Remedy ITSM), BMC Service Request Management, and BMC Atrium Service Level Management, web services are registered by using the AR System Web Services Registry form. When you install one of these products, a ServiceContext web service record is created in this form. To register the web service, update this record with information specific to the BMC application or suite.

You can register web services only for BMC Remedy ITSM, BMC Service Request Management, and BMC Atrium Service Level Management applications from here. You cannot register web services for BBPM or BMC Bladelogic applications. 

Note

Only a user with AR admin rights can register and verify web services for BMC applications.

(8.0.00) Registering the Service Context web service for a BMC applications

 Registering and verifying applications

  1. Open the AR System Web Services Registry form from the BMC Remedy AR System Administration Console (System > General > Web Services Registry).
  2. Click New Request.
  3. Modify the service context record as follows:
    1. In the Business Name field, type BMC.
    2. In the Web service field, type ServiceContext.
    3. In the WSDL URL field, modify the value with the Mid Tier server name, port number, and context path to reflect your current configuration.
      Example syntax for ITSM:
      http://<midtierServer>:<portNumber>/arsys/services/servicecontext_attr_itsm?wsdl
      Example syntax for SLM:
      http://<midtierServer>:<portNumber>/arsys/services/servicecontext_attr_slm?wsdl
      Example syntax for SRM:
      http://<midtierServer>:<portNumber>/arsys/services/servicecontext_attr_srm?wsdl
    4. In the End Point URL field, modify the value with the Mid Tier server name, port number, and context path to reflect your current configuration.
      Example syntax for BMC Remedy ITSM:
      http://<midtierServer>:<portNumber>/arsys/services/servicecontext_attr_itsm
      Example syntax for SLM:
      http://<midtierServer>:<portNumber>/arsys/services/servicecontext_attr_slm
      Example syntax for SRM:
      http://<midtierServer>:<portNumber>/arsys/services/servicecontext_attr_srm
  4. In the Publish To Registry? field, choose Yes.
  5. Click Save.

(8.0.00) To verify the Service Context web service registration for a BMC application

  1. Open the AR System Web Services Registry Query form from the BMC Remedy AR System Administration Console (System > General > Web Services Registry Query).
  2. Click New Search.
  3. In the Web Service field, enter ServiceContext.
  4. Click Search.
  5. From the results list, select the ServiceContext web service record for your BMC application.

    The BMC application name appears in the Application Name field as ITSM, SRM, or SLM.
  6. Verify that the WSDL URL and End Point URL fields are populated with valid URLs that reflect your current configuration.

    For example URL syntax, see step 5 in "To register the ServiceContext web service for a BMC application", which precedes this procedure. 
  7. If you cannot find the ServiceContext web service for your BMC application, or if the URLs are not correct, follow the steps in (8.0.00) Registering the Service Context web service for a BMC application to register or re-register the web service.

Related topic

For more information on web services in BMC Remedy AR System, see BMC Remedy AR System web services architecture.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments

  1. Anne Brock

    I have this set up and I can see incidents and outages in the service context window; I can add change as an attribute, although the closed change I have isn't actually showing up, not sure why. But I can't add Problem as an attribute of a service. I assume my ITSM wsdl is correct since I can add incidents, outages and changes as attributes. I see a time parameter for problems on the advanced settings page. Any idea why I don't see problems as an available attribute?

    Anne

    ps - I am NOT getting emails when pages are updated even though I have "watch this page" checked. Sure would love to get that fixed!

    Aug 09, 2012 12:30
    1. Devendra Yadav

      Anne,

      Please take a look at this link it describes list of available attributes for service context. "Open Problems" is available only for Internal use and it can be accessed via APIs we don't allow this to be added on UI.

      Thanks,

      Devendra Yadav

      Aug 28, 2012 12:12