Oracle® Communications Service Broker System Administrator's Guide Release 6.0 Part Number E23523-02 |
|
|
View PDF |
This chapter describes how to manage the life cycle of Processing Servers and Signaling Servers.
Oracle Communications Service Broker has life cycle states and transitions, as illustrated in Figure 17-1. The life cycle begins when Service Broker starts. OSGi defines a life cycle and Service Broker defines an overlay life cycle based on OSGi.
The life cycle is triggered when a server is started.
Figure 17-1 shows Service Broker states and transitions.
Table 17-1 describes the OSGi states and state transitions, and gives information on the corresponding OSGi start levels.
Table 17-1 OSGi Start Levels, Service Broker States, and State Transitions
State | Transition | Description |
---|---|---|
SHUTDOWN |
Initial state. The server is not running. Corresponds to OSGi start level 0. |
|
SHUTDOWN |
start |
This state transition is triggered by the server start script. Safe services are started. See "System Administrator's Reference" for details. Corresponds to OSGi start levels 0 to (SAFE MODE -1). If any error occurs during this transition, the OSGi framework shuts down. |
SAFE MODE |
The server can be managed on OSGi level and is running with a minimal set of OSGi bundles. Corresponds to OSGi start levels SAFE MODE to (RUNNING -1). Traffic is not processed and there is no interaction between Processing Servers and Signaling Servers. |
|
SAFE MODE |
resume |
This state transition is triggered by the server start script and by management operations. The server transitions into state RUNNING. |
SAFE MODE |
shutdown |
Two scenarios are possible:
|
RUNNING |
When entering this state, all modules transition into state RUNNING. |
|
RUNNING |
suspend |
This state transition is triggered by management operations and the server transitions into SAFE MODE. |
RUNNING |
shutdown |
This state transition is triggered by management operations. During this transition, the server automatically continues with shutting down all running OSGi bundles. |
Life cycle management can be done using MBeans.The following sections provide reference information for the life cycle management of MBeans.
Using ManagementAgentMBean, you can perform lifecycle management of a server though JMX. See "Life Cycle".
oracle.axia.platform.managementagent-version.jar
where version is the version number of the JAR file: for example, 1.0.0.0.
oracle.axia.api.management.agent
oracle:type=oracle.axia.api.management.agent.ManagementAgentMBean
Created automatically.
Read only.
Specifies the start level.
Forces the server to transition to state SHUTDOWN.
Transitions the server to state RUNNING.
Transitions the server to state SAFE MODE.
Returns true if the server has reached start level SAFE MODE, otherwise false.
Returns true if the server has reached state RUNNING, otherwise false.
Transitions the server to state SHUTDOWN.