SAP Process Integration for Basis Consultants

 Share it on  Facebook, Twitter, LinkedIn, Google+

Here is a list of PI blog posts relevant for Basis support.

SAP Process Integration for Basis Consultants

SAP Process Integration

They used to call it SAP Exchange Message Broker.
Basic mechanics of PI message processing
Basics of SAP PI cache
Load balancing SAP PI
How do Integration Engine, Adapter Engine and Integration Builder tools know how to contact each other?
How to install external drivers and SOAP Axis Adapter?
How to check message status using database SQL queries
How to turn off basic authentication for RNIF Adapters (the SAP's way)
How to find largest PI messages between two time stamps
Why are channels in error status although underlying problem is resolved?
HOLDING status messages are driving me mad! How-to deal with it (the messages)
No Adapter Registered. Legalizing the illegal communication channels!
Which services and applications constitute a healthy SAP PI
Why is File Sender channel picking up a file? How can it forget its purpose of life?
Once you remind them of their purpose of life, how to increase throughput of File Sender channels?
Why JDBC Sender channel is not polling? These Communication Channel should remember their duties
You changed the RFC metadata in ECC, how to force the update in PI channel
How to stop message failure during SAP J2EE startup?
It's a mess, but if you have to change the passwords, understand how complex it could be.
Dealing with SSL handshake errors
Getting rid of hard-to-get-rid of certificates in Key Storage
Unlimited strength or unrestricted jurisdiction policy files required for encryption and decryption
How to migrate SLD server used by SAP PI?
SAP PI data are mostly XML. If you are running PI on Oracle, use this feature to better store and retrieve XML data.

Useful Tools

XPI Inspector - The most important debug tool for SAP PI
When in comes to troubleshooting issues in PI, Web Diagtool is the lesser alternative to XPI Inspector
How to analyse a heap dump? The same drill using an older version of MAT.

Performance Tuning based on Errors

Large message causes J2EE crash and subsequent attempts to restart
Messages fail intermittently with 401 error
Reduce the devil's exit code (OutOfMemory errors) in SAP PI
Tuning threads per adapter and receiver channel
Maximum number of parallel connections by JDBC receiver
Faster processing of backlogs
You know SAP PI is an application on top of SAP NetWeaver and it does not use all of its services. So why run them at all?
Again... SAP NetWeaver is not optimized for PI, you need to do it yourself!
There is a scope to improve JDBC receiver channels.
JDBC service startup slowing down SAP J2EE startup
Something as simple as IDoc acknowledgement can cause system issues.

Integration Builder and Transports

Use CTS+ or CMS for transports. Disable File System transport.
How to import IDoc metadata into Integration Builder
How to recover deleted PI objects
You locked your own object in Integration Builder? No need to contact Basis!
Fixing OOM errors of Integration Builder

Data Volume Management in SAP PI

Messages are not deleted by archive and delete jobs
Getting the raw data dump of Seeburger AS2 message and MDN
Reorganizing SAP PI message performance header data - SXMSPFRAWH
Delete unnecessary workitems
Archive Job failure (503 error)
Automate SLD change log cleanup

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