Integration & B2B

webMethods flow reader

Read a flow.xml and node.ndf into a readable step tree, service dependency list and hard-coded value report — the first artefacts a migration assessment needs.

Built from the schema, not yet from a production package

This reads the documented FLOW schema, which has been stable from webMethods 6.x through 10.x. It has not yet been verified against a real package. If it mis-reads something in yours, that is worth telling us — it is the kind of bug we would rather hear about than ship quietly.

flow.xml — the logic

37 lines · 1,486 characters

<?xml version="1.0" encoding="UTF-8"?>
<FLOW VERSION="3.0" CLEANUP="true">
  <MAP MODE="INPUT" NAME="Normalise input" COMMENT="Trim and default">
    <MAPCOPY FROM="/orderIn/id" TO="/order/id"/>
    <MAPCOPY FROM="/orderIn/lines" TO="/order/lines"/>
    <MAPSET FIELD="/order/source"><VALUE>ACME_PROD</VALUE></MAPSET>
    <MAPDELETE FIELD="/orderIn"/>
  </MAP>
  <INVOKE SERVICE="pub.schema:validate" NAME="Validate order" VALIDATE-IN="$none">
    <MAP MODE="INPUT">
      <MAPCOPY FROM="/order" TO="/object"/>
      <MAPSET FIELD="/conformsTo"><VALUE>orders:orderDoc</VALUE></MAPSET>
    </MAP>
  </INVOKE>
  <BRANCH SWITCH="/isValid" NAME="Valid?">
    <SEQUENCE NAME="true" EXIT-ON="FAILURE">
      <LOOP IN-ARRAY="/order/lines" NAME="Each line">
        <INVOKE SERVICE="orders.util:enrichLine" NAME="Enrich"/>
        <BRANCH SWITCH="/line/backordered" NAME="Backordered?">
          <SEQUENCE NAME="true">
            <INVOKE SERVICE="orders.notify:raiseBackorder" NAME="Notify"/>
          </SEQUENCE>
          <SEQUENCE NAME="$default"/>
        </BRANCH>
      </LOOP>
      <INVOKE SERVICE="orders.out:sendToErp" NAME="Send to ERP"/>
    </SEQUENCE>
    <SEQUENCE NAME="$default">
      <INVOKE SERVICE="pub.flow:debugLog" NAME="Log rejection" DISABLED="true"/>
      <EXIT FROM="$parent" SIGNAL="FAILURE">
        <MAP>
          <MAPSET FIELD="/failureMessage"><VALUE>Order failed validation</VALUE></MAPSET>
        </MAP>
      </EXIT>
    </SEQUENCE>
  </BRANCH>
</FLOW>

node.ndf — the signature (optional)

41 lines · 1,677 characters

<?xml version="1.0" encoding="UTF-8"?>
<Values version="2.0">
  <value name="node_type">flow</value>
  <value name="node_nsName">orders.process:handleOrder</value>
  <value name="node_comment">Validate an inbound order and post it to the ERP.</value>
  <value name="svc_type">flow</value>
  <record name="node_sigtype" javaclass="com.wm.util.Values">
    <record name="sigin" javaclass="com.wm.util.Values">
      <array name="field" type="record" depth="1">
        <record javaclass="com.wm.util.Values">
          <value name="field_name">orderIn</value>
          <value name="field_type">3</value>
          <value name="field_dim">0</value>
          <value name="field_opt">false</value>
        </record>
        <record javaclass="com.wm.util.Values">
          <value name="field_name">sourceSystem</value>
          <value name="field_type">0</value>
          <value name="field_dim">0</value>
          <value name="field_opt">true</value>
        </record>
      </array>
    </record>
    <record name="sigout" javaclass="com.wm.util.Values">
      <array name="field" type="record" depth="1">
        <record javaclass="com.wm.util.Values">
          <value name="field_name">erpDocNumber</value>
          <value name="field_type">0</value>
          <value name="field_dim">0</value>
          <value name="field_opt">false</value>
        </record>
        <record javaclass="com.wm.util.Values">
          <value name="field_name">rejectedLines</value>
          <value name="field_type">4</value>
          <value name="field_dim">1</value>
          <value name="field_opt">true</value>
        </record>
      </array>
    </record>
  </record>
</Values>

Inspection files can contain the original data and identifiers. Review them before sharing; downloads are processed locally. This is a parser inspection, not certification.

Parsed in your browser. That matters more here than anywhere else on this site: a flow.xml carries internal service names, field paths and sometimes literal credentials in MAPSET values. Nothing you paste is transmitted, logged or stored.

Stay ahead of the integration layer.

Integronauts Signal — practical enterprise integration, API and agentic AI thinking. The tools stay free either way.

Integronauts Signal is launching soon.

Practical enterprise integration, APIs, agentic AI and emerging architecture. Sign-up opens when the list does — nothing to enter yet.