This document covers the following topics:
To monitor a component, proceed as follows:
Configure the product-specific environments that are used for monitoring. See Product-Specific Environment Configuration.
Log on to My webMethods.
Go to Navigate > Applications > Administration > Analytics > Infrastructure Components > Discovery and add an asset.
Perform a discovery (that is, click on the green arrow). Click the button to verify whether the discovery was successful.
Go to Navigate > Applications > Administration > Analytics > Infrastructure Components > Monitored Components, click the product to be monitored, and then select the components and KPIs.
To view the monitor data, go to Navigate > Applications > Monitoring > System-Wide > Analytics Overview.
This may have one of the following reasons:
If the connection to the component is down, KPIs of the component cannot be monitored. The state flag of the Adabas or Natural Collector indicates this situation.
If the monitored component is down, only the component state flag is provided ("offline").
When the monitoring is restarted, KPIs displaying delta values are not provided for the first polling interval. This is because the Infrastructure Data Collector interface needs at least two succeeding values for the delta calculation. See KPI Definitions for Infrastructure Monitoring: KPIs where the type is "delta" use the delta calculation.
Some KPIs reflect features which are not applicable to every component of the given product. For example, the "cache" KPIs of the Natural buffer pool can only be monitored if the buffer pool uses a cache. A special state flag indicates this situation.
Some event maps monitor similar products. They contain common KPIs and product-specific KPIs. For example, the "cluster" KPIs of the Adabas Server event map are only displayed if the Adabas Server runs as a cluster.
If the Natural version supports the Natural Optimize Monitor Buffer Pool and this buffer pool is down or in error, several Natural products and components cannot be monitored. The affected products and components are listed in Product-Specific Environment Configuration > Natural > Mainframe.
To display the graphics, Adobe Flash Player is required. Make sure that Adobe Flash Player Version 10 or above is installed.
For Software AG's enterprise products, the preferred view in the My webMethods Analytics Overview is Dimension Tree with Show Component Categories unchecked.
Any other view can also be used.
When you log on to My webMethods for the first time, the message "No Configuration Selected" is displayed in the Analytics Overview. To select the configuration, proceed as follows:
Go to Navigate > Applications > Administration > Analytics > Overview Configuration.
Initially, only the configuration with the name Analytics System View is available.
Click the red "disabled" icon (
) for the configuration that you want to use.
The icon switches to the green "enabled" icon
(
).
Go to Navigate > Applications > Monitoring > System-Wide > Analytics Overview.
From the Overview Configuration drop-down list box in the upper right corner, select the configuration that you want to use (for example, Analytics System View).
In the Analytics Overview and in some other screens of My webMethods, it may happen that a red message "Max Results Enforced (nnn)" is displayed (where nnn can be any number). This means that not all potential elements of the screen are displayed. To change the "Max Results Enforced" setting, proceed as follows:
In the Search frame, select the Options tab.
Change the value in Max Results as desired, or select No Maximum.
Click the button.
You can specify the parameters for monitoring critical Adabas files in the Adabas/Natural Data Collector profile (see Adabas Files).
If you do not know which threshold values are appropriate for your
environment, you can start the test program (SYSEDM) and select
the Adabas Files function (see
Testing the Monitoring of
Adabas Critical Files). In a first approach, perform the
test monitoring with low threshold values (such as 5%), with UserIsn=Y and the
long list. Use trace level 10 to receive the file-specific trace entries, and
monitor file KPIs only to shorten the output.
In the output, you can evaluate the KPIs for listing files (AdabasFilesCriticalExtentsList and AdabasFilesCriticalIsnRangeList). For the critical extents, you see the percentage value and the corresponding allocated extents. Example:
12:80%97x,31:91%112x
In the list, you can see which files would be critical if you would select a higher threshold. If you know how many extents should be allocated at most or should be free at least, you can determine the average percentage value corresponding to an extent, and use this value as the threshold.
For the critical ISN range, you see the currently used percentage values and how the file is defined. Example:
12:93%NU,31:52%RS4
In the list, you can see which files would be critical if you would
select a higher threshold. If files defined with USERISN=YES
(indicated by a "U") have an abnormally high
percentage value, it might be better to sort them out by specifying
USERISN=NO in the profile.
By default, the Adabas critical file data is collected only once a day. The trace output shows the elapsed time for the monitoring of the database(s) you have selected. Example:
OPTMONI : MONADA - Event maps: 2 Attributes: 13 Time: 0.4
From the displayed elapsed time, you can estimate how long it would take to monitor all databases. You can then decide whether you would like to monitor Adabas critical files more often, for example, once an hour.
In general, all predefined rules can be modified. This is done in My webMethods. Go to Navigate > Applications > Administration > Analytics > Rules > Rule List and click on the rule name.
Some predefined rules are essential for proper monitoring of the
products. These are in general the rules referring state KPIs. Other predefined
rules serve as samples. You can edit a rule and adjust the limits to your
needs. You can disable a rule by clicking the green "enabled" icon
(), or you can even delete a rule completely.
Proceed as follows:
Configure the firewall of the machine on which My webMethods Server (MWS) is running so that the mail server port is opened.
Configure the access protection rules of your anti-virus software so that the processes java.exe and mwssvc.exe are allowed to send mail.
Before any e-mail can be sent from Optimize, the name of the mail server has to be specified in the mail settings for the Analytic Engine.
To configure the mail settings, log on to My webMethods as administrator and proceed as follows:
Go to Navigate > Applications > Administration > System-Wide > Environments > Define Environments.
Click the name of the environment for which you want to configure the mail settings.
Select the Configure Servers tab.
Expand Analytic Engine in the tree (by clicking on the plus sign in front of it).
Click Mail Settings.
Specify the following options:
| Option | Description |
|---|---|
| Mail Server | The name of the mail server. |
| Default Sender | The address that is to be shown as the sender in the test e-mail. |
| Admin Address | The address to which the test e-mail is to be sent. |
Click the button.
A test e-mail is sent to the Admin Address specified before. You should receive a message such as the following: "Connected to SMTP server successfully. If you did not receive an e-mail, be sure the Admin Address is correct and try again."
You should now check the inbasket of the recipient specified in the Admin Address to find out whether the test e-mail was delivered correctly.
Click the button.
Before an e-mail alert can be sent, the e-mail address of the user who is to receive the e-mail alert must be known to Optimize.
Log on to My webMethods as administrator and then proceed as follows:
Go to Navigate > Applications > Administration > System-Wide > User Management > Users.
Click the name of the user who is to receive the e-mail.
Fill the E-mail Address field.
Click the button.
Note:
If you want to specify your own e-mail address, it is not required
to log on as administrator.
An e-mail alert can be sent for any predefined rule or for any additionally created rule.
Log on to My webMethods and then proceed as follows:
Go to Navigate > Applications > Administration > Analytics > Rules > Rule List.
Click the name of the rule for which you want to send an e-mail alert.
Click the button.
A drop-down list box is now shown below the button. If the drop-down list box is empty, you must first define an e-mail address for a user as described above.
Select a user from the drop-down list box.
Click the button.
This is configured in the file web.xml which is stored in <drive>:\webMethods8\MWS\server\default\deploy\portal.war\WEB-INF.
Edit the file web.xml.
In the section <session-config>, specify the
required timeout value, in units of seconds, in
<session-timeout>.
<session-config> <session-timeout>60</session-timeout> </session-config>
The polling interval specifies how often the Infrastructure Data Collector polls the monitored products for statistical data. The polling interval should be a divisor of the collection interval which is defined with the KPI. In general, the collection interval for Software AG's enterprise products is five minutes. Therefore, it makes sense to use either five minutes or one minute as the polling interval. The recommended value is five minutes; this is also the default value.
To configure the polling interval, proceed as follows:
Go to Navigate > Applications > Administration > System-Wide > Environments > Define Environments.
Click the name of the environment for which you want to configure the polling interval.
Select the Configure Servers tab.
Expand Infrastructure Data Collector in the tree (by clicking on the plus sign in front of it).
Click Collector Settings.
Specify the value for Monitor Polling Interval (in units of minutes) as desired.
Click the button.
When the MashZone portlet has been installed in My webMethods Server, the system administrator can publish it in the Workspace Tools section. You can then drag it into a workspace. See also Integrating MashZone in My webMethods Server.
Log on to My webMethods as administrator and then proceed as follows:
Go to Navigate > Applications > Administration > System-Wide > User Management > Users.
Click the button.
Fill the fields in the Create User frame and click the button.
Fill the user attributes as desired and click the button.
Log on to My webMethods as administrator and then proceed as follows:
Go to Navigate > Applications > Administration > System-Wide > User Management > Roles.
Click the role name My webMethods Administrators.
Select the Members tab.
Click the button.
Click the button.
If many users are defined, you can restrict the search by specifying a keyword. The list of available users is displayed in the left window.
In the Available window, click the name of the user to whom you want to assign administrator rights and then click the arrow which shows to the right.
The user is moved from the Available window to the Selected window.
Click the button.
Click the button.
In a mainframe CICS environment, start the RPC server from PLTPI. See RPC Server Configuration and Start for more details.
In a mainframe batch environment, run the RPC job as started task.
Adabas and Natural Data Collectors
The log file of the Adabas and Natural Data Collectors is written to
an output data set of the RPC or CICS job on the mainframe. Under UNIX and
Windows, the log file is written to a work file on the Natural temporary
directory. For more details, see Tracing the Adabas and Natural Data
Collectors.
Infrastructure Data Collector
By default, the Infrastructure Data Collector logging for the data
collector packages of Software AG's enterprise products is written to the
\profiles\InfraDC\logs directory into a file with the
following name:
serveryyyymmdd.log
See also Tracing the Enterprise Products in the Infrastructure Data Collector.
EntireX Communication
The EntireX communication logging in the Infrastructure Data
Collector is written to the \profiles\InfraDC\logs
directory into a file which has the following name:
entirexyyyymmdd.log
See also Tracing the EntireX Communication in the Infrastructure Data Collector.
where yyyymmdd in the above file names stands for the current date (year month day).
To restrict the amount of disk space, proceed as follows:
Go to Navigate > Applications > Administration > System-Wide > Environments > Define Environments.
Click the name of the environment for which you want to restrict the amount of disk space.
Select the Configure Servers tab.
Expand Default Settings in the tree (by clicking on the plus sign in front of it).
Click Journal Logging.
Click the target name DailyFile.
Specify the value for Max # Log Files as desired.
Click the button.
If you restrict the number of log files and the maximum number is reached, the oldest log file will be removed before a new file is allocated.
By default, both the Adabas Data Collector and the Natural Data
Collector use the Optimize Infrastructure Data Collector logging level as the
trace level. The default trace level can be overridden using the
TRACE
parameter as described in Adabas/Natural Data Collector
Profile.
