| Oracle® Enterprise Manager Configuration for Oracle Collaboration Suite 10g Release 1 (10.1.0.4) Part Number B13601-02 |
|
|
View PDF |
| Oracle® Enterprise Manager Configuration for Oracle Collaboration Suite 10g Release 1 (10.1.0.4) Part Number B13601-02 |
|
|
View PDF |
This chapter describes how to set up Grid Control to monitor the Mail components of Oracle Collaboration Suite 10g Release 1.
Note:
See Chapter 12, "Configuring Enterprise Manager to Manage Oracle Email Targets" for information on setting up Grid Control to monitor the Mail components of Oracle Collaboration Suite Release 1 and 2.After the Grid Control Management Agent and Mail have been installed, the Mail server targets will be discovered and ready to configure in Grid Control.
Enterprise Manager Grid Control automatically discovers the following targets for Mail:
E-Mail Housekeeper
E-Mail IMAP Server
E-Mail List Server
E-Mail Middle Tier
E-Mail NNTP Inbound Server
E-Mail NNTP Outbound Server
E-Mail POP Server
E-Mail SMTP Inbound Server
E-Mail SMTP Outbound Server
E-Mail Virus Scrubber
The following sections describe the steps to complete the configuration of Mail targets in Grid Control.
One Collaboration Suite Database target must be created for each mail store created for Mail. It is also possible to locate these targets on any host on the network capable of accessing the Collaboration Suite Database. The benefit of this approach is that the target deployment becomes non-intrusive to the Oracle Mail Collaboration Suite Databases.
Enterprise Manager includes one Oracle Mail Collaboration Suite Database target type. You must add and configure a Collaboration Suite Database target for each mail store in the network. These targets must be configured on each mail store that you want to monitor.
To create an Oracle Mail Collaboration Suite Database target:
Using Grid Control, navigate to the Agent Home page for the Oracle Management Agent that was installed on the Collaboration Suite Database host.
In the Monitored Targets section of the page, select Collaboration Suite Database from the Add list. Click Go.
Grid Control displays the property page for the Collaboration Suite Database target type. Provide the required information, which is described in Table 2-1.
Table 2-1 Collaboration Suite Database Target Properties
| Property | Description |
|---|---|
|
The host name of the machine that has the database with the ES_MAIL schema and data. If you specify a value for this property, you must also specify a value for the DB Port and DB SID properties. |
|
|
The port of the database with the ES_MAIL schema and data. Specify the value for this property if you specified the value for the DB Host property. |
|
|
The SID of the database with the ES_MAIL schema and data. Specify the value for this property if you specified the value for the DB Host and DB Port properties. |
|
|
The connect information for this E-Mail information store. If the information store is running in RAC mode, a RAC connect descriptor can be supplied. The default is usually in the following format: (DESCRIPTION=(FAILOVER=ON)(LOAD_BALANCE=ON) (ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=<host-name>)(PORT=<port>)))(CONNECT_DATA=(SERVICE_NAME=<service-name>))) Edit the descriptor when the Oracle Collaboration Suite information store connect information changes. If you specify a value for this property, do not specify values for the DB Host, DB Port, and DB SID properties. |
|
|
The database user name for the E-Mail information store. The default value is es_mail. Do not change this valule. |
|
|
The database password for the E-Mail information store. Change this value when the password is changed. |
|
|
The Oracle home in which this database is installed. |
The service targets monitor the Mail services and simulate an end-user accessing the services. Thus, it is most beneficial to locate these targets close to where the user community using the services resides. It is also possible to create multiple targets for each service in order to measure responsiveness from multiple geographical locations.
Follow these steps to create the Mail service targets:
Using Grid Control, navigate to the Agent home page for the Oracle Management Agent that was installed on the Mail service host.
In the Monitored Targets section of the page, select one of the Mail service target types from the Add list. It is recommended that you create targets for at least the following service types:
E-Mail IMAP Service. When Grid Control displays the property page for this service type, provide the required properties, which are described in Table 2-2.
E-Mail POP Service. When Grid Control displays the property page for this service type, provide the required properties, which are described in Table 2-3.
E-Mail NNTP Inbound Service. When Grid Control displays the property page for this service type, provide the required properties, which are described in Table 2-4.
E-Mail SMTP Inbound Service. When Grid Control displays the property page for this service type, provide the required properties, which are described in Table 2-5.
E-Mail SMTP Outbound Service. When Grid Control displays the property page for this service type, provide the required properties, which are described in Table 2-6.
Table 2-2 E-Mail IMAP Service Target Properties
| Property | Description |
|---|---|
|
The host name or the IP address of the load balancer or machine used by clients for accessing the IMAP service. |
|
|
The port where the IMAP service is running. |
|
|
The Mail ID of a test user account that will be used to determine the status and availability of the IMAP service. You can use the orclguest@<yourdomain> account that is created by default in the mail system. |
|
|
The Mail account password of a test user account that will be used to determine the status and availability of the IMAP service. |
Table 2-3 E-Mail POP Service Target Properties
| Property | Description |
|---|---|
|
The service host name used by clients. This may be a load balancer or other type of service front-end. The service port is expected to be 110 for POP. Change this value when the service address changes. |
|
|
The address of a test Mail account which will be used to log into the POP Service to monitor the service. Change this value when the test account changes. |
|
|
The password for the test Mail account specified above. Change this value when the password for the test account changes. |
Table 2-4 E-Mail NNTP Inbound Service Target Properties
| Property | Description |
|---|---|
|
The service host name used by clients. This may be a load balancer or other type of service front-end. The service port is expected to be 119 for NNTP. Change this value when the service address changes. |
|
|
The name of a test newsgroup to which messages will be posted to test news delivery. Change this value when the test newsgroup changes. |
Table 2-5 E-Mail SMTP Inbound Service Target Properties
| Property | Description |
|---|---|
|
The host name or the IP address of the load balancer or machine used by clients accessing the SMTP IN service. |
|
|
The email address of a test account used for sending an email and that will be used to determine the status and availability of the SMTP IN service. You can use the orclguest@<yourdomain> account that is created by default in the email system. |
|
|
The email address of a test account used for receiving an email and that will be used to determine the status and the availability of the SMTP IN service. You can use the orclguest@<yourdomain> account that is created by default in the email system. Note that Sender E-Mail and Recipient E-Mail can be the same address. |
Table 2-6 E-Mail SMTP Outbound Service Target Properties
| Property | Description |
|---|---|
|
The connect information for this Mail administration store. If the administration store is running in RAC mode, a RAC connect descriptor can be supplied. The default value is usually in the following format:
Edit the descriptor when the administration store is changed or the connect information changes. |
|
|
The database user name for the Mail administration store. The default value is |
|
|
The database password for the administrator store user name. Change this value when the password is changed. |
To monitor web access to Mail, you create a Web Application in Grid Control. Web Application targets can be monitored for availability and performance with Application Service Level Management transactions.
Before you configure a Mail Web Application target, Oracle recommends that you create a test account so you can test the target immediately after it is created.
Follow these steps to create a Web Application target to monitor web access to Mail:
Using Grid Control, click Targets, then click the tab for Web Applications. Click the Add button to Add a new Web Application.
Grid Control displays the Create Web Application wizard, which guides you through the process of creating the Web Application.
When the wizard asks you for the Homepage URL, enter the URL for Mail. For example:
http://<host>:<port>/um
Click Help if you need help using the wizard. Include the following targets in the Mail Web Application:
The host targets where the mail servers reside
The database and listener targets that support the Mail servers
E-Mail IMAP Server and E-Mail IMAP Service targets
E-Mail NNTP Inbound Server and E-Mail Inbound Service targets
E-Mail POP Service and E-Mail POP Server targets
E-Mail SMTP Inbound Server and E-Mail SMTP Inbound Service targets
E-Mail SMTP Outbound Server and E-Mail SMTP Outbound Service target
E-Mail List Server target
E-Mail Virus Scrubber target
E-Mail Collaboration Suite Database target
OID Client target
Click OK to create the Mail Web Application target.
Use the instructions in the online help to create a representative transaction to measure the availability and performance of the Web application you just created. For example, create a transaction that logs into Mail and logs out. You can also add other transactions that test the performance of other Mail features, for example, a transaction that logs into Mail and sends a mail message.
See Also:
"Creating Transactions" in the Enterprise Manager online help.After all the Mail targets are configured, you can create the Mail group target, which provides a custom user interface for managing Mail in your Oracle Collaboration Suite environment.
The Oracle Collaboration Suite Mail group Home page contains the alerts table, followed by a table of rows of component targets. The server targets listed here can also be remotely started/stopped from this page. There is also a Performance page where key metrics are charted for the Mail group. The IMAP Operations page contains a summary of all IMAP operations in bar chart style.
Follow these steps to create the Mail group target:
In Grid Control, click the Targets tab.
Click All Targets.
Select Collaboration Suite Component from the Add list and click Go. Grid Control displays the Create Collaboration Suite Component page.
Select E-Mail from the Component Type list.
Enter a name for the Mail group in the Name field.
Select the targets you want to add to the group from the Available Targets list and add them to the Selected Targets list. Be sure to add the following target types to the Mail group:
The host targets where the Mail servers reside
The database and listener targets that support the Mail servers
An E-Mail IMAP Server and E-Mail IMAP Service
An E-Mail POP Server and E-Mail POP Service
An E-Mail NNTP Inbound Server and E-Mail NNTP Inbound Service
An E-Mail SMTP Inbound Server and E-Mail SMTP Inbound Service
An E-Mail SMTP Outbound Server and E-Mail SMTP Outbound Service
An E-Mail List Server
An E-Mail Virus Scrubber
An E-Mail Housekeeper
An E-Mail Collaboration Suite Database
An OID Client
An E-Mail Web Application
Click OK to create the group target.
Note:
The Mail group target is a custom group target. After creation, it appears on the All Targets page in Grid Control, not on the Groups page. Only generic group targets appear on the Groups page.In Grid Control, listeners for IMAP and POP servers have a status of Down after they are discovered.
The next two sections show how to change the Mail listener's status to Up on UNIX and Windows operating systems.
To change the status for Mail listeners on the UNIX operating system to Up in Grid Control, follow these steps:
Use the Net Merge utility to modify the listener.ora file to create one or more TCP addresses for the same listener without the presentation, that is, add the following to the end of the description list:
(description=(address=(protocol=tcp)(port=<any_available_port_above_1024>)(host=127.0.0.1)))
Note that the port can be any port above 1024 that is available on the system for the listener, such as 1522 or 1526, but it has to be different than the one with presentation.
Restart the Mail listener by performing the following steps:
Log in as root.
Check if sendmail is running by using this command:
ps -ef | grep sendmail
If it is running, kill the process.
Execute the following command, where userid is the UNIX account that owns the Oracle software:
id userid
Issue the following command, where listener_es is the name of the Mail listener:
tnslsnr listener_es <uid_value> -group <gid_value>
Note:
The Mail listener cannot be started using
lsnrctl from a user shell. Since it has to listen on ports below 1024, it has to be started by the superuser on UNIX operating systems. When restarting the Mail listener following the listener.ora change, you should use the same command, with the same command line arguments, as was used to start it up initially.In Grid Control, navigate to the All Targets page and click the link for the listener_es target that shows a status of Down.
On the Listener Home page, click Monitoring Configuration. Change the Machine name property to 127.0.0.1 and change the Port number property to the port number used in the new TCP address without presentation.
To change the status for Mail listeners on the Windows operating system to Up in Grid Control, follow these steps:
In Grid Control, navigate to the All Targets page and click the link for the listener_es target that shows a status of Down.
On the Listener Home page, click Monitoring Configuration. Make sure that the Port number property is set to the port number corresponding to the port number used in the new TCP address without presentation (that is, the port number corresponding to the entry in listener.ora which has HOST=127.0.0.1).
