Oracle® Communications Service Broker System Administrator's Guide Release 5.0 Part Number E15183-01 |
|
|
View PDF |
This chapter describes how to start and stop Processing Servers and Signaling Servers:
To start a Processing Server or a Signaling Server:
Log in to the physical server where your server software is installed.
Change directory to:
Oracle_home/axia/managed_server
Where Oracle_home is the Oracle Home directory you defined when you installed the product.
Enter:
./start.sh Server Domain_URI
where
Server is the server name given when you configured your domain.
Domain_URI is the URI to the domain configuration. Always include initial.zip
If your domain configuration is accessed using the Domain Web server, use the scheme http:// or https:// depending on the security settings.
If your domain configuration is accessed using a shared file system, use the scheme file://.
Example where the domain configuration is accessed using the Domain Web server:
./start.sh proc_srv_1 https://somewebserver.com:9000/initial.zip
Example where the domain configuration is accessed using a shared file system:
./start.sh proc_srv_1 file://some_directory/mydomain/initial.zip
In both cases the name of the server is proc_srv_1.
If you are using HTTPS you are prompted for the keystore password.
If you are using Basic authentication you are prompted for the user name and password combination. Use the same as when you started the domain.
To stop a Processing Server or a Signaling Server, use the Administration Console. For information on how to stop a server. See Oracle Communications Service Broker Configuration Guide.
You can also use the Scripting Engine and the MBean ManagementAgentMBean. See example below.
To connect to the SS7 network, an SS7 process needs to be started on the Signaling Servers where the SS7 SSUs are executing.
The binaries for starting the SS7 process are located in the directory:
Oracle_home/axia/managed_server/ss7stack
Where Oracle_home is the Oracle home directory.
To start the SS7 process used for connecting to the SS7 network using TDM, enter:
Linux: convergin.ss7stack.dialogic.linux port_number –src=ss7_process_module_id -sccp dialogic_sccp_module_id
Solaris: convergin.ss7stack.dialogic.solaris port_number –src=ss7_process_module_id -sccp dialogic_sccp_module_id
Where:
port_number is the port the SS7 SSU listens to messages from the SS7 process.
ss7_process_module_id is the ID that the SS7 process use to identify itself when connecting to the underlying SS7 stack.
dialogic_sccp_module_id is the identifier of the underlying SCCP module of the SS7 stack.
To start the SS7 process used for connecting to the SS7 network using SIGTRAN, enter:
Linux: convergin.ss7stack.sigtran.linux port_number
Solaris: convergin.ss7stack.sigtran.solaris port_number
Where port_number is the port the SS7 SSU listens to messages from the SS7 process.
Stop the SS7 process using operating-system commands to terminate it, for example kill.