How to Process empty file in Text (FCC) to Text (FCC) file scenario using G

[Former Member]

Interface has to pick text files from the source system and deliver on target system as text file. If the source text file is empty (zero Bytes), interface has to delivery an empty text file on target system.

To accomplish this , we have developed an interface in PI system using graphical mapping and to process and delivery the empty files used empty file handling options on both communication channels. We have used Graphical mapping to transform the source file.

Interface is working fine if the source file is not empty. But in case of empty file, interface failed with an error message 'Parsing an empty source. Root element expected!' . We tried with all the available option on graphical mapping editor to fix the issue. But none of the options are worked.

Could you please let me know how to fix this issue.

[Former Member]

Hi,

If you are picking empty text file and to put the same empty text file as (FCC) on the reciever side, then need not do any mapping, Also skip IR part.

To developing this interface, there is no need to create any objects in the Integration Repository (IR). This means no mapping. if the data is not in XML, then no mapping can be done. So, only need to work in the Integration Directory (ID).

For this scenario we can use only with integration directory in the XI.

Open Integration Directory and create new scenario

Create Business Service

Create sender Communication Channel with parameter of the source location

Create receiver Communication Channel with parameter of the target location

Create Sender Agreement with outbound Interface = <DummyInterface>, Namespace = <DummyNamespace> and sender Communication Channel

Create Receiver Determination with outbound Interface = <DummyInterface> and Namespace = <DummyNamespace>

Create Interface Determination with inbound Interface = <DummyInterface> and Namespace = <DummyNamespace>

Create Receiver Agreement with inbound Interface = <DummyInterface>, Namespace = <DummyNamespace> and receiver Communication Channel

Activate

Note: The <DummyInterface> should be unique and the <DummyNamespace> can either be an existing namespace or a new namespace.

Sameer

[former_member200962]

Hi,

If your requirement is to just pick file from the source and dump it in the target folder then why have a design option as:

To accomplish this , we have developed an interface in PI system using graphical mapping 
and to process and delivery the empty files used empty file handling options on both 
communication channels. We have used Graphical mapping to transform the source file.

You don't need to have objects in IR at all....just do configuration in ID with dummy interfaces and namespaces (have actual filenames and file paths)....in this case XI wont be bothered what the content is, what the format is..etc...

Regards,

Abhishek.

[prasannakrishna_mynam]

Hello William,

In your Message Mapping change the target message type occurences to '0' in the Meesages tab and try.

Regards..

Prasanna..

[Former Member]

Hi,

Along with FCC parameters(processing parameters ->process empty files.... can u try to build a message with some fields and use exists() function in mapping.

Regards,

Madhu

[siddhesh_pathak4]

Hello,

Try out,

In your FCC parameters,

Put , ignoreRecordsetName TRUE.

In your mapping try to have the "mapWithDefault" parameter.