Monitoring Frequency in Production system

Hi Experts,
In Production system, we can do monitoring as
           Component monitoring
           Message monitoring
           Adapter monitoring
           Monitoring Memory Exceptions
           Performance monitoring
            please list, if you can think of any more types.
      And How frequently the Support team should perform these different monitoring tasks.
Thank you,
MK

Hi,
The major Production XI support work will be:
--Monitoring and Operations Support
--Bug fixing, patching and enhancements
--Disaster Recovery
Refer
Some errors in an XI production environment
/people/prashanth.azharuddin/blog/2006/11/24/some-errors-in-an-xi-production-environment
Here you will get the flow-chart to for XI production support.
Also see the below document for Best practises for XI monitoring --Page No 18
It have suggsted for creating Your Own XI Monitor in CCMS & Configuring a Central Monitoring (CEN) System
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0b4580be-0601-0010-d3ad-bd6ce51ae916
Monitoring Setup Guide for SAP NetWeaver 2004 SPS16
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/43f30e51-0a01-0010-f59a-fecea2b95b2c
Configuring the Monitoring Architecture
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6ee4b979-0901-0010-cfa8-f96c8313b5fb
Thanks
Swarup
Edited by: Swarup Sawant on Feb 29, 2008 5:19 AM

Similar Messages

Log frequence for productive system

Hello!
We use SAP DB (version 7.7) and use auto log function.
We configured the redo log frequence so, that every 10 minutes a new redolog will be written to hardware drive.
Question:
How does this setting (log frequence of 10 minutes) affect the performance of the SAP system?
And which setting (every 10, 20, 30 minutes) should be set for productive system?
kind regards

> My question is about the log settings. Untill today the redo logs were written to the drive, when the max. size of redo log (appr. 1 GB) has been reached.
> Now I changed this settng, so I have every 10 minutes a new redolog file on the hardware drive.
So again my question: Why did you change that? What was the reason to do so?
> The questions:
> Does this frequence (10 minutes) affect the performance of the server (network, SAP system, DB)?
The default max time between database savepoints is 600 seconds - so 10 minutes.
> What is the recommended setting to redolog setting for productive systems?
There is no recommended setting for that, it all depends on what you are trying do. If you want e. g. a shadow database running "after" the production database for 10 minutes, then you use that 10 minutes setup. If you want an hour you configure an hour etc.
It's all based on your setup and what you want to do.
Markus

Which components need to be monitored for a productive BO Enterprise XI 3.1

Dear colleagues,
we will start soon with a productive BO Enterprise XI 3.1 system. We do not have detailed information which components need to be monitored in a productive system. Is there any experience or are there documents available which give a hint? Many thanks in advance for help.
Best regards,
Detlef Kreiss (HP Outsourcing services)

For services, you need to monitor the Server Intelligence Agent (SIA) and Tomcat (if you're deploying on Java.) Unlike the pre-3.0 versions of XI, these are the only two processes that run as services. Everything else is managed by the SIA.
Other than that you need to go to the Central Management Console (CMC) and monitor CMS, File Repository Servers, and whatever other components that you use (Crystal, WebI, etc.)
If you're using WebI and installing the base version of 3.1 without any fix packs or without SP2, you'll need to monitor the Web Intelligence Processing Server processes - there is an issue that will cause them to hang. You can tell they're hung if they're either stopped in the CMC and wont start or if they're in "Starting" status but they never actually start. The work-around is to stop them in the CMC then go to Task Manager on the report server and stop all of the "webiprocessingserver" processes, then start them again in the CMC.
-Dell

HI in production system RWB adapter monitoring

HI in production system RWB adapter monitoring , i am using FILE and RFC , but i am not able to see the Adapter monitoring any thing the both are in grey colour ,
please help me in that
sridhar

Hi,
Can you please tell me your XI SP.?.
bcoz.. in New SP version..
We have to see in the following link for channel monitoring and adapterframework
http://host:port/mdt/monitorservlet?objectName=type=XIAdapterFramework
OR
http://host:port/mdt/channelmonitorservlet..
If solved .. points rewarded please..
Regards
Chilla..

How we can monitor while import request in production system?

dear friends,
will you please explain me
how we can monitor while import request in production system?
and
what are the things we have to monitor during the transport?
thanks
regards
zaheer

Hello Zaheer ,
I would always recommend to check that you have the latest transport tools, tp and R3trans in use in the system to avoid import errors.
Check with
tp -v
R3trans -v
if either are more than around 4 months old, I would strongly recommend to download the latest for your release from the SAP service marketplace. This avoids needlesly encountering issues that have been resolved in more recent patch lebels of these tools.
During the import, it is important to check the contents of the directories
usr/sap/trans/tmp
and
usr/sap/trans/log
that they are being continously updated which shows import is progressing.
Most important, keep checking the latest entries in the alog, uloag and slog to see which phases and trasnports are currently being imported.
If a transport fails, check these logs and the latest ones updated in usr/sap/trans/log for further details on the failure.
If there is an error please NEVER manual run any commands wihtout contacting SAP and having them analyse the issue.
When opening a message, be sure to include the latest alog, ulog and slog, along with the last few files most recently updated in usr/sap/trans/log and if possibel open an R3 connection to the import system.
Best regards,
Paul

Technical Monitoring one template used for production and non-production system.

Dear All,
Is there a way to have one template in Solman Technical Monitoring for production system and non-production system with different alerts ? For example if it exceeds a threshold for production system it will trigger red alert or set automatically an incident and if it's non prod system it will go to yellow warning alert ?
Regards
Lukasz Goral

Hi Likasz,
You first create and customize the template, and then assign to a system.
If it was selecting a system and then customizing a template, then may be such functionality makes sense.
So, I don't think that is possible.
Better would be copy the template used for production to non-production and make the adjustment to it.
Regards,
Divyanshu

Delete COPA value fields in a productive system

Does anyone have practical experience with deleting COPA value fields in a productive system?
The issue is that old, no longer used value fields should be deleted from a productive system to allow creating new ones, as the maximun number of value fields is reached.
An alternative would be to delete the prior transaction data captured on these no longer to be used value fields and rename them for their new use (to avoid that different kind of old and new data is reported on the same value field).
I am refering to the documentation on transaction KEA0 (or OSS note 160892 up to release 4.5), where it is mentioned that deleting value fields should only be done for operating concerns that have not yet been used productively. Did anyone do this already in a productive system?
Cheers, Peter

To delete characteristics or value fields, you should perform the following
activities:
1. Delete the corresponding characteristics and value fields from
Customizing in all clients (this includes forms, reports, planning
layouts, and so forth). To locate characteristics and value fields, use
the appropriate where-used list in the Customizing Monitor. You can
access it by choosing Tools -> Analysis -> Check Customizing Settings
(TA KECM).
You can jump directly from the where-used list to the relevant
Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an
operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the
operating concern before making any deletions, effect those changes and
save the data structure.
4. In order to be able to select the fields of the data structure,
choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove
them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking
whether the operating concern contains any data and whether the fields
to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the
re-activation. If the operating concern does not contain any data or
does not require the database system to be converted, the tables are
activated. You are then able to activate the environment for the
operating concern. In this case, the following activities no longer
apply.
If the operating concern already contains data, a system message tells
you that the database needs to be converted. If you proceed, an
activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages
telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can
be converted. In this case, you should answer "No" to the next prompt,
which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the
tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted
is shown for this. If the tables only contain a small amount of data
(less than 10 000 records), then all the tables can be converted in one
job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs.
However, you should ensure that table CE4xxxx (where xxxx = operating
concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during
the conversion.
A copy of the table is generated during the conversion. The database
system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function.
You can display the current status of the conversion by selecting the
"Refresh" icon. Tables disappear from the list once they have been
converted sucessfully. If a conversion is taking a while, it is also
possible to leave the transaction. You can then continue the conversion
using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services ->
Jobs.
Using the database utility transaction. You access this by choosing
Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating
concern during operating concern maintenance. You need to activate all
tables after conversion.
11. To analyze errors that have occurred during the conversion, you can
use the database utility transaction by choosing Extras -> Logs. The log
has the same name as the conversion job: TBATG-date. You can also
restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application
help while still in the above transaction.
12. Once you have activated all the tables in the operating concern,
generate the operating concern environment from within operating concern
maintenance.
You can then use the operating concern again.
Please, refer to the IMG documentation under Controlling ->
Profitability Analysis -> Structures -> Define operating concern
-> Maintain operating concern, for further details.
Hope it helps

SOAP Receiver Channel 2 nodes inactive in Production system

Hi All,
We are facing an issue with the SOAP receiver channels in production system. There are 4 nodes which can be seen in the communication channel monitoring and out of which 2 have the status as inactive and the short log says "inactive or never used".
But the same nodes are active on the sender SOAP channel and all other channels.We have also checked the Status of the SOAP service that is also set to active.
Now when the server (App server5 in our case) is switched off, which has the 2 active nodes, the messages are not processed since the nodes on the other server are inactive.
Request you to please help us out in finding out why the nodes are in inactive status only for SOAP receiver channels. Do we need to change any settings at the adapter engine level.
Thank you.
Regards,
Sarvesh Desai
Edited by: Sarvesh Nispat Desai on Aug 25, 2010 5:25 PM

There is an error in reporting the status of SOAP channels. This error has already been fixed by SAP and is available as a fix in higher releases (PI 7.10 and above, latest SPs) .
The status "inactive or never used" is shown in channel monitoring at the following two times:
1. After creating a new SOAP channel (sender/receiver) till this channel processes any new message.
2. After the PI system is restarted, all the SOAP channels show this status, though they are ready to handle any incoming/outgoing messages. The channels continue to display this status till they process any new message.
In both these situations, the SOAP Channel can handle/process messages successfully. So, kindly ignore this channel status ("inactive or never used") reporting error in channel monitoring. This will not at all hamper the normal functioning of the SOAP channels.
Hope this answers your query.

How to Enhance SPRO so that Config can be maintained in Production System

I have a requirement to Enhance the configuration nodes within SPRO so that the Client can directly edit specific configurations that would pose a risk to the business if they have to wait for the production release.
I have to enhance the following Node :
u2022 Advanced Planning & Optimization --> Supply Chain Planning --> Service Parts Planning (SPP) --> Monitoring --> Shortage Analysis -->Make General Settings for Shortage Analysis
u2022 Supply Network Collaboration --> Basic Settings --> Notes --> Define Reason Codes for Notes
The check box for "Current Setting" is input disabled for the above nodes in SPRO.
Please let me know if there is a SAP Note available to Enable "Current Settings" which will allow the Client to maintain settings directly in Production System.
If not , Please suggest any alternative solutions.
Thanks in Advance,
Vinit

Hi,
Your basis team should be able to help you to make changes directly in the production system.
Regards
Datta

Steps to configure BPM report from Solman 7.00 for productive system ECC6.0

Hi all,
Please given me the steps to configure Buisness process Monitoring reports from Solman 7.0 for productive system( ECC6.0, windows & database oracle 10.2),
I wanted to create the Reports of monitoring the buisness.
Regards,
Akash Basis consultant.

Thanks for replying Volker von Gloeden,
This thread is my first one in SDN & I am very glad that someone has given the answer ,
I will take a look for solution you have provided & will inform you.
Thanks again.

Monitor Changes in PRD System

Hi,
Is there any transaction Code to monitor the changes (a log file kind of thing) that were made to the objects in the production system on day to day basis ?
If there is no such transaction code is there any other way to trace the changes any work around ?
Regards
Ellora

Hi,
Thanks Kapadia for your response.SLG1 is for analysing application log but my requirement is to monitor the changes occured to the objects say Info objects,Infopackage,Queries,Templates and so on with user name and nature of change.Is there any way to trace these changes ?
Regards
Ellora.

Problem of unit of measurment in production system

Hi Friends,
I'm facing a peculiar problem of unit of measurement like error in all quantity and curreny fields in report output after transporting a query from quality system to production system but this query is generated from multiprovdier. what might be the problem.
Regards,
Srinivas.

Hi Dave,
Thanks for ur reply. but to trace in monitor it is not showing any error message.
My Mail ID is [email protected] Please the send the document
Regards,
bharat

EWA for non-productive Systems

Hi all,
is there a possibility to get Early Watch Alerts for Systems in a Solution, which are not marked as productive.
I don't want to create many solutions.
The same problem i have with the monitoring, I only see the productive in the monitoring overview.
Regards
Tobias

>
Schlosser Tobias wrote:
> I have added Systems to the Solution XY. The Leading Role of this solution is "productive Systems"
>
> I have add System PR1 (Productive) and System DE1 (Development). But I can only see the EWA for the Productive.
> If I want to see the EWA for the Development I have to delete the log. components and switch the leading role to "Development Systems".
>
> That's very inconvenient.
>
> I wan't one Solution with all my Systems, and EWAs for every System in it. Is this possible?
Yes, it's possible to have all systems (Prod, Dev, QA, ...) within one solution and to have EWA activated.
You need to choose "Put in Solution" from the context menu. See screen shots attached.
Regards,
Ruediger

Does two seperate client required if the solman monitors DEV and QAS system

Hi All,
This is our client landscape:
1 Dev-SolMan->For all development and quality systems(ECC 6.0, BI and EP).
1 PRD-SolMan->For all production systems(ECC 6.0, BI and EP).
Note: We have build only DEV-SolMan system as of now and we haven't done any configuration yet like either service desk or ChaRm.
The question is:
Do we need to have two seperate clients in DEV-Solman, one for all development systems and one for all quality systems? or Can we have a single client in DEV-Solman to handle all development and quality systems? What is the SAP recommented approach?
Thanks
Sanjai

Hi,
you even don't need separate Solution Manager systems to monitor DEV / QA and Prod. You could use one SolMan client to monitor and administrate all systems / clients.
Maybe it would be a good idea to create different Solution Landscapes, but this depends on your need.
Separate clients are no good option, because CHARM can only activated in on client. Also if you plan to activate charm, you need a solution that contains all systems in your transport landscape (DEV, QAnad Prod).
Kind Regards,
Holger

How to remove Production System from Solution manager.

Hi All,
We have Three system landscape and solution manager installed.
All the system are managed by Solution manager.
here we are looking to remove the Production System from Solution manager.
as in case if is there any problem in solution manager then we are not dependent on it.
things will work directly on Production system.
Could you please let us know the procedure to remove the system from solution manager.
Please let us know if is there any document provided by SAP.

Hi,
Have you implemented charm,ccms monitoring or any other functionalities?
if yes,.Delete the sytem from tms domain. and TR route needs to be adjusted, if you are using ccms, remove the agent details from RZ21 also.
Does your production system data coming from SLD?
if yes, Delete the entry from SLD
if both the answer is no.
1.delete RFC from SOLMAN to the production systems.
2. delete the production system using SMT2 transaction.
3. Remove system rom SMSY from SOLMAN.
Thanks,
Jansi

Monitoring Frequency in Production system

Similar Messages

Maybe you are looking for