AE_EOIO_OPTIMIZE: New Mechanism for Handling EOIO Messages

When EOIO messages are sent from Integration Engine to Adapter Engine, they may be sent to different J2EE server nodes by the web dispatcher based on the load. The J2EE engine communicate with each other to ensure that the messages are processed in the desired serial order. There is a performance overhead with the cluster communication, specially when there are a lot of EOIO messages. Administrators dealing with J2EE node restarts with Missed broadcast from Message Server can feel the pain.

Good news is: The latest SPS on PI 7.1, 7.11 and 7.3 have introduced a mechanism to send the EOIO messages of a queue to a single J2EE engine and reducing the need for cluster communication. Bad news is: Due to a bug, this mechanism is not working well now and SAP is working on fixing it.

It won't take time for SAP to come up with a better mechanism, meanwhile you can disable this (default) feature (on the above said SPS) by setting AE_EOIO_OPTIMIZE to 0 in SXMB_ADM --> Integration Engine Configruation. To enable it, you can set the same parameter to 1.

The error (503 service not available. Detail: server overload: no more sessions available) details are available on SAP Note 1586827.

Recommended reading for SAP XI/PI developers:
SAP NetWeaver PI Development: Practical Guide


With this practical guide, you ll learn how to develop mappings, adapters, and proxies for SAP NetWeaver Process Integration. Each exercise includes detailed descriptions for all development and configuration objects (including monitoring), and then concludes with an integration example. The book is suitable for SAP NetWeaver PI beginners.

Comments

Post a Comment

Popular posts from this blog

OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more

Image
With increasing need to improve performance or reduce costs or vanishing support for operating systems/databases it becomes inevitable to migrate to a better OS or DB. We feel take a quick look at the primary ingredients of the tools for OS/DB migration handled by R3SETUP. Tools - R3load, R3ldctl and R3szchk R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups. The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own. Files Command files*.cmd  are creat...
Read more

Fixing Inconsistent Table - Table activation fails due to inconsistency between DD and DB

If you find a table to be available on the database, but not active in ABAP dictionary, try calling SE14 as DDIC user, enter the table name and choose Table > Reconstruct, Execute. If this method fails follow these steps: Call transaction code SE37 and execute the function module  DD_TABL_ACTM with single test On the next screen, do not change any other field except the following and set them as shown below: MODE: 12 NTAB_PUTSTATE: N TABNAME: <enter the correct table name> Click on Execute The export parameter ACT_RESULT should show 0. To verify if the inconsistency is fixed, call transaction SE14 > Extras > Database Object > Check and  SE14 > Extras > Runtime object > Check.
Read more

301 Redirect Using SAP Web Dispatcher

301 redirects are typically used to redirect accesses that include www to non-www or vice-versa. Example, when you call http://blogger.com, the call is redirected to www.blogger.com. An end-user may prefer to call a URL in any manner. You must ensure that all these calls are redirected to relevant URLs with content. SAP web dispatcher can be configured to send a redirect (301) to the client. To enable redirection add icm/HTTP/redirect_<xx> to the web dispatcher's profile file. The parameter uses the following syntax: icm/HTTP/redirect_<xx> = PREFIX=<URL prefix>[, FROM=<pattern for URL>, FROMPROT=<incoming protocol>, FOR=<pattern for host name:port>,TO=<new URL prefix>, PROT=<protocol>, HOST=<host>, PORT=<port number/name>] Let's say you want to redirect all the HTTP requests on mysource.com on 80 port to mytarget.com on HTTPS 443 port icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, FOR=mysource.com:80,...
Read more