Example: Using a Java Program to Scale Out to Servers

Introducing the Oracle BI Systems Management API 22-25 print file, Start Metric Dump of: + strmetric_table + : + strmetric_ of_interest + for Category: + strcategory_of_interest + at + strSimpleDateFormatdd-MMM-yyyy HH-mm-ss.formatDate counter = 0 while counter = sample_length: results = displayMetricTablesmetric_table for table in results: name = table.getTable rows = table.getRows rowCollection = rows.values iter = rowCollection.iterator while iter.hasNext: row = iter.next if row.containsValuecategory_of_interest: rowType = row.getCompositeType keys = rowType.keySet keyIter = keys.iterator while keyIter.hasNext: columnName = keyIter.next value = row.getcolumnName if columnName == metric_of_interest: print file, strSimpleDateFormatdd-MMM-yyyy HH-mm-ss-SSS.formatDate + , + strvalue counter = counter + 1 file.close disconnect

22.4 Descriptions of JMX Admin MBeans and Methods for the Oracle BI Systems Management API

This section lists the JMX Admin MBeans of the Oracle BI Systems Management API that you use to perform system administration tasks using WLST scripts and Java programs. Your code must reference Admin MBeans and their attributes and methods. This section lists the Admin MBeans. The JavaDoc pages describe the attributes and methods that are available for each Admin MBean. For example, display the JavaDoc files in a Web browser and click the Admin MBean EmailConfigurationMBean. You see all related attributes and methods, and you can then use the correct attribute and method names in WLST scripts or Java programs. See the JavaDoc file that is located in the following directory: ORACLE_HOMEdocjavadocbifoundationjmxapiindex.html Table 22–1 lists the JMX Admin MBeans for the Oracle BI Systems Management API. Table 22–1 Oracle BI Systems Management API JMX Admin MBeans Admin MBean Description AvailabilityConfigurationMBean Provides an MBean interface for configuring several options that affect process availability for Oracle Business Intelligence. BIComponentMBean Defines an MBean interface for a component of a BI domain. BIDomainMBean Defines an MBean interface for managing a BI domain. 22-26 System Administrators Guide for Oracle Business Intelligence Enterprise Edition You can also use the MBean Browser to access Admin MBeans. For information, see Section 2.4, Managing Oracle Business Intelligence JMX MBeans Using the Fusion Middleware Control MBean Browser. BIInstanceDeploymentMBean Defines an MBean interface to describe the deployment provisioning of system components to an Oracle instance. BIInstanceMBean Defines an MBean interface for managing system components. BILogConfigurationMBean Defines an MBean interface for managing Oracle Business Intelligence log file settings and levels. BISizeAgeLogConfigurationMBean Defines an MBean interface for managing query log file settings. EmailConfigurationMBean Defines an MBean interface for managing the email configuration of system components. MarketingConfigurationMBean Defines an MBean interface for managing the marketing configuration of system components. OracleInstanceMBean Defines an MBean interface for managing an Oracle instance. PerformanceConfigurationMBean Defines an MBean interface for managing the performance configuration of system components. PresentationConfigurationMBean Defines an MBean interface for managing the presentation configuration of system components. PresentationServerConfigurationM Bean Defines an MBean interface for managing the configuration of Presentation Services. ScaleOutSupportMBean Provides operations to support scaling out a domain. SchedulerDatabaseMBean Defines an MBean interface for managing Scheduler database connection settings. SecurityConfigurationMBean Defines an MBean interface for managing the centralized security configuration of system components. ServerConfigurationMBean Defines an MBean interface for managing settings related to the Oracle BI Server. Table 22–1 Cont. Oracle BI Systems Management API JMX Admin MBeans Admin MBean Description Part VIII Part VIII Managing the Life Cycle This part describes life cycle management tasks for Oracle Business Intelligence. Life cycle management consists of installing, upgrading, patching, moving to a new environment, moving to a production environment, and backing up and recovering systems. For information about installation, see Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence. For information about upgrade, see Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence. This part includes the following chapters on life-cycle management tasks: ■ Chapter 23, Patching Oracle Business Intelligence Systems ■ Chapter 24, Moving Between Environments ■ Chapter 25, Backup and Recovery of Oracle Business Intelligence Systems 23 Patching Oracle Business Intelligence Systems 23-1 23 Patching Oracle Business Intelligence Systems Patching involves copying a small collection of files over an existing installation. A patch is normally associated with a particular version of an Oracle product and involves updating from one minor version of the product to a newer minor version of the same product for example, from version 11.1.1.2.0 to version 11.1.1.3.0. A patch set is a single patch that contains a collection of patches that are designed to be applied at the same time. For more information, see Oracle Fusion Middleware Patching Guide. This chapter includes the following topics: ■ Section 23.1, What Is Patched for the Oracle Business Intelligence Platform? ■ Section 23.2, Patching the Platform ■ Section 23.3, Rolling Back a Platform Patch ■ Section 23.4, Determining Current Patch Levels 23.1 What Is Patched for the Oracle Business Intelligence Platform? Oracle Business Intelligence platform patching applies patches for binary files with extensions such as DLL, JAR, and EXE. Oracle Business Intelligence platform patching does not patch the following: ■ Configuration Files If configuration updates are required as part of a patch, then these are detailed in the accompanying README.txt file, and you must manually apply them. No automated mechanism is available for merging customer configuration and patched configuration files. ■ Schema-based Metadata Nondesign-time metadata that is stored in database schemas including schemas for the Scheduler, usage statistics, event polling, repository files, and the Oracle BI Presentation Catalog is not patched. Other platform metadata such as repository files and Oracle BI Presentation Catalog files that are delivered in the context of an application are patched, but as part of an applications patch and not as part of a platform patch.