Tivoli Integrated Portal
Questions about TIP? Use our Message Board to post questions.
Comments about TIP? Use our Message Board to post your comments.
Is there a single sign on available between Impact 5.1.1 and WebGUI 7.3.0?
How to integrate operator view from Impact 5.1.1 and WebGUI 7.3.0? I would like to launch Impact operator view from AEL event of WebGUI.
Vasanth Kumar Kodi 0600011J0W 129 Views
Taking example from this logs:
- The last good request, using sessionID=00001FR_6ne65N2pHeqt7amvvU9:
network: Connecting https://xyz.com/ibm/console/webtop/EventDataService?top-nCompatible=true&rowidconsumer=true&applysort=false&filtertype=global&filterowner=global&filtername=Yoigo_CORE_LTE&viewtype=global&viewname=YOIGO_Supervision&datasources=AGG_K1&commands=×tamp=AGG_K1:1445324280 with proxy=DIRECT
- The first failure (one minute interval for AEL refresh time), using the sessionID=0000XDfOf2h-iGX8F0xfKmVZJWR redirect to invalidationSession.jsp:
- The first W0025 message using the failure sessionID:
Looking at the session id changed on next refresh, high possibly the cookies still having multiple session ids, or new user logged in on the same browser.
Clear all browser cache and always log out from the session to avoid another user to the same browser session
Yazhini K Murugesan 270003TACD 174 Views
When an installation fails due to WAS FP issue, we may need to check .nifregistry file. The location of the .nifregistry file varies per operating system:
Yazhini K Murugesan 270003TACD 158 Views
When customer upgrades TIP/product version and after the upgrade,if the version info in TIP welcome page and components.xml show the old versions but the listIU shows the current upgraded version, then there is a possibility that the upgrade might not be successful. But, DE might have the entry of product/TIP from the previous failed install attempt and the rollback after install failure might have not happened and that wrong product/TIP version entry might exist in DE registry.
An example scenario:
WEBGUI 188.8.131.52 installation attempt was done.
Looking through IBM_Tivoli_Netcool_OMNIbus_Web_GUI_FP6_Install-00.log, the first WEBGUI 184.108.40.206 install attempt was made on 2013-11-05 13:10:25.733+01:00. However there are error messages such as:
2013-11-05 13:17:50.280+01:00 : FINE : MachinePlanEventOccurred(An exception was received during the processing of MachinePlan: localhost. See the Exception Stack Trace for more information.) (from com.ibm.ac.coi.ext.ia.COIWrapperPluginImpl.eventOccurred)
2013-11-05 13:17:51.000+01:00 : FINE : Exception via callback from DeploymentPlanProcessor.process(INSTALL): (from com.ibm.ac.coi.ext.ia.COIWrapperPluginImpl.install)
such that the installer exited with code -1:
2013-11-05 13:17:54.599+01:00 : STDERR : Exiting with exit code: -1
There was another installation attempt on 2013-11-05 13:41:35.594+01:00. There are indications that the FP6 installation step was skipped
2013-11-05 13:43:33.314+01:00 : FINEST : LogicalComponentInstance(WebtopInstallFP_LC).addVariable(Webtop-FP6,skip); (from com.ibm.ac.coi.ext.ia.COIWrapperPluginImpl.addVariableToAllLCs)
presumably because at that point DE already had a record of 220.127.116.11 from the previous failed installation attempt and the rollback didn't happen properly.
Cross-checking with SystemErr.log,
[11/5/13 17:06:08:776 CET] 00000008 SystemErr R System Information:
i.e., the server was started up after the two 18.104.22.168 installation attempts, and the above shows that the installed code is still 22.214.171.124.
1. Take the backup of the following:
/usr/ibm/common/acsi/bin/manage_iu.cmd -o undo -r <product home> -d RootIUTypeID[<The RootIUTypeID of the product entry which you want to remove>,<product version>]
3. Re-run the install.
Yazhini K Murugesan 270003TACD 167 Views
Steps to copy fixed WEB-INF xml files to servers which are in a cluster:
1. Stop all servers that are in the cluster
To remove the last server from the cluster, use the following command:
Likewise, if you want to upgrade servers in a cluster:
1. Stop all servers
2. Disjoin all servers from the cluster
3. Upgrade servers separately
4. Join the servers back to cluster
5. Start all servers.
Yazhini K Murugesan 270003TACD 188 Views
Run the following command from <TIPHOME>/bin/ha
If this returns list of modules, then HA is configured and the server is joined
Yazhini K Murugesan 270003TACD 200 Views
Database Maintenance Mode
To determine if the system is currently in maintenance mode
If the GLOBAL_LOCK value is '0' the system is NOT in maintenance mode otherwise a '1' would indicate maintenance mode is enabled.
To properly remove or obtain maintenance mode
where obtain puts the server in maintenance mode and release takes it out of maintenance mode.
Yazhini K Murugesan 270003TACD 183 Views
There are certain scenarios where one will need to remove a server from the load balancing configuration.
Removing a single server from a load balancing install
Removing the last server instance from a load balancing install
Note: Run this set of commands will drop the TIPDB from DB2.
If one chooses to no longer use a server within a load balancing environment, it is recommended to remove the following from <TIP_HOME>/profiles/TIPProfile/config/cells/TIPCell/nodes/TIPNode/servers/server1/resources.xml
Restart the server after removing this entry.
Yazhini K Murugesan 270003TACD 188 Views
HA/Load balancing configurations:
Creating the database:
Joining the servers to the database:
For example, if there are two servers - Server A and Server B
Verifying load balancing is working:
Yazhini K Murugesan 270003TACD 213 Views
tipcli export/import command is not used to export/import ITNM and TCR data/configurations.ITNM and TCR have their own scripts/procedures to export/import ITNM/TCR data. Hence, if customers have ITNM/TCR installed in source/target systems then ITNM and TCR plugins must be excluded during tipcli export/import .
Please find below the documentations on ITNM and TCR:
The general tipcli export/import commands are as below:
./tipcli.sh Export --username tipadmin --password <tipadmin_password> --excludePlugins TCRExportPlugins,ITNMGUI,ESSServerExportPlugin,failed_rollback,ChartExportPlugin --settingFile <product_home>/netcool/omnibus_webgui/integration/importexport_tool/etc/OMNIbusWebGUI_settings.properties
./tipcli.sh Import --username tipadmin --password <tipadmin_password> --excludePlugins TCRImportPlugins,ITNMGUI,ESSServerImportPlugin,failed_rollback,ChartImportPlugin --settingFile <product_home>/netcool/omnibus_webgui/integration/importexport_tool/etc/OMNIbusWebGUI_settings.properties
As mentioned in the above documentation,ensure you edit OMNIbusWebGUI_settings.properties file to define items correctly before you run the commands.
Vasanth Kumar Kodi 0600011J0W 256 Views
Note : This might be happening only in IE.
Follow the steps to workaround on this issue
Thanks Kishore for the steps.
Vasanth Kumar Kodi 0600011J0W 230 Views
Many a times the installation fails with server time out. The installation fails even after increasing the server start timeout. In this case please try the following
- Machineplan log may show failure at line 202 which is the failure condition for check on some ports to see if WAS server has started or not
Edit the startWAS.xml file which can be found under the cdimage.featurepack\COI\PackageSteps\StartWAS
Comment the below line
The new code should look like shown below
Once done, retry the installation and the installation should be successful
Vasanth Kumar Kodi 0600011J0W 299 Views
The user has to login twice when the session times out and redirects to TIP login page.
The recommended value should be something like this
1. ISC.KEEPALIVE.INTERVAL in consoleProperties.xml should be greater than invalidationTimeout value in deployment.xml
2. LTPA timeout value in security.xml should be greater than invalidationTimeout value in deployment.xml and also ISC.KEEPALIVE.INTERVAL in consoleProperties.xml
In short, LTPA in security.xml > ISC.KEEPALIVE.INTERVAL in consoleProperties.xml > invalidationTimeout in deployment.xml
NOTE: invalidationTimeout value in server.xml should NOT be modified and be left to default value
Location of files.
To make these changes, the nodes need to be disjoined first and update
the values in all nodes and join again else the changes will not take
Steps to disjoin and join is described here