Skip to Content
avatar image
Former Member

Copied CC not working - missing InterfaceNamespace


i copied a JMS-CC from an Business-System to a BusinessService, deaktivated the old JMS-Channel and would like to run XI via the BusinessService. I configured all the rest (receiver Det. and so on...) but i don't know why this error is arising in Adapter-Monitoring:

<b>Minimum address data not configured. Field InterfaceNamespace is empty.</b>

Any ideas?! br, Jens

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    May 15, 2007 at 03:19 PM


    when u copied the CC from Business system to business service,did u make changes in the businesse service in CC(to make them point to business service instead of old business system)?



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi, well nothing changed. the JMS still points to the same MQSeries-Machine.

      Really nothing changed!!!

      i also checked receiver det. etc. but i have no clue....


  • avatar image
    Former Member
    May 15, 2007 at 03:30 PM


    You have to change the receiver agreement, receiver determination and interface determination too. Please check all these?


    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Ok guys, i solved on my own.

      Well my Scenario was like i am getting Data from a MQSeries-Machine, so the JMS-Adapter is configured as Sender.

      Related on the SAP-Docu i found out that:

      <i>Special Conditions when Using the Sender <b>JMS</b>, JDBC, or File/FTP Adapter

      In the case of these adapter types, the information about address fields of the message header is determined from the sender agreement that the communication channel is assigned to. The following conditions apply to sender agreements that use communication channels with these adapter types.

      &#9679; The sender channel must not be assigned to more than one sender agreement.

      &#9679; No key fields may contain the wildcard character (*).

      &#9679; At least the interface (name and namespace) and the sender service must be specified in the sender agreement because the corresponding address fields in the message must be set uniquely. The remaining fields are optional (see the key fields for the sender agreement).

      The sender agreement is determined from the sender channel at runtime. The information from the sender agreement is used to construct the address header of the message.</i>

      So everything worked fine after adding a sender agreement!!

      br, Jens