SAP PI7.31 Java Single Stack - Default Delete Job Retention period

Hi
anybody know where the Default Delete Job Retention periods can be set ? I'm on a SAP PI7.31 Java Single Stack.

thanks - in milliseconds - very precise.
1) NWA-->Configuration-->Infrastructure -->Java System Properties
2) Go to Services tab, and type XPI and select – XPI Adapter: XI
3) Type “persist” in Properties filter
4) for example Set Retention period in Milli seconds and save
2592000000 = 30 Days

Similar Messages

Unable to see Payload in SAP PI7.31 Single stack

Hello Experts,
We have a scenario of Mail as sender and ECC as reciever using Proxy. We are using SAP PI7.31 single stack.
Here we are reading the file from mail attachment which is in CSV format and sending the data to ECC successfully.
But while to check the payload in Message Monitor, while click on the "Mailattachement-1.csv" it is opening with "No Message Selected".
Can someone please let me know how can I check the payload of the attachement.
Thanks
VR

Hi VR
Check this parameter:
NWA -> Configuration -> Infrastructure -> Java System Properties -> Services -> XPI Service: Messaging System, set property messaging.SyncMessageRemover.removeBody = false
Check also the general parameters for tracing and logging
Saving Message Versions in the AAE (Local Message Processing) - Advanced Adapter Engine - SAP Library
Regards
Javi

Idoc Acknowledgements in SAP PI7.31 Single stack

Hello All,
We are migrating from SAP PI 7.0 to SAP PI7.31 single stack.
in Existing landscape(SAP PI7.0) - sender system ECC is receiving the acknowledgements(ALEAUD) for the idocs sent to PI system where in the port is different i.e. port is receiving back with different Partner Number.
But in SAP PI7.31 single stack, ECC is recieving the acknowledgmenets(ALEAUD) as same as the sender partner number of the idoc sent to PI 7.31 system.
can someone please explain me if it is possible to implement the same functionality as per SAP PI7.0 in SAP PI7.31 single stack as well or is this the Limitation of the product.
Thanks
VR

Hello Experts,
Can someone please suggest me if SAP PI7.31 Single stack can send ALEAUD with different partner number to ECC.
Thank you
VR

Default Delete Job on AE ?

Hi,
On RWB -> Component Monitoring ->Adapter Engine -> "Status" Tab -> Background Process:
There are three background jobs on Adapter Engine:
Default Delete Job
Default Recover Job
Default Version Archive Job
We have first two jobs active.
Since we have scheduled archive and delete in ABAP stack, and to my knowledge, the message persisted in Adapter Engine will goes to different database table from ABAP stack.
I would like to know how the Default Delete Job running, can it be customizable ?
Thanks in advance.
Liang

Anyone has idea about the delete job ?
My investigation showed that persisted message goes to following tables
For Integration Server: SXMSPMAST, SMXSCLUR, SXMSCLUP etc.
For Adapter Engine: XI_AF_MSG
For BPM: SWWWIHEAD, SWFRXI*
For Integration Engine, we can define retention period for message archiving and deleting.
For Adapter Engine, there is default archive and delete job I mentioned in above message.
Just do not know how to customize those jobs.
Thanks
Liang

IDOC Status, Tracking in SAP PI/PO Single Stack

Hi All,
My PO version: 7.4, SP4. I am not sure my questions below are still a limitation in current PI/PO single stack systems, and hence requesting your help for the same.
1) Is there a way we can track outbound idocs in SAP PI/PO single stack similar to PI abap stack IDX5? ( Note:- I couldn't find any option in IDOC monitoring in single stack SAP PO 7.4, SP4)
2) IDOC status is always 0 in SAP PO 7.4 single stack IDOC monitoring. I am not sure if this status is just specific to my PO system. Any setting needs to be applied?
ps: Please post only relevant answers/solutions
Thanks,
Praveen Gujjeti
Message was edited by: Praveen Gujjeti

Hi All,
As per SAP help: Comparison of IDoc Adapter (IE) and IDoc Adapter (AAE) - SAP NetWeaver PI Reference Documentation - SAP Library idoc status and tracking not supported in current PO versions. May be SAP will add this feature in upcoming PO versions
Auditing, Monitoring ,and Tracing Functions
Attribute/Feature
IDoc Adapter (IE)
IDoc Adapter (AAE)
ALE Audit
Supported
Supported
IDoc tracing
Supported (transaction IDX5)
Not supported
IDoc monitoring
Transaction IDX5
Integration with channel monitor and message monitor (as part of Advanced Adapter Engine monitor)
Status tracking -SYSTAT
(analysis and further processing of messages that have not been processed)
Not supported
Not supported
RFC monitoring
Supported
Not supported
Message persistence in the IDoc adapter
Supported
Message correlation information can be stored in IDoc adapter.
Not supported.
Message is persisted in messaging system with correlation data persisted in adapter.
Regards,
Praveen Gujjeti

How to find Traces in SAP PI 7.3 java only stack

Hello Experts,
How to find the trace logs and pipeline steps in sap pi 7.31 java only stack, which we will get in below areas,
1. In sap pi dual stack , SXMB_MONI (abap stack) in window 1
2. In sap pi dual stack , monitoring--->integration engine--->message monitoring----> xml messages(data base)
I already found some blog related to the logging but i doesn't help to find the traces which we get in SXMB_MONI (window 1, trace)
http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/09/18/tracing-in-sap-pi-731-single-stack
Your suggestions are highly appreciated.
Thanks & Regards,
Venkat

Hi,
In Single stack we go for ICO instead of classical configurations(Pipe line steps(SA,RA,RD,ID)).
Link you are referring is to find the display of traces that you put in your UDF or Java mapping or XSLT mapping .
If you want to see the traces/payloads of end to end flow ,then you can see the same either in your communication channel monitoring/receiver channel or via message monitoring/adapter engine-->message log
If you want to see payloads in the below steps .you can also do so by following the below link.
Message Staging and Logging Options in Advanced Adapter Engine of PI 7.3x
Processing Step
Description
AM
After mapping step, but before outbound schema validation
VO
After outbound schema validation
BI
After sender adapter processing, but before inbound schema validation
MS
Before mapping step
VI
Before scenario look-up step (check if scenario is local Advanced Adapter Engine based or dual-stack based involving Integration Engine)
Regards
Venkat

How to track the Inbound child IDOcs in PI 7.4 Single stack

Hi Friends,
I would like to know the procedure of tracking the Inbound child IDocs in PI 7.4 Single stack.
Here is the detailed description.
Say we are getting the data from third party system and the message may have multiple IDOcs in it. The message has processed successfully from PI and reached to the target system(ERP). So, now my question is how to track the IDOc count with in that message.
Please suggest on the same.
Thanks in Advance,
Venkateswarlu.

Hi Hareesh,
Thanks for your inputs. According to the link IDOC Status, Tracking in SAP PI/PO Single Stack I am thinking the required funcionality is not there in PO 7.4, but still i would like to have little more clarity before moving further.
I will explain what what was happening in PI 7.11 so that you can understand what i am looking for in PO 7.4.
We will get the data from third party system in xml format, we had to search for the messages based on interface name and time range within SXMB_MONI. After getting the result(say the output is 100 messages), we will download the values of "Outbound Reference" field(which is a key to find the child messages for messages resulting in an Interface Collection). Below is the snap of Outbound Reference field for your reference.
Now we will go to the table IDXRCVPOR in SE16(within PI) and put the values of Outbound Reference field in Text 24 and execute. Here we will get all the child messages.
Now please let me know if this kind of scenario is possible in PO 7.4.
Thanks,
Venkat.

In Spool Retention Period adding - "Delete After 365 Days"? Is it possible?

Team,
rel 4.7
I have the following retention periods in the spool drop down:
Delete After 1 Days
Delete After 2 Days
Delete After 3 Days
Delete After 8 Days
Do Not Delete
Question: I want to add other periods like 365...
where can I maintain it.
Thanks
Naved
PS. These retention periods carry over to SAPinBOX and populate expiration date field
Message was edited by: SAPna2000
Message was edited by: SAPna2000

Hi,
I know Job retention period by using T/code : SO16--> document org.
Check this may help.
Lanka

Archiving and Deleting of XML Messages in SAP NetWeaver PI 7.31 single stack

Hello my XI friends!
Need step by Step Guide to Archiving
and Deleting of XML Messages in
SAP NetWeaver PI 7.31 single stack
Similar to these instructions
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0afdd69-a8a7-2d10-7e9a-cbf6fa21c5a7?quicklink=index&overridelayout=true
Regards,
Rinaz

Please check the below blog for archiving java only-(XMLDAS)
http://scn.sap.com/community/pi-and-soa-middleware/blog/2011/11/16/aae-archiving-in-sap-pi-711-with-xmldas
For deletion there is standard delete job..
https://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/b2e0036b156ff4e10000000a42189b/frameset.htm
Message was edited by: Hareesh Gampa

SAP PI 7.3 Single stack- Set tracing and logging

Hi experts
We have configured a SOAP to SOAP sync scenario in SAP PI 7.3 single stack(Java Only).
I have sent some test messages from WSNavigator to PI .
But when i checked messages in adapter engine, it is showing*"Unable to retrieve payload or you don't have sufficient authorization to view the content" I am able to monitor payloads of Async messages.
How can we set Logging and trace levels in Single stack PI? I couldn't find any options in RWB os NWA.
Thanks,
Dhanish

Hello Dhanish,
As it was stated by Kenneth in his post, if you would like to see payload of a synchronous message in Message Display Tool (e.g. from Runtime WorkBench), you should set value of property messaging.SyncMessageRemover.removeBody of J2EE service XPI Service: Messaging System to 'false'. Please note that this affects only synchronous messages in final states (DLVD and FAIL).
Regarding the second part of your question - logging. In PI 7.3, you can persist the message in Adapter Framework in two ways - stage it or log it. Staging allows you to edit/restart the message later from the stage where the message was persisted and is relevant for asynchronous messages; logging allows you to only display the logged message and is relevant for both synchronous and asynchronous messages. Please also note that staging affects performance of message processing more greatly than logging, extensive staging (e.g. staging on several processing stages) can even be a reason of performance degradation for processed messages, so if you only need to display details of the message on different processing steps in Adapter Framework, logging should be sufficient. Both staging and logging can be configured using properties xiadapter.stage.conf (for staging) and xiadapter.logger.conf (for logging) of J2EE service XPI Adapter: XI.
Regards,
Vadim

PI 7.4 Single Stack - OS Command and Java Mapping Trace

Hi,
Since ABAP stack is not avilable how to use the OS command and also want to know how to check the trace for java mapping since sxmb_moni is not avilable.
Please send me some link for 7.4 or 7.31 single stack document.
Thanks
Jignesh shah

Jo Jignesh,
Please see the document below.
Mapping Trace in SAP PI 7.31 Single Stack
Regards,
Jannus Botha

Install SAP BW Java Stack on SolMan server

Hi.
Regarding the single stack requirement coming in with SAP BW 7.4 my customer ask me if it is possible to move the Java Stack to the SolMan server because it has more or less nothing to do. But regarding the actual definition I am not sure if it is possible.
I am not an infrastructure guy so I like to identify if this can be handled like this in line with the SAP guideline only and then start an internal discussion.
Thanks in advance,
Nils

Hi Nils,
Installing a second Java stack on the same machine with a different SID is perfectly fine. Personally I don't recommend it as two different SAP products (different NetWeaver versions) will be running on the same Windows, definitely requires more maintenance effort than managing two instances on different servers. The downtimes will effect both servers, one of them may encounter a server-related problem while the other working fine etc.
Also make sure you have enough resources for both of them.
BR,
Alper Somuncu

Want to learn SAP PI 7.4 Single stack

Hi Experts,
I am a beginner in SAP PI and started by journey with SAP PI 7.0. Now, we are upgrading it to SAP PI 7.4 single stack.
I want to learn it as much as possible before the migration but when I search for the topics in SCN, I am getting confused with the different topics and its naming conventions explained. (For Eg PI and PO). So, will it possible for you experts to provide me the links which can actually help me to get the full depth knowledge on PI 7.4 (Single stack). Am just hoping to be a productive member of this SAP family:)
Regards,
Adarsh

Hi Adarsh,
SAP Process Orchestration is the new name of SAP Process Integration (SAP PI). SAP changed the name with the release 7.3 to include the additional features of SAP NetWeaver Business Process Management (nBPM), Advanced Adapter Engine Extended (AEX) and SAP NetWeaver Business Rules Management (BRM).
Source - Latest version is SAP PO 7.4 or SAP PI 7.4 (commonly known as of now). Good part is that PO 7.4 license includes BPM and BRM. Till PO 7.4 SAP still provides the dual stack (ABAP + JAVA) option to install. But going forward it would be single stack (JAVA) only i.e. only swing tool for ESR and ID or NWDS. no more transactions/tocde.
From a developer standpoint:
You got all adapter based on JAVA. IDOC and HTTP are now IDOC_AAE and HTTP_AAE, also proxy scenario can be done using SOAP adapter XI protocol and there is no ccBPM.
Regards,
Sachin Dhingra

New BW 7.0 System (ABAP+Java) as two single-stack Systems? How?

Hello,
as of the current recommendation not to install a dual-stack system anymore, we are planning to setting up our new BW 7.0 sandbox-system as two single-stacks.
In my understanding, I have two install two separate systems (1. AS ABAP, 2. AS JAVA) and connect them each other. So each system should have it's own SID?
Procedure: I first have to setup the AS ABAP with SID=NWA and then afterwards setup the AS JAVA with SID=NWJ - and connect each other afterwards (e.g. RSPOR_SETUP and so on...).
Or am I allowed to use the same SID(=NWA) also for the AS JAVA (as it is in a dual-stack installation)? If so, am I allowed to use the same system (OS will be windows 2008) for them? In the Installation Guide I found for NW 7.0 EhP2, they still mention the dual-stack installation...
So, if you have a dual-stack installation, it looks like this:
Host: nw.sap.company.local / SID: NWA, Instance: 00 (AS ABAP) + NWA, Instance: 00 (AS JAVA)
How should it look now? Like this:
1. Host: nw.sap.company.local / SID: NWA, Instance: 00 (AS ABAP) + NWJ, Instance: 00 (AS JAVA)
2. Host: nw.sap.company.local / SID: NWA, Instance: 00 (AS ABAP) + NWJ, Instance: 01 (AS JAVA)
3. Host: nwa.sap.company.local / SID: NWA, Instance: 00 (AS ABAP)
+ Host: nwj.sap.company.local / SID: NWJ, Instance: 00 (AS JAVA with EP_CORE, BI_JAVA, ...)
In case of option 3, do they have to use their own DBMS?
Thanks in advance!
BR,
Markus

Hi Oliver,
thanks for you reply!
>
Olivier CHRETIEN wrote:
> Yes, each system (abap and java) will have its own SID.
> If you have sufficient hardware ressources, it is possible to install these 2 systems on the same physical host.
It's virtualized using XenServer, so I can decide to use a "large" system/virtual machine containing both ABAP and Java or to have two separate systems/virtual machines... I prefer the second solution (each with it's own DBMS/MSSQL2008) even if it's a "waste" of resources in comparison to a dual-stack system (2x OS/Windows, 2x DB/MSSQL-Server).
> You could also use MCOD to use only one database instance with 2 schema but I personally don't like this solution.
> The key to not install anymore as a dual stack system is to have independency between java ans abap.
I had a look at this also... I think there are no advantages (beside resources), because when you have to do some maintainable at the DBMS (e.g. OS updates), more than one system is affected.
> The installation will be more complicated than a dual stack but it will be easier to manage, be more reliable, easier to patch and upgrade.
Maybe, but you need an additional (hardware-)resources - as seen above. But anyway, thanks. We will try with separate hosts.
Regards,
Markus

Single stack vs. Dual Stack - Why does SAP recommend single stack?

Hello SAP,
I am a business partner who specializes in infrastructure consulting for SAP solutions. The SAP Consultants I am working with recently have been recommending that customers install single stack systems. I would like to know why? Are there problems with dual stack systems? Is SAP changing things in a later release and they want customers to be prepared for the change?
From an infrastucture point of view this recommendation combined with SAP NetWeaver architecture will result in an explosion of SID names which leads to an explosion of application server instances and DBMS instances and an explosion of installed servers. I know it is possible to combine SIDs into a single DBMS using MCOD and to have multiple application servers in a single physical server, but there are issues with mulitple application server instances and MCOD use which make normal maintenance operations difficult.
I think it would be much better for customers to install dual stack systems and simply adjust the SAP profile parameters to disable one stack or the other. This way, you could still have 1 stack per application server instance and you would not be have to be creative with SAP SID names!!! Creating a DBMS instance or installing an additional server is not a simple nor economical proposition.
Regards,
Zaz

I am a business partner who specializes in infrastructure consulting for SAP solutions. The SAP Consultants I am working with recently have been recommending that customers install single stack systems. I would like to know why? Are there problems with dual stack systems?
The problems are:
- difficult to size and maintain - Java + ABAP will fight for resources (memory,CPU) and there´s not much one can do to tune if either ABAP or Java as dual stack instance on a single box is running nuts (for whatever reason).
- System copies via R3load - if you want to copy a huge system (let´s say ERP 6.0 + Java stack) you need to use sapinst + R3load to do the copy. Imagine if the system is 1 TB or bigger, this is very time consuming
- Upgrades are complicated - if you upgrade a dual stack system you need to run two PREPARES and two upgrades at the same time - there are sync points each upgrade wait for the other to finish --> difficult to plan in sense of runtimes and even more notes/preparation to do (a dual stack SolMan upgrade from 3.2 to 4.0 had almost 100 notes (technical!) and two upgrade preparation guides...)
- interdependencies - example: you run ERP + EP + BI-Java on one system. You upgrade your BI (which is on a different box) to a new support package. Since the BI-Java need to be in sync with the BI ABAP support package you need to upgrade the EP too - and since there´s a direct dependency (doublestack system) you will need to install support packages on your ERP. So you finally end up in having dependency chains that a total different system (BI) will force you to upgrade/patch your ERP. And if you have e. g. a CRM connected to the same EP you will need to patch that too...
Is SAP changing things in a later release and they want customers to be prepared for the change?
No - the possibility of having a dual stack installation will be still there.
From an infrastucture point of view this recommendation combined with SAP NetWeaver architecture will result in an explosion of SID names which leads to an explosion of application server instances and DBMS instances and an explosion of installed servers. I know it is possible to combine SIDs into a single DBMS using MCOD and to have multiple application servers in a single physical server, but there are issues with mulitple application server instances and MCOD use which make normal maintenance operations difficult.
I agree - MCOD is not a good solution for this problem.
I think it would be much better for customers to install dual stack systems and simply adjust the SAP profile parameters to disable one stack or the other. This way, you could still have 1 stack per application server instance and you would not be have to be creative with SAP SID names!!! Creating a DBMS instance or installing an additional server is not a simple nor economical proposition.
There are 36 * 36 * 36 (minus a few reserved) names for SIDs- this should be enough - also for the biggest customers
Of course one could install both and disable the one you don´t need - but this won´t help in dependency thing. If you e. g. install a dual stack instance for CRM and disable the Java part, you can nicely run it. In case of an upgrade, you will need to upgrade the Java part too (see above) although you don´t use it. The upgrade will detect the doublestack and wait for the java instance to be upgraded too. Same is true vice versa. And believe me: you don´t want that
In fact it is better to separate - that´s at least our experience. The main no-go for such a configuration on our side was the dependency thing. Since they are there and you can´t do much about them we decided to have a 1:1 relationship for ABAP backend and Java "frontend". You will get more instances (and names and databases) but you can patch applications independently from each other. So an implementation of a BI patch won´t imply that you finally also patch your ERP production and other systems that connect to that portal.
There are virtualization techniques available to not need more boxes, you can consolidate them on one machine as if you were installing a dual stack so that is not really an issue. This depends, of course, on the platform and database you use (e. g. Oracle does not support production installations in VMWare). We use for our Java instances Solaris on Opteron (or Intel 64bit) and zones/containers and for the ABAP part we use Linux + Xen. Both virtualization methods come with the OS (so no additional $$$) and both are supported by SAP.
The propagated advantage of having a dual stack installation (shared memory access etc.) is so small that it doesn´t outban the additional complexity - which is definitely there.
I hope those arguments will help to understand SAPs (and the consultants) position - get back if you want more
Markus

SAP PI7.31 Java Single Stack - Default Delete Job Retention period

Similar Messages

Maybe you are looking for