www.solutioning.eu Open in urlscan Pro
192.254.185.182  Public Scan

Form analysis
1 forms found in the DOM

GET https://www.solutioning.eu/

<form role="search" method="get" id="searchform" class="searchform" action="https://www.solutioning.eu/">
  <div>
    <label class="screen-reader-text" for="s">Search for:</label>
    <input type="text" value="" name="s" id="s">
    <input type="submit" id="searchsubmit" value="Search">
  </div>
</form>

Text Content

IBM TIVOLI & WEB DEVELOPMENT TECHNICAL BLOG




Menu Skip to content
 * Home
 * Devops and SRE Consultant CV
 * Contact us


CATEGORY ARCHIVES: IBM TIVOLI MONITORING 6


HOW TO CHECK IF PRODUCT SUPPORT FOR TEPS / ITM6 IS CORRECTLY INSTALLED

Leave a reply

After installing the specific product support, check if the files are correctly
added. Find out what the product code is and run find for that pattern, in this
example we will be using Tivoli Network Manager IP Agent. The product code for
this is NP or KNP.

find . -name knp*
./aix536/cq/sqllib/knp.his
./aix536/cq/sqllib/knp_kcj.sql
./aix536/cq/sqllib/knppackage.xml
./aix536/cw/classes/candle/knp
./aix536/cw/classes/candle/knp/resources/help/de/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/de/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/de/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/de/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/es/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/es/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/es/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/es/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/fr/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/fr/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/fr/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/fr/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/hu/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/hu/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/hu/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/hu/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/it/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/it/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/it/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/it/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/ja/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/ja/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/ja/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/ja/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/ko/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/ko/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/ko/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/ko/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/pl/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/pl/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/pl/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/pl/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/pt_BR/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/pt_BR/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/pt_BR/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/pt_BR/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/ru/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/ru/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/ru/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/ru/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/zh_CN/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/zh_CN/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/zh_CN/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/zh_CN/knp_trademarks.htm
./aix536/cw/classes/candle/knp/resources/help/zh_TW/knp_contents.htm
./aix536/cw/classes/candle/knp/resources/help/zh_TW/knp_home.htm
./aix536/cw/classes/candle/knp/resources/help/zh_TW/knp_notices.htm
./aix536/cw/classes/candle/knp/resources/help/zh_TW/knp_trademarks.htm
./aix536/cw/classes/knp_resources.jar
./aix536/cw/knp.inf
./config/.ConfigData/.tmp/knpenv
./config/.ConfigData/knpenv



Check if the applet.html is properly updated, grep for knp on your applet.html.
This file is located in different directories in each platform, if you are
unsure where it is just do a find for it:

find . -name applet.html
./aix536/cw/applet.html

grep -i knp ./aix536/cw/applet.html

optimizeArchiveOrder( ‘<PARAM NAME = CACHE_ARCHIVE VALUE=”cnp_vbjorball.jar,
kjrall.jar,         util.jar,  chart.jar, ae.jar,             cnp_jviewsall.jar,
terminal.jar, browser.jar, browser-@P.jar, browser-core-@P.jar, icu4jm32.jar,
deploy.jar,         cnp_ps.jar, cnp.jar,            kum_resources.jar, 
kdy_resources.jar,  kis_resources.jar, koq_resources.jar, kqb_resources.jar,
kq7_resources.jar, kqf_resources.jar, koy_resources.jar, kq5_resources.jar,
klz_resources.jar,  kno_resources.jar, kqp_resources.jar, ism.jar,
kp5_resources.jar, kqr_resources.jar, kqv_resources.jar, ka4_resources.jar, 
kex_resources.jar, kph_resources.jar, nvnways.jar,         kqx_resources.jar,
kdp_resources.jar,  kib_resources.jar, kr2_resources.jar, log4j-1.1.1.jar,    
kr6_resources.jar, km5.jar,  kpx_resources.jar, ksy_resources.jar,
kmq_resources.jar, kr4_resources.jar, jrim.jar,            console.jar,        
kgw_resources.jar,  kud_resources.jar, kpv_resources.jar, k99_resources.jar,
kul_resources.jar,  kip_resources.jar,  kn3_resources.jar,  khd_resources.jar,
kor_resources.jar, kcp_resources.jar,  klo_resources.jar, commons-codec-1.3.jar,
k3z_resources.jar, kcf.jar, k87_resources.jar, jsafe.zip,          
kqi_resources.jar, kux_resources.jar,  ibmjsse.jar,         kht_resources.jar,
kva_resources.jar, ks3.jar,            jcf.jar,             kmc.jar,
kgb_resources.jar, kpk_resources.jar, km5_resources.jar, ks3_resources.jar, 
tec_tap.jar,         khv_resources.jar, uif.jar,             knt_resources.jar, 
nways_dep.jar,       launch.jar,          kr3_resources.jar, kvm_resources.jar,
jhall.jar,           kyn_resources.jar, kit.jar,             kr5_resources.jar,
k07_resources.jar, knp_resources.jar,”>’ );

/opt/IBM/ITM/bin/cinfo -i

Look for the product from the list.

np      IBM Tivoli Network Manager
tps     Version: 03.90.00.00
tpw     Version: 03.90.00.00

/opt/IBM/ITM/bin/tacmd listworkspaces |grep knp

Application Type: knp
Application Type: knp
Application Type: knp
Application Type: knp
Application Type: knp

If there knp can not be found in applet.html or in the listworkspaces the TEPS
server will have to be reconfigured. This will kick off the
InstallPresentation.sh script which will then configure the support correctly.
This can be achieved in the following 2 ways:



/opt/IBM/ITM/bin/itmcmd config -A cq <- this will reconfig the entire TEPS
server



./itmcmd execute cq <ITMHOME>/arch/cq/bin/InstallPresentation.sh <- this will
only configure the things you need and it can also be run as a non-root user.

>  

Sharing is caring!
 * Tweet
 * Share
 * Pin
 * Mail
 * Share

This entry was posted in AIX, IBM Tivoli Monitoring 6 on 2012/03/09 by admin.


ITM/TEPS – HOW TO FIX EXCESSIVE NAVIGATOR TREE REBUILDING – AGENTS
APPEARING/DISAPPEARING CONSTANTLY

Leave a reply

I have recently run into this problem. The navigator tree was
rebuilding/changing constantly resulting the TEPS Console to be nearly unusable.
To fix this I set the following variables in cq.ini ( TEPS ini file location
under $CANDLEHOME/config/)

KFW_CMW_DETECT_AGENT_ADDR_CHANGE=N

The Navigator function detects when the IP address for an agent is discovered.
If the agent environment is constantly changing or has improper configurations
that generate excessive Navigator tree rebuilding, consider adding this
environment variable to have any discovery of changes or additions of IP address
ignored.

KFW_CMW_DETECT_AGENT_HOSTNAME_CHANGE=N

This variable is like the one for detect agent address change except that it
prevents the Navigator rebuilding if an agent hostname is changed.

KFW_CMW_DETECT_AGENT_PROPERTY_CHANGE=N

This is like the detect agent address change except that it prevents the
Navigator rebuilding if an agent affinity or affinity version changes.

References/Documentation on TEPS environment variables:

http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/index.jsp?topic=/com.ibm.itm.doc_6.2.fp1/itm_admin52.htm

[ad#Google Adsense-1]

Sharing is caring!
 * Tweet
 * Share
 * Pin
 * Mail
 * Share

This entry was posted in IBM Tivoli Monitoring 6 and tagged ITM, Navigator Tree,
TEPS on 2009/10/21 by admin.


ITM UNIX INSTALLATION – NOTABLE DIRECTORIES

Leave a reply

The table below lists some of the most important directories used by ITM. This
is far from being complete. I will add new information to this whenever I find
an other directory worth mentioning

Number Location Description NodeType 1 $CANDLEHOME/logs ITM log files ALL 2
$CANDLEHOME/bin ITM binary files ALL 3 $CANDLEHOME/config ITM ini files.
Constructing additonal product configuration values using the environment
variable and product specific settings. ALL 4 $CANDLEHOME/config/.ConfigData ITM
environment variables. contains values set at configuration time. ALL 5
$CANDLEHOME/tables/[tems name]/ATTRLIB ITM Attribute files. If you have a
seeding problem you can check if the required attr file is in this directory. If
it is not the seeding wasn’t successful. TEMS 6
$CANDLEHOME/tables/cicatrsq/ATTRLIB Historical data and attrib files ready to be
seeded. Once you install TEMS support for a new product the attrib and
historical data files are being copied here first. Once you do the seeding it
all being copied over to the directory shown above this entry. TEMS 7
$CANDLEHOME/tables/[tems name]/depot In this directory there is a parent
directory called PACKAGES Sub-directories contain all the packages in that
depot. TEMS 8 $CANDLEHOME/[architecture type]/iw/profiles/ITMProfile/logs
Embedded WebSphere log files TEPS 9 $CANDLEHOME/[architecture]/ui/jars/resources
TEPS server resource files. If you have teps support problems check if the
relevant .jar file is in this directory TEPS 10
$CANDLEHOME/[architecture]/cw/classes TEPS Browser client resource files, If you
have teps support problems check if the relevant .jar files are in this
directory TEPS Browser Client 11 $CANDLEHOME/tables/[tems name] Location for
historical data collection files if the collection is enabled on TEMS level TEMS
12 $CANDLEHOME/[architecture]/[agentcode]/hist Location for historical data
collection files if the collection is enabled on TEMA level TEMA 13
$CANDLEHOME/tmaitm6/agentdepot Latest installation logs. This directory keeps
details of the latest ITM product installation ALL 14
$CANDLEHOME/[architecture]/cw/classes/candle/[agencode]/resources/advice/[lang]
Location for Expert Advice HTML files TEPS

Sharing is caring!
 * Tweet
 * Share
 * Pin
 * Mail
 * Share

This entry was posted in IBM Tivoli Monitoring 6 and tagged directories, ITM,
TEMS, TEPS on 2009/10/20 by admin.


HOW TO FORCE ITM AGENTS TO SPECIFIC NETWORK ADAPTERS WHEN USING HACMP

Leave a reply

When you install ITM agents on a HACMP solution you need to make sure that the
OS agents are running on both Physical nodes and the application agents are
running on the active one. The application agent has to be installed on the
shared volume group so when a takeover happens it moves with the application.
The OS agents to the local filesystem on the physical nodes this way you have
both nodes ( Active/Passive ) monitored.

After installation you have to modify the monitoring agent’s .ini file that is
located in the [itmroot]/config directory. For example if you try to configure
the Unix OS Agent you need to modify the ux.ini.

Set/Modify the following values:

KDEB_INTERFACELIST=!10.10.10.1 This instructs the product to bind to ONLY the
10.10.10.1 interface
attached to the system and publish IP address 10.10.10.1 for the Tivoli service.

CTIRA_HOSTNAME=[hostname]
CTIRA_SYSTEM_NAME=[hostname]

Repeat this step for all agents in scope then restart the agents and after a
while they should show up on the TEPS Console under the correct hostname.

References:

http://www-01.ibm.com/support/docview.wss?uid=swg21328735

Sharing is caring!
 * Tweet
 * Share
 * Pin
 * Mail
 * Share

This entry was posted in IBM Tivoli Monitoring 6 and tagged AIX, HACMP, ITM on
2009/10/14 by admin.


POST NAVIGATION


Newer posts →
Search for:



CATEGORIES

 * AIX
 * Appdynamics
 * azure
 * bash
 * CentOS
 * DB2
 * Django
 * Gitlab
 * Google Base
 * GraphQL
 * IBM Monitoring 8
 * IBM Tivoli Monitoring 6
 * Integration Composer
 * iRedMail
 * Jazz SM
 * Kubernetes
 * Magento 2
 * MS SQL Server
 * MySql
 * Omnibus
 * openshift
 * Our Work
 * perl
 * PHP
 * phpLDAPadmin
 * Pipelines
 * Postfix
 * Prestashop
 * PRTG
 * Python
 * SCOM
 * SLES
 * SmartCloud Control Desk
 * Splunk
 * Suse 64
 * TADDM
 * terraform
 * Tivoli Common Reporting
 * Ubuntu
 * Uncategorized
 * VPS
 * Windows 7 64 Bit
 * wordpress
 * WSL
 * Zabbix


OUR WEBSITES

 * cooksandtravels.com
 * www.tivolispecialist.com





RECENT COMMENTS

 * InfoP1 on How to install Zabbix Proxy on Windows?
 * InfoP1 on How to install Zabbix Proxy on Windows?
 * Laszlo on How to install Zabbix Proxy on Windows?
 * Ľuboš Komorník on mariadb.service: Start operation timed out. Terminating.
 * Frans Streur on Installing IBM Tivoli Monitoring 6.3.0.3 on CentOS 7


TAGS

 * AIX
 * Appdynamics
 * azure
 * bash
 * CentOS
 * DB2
 * Django
 * Gitlab
 * Google Base
 * GraphQL
 * IBM Monitoring 8
 * IBM Tivoli Monitoring 6
 * Integration Composer
 * iRedMail
 * Jazz SM
 * Kubernetes
 * Magento 2
 * MS SQL Server
 * MySql
 * Omnibus
 * openshift
 * Our Work
 * perl
 * PHP
 * phpLDAPadmin
 * Pipelines
 * Postfix
 * Prestashop
 * PRTG
 * Python
 * SCOM
 * SLES
 * SmartCloud Control Desk
 * Splunk
 * Suse 64
 * TADDM
 * terraform
 * Tivoli Common Reporting
 * Ubuntu
 * Uncategorized
 * VPS
 * Windows 7 64 Bit
 * wordpress
 * WSL
 * Zabbix


Proudly powered by WordPress