cancel
Showing results for 
Search instead for 
Did you mean: 

No Message generated for the File to File Scenario - PI 7.3 Dual Stack

former_member596513
Participant
0 Kudos

Hi All,

I have just created a dummy CS in PI Dev (Inbound for XML file to XML File) – to confirm that we have all the config in place. This is only a dummy one so I might have missed something.

All the design objects and Config objects are created and activated.

However, I am unable to see any message in SXMB_MONI, no queue in SMQ2 and SMQ1 (ECC and PI) and no channel activity in Monitoring the communication Channel.

What am i doing wrong and what have i missed?

I am also not getting any details in Java logs in NWA.

I have not worked that much in PI 7.3 so am not comfortable specially the channel monitoring.

I have also tried to check the channel monitoring via Monitoring component but this is totally different than what i have been used to.

Please advice.

The file paths as created by Basis are with the below format-

\\<SERVER Name>\<File paths>

The server is on Windows so the alternate file path is like - S:\usr\sap\<sysid>\<Interface>

I have always used the UNIX / LINUX system level file paths in my previous experience as /usr/sap/interface/......

Also, Basis have given the file permissions as 666 and i have now requested for full read and write permissions.

I have seen that the file interfaces in previous releases have errored with the file permissions 666 which I had to get changed to 777.

The parent directory and the directory at the same level have 777

Please help as I really need to confirm if we are ready to start the development.

This client has not developed any PI interface in this environment.

Regards,

Archana

Accepted Solutions (0)

Answers (1)

Answers (1)

gagandeep_batra
Active Contributor
0 Kudos

Hi Archana,

did yo check the status of sender CC?

whether that is can  pick the file or not:

http://host:port/mdt/channelmonitorservlet

and also try to create some common sharing  directory to pick & post the file on same network

give path  with ip like "192.XXX.XXX..34"

Regards

Gagan

former_member596513
Participant
0 Kudos

Hi Gagan,

I have tried the channel monitoring and it is empty. Even in NWA channel monitoring not a single channel (with or without errors or inactive) is listed.

Can this be that there is some configuration missing or not ok with Central Adapter engine when the environment was installed?

Basis has today set up a common file share across so that i can upload the file from ECC into PI via the standard transaction.

However that is also with the server name like \\<SAPPIxxx>\<Sys ID>\<file path>

Please help.

Regards,

Archana

Harish
Active Contributor
0 Kudos

Hi Archana,

It seems there is some issue with your adapter engine. Please try to push the data from RWB (to integration engine) and check the receiver channel in monitoring.

regards,

Harish

former_member596513
Participant
0 Kudos

Hi Harish,

I have tried to doe as you suggested but i am getting the error that no details are found for the receiver agreement and the component.

RWB - Integration Engine - Test Message and then gave all the details and uploaded the payload.

I am also getting some authoriastion error code 401.

I have send these details to Basis so that they can replicate the issue.

Any ideas from your experience and knowledge?

Anything that i can do from my side to see what is going wrong?

Regards,

Archana

Harish
Active Contributor
0 Kudos

Hi Archana,

the error -  no details are found for the receiver agreement and the component.

--> problem with interface determination or receiver agreement configuration (or cache), check if you have right receiver interface and receiver system in MONI.

error code 401 --> Authorization problem. make sure you are pushing the msg under integration engine and using right user id and password.

reagards,

Harish

former_member596513
Participant
0 Kudos

Hi Harish,

I hails found.

I have double checked and the configuration is ok.

Only issue is when i test the Configuration via Tools -> test Configuration it also points to no receiver details found.

I have checked and re-checked and it looks ok.

However, by sender component is not a Business System and i have added the sender and receiver interfaces there.

In my actual receiver Business System from SLD i have no option of adding (no add option) any interface for Sender or Receiver tab.

Can this be causing issue?

I am asking this because when i was creating the Receiver Agreement i could not select the receiver interface from value list but had to write manually.

Can this be blocked out and needs to be updated so that the business system should allow for the update of interfaces?

Also, the PI i am working is Windows based and for this the file path example is as -

S:\usr\sap\<sysid>\<Interface>

The file paths as created by Basis are with the below format-

\\<SAPECC090>\PI\INCOMING

How do i use these file access parameters?

Nothing is working.


Something did change from yesterday as my failed attempts are now coming out as messages in PI SXMB_MONI. They were not there yesterday.

I have also managed to do the successful cache refresh today which was not working yesterday after Basis downloaded a note to make it work.

Please advice

Regards,

Archana

former_member184720
Active Contributor
0 Kudos

Hi Archana - Assign the SWCV of the receiver interface to the business system in SLD. This way you can select the inbound interface while creating the receiver agreement.

former_member596513
Participant
0 Kudos

I have done this now and was able to select the interfaces in Business System

Thanks Hareesh.

Now the call is failing at Call Adapter stage and we found some notes that will need to be implemented by Basis. Hopefully tomorrow i will be able to update.

Basis still has to check as to why there are no logs or channel details in monitoring.

I hope they can resolve this.

Thanks for your advice.

Regards,

Archana

former_member184720
Active Contributor
0 Kudos

Good to know

May be you post the error too.

former_member596513
Participant
0 Kudos

Hi Hareesh,

I am still waiting for Basis to confirm that they have implemented the details. After this they will have to check why no logs and no channels are being picked up in monitoring. I will do the test message after that and update but that is just a step closer to successful processing.

Regarding the error, i am giving below the details and the corresponding thread that we found recommending the notes for PI 7.3 (related to the error in Call Adapter step):

Error -

Attribute ProcessingMode has the unexpected value S; A was expected

http://scn.sap.com/thread/3424871

Above thread is suggesting to apply below notes:

Note 1609041 - XI runtime: Synchronous acknowledgements

Note 1849533 - XI runtime: synchronous acknowledgments II

Note 1857701 - XI runtime: Synchronous acknowledgements III


Regards,

Archana

former_member184720
Active Contributor
0 Kudos

Hi Archana - Meanwhile can you also check if the adapter engine is registered in the SLD.

go to RWB->SLD registration->

Here you can find the components and their registration status..

former_member596513
Participant
0 Kudos

Hi Hareesh,

I have checked in RWB for SLD Registration and it shows OK for the Adapter Engine.

However, i still think it is something to do with the Adapter Engine as even if the File adapter is polling incorrectly or has empty polling, the channel should still be identified and picked up in the channel monitoring in RWB.

This is the basic health check that the adapters are ok.

I am going to double check the configured trace level but if i am not wrong there should be a default value and it should be active.

Any advice?

Regards,

Archana

Harish
Active Contributor
0 Kudos

Hi Archana,

Please check the adapter engine status in pimon or NWA.

also check the central adapter engine in Component monitoring. you will find some logs about the error.

regards,

Harish

former_member596513
Participant
0 Kudos

Hi Hareesh,

I have worked out a work around now

The issue is that currently as we are on PI 7.3, we are by default creating channel adapters with Basis 7.3 for example when i am creating a sender file adapter, i choose File in Basis 7.3 domain.

However, as i discovered yesterday in my analysis, the Adapter Engine seems to be missing the Basis 7.3 in its Adapter Metadata which shows Only 7.1.

Also, in the next tab for Software Component, I found that the SAP Basis 7.3 is not registered in the list of software components.

Just to confirm this, i created a sender file communication channel with Basis 7.1 after updating the sender agreement with the new channel, my channel was listed in the channel monitoring.

As I am not Basis, i really am not sure where all this configuration needs to be updated for Adapter Engine but I have also requested Basis to raise the issue with SAP.

Hi All,

Thanks you so much for the continuous suggestions on this.

I appreciate it

Regards,

Archana