Topic
  • 5 replies
  • Latest Post - ‏2013-09-03T14:34:37Z by RM03_Chris_Barlock
enrico.vannini
enrico.vannini
21 Posts

Pinned topic unsupported data sources

‏2013-08-30T14:09:33Z |

how do I set a generic ITM agent to feed AI?

is it enough to install and run ? Or should I configure to use a different port from 1920 (which does not make sense to me, since 1920 is the port on TEPS, that of course does not exist) ?

Or what ?

Thanks

Enrico Vannini

  • RM03_Chris_Barlock
    RM03_Chris_Barlock
    43 Posts

    Re: unsupported data sources

    ‏2013-08-30T14:57:53Z  

    AI will detect any ITM agent that is installed on a VM that it can see.  We changed the default port on which we look for agents from 1920 to 51920.  The reason for this is that we uncovered a number of agent defects in our testing that are fixed in the version of the agents that we ship with AI.  We did not want to detect older agents that did not incorporate these fixes and have them behave badly. 

    To detect any ITM agents, you can reconfigure the agent to use port 51920 or you can go to the AI Advanced Configuration page in our UI and change the default HTTP port back to 1920 on the Agent Service Interface tab.

    Chris

  • enrico.vannini
    enrico.vannini
    21 Posts

    Re: unsupported data sources

    ‏2013-09-02T18:16:16Z  

    AI will detect any ITM agent that is installed on a VM that it can see.  We changed the default port on which we look for agents from 1920 to 51920.  The reason for this is that we uncovered a number of agent defects in our testing that are fixed in the version of the agents that we ship with AI.  We did not want to detect older agents that did not incorporate these fixes and have them behave badly. 

    To detect any ITM agents, you can reconfigure the agent to use port 51920 or you can go to the AI Advanced Configuration page in our UI and change the default HTTP port back to 1920 on the Agent Service Interface tab.

    Chris

    Chris, I was able to see an unsupported agent by switching the listening port on FN to 1920, but not the other way around.

    I am actually confuses because I thought that 1920 was merely the port that TEPS listen on for http requests, while communication between agents and TEMS occurs on 1918+(N*4096) as explained here:

    http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=%2Fcom.ibm.itm.doc%2Fitm_install171.htm&path%3D3_8_1_0_5_0_7_2

    so, what is agent doing with 1920 ? Can you please clarify that ?

    And how do I change the port on agent side ? At the same link I found a lot about KDE_TRANSPORT and KDC_FAMILIES ut again it seems to apply to ip-pipe port (that defaults to 1918

    Can you help ?

  • RM03_Chris_Barlock
    RM03_Chris_Barlock
    43 Posts

    Re: unsupported data sources

    ‏2013-09-02T20:52:12Z  

    Chris, I was able to see an unsupported agent by switching the listening port on FN to 1920, but not the other way around.

    I am actually confuses because I thought that 1920 was merely the port that TEPS listen on for http requests, while communication between agents and TEMS occurs on 1918+(N*4096) as explained here:

    http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=%2Fcom.ibm.itm.doc%2Fitm_install171.htm&path%3D3_8_1_0_5_0_7_2

    so, what is agent doing with 1920 ? Can you please clarify that ?

    And how do I change the port on agent side ? At the same link I found a lot about KDE_TRANSPORT and KDC_FAMILIES ut again it seems to apply to ip-pipe port (that defaults to 1918

    Can you help ?

    1920 is the default port on which the agent (not the TEPS) listens for HTTP requests.  You can change the ASI port using KDC_FAMILIES.   Here's an example:

    KDC_FAMILIES="ip.spipe port:3660 ip use:n ip.pipe use:n sna use:n http:51920"

    I believe I mentioned in one of these threads that we changed the default ASI port from 1920 to 51920 for the agents that we ship because we uncovered some problems with agent communication during our testing.  These are fixed in the agents we ship but we wanted to minimize the chance of discovering "older" agents that did not have these fixes.

    Chris

  • enrico.vannini
    enrico.vannini
    21 Posts

    Re: unsupported data sources

    ‏2013-09-03T08:09:17Z  

    1920 is the default port on which the agent (not the TEPS) listens for HTTP requests.  You can change the ASI port using KDC_FAMILIES.   Here's an example:

    KDC_FAMILIES="ip.spipe port:3660 ip use:n ip.pipe use:n sna use:n http:51920"

    I believe I mentioned in one of these threads that we changed the default ASI port from 1920 to 51920 for the agents that we ship because we uncovered some problems with agent communication during our testing.  These are fixed in the agents we ship but we wanted to minimize the chance of discovering "older" agents that did not have these fixes.

    Chris

    Thanks Chris,

    I modified yn.config with your line above and yn.ini with this line: KDC_FAMILIES=$NETWORKPROTOCOL$ http:51920 https:0
     (not sure this is needed).

    It works perfect now and I really appreciate the flexibility (using ITM agents for SCM-AI and using SCM-AI distributed agents for ITM).

    Looking at dashboard for WebSphere agent (the one I used for this test) I realize that the only difference between the supported and not supported agents is the presentation layer: for OS/WRT/DB you have a lot of out-of-the-box graph, for unsupported you provide just the table view.

    That would be one reason to give higher priority to dashboard customization features: if the end user can create his/her own graphs, then he/she can basically add ANY agent and have the same good result he/she has for the supported ones.

    Thanks for the help

    Enrico

     

  • RM03_Chris_Barlock
    RM03_Chris_Barlock
    43 Posts

    Re: unsupported data sources

    ‏2013-09-03T14:34:37Z  

    Thanks Chris,

    I modified yn.config with your line above and yn.ini with this line: KDC_FAMILIES=$NETWORKPROTOCOL$ http:51920 https:0
     (not sure this is needed).

    It works perfect now and I really appreciate the flexibility (using ITM agents for SCM-AI and using SCM-AI distributed agents for ITM).

    Looking at dashboard for WebSphere agent (the one I used for this test) I realize that the only difference between the supported and not supported agents is the presentation layer: for OS/WRT/DB you have a lot of out-of-the-box graph, for unsupported you provide just the table view.

    That would be one reason to give higher priority to dashboard customization features: if the end user can create his/her own graphs, then he/she can basically add ANY agent and have the same good result he/she has for the supported ones.

    Thanks for the help

    Enrico

     

    We understand the requirement, Enrico.

    Chris