Oracle Applications →

Active Monitoring JumpStart Guide

This guide is designed to get you a basic active monitoring system that is useful without going through the different parts of the documentation. At the end of this walk through you will find links to relevant topics for each step, should you wish to customize the setup.

Process Flow

  1. Setup SMTP Credential.
  2. Setup SMTP Connection.
  3. Create E-mail Alert Gateway.
  4. Create Alert Escalation.
  5. Create Ad Hoc Alert Source.
    1. Test Ad Hoc Alerts.
    2. Improve Ad Hoc Alert E-Mail.
    3. Test SimpleAdHocEmail Ad Hoc Alert Source.
    4. SimpleAdHocEmail Result.
  6. Create a Process Alert Source.
    1. Test Process Alerts.
    2. Improve Process Alert E-Mail.

Setup SMTP Credential

Create a credential to authenticate to the SMTP server. Only required if your SMTP server requires authentication.

  1. Navigate to Security > Credentials.
  2. Choose New Credential from the context-menu.
  3. Choose smtp Protocol.
  4. Fill the SMTP username into the Real User, usually your e-mail address.
  5. Fill the password and confirm the password in the Password and Retype.
  6. Enter the FQDN of the SMTP server into the Endpoint field.

Setup SMTP Connection

To send e-mail, the system needs an SMTP server connection.

  1. Create registry entries /configuration/jcs/Mail/Server, /configuration/jcs/Mail/From, /configuration/jcs/Mail/Port:
    1. Navigate to Configuration > Registry, choose New > Registry by path from the context-menu of configuration.
    2. Copy-paste /configuration/jcs/Mail/Server in the Path field and the FQDN of your SMTP server in the Value field, example: smtp.company.com. If you previously created an SMTP credential, it must the Endpoint of the credential, choose Ok.
    3. Copy-paste /configuration/jcs/Mail/From in the Path field and an e-mail address in the Value field, example: notifications@company.com, choose Ok.
    4. Copy-paste /configuration/jcs/Mail/Port in the Path field and your SMTP port in the Value field, example: 25, choose Ok.
  2. Send an and check you received it.
    1. Navigate to Definitions > Processes, fill System_Mail_Send into the Search box, locate System_Mail_Send and select Submit from the context-menu.
    2. Fill your e-mail address into the To field, Testing SMTP in the Subject field, and Hello World! into the Text field.
    3. Choose Submit and Submit once more to send the e-mail.
    4. If you received the e-mail, you have correctly set up e-mail sending and may proceed to setting up an Email Alert Gateway.

Create E-mail Alert Gateway

  1. Navigate to Alerting > Email Alert Gateway.
  2. Choose New e-mail alert gateway from the context-menu.
  3. Fill CatchAll into the Name field, *@company.com into the Address Pattern field, and 99 into the Processing Order fields. Note that any existing e-mail alert gateways with a lower processing order will override this one.
  4. Choose Save & Close.

Create Alert Escalation

  1. Navigate to Alerting > Alert Escalations.
  2. Choose New alert escalation from the context-menu.
  3. Fill SimpleEscalation into the Name field.
  4. Choose Save & Close.

Create Ad Hoc Alert Source

  1. Navigate to Alerting > Ad Hoc Alert Source.
  2. Choose New ad hoc alert source from the context-menu.
  3. Fill SimpleAdHoc into the Name field.
  4. In the Sent to field, fill your e-mail address (example: user@company.com) into the Address field and SimpleEscalation into the Default Alert Escalation field.
  5. Choose Save & Close.

Test Ad Hoc Alerts

  1. Navigate to Definitions > Processes, fill System_Alert_Send into the Search box, locate System_Alert_Send and select Submit from the context-menu.
  2. Select SimpleAdHoc in the Alert Source field, fill Hello World! into the Data field.
  3. Choose Submit and Submit once more to send the e-mail.
  4. If you received the e-mail with Acknowledge in the e-mail body, you can improve the e-mail.

Improve Ad Hoc Alert E-Mail

  1. Navigate to Alerting > Ah Hoc Alert Source
  2. Locate SimpleAdHoc, choose Duplicate from the context-menu.
  3. Change the Name field to SimpleAdHocEmail
  4. On the Alert Source Email tab, choose Add.
  5. Paste the below HTML into the Body field.
  6. Choose Save & Close
<html>
<head><title>Email</title></head>
<body>

<p>Hello colleague,<br />
<br />An Ad hoc alert has been sent at [?=Time.now('Europe/Rome')?] with data:</br />.[?=data?].</p>

<h5>Links:</h5>
<ul>
[?if test="chainJobId != null &&  jobId != chainJobId"?]
  [?if test="topLevelJobId != null && topLevelJobId != chainJobId"?]
    <li>
      <a
      href="https://server/redwood/api-permalink/show?link-objecttype=Process&link-processid=[?=topLevelJobId?]">
        alert parent chain</a></li>
  [?endif?]
    <li>
      <a
      href="https://server/redwood/api-permalink/show?link-objecttype=Process&link-processid=[?=chainJobId?]">
        alert chain</a></li>
[?endif?]
  <li>
    <a
      href="https://server/redwood/api-permalink/show?link-objecttype=Process&link-processid=[?=jobId?]">
      alert process</a></li>
<li>
  <a
    href="https://server/redwood/api-permalink/show?link-objecttype=[?=alertSourceType?]&link-uniqueid=[?=alertSourceUniqueId?]">
    alert source</a></li>
</ul>

<p>Regards,<br />IT</p>

</body>
</html>

Test SimpleAdHocEmail Ad Hoc Alert Source

  1. Navigate to Definitions > Processes, fill System_Alert_Send into the Search box, locate System_Alert_Send and select Submit from the context-menu.
  2. Select SimpleAdHocEmail in the Alert Source field, fill Hello World! into the Data field.
  3. Choose Submit and Submit once more to send the e-mail.
  4. If you received the e-mail with links in in the e-mail body, you have completed the ad hoc alerting.

SimpleAdHocEmail Result

You have created a basic alerting system you can extend to actively monitor processes.

Create a Process Alert Source

  1. Navigate to Alerting > Process Alert Source.
  2. Choose New process alert source from the context-menu.
  3. Fill CatchErrorProcess into the Name field.
  4. Fill *Error* into the Name field of the Raise an alert for definitions that match field, leave Match Type on GLOB Case Insensitive.
  5. In the Sent to field, fill your e-mail address (example: user@company.com) into the Address field and SimpleEscalation into the Default Alert Escalation field.
  6. On the Statuses tab, choose status Error for the first.
  7. Choose Save & Close.

Test Process Alerts

  1. Navigate to Definitions > Processes.
  2. Choose New Process Definition, select RedwoodScript, and choose Next.
  3. Fill ThrowError into the Name field, and {throw new RuntimeException();} into the Source field.
  4. On the Process Control tab, select a Default Queue.
  5. On the Parameters tab, create a parameter named MyParameter with Direction In Out and Default Expression Hello world!.
  6. Choose Switch to Definition Studio, choose Save & Submit, notice the process reaches status Error.
  7. If you received the e-mail with Acknowledge in the e-mail body, you can improve the e-mail, choose Save & Close.

Improve Process Alert E-Mail

  1. Navigate to Alerting > Process Alert Source.
  2. Locate CatchErrorProcess, choose Edit from the context-menu.
  3. Change the Name field to CatchErrorProcessEmail.
  4. On the Alert Source Email tab, choose Add.
  5. Paste the below HTML into the Body field.
  6. Choose Save & Close
<html>
<head><title>Email</title></head>
<body>

<p>Hello colleague,<br />
<br />A process alert has been sent at [?=Time.now('Europe/Rome')?] with MyParameter:</br />[?=parameters.MyParameter?]<br />${MyParameter}</p>
<ul>
  <li>The name of the process definition of the process ${jobId} in status ${newStatus} is ${jobDefinition}</li>
  <li>The owner of the process definition is ${jobDefinitionOwner}.</li>
  [?if test="topLevelJobId != null &&  jobId != topLevelJobId"?]
    <li>The ID of the highest parent ${topLevelJobId}.</li>
  [?endif?]
  <li>The owner of the process is ${jobOwner}.</li>
  <li>The old status of the process is ${oldStatus} and new status of the process was ${newStatus}.</li>
  <li>The input value of parameter 'MyParameter' is [?=parameters.MyParameter?] of the process, available in REL only. The value of the field must be prefixed with <code>=</code>, the only exception being the E-mail *Body* field.</li>
  <li>The output value of parameter 'MyParameter' is [?=outParameters.MyParameter?] of the process, available in REL only. The value of the field must be prefixed with <code>=</code>, the only exception being the E-mail *Body* field.</li>
  <li>The name of the queue of the highest parent process is ${topLevelQueue}</li>
  <li>The status in the remote system is ${remoteStatus}</li>
  <li>The return code of the process is ${returnCode}</li>
  <li>The queue of the process is ${queue}</li>
</ul>
<h5>Links:</h5>
<ul>
[?if test="chainJobId != null &&  jobId != chainJobId"?]
  [?if test="topLevelJobId != null && topLevelJobId != chainJobId"?]
    <li><a
    href="https://server/redwood/api-permalink/show?link-objecttype=Process&link-processid=[?=topLevelJobId?]">top-level chain with error process</a></li>
  [?endif?]
    <li><a
    href="https://server/redwood/api-permalink/show?link-objecttype=Process&link-processid=[?=chainJobId?]">chain with error process</a></li>
[?endif?]
<li><a
href="https://server/redwood/api-permalink/show?link-objecttype=Process&link-processid=[?=jobId?]">Error process</a></li>
<li><a
href="https://server/redwood/api-permalink/show?link-objecttype=[?=alertSourceType?]&link-uniqueid=[?=alertSourceUniqueId?]">alert source</a></li>
</ul>

<p>Regards,<br />IT</p>

</body>
</html>

Follow-up Reading

Oracle Applications →