Index
A B C D E H I J L M O P R S T U W
A
- Active Data Cache
-
- not starting after initial Oracle Business Activity Monitoring installations, 4.9.1
- running on the same host with the Oracle database, 4.10.2
- security measures, 3.12.5
- Active Data Cache Server
-
- system requirements, 1.3.2
- ADCAutomaticallyAddUsers key
-
- configuring, 3.12.8
- ADCMaxThreadPoolWorkerThread key
-
- configuring, 3.12.9
- ADCMaxViewSetRowCount
-
- configuring, 3.12.6
- Administrator group
-
- required for choosing a Windows account for the services, 2.2.1
- alert history
-
- writing to the Event Log, 3.12.4
- alerting
-
- enabling, 2.4.5
- Application Event Log
-
- clearing when full, 4.8.1.2
- Architect
-
- starting, 2.4.2
B
- BAMSecureServerKey
-
- configuring, 3.12.5
- batch processing
-
- configuration, 3.12.15
C
- client system
-
- system requirements, 1.4
- clustering services
-
- enabling for Active Data Cache, 2.4.6
- configuration
-
- ADCMaxViewSetRowCount, 3.12.6
- adjusting plan monitor settings, 3.12.10
- BAMSecureServerKey, 3.12.5
- batch processing, 3.12.15
- changing culture codes for different locales, 3.12.14
- changing the Windows locale after installation, 3.12.13
- completing after installation, 2.4.2
- disabling the automatic addition of domain users, 3.12.8
- ensuring that same account is used for all services, 2.4.2
- ensuring that there is an Enterprise Link user with the required rights, 2.4.2
- EventEngineAlertHistoryEventLogging, 3.12.4
- HTTP protocol, 3.12.11
- increasing the record limit for e-mail, 3.12.7
- increasing the server thread pools for more users, 3.12.9
- location of configuration files, 3.12
- of performance, 3.2
- OracleBAMActiveDataCache.exe.config file, 3.12.6
- PlanMonitor.ClearJournalOnStart, 3.12.10
- PlanMonitor.PlanChangeDetectFrequency, 3.12.10
- PlanMonitor.StatusInterval, 3.12.10
- requirements, 2.2
- setting the ADCMaxThreadPoolWorkerThread key, 3.12.9
- setting the ReportCacheMaxThreadPoolWorkerThread key, 3.12.9
- starting Architect, 2.4.2
- Windows Server 2003 requirements, 2.4.1
- culture codes
-
- changing for different locales, 3.12.14
D
- Data Flow Plans
-
- creating and running, 2.4.2
- Data Flow Service
-
- make note of settings prior to deinstallation, 2.1, 3.5, 3.7, 3.7
- terminated, 4.8.1.1
- deinstallation, 3.7
- domain users
-
- disabling the automatic addition of, 3.12.8
E
- e-mail
-
- increasing the record limit for e-mail, 3.12.7
- Enterprise Link
-
- deinstalling, 4.1.9
- ensuring there is a user with the required rights, 2.4.2
- installing, 2.3.2
- system requirements, 1.3.7
- Enterprise Link Data Flow Service
-
- one per machine permitted, 3.6.1
- Enterprise Link Repository
-
- backing up with SARPUTIL, 2.1, 3.5, 3.7, 3.7
- supported database versions, 1.3.7
- using multiple repositories with plan monitor, 3.6.7
- Enterprise Message Sources
-
- creating, 2.4.2
- event engine
-
- can connect to a single plan monitor, 3.6.5
- Event Log
-
- writing alert history to, 3.12.4
- Event Viewer
-
- changing logging settings, 2.4.3
- EventEngineAlertHistoryEventLogging
-
- configuring, 3.12.4
- Excel view type
-
- system requirements, 1.4.2.1
- external data sources
-
- connection strings, 4.5.2
- Microsoft Data Access Components (MDAC) requirement, 1.3.2
H
- HTTPS protocol
-
- configuration, 3.12.11
I
- ICommand
-
- using with multiple plan monitors, 3.6.4
- installation
-
- of multiple plan monitors, 3.6
- installing
-
- Enterprise Link, 2.3.2
- Internet Information Services, 2.2.2
- Oracle Business Activity Monitoring, 2.3
- Oracle Business Activity Monitoring Suite, 2.3.1
- overview, 2.1
- Internet Information Services, 1.3
-
- installing, 2.2.2
- manually creating the IIS virtual directory as an application, 4.1.6
- serving dynamic data on Windows 2003 Server, 4.1.4
- system requirements, 1.3.3
J
- JMS messaging credentials
-
- configuring after installation, 3.3
- jndi.properties file
-
- configuring JMS messaging credentials, 3.3
L
- logging settings
-
- changing, 2.4.3
M
- Message Center
-
- configuring to enable alerting, 2.4.5
- message queues
-
- classpath errors, 4.5.1
- Microsoft Data Access Components (MDAC)
-
- downloading, 1.3.2, 4.5.2
- required versions, 1.3.2, 4.5.2
- Morpheus.exe file
-
- error while upgrading, 4.1.10
- updating data in the Active Data Cache from version to version, 4.1.10
O
- Oracle BAM services
-
- starting, 2.4.2, 2.4.3
- Oracle Data Access Client
-
- location on Oracle Business Activity Monitoring software CD-ROM, 1.3.2
- required version, 1.3.2
- Oracle database
-
- installation procedures, 1.3.8
- location of installation documentation, 1.3.7, 1.3.8
- running on the same host with the Active Data Cache, 4.10.2
- system requirements, 1.3.8
- Oracle External Data Objects
-
- troubleshooting errors, 4.5.3
- Oracle homes
-
- multiple Oracle homes on your system, 4.1.1
- Oracle Outlook Connector
-
- troubleshooting errors, 4.8.2
- OracleBAMActiveDataCache.exe.config
-
- configuring, 3.12.5
- OracleBAMActiveDataCache.exe.config file
-
- configuring, 3.12.6
- setting the ADCMaxThreadPoolWorkerThread key, 3.12.9
- OracleBAMEventEngine.exe.config file
-
- configuring, 3.12.4
- configuring HTTPS protocol, 3.12.11
- OracleBAMPlanMonitor.exe.config
-
- adjusting settings for plan monitor behavior, 3.12.10
- OracleBAMPlanMonitor.exe.config file
-
- configuring plan monitors on multiple hosts, 3.6.8
- setting controls to clear the journal at startup, 3.12.10
- setting the number of times the plan monitor checks running plans before looking for changes, 3.12.10
- OracleBAMReportCache.exe.config
-
- setting the, 3.12.9
P
- patches
-
- downloading, 3.1
- performance
-
- configuration steps, 3.2
- improving, 3.2
- plan monitor
-
- adjusting settings, 3.12.10
- client configuration file settings, 3.6.11
- configuration file entries, 3.6.10
- editing the monitoring settings of plans, 3.6.3
- establishing connections to, 3.6.2
- event engine can connect to a single plan monitor, 3.6.5
- installing multiple plan monitors, 3.6
- installing multiple plan monitors on a single host, 3.6.9
- installing on multiple hosts, 3.6.8
- setting change detection, 3.6.6
- uses and restrictions of multiple plan monitors, 3.6
- using ICommand with multiple plan monitors, 3.6.4
- using multiple Enterprise Link repositories, 3.6.7
- PlanMonitor.ClearJournalOnStart
-
- configuration, 3.12.10
- PlanMonitor.PlanChangeDetectFrequency
-
- configuration, 3.12.10
- PlanMonitor.StatusInterval
-
- configuring, 3.12.10
R
- RecordsLimitForEmail key
-
- configuring, 3.12.7
- ReportCacheMaxThreadPoolWorkerThread key
-
- configuring, 3.12.9
- reports
-
- upgrading from a previous release, 3.5.1
- requirements
-
- for choosing a Windows account for the services, 2.2.1
S
- Sadcagnt.exe.config file
-
- configuring batch processing, 3.12.15
- SARPUTIL
-
- documentation on using for backups, 2.1, 3.5, 3.7
- for backing up Enterprise Link Repository, 2.1, 3.5, 3.7, 3.7
- server thread pools
-
- increasing for more users, 3.12.9
- services
-
- choosing a Windows account, 2.2.1
- choosing a Windows account for the services, 2.2.1
- ensuring that same user account is used for all services, 2.4.2
- starting, 2.4.3
- system requirements, 1.3
-
- Active Data Cache Server, 1.3.2
- client system, 1.4
- Enterprise Link, 1.3.7
- Excel view type, 1.4.2.1
- Internet Information Services, 1.3.3
- Oracle database, 1.3.8
- Web Applications host, 1.3.3
T
- troubleshooting
-
- Active Data Cache service does not start, 4.9.1
- Application Event Log is full, 4.8.1.2
- Data Flow Service terminated, 4.8.1.1
- deinstalling Enterprise Link, 4.1.9
- enabling Internet Information Services to serve dynamic data, 4.1.4
- error during Morpheus.exe upgrade operation, 4.1.10
- errors when running many simultaneous plans, 4.11.1
- external data source connection strings and errors, 4.5.2
- manually creating the IIS virtual directory as an application, 4.1.6
- message queue classpath errors, 4.5.1
- multiple Oracle homes, 4.1.1
- Oracle External Data Object errors, 4.5.3
- Oracle Outlook Connector errors, 4.8.2
- running the Oracle database and Active Data Cache on the same host, 4.10.2
U
- upgrading
-
- Oracle Business Activity Monitoring components, 3.5
- reports from a previous version, 3.5.1
- user accounts
-
- ensuring that same account is used for all Oracle Business Activity Monitoring services, 2.4.2
W
- Web applications
-
- starting, 2.4.4
- Web Applications host
-
- system requirements, 1.3.3
- Web.config file
-
- changing culture codes for different locales, 3.12.14
- configuring the HTTPS protocol, 3.12.11
- increasing the RecordsLimitForEmail key, 3.12.7
- location of, 3.12.7
- setting the ADCAutomaticallyAddUsers key, 3.12.8
- Windows 2003 Server
-
- serving dynamic data on Internet Information Services, 4.1.4
- Windows locale
-
- changing after installation, 3.12.13
- Windows Server 2003
-
- configuration requirements, 2.4.1
- Oracle Business Activity Monitoring configuration requirements, 2.4.1