Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
5 replies Latest Post - ‏2014-03-04T17:42:57Z by janreed1
janreed1
janreed1
4 Posts
ACCEPTED ANSWER

Pinned topic Service Catelog using WSRR

‏2014-02-21T17:10:53Z |

I am looking to maintain all my interfcaes in the WSRR. I have interfaces like web services, rest services, MQ communications, MQ FTE processes and  DB to DB interactions with scheduled jobs.

Right now all these are mainained in a excel sheet. Below are some of the excel sheet columns. 

Could any one suggest what is best approach to maintain them within WSRR.

 

 

 

Interface ID
Description
Business Area
Project Nam
Business Priority
Direction(Inbound/Outboud)
Document Link
JOB Name
Source Application Name
Target Application Name
Contact Details
Source interface details(queue, directory, DB, schema)
Destination interface details(queue, directory, DB, schema)
Application server name, cluster name, ports used
Scheduer info
sourc code location and tag
User Defined field 1
User Defined field 2
User Defined field 3
User Defined field 4
User Defined field 5
User Defined field 6

 

  • DavidSeager
    DavidSeager
    63 Posts
    ACCEPTED ANSWER

    Re: Service Catelog using WSRR

    ‏2014-02-26T09:46:07Z  in response to janreed1

    For the web services & rest services, these are modelled out of the box as Business Services (representing the business need for the service) and Service Versions (representing a version of the service).

    A "Service" in WSRR is something that provides a callable service and can also consume other services. We also have "Applications" which only consume other services and do not themselves provide a service, this is so you can model things like a web site that uses a service.

    For MQ communications if you use the MQ WSDL standard described here http://www-01.ibm.com/support/docview.wss?rs=802&uid=swg24017518&loc=en_US&cs=utf-8&lang=en then you can load the WSDLs which describe MQ applications into WSRR and register them as the above type of service.

    For the other types MQ FTE processes and DB to DB interactions with scheduled jobs, these are not modelled OOB in WSRR. However you can extend the model and add another type if required. The way that REST is described is by manually defining the endpoints and uploading a document that describes the format of the message and how the REST service can be called. This is then a model that other clients have duplicated to describe their own non-SOAP services.

    I would still recommend describing other services as a Service Version, but the underlying objects that describe the interface, endpoints, etc can be created to describe say MQ FTE endpoints and interfaces.

    For the column you have in the spreadsheet, these are described as properties on the various objects in WSRR, such as properties on the Service Version. Properties can be added to objects in WSRR and defined as required. Properties are single values and can be of various types. For Contact Details this would make a good property, and we do already have properties like owner email and owner name.

    You can also use classifications and add them to objects. These are like tags but are defined in the model, so users can only choose from predefined values. So for Business Area this would make a good classification where you define all the different allowed areas in a hierarchy.

    For links between services, eg service X consumes service Y, we model these using Service Level Definitions (non functional quality of service definition) and Service Level Agreements (an agreement to use a service), where there is an SLA between a consumer service and the provider service, and that SLA is on a certain SLD the provider service offers.

     

  • DavidSeager
    DavidSeager
    63 Posts
    ACCEPTED ANSWER

    Re: Service Catelog using WSRR

    ‏2014-02-26T10:13:52Z  in response to janreed1

    For Source interface details(queue, directory, DB, schema) and Destination interface details(queue, directory, DB, schema) these are modelled in WSRR as an interface object that is attached to the Service Version. For SOAP based services WSRR will shred the WSDL document and create all the objects, for other types like REST you define them manually. Of course for the Source this is on the Service Version that is the consumer I assume and the Destination this is the Service Version that is being consumed.

    For Application server name, cluster name, ports used these details live on the endpoint objects. For WSDL based services WSRR will shred the WSDL and generate the endpoint objects. For REST you create them yourself.

  • janreed1
    janreed1
    4 Posts
    ACCEPTED ANSWER

    Re: Service Catelog using WSRR

    ‏2014-03-04T15:54:12Z  in response to janreed1

    Thanks David. Much appreciated your response. I did a POC with few interfaces and it is working as expected.

    I have one quick qustion is there a way we can change the Graphical object image and on mouse hover help contents (When we place move over any object in grahical view it will give a help box with more contentc).

     

     

    • DavidSeager
      DavidSeager
      63 Posts
      ACCEPTED ANSWER

      Re: Service Catelog using WSRR

      ‏2014-03-04T17:02:26Z  in response to janreed1

      You cannot customize the icons used for the various types in Business Space, including in the hover card.

  • janreed1
    janreed1
    4 Posts
    ACCEPTED ANSWER

    Re: Service Catelog using WSRR

    ‏2014-03-04T17:42:57Z  in response to janreed1

    Thanks David.