Message Prioritization

In layman terms, message prioritization = queue prioritization,
& this can be achieved by setting up a filter via SXMB_ADM, registering the queues in SMQR.

Following links will help you to perform this -

https://archive.sap.com/kmuuid2/59e837d3-0201-0010-c096-dc1869733413/How%20To%20Prioritize%20Exchange%20Infrastructure%20Messages%20on%20the%20Integration%20Server%20(NW2004).pdf


https://help.sap.com/doc/saphelp_nwpi71/7.1/en-US/7b/94553b4d53273de10000000a114084/content.htm?loaded_from_frameset=true

AMOR FATI - LOVE OF FATE

IDOC Packaging

IDOC PACKAGING / COLLECTION


In some scnearios, we have to collect the idocs and dispatch them collectively.

For ex:

1. Collect of Purchase Orders and create a file at EOD everyday

2. Create a file with a maximum of 100 Idocs/records only. So, set the package size as 100 here.

This can be achieved by IDOC sender adapter. You need to define a package size in the adapter.
The package size defined here will be used to create IDoc packages in PI.

Some configuration needs to be done in ECC to work this -

In the partner profile of the Idoc,

Select the collect idocs options and also proivde the package size.

Report RSEOUT00

This report can be executed or scheduled as a background job to send the IDocs.

Sample Payload in SXMB_MONI

Challenges -

Ex. In a package of say 500 IDocs, if the field of an IDoc has wrong value which leads to mapping error in PI. The idocs may get stuck in queues.

So, we need to reprocess the idoc package from ECC.

When sending an IDoc package (assume N IDocs) if it goes into a data mapping error, we can fix the data at the source and resend the whole package again as follows-

1. In PI, find out what is causing the error & the idoc that contains the data.

2. In SXMB_MONI - extract all the idoc numbers in error state

3. Edit the error idoc in WE02

4. In ECC, use the report RC1_IDOC_SET_STATUS to change the status of the IDocs (to Ready for Dispatch)

5. Use RSEOUT00 and send the N IDocs again to PI

AMOR FATI - LOVE OF FATE

PI TO PO MIGRATION

We cannot upgrade from dual stack PI to single stack PO.

All integration content has to be moved/redesigned and tested

• Connectivity
• Communication Channels (Replace all ABAP adapters with JAVA adapters)
  • IDoc -> IDoc_AAE
  • XI -> SOAP (XI 3.0)
  • HTTP -> HTTP_AAE
  • WS -> WS_AAE
• RFC Destinations
• Use Destinations in NWA to create HTTP and RFC connections to backends

• Mapping
• No more use of ABAP/ABAP-XSLT: Redesign in Java!
• Keep on using Swing Client! NWDS/Eclipse is not comfortable enough

• Routing
• Classic Routing -> Integrated Configuration (ICO)
  • Make sure you understand the settings for Staging & Logging!
• Multi-Adapter Engine Usage (ICO-ICO)
• Usage of iFlows & Folders in NWDS/Eclipse (optional, but recommended)

• BPM
• Redesign ccBPMs: replace BPM by Adapter Modules (e.g. Async-Sync Bridge) or Collect BPMs
• Create BPM processes to replace ccBPM

• Basis
• CTS+ now e.g. via ABAP Stack of SAP Solution Manager
• User Management now locally (UME) or connected to Active Directory
• Set up NWDI for BPM Design Time Repository & Transport

• Monitoring
• No more SXMB_MONI
• All messages are visible in PIMON

• Alerting
• New Message based alerting available, configured in DIR/NWA

• Backend Systems (SAP ECC/ERP, CRM, SRM, …)
• IDoc – WE21: New IDoc Port to connect with IDoc_AAE via RFC Destination type T (SAP Gateway)
• ABAP Proxy – SXMB_ADM: Point to Adapter Engine RFC Destination instead to Integration Engine (configured globally or per outbound Service Interface/Proxy)

Area	Activity	Objects
SLD	In case you are using a central SLD, point your PO system there. Otherwise you Export/Import	> Software Products > Software Components > Technical Systems > Business Systems
ESR	Export/Import via TPZ all relevant objects. Decide which source system to use (DEV/QAS/PROD)	> Software Components
DIR	Migrate all Channels & Routings using the tool where possible	> Communication Channels > Business Components > Routing Objects
NWA	(Re-)define the relevant objects in NetWeaver Administrator	> Keystore > Destinations > User Management > Alert Configuration

INT4 & FIGAF can be used for automated testing of interfaces.

AMOR FATI - LOVE OF FATE

MESSAGE PACKAGING

MESSAGE PACKAGING

We can improve the performance of message processing in SAP NetWeaver Process Integration (PI) by grouping together asynchronous messages in packages and then processing each message package in one LUW.

We configure how packages are created in the sender system and in the central Integration Engine. Packages can be received and saved in the receiver system. They are then processed as individual messages.

Sender adapters handle message packages in different ways.

●      The Advanced Adapter Engine can receive packages but not create them.

●      The Business Process Engine (BPE) can process packages

●      The IDoc adapter sends all messages that have the same interface to the Integration       Server in one RFC call. It can send IDoc message packages to an IDoc receiver.

●      The plain HTTP adapter cannot process packages.

●      The Web service runtime can receive packages but processes the messages individually.

To use message packaging, you must first activate it.

How to Activate ?

- SXMB_ADMIN - CONFIGURATION - CONFIGURE INTEGRATION ENGINE 

- Under PARAMETER Categories select RUNTIME category

- choose change configuration

- Select the entry with the category 'RUNTIME', parameter 'PACKAGING', current value '0' (packaging deactivated), and the default '0' (no packaging).

- Set the current value to 1.

Packaging is now activated.

CONFIGURE MESSAGE PACKAGING

We can configure message packaging so that it suits your requirements. To do so, you define configuration types that you then assign to the different locations where message packaging can be used.

These are the seven locations in pipeline processing where packages can be created.

To make a global package configuration such as this more specific, you can assign a configuration type not just to a specific message packaging location, but also to a specific sender or receiver ID. This configuration type is then applied instead of the global configuration for those messages that correspond to this sender or receiver ID.

To create configuration type - 

Call SXMS_BCM and switch to change mode.

Create a new configuration type by using one of the following two methods:

○       Use the DEFAULT configuration type and modify it to meet your requirements

○       Add a new entry

To assign a configuration type to a packaging location, use transaction SXMS_BCONF.

There are three parameters that you can use to define configuration types:

●      Wait Time

Maximum wait time until the queue is processed when the maximum number of messages has not yet been reached.

●      Number

Maximum number of messages per package.

●      Package Size

Maximum total size of all messages in package in KB.

SAP ships the configuration type 'DEFAULT', which is assigned by default to all locations where packaging is possible, and which is available for all queues:

●      Wait Time: 0 seconds

●      Number: 100 messages

●      Package Size: 1000 KB

Since the wait time in this case is 0, there are no delays in message processing once packaging has been activated. The messages are simply processed quicker.

Monitoring Message Packaging

Transaction XMSPKSTATCNF to configure package statistics.

Transaction XMSPKSTATCNF to configure packaging.


                                                             

                                                            AMOR FATI - LOVE OF FATE

Proxy Configuration between PO & ECC

A)

First, we need to create a Logical System in ECC which will point to PO system. Go to tcode - BD54  & create a logical system.

B)

Then, depending on whether your system is single/dual stack, create a RFC destination from SM59 which will point to PO system.

If its a Single stack - create Type G connection

           Dual stack - create Type H connection

while creating we should follow a standard Path Prefix for both Type H & Type G connection

Connection Test should result in Status 200

ex: Type H

Target Host : Hostname of PO system

Path Prefix : /sap/xi/engine/?type=entry

Type G

Target Host : Hostname of PO system

Path Prefix :   /XISOAPAdapter/MessageServlet?ximessage=true

C)

Go to SXMB_ADM - Configuration -  Select Category as Runtime 

select parameter -  IS_URL

Value =  dest://<your_rfc_destination>

D)

We will create one more TYPE G - RFC Destination for PROXY generation 

RFC dest. name - SAP_PROXY_ESR

Provide Host Name

Path Prefix: /rep

E)

Go to Tcode - SLDAPICUST & configure entry for PO system in ECC system.

                                                          Amor Fati - Love of Fate