Saturday, June 25, 2011

Steps Using ABAP proxies using AAE







some times Parallel processing with different aae as fallows

Avoiding communication with Integration Engine as fallows



System requirement to Implement abap proxies on AAE

Necessary Step at Sender ABAP system. as fallows.



Need to create system id ( similar to Sender rfc scenario)


  • Use same System id, in Integration engine entry(sxmb_adm) Foe example: BOOKS is our system id( it is orbiter value)
  • We can use different system id, for different AAE ( In-case of different AAE SYSTEMS)

(Let us see list steps as summary as said above)


Step at AAE( pi SIDE Configuration as fallows), Createing soap communication channel.



For Asynchronous apap proxies, need specify module details as fallows.

InBound processing is mandatory step for sender abap proxies as fallows.



Now, we see the differnt step for configuration receiver abap proxies.


Also create outbound processing step for receiver abap proxies scenario.



Monitoring is common step in this case also.



Limitations about ABAP proxies using AAE


Deviprasad

Working with Idoc adapter in SAP PI

IDoc Packaging Benefits



Another benifits of using IDoc packaging



Idoc settings at sender SAP system(partner profile we20) specify idoc size and collection radio button


How these are split into package size based on we20(sender sap system) settings and PI idoc adapter settings(PI side). you analyze by seeing this example.

Sender aggrement is required, if you want to use this feature.



Idoc monitoring as fallowsing , control records, content. as fallows.


SAP PI webBased SAP Management Console

Advantages of webBased SAP Management Console
(Get fast overview on system situation and detect bottlenecks)
->Especialy for SAP PI
  • Display and control Java processes.
  • Display the abap work proces overview and control ABAP processes
  • Display java Virtual Machine garbage collection and heap memory information for application server.
  • Display SAP log and traces files, start profiles instance parameters, the system environment, sap environment, Internet communication manager(ICM) queue statistics and so on..

-> In General
  • Monitor and control (start, stop or restart) the SAP system and its instances with singel tool.
  • Monitor system alerts
  • Display the current status tree
  • Display the list of all access points to an SAP system.
  • Display information about the AS Java thread, sessions, caches, aliases, Enterprise Java beans(EJB) sessions, and remote objects.




http://:50000
simply replace 50013 (last 2 digits and press enter), atomatially new java webstart console starts.

Advantages of webBased SAP Management Console
(Get fast overview on system situation and detect bottlenecks)
->Especialy for SAP PI
1. Display and control Java processes.
2. Display the abap work proces overview and control ABAP processes
3. Display java Virtual Machine garbage collection and heap memory information for application server.
4.Display SAP log and traces files, start profiles instance parameters, the system environment, sap environment, Internet communication manager(ICM) queue statistics and so on..
-> In General
1. Monitor and control (start, stop or restart) the SAP system and its instances with singel tool.

2. Monitor system alerts
3. Display the current status tree
4. Display the list of all access points to an SAP system.
5. Display information about the AS Java thread, sessions, caches, aliases, Enterprise Java beans(EJB) sessions, and remote objects.

How to open the webBased Management console

Open the integration builder as fallows.

http://:50000
simply replace 50013 (last 2 digits and press enter), atomatially new java webstart console starts.


1. it has abap, java stacks and each one has its own database and schema.

os -> memeory , file system management.
(files system exceeds, we can delete some , which is showing red colour)

here we can see work process status, ideal and busy.
also gives memory consumptions details also.

Gc history: Garbage collector details also we can check.
Java stack object table: we can check number of threads also( currently using )
Red colour thread, states us, already used thread by applications.

icm: check http connections status( opened, closed) we can increase also this.


Developer can also trace his required things as fallows.


then you can see search help, use search key to find your require things.

we can see logFiles of SAP PI.

Tuesday, June 14, 2011

Errors in BPM

Some times, after export to Integration process into DPI to QPI, your bpm may not work due to cache refresh problems.( it causes red colour System error , bpm run time work flow)

That time go to Integraiton builder. select administration section. ( it has sections like Intergration repository, directory ) choose required section( Example: ir and ip) refresh the data caches. Now again send a message to bpm, to check.


Starting and Stopping the BPE
Use
You use transaction SWF_XI_ADM_BPE to regulate the starting and stopping of the Business Process Engine (BPE). You can also use this transaction to determine whether the BPE has been started or is stopped.
Prerequisites
● To display the status of the BPE you require role SAP_XI_BPE_MONITOR_ABAP.
● To start or stop the BPE you require role SAP_XI_BPE_ADMINISTRATOR_ABAP.
Procedure
1. Call transaction SWF_XI_ADM_BPE.
The status display shows the status of the BPE and its components:
○ Green: Component running
○ Red: Component stopped
○ Amber: Component currently being stopped or started
This can take a few minutes. Wait until the status display changes.
○ Error icon: Error when starting or stopping the component.
You can decide whether you want to continue with the procedure or terminate. For example, if a component cannot be stopped, you can decide whether you want to attempt to stop the BPE again, or whether you want to restart the BPE completely.
2. Start or stop the BPE.
Whether the button for starting the BPE or the button for stopping the BPE is displayed depends on the status of the BPE. If an error occurs, both buttons are displayed and you must decide how you wish to continue.
The individual steps for starting and stopping the BPE are executed in turn and the status of each step is displayed. The log for the individual process steps is displayed in the window area at the bottom of the screen.


How To…Configure ccBPM RuntimePart III: Transactional Behavior of an Integration Process
go to sdn.sap.com and check for above document.

We need to enable create new transaction, in send step, while calling one bpm to another bpm (syncronously). if you enable this, then only(syncronous mode) we get the response from 2nd bpm.


also see: what is bpm

Sunday, June 12, 2011

smq2 errors in SAP PI

Queue Status in SMQ2 and Table ARFCRSTATE
Use
Depending on the way a Logical Unit of Work (LUW) is processed, an inbound queue or the table ARFCRSTATE (status table of the LUWs in the tRFC/qRFC target system) can have different statuses.

Inbound Queue
The following statuses may be displayed in transaction SMQ2:

· READY
The queue is ready for processing. This status should only be a temporary status. However, in the following case this status can also be permanent: A queue has been locked manually using transaction SMQ2 or using a program, and then unlocked without being activated at the same time. This queue must be activated explicitly.

· RUNNING
The first LUW of this queue is currently being processed. If a queue in this status hangs for more than 30 minutes, this may mean that the work process responsible for processing this LUW has been terminated. In this case you can activate this queue again. Note that activating a queue in status RUNNING may cause a LUW to be executed several times if this LUW is still being processed in the target system at that time. We therefore recommend a waiting time of at least 30 minutes before you reactivate the queue.

· SYSFAIL
A serious error occurred while the first LUW of this queue was being executed. The execution was interrupted. When you double-click on this status, the system displays an error text. For more information on this error, see the corresponding short dump in the target system (transaction ST22). No background job is scheduled for a retry and the queue is no longer processed. To solve the problem, information from the affected application is required. See SAP Note 335162 for the error text "connection closed".

· CPICERR
A network or communication error occurred while the first LUW was being executed. When you double-click on this status, the system displays an error text. For more information on this error, see the syslog (transaction SM21) or the trace files dev_rd and dev_rfc*. Depending on the registration of this queue (SMQR), a background job is scheduled for a retry. See SAP Note 369524 for the error text “Logon failed". Status CPICERR may also exist in the following cases although no communication error occurred: A qRFC application finds out that a LUW cannot be processed any further due to a temporary error in the application and therefore calls the RESTART_OF_BACKGROUNDTASK function module to prompt the qRFC Manager to cancel the execution of this LUW and to repeat this LUW later in accordance with the specification in transaction SM59. In this case, qRFC simulates a communication error with the text "Command to tRFC/qRFC: Execute LUW once again." If this error occurs very often, you must contact the corresponding application.

· STOP
On this queue or a generic queue (for example BASIS_*) a lock was set explicitly (SMQ2 or programs). Note that the processing of qRFC never locks a queue. After having informed the corresponding application, you can unlock this queue using transaction SMQ2.

· WAITSTOP
The first LUW of this queue has dependencies to other queues, and at least one of these queues is currently still locked.

· WAITING
The first LUW of this queue has dependencies to other queues, and at least one of these queues currently still contains other LUWs with higher priorities.

· ARETRY
When the LUW was processed, the application diagnosed a temporary problem and has prompted the qRFC Manager with a specific qRFC call to schedule a background job for a retry, based on the registration in SMQR.

· ANORETRY
When the LUW was processed, the application diagnosed a serious error and has prompted the qRFC Manager with a specific qRFC call to stop processing this LUW. To solve the problem, information from the affected application is required.

· MODIFY
Processing of this queue is locked temporarily because the LUW data is being modified.

Table ARFCRSTATE
You can use transaction SE16 to display the status:

· EXECUTED
The related LUW is completely executed in the target system. The system waits for an internal tRFC/qRFC confirmation from the sending system before this entry is deleted.

· HOLD
The corresponding application has processed this LUW in parts and wants this LUW to not be repeated in the case of subsequent network or communication errors (see SAP Note 366869 if there are many entries with this status).

· WCONFIRM
During a LUW execution the application has prompted the tRFC/qRFC Manager to set status HOLD. If the LUW execution has already been completed but this application has not yet signaled the logical LUW end and if the tRFC/qRFC-internal confirmation from the sending system has been received, then this LUW receives status WCONFIRM.
If the respective application informs the tRFC/qRFC Manager about the logical LUW end, then this entry is deleted (see also SAP Note 366869 for more details).
From author advice(riyaz)
Messages stuck in queues
Check the queues using transactions SMQ1 (outbound)/SMQ2 (inbound). Resolve the displayed errors. You can cancel the messages from SXMB_MONI. Execute LUW if necessary and avoid deleting entries manually