chunk_id
stringlengths
3
7
chunk
stringlengths
1
850
source_url
stringclasses
601 values
title
stringclasses
1 value
chunk_idx
int64
0
433
chunk_start_char
int64
0
178k
chunk_end_char
int64
70
178k
66_202
The 6.3.0-TIV-ITM_LFA-FP000<n> bundles must be removed from the depot, using the "tacmd removeBundles" command.
TRAIN_Q066
202
67,160
67,272
66_203
For example: tacmd removeBundles -t lo -v 06300000<n> On UNIX systems, if the fix was expanded to <TEMP>/6.3.0-TIV-ITM_LFA-FP0002: > $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.3.0-TIV-ITM_LFA-FP0002 On Windows systems, if the fix was expanded to <TEMP>\6.3.0-TIV-ITM_LFA-FP00
TRAIN_Q066
203
67,272
67,560
66_204
02: > %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.3.0-TIV-ITM_LFA-FP0002 where: -n indicates that prerequisite bundles are not automatically added. The -n parameter must be used because the fix directory does not contain any prerequisites that the fix might require. Please see Section 3.1 for the prerequisite...
TRAIN_Q066
204
67,560
67,983
66_205
To log in to the Tivoli Enterprise Monitoring server, and deploy the fix to the appropriate nodes where the agent is running, use the following "tacmd" commands. For more information on the "tacmd login" and "tacmd updateAgent" commands, see the IBM Tivoli Monitoring Administrator's Guide.
TRAIN_Q066
205
67,983
68,275
66_206
On UNIX systems: > $CANDLEHOME/bin/tacmd login -s <server> -u <itmuser> -p <password> > $CANDLEHOME/bin/tacmd listSystems The output shows the Managed System Name for the OS agent on the remote system to be updated. Use this value as the target of the "tacmd updateAgent" command.
TRAIN_Q066
206
68,275
68,561
66_207
> $CANDLEHOME/bin/tacmd updateAgent -t lo -n <Managed system name> -v 06300200 On Windows systems: > %CANDLE_HOME%\bin\tacmd login -s <server> -u <itmuser> -p <password> > %CANDLE_HOME%\bin\tacmd listSystems The output shows the Managed System Name for the OS agent on the remote system to be updated. Use this va...
TRAIN_Q066
207
68,561
68,934
66_208
> %CANDLE_HOME%\bin\tacmd updateAgent -t LO -n <Managed system name> -v 06300200 Note: - The component (-t) for the "tacmd updateAgent" command is specified as two characters (LO), not three characters (KLO). - The node (-n) for the "tacmd updateAgent" command is the managed system name of the operating system (OS...
TRAIN_Q066
208
68,934
69,351
66_209
5.2 Agent support update ------------------------------ Fix pack 6.3.0-TIV-ITM_LFA-FP0001 included new certificates in the agent support files which need to be installed. If you have already installed these updates, there are no additional installation steps. Otherwise, install the updates to the Tivoli Enterprise ...
TRAIN_Q066
209
69,351
69,926
66_210
6.0 Additional installation information ======================== 6.1 Installation instructions for agent baroc file ----------------------------------------------------- There are no updates to the baroc files included in this fix or any of the superseded fixes. No additional installation steps are required. 6.2 Ve...
TRAIN_Q066
210
69,926
70,533
66_211
For example: On UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring installation directory, the default location is '/opt/IBM/ITM'. > $CANDLEHOME/bin/tacmd login -s <server> -u <itmuser> -p <password> > $CANDLEHOME/bin/tacmd listSystems -t LO On Windows systems, where %CANDLE_HOME% is the IBM Tivoli Mo...
TRAIN_Q066
211
70,533
70,923
66_212
> %CANDLE_HOME%\bin\tacmd login -s <server> -u <itmuser> -p <password> > %CANDLE_HOME%\bin\tacmd listSystems -t LO Note: The component (-t) for the "tacmd listSystems" command is specified as two characters (LO), not three characters (KLO). When the agent update is successful, the agent version is: 06.30.02.00...
TRAIN_Q066
212
70,923
71,346
66_213
For the agent on Windows systems, the version number is 06.30.02.00. 2.
TRAIN_Q066
213
71,346
71,422
66_214
To verify the agent you are running contains the updates from the fix, see the following lines in the agent log <hostname>_lo_<instance>_kloagent_<timestamp>.log located in $CANDLEHOME/logs on UNIX systems and %CANDLE_HOME%\tmaitm6\logs on Windows systems: <timestamp> Component: ira <timestamp> Driver: agent_fac_63:...
TRAIN_Q066
214
71,422
71,825
66_215
and workarounds ========================= None. 8.0 Additional product information ====================== None. 9.0 Copyright and trademark information ================================== A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrad...
TRAIN_Q066
215
71,825
72,189
66_216
10.0 Notices ======= INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow d...
TRAIN_Q066
216
72,189
72,832
66_217
IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Microsoft, Windows, and Windows Server are trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are t...
TRAIN_Q066
217
72,832
73,412
66_218
Other company, product, or service names may be trademarks or service marks of others. Third-Party License Terms and Conditions, Notices and Information ----------------------------------------------------------------- The license agreement for this product refers you to this file for details concerning terms and co...
TRAIN_Q066
218
73,412
74,019
66_219
Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.
TRAIN_Q066
219
74,019
74,268
66_220
Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions: - the Excluded Components are provid...
TRAIN_Q066
220
74,268
74,882
66_221
A PARTICULAR PURPOSE - IBM will not be liable to you or indemnify you for any claims related to the Excluded Components - IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components. PREREQUISITES The prerequisite level f...
TRAIN_Q066
221
74,882
75,317
66_222
As this fix is cumulative, it can be installed on any fix level for this version, release, and mod level above the prerequisite. INSTALLATION INSTRUCTIONS Please refer to the full README contained in the Download Description section above for general installation instructions. DOWNLOAD PACKAGE Download RELEAS...
TRAIN_Q066
222
75,317
75,707
66_223
[https://www.ibm.com/support/fixcentral/help?page=swfaqs] 6.3.0-TIV-ITM_LFA-FP0002 25 Sep 2017 English 1796861216 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=6.3.0-TIV-ITM_LFA-FP0002&product=ibm/Tivoli/IBM Tivoli Monitoring&source=dbluesearch&platform=All] [ ] PRODUCT ALIAS/SYNONYM
TRAIN_Q066
223
75,707
76,007
66_224
KLO log adapter [/support/docview.wss?uid=swg24043263&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24043263&aid=2]Problems (APARS) fixed IV96363, IV95005, IV93401, IV89574, IV82875, IV82170, IV81364, IV79219, IV7
TRAIN_Q066
224
76,007
76,237
66_225
9204, IV78340, IV77403, IV76731, IV76119, IV75776, IV75603, IV75336, IV74487, IV74480, IV72073, IV71539, IV68698, IV68574, IV68490, IV67737, IV67708, IV65900, IV655
TRAIN_Q066
225
76,237
76,401
66_226
00, IV64093, IV63704, IV60491, IV60331, IV60333, IV59814, IV57736, IV56299, IV54710, IV53803, IV53568, IV52833, IV52411, IV48040, IV45784, IV42745, IV42699, IV42315
TRAIN_Q066
226
76,401
76,565
66_227
, IV41215, IV39967, IV37051, IV21752
TRAIN_Q066
227
76,565
76,601
67_0
Title: IBM Rule Team Server/Decision Center is timing out while performing certain operations - United States Text: TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT) How to resolve "Transaction timed out after 601 seconds" error while performing certain operations in Rule Team Server (RTS)/Decision Center (DC)? SYMPTO...
TRAIN_Q067
0
0
508
67_1
The internal error message is: #{SelectionBean.asynchAction}: javax.faces.el.EvaluationException: java.lang.RuntimeException: java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 601 seconds BEA1-5057...
TRAIN_Q067
1
508
906
67_2
... On WebSphere: TimeoutManage I WTRN0006W: Transaction XXX has timed out after 300 seconds. TimeoutManage I WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[WebContainer : 3,5,main].
TRAIN_Q067
2
906
1,173
67_3
The stack trace of this thread when the timeout occurred was: ilog.rules.brl.parsing.parser.earley.IlrEarleyParser.errorRecovery(IlrEarleyParser.java:1046) ilog.rules.brl.parsing.parser.earley.IlrEarleyParser.buildCharts(IlrEarleyParser.java:772) ilog.rules.brl.parsing.parser.earley.IlrEarleyParser.parse(IlrEarleyPar...
TRAIN_Q067
3
1,173
1,510
67_4
CAUSE The transaction timeout for RTS/DC is set to 10 minutes by default in the teamserver web module deployment descriptor (WEB-INF/web.xml), and application servers also have container level transaction timeouts that are configurable. If a transactional operation performed by RTS/DC takes longer than these timeout...
TRAIN_Q067
4
1,510
1,911
67_5
RESOLVING THE PROBLEM If you perform time consuming operations in large repositories, you can increase the timeout value in the web.xml file of the RTS/DC EAR file (jrules-teamserver-<appserver>.ear\teamserver.war\WEB-INF) by changing the value of the property ilog.rules.teamserver.transaction.timeout.
TRAIN_Q067
5
1,911
2,218
67_6
You will find the property in the file web.xml defined as below: ... <context-param> <description>Modify the timeout value that is associated with transactions (in seconds)</description> <param-name>ilog.rules.teamserver.transaction.timeout</param-name> <param-value>600</param-value> </context-param> ... Another...
TRAIN_Q067
6
2,218
2,624
67_7
For example, for WebSphere Application Server, check the "Maximum transaction timeout" and increase it as needed as described here [http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/tjta_settlog.html]. Cross reference information Segment Product Component Platform Version ...
TRAIN_Q067
7
2,624
3,138
68_0
Title: IBM When a Certificate Authority (CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate the signature of CA on certificate. - United States Text: Datapower DP valcred SHA2 SHA-2 SHA-256 certificate trust CA TECHNOTE (FAQ) QUESTION When a Certificate Authority(CA) sign...
TRAIN_Q068
0
0
440
68_1
ANSWER Yes, if a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate CA's signature on the certificate while building trust chain from the DataPower ValCred. Cross reference information Segment Product Component Platform Version Edition Business...
TRAIN_Q068
1
440
849
69_0
Title: IBM DataPower firmware version 6.0 will enable TLS v1.2 or v1.1 by default - United States Text: ssl tsl client hello handshake fail failed version 6.0 TECHNOTE (FAQ) THIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S): English QUESTION Why would some outgoing SSL handshakes fail with firmware ...
TRAIN_Q069
0
0
456
69_1
The Crypto profiles now have TLSv1.2 and 1.1 which will be enabled by default. This affects the protocol version included in the Client Hello when DataPower is acting as the SSL client. If TLSv1.2 is not supported, the server still negotiates to the most secure supported protocol (e.g. TLSv1.1, TLSv1.0, SSLv3) if enab...
TRAIN_Q069
1
456
909
69_2
In these cases, the handshake fails without properly negotiating to a mutually agreeable protocol. The TLS versions 1.1 and 1.2 are part of the requirements for being compliant with NIST SP800-131a. ANSWER Upgrade the SSL server to a version compliant with the SSL/TLS specifications. If required you may disable TL...
TRAIN_Q069
2
909
1,296
69_3
Within the domain simply navigate to the Objects> Crypto Configuration> Crypto Profile> Then simply click on your specific profile to view the Options selection and see what SSL protocol versions are supported. Any further questions or issues please feel free to contact DataPower support. A packet trace and error ...
TRAIN_Q069
3
1,296
1,684
70_0
Title: IBM Search option for a reserved word or character in documents in Atlas - United States Text: TECHNOTE (FAQ) QUESTION How do I search for a string which has reserved words or characters when searching in documents in Atlas?
TRAIN_Q070
0
0
235
70_1
CAUSE There are specific options to use in oracle when you search for certain strings ANSWER When there is a "-" in a string you are searching for, you need to use "\" in front of the "-" For example - "String1-String2" should be searched as "String1\-String2" Please refer to the oracle documentation for Specia...
TRAIN_Q070
1
235
590
71_0
Title: IBM Verify an IEM server upgrade is still in progress - United States Text: TECHNOTE (FAQ) QUESTION How can I tell if the IBM Endpoint Manager (BigFix) server database upgrade is progressing? CAUSE When upgrading a BigFix server, most of the time is usually spent upgrading the database. The installer launc...
TRAIN_Q071
0
0
440
71_1
For some long running upgrades, it may appear that the upgrade is hung or not progressing: On Windows, the BESAdmin UI will indicate "Not Responding" if clicked on at this point. On Linux, the message "Info: Configuring the database for the server component, please wait ... " is reported. ANSWER It is important ...
TRAIN_Q071
1
440
867
71_2
To verify the upgrade is still active, check that the following process is still running: Windows: BESAdmin.exe Linux: BESAdmin CPU usage of BESAdmin may be minimal during times when the database is doing most of the work, so just the existence of the process is good confirmation. For additional confirmation, th...
TRAIN_Q071
2
867
1,350
72_0
Title: IBM PI34677: MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION - United States Text: A FIX IS AVAILABLE Fixes integrated in WebSphere Portal 8.5.0.0 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24037786] SUBSCRIBE You can track all active APARs for this component. APAR S...
TRAIN_Q072
0
0
353
72_1
ERROR DESCRIPTION * During Portal Start-Up following error is shown: -------------------- 0000005e MBeanStarter E com.ibm.wps. scripting.server.MBeanStarter loadExtensions failed to load extension: key: ServerExt.applications / value: com.ibm.wps.scripting.server.
TRAIN_Q072
1
353
657
72_2
ApplicationServerExtensions LOCAL FIX * 1) open the WAS admin console 2) navigate to Resources > Resource environment providers > WP ScriptingService > Custom properties 3) you should see an entry with the name "ServerExt.applications" and value "com.ibm.wps.scripting.server.A...
TRAIN_Q072
2
657
1,058
72_3
PROBLEM SUMMARY * A code fix for this issue is integrated into the WebSphere Portal & WCM Combined Cumulative Fix 05 (PI31198 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI31198]) for Portal 8.5.0.0 available from Fix Central: http://www-933.ibm.com/support/fixcentral/swg/se...
TRAIN_Q072
3
1,058
1,451
72_4
&release=Al [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm/WebSphere&product=ibm/WebSphere/WebSphere+Portal&release=Al] l&platform=All&function=aparId&apars=PI31198 PROBLEM CONCLUSION * Added a task to remove the outdate resource environment provider entry.
TRAIN_Q072
4
1,451
1,761
72_5
TEMPORARY FIX COMMENTS APAR INFORMATION * APAR NUMBER PI34677 * REPORTED COMPONENT NAME WEBSPHERE PORTA * REPORTED COMPONENT ID 5724E7600 * REPORTED RELEASE 850 * STATUS CLOSED PER * PE NoPE * HIPER NoHIPER * S...
TRAIN_Q072
5
1,761
2,148
72_6
10 * CLOSED DATE 2015-03-10 * LAST MODIFIED DATE 2015-03-10 * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING: * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING: FIX INFORMATION * FIXED COMPONENT NAME WEBSPHERE PORTA * FIXED COMPONENT ID ...
TRAIN_Q072
6
2,148
2,522
72_7
PSY UP
TRAIN_Q072
7
2,522
2,532
73_0
Title: IBM An unexpected ruleset version is executed - United States Text: TECHNOTE (FAQ) QUESTION Why is Rule Execution Server (RES) not executing the expected version of a ruleset ? What are the possible causes after a hot deployment for Rule Execution Server not to use the updated ruleset ?
TRAIN_Q073
0
0
298
73_1
CAUSE Possible causes for unexpected versions to be executed are: - the RES client requesting execution may be passing a wrong ruleset path - a hot deploy notification was not sent by the RES console, or not received by all the Execution Units (XU) - the ruleset parsing policy may be delaying the use of a ruleset v...
TRAIN_Q073
1
298
924
73_2
may be HTDS, MTDS, the SSP or a custom application) have been installed properly as per the documentation, see Configuring Rule Execution Server [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.config/config_ds_res/tpc_res_config.html]. The ruleset version that is executed depends fi...
TRAIN_Q073
2
924
1,286
73_3
Specifying a ruleset path with no version ( such as /MyRuleApp/MyRuleset/ ) is interpreted as a request to execute the highest version of the ruleset, as opposed to a version specific ruleset path ( such as /MyRuleApp/2.0/MyRuleset/1.0 ). Validate that the executed ruleset path is indeed unexpected considering the req...
TRAIN_Q073
3
1,286
1,763
73_4
The more frequent causes for the hot deployment not to happen as expected are: * Permission issue: the user publishing the ruleset update must have sufficient administrative rights ( Monitor role in WebSphere Application Server ) in order for the deployment to notify all the Execution Units of the ruleset update th...
TRAIN_Q073
4
1,763
2,093
73_5
For example on WebSphere Application Server see Mapping the resAdministrators group to the Monitor role [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.config/config_ds_res_was8/tsk_was_map_admin_group.html] * Version mismatch between the Execution Unit(s) and the Management Console...
TRAIN_Q073
5
2,093
2,559
73_6
For example 7.1.1.4 Management Console would not interact properly with a 7.1.1.3 Execution Unit. The version of the RES console is displayed in the "About" link (top right corner). The version of the Execution Unit can be seen in the resource adapter ra.xml file where a resourceadapter-version tag shows the version.
TRAIN_Q073
6
2,559
2,878
73_7
For example with the WebSphere Application Server this can seen through: Resources > Resource adapters > XU > Deployment Descriptor * Asynchronous ruleset parsing is used : in this mode, while an updated ruleset is being parsed, an earlier version of the ruleset can be used for executions that are requested at that ...
TRAIN_Q073
7
2,878
3,426
73_8
In order to remove any uncertainty on the version that can be executed, it is possible to either turn off the asynchronous mode [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.res.managing/topics/tsk_res_config_asynchron_turnoff.html], or force synchronous parsing in asynchronous mode...
TRAIN_Q073
8
3,426
3,888
73_9
* Notification scope is limited to one cell : by design the RES notification mechanism only works within one WebSphere Application Server Cell ( or one JBoss domain, or one Weblogic domain ), so a Management Console may only notify Execution Units that are running on servers in the same cell as the RES Console. See ...
TRAIN_Q073
9
3,888
4,317
73_10
If you need to implement notifications to several cells at once, the document Ruleset updates and programmatic notification of RES eXecution Unit [http://www-01.ibm.com/support/docview.wss?uid=swg21418646] can be useful.
TRAIN_Q073
10
4,317
4,538
73_11
* Parsing failure of an updated ruleset : leading the XU to fall back on an earlier active version that parses successfully * Ruleset update was only written to persistence: writing directly to RES persistence with the ant tasks res-write-db or res-write-file [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/...
TRAIN_Q073
11
4,538
5,023
73_12
* XU MBean is not activated in Java SE mode : See Activating the XU MBean in Java SE [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.res.managing/topics/tsk_res_config_xu_mbean_jse.html] * Multiple Java SE Execution Units are deployed in the same JVM: See Rule Execution Server J2S...
TRAIN_Q073
12
5,023
5,480
73_13
Segment Product Component Platform Version Edition Business Integration WebSphere ILOG JRules Modules:Execution Server (BRES / RES) Platform Independent 7.1.1, 7.1, 7.0.3, 7.0.2, 7.0.1, 7.0
TRAIN_Q073
13
5,480
5,670
75_0
Title: IBM Tivoli Composite Application Manager for Applications 721 FP2: Monitoring Agent for Sybase Server 620 FP2 (6.2.0-TIV-ITM_SYB-FP0002) - United States Text: Sybase Agent; OY; KOY; 5724B96SO; ITM; ITCAM DOWNLOADABLE FILES ABSTRACT This fix resolves the APARs and defects and provides the enhancements listed ...
TRAIN_Q075
0
0
358
75_1
DOWNLOAD DESCRIPTION Copyright International Business Machines Corporation 2018. All rights reserved.
TRAIN_Q075
1
358
464
75_2
Component: IBM® Tivoli® Composite Application Manager for Applications 721 FP2: Monitoring Agent for Sybase® Server 620 FP2 (6.2.0-TIV-ITM_SYB-FP0002) Fix Pack: 0002 Component ID: 5724B96SO Date: December 8, 2017 Table of contents: 1.0 General description 2.0 Problems fixed 3.0 Architecture and prerequisites 4.0 ...
TRAIN_Q075
2
464
840
75_3
.0 Additional installation information 7.0 Known problems and workarounds 8.0 Additional product information 9.0 Copyright and trademark information 10.0 Notices 1.0 General description ======================= This fix contains the APARs and defects that are specified in the "Problems fixed" section. 2.0 Problems f...
TRAIN_Q075
3
840
1,233
75_4
2.1 APARs ---------- APAR :IV95149 Abstract :While installing Sybase agent "find / -name ASE-*" command takes too long on system containing large disk and high volume mounts Additional Information: While installing Sybase agent, prereqchecker invokes the SybaseVersion_plug.sh script which executes the "find" comm...
TRAIN_Q075
4
1,233
1,691
75_5
2.2 Enhancements ---------------- RFE :86384 Abstract :Monitor availability of the Sybase backup Server, Job Server and database job failures. Additional Information: To monitor sybase backup server and job server status two new attributes were added in existing attribute group Server Details.And to monitor fai...
TRAIN_Q075
5
1,691
2,256
75_6
For information about system requirements, go to the software product compatibility reports website, and search for the ITCAM for Applications product: (http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html]).
TRAIN_Q075
6
2,256
2,561
75_7
3.1 Prerequisites for this fix ------------------------------- The minimum required version of IBM Tivoli Monitoring is V6.2.2 FP2 4.0 Image directory contents ============================== Electronic Part Number: ITCAM Apps Ag for Sybase CNN25ML The following folder structure of the image is created: 1. Sybase ...
TRAIN_Q075
7
2,561
3,086
75_8
- unix folder: This folder contains the binary files for installing the 32-bit agent on Unix platform. The folder also contains the Prereqchecker utility in the prereqchecker folder for the Sybase agent. This fix image contains the following files and directories: AUTORUN.INF [Deploy] DeployLnk.sh README.TXT [uni...
TRAIN_Q075
8
3,086
3,506
75_9
Sybase Support Installer -WINDOWS folder: This folder contains the Windows agent support files for the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Desktop client, and Tivoli Enterprise Browser client. - Unix folder: This folder contains the non-Windows agent support files ...
TRAIN_Q075
9
3,506
3,975
75_10
This fix image contains the following files and directories: AUTORUN.INF DeployLnk.sh [WINDOWS] README.TXT [unix] notices install.sh kcirunas.cfg tmv630fp6-d5334a-201511302339.appsall.tar [license] silent_install.txt silent_config.txt Note: If you are working in a UNIX environment, use install.sh file to i...
TRAIN_Q075
10
3,975
4,302
75_11
If you are working in a Windows environment, you can choose setup.exe under directory [WINDOWS] or [WIA64] according your Windows platform. 5.0 Installation instructions ============================= When this fix pack image is downloaded from the IBM Software Support Web site, these rules apply: * You can local...
TRAIN_Q075
11
4,302
4,891
75_12
* You can populate agents to the depot. * You can remotely deploy agents to existing or new installations. When this fix pack image is downloaded from Passport Advantage, these rules apply: * You can locally install the fix pack on a system that already hosts a licensed copy of IBM Tivoli Monitoring for Databases. ...
TRAIN_Q075
12
4,891
5,452
75_13
5.1 Before installing the fix ----------------------------- - The prerequisites listed under section 3.1 entitled 'Upgrade prerequisites for this fix' must be installed when for upgrade. - For the purpose of this README, the symbol <CANDLEHOME> is the IBM Tivoli Monitoring installation directory. The default valu...
TRAIN_Q075
13
5,452
5,859
75_14
- If you have customized the Monitoring Agent for Sybase Agent oy.ini file on UNIX system, this file should be backed up before the fix install. After this fix is installed, edit the latest oy.ini file and merge your modifications into this oy.ini file. 5.2 Local agent install and update (including silent instal...
TRAIN_Q075
14
5,859
6,399
75_15
For the purpose of this README, the symbol <TEMP> represents the fully qualified path to this directory. Note: On Windows, this includes the drive letter. 2. Expand the archive file using the tar command on UNIX systems or an unzip utility on Windows systems. This creates a directory structure that contains fixe...
TRAIN_Q075
15
6,399
6,884
75_16
Use the procedures in the specific database monitoring agent user's guide to complete the installation and configuration. 5. After agent upgrade bitness of agent binary should be same as pre-upgrade on x86-64 bit windows. Agent do not support upgrade to 64 bit binary. 5.3 Remote agent update and installation -----...
TRAIN_Q075
16
6,884
7,387
75_17
For the purpose of this README, the symbol <TEMP> represents the fully qualified path to this directory. Note: On Windows, this includes the drive letter. 2. Expand the archive file using the tar command on UNIX systems or an unzip utility on Windows systems. This creates a directory structure that contains fixes ...
TRAIN_Q075
17
7,387
7,930
75_18
For more information on the tacmd addBundles command, see Appendix A. Commands reference of the "IBM Tivoli Monitoring Administrator's Guide."
TRAIN_Q075
18
7,930
8,073
75_19
On a UNIX system: if the fix was expanded to <TEMP>/CNN25ML: > $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/CNN25ML/WINDOWS/Deploy -t oy -f > $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/CNN25ML/unix -t oy -f where: -i is the directory that contains the deployment bundles to be added to the depot.
TRAIN_Q075
19
8,073
8,372
75_20
-t is the product code of the product to add, in this case or represents the Monitoring Agent for Sybase Agent -f performs the actions without asking for confirmation On a Windows system: if the fix was expanded to <TEMP>/CNN25ML: > %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\CNN25ML\WINDOWS\Deploy -t oy -f > %CAN...
TRAIN_Q075
20
8,372
8,797
75_21
the deployment bundles to be added to the depot. -t is the product code of the product to add, in this case oy represents the Monitoring Agent for Sybase Agent -f performs the actions without asking for confirmation 5. To log in to the Tivoli Enterprise Monitoring server, and deploy the fix to the appropriate nodes...
TRAIN_Q075
21
8,797
9,334
75_22
On a UNIX system: > $CANDLEHOME/bin/tacmd login -s <server> -u <itmuser> -p <password> > $CANDLEHOME/bin/tacmd listSystems The output shows the managed system name for the OS agent on the remote system to be updated. Use this value as the target of the tacmd updateAgent command.
TRAIN_Q075
22
9,334
9,620
75_23
> $CANDLEHOME/bin/tacmd updateAgent -t oy -n <Managed system name> -v 062002000 On a Windows system: > %CANDLE_HOME%\bin\tacmd login -s <server> -u <itmuser> -p <password> > %CANDLE_HOME%/bin/tacmd listSystems The output shows the managed system name for the OS agent on the remote system to be updated. Use thi...
TRAIN_Q075
23
9,620
9,995
75_24
> %CANDLE_HOME%\bin\tacmd updateAgent -t OY -n <Managed system name> -v 062002000 If there are not prior version koy agent on remote system .Then use below tacmd addSystem command. > %CANDLE_HOME%\bin\tacmd addSystem -t OY -n <Managed system name> -p INSTANCE="<Sybase instance name>" Note: - The <Sybase insta...
TRAIN_Q075
24
9,995
10,393
75_25
- The component (-t) for the updateAgent command is specified as two characters (oy), not three characters (koy). - The node (-n) for the updateAgent command is the managed system name of the operating system (OS) agent to be updated. The target node for an updateAgent command is always an OS agent. -Remote installa...
TRAIN_Q075
25
10,393
10,777
75_26
5.4 Agent support update ------------------------ Use the following steps to update the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, or Tivoli Enterprise Portal Desktop: 1. Transfer the appropriate archive file (CNN25ML.tar.gz or .iso) to the IBM Tivoli Enterprise Monitoring Servers, IBM T...
TRAIN_Q075
26
10,777
11,279
75_27
Use the procedures in the "ITCAM for Applications, Version 7.2.1.2 Installation and Setup Guide." 4. Use the procedures in the specific database monitoring agent user's guide to complete the installation and configuration. 5. If the Tivoli Enterprise Monitoring Server being updated is remote (not a Hub Tivoli Enter...
TRAIN_Q075
27
11,279
11,678
75_28
6.0 Additional installation information ======================================= 6.1 Verifying the update ------------------------- 1.To verify whether the agent is updated correctly, use the tacmd command to view the current version of the agent after the agent is restarted. Ensure that you log on to the Tivoli Ent...
TRAIN_Q075
28
11,678
12,198
75_29
> $CANDLEHOME/bin/tacmd login -s <server> -u <itmuser> -p <password> > $CANDLEHOME/bin/tacmd listSystems -t OY On Windows systems, where %CANDLE_HOME% is the IBM Tivoli Monitoring installation directory, the default location is C:\IBM\ITM.
TRAIN_Q075
29
12,198
12,441
75_30
> %CANDLE_HOME%\bin\tacmd login -s <server> -u <itmuser> -p <password> > %CANDLE_HOME%\bin\tacmd listSystems -t OY Note: The component (-t) for the tacmd listSystems command is specified as two characters (OY), not three characters (KOY). When the agent is updated, the agent version is changed to 06.20.02.00. Afte...
TRAIN_Q075
30
12,441
12,852
75_31
For the agent on Windows systems, the version number is 06.20.02.00. 2.To verify whether the agent support files are updated correctly, use the kincinfo command on Windows systems or the cinfo command on Linux or UNIX systems.
TRAIN_Q075
31
12,852
13,080
75_32
On UNIX or Linux systems: To validate that all components have been installed, run the following command: $CANDLEHOME/bin/cinfo -i Sample output for the cinfo command on a UNIX or Linux systems ---------------------------------------------------------- [root@HJS-SYB-1 bin]# ./cinfo *********** Wed Nov 29 23:53:13 I...
TRAIN_Q075
32
13,080
13,510