Topic
  • 9 replies
  • Latest Post - ‏2014-07-15T22:50:11Z by 135711
135711
135711
25 Posts

Pinned topic Generic Adapter for Web Service Applications - ITIM

‏2014-06-09T01:20:37Z |

Hi All,

I have a requirement to develop a generic adapter, to integrate ITIM with web services based applications.  Basic idea is to develop a single standarised adapter which will be used to integrate different web service applications with ITIM.  This is aimed to save cost and effort, everytime a new application gets integrated with ITIM.

Now the question is, is this practically possible? If yes, then can someone pls guide me how to start with the development.  If No, can someone pls let me know why its not possible.

I am very new to ITIM and Web Services.

Thanks in Advance.

 

Thanks.

  • Sanjay Sutar
    Sanjay Sutar
    157 Posts

    Re: Generic Adapter for Web Service Applications - ITIM

    ‏2014-06-09T05:24:34Z  

    If the target applications are exposing *same* web services then single adapter should work mostly, only problem I see about the schema for each application accounts. Its not same generally for different applications. You may have to develop some intellegent logic to handle that. Anyway once an adapter is developed for one appliations, if the other applications are exposing same web services , it should not be very difficult to modify existing adapter and create new for other applications.

  • yn2000
    yn2000
    1112 Posts

    Re: Generic Adapter for Web Service Applications - ITIM

    ‏2014-06-09T14:27:53Z  

    If AD uses sAMAccountName, LDAP uses uid, and DB uses USERNAME, somebody has to pay for the translation. So, Generic Adapter for Web Service application is possible, but it does not mean that the company save cost. For example: You have Generic Adapter for Web Service, but then you deploy XML translator device like DataPower, then you save in TIM, but pay in DataPower. So, observe and analyze your future managed targets to justify your choice. Based on my experience, uniform identity, or even centralized identity, is a myth. Well, unless, it is in a tiny company probably.

    Rgds. YN.

     

     

  • franzw
    franzw
    396 Posts

    Re: Generic Adapter for Web Service Applications - ITIM

    ‏2014-06-09T15:09:29Z  
    • yn2000
    • ‏2014-06-09T14:27:53Z

    If AD uses sAMAccountName, LDAP uses uid, and DB uses USERNAME, somebody has to pay for the translation. So, Generic Adapter for Web Service application is possible, but it does not mean that the company save cost. For example: You have Generic Adapter for Web Service, but then you deploy XML translator device like DataPower, then you save in TIM, but pay in DataPower. So, observe and analyze your future managed targets to justify your choice. Based on my experience, uniform identity, or even centralized identity, is a myth. Well, unless, it is in a tiny company probably.

    Rgds. YN.

     

     

    Based on my experience, uniform identity, or even centralized identity, is a myth. Well, unless, it is in a tiny company probably.

    Amen - and by the way a tiny company does probably not need a uniform identity anyhow :-)

    Regards

    Franz Wolfhagen

  • goonitsupport
    goonitsupport
    117 Posts

    Re: Generic Adapter for Web Service Applications - ITIM

    ‏2014-06-09T15:18:52Z  

    Yes, I think this is a good plan and we have done this for a customer before where each Web Application had its own custom registry. So the plan is to have a generic TDI adapter that calls a WebService held in each application. The Web Service is a template that each application deploys within their application and adapts to their own needs.

    So the service form will contain the url of the WebService to be called for each application which TDI then calls on receipt of a provisioning request..

    The account form will contain a set of standard attributes common across all services e.g. name, group, user id, etc

    A special attribute can then exist to contain any custom attributes that a future application may need. This can be a JSON or XML string that can be populated from provisioning poilices. The application owner specifies what additional data (if any needs to be populated into this field for its own parsing).

    In this way you have 1 adapter for many applications, each application deploys their own version of the template WebService.

     

    Hope this helps,

    Vincent

  • 135711
    135711
    25 Posts

    Re: Generic Adapter for Web Service Applications - ITIM

    ‏2014-06-09T22:24:01Z  

    Hello All,

    Thanks for all your valuable inputs.

    I will be starting with the development and probably will again need your help in future.

    Once again thanks.

    Thanks.

  • 135711
    135711
    25 Posts

    Re: Generic Adapter for Web Service Applications - ITIM

    ‏2014-07-03T22:50:56Z  

    Hello Vincent/All,

    I have a couple of queries.  Can you pls answer them?

    I need to know what TDI connectors would be best suitable in this situation.  I understand we have multiple connectors like Axis2WebServiceClientFunctionComponent, AxisEasyInvokeSoapWebServiceFunctionComponent etc are available in TDI through which we can invoke a Web Service.  Which connector would be most feasible for this case?

    Do we need to define WSDL/SOAP messages?  I mean the basic operations performed are Add, Modify, Supend, Delete, Test in ITIM.  Corresponding to each operation respective assemblyLine from the adapter is invoked.  So if we are developing a generic adapter, then probably we need to use one single connector in an assemblyLine with well defined parameters like, "SOAP Operation", "Operation Paremeters" etc.  This would be common for all applications which in future we will be trying to integrate.  So my question is do I need to come up with a template of WSDL and the same should be passed to respective application owners in future?

    Also will it be a good idea to read the connector parameters from a property file based on "application name" received from front end, say Service Form.  I mean writing some Java Code to fetch parameters in "Prolog" script and passing the same in connector parameter.

    Will it be feasible for me to integrate Cloud based applications in future?

    Please let me know.  Currect me if I am going wrong somewhere.

    Thanks in Advance.  Please help.

     

     

  • 135711
    135711
    25 Posts

    Re: Generic Adapter for Web Service Applications - ITIM

    ‏2014-07-09T05:15:37Z  
    • 135711
    • ‏2014-07-03T22:50:56Z

    Hello Vincent/All,

    I have a couple of queries.  Can you pls answer them?

    I need to know what TDI connectors would be best suitable in this situation.  I understand we have multiple connectors like Axis2WebServiceClientFunctionComponent, AxisEasyInvokeSoapWebServiceFunctionComponent etc are available in TDI through which we can invoke a Web Service.  Which connector would be most feasible for this case?

    Do we need to define WSDL/SOAP messages?  I mean the basic operations performed are Add, Modify, Supend, Delete, Test in ITIM.  Corresponding to each operation respective assemblyLine from the adapter is invoked.  So if we are developing a generic adapter, then probably we need to use one single connector in an assemblyLine with well defined parameters like, "SOAP Operation", "Operation Paremeters" etc.  This would be common for all applications which in future we will be trying to integrate.  So my question is do I need to come up with a template of WSDL and the same should be passed to respective application owners in future?

    Also will it be a good idea to read the connector parameters from a property file based on "application name" received from front end, say Service Form.  I mean writing some Java Code to fetch parameters in "Prolog" script and passing the same in connector parameter.

    Will it be feasible for me to integrate Cloud based applications in future?

    Please let me know.  Currect me if I am going wrong somewhere.

    Thanks in Advance.  Please help.

     

     

    Any help please??

  • goonitsupport
    goonitsupport
    117 Posts

    Re: Generic Adapter for Web Service Applications - ITIM

    ‏2014-07-15T20:50:59Z  
    • 135711
    • ‏2014-07-09T05:15:37Z

    Any help please??

    Hi, apologies I have been/am on holiday at the moment and so my answer may not be as complete as it may otherwise be.

    TDI connector for Web Services - to be honest I find the Web Services connectors to be problematic sometimes. Normally people give me WSDL to connect to their services and sometimes especially with complex WSDL I find I have to use a simple HTTPClientConnector and generate my own POST data manually. But you can dictate what the WSDL should be (am I right)? So perhaps first of all you need to write a stub example service that you will use and call from your connector and test against this. The choice is yours.

    Yes you need to define the WSDL! I think you are trying to say to Application developers that if they want to have applications managed by ISIM then they must implement these operations and you will send them these parameters/attributes. 

    I would Map 1-2-1 the ITIM/ISIM operations   to individual AssemblyLines and SOAP operations that are being called.

    Any connector parameters I would pass to the AssemblyLine from the Service form in ISIM. So you may have URL, Username and Password passed for each application. Any other parameters that you can think of just customise the Service form?

    Last any application could be Cloud or internal based. Of course if someone purchases a generic Cloud application you may have to write to their API (SOAP Operations) than perhaps them implementing yours. This is always the dilemma.

    From your questions I would say that you have the correct line in thinking. There is always a multitude of possible correct answers and you have to consider the pitfalls of each and be confident in your judgement to implement the best. I think you will be fine.

    Best regards,

    Vincent

     

     

  • 135711
    135711
    25 Posts

    Re: Generic Adapter for Web Service Applications - ITIM

    ‏2014-07-15T22:50:11Z  

    Hi, apologies I have been/am on holiday at the moment and so my answer may not be as complete as it may otherwise be.

    TDI connector for Web Services - to be honest I find the Web Services connectors to be problematic sometimes. Normally people give me WSDL to connect to their services and sometimes especially with complex WSDL I find I have to use a simple HTTPClientConnector and generate my own POST data manually. But you can dictate what the WSDL should be (am I right)? So perhaps first of all you need to write a stub example service that you will use and call from your connector and test against this. The choice is yours.

    Yes you need to define the WSDL! I think you are trying to say to Application developers that if they want to have applications managed by ISIM then they must implement these operations and you will send them these parameters/attributes. 

    I would Map 1-2-1 the ITIM/ISIM operations   to individual AssemblyLines and SOAP operations that are being called.

    Any connector parameters I would pass to the AssemblyLine from the Service form in ISIM. So you may have URL, Username and Password passed for each application. Any other parameters that you can think of just customise the Service form?

    Last any application could be Cloud or internal based. Of course if someone purchases a generic Cloud application you may have to write to their API (SOAP Operations) than perhaps them implementing yours. This is always the dilemma.

    From your questions I would say that you have the correct line in thinking. There is always a multitude of possible correct answers and you have to consider the pitfalls of each and be confident in your judgement to implement the best. I think you will be fine.

    Best regards,

    Vincent

     

     

    Thank you very much Vincent for the detailed reply.  Enjoy your holiday mate.  Let me start working on this.  Will keep you posted.  Once again thanks.