The entire architecture we have discussed is typically referred to as an Enterprise
Service Bus.
Enterprise Service Bus (ESB) is a standard-based middleware architecture
that allows pluggable components to communicate with each other via a
messaging subsystem.
Now that we have a basic understanding of what a Service Engine is, how
communication is made between application clients and Service Engines, and
between Service Engines themselves, let's take a look at what support the NetBeans
IDE gives us for interacting with Service Engines.
Service Engine Life Cycle
Each Service Engine can exist in one of a set of predefined states. This is called the
Service Engine life cycle.
Started
Stopped
Shutdown
Uninstalled
The figure below gives an overview of the life cycle of Service Engines:
????????????
Service Engines
[ 32 ]
Service Engines can be managed from the command line utility, asadmin, that is
supplied as part of the Sun Java System Application Server. The table below shows
some of the common commands that can be used to manage Service Engines:
asadmin list-jbiservice-
engines
Obtains a list of installed Service Engines
$>./asadmin list-jbi-service-engines
sun-aspect-engine
sun-bpel-engine
sun-dtel-engine
sun-etl-engine
sun-iep-engine
sun-javaee-engine
sun-script-engine
sun-sql-engine
sun-wlm-engine
sun-xslt-engine
Command list-jbi-service-engines executed
successfully.
Pages:
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53