ServiceGrid Article - Metro Webservice Setup Guide

From DocWiki

Jump to: navigation, search

Contents

Overview

Depending on the the communication direction one has several possibilities in the application. Before creating a connection we have to decide whether SolveDirect has to play the active or the passive part.

Passive

Passive in this context means that ServiceGrid does not communicate actively even if an update at ServiceGrid occurs. It waits for data to be pushed to ServiceGrid by a connection partner or data to be pulled from ServiceGrid.

Active

Active in this context means that ServiceGrid pushes data to a parter as soon as an update occurs and polls periodically for updates from the connection partner.

All the mentioned connection methods can be combined arbitrarily. A more detailed high level explanation of the connection methods you can find in the latest Green Book Use Cases.

ServiceGrid is passive - connection partner initiates communication

When you have decided that ServiceGrid plays the passive part and the connection partner initiates the communication you can choose between several alternatives.

Core CallService

The least effort for the customizer is to use the Core CallService. In this service the connection partner can handle a fixed format. The Core CallService is the ServiceGrid standard implementation. It contains all important fields that can be used for inbound or for outbound transactions.

A basic setup guide including possible limitations can be found here. The setup guide will describe inbound as well as outbound configuration.

Custom CallService

As soon as the connection partner is not able to process or send data in the ServiceGrid standard format that is provided/accepted by the Core CallService, the customizer has to send or process a connection partner specific format. For this purpose the Custom CallService is the right choice. Anyway the service is sending valid SOAP messages.

A basic setup guide including possible limitations can be found here. The setup guide will describe inbound as well as outbound configuration.

ServiceGrid is active - ServiceGrid initiates communication

Quite often the connection partner does not want to configure or implement any triggers or something else for communication. In this case ServiceGrid has the active role and has to push data to the partner as soon as an update occurs. To get informed about an update on the connection partner's side ServiceGrid polls steadily for information updates.

Pushing data based on Metro

This method can be used to push data from ServiceGrid to a connection partner actively as soon as an update on a call occurs. This message can be either a structured SOAP message or an "unstructured" HTTP message. Both types of communication are described in the setup guide.

Pulling data based on Metro

Whenever the connection partner is not able or does not want to send call updates actively to ServiceGrid, ServiceGrid itself has to become the active player in the communication. For this purpose the application provides a pulling service which polls the connection partner in a certain interval. How to configure this service can be found in the setup guide for pulling services.



For a complete list of Cisco ServiceGrid Articles, go to the List of Articles page.




Rating: 0.0/5 (0 votes cast)

Personal tools