Monitoring SAP-systems

Hi there,
Our company is currently setting up a monitoring system (Nagios) for the IT-infrastructure.
I'm looking for a consistent check for our SAP systems.
On a Oracle database level, a tnsping <ORACLE_SID> should be sufficient, I believe.
For the app_server, a possibility is to check for the existence of SAP-workprocesses with a ps -ef | grep <SAP_SID>. However, this looks rather primitive.
Are there any SAP tools available to implement a more consistent check on app_server level ?
Thanks in advance,
Erik

Hi Eric,
you can use dpmon to check the state of the workprocesses. For example, if they are in PRIV mode, new users won't be able to logon, although on OS level all processes are running fine ...
For J2EE you would have to use jcmon to monitor your instance...
Thanks,
Hannes

Similar Messages

Nagios monitoring SAP systems

Dear Sir or Madam,
I have RHEL 6.2 with Nagios 3 and I wanted to monitored my SAP systems. I downloaded from SAP Website the SAP NW RFC SDK 7.20. I used the SAPCAR to unzip the file. Do I need to compile something to install the RFC on my server?
Do you have some information about how to connect monitoring tools like Nagios with SAP systems?
Thank you in advance.

Hi Eric,
you can use dpmon to check the state of the workprocesses. For example, if they are in PRIV mode, new users won't be able to logon, although on OS level all processes are running fine ...
For J2EE you would have to use jcmon to monitor your instance...
Thanks,
Hannes

Solution Manager System Monitoring for non SAP system

Dear Support,
I have configured the CCMS Agent (SAPCCMSR) for non-SAP system (Windows 2008R2).
The system information (e.g. CPU, Memory, Disks etc) has already showed in RZ20 of Central Monitoring system (e.g. Solution Manager).
How can I do to configure to display these information in the Alert Inbox tab on System Monitoring Workcenter?
Best regards,
Fan Hung

Hi,
Have you defined and added corresponding logical systems for the respective satellite systems?
Here is the sequence of steps you've to do:
in SMSY:
1) Define server, DB, Systems
2) Generate READ, TMW, TRUSTED RFCs to the satellite systems
3) define logical systems and assign the satellite system to it
in Solution_Manager:
1) define new solution
2) add the logical system into the solution
If these steps are successful, you should be able to see the satellite system in SYSTEM MONITORING in Solution_Manager.
Have you already done these steps?
After performing these steps:
Solution_Manager>choose relevant solution>operations setup>Solution Monitoring>System monitoring>Activate monitoring> choose the system and activate monitoring.
Your system will then appear.
Does this help any way?

How to add other SAP systems in CCMS ALE Monitoring

Hi all, how do I add other SAP systems to be ALE monitored centrally in the PI system?
I want to monitor the Idocs in the SAP R/3 system centrally in PI with CCMS. Default is only ALE for the PI system itself.

You can add additional systems to CCMS quite easily.
I would recommend this to be done in Solution Manager though!
http://help.sap.com/saphelp_nw04s/helpdata/en/c8/40a442b024b211e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/90/4e313f8815d036e10000000a114084/frameset.htm
Also, search Google for SAP CCMS Central monitoring.

**SAP System Monitoring**

Hi All,
This is very challenging Question with expecting big answer.
What are the monitoring t-codes in sap?
How to correct the errors while monitoring the sap system?
Answer will be highly appreciated.
Thanks in advanced.
Regards
Hemant

What are the monitoring t-codes in sap?
This can be found on google by searching this question.
How to correct the errors while monitoring the sap system?
Error can be corrected only after analyzing the problem and searching the solution on SMP, SDN and other site if you cannot analyze by your self.
Regards,
Subhash

SAP System run slowly

Dear all,
Our DB Instance always run very slowly and update process
responding time is very long during month end.
I think this maybe due to it runs the database and application.
So I want to delete the DB Instance from Logon Group, and then users
will just access other else three Dialog Instances, is it Ok or what
impact will have ?
How to check PI system connected to SAP ECC Logon Group's IP , but not only
connected to the DB Instance ?
Users always need run many Background Jobs at the day,but I heard other
company almost only allow users run Background Jobs at the night.
Generally, how many background jobs running on one Instance is normal?
Do we have any good ways to control or limit users' background job
setting at the day ?
The dialog and update process numbers of DB Instance are respectively 80 and 6(Update & Update2) , other Dialog Instance is 50:4(Batch:Update)
How is the general ratio between dialog and update process numbers ?
what's the difference between update and update2 process ?
Thanks,
Michael

Hi Michael,
Your company basis team searching why SAP system run slowly.
But don't have your company basis team check your system transactions.
ST01 - Operating system monitor
ST02 - Tune Summary
ST04 - SQL Server performance analysis
SM21 - System Log
SM50 - Process Overview
SM13 - Update Requests.
SM12 - Lock Entries
Maybe long time background working process see u overview tcode SM50 and SM12 kill procees after system speed normaly.
Regards.
Cem ATES

What are the major process to transfer the data from legacy to sap system.

What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?

hi,
BATCH DATA COMMUNICATION
main methods are:
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
null

Need of XI to send an XML from one SAP system to another SAP system

Dear colleagues,
I work in the SRM solution.
In SRM there is a Purchaser and Supplier scenario called Supplier Self Services.
The Purchaser creates a Purchase order and sends it to the supplier in form of an XML file.
The purchaser system and supplier system are the same SAP system but different clients.
Example: Purchaser client is 300 and Supplier client is 330 and both of them are on the same system.
I have a very basic question.
Currently we have the XI system which acts as an interface to send the Purchaser PO XML to the Supplier as XML.
a)My question is in case the XML structure is identical across both the clients, then what is the need of XI system?
b) Is it not possible to send XML from one client to another without an XI system? there si no need of any message mapping required since I am expecting the same XML structure in both clients.
Please clarify the need of XI system in the following scenario. Is it not possible without XI?
Many thanks.
Best regards,
Srivatsa

Hi Srivatsa,
YOu can send the XML message from one sap system to another sap system even without an XI system in between.
But the use of SAP XI (Or any other middleware) is recommended because, it gives you the following advantages.
1) Better monitoring and alerting mechanism. XI provides you robust set of tools that let you monitor the status of the messages that are exchanged.
2) Direct communication between systems is referred to as Point to Point communication, which has its own disadvantages as against Hub and SPoke model (Message exchange using XI).
3) Message delivery is guaranteed if you have XI in between.
If the target system is down, the sender sap system will not try multiple times to post the message.
But if you use XI, it can be configured to send the message multiple times, till it succeeds.
Regards,
Ravi Kanth Talagana

Get an E-Mail-Notification if there is a alert for a SAP-System in DSWP

Hello,
how can i get an E-Mail-Notification when there is a alert in a SAP-System?
I know that alerts are shown in the transaction dswp under System Monitoring but exists a alternative to get these alerts via E-Mail?
In the transaction rz21 autoreactions can be defined for single MTE classes - but i search for a more generally method to get all in DSWP reported alerts via E-Mail.
Best Regards
Torsten Urban

Hello All,
You can get EWA reports thru mail.
Selection the solution for which you want the reports thru mail in DSWP tcode.
Then Edit>Automatic Email transmission>create Email recipeint.
Hope this solves your query.
Cheers,Amber S

How to implement for sap system use HADR

hi expert ，
       i am a newbie to sap basis， we have a requirement that do HA for our sap using HADR，i want know if there are some good sulotion for my scenario。
   our scenaro is we have two window 2008 sever host，one host has a sap system and we want the sap db2 database as a primary，and the other host also has a same the system which is restore from the previous sap system which we implement by system copy using database restore not migration。i want know as our secanrio could i achive SAP application HA by HADR，if we donu2018t have HA software like MSCS。whether we must manual monitor the primary sap   when it stop because any issue like hardware failed and then manual start the other sap system in the other host？
our two sap system have different sap profile beacause the hostname are different.
our aim is when one of our host can't use we can immediate start the other sap system in the other host, the less the change the better the solution .
is it possible?
thanx very much,
best regards.

hi paul ,
    thanx for your information，i have already read the inforamtion about sg247363 once-over and SAMP。 but unfortunately we have a different situation，we only have two windows servers and must installed windows server 2008 OS because some reasons。we also don't have have other host to install sap。as this situation，how could we implement HA beacuse we also don't have shared disk。the window server are isolation。
i also read some pdf which download from sdn ， in the book the HA is implemneted as the sap application has a separate host and has two host for DB2 database using HADR，the HA is rely the cluster software 。in this situation the sap application also need HA to avoid single point failure。
    as the limited i have said above， is it possible to do HA by MSCS ，can any body tell me if the MSCS is free to install in OS windows 2008？ if we can't use it free，have any other solution？in the worst ， we must manual monitor the application and when a sap application or database can't work ，we want to restart the other sap which in the other host，we need the database synchronization between two database which using HADR。is it possible ？if it do， whether there are some additional setup for sap application because the two sap application have different sap profile name（a sap is a system copy from the other by database restore）。
    any reply will be appreciated。

Error import ABAP in setup sap system

Dear experts!
Now, I'm getting some issue about setup the sap system.
when I setup the sap system, to step of import abap, I get description the issue according the following:
An error occurred while processing option SAP Business Suite 2005 > SAP ERP 6.0 Support Release 3 > SAP Application Server ABAP > Oracle > Central System > Central System( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.). You can now:
Choose Retry to repeat the current step.
Choose Log Files to get more information about the error.
Stop the option and continue with it later.
Log files are written to C:\Program Files/sapinst_instdir/BS2005/ERP60SR3/AS-ABAP/ORA/CENTRAL/.
Help me to process the issue.
Best regards, Huy

Dear you!
when i open log file the system display content according the following:
ERROR: 2014-06-04 14:22:34 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is interrupted with R3load error.
Process 'C:\usr\sap\PIE\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -stop_on_error' exited with return code 2.
For mode details see 'SAPAPPL1.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2014-06-04 14:22:34 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is interrupted with R3load error.
Process 'C:\usr\sap\PIE\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -stop_on_error' exited with return code 2.
For mode details see 'SAPAPPL2.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2014-06-04 14:22:34 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is interrupted with R3load error.
Process 'C:\usr\sap\PIE\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -stop_on_error' exited with return code 2.
For mode details see 'SAPAPPL0.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2014-06-04 14:22:56
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2014-06-04 14:22:56
3 error(s) during processing of packages.
INFO: 2014-06-04 14:22:56
Import Monitor is stopped.
Help me to process the issue!
Best regard, Huy

Monitoring SAP environment from portal

Hello,
Im a web developer and as Im new to portal development I want to find out if there exists a program or way to monitor a SAP system from the portal.
I want to call up e.g. the dialog stats (st03n) for each day of the month and display a graph in the portal.
Once I can do that I want to call solution manager and determine the custom checks and create a graph/table for each of the checks.
E.g. If I need to check cpu performance (st04), canceled jobs (sm37) and short dumps (st22), then the page displays those either for the current day or I can choose to display the month.
I know I have to use web dynPro IViews and Java and have been playing with JCo and jsp pages.
I also heard about JCA but have not gone into detail with that.
With JCo I can connect to a R3 system and call a BAPI function. As I found out there are thousands of them and no list, documentation or definition about them that I have found so far.
E.g.
import com.sap.mw.jco.*;
aConnection = JCO.createClient(SAP_CLIENT, USER_ID, PASSWORD, LANGUAGE, HOST_NAME, SYSTEM_NUMBER);
aConnection.connect();}
JCO.Function function = getFunction("BAPI_EMPLOYEE_CHECKPASSWORD");
JCO.ParameterList listParams = function.getImportParameterList();
listParams.setValue(username, "NUMBER");
listParams.setValue(password, "PASSWORD");
aConnection.execute(function);
I would appreciate it if someone can point me in the right direction.

Hello Nick,
I can create an IView for each transaction and display the gui frontend in the page, but that will be as if I work with the gui and not let me access or receive specific information.
It will also not be usefull to combine transactions in one page, or to create graphs from the information.
I want just the data that is stored in the database or created from the BAPI function I.e. variables or hashtables

App.server load balancing for SAP System with 1 PS

Hi,
In SAP CPS 7.0 (Build M26.12) I have a SAP system with Central Instance + 10 App.servers, but all instances are managed by 1 ProcessServer.
After activating the "App.server load balancing" setting in SAP system definition the application servers are becoming visible in CPS with their load factors (number of BGD wp's on app.servers) and load numbers (number of active jobs on app.servers).
This is so far fine, but the additional functionality is not working as I would expect, I have issues with 2 functionalities:
1. Based on documentation after activating also the XAL connection the CPS should submit the job on app.server with best performance based on XAL monitoring data filling the TARGET_SERVER parameter.
This functionality is not working for me at all
2. A useful functionality after activating the "App.server load balancing" setting is that the ProcessServer is going to "Overloaded" status when all BGD wp's of SAP system are occupied, thus restricting submitting new jobs during overload situation. But I had an issue also with this functionality, after SAP system recovery from overload situation, the CPS still remained in Overload status (so no new jobs were submitted).
As a workaround I had increased the treshold values for loads on all app.servers for this SAP system, what was fine for several days, but after a while I believe this was a reason of unexpected performance issues in CPS, therefore I have deactivated the 'App.server load balancing" setting at all for this ProcessServer.
I would appreciate your feedbacks with this functionality.
Thanks and Regards,
Ernest Liczki

Hi Preetish,
This connect string option is to loadbalance RFC connections. These are balanced upon login, once you are connected to a particular application server (AS) you stay on that server until you reconnect.
Since CPS uses multiple RFC connections, this will result in the connections being distributed over the available AS resources which is fine as long as they are generally evenly loaded. If you have certain AS hosts that are continuosly more loaded than the rest, then you probably don't want the CPS RFC connections to end up on these servers.
The original question is about loadbalancing of batch jobs over the available AS resources, and this is done independent of the RFC connection load balancing. Even if all CPS RFC connections are pinned to the DB/CI host, you can still loadbalance jobs over the available SAP AS hosts, either by using SAPs builtin balancing, or the CPS algorithm by activating the checkbox as indicated in the first entry in this thread.
Finally, to reply to Ernest's question: I believe there are some fixes on the app load balancing in the latest release, M26.17 should be available on the SWDC now.
Regards,
Anton.
Edited by: Anton Goselink on May 29, 2009 9:06 PM

How to transport ALEAUD to non-SAP system?

Hello,
I have R/3 system which receives documents from non-SAP system. I want to transport acknowledgements from R/3 back to non-SAP system. I want to use standard SAP ALE monitoring possibility. All needed information exists in ALEAUD IDOC which can be generated by program RBDSTATE.
But I can not process ALEAUD IDOC in SAP XI because it always automatically converts to internal XI acknowledgement.
How to transport data from ALEAUD to non-SAP system?
Best regards,
Eugeny

Hi,
We had converted the Idoc to Zidoc for the same. Thats one way to do it.
Lets see if anyone has done it with the standard IDoc
Regards
Vijaya

What are the prerequisites to monitor SAP ENVIROMENT with grid control

anybody know what are the prerequisites to monitor SAP ENVIROMENT with grid control
its necessary another software
thanks

There's currently no way to monitor a whole SAP system through gridcontrol. Of course you can monitor the underlying database.
Werner

Monitoring SAP-systems

Similar Messages

Maybe you are looking for