xml namespaces and assign action block

[Former Member]

We recently turned on https on our MII box and since then my assign action block is not recognizing xml with namespace references in the tags.

I created a parameter called inputXML with the datatype set to xml, this is roughly the data it contains:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:gdt="http://sap.com/xi/SAPGlobal/GDT" xmlns:me="http://sap.com/xi/ME" xmlns:sch="http://sap.com/xi/ME">

    <soapenv:Header/>

    <soapenv:Body>

        <me:RouterUpdateRequest_sync>

            <me:Router>

                <sch:SiteRef>

                    <sch:Site>201</sch:Site>

                </sch:SiteRef>

                <sch:Router>RouteName</sch:Router>

                <sch:Revision>Revision</sch:Revision>

                <sch:RouterType>U</sch:RouterType>

                <sch:Description>RouteDescription</sch:Description>

...

In my transaction I need to extract the contents of the Router tag.  My Assign action block assigns the following string to a parameter I created called Transaction.routeName

Transaction.inputXML{/soapenv:Envelope/soapenv:Body/me:RouterUpdateRequest_sync/me:Router/sch:Router}

Prior to turning on HTTPS, this worked fine, but now it only works if I remove the namespace info from both the input and the assignment string.  Any idea what might be causing this?

[agentry_src · Accepted solution]

Hi Alli,

What version of MII are you using?  There were several updates to https in later versions of 12.1 to fix some of these issues.

Regards, Mike

[Former Member · Accepted solution]

It looks like we're using 12.2.3 Build(177)

[Former Member · Accepted solution]

Any other thoughts?

[agentry_src · Accepted solution]

Hi Alli,

Sorry about the delay, but was out in the woods on vacation.  Please open a ticket as the changes associated with default namespace assignment are a little outside my area of expertise.  I do know that there have been some issues in 12.1 with https:// but thought they were associated with redirects rather than NS issues.  Send me a ticket number and I will make sure it gets routed to the correct folks.

Regards, Mike

[Former Member · Accepted solution]

No problem, Mike, I suppose even SAP employees should be allowed to enjoy an occassional vacation

I think we figured it out though... It seems that MII doesn't like that I had two namespaces in my xml input that both referenced the same url:

xmlns:me="http://sap.com/xi/ME" and xmlns:sch="http://sap.com/xi/ME"

After I removed the "me" namespace reference from the envelope and replaced it with "sch" for the appropriate tags everything seems to work fine.  Still not sure if/why turning on https would have caused this, but that was our resolution.

Thanks,

Alli

[agentry_src · Accepted solution]

Hi Alli,

Thank you very much for posting your solution and comments.  I am sure someone else will run into the same issue at some point down the line. 

Did you open a ticket?  It would help get the developers involved in fixing it.  Please DM me the ticket number if you have it.

Thanks, Mike

[Former Member · Accepted solution]

Unfortunately, I don't have access to create tickets for my client and have no MII box of my own right now, so no ticket was created.

[agentry_src · Accepted solution]

Okay.  Worth a shot.  Thanks, Mike