Sun Microsystems 820433510 BindingComponents, JBIComponent Loggers

BindingComponents
BindingComponents are proxies for consumers or providers that are outside the JBI
environment.Binding components typically are based on a standard communications protocol,
suchas FTP,JMS, or SMTP, or a call to an external service, such as SAP or WebSphere MQ.
JBIcomponents have the following lifecyle states:
■Started
■Stopped
■Shutdown
TheJBI Runtime persists the life cycle states of JBI Components. When the server shuts down
andthen restarts, JBI Components revert to their state at the time the Enterprise Server shut
down.
Note– The JBI runtime attempts to revert to the "desired"state of a JBI component. For
example,suppose you tried to start a JBI component but it did not start due to an error in the
component.If you restart the Enterprise Server, the JBI runtime attempts to start the
componentagain.
Youcan do the following operations on the JBI components. For detailed steps, log on to the
AdminConsole, navigate to the JBI node, click Components and then click Online Help.
■ViewJBI components by their specic lifestyle states.
■InstallJBI components.
■UninstallJBI components.
■Managethe lifecycle states of the JBI Components.
■Viewthe general properties of a JBI Component.
■Viewthe conguration information for a JBI Component.
■Viewthe descriptor for a JBI Component.
■ManageJBI Component Loggers.
JBIComponent Loggers
Usingthe Admin Console, you can manage the log levels for JBI Components. Some JBI
Componentsprovide several loggers while other components might not provide any. However,
therewill always be a logger level displayed for the entire component. But the logger level
settingwill only have an eect if a component implements its loggers based on the default name.
Theprovider of a JBI Component might provide additional documentation on specifying
logginglevels.
JBIEnvironment
SunGlassFishEnterprise Ser ver2.1 Administration Guide • December 200840