지금 지원 담당자와 채팅
지원 담당자와 채팅

SharePlex Manager 3.0 - User Guide

Ignoring Events

You can configure SharePlex Manager to ignore clearable events that automatically trigger warning and error notifications but which do not otherwise affect performance. Ignoring an event does not remove it from the status database or keep it from being written to the event log file; it only alters the way the data is presented to the user in SharePlex Manager.

After ignoring an event, you can enable it again at any time.

To ignore an event, select its corresponding checkbox and click Ignore Events. Ignored events are indicated in the Event Level column by the status “Ignored.” To enable an ignored event, select its corresponding checkbox and click Enable Ignored Events.

Appendix: Starting SharePlex Web Services

Contents 
Overview
Windows
Linux
 

 

Overview

SharePlex Web Services must be running to monitor your SharePlex instances. On Windows, SharePlex Web Services starts automatically at reboot. On Linux, you can start SharePlex Web Services manually, or you can configure it to start at reboot.

Note
Before starting SharePlex Web Services, be aware of the following:
•
It is not recommended that you start multiple instances of SharePlex Web Services on different ports using the same installation. You should only run one instance of SharePlex Web Services at a time.
•
Occasionally you may receive an error message that SharePlex Web Services is not available at the specified port. This may be because SharePlex Web Services is down, or it may be because SharePlex Web Services is running but not responding. In either case, you should make sure SharePlex Web Services is not running by executing a stop command before executing a start command. If you execute a stop command when SharePlex Web Services is already stopped you will receive an error message which you can safely ignore.
Windows

As a Windows NT service, SharePlex Web Services is configured to start automatically when the machine reboots. However, if it is necessary to start SharePlex Web Services manually (for example, due to a port conflict), you can start it manually in two ways:

•
By going to the Start menu and selecting All Programs>Quest Software>SharePlex Manager>Start SharePlex Web Services.
Note
To stop SharePlex Web Services, select the Stop SharePlex Web Services option
•
By executing the command web-services start from the web-services.bat file located in the <install_dir>\Webservices\bin directory.
The commands are:
web-services start
Note
To stop SharePlex Web Services, execute the command web-services stop.
Linux

After the installation is complete, you can start SharePlex Web Services manually, or you can configure it to start at reboot.

1
To start SharePlex Web Services manually on Linux, execute the following command:
sh <install_dir>/Webservices/bin/web-services.sh start
Note
To stop SharePlex Web Services for Linux, execute
sh <install_dir>/Webservices/bin/web-services.sh stop. For Windows, close the window it is running in.
If started successfully, SharePlex Web Services writes log entries to the console that indicate it's running. For example:
$ sh ./bin/web-services.sh start
Activated on port 3000: <process entry from ps>
2
To configure SharePlex Web Services to start at reboot, do the following:
a
Create the file /etc/init.d/spo-web-services with the following content (assumes that Java is installed in the default <install_dir>/jre directory and the SharePlex Web Services is installed in <install_dir>/Webservices/bin):
#!/bin/sh
JAVA_HOME=<install_dir>/jre
PATH=/bin:/usr/bin:/usr/local/bin
export JAVA_HOME PATH
sh <install_dir>/Webservices/bin/web-services.sh "${@}"
#!/bin/bash
#
# SharePlex for Oracle Web Services
#
# chkconfig: 35 <start priority> <stop priority>
# description: SharePlex for Oracle Web Services
JAVA_HOME=<install_dir>/jre
PATH=/bin:/usr/bin:/usr/local/bin
export JAVA_HOME PATH
sh <install_dir>/Webservices/bin/web-services.sh "${@}"
Replace <install_dir> with the directory for the installation of SharePlex Manager.
Note
Unless there is a good reason to the contrary, the <endpriority> should be equal to 100 minus <startpriority>. <startpriority> is the “priority” weight for starting the service, while <endpriority> is the “priority” weight for stopping the service. Services are started and stopped in numerical order starting at 0, e.g., 90 for <startpriority> and 10 for <endpriority>.
Replace <start priority> and <stop priority> with
b
Use the chkconfig command to configure the script to start at boot
[root@hostname dir]# /sbin/chkconfig --level 35 spo-web-services on
c
Verify the installation with
[root@hostname dir]# service spo-web-services status
SharePlex Web Services is configured to start on next reboot.

 

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택