This documentation applies to the 8.1 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.

To register the Service Context web service for BMC applications

  1. From IT Home, go to Applications > BMC Atrium Core > Service Context Administration console > Advanced Settings.
  2. Click the Configure button next to Configure provider endpoints. The AR System Web Services Registry form is displayed.
  3. Click New Request.
  4. 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
  5. In the Publish To Registry? field, choose Yes.
  6. Click Save.

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

  1. From IT Home, go to Applications > BMC Atrium Core > Service Context Administration console > Advanced Settings.
  2. To configure provide endpoints, click the respective Configure button. The AR System Web Services Registry form is displayed
  3. 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.
  4. 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. 
  5. If you cannot find the ServiceContext web service for your BMC application, or if the URLs are not correct, follow the steps in Registering the Service Context web service for BMC applications 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
  2. Jose pedro Teixeira

    Hi, in order to configure https URLs where and how do we add certificates?

    AR server, Atrim WS server, MidTier, all?

    Feb 11, 2015 07:01
  3. Young So

    Base on the document;  I am suppose have the ability to configure the following field WSDL URL: but, the field isn't available on the form.  Here is the URL:  http://<ARSERVER>/arsys/forms/remedydev/CMDB.SC%3AServiceContextAuthenticationInfo/Service+Context+Authentication+Info/?cacheid=2037f19e

    Am I missing something?

     


    May 22, 2015 12:27
    1. Amol Redij

      Hi Young,

      I have noted your comment. Thank you.

      I will reply to you with a valid confirmation from the concerned SME.

      Regards,

      Amol Redij

      May 25, 2015 01:44
    1. Amol Redij

      Hi Young,

      You should click the Configure button next to Configure provider endpoints. This opens the AR System Web Services Registry form. WSDL URL field is available on that form.


      I suppose you clicked the Configure button next to Configure authentication information. This opens the CMDB.SC%3AServiceContextAuthenticationInfoConsole form and hence you are cannot view the WSDL URL field.

      Regards,

      Amol

       

      May 29, 2015 04:26
  4. Young So

    Amol,

    uh, oh!  I don't see configure buttons.  It must be not configured right!  Thanks for the screen shot.

    May 29, 2015 12:02
    1. Amol Redij

      Hi Young,

      Possibly you are referring to the wrong version of documentation then. This documentation refers to the product version 8.1

      Please make sure that the documentation version matches the product version that you are using.

      If you are using an earlier version, for example 8.0, then you should refer to https://docs.bmc.com/docs/display/public/ac80/Registering+the+Service+Context+web+service+for+BMC+applications.

      Hope this helps.

      Regards,

      Amol Redij

      Jun 01, 2015 05:00
      1. Young So

        I thought the something, and review the 8.0 document. I do show my web service display properly for the following: SLM, SRM, and ITSM. But, I have more thane those entries. Which is bit confusing than what's documented.

        Jun 01, 2015 11:29
        1. Amol Redij

          Hi Young,

          Given the situation, I would request you to contact Customer Support to log a formal ticket on this issue. To contact BMC support, click BMC Support Contacts.

          Regards,

          Amol

          Jun 02, 2015 01:19
          1. Young So

            Amol,

            Thanks. I've open an support incident.

            Jun 02, 2015 09:21