Threads per Adapter Type and Receiver Channel



You can increase the scalability at Adapter and Channel level with these two options:

Maximum Threads per Adapter Type:

You can control the thread allocation for each adapter by customizing messaging.connectionDefinition property in the service SAP XI AF Core using the following syntax:

messaging.connectionDefinition=(name=global,...)(name=<AdapterTypeIdentifier>, Send.maxConsumers=<a>, Recv.maxConsumers=<b>, Call.maxConsumers=<c>, Rqst.maxConsumers=<d>)

with <AdapterTypeIdentifier>=<AdapterType>_<Namespace>
(e.g.: File_http://sap.com/xi/XI/System)

Send.MaxConsumers indicates queue for asynchronous communication from AFW to IS
Recv.MaxConsumers indicates queue for asynchronous communication from AFW asynchronous
Call.MaxConsumers indicates queue for synchronous communication from AFW to IS
Rqst.MaxConsumers indicates queue for synchronous communication from IS to AFW synchronous

Check SAP Notes 1084161 and 1129604 for more details.

Maximum Threads per Receiver Channel:

One slow back-end system can block all the threads in an Adapter type.

Such situation can be avoided by controlling messaging.system.queueParallelism.maxReceivers parameter in SAP XI AF Messaging service.

This parameter specifies the maximum number of parallel worker threads per queue, based on the receiver fields of the processed messages. If this is set to value 'm', any receiver channel can use a maximum of 'm' threads for processing. Remaining threads will be available for other Channels in the Adapter type.

Check SAP Note 1136790 for more details.

Multiple threads will obviously not be available for EOIO type quality of service.

You may check this book out if interested in learning PI:
The Essentials on SAP NetWeaver Process Integration - A SAP Mentor 2010 Series

Comments

  1. AnonymousAugust 1, 2011 at 8:40 PM

    hi
    where I can get AdapterTypeIdentifier details ?

    ReplyDelete
  2. Hello ITAugust 2, 2011 at 5:52 AM

    You can find the list of adapters installed and their adapter identifier by calling http://host:java-port/MessagingSystem/monitor/systemStatus.jsp

    ReplyDelete

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 created i
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