Dbupdate
Updatedb
Dbupgrade
Upgradeui
Text searching
Full DBA rights
Maximo schema
Index tablespace
Text
Data
Exact
Wildcard
The Maximo fix pack has disabled the help functions in Maximo.
The Maximo administrator did not install the Maximo fix pack correctly.
The Maximo administrator did not update the properties for the Help application.
The Maximo administrator did not build and deploy the maximoiehs.ear file after installing the fix pack.
KPIs
Favorites
Result Sets
Quick Insert
Bulletin Board
INFO
AUDIT
ERROR
DEBUG
SEVERE
VERBOSE
Configdb
TDToolKit
Mtegrityui
CleanDatabase
Simple file sharing is disabled.
The Windows firewall is disabled.
The database server is inaccessible.
The Oracle WebLogic Server is inaccessible.
Maxinst.log
Dbconfig.log
Updatedb.log
Dropbackup.log
Restorefrombackup.log
IBM Maximo for Transportation V7.1 has been installed.
IBM Maximo for Transportation V7.1 has not been installed.
IBM Maximo Asset Management V7.5 has not been installed.
IBM Maximo Asset Management V7.1 only has been installed.
MAXIMO_HOME=
EAR_FILENAME=
BUILD_EAR_NAME=
MAXIMO PROPERTIES=
Telnet
Netstat
Portping
SOAP port utility
There is extensive tailoring to the UI
The architecture is 64-bit instead of 32-bit
Most users will be retrieving large record sets
Most users who will be on the system are self-service users
The values entered into the text fields of data forms are largely abbreviations and acronyms
Both WAS and WebLogic have configurable garbage collection schemes.
Generic JVM parameters are specified in start up scripts for WAS and in the admin console
WAS 64-bit requires less memory for JVMs than 32-bit WAS; WebLogic 32-bit and 64-bit JVMs have the same memory requirements.
To turn on garbage collection logging for WAS requires adding the -verbosegc parameter to the startup script; WebLogic requires checking a check box in the admin console.
The Maximo schema will be created and updatedb will not be executed.
The Maximo schema will not be created and updatedb will not be executed.
The Maximo schema will be created and at the end of the Maximo installation a dialog box will warn that updatedb must be run.
The Maximo schema will not be created and at the end of the Maximo installation a dialog box will warn that maxinst and updatedb must be run.
JRE V1.5
JRE V1.6
JRE V1.7
JRE V1.8
Use the RMI Checker utility
Use the netstat command
Use the wsadmin command
Use the CheckVer command
Mxe.mbo.count
Mxe.db.mboMonitor
Mxe.db.logSQLTimeLimit
Mxe.db.fetchResultLogLimit
Mxe.mbocount
Mxe.db.mboMonitor
Mxe.db.logSQLTimeLimit
Mxe.db.fetchResultLogLimit
Escalation
Workflow action
Workflow condition
Cron task definition
Communication template
Start Center result set portlet
The heap size is too large.
The heap size is too small.
The heap size is adequately sized.
It is impossible to correlate garbage collection instances to the size of the application heap.
Files from the installation source are copied to the administrative workstation during the install and si_inst_must be run manually to complete the installation.
Files from the installation source are copied to the administrative workstation during the install and updatedb must be run manually to complete the installation.
Files from the installation source are copied to the administrative workstation during the install and taskRunner must be run manually to complete the installation.
Files from the installation source are copied to the administrative workstation, taskRunner is run during the install, and the Maximo EAR file must be deployed manually to complete the installation.
Garbage collection increases user performance.
Garbage collection has no impact on user performance.
The application appears frozen during garbage collection.
. Garbage collection can only be run while the system is in admin mode.
A new Java Message Service (JMS) activation specification connected to the UIcluster.
A new Service Integration Bus must be created for the cluster.
A new sequential inbound JMS queue connected to the UIcluster.
A new continuous outbound JMS queue connected to the MIF cluster.
It uses all default values on a single system.
It allows middleware configuration values on a single system.
It uses all default values where middleware is across multiple servers.
It allows middleware configuration values where middleware is across multiple servers.
Wait!
Here's an interesting quiz for you.