Oracle Fusion Middleware extensions for Logging and Diagnostic
11g Release 1 (11.1.1.6)

E22565-06

oracle.apps.fnd.appltest.diagfwk.mbean.internal
Class DiagTestExecutorMXBeanImpl

java.lang.Object
  extended by oracle.apps.fnd.appltest.diagfwk.mbean.internal.DiagTestExecutorMXBeanImpl
All Implemented Interfaces:
DiagTestExecutorMXBean

public class DiagTestExecutorMXBeanImpl
extends java.lang.Object
implements DiagTestExecutorMXBean

Implementation of the Diagnostics Executor MBean

Since:
release specific (what release of product did this appear in)
Version:
$Header: atgpf/appltest/applications/Diagnostics/TestExecutor/src/oracle/apps/fnd/appltest/diagfwk/mbean/internal/DiagTestExecutorMXBeanImpl.java /main/13 2010/09/10 17:10:17 ilawler Exp $
Author:
Oracle

Constructor Summary
DiagTestExecutorMXBeanImpl()
          Default Constructor
DiagTestExecutorMXBeanImpl(java.lang.String jpsPolicyContextId)
          Constructor for when the web app where this MBean is registered has declared which jps policy context ID to use, not requiring is to look it up later using the costly pillar APIs.
 
Method Summary
 java.util.Map<java.lang.String,java.lang.String> executeTests(java.lang.String pRunId, java.util.List<java.lang.String> pTestNames, java.util.Map<java.lang.String,java.util.Map<java.lang.String,java.lang.String>> pParameters, java.util.Map<java.lang.String,java.lang.String> pUserContext, java.util.Map<java.lang.String,java.lang.String> pRunParams)
          Executes one or more Diagnostic Tests with the given name and under the given run ID and with the given list of parameters.
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

DiagTestExecutorMXBeanImpl

public DiagTestExecutorMXBeanImpl()
Default Constructor


DiagTestExecutorMXBeanImpl

public DiagTestExecutorMXBeanImpl(java.lang.String jpsPolicyContextId)
Constructor for when the web app where this MBean is registered has declared which jps policy context ID to use, not requiring is to look it up later using the costly pillar APIs.

Parameters:
jpsPolicyContextId -
Method Detail

executeTests

public java.util.Map<java.lang.String,java.lang.String> executeTests(java.lang.String pRunId,
                                                                     java.util.List<java.lang.String> pTestNames,
                                                                     java.util.Map<java.lang.String,java.util.Map<java.lang.String,java.lang.String>> pParameters,
                                                                     java.util.Map<java.lang.String,java.lang.String> pUserContext,
                                                                     java.util.Map<java.lang.String,java.lang.String> pRunParams)
Description copied from interface: DiagTestExecutorMXBean
Executes one or more Diagnostic Tests with the given name and under the given run ID and with the given list of parameters.

The tests are kicked off asynchronously and the API returns an execution ID that tracks the test execution.

The list of parameters also contains any user context related parameters that might be required in order to initialize a user session in the JMX Thread prior to invocation of the test.

Specified by:
executeTests in interface DiagTestExecutorMXBean
Parameters:
pRunId - - ID of the Run under which this test should be executed
pTestNames - - Fully qualified list of test names to be executed.
pParameters - - Input parameters for each test keyed by the test name.
pUserContext - - User context related parameters such as user guid, role guid that would be required to set an Applications context in the JMX thread during execution of the mbean.
pRunParams - - Run parameters to use for invocation in worker mode
Returns:
- A map of execution GUIDs for each specified test name (keyed by the test name)

Oracle Fusion Middleware extensions for Logging and Diagnostic
11g Release 1 (11.1.1.6)

E22565-06

Copyright © 2012 Oracle. All Rights Reserved.