13 Life Cycle of Processing Servers and Signaling Servers

This chapter describes how to manage the life cycle of Processing Servers and Signaling Servers.

Processing and Signaling Server Life Cycle

Oracle Communications Service Controller has life cycle states and transitions, as illustrated in Figure 13-1. The life cycle begins when Service Controller starts. OSGi defines a life cycle and Service Controller defines an overlay life cycle based on OSGi.

The life cycle is triggered when a server is started.

Figure 13-1 shows Service Controller states and transitions.

Figure 13-1 States and State Transitions

Table 13-1 describes the OSGi states and state transitions, and gives information on the corresponding OSGi start levels.

Table 13-1 OSGi Start Levels, Service Controller States, and State Transitions

State	Transition	Description
SHUTDOWN	N/A	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	N/A	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: During server startup. That is, before entering state SAFE MODE from state initial. During this transition, the running OSGi bundles are shut down. Errors are logged. During server shutdown. That is, before entering state initial from state SAFE MODE. This state transition is triggered by management operations. If any error occurs during this transition, the transition is rolled back and the server retains state SAFE MODE.
RUNNING	N/A	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 MBeans

Life cycle management can be done using MBeans.The following sections provide reference information for the life cycle management of MBeans.

ManagementAgentMBean

Using ManagementAgentMBean, you can perform lifecycle management of a server though JMX. See "Processing and Signaling Server Life Cycle".

JAR File

oracle.axia.platform.managementagent-version.jar

where version is the version number of the JAR file: for example, 1.0.0.0.

Package

oracle.axia.api.management.agent

Object Name

oracle:type=oracle.axia.api.management.agent.ManagementAgentMBean

Factory Method

Created automatically.

Attributes

int StartLevel

Read only.

Specifies the start level.

Operations

void forceShutdown()

Forces the server to transition to state SHUTDOWN.

void goToRunningLevel()

Transitions the server to state RUNNING.

void goToSafeLevel()

Transitions the server to state SAFE MODE.

boolean hasReachedSafeLevel()

Returns true if the server has reached start level SAFE MODE, otherwise false.

boolean serverIsRunning()

Returns true if the server has reached state RUNNING, otherwise false.

void shutdown()

Transitions the server to state SHUTDOWN.