Index Changes

Difference between version and version     

Back to Component Configuration, or Component Configuration Info


At line 3 added 13 lines.
!!Rules to Minimize data type mismatch problems
Runtime Management and Monitoring MBeans will only use data types that can be expressed unambiguously through an XML-Schema.
That means, only use a set of basic data types that can be marshaled and unmarshaled in a platform and programming language-neutral manner for attributes, operation parameters and return types.
These data types include:
* Primitive types (int, long, boolean, etc.),
* Primitive wrapper classes (Integer, Long, Boolean, etc.) - http://java.sun.com/j2se/1.5.0/docs/api/javax/management/openmbean/OpenType.html#ALLOWED_CLASSNAMES,
* Enumeration classes (Enum),
* Classes that define a mechanism to convert from an input CompositeData class to an instance of that class.
* List and Map types are supported as long as the contained objects are primitive types, primitive wrapper classes, enumerations, or a class supporting CompositeData conversion.
The above guidelines follow the same restrictions imposed by the new MXBeans (http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/ManagementFactory.html#MXBean), a new kind of MBeans introduced in J2SE 5.0 which do exactly this to minimize data type mismatch problems.
At line 4 changed 2 lines.
!! Enterprise Manager Runtime Configuration and Installer MBeans
Sun __Installer Extension MBeans__ should have names of the format:\\
----
!! Runtime Configuration and Installer MBeans
__Installer Extension MBeans__ should have names of the format:\\
At line 10 changed 1 line.
Similarly, Sun __Runtime configuration MBeans__ should have names of the format:\\
Similarly, __Runtime configuration MBeans__ should have names of the format:\\
At line 31 added 10 lines.
!!Object Naming
A valid ObjectName will be of the form:
SUN_EBI_DOMAIN:\\
SERVICE_TYPE=SERVICE_TYPE_NAME,\\
INSTALLATION_TYPE=INSTALLATION_TYPE_NAME,\\
IDENTIFICATION_NAME_TYPE=IDENTIFICATION_NAME\\
Where:\\
SUN_ EBI_DOMAIN is com.sun.ebi
At line 42 added 27 lines.
SERVICE_TYPE is ServiceType
SERVICE_TYPE_NAME will have one of the following values:
# Status
# Configuration
INSTALLATION_TYPE is InstallationType
INSTALLATION_TYPE_NAME will have one of the following values:
# bindingComponents
# serviceEngines
# sharedLibraries
# serviceAssemblies
IDENTIFICATION_NAME_TYPE is IdentificationName
IDENTIFICATION_NAME will have the Identification Name of the installed JBI component (ServiceEngine or Binding Component or Shared Library or Service Assembly)
Examples of valid ObjectNames
* An MBean that allows configuration changes at runtime for a Binding Component type with an Identification Name stchttpsoap-b393-4f54-aaad-9294ae9c5a23 will be:
com.sun.ebi:ServiceType=Configuration,InstallationType=bindingComponents,IdentificationName=stchttpsoap-b393-4f54-aaad-9294ae9c5a23
* An MBean that provides Status updates at runtime for a Service Engine type with an Identification Name bpelserviceengine-9bfbff60-467d-11d9-9669-0800200c9a66 will be:
com.sun.ebi:ServiceType=Status,InstallationType=serviceEngines,IdentificationName=bpelserviceengine-9bfbff60-467d-11d9-9669-0800200c9a66
At line 261 added 1 line.
Back to [CAM]

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-8) was last changed on 26-Jun-07 18:47 PM, -0700 by Gopalan Suresh Raj