File adapter metadata changed for adapter attributes

July 1, 2009 at 6:01 am

[] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []

  1. File adapter: NegativeArrayException occurs while ArchivingSymptom You have configured the File Adapter in your scenario with following options set in configuration: 1.Files are to be archived (with or without timestamp) after processing. 2.Local file system (and not...
  2. Receiver file adapter thread hangingSymptom The thread of receiver file adapter remains in runnable state while communication channel has the following configuration File Construction Mode=Create, Overwrite Existing File=false, Write Mode= Use Temporary File. Other terms File...
  3. File Adapter messages stuck in “To Be Delivered” statusSymptom You have upgraded to PI 7.0 SP 18 and you notice that File Adapter messages are stuck in “TBDL”(To Be Delivered) status. Additionally, the following symptoms are noticed: 1 – File...
  4. FTP receiver adapter deletes file with append modeSymptom You are using the File Adapter in your business scenario for message processing. During the message processing, you notice, that, the FTP receiver adapter deletes the output file if it encounters...
  5. File sender adapter generates duplicate message IDs.Symptom This note attempts to solve two issues: a) File sender adapter generates duplicate message IDs and sends it to Messaging system. In the Synchronous(Best Effort) scenario cases, Messaging system does not...
  6. Temp file remains in directory when file fails with errorSymptom You are using the File Adapter in your business scenario for message processing. During file processing, you notice, that, the temporary file is not deleted(in case file fails with error). The...
  7. Default type for attributesSymptom When executing a proxy the simple transformation fails with exception CX_ST_REF_ACCESS. Reason and Prerequisites Within the WSDL used to generate the proxy an attribute is is defined without type. This should...
  8. ES Modeler: Names of attributes are missingSymptom If an ABAP Dictionary reference is entered during the creation of a template node, the system transfers all of the names (nodes and attributes) in all of the languages from the...

Symptom

You are using the File Adapter in your business scenario for message
processing. During the transport of XI to another system, you notice that the values for some of the File Adapter attributes are getting overwritten(i.e the old values are transported instead of a blank value). The described issue can occur till XI 3.0 SP 23 and PI 7.0 SPS18 releases.
The following attributes of File Adapter are getting transported through a XI transport:
‘file.sourceDir’
‘file.sourceFileName’
‘file.archiveDir’
‘advancedSourceDir’
‘errorArchiveDir’
Other terms

XI 3.0/PI 7.0 File Adapter,adapter specific attributes, metadata, sourceDir, sourceFileName, archiveDir, advancedSourceDir, errorArchiveDir, transportable, nonTransportable
Reason and Prerequisites

In the metadata of File adapter, the “nonTransportable” tag is not set for these attributes. Consequently, the old values are getting transported even if not desired.
Solution

The described problem is solved with changes in File adapter metadata.
The archives and the support package stack guide can be found on the service marketplace as described in SAP Note 952402.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment