A DeploymentRequestTaskRuntimeMBean provides a container for tasks that collaborate on a DeploymentService request. These are typically a task tracking the application of a configuration change and one or more tasks that involve deployment [application or system resource] actions. This interface provides an overall status of the deployment request progress. Details such as the completion of the task are however dependent on the completion of the subtasks. DeploymentService requests are handled in 2 phases. The first phase - the 'prepare' phase, involves the validation of the request on each target server. Any failure encountered in this validation results in the failure of the overall request. If all targets validate the request properly, the request is considered to be successful and the admin server triggers the 2nd phase - the 'commit . Note that the 'commit' is triggered at the point when the admin server has already determined the request to be successful even though it has not yet completed.
Parsed from file BEA-WEBLOGIC-MIB.mib.txt
Company: None
Module: BEA-WEBLOGIC-MIB
A DeploymentRequestTaskRuntimeMBean provides a container for tasks that collaborate on a DeploymentService request. These are typically a task tracking the application of a configuration change and one or more tasks that involve deployment [application or system resource] actions. This interface provides an overall status of the deployment request progress. Details such as the completion of the task are however dependent on the completion of the subtasks. DeploymentService requests are handled in 2 phases. The first phase - the 'prepare' phase, involves the validation of the request on each target server. Any failure encountered in this validation results in the failure of the overall request. If all targets validate the request properly, the request is considered to be successful and the admin server triggers the 2nd phase - the 'commit . Note that the 'commit' is triggered at the point when the admin server has already determined the request to be successful even though it has not yet completed.
Parsed from file BEA-WEBLOGIC-MIB.mib
Module: BEA-WEBLOGIC-MIB
Vendor: Independence Technologies, Inc.(ITI)
Module: BEA-WEBLOGIC-MIB
[Automatically extracted from oidview.com]
deploymentRequestTaskRuntimeTable OBJECT-TYPE SYNTAX SEQUENCE OF DeploymentRequestTaskRuntimeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A DeploymentRequestTaskRuntimeMBean provides a container for tasks that collaborate on a DeploymentService request. These are typically a task tracking the application of a configuration change and one or more tasks that involve deployment [application or system resource] actions. This interface provides an overall status of the deployment request progress. Details such as the completion of the task are however dependent on the completion of the subtasks. DeploymentService requests are handled in 2 phases. The first phase - the 'prepare' phase, involves the validation of the request on each target server. Any failure encountered in this validation results in the failure of the overall request. If all targets validate the request properly, the request is considered to be successful and the admin server triggers the 2nd phase - the 'commit . Note that the 'commit' is triggered at the point when the admin server has already determined the request to be successful even though it has not yet completed." ::= { wls 1215 }
deploymentRequestTaskRuntimeTable OBJECT-TYPE SYNTAX SEQUENCE OF DeploymentRequestTaskRuntimeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A DeploymentRequestTaskRuntimeMBean provides a container for tasks that collaborate on a DeploymentService request. These are typically a task tracking the application of a configuration change and one or more tasks that involve deployment [application or system resource] actions. This interface provides an overall status of the deployment request progress. Details such as the completion of the task are however dependent on the completion of the subtasks. DeploymentService requests are handled in 2 phases. The first phase - the 'prepare' phase, involves the validation of the request on each target server. Any failure encountered in this validation results in the failure of the overall request. If all targets validate the request properly, the request is considered to be successful and the admin server triggers the 2nd phase - the 'commit . Note that the 'commit' is triggered at the point when the admin server has already determined the request to be successful even though it has not yet completed." ::= { wls 1215 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.140.625.1215.1 | deploymentRequestTaskRuntimeEntry | 10 | 10 | Generated SNMP Table Entry. |
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.140.625.1165 | webServiceTable | 1 | 10 | Encapsulates information about a Web Service configuration. Deprecation of MBeanHome and Type-Safe Interfaces This is a type-… |
| 1.3.6.1.4.1.140.625.1170 | webserviceCredentialProviderTable | 1 | 7 | Encapsulates information about a particular credential provider that has been configured for a Web Service security configurati… |
| 1.3.6.1.4.1.140.625.1175 | webserviceSecurityTable | 1 | 8 | Encapsulates information about a Web Service security configuration. Deprecation of MBeanHome and Type-Safe Interfaces This i… |
| 1.3.6.1.4.1.140.625.1180 | webserviceSecurityTokenTable | 1 | 7 | Encapsulates information about a particular token that has been configured for a Web Service security configuration. Deprecati… |
| 1.3.6.1.4.1.140.625.1185 | webserviceTimestampTable | 1 | 11 | Encapsulates the timestamp information that is associated with a Web Service security configuration. Deprecation of MBeanHome … |
| 1.3.6.1.4.1.140.625.1190 | webserviceTokenHandlerTable | 1 | 8 | Encapsulates information about a particular token handler that has been configured for a Web Service security configuration. D… |
| 1.3.6.1.4.1.140.625.1195 | workManagerTable | 1 | 7 | Configuration MBean representing WorkManager parameters. A WorkManager configuration can have a RequestClass(FairShare, Respons… |
| 1.3.6.1.4.1.140.625.1200 | workManagerShutdownTriggerTable | 1 | 7 | This MBean is used to configure the trigger that shuts down the WorkManager. The trigger specifies the number of threads that n… |
| 1.3.6.1.4.1.140.625.1205 | appClientComponentRuntimeTable | 1 | 7 | This is the ComponentRuntimeMBean for J2EE Application Client Containers. Deprecation of MBeanHome and Type-Safe Interfaces T… |
| 1.3.6.1.4.1.140.625.1210 | appRuntimeStateRuntimeTable | 1 | 5 | Provides access to runtime state for deployed applications. |
| 1.3.6.1.4.1.140.625.1220 | entityEJBRuntimeTable | 1 | 6 | This interface contains accessor methods for all EJB runtime information collected for an Entity Bean. Deprecation of MBeanHom… |
| 1.3.6.1.4.1.140.625.1225 | jdbcDataSourceTaskRuntimeTable | 1 | 11 | None |
| 1.3.6.1.4.1.140.625.1230 | jdbcDriverRuntimeTable | 1 | 5 | This class maps to a JDBCDriver JMO Deprecation of MBeanHome and Type-Safe Interfaces This is a type-safe interface for a Web… |
| 1.3.6.1.4.1.140.625.1235 | jdbcMultiDataSourceRuntimeTable | 1 | 5 | This class is used for monitoring a WebLogic JDBC Multi Data Source and its associated data sources. |
| 1.3.6.1.4.1.140.625.1240 | jdbcServiceRuntimeTable | 1 | 5 | This class is used for monitoring a WebLogic JDBC service. It maps to a JDBCResource JMO. Deprecation of MBeanHome and Type-Sa… |
| 1.3.6.1.4.1.140.625.1245 | jmsRemoteEndpointRuntimeTable | 1 | 25 | This class is used for monitoring a WebLogic SAF remote endpoint for a JMS imported destination. Deprecation of MBeanHome and … |
| 1.3.6.1.4.1.140.625.1250 | jobRuntimeTable | 1 | 11 | RuntimeMBean that provides information about a particular job. |
| 1.3.6.1.4.1.140.625.1255 | jobSchedulerRuntimeTable | 1 | 5 | RuntimeMBean that provides information about jobs scheduled with the Job Scheduler. |
| 1.3.6.1.4.1.140.625.1260 | kodoDataCacheRuntimeTable | 1 | 10 | Base class for all runtime mbeans that provide status of running modules. Deprecation of MBeanHome and Type-Safe Interfaces T… |
| 1.3.6.1.4.1.140.625.1265 | kodoPersistenceUnitRuntimeTable | 1 | 6 | Base class for all runtime mbeans that provide status of running modules. Deprecation of MBeanHome and Type-Safe Interfaces … |
| ... | ||||