cancel
Showing results for 
Search instead for 
Did you mean: 

PI-7.31 and NWA ResourceAdapter-config inboundRA, multiRepository entry is missing, after system restart

christoph_ostrop
Active Contributor
0 Kudos

in PI-7.31 doublestack in NWA

after maintaining ResourceAdapter Configuration, entry in field:  multiRepository

save the changed configuration,

after a system restart, the maintained entry in field:  multiRepository is missing

any idea ?

Chris

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hi Christoph,

I'm running PI 7.4 SP9 having the same issue losing the multiRepository entries after SAP is restarted.  Did you ever get a resolution from SAP?

Thank!

christoph_ostrop
Active Contributor
0 Kudos

Emmanuel Lauture wrote:

Hi Christoph,

I'm running PI 7.4 SP9 having the same issue losing the multiRepository entries after SAP is restarted.  Did you ever get a resolution from SAP?

Thank!

Hi,

no,

until now, we did as "workaround" to delay the start of SAP-PI,

so first start ECC-System, than second, start SAP-PI system.

regards

Christoph

JaySchwendemann
Active Contributor
0 Kudos

Hi Emmanuel,

if you are on SP9 I would open a call at SAP referring to already mentioned note 1935085.

For sake of completness: here's a screenshot of our properties of inboundRA

Cheers Jens

Answers (2)

Answers (2)

avinash_ayanala
Participant
0 Kudos

Hi Christoph,

I believe multiRepository is not an mandatory field, so Please once check whether the maxthread count is equal to the number of loggedon clients in SMGW TCODE with basis team and also check for other possibilities also.

Regards,

Avinash.

christoph_ostrop
Active Contributor
0 Kudos

Hi, Avinash,

attribute MaxReaderThreadCount is 10.

Chris

avinash_ayanala
Participant
0 Kudos

Hi Christoph,

If Local is set to false then default Gateway server and Gateway service of PI system

need to be provided and if set to true then enter the ECC system details while configuring inboundRA.

Regards,

Avinash

christoph_ostrop
Active Contributor
0 Kudos

yes, we have local = false

and maintained the sapgw26 and the server of the pi-system.

avinash_ayanala
Participant
0 Kudos

Hi Christoph,

have you checked the

default destination -->  XI_IDOC_DEFAULT_DESTINATION

given in the inboundRA is also present in the destinations of NWA and it is working correctly?

Regards,

Avinash.

christoph_ostrop
Active Contributor
0 Kudos

Avinash Ayanala wrote:

Hi Christoph,

have you checked the default destination -->  XI_IDOC_DEFAULT_DESTINATION

given in the inboundRA is also present in the destinations of NWA and it is working correctly?

Regards,

Avinash.

Avinash,

later on, when all sap-systems are running and working, the default-destination is working, yes.


when starting the pi-system, the ECC-system (ERP-backend) is not already running,

so at this time (the pi-system is starting) the connection to ECC-system will not work.

but this should not cause, that the attribute in field:  multiRepository  is erased and lost.

pi-system is starting first, => ecc-system is starting second.

Chris

avinash_ayanala
Participant
0 Kudos

Hi Christoph,

multiRepository is not an mandatory field i have configured my inboundra without that field and it is working fine, even though if you want that field to be configured then you can configure in this way

<ecc instance>=XI_IDOC_DEFAULT_DESTINATION_<ECC instance> it should also present in the destinations in NWA pointing to ECC system.

Regards,

Avinash.

JaySchwendemann
Active Contributor
0 Kudos

Hi Christoph,

did you see http://service.sap.com/sap/support/notes/1935085?

You talking about starting PI when backend system is not running got me curious. Maybe this is the same problem that we are facing, too.

Could you please check if your XI ADAPTER FRAMEWORK 7.31 is below the mentioned patch level of the note? If so, the note may well solve your problems. At least I would provide SAP with this information in your ongoing support ticket.

I could say for our system, that for XI ADAPTER FRAMEWORK 7.40 we are currently on SP 5 Patchlevel 0 so the note would apply for us. Currently checking if update is feasible.

Thanks and kind regards

Jens

JaySchwendemann
Active Contributor
0 Kudos

Hi Christoph,

being curious: Could you resolve your issue yet?

Cheers

Jens

christoph_ostrop
Active Contributor
0 Kudos

Hi, Jens,

sorry but not yet !

> did you see http://service.sap.com/sap/support/notes/1935085?
>

we found out in testing, that the entry is going lost when the sap-backend is not available when pi-system is starting up. so it looks, that the mentioned sap-note 1935085 is the solution to our issue,

but ....

to update the pi-system is now much more complicated by sap, forcing the customers to use SUM (instead of JSPM) and by forcing the customers to use SMSY, MOPZ in solutionmanager.

so, i looks that we first have to update our Solutionmanager to 7.1, before beeing able to patch the PI-systems .......

it really is extremely frustrating to use sap software

Former Member
0 Kudos

Hi Christoph,

we have same issue and we are not realy happy with PI 7.4 java only version. Otherwise when we are trying to test our message mapping then the system hangs and we always have restart the ESR. We have lot of file to IDoc integrations that takes up all CPU resources. You can find similar discussion here(http://scn.sap.com/thread/3559066).

Kind Regards,

Fatih Kokce

christoph_ostrop
Active Contributor
0 Kudos

        no one has any idea about it ?

i already opened a support-ticket, but no answer until now .......

JaySchwendemann
Active Contributor
0 Kudos

We have the same issue with PI 7.4 AEX. However no solution yet.

Kind regards

Jens