Do you have any suggestions on the monitoring activities we need to perform to ensure tidiness of IFS application (Version 9).
For example: 1. Non-Finished Application Message Analysis 2. Non- Finished Background Job Analysis 3. Non-Transferred External File Load Analysis 4. Non-Complete Print Manager Job Analysis 5. Number of Database invalids
Page 1 / 1
Hi Randi,
There is a lobby designed by IFS which shall cater the requirement of yours.
You could monitor following from ADMINISTRATOR lobby overview which is bundled with IFS.
1. Background Jobs 2. Print Jobs 3. Application Messages 4. Failed Incoming Messages 5. Failed Outgoing Messages 6. DB Alerts 7. User Access Conflicts 8. Event Errors 9. Background Jobs Execution Time 10. Background Jobs Waiting Time 11. Current Users 12. Long Running Calls 13. Recent Calls 14. Licence Information
Further there are links to the Application Monitoring Console, User Administration, Permission set Administration, User Profile Administration etc.
We have seen this lobby being user in many customer environments. Hopefully this would be a good indication dashboard to fit into your requirement.
Further you could use ‘IFS System Monitoring’ , Administration Tool for in depth monitoring purposes.
You could direct to this link from IFS application access point url.
It serves information on 1. IFS Application 2. Middleware Server 3. Database
I hope these indications would be helpful to get an understanding what are the monitoring activities performed by IFS to ensure that IFS is running healthy :)
send_header('Subject', ' customer_name (#DB_SID#) - IFS Monitoring console alert: &ENTRY_ID current value is &VALUE which is outside the range &LOWER_WARNING_LIMIT - &UPPER_WARNING_LIMIT. ');
UTL_SMTP.WRITE_DATA(c, UTL_TCP.CRLF || ' ** This is an automated message from IFS Monitoring Console on #DB_SID#. **
The item &ENTRY_ID current value is &VALUE which is outside the range &LOWER_WARNING_LIMIT - &UPPER_WARNING_LIMIT. Please take the appropriate action.
Procedure for handling such alerts.
==========================
In order to prevent further messages from being sent to you while this problem is being investigated, please add the case number created to investigate this problem to the description of the monitoring item and disable the item. Both changes can be accomplished under Solution Manager / Configuration / Monitoring / Application Monitoring Entries. For example, "G123456 Investigation - <Original description> ". Once the problem is solved and the case is closed, please make sure to remove the case number from the description and to enable the monitoring item again.
All the items are always supposed to be enabled. If you need an item to be suppressed (off for an extended period), please add comments to the description, the name of user who requested the suppression and when the item is expected to be enabled again. This way, other members of the team will be known that the item is suppressed. For example, "G123456 - SUPPRESSED <by Requester> until 1/1/2015 <3:00pm EST> - <Original description> ".
');
UTL_SMTP.CLOSE_DATA(c);
UTL_SMTP.QUIT(c);
EXCEPTION
WHEN utl_smtp.transient_error OR utl_smtp.permanent_error THEN
BEGIN
UTL_SMTP.QUIT(c);
EXCEPTION
WHEN UTL_SMTP.TRANSIENT_ERROR OR UTL_SMTP.PERMANENT_ERROR THEN
NULL; -- When the SMTP server is down or unavailable, we don't have
-- a connection to the server. The QUIT call will raise an
-- exception that we can ignore.
END;
raise_application_error(-20000,
'Failed to send mail due to the following error: ' || sqlerrm);
END;
Note: Please change the bold texts according to your request.
For multiple senders use this SQL script
DECLARE
c UTL_SMTP.CONNECTION;
name_array DBMS_SQL.varchar2_table;
CC_parties varchar2(2000);
PROCEDURE send_header(name IN VARCHAR2, header IN VARCHAR2) AS
BEGIN
UTL_SMTP.WRITE_DATA(c, name || ': ' || header || UTL_TCP.CRLF);
END;
BEGIN
name_array(1) := 'cc1 @ifsworld.com';
name_array(2) := 'cc2 @ifsworld.com';
c := UTL_SMTP.OPEN_CONNECTION('ifsworld-com.mail.protection.outlook.com');
send_header('Subject', ' customer_name - (#DB_SID#) - IFS Monitoring console alert: &ENTRY_ID current value is &VALUE which is outside the range &LOWER_WARNING_LIMIT - &UPPER_WARNING_LIMIT. ');
UTL_SMTP.WRITE_DATA(c, UTL_TCP.CRLF || ' ** This is an automated message from IFS Monitoring Console on #DB_SID#. **
The item &ENTRY_ID current value is &VALUE which is outside the range &LOWER_WARNING_LIMIT - &UPPER_WARNING_LIMIT. Please take the appropriate action.
Procedure for handling such alerts.
==========================
In order to prevent further messages from being sent to you while this problem is being investigated, please add the case number created to investigate this problem to the description of the monitoring item and disable the item. Both changes can be accomplished under Solution Manager / Configuration / Monitoring / Application Monitoring Entries. For example, "G123456 Investigation - <Original description> ". Once the problem is solved and the case is closed, please make sure to remove the case number from the description and to enable the monitoring item again.
All the items are always supposed to be enabled. If you need an item to be suppressed (off for an extended period), please add comments to the description, the name of user who requested the suppression and when the item is expected to be enabled again. This way, other members of the team will be known that the item is suppressed. For example, "G123456 - SUPPRESSED <by Requester> until 1/1/2015 <3:00pm EST> - <Original description> ".
');
UTL_SMTP.CLOSE_DATA(c);
UTL_SMTP.QUIT(c);
EXCEPTION
WHEN utl_smtp.transient_error OR utl_smtp.permanent_error THEN
BEGIN
UTL_SMTP.QUIT(c);
EXCEPTION
WHEN UTL_SMTP.TRANSIENT_ERROR OR UTL_SMTP.PERMANENT_ERROR THEN
NULL; -- When the SMTP server is down or unavailable, we don't have
-- a connection to the server. The QUIT call will raise an
-- exception that we can ignore.
END;
raise_application_error(-20000,
'Failed to send mail due to the following error: ' || sqlerrm);
END;
Note: Please change the bold texts according to your request.
Then login to the DB using the sys user and execute the following SQL block (this will allow to Application owner to execute UTL_SMTP package)
Note: If the App Owner user name (IFSAPP) is different use that user name for this.
Hope this helps as well !
Hi Minoshini,
Regarding use of ‘IFS System Monitoring’, Administration Tool for in depth monitoring purposes. You wrote that one could direct to this link from IFS application access point url.
I don’t quite understand you here, may you please explain more in detail?
PS. I’m using the lobby page Administrator which is very helpful! ;-)
Thanks, Trond
@nodtrondm
Hi Trond,
I am happy to explain how you can access to IFS System Monitoring tool.
Step 1: Go to access point url and click on IFS System Monitoring link
Step 2: Enter the credentials for IFS middleware server.
Step 3: Now you are in. You can start monitoring.
Further you can go to the documentation, you would be able to find more information about this tool.
I hope this would help …
PS: I am glad to hear that you make use of that lobby page for monitoring purposes..
Hi Minoshini,
Thank you very much for your quick feedback, now I understand what you mean with access point url. I’ve now logged into the IFS System Monitoring Tool and everything looks OK (no errors)! :-)
Thanks, Trond
Hi Minoshini,
Regarding use of ‘IFS System Monitoring’, Administration Tool for in depth monitoring purposes. You wrote that one could direct to this link from IFS application access point url.
I don’t quite understand you here, may you please explain more in detail?
PS. I’m using the lobby page Administrator which is very helpful! ;-)
Thanks, Trond
Hi,,
Is there a way that we can accommodate the Email authentication with above SQL query?