webMethods

On this page

modernAIze supports webMethods as an application estate source platform. Prepare the service definitions for the integration operation being assessed. Flow service source describes steps and invocations; namespace and document definitions provide the surrounding service context. Keep these files together so similarly named artifacts retain their package identity.

Inputs to prepare

Integration Server package artifacts such as manifest.v3, flow.xml, node.ndf (including *.node.ndf), and node.idf. Preserve their package and service directory structure using Folder or ZIP.

Native assets and what to collect

Asset	Material to supply	What it contributes
Flow service	`flow.xml` and associated service files	INVOKE, MAP, BRANCH, LOOP, and other recorded Flow steps
Namespace/service definition	`node.ndf` and associated namespace artifacts	Service identity, signatures, and source context
Document definition	The corresponding namespace definition files	Input/output document and record structure
Package metadata	`manifest.v3` with the package’s `node.ndf`, `node.idf`, and `flow.xml` context	Package and asset context accompanying the service source
Referenced service	Its definitions when available in scope	Behavior behind an invocation

The uploader admits .xml, .ndf, .idf, .v3, and .bak, but backup files (.bak) are ignored by analysis. Other filenames with these extensions may also remain unclassified. File acceptance alone does not make an arbitrary XML file a Flow service. Java-service binaries, adapter implementations, and remote services can remain dependencies rather than supplied Flow behavior.

How to collect the inputs

Use the Integration Server package source or a native package export to obtain the selected service and namespace files. Preserve package-relative paths and collect the required shared document types and services. This route uses native package collection; it does not require a separate modernAIze extractor.

Do not flatten the package into one directory: many services contain files named flow.xml or node.ndf. Their location distinguishes the owning service. Inspect package configuration for credentials before transfer and retain approved context for external adapter or endpoint references.

Prepare the source

Choose the entry service and the operation it implements.
Collect its Flow and namespace definitions, including the relevant invoked services and shared document definitions.
Preserve package-relative paths rather than flattening repeated filenames such as flow.xml or node.ndf.
Record external adapters, services, and implementation dependencies that are not present in the supplied material.

Investigate the analysis

Follow the service sequence and its invocation, mapping, branching, and error paths. Inspect the document structures passed across important boundaries. Distinguish a service implemented by supplied Flow source from an external operation whose implementation must be reviewed with its owner.

Start with Briefing for the system-level explanation, then use the appropriate Landscape view and available Detail links to investigate the relevant processing. Keep the question tied to the supplied source revision.

Example review question

The following example is synthetic.

In an order-submission flow, the entry service validates a document, invokes a shared pricing service, and sends the accepted order to another system. Review both the successful path and the branch taken when pricing or submission fails.

Verify the scope

Locate the entry service and relevant invocations in the analysis, then compare the represented behavior with the supplied definitions. If an invoked service is outside the package, obtain its source or record its interface and owner as an assessment dependency. An invocation does not expose an adapter’s or external service’s implementation.