Lotus Domino Administrator 8 Help - Creating Server probes

MONITORING

Creating Server probes
1. From the IBM® Lotus® Domino™ Administrator, click the Files tab.

2. Open the Monitoring Configuration database.

3. Choose DDM Configuration.

4. Choose any DDM probe view, and then click New DDM Probe.

5. Choose Server.

6. Complete these fields:

Field Action

Probe Subtype Choose one:

Administration
WebSphere Services

Probe Description Type a description of the new probe.

Which servers should run this probe? Choose one:

All servers in the domain -- Runs the probe on all servers in the domain.
Special target servers -- Specify the type of servers to run the probe, such as POP3 servers or the administration server for the Domino Directory.
Only the following servers -- Specify the servers on which the Server probe will run.

Administration Requests Choose the administration requests that are to be reported in DDM when the request fails to run on the servers you selected.

Severity Choose the severity that will generate an error.

Target WebSphere Server Name Specify the fully-qualified host name or IP address of the WebSphere server to be monitored by the probe.

Port Numbers Specify the port numbers of the ports you are monitoring to determine if protocol requests are being processed for WebSphere services. You can use setting with or without the autodiscovery feature enabled in the field below. The default setting 80.

Autodiscover WebSphere Ports Select this option if you want the probe to automatically discover the ports that are to be monitored based on the application name. The application name is specified in the Target WebSphere Application field.

SOAP Connector Address The Simple Object Access Protocol (SOAP) Connector Address is the protocol used to connect Domino to the remote WebSphere Application Server (WAS). To find the SOAP connector address on the remote WebSphere Application Server, connect to the WebSphere Integrated Solutions Console and go to Server -- Application Servers -- Server name -- Ports -- SOAP Connector Address. Specify the port number in this SOAP Connector Address field.

Target WebSphere Application Specify the applications that you want to monitor on a remote WebSphere server. The probe will determine which WebSphere ports need to be active for the application to run properly. The probe monitors these ports and generates an event if the port becomes inactive.

Administrative security is enabled Select this option if administrative security is enabled on the WebSphere Integrated Solution Console. Domino requires this information for connection purposes.

Websphere Integrated Solution Console User ID Specify the administrative User ID for the WebSphere Integrated Solution Console so that Domino can authenticate and make the remote connection to WAS.

WebSphere Integrated Solution Console Password Specify the administrative password for the WebSphere Integrated Solution Console.

7. Complete these fields on the Schedule tab:

Field Action

How often should this probe run? Choose one:

Run multiple times per day -- The probe runs more than once each day. Causes the "Defined schedule" field to display.
Daily -- The probe runs once each day. Use the "On which days should this probe run" field to specify the days on which the probe is run.
Weekly -- The probe runs once each week. Use the "On which day of the week should this probe run?" field to specify the day on which the probe is run.
Monthly -- The probe runs once each month. Use the "On which day of the month should this probe run" field to specify when the probe should run.

Defined schedule Specify the number of minutes between each run of the probe.

Should this probe run twenty four hours per day, seven days per week? Choose one:

Yes -- Run the probe continuously.
No -- The probe runs on the days and at the times that you specify.

During which hours of the day should this probe run? Specify the start time in the From field, and the end time in the To field. The probe will run during those hours.

On which days should this probe run? Choose the days on which to run the probe.

On which day of the week should this probe run? Specify the day of the week on which to run this probe.

On which day of the month should this probe run? Specify the day of the month on which to run this probe. For example, enter 15 to run the probe on the 15th day of the month.

At what time should this probe run? Specify the time that you want the probe to run.

How should missed probes be handled? Choose one:

Ignore missed probe -- The missed probe is not run or rescheduled.
Run missed probe on startup -- The next time that the server starts, the missed probe runs.
Run missed probe at next time range -- The missed probe reschedules itself once. For example, if a probe scheduled to run every Tuesday at 5:00 AM fails to run, the probe reschedules itself to run on Wednesday at 5:00 AM. After that, the probe returns to its regular schedule.

For information about the individual administration requests, see this topic Administration process requests.

See also

Server probes

DDM probes

Maintaining DDM Probes

Glossary

Feedback on Help or Product Usability?

Help on Help

All Help Contents

Glossary

Field	Action
Probe Subtype	Choose one: Administration WebSphere Services
Probe Description	Type a description of the new probe.
Which servers should run this probe?	Choose one: All servers in the domain -- Runs the probe on all servers in the domain. Special target servers -- Specify the type of servers to run the probe, such as POP3 servers or the administration server for the Domino Directory. Only the following servers -- Specify the servers on which the Server probe will run.
Administration Requests	Choose the administration requests that are to be reported in DDM when the request fails to run on the servers you selected.
Severity	Choose the severity that will generate an error.
Target WebSphere Server Name	Specify the fully-qualified host name or IP address of the WebSphere server to be monitored by the probe.
Port Numbers	Specify the port numbers of the ports you are monitoring to determine if protocol requests are being processed for WebSphere services. You can use setting with or without the autodiscovery feature enabled in the field below. The default setting 80.
Autodiscover WebSphere Ports	Select this option if you want the probe to automatically discover the ports that are to be monitored based on the application name. The application name is specified in the Target WebSphere Application field.
SOAP Connector Address	The Simple Object Access Protocol (SOAP) Connector Address is the protocol used to connect Domino to the remote WebSphere Application Server (WAS). To find the SOAP connector address on the remote WebSphere Application Server, connect to the WebSphere Integrated Solutions Console and go to Server -- Application Servers -- Server name -- Ports -- SOAP Connector Address. Specify the port number in this SOAP Connector Address field.
Target WebSphere Application	Specify the applications that you want to monitor on a remote WebSphere server. The probe will determine which WebSphere ports need to be active for the application to run properly. The probe monitors these ports and generates an event if the port becomes inactive.
Administrative security is enabled	Select this option if administrative security is enabled on the WebSphere Integrated Solution Console. Domino requires this information for connection purposes.
Websphere Integrated Solution Console User ID	Specify the administrative User ID for the WebSphere Integrated Solution Console so that Domino can authenticate and make the remote connection to WAS.
WebSphere Integrated Solution Console Password	Specify the administrative password for the WebSphere Integrated Solution Console.

Field	Action
How often should this probe run?	Choose one: Run multiple times per day -- The probe runs more than once each day. Causes the "Defined schedule" field to display. Daily -- The probe runs once each day. Use the "On which days should this probe run" field to specify the days on which the probe is run. Weekly -- The probe runs once each week. Use the "On which day of the week should this probe run?" field to specify the day on which the probe is run. Monthly -- The probe runs once each month. Use the "On which day of the month should this probe run" field to specify when the probe should run.
Defined schedule	Specify the number of minutes between each run of the probe.
Should this probe run twenty four hours per day, seven days per week?	Choose one: Yes -- Run the probe continuously. No -- The probe runs on the days and at the times that you specify.
During which hours of the day should this probe run?	Specify the start time in the From field, and the end time in the To field. The probe will run during those hours.
On which days should this probe run?	Choose the days on which to run the probe.
On which day of the week should this probe run?	Specify the day of the week on which to run this probe.
On which day of the month should this probe run?	Specify the day of the month on which to run this probe. For example, enter 15 to run the probe on the 15th day of the month.
At what time should this probe run?	Specify the time that you want the probe to run.
How should missed probes be handled?	Choose one: Ignore missed probe -- The missed probe is not run or rescheduled. Run missed probe on startup -- The next time that the server starts, the missed probe runs. Run missed probe at next time range -- The missed probe reschedules itself once. For example, if a probe scheduled to run every Tuesday at 5:00 AM fails to run, the probe reschedules itself to run on Wednesday at 5:00 AM. After that, the probe returns to its regular schedule.