ITM 6.1 Best Practices for Implementations

Transcription

1 ITM 6.1 Best Practices for Implementations John Willis

2 Agenda Introduction and Overview Panning Physical Infrastructure Logical Infrastructure Trouble Shooting Extra Stuff

3 Planning

4 Planning Project Plan Infrastructure server sizing Network topology/geography Check Lists Infrastructure servers Managed servers Staffing Initial project Maintenance Care and Feeding Development projects

5 Planning Project Plan Discovery Infrastructure Depot implementation Best practices customization OS Agent deployment UA Development and Deployment Non OS agent Dashboard Design Monitoring implantation Historical customization and implementation

6 Physical Infrastructure

7 ITM 6 Physical Infrastructure Component Definitions HTEMS, RTEMS, TEPS, WPA, SPA, RDBMS TEPS, TEP Desktop, TEP Browser Application support, Seed Files MTEMS, Starting and stopping components Architecture examples All Linux All Windows Mixed

8 ITM 6.1 Enterprise (Large) TEP Client TEP Browser TEP Client TEP Browser TEPS DB TEPS TEPS TEPS DB Aggregation & Pruning Agent (Hub) TEMS TEMS DB TDW 2.1 Warehouse Proxy Remote TEMS OS Agent Application Agent Universal Agent

9 ITM 6.1 Enterprise (Very Large) Site A Site B TEP Client TEP Browser TEP Client TEP Browser TEPS DB TEPS Aggregation & Pruning Agent TEPS TEPS DB TDW 2.1 TEMS DB (Hub) TEMS Warehouse Proxy Warehouse Proxy (Hub) TEMS TEMS DB Remote TEMS Remote TEMS OS Agent Application Agent Universal Agent OS Agent Application Agent Universal Agent

10 Legacy Terminology ITM 6.1 HUB TEMS REMOTE TEMS TEPS TEP (Desktop/Browser) TEMA ITM 5.x OS Engine Legacy Term TMR Server ManagedNode/Gateway Web Health Console (Server) Web Health Console Endpoint ITM 6.1 OS Agent ITM 5.x for xxx ITM 6.1 NON OS Agent

11 ITM 6 Physical Infrastructure General Questions Checklist How many agents to manage How many HUBS How many Remotes Agent account and authentication (root vs. non-root) TEMS OS Architecture WPA/SPA/RDMBS Architecture Dedicated file systems Agent deployment methodologies Have you ever had or do you want to use TME Endpoints

12 ITM 6 Physical Infrastructure HUB TEMS How many HUBS More than 10k Agents Total Windows or UNIX Account management Root vs. Non Root Resources Memory (no less than 2 Gig) CPU s (at least 2way) Recommendation AIX or Linux Keep agents off of the HUB

13 ITM 6 Physical Infrastructure Remote TEMS How many RTEMS No more than 1k (IBM says 1.5k) 10 RTEMS (IBM says15) Windows or UNIX Follow your HUB Resources Memory (no less than 2gig) CPU s (at least 2way) Recommendation AIX or Linux (same as HUB) Silent installs

14 ITM 6 Physical Infrastructure TEPS Typically only 1 50 simultaneous users Use SOAP and TEC to offload Run TEPS headless for Events Windows or UNIX Windows has more burn time Unix Requires DB2 Windows does not clean up well Resources Memory (no less than 2gig) CPU s (at least 2way)

15 ITM 6 Physical Infrastructure WPA How many WPA s Depending on amount of agents and locations I wouldn t run on the RTEMS (unless NAT) Windows or UNIX How hard will it be hit RDBMS local or remote Resources Memory (no less than 4gig) CPU s (at least 2way) Use OPAL Spread sheet for Disk Space Silent installs

16 ITM 6 Physical Infrastructure SPA One SPA per Multi HUB Environment Some customers run more than 1 due to amount of data they process (be careful with this) SPA and RDBMS should be on same box Silent install

17 ITM 6 Physical Infrastructure TEP Desktop vs. Browser IMHO, give power users the desktop and deal with it. Browser for the genial public Offload requirements with SOAP and TEC Java Webstart with the TEP client. Eliminate the need to patch and maintain your TEP Clients. JRE Parms -Xms1024m Xmx1024m if you are using dashboards Set in IBM/ITM/CNP/cnp.bat

18 ITM 6 Physical Infrastructure TEMA Use different directory than TEMS

19 ITM 6 Physical Infrastructure UA Don t install on every machine Set the default Data Providers at install Don t Start/Stop from the TEPS Don t set the PrimaryIP (i.e., Bind the NIC) or the MS names will be IP addresses Watch out for time outs on Scripts and situations Use display names in metafiles Watch out for TTL and keyed data (e.g., portscan)

20 ITM 6 Physical Infrastructure Physical Implementation Checklist Server names and primary IP address Use primary network address for all ITM components Protocols (TCP/IP, UDP, SSL) Port allocation (1918, 1920, 3660, 6014) Dedication file systems (/Tivoli, or /opt/tivoli) Depot location (don t use the default) Consider 2 gig for the Depot (per TEMS) At least a 1 gig for the ITM files (per TEMS) Common directories for all components Install OS and UA agents at the same time as the TEMS TEPS and WPA Servers Silent install of all infrastructure machines

21 ITM 6 Physical Infrastructure Physical Implementation Checklist Get the OS uname get the versions Get the Architectures bootinfo K get 64 or 32 for AIX isainfo b for Solaris getconf KERNEL_BITS for HP rpm -q libstdc++ grep libstdc for Linux

22 ITM 6 Physical Infrastructure Implementation Checklist TEMS on Unix is a three step process Installation Install.sh Configuration Itmcmd config S t HUB_CAPS001 Application Support itmcmd support t HUB_CAPS001 um ux lz nt sy

23 ITM 6 Physical Infrastructure Implementation Checklist Example Installation HUB first in /opt/tivoli/itm Use IP.PIPE/1918 defaults Install OS and UA at this time Name HUB_MYHOSTNAME

24 ITM 6 Physical Infrastructure STOP NOW Modify the CandleServer script # #Local change to check for another running kdsmain # if [ "$action" = "start" ] then if ps -ef grep -v grep grep kdsmain then echo "There is a KDSMAIN running already" exit fi fi

25 ITM 6 Physical Infrastructure Implementation Checklist Example Configure the HUB itmcmd config S t HUB_CAPS001 Use IP.PIPE for Protocol 1 and IP for protocol 2 Optional Primary Network Name (bind interface) Security off (until implementation is stable)

26 ITM 6 Physical Infrastructure Implementation Checklist Example Add Application Support Start the server itmcmd support t HUB_CAPS001 um ux lz nt sy Stop the server and restart Configure the RTEMS Basically the same as HUB Don t forget *REMOTE TEMS server name

27 ITM 6 Physical Infrastructure $installdir/install.sh -q -h $CANDLEHOME -p /$installdir/silent.txt which itmcmd { echo "Unable to find itmcmd in $PATH"; exit 1; } itmcmd config -S -p $installdir/silent_$type.txt -t $tems checkproc "kdsmain" && exit 1 itmcmd server start $tems itmcmd support -t $tems um ux lz nt sy itmcmd server stop $tems DEPOT=$CANDLEHOME/../depot [ -d $DEPOT ] mkdir -p $DEPOT file=`hostname`_ms_$tems.config configfile="$candlehome/config/$file" cat <<EOF >> $configfile export DEPOTHOME=$DEPOT KDS_NCSLISTEN=256 KDCFC_RXLIMIT=8192 EOF checkproc "kdsmain" && exit 1 itmcmd server start $tems [ $disablesit = "yes" ] && disablesits() exit 0

28 ITM 6 Physical Infrastructure Implementation Checklist Example Take a cold backup of all TEMS Take a backup of the TEPS DB Turn off default scripts

29 ITM 6 Physical Infrastructure listsit -n -d ","`); print "Turn off default situation processing\n"; foreach $sit (@sits) { $sitname = (split(',',$sit))[1]; next if ($sitname =~ /^CE/); next if ($sitname =~ /^UADVISOR/); print "Processing situations\n"; `tacmd editsit -s $sitname -f -p RunOnStart=NO Distribution=`; (!$?)? (print "editsit ok for $sitname") : (print "editsit failed for $ sitname",$?>>8,", "); } exit 0;

30 ITM 6 Physical Infrastructure Implementation Checklist Example TEPS on Windows Pick a drive and stick with it. Clean up on Windows is not that good Get ITMRmvall.exe from ITM support I like to get the infrastructure running and tested before I start on the TDW.

31 ITM 6 Physical Infrastructure TEPS (Windows) KfwServices.exe TEPS (Unix/Linux) KfwServices -c TEMS (Windows) kdsmain.exe, cms.exe TEMS (Unix/Linux) kdsmain, cms start WPA (Windows) khdprxto.exe WPA (Unix/Linux) khdxprtj server SPA (Windows) ksy610.exe SPA (Unix/Linux) ksy610 console

32 ITM 6 Physical Infrastructure TEMA (Unix OS Agent) kuxagent stat_daemon kux_vmstat nfs_stat Ifstat iostat

33

34 Post Configuration Setup export CANDLEHOME=/opt/Tivoli/itm export PATH=$PATH:$CANDLEHOME/bin export ITMBINDIR=/$CANDLEHOME/bin export ITMLOGS=/$CANDLEHOME/logs export ITMCONFIG=/$CANDLEHOME/config export ITMDBDIR=/$CANDLEHOME/tables/HUB_CAPS001

35 Post TEMS Configuration Files $CANDLEHOME/config ms.ini <hostname>_ms_<temsname>.config kbbenv.ini env.config $CANDLEHOME/tables/HUB_CAPS001 KBBENV

36 Post TEMS Configuration Parms KDS_NCSLISTEN is the number of active listening threads and the default is 10. This should be extended. Recommendation 256 KDCFC_RXLIMIT is the buffer used for return queries. The default is 2 meg. I am not sure what a good value is in each environment. 8 meg seems to working ok for now. Recommendation 8192 DEPOTHOME The location of the depot. The default is in $CANDLEHOME/tables/<temsname>/depot Recommendation $CANDLEHOME/../depot

37 Post TEMS Configuration Parms Bind a specific IP address KDEB_INTERFACELIST= Bind a specific hostname KDEB_INTERFACELIST=caps001 Bind the first IPV4 address associated with the current hostname to be the default interface. KDEB_INTERFACELIST=!* Use IPV4 symbolic name KDEB_INTERFACELIST=!en0

38 ITM 6 Physical Infrastructure Agent Deployment Local installs tacmd (createnode and addsystems) Software Packages Tarball Install

39 ITM 6 Physical Infrastructure Agent Deployment tacmd (createnode and addsystems) Plus Uses the depot to create image Minus Need OS account and password for createnode Need depots on every TEMS Depots need to be sync d All non OS agents get installed through the OS Agent Universal Agent meta file management Application support for UA s

40 ITM 6 Physical Infrastructure Agent Deployment Software Packages Plus Better distribution method Uses SPE authorized accounts Minus Does not use Depot to build images Need a Software Distribution product Image module names need to be built manually Might mix up dependencies Training or cross functional requirements

41 ITM 6 Physical Infrastructure Agent Deployment TarBall Installs Plus Better distribution method Uses SPE authorized accounts Uses Depot to build image Packages are ½ the size Can use wadminep or SD Can run with a single Depot Minus none

42 Post Agent Configuration Files $CANDLEHOME/config ux.ini ux.config env.config $CANDLEHOME/config/.ConfigData/kuxenv

43 ITM 6 Physical Infrastructure Agent Configuration Parms CTIRA_HOSTNAME KDCB0_HOSTNAME KDEB_INTERFACELIST CTIRA_HEARTBEAT CTIRA_RECONNECT_WAIT CTIRA_MAX_RECONNECT_TRIES

44 ITM 6 Physical Infrastructure The CTIRA_HOSTNAME is how you can set the FQDN or short name for the managed system name. For example, if the CITRA_HOSTNAME=cap001 then the managed system name will be cap001:kux. In EQRD we have made this a radio button selection to use short name or long name. This parm needs to be set in ux.ini for Unix and lz.ini for Linux. The KDCB0_HOSTNAME can be used on an agent to bind a specific interface. Here again in EQRD we have an option to use the endpoints WEP IP or DNS as a radio button selection. This parm get set in kuxenv for Unix and klzenv for Linix as PRIMARYIP.

45 ITM 6 Physical Infrastructure The CTIRA_HOSTNAME is how you can set the FQDN or short name for the managed system name. For example, if the CTIRA_HEARTBEAT is set on an agent to tell the RTEMS how long it should expect to wait for heartbeats. The default is 10 minutes. The RTEMS waits for two missed heartbeats before it marks an agent offline. This means that an agent can be offline for 20 minutes before ITM 6 knows its down. I think that is way to long. I am setting this to 3 minutes in this environment. I have seen some customers set this as low as 1 minute. Buyer beware, on this one. IBM has not really put out a clear direction on this setting. This parm needs to be set in ux.ini for Unix and lz.ini for Linux.

46 ITM 6 Physical Infrastructure The CTIRA_RECONNECT_WAIT default is 600 (10 minutes). This parm tells the agent how long to wait to try a reconnect. If an RTEMS restarts and an agent can't connect because the RTEMS is not fully initialized the agent will then wait 10 minutes. This can sometimes cause agents to show up as offline when a RTMES is recycled. If the wait interval is greater then 1800 seconds, then a failure is declared after a single wait. I am going to set this to 3 minutes in this environment. As previously mentioned --- buyer beware. This parm needs to be set in ux.ini for Unix and lz.ini for Linux. The CTIRA_MAX_RECONNECT_TRIES is how many times the agent will retry to connect to the RTEMS. The default is 720 (i.e., it will retry 6 times an hour for 5 days if you keep all the default You are probably thinking the same thing I am thinking at this point, When does it try to go to the secondary RTEMS? Since I don t have an answer for this I am going to leave this one alone for now. This parm needs to be set in ux.ini for Unix and lz.ini for Linux.

47 ITM 6 Physical Infrastructure Agent Configuration Recommendations CTIRA_HOSTNAME=short name KDEB_INTERFACELIST=!* CTIRA_HEARTBEAT =5 CTIRA_RECONNECT_WAIT=180 CTIRA_MAX_RECONNECT_TRIES=720

48 ITM 6 Physical Infrastructure Agent Configuration Issues 64 vs. 32 bit for some non OS agents MQ DB2 Space requirements for Remote deployment SP needs around 200 meg of temp space Plus agent build Tacmd needs the same Tarball needs no temp space at all

49 ITM 6 Physical Infrastructure Additional Information on capitalsoftware.com/forums Another day in the life of an ITM 6.1 implementation Demystifying ITM 6.1 Agent Configuration Files on Windows Demystifying ITM 6.1 Agent Configuration Files on Unix

50 Best Practices In my test environment I have a RTEMS called cemcp32 and another RTEMS called cemcp15. I am going to configure an agent called cemcp01. In this example I wan to make sure the name in the TEP (a.k.a the managed system name) uses the short name not the FQDN.

51 Best Practices (Unix Agents) For example cemcp01:kux not cemcp01.capitalsoftware.com:kux. The way the architecture for agent config file work is as follows. The $CANDLEHOME/config/.ConfigData/k<pc>env file defines symbolic variables to be used to process the $CANDLEHOME/config/<px>.ini file. The $CANDLEHOME/config/<px>.ini is used to build the the final output file called $CANDLEHOME/config/<px>.config. The <px>.config get regenerated when the agent is restarted. Kind of like last.cfg. In my test environment here are the three files I will use to explain this process:

52 Best Practices (Unix Agents) /opt/tivoli/itm/config/.configdata/kuxenv /opt/tivoli/itm/config/ux.ini /opt/tivoli/itm/config/ux.config

53 Best Practices (Unix Agents) kuxenv aix516 RUNNINGHOSTNAME cemcp01 aix516 SO a aix516 FTO YES aix516 CTIRA_HOSTNAME cemcp01 aix516 CTIRA_HEARTBEAT 5 ux.ini CTIRA_HOSTNAME=$EQHOSTNAME$ CTIRA_HEARTBEAT=$EQHEARTBEAT$ This creates a ux.config as follows.. CTIRA_HOSTNAME=cemcp01 CTIRA_HEARTBEAT=5

54 Best Practices (Windows Agents) [HKEY_LOCAL_MACHINE\SOFTWARE\Candle\KNT\Ver610\Primary\Environment] "CTIRA_STANDALONE"="N" "KDC_FAMILIES"="IP.PIPE PORT:1918 IP use:n SNA use:n IP.SPIPE use:n" "CTIRA_SUBSYSTEM_ID"="Primary" "CTIRA_HOSTNAME"=hex(2):25,00,63,00,6f,00,6d,00,70,00,75,00,74,00,65,00,72,0 0,\ 6e,00,61,00,6d,00,65,00,25,00,00,00 "CTIRA_NODETYPE"="NT" "CTIRA_LOG_PATH"="D:\\IBM\\ITM\\TMAITM6\\logs" "CTIRA_HIST_DIR"="D:\\IBM\\ITM\\TMAITM6\\logs" "KGL_KGLMSGBASE"="D:\\IBM\\ITM\\TMAITM6" "ATTRLIB"="D:\\IBM\\ITM\\TMAITM6\\ATTRLIB" "KNT_INTERVAL"="5" "CTIRA_SIT_PATH"="D:\\IBM\\ITM\\TMAITM6" "KDS_RATE_CACHE_SIZE"="8192" "KDS_RATE_ENABLEFIRE"="false" "CT_CMSLIST"="IP.PIPE:CAPS003" "KDE_WAPPC32"="dummy.dll"

55 Best Practices (Windows Agents) The CTIRA_HOSTNAME is hex for %computername% by default. You can change this parameter to set it to the DNS short name or FQDN to enforce consistency. If someone changes the hostname of the system inadvertently then the next time the agent recycles it will pick up the new computer name and all of the non-system based MSL s the old system was defined in won t be assumed for the newly named managed system. Even worse this could cause a gap in your Datawarehouse for this new system name and totally hose DW aggregation. IMO, I would rather this be set to the network name instead. The CTIRA_SUBSYSTEM_ID is used to set the silly prefix to all of the Windows OS names. I am not sure of what the implications of unsetting this will be but it would sure be nice to have all of my systems be in the same format. For example, If I set the "CTIRA_SUBSYSTEM_ID"="" then I my NT systems will be in the same format as my Unix system. However, I am not doing this at this point because I need to test it a lot more.

56 Best Practices (Windows Agents) caps005:nt caps002:ux

57 Best Practices (Windows Agents) The other parameter that you can set in the Windows registry is the CTIRA_HEARTBEAT. The CTIRA_HEARTBEAT can be set in the %candle_home%\tmaitm6\kntenv however if it is set in the registry the registry will override the KNTENV settings. In fact as far as I can tell the registry is the final authority for setting all env parms. Due to this fact I just set all of my default parameters in the registry so they I don t have to change it in two places. You could actually whack the registry entries and then all of the parameters would be set by KNTENV (buyer beware). That would be my preferred method but I am not sure if we should do that in EQ. For now we are using the registry.

58 Logical Infrastructure

59 ITM 6 Logical Infrastructure Components Policy based management issues Naming conventions Event Management Data Warehouse Monitoring

60 ITM 6.1 Management Issues No policy based automation for agent deployment and agent decommission. Primary and backup RTEMS server assignment for agents (i.e.,, like a select_gateway in TME). No auto migration Automated MSL assignments (i.e., like a after_install in TME). Authorization and logging of agent installs (i.e., like a allow_install in TME). No consistent best practice templates No throttle or bandwidth control

61 ITM 6.1 Management Issues ITM 6.1 no real auditing. No centralized auditing of agent installations, changes, and removals. No centralized repository for ITM 6.1 infrastructure reporting. No way to determine allocation of resource. Who, What, When

62 ITM 6.1 Management Issues Limited remote agent management No remote start/stop of OS agents. No remote configuration of OS agents. Deployment of Fix Packs can some times takes weeks to deploy. No support for automated agent migration. Trouble shooting agent problems needs to be done on the local agent. No default way to manage remote logs.

63 ITM 6.1 Management Issues Training requirements Large organizations can have 100 s of SA s that will need to be trained on how to use the TEPS and ITM 6.1 commands.

64 ITM 6 Logical Infrastructure Naming Conventions Situation Names (31 character max) MSL Names Query Names Workspace Names Universal Agent (product code names)

65 Example naming convention CE_Unix_CPUBusy_Warn (Situation) CE_Unix_DB2_Servers (MSL) CE_Unix_Processinfo (Query) CE_Unix_Processinfo (Workspace)

66 Event Management Sampled vs. Pure Edge vs. Level based monitoring Run ITM headless

67 SituationNaming Conventions Situation names Must be unique Must be 31 characters or less, Must start with an alphabetic character (a-z, A-Z) May contain any alphabetic, numeric (0-9) or underscore (_) character Must end with an alphabetic or numeric character.

68 ITM 6.1 Severities Informational Warning Critical

69 Sampled Events Sampled events Are interval driven (sampled) Interval can be customized Example: CPU usage monitored each 15 minutes, if threshold is reached -> event, Situation event will be closed automatically if in the next interval the value is below threshold

70 Pure Events Pure events Are event driven (trap,event log,...) No control over when the event happens Example: Log agent monitors a log for specific entries. So it checks the log each time the application writes to the log. Situation event are not closed automatically, have to be closed manually

71 More on Situations Persistence no holes only occurrences Create multiple situations for multiple thresholds 1020 character max Soft limit 10 attributes Situation grouping Functions in multiple row attribute groups Display Item

72 More on Situations Turn on CCC logs for TDW To keep all situation alerts in case they don t get delivered. Create a Custom workspace for Unix System. The default is not that useful for seeing what happened last night

73 ITM 6 Logical Infrastructure Event Management The sitname is prefixed by _Cri or _Warn The situation name is defined in CANDLEHOME/tables<hubtemsname>/tables /TECLIB/texserver.txt The severity is defined in the SITINFO tag in a situations XML. Only option two can use all 6 TEC severities

74 ITM 6 Logical Infrastructure Event Management If you have TEC use it for Correlation Try using the UMC for consolidation

75 ITM 6 Logical Infrastructure Data Warehouse The defaults will kill you. If you turn off Shift data you can reduce the size of your summarized tables by two thirds. Also, I am not certain of this but I don t think the OPAL spread sheet includes the 3X * Total historical size requirement for Shift data. In other words the OPAL XLS could be off by two thirds if you leave the default Shift data on. The default for hourly is 90 days. Cutting this down to 30 days reduces it by another two thirds

76 ITM 6 Logical Infrastructure Data Warehouse Turn off quarterly summarized data. Reduce the collection intervals for disk (e.g., 60 minutes) Reduce or turn off the amount of detailed retention for large multi-instance attribute groups (e.g., Unix Process 3 days). Here are some others (Linix process, Windows services, Windows Thread) Also, beware of the defaults on the OPAL projects XLS. For example on Unix disk the default number of instances is 2. On most Unix systems that number is much higher. I just did one where the average was 15 file systems per box.

77 ITM 6 Logical Infrastructure Data Warehouse Care and Feeding Higher volume than TDW 1.x Much easier to manage than the TDW 1.x. The TDW 2,x is a row based schema and not a star schema like 1.x. Only one operational database in TDW 2.x as apposed to 1.x s CDW and DMART databases. There also are no complex ETL1 and ETL2 processing in TDW 2.x.

78 ITM 6 Logical Infrastructure Data Warehouse Recommendations Run RDBMS and SPA on Unix DB2 to or Oracle

79 ITM 6 Logical Infrastructure Data Warehouse Create Scripts to check Check warehouselog Check warehouseaggregatelog Check each attribute group for agent count Check for malformed data Offload critical SLA data using SOAP calls

80 ITM 6 Logical Infrastructure Monitoring DM Classic conversion ITM 5.x Conversion or Integration Understand the architectural differences Build Logical Workspaces by Group

81 Monitoring Examples Component p an Defa ult/e nabl ed Situation Name interval Monitored State Threshold Severity Windows OS Y CE_NT_Invalid_Logon_Warn none 529 Error in security log Warning Y CE_NT_Paging_File_Warn 15 minutes Paging file percent usage 0.8 Warning Y CE_NT_Physical_Disk_Busy_Warn 15 minutes Disk time percent usage 0.9 Warning Y CE_NT_Process_CPU_Warn 15 minutes Process CPU percent busy 0.65 Warning Y CE_NT_Service_Error_Warn none Service Control Manager reports ERROR Warning Y CE_NT_System_File_Warn 15 minutes File Data Operations Warning N CE_NT_Services_Automatic_Warn 15 minutes Check autostart services running

82 Best Practices (Other Issues) Security Run w/o security until latter implantation phase Define soap users Run as root or not GSKIT IP.SPIPE vs. IP.PIPE vs. IP Encryption key USE_EGG1_FLAG=1 HTTP_SERVER:N on the KDC_FAMILIES var.. tacmd configureportalserver -s DSUSER1 -d /opt/ibm/itm -p DSN=MY_NEW_DATASOURCE UID=tivoli_user PWD=tivoli_password... Log monitoring/trimming Agents Tems WPA SPA

83 Upgrades Always backup your $CANDLEHOME Keep a copy of stub QA1 files for your UNIX TEMS Move your default $DEPOTHOME Use the tacmd to export or of your situations

84 Best Practices (Other Issues) Limited CLI and remote command support No CLI to create MSL s (Can be done with SOAP) MSL s not hierarchical No CLI to create and maintain TEP administrators No BuiltInNTAdministrator Actions run as install account Authentication (TEMS server) w/10 character limit tacmd listsystems unpredictable output

85 Best Practices (Other Issues) Managing logs Message logs Epoch time gbs100_ux_ log Trace (RAS1) HEX version of Epoch Gbs100_ms_43c6c7f7-01.log Also use hex format inside of the logs Debugging KDC_DEBUG=M KBB_RAS1=(filters)