3 Starting and Stopping IP Service Activator

This chapter explains how to start and stop Oracle Communications IP Service Activator.

Starting IP Service Activator Components

This section describes how to start the naming service, component manager, and user interface. This can be done from the shell.

The IP Service Activator system start-up procedure requires components to be started in the following order:

Start the Naming Service
Start the Component Managers controlling the installed Policy Server, Proxy Agent, Measurement Component, Event Handler, and OIM components
Start the User Interface

IP Service Activator does not start if the naming service is not running, and any installed system component that does not have its component manager up and running is not available to the system. The exception is the user interface component, which does not require the component manager to be installed or running on its host machine.

During the installation, if you chose to run the naming service and component manager as services, they are started in the correct order on system reboot. You must perform this manual startup whenever you reboot the host.

Note:

It is advisable to change to the /opt/OracleCommunications/ServiceActivator/bin directory before starting or stopping components.

Starting the Naming Service

If you chose not to run the naming service as a service that is started automatically on reboot, it must be started manually.

Note:

Only the IP Service Activator administrator can start and stop the naming service.

To start the naming service from the shell:

Log in as the IP Service Activator administrator.
Type the following command:
```
$ ./ipsans start
```

This starts the naming service in the background. Logging information is recorded in /opt/OracleCommunications/ServiceActivator/logs/ipsans.log

To check whether the naming service is running:

Run the ipsaps script:
```
$ ipsaps
```

For more information about the ipsaps script, see "Running Troubleshooting Scripts".

Starting the Component Manager

If you chose not to run the component manager as a service that is started automatically on reboot it must be started and stopped manually.

Note:

Only the IP Service Activator administrator can start and stop the component manager.

The naming service must be running before you can start the component manager.

To start the component manager from the shell:

Enter the following commands:

/opt/OracleCommunications/ServiceActivator/bin
$ ./ipsacm start

This starts the component manager in the background, logging information is recorded in /opt/OracleCommunications/ServiceActivator/logs/ipsacm.log

To check whether the component manager is running:

Run the ipsaps script:
```
$ ipsaps
```

For more information about the ipsaps script, see "Running Troubleshooting Scripts".

To see error output:

Type:

$ tail -f /opt/OracleCommunications/ServiceActivator/logs/ipsacm.log

To exit the log file, press Ctrl+C.

IP Service Activator Fast Start Mode

After system startup, the device drivers are in fast start mode. This means that no configurations are sent to the devices from the device drivers. The required configurations are subsequently sent when the device gets a second commit or after a pre-determined timeout period. The second commit, which is measured since the Proxy Server and device driver startup, can also be forced by invoking a script.

Forcing the exit of fast start mode can be helpful during upgrade testing. See the IP Service Activator Installation Guide for information about upgrading IP Service Activator.

Starting the Windows-based User Interface

Note:

The naming service and component manager must be running before you can start the user interface.

To start the user interface:

From the Start Menu select Start, select Programs, select Oracle- Oracle Communications, select Service Activator, and then select User Interface.

Stopping IP Service Activator Components

This section describes how to stop the user interface, component manager, and naming service. (Stopping the component manager stops other IP Service Activator components running on the same host machine.)

These activities can be performed from the shell.

Stopping the Windows-based User Interface

From the main menu, select File, and then select Exit to shut down the user interface on the Windows host.

Stopping the Component Manager

If you chose not to run the component manager as a service that is started automatically on reboot it must be started and stopped manually.

Note:

Only the IP Service Activator administrator can start and stop the component manager.

The naming service must be running before you can start the component manager.

To stop the component manager from the shell:

Log in as the IP Service Activator administrator.
Enter the following command:
```
$ ./ipsacm stop
```

This stops the component manager.

To check whether the component manager is running:

Run the ipsaps script:
```
$ ipsaps
```

For more information about the ipsaps script, see "Running Troubleshooting Scripts".

To see error output:

Enter:

$ tail -f /opt/OracleCommunications/ServiceActivator/logs/ipsacm.log

To exit the log file, press Ctrl+C.

Stopping the Naming Service

If you chose not to run the naming service as a service that is started automatically on reboot it must be started and stopped manually.

Note:

Only the IP Service Activator administrator can start and stop the naming service.

To stop the naming service from the shell:

Log in as the IP Service Activator administrator.
Type the following command:
```
$ ./ipsans stop
```

This stops the naming service.

To check whether the naming service is running:

Run the ipsaps script:
```
$ ipsaps
```

For more information about the ipsaps script, see "Running Troubleshooting Scripts".

To see error output:

Type:

$ tail -f /opt/OracleCommunications/ServiceActivator/logs/ipsans.log

To exit the log file, press Ctrl+C.