Comments (6)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 commented Permalink

Hi Jim, <div>&nbsp;</div> I plan to install Omegamon XE on z/OS version 1.11 I read from Tivoli Monitoring and Omegamon XE Information Center they mention that Omegamon XE is not support SPIPE. But our ITM environment is using SPIPE because of security concern and agreed on Hardening Document with Customer. <div>&nbsp;</div> Do you have any recommend solution for us to fix this issue? Thank you in advance.

2 Jim Felder commented Permalink

Hi Matee, <div>&nbsp;</div> I am not sure to which usage of SPIPE the information center refers. <div>&nbsp;</div> The IBM Tivoli OMEGAMON XE on z/OS agent runs in the monitoring server address space and hence can use any of its configured protocols, including IP.SPIPE, to communicate with the TEMS. <div>&nbsp;</div> I searched the IBM Tivoli OMEGAMON XE on z/OS Version 5 Release 1 Planning and Configuration Guide <div>&nbsp;</div> <div>&nbsp;</div> but found no matches for SPIPE. <div>&nbsp;</div> Please send me a link to the information that you found and I will give you an explanation of its intent. <div>&nbsp;</div> Thanks.

3 commented Permalink

Hi Jim, <div>&nbsp;</div> Thank you for your response. The link that I mention "". <br /> By the way, I had installed Omegamon XE on UAT environment with SPIPE and it reply "Location server unavailable". Then, I reconfigure with PIPE, it's work. I already check the firewall by telnet to Hub TEMS both SPIPE and PIPE port are passed. <div>&nbsp;</div>

4 Jim Felder commented Permalink

The section in the book to which you refer is in the context of "Using existing OMEGAMON and other monitoring agents with IBM Tivoli Monitoring". It is the pre-ITM agents that do not have support for IP.SPIPE. <div>&nbsp;</div> That said, "Location server unavailable" means that the agent was unable to connect to a TEMS with the specified protocol. Make sure that the TEMS has IP.SPIPE enabled and configured, and that for z/OS, a TTLS profile has been defined for ITM in z/OS Communications Server. That allows the SSL PIPE to work.

5 Jackie Fernandez commented Permalink

Hi Jim, <div>&nbsp;</div> I work for an IBM middleware operations team. We manage all the customer software and the middleware in IBM hosted servers (GHO). Our servers are all Linux (SuSe) in GHOz. We have multiple clients running applications (DB2, WAS and Domino) on the same servers (ie two web apps in one Linux server, 5 DB's in one Linux server). <div>&nbsp;</div> My management team would like to monitor what each application is consuming (CPU, Memory) so that we can have better metrics to charge our clients. We would also like to investigate if we can consolidate some servers.

6 Jim Felder commented Permalink

Hi Jackie, <div>&nbsp;</div> As a start, I would suggest looking at the IBM Tivoli Monitoring Linux OS Agent. You can review the Linux OS Agent User's Guide at the link below: <div>&nbsp;</div> <div>&nbsp;</div> For IBM Tivoli Monitoring as a whole, here is a link to its Information Center: <div>&nbsp;</div> <div>&nbsp;</div> If you'd like to dig deeper than the processes themselves, there are agents for the various applications. Here is the link for the IBM Tivoli Composite Application Manager for Applications Information Center: <div>&nbsp;</div> <div>&nbsp;</div> Please let me know if this is what you are looking for or if I can be of any further assistance to you. <br />