webMethods Developer

• Introduction • Requirements to use Developer • Developer Features • Q&A


• webMethods Developer is a graphical development tool that you use to build, edit, and test integration logic. • It provides an integrated development environment in which to develop the logic and supporting objects that carry out the work of an integration solution. • It also provides tools for testing and debugging the solutions you create.

Requirements to use Developer
• Have access to a webMethods Integration Server on which you can build and test services. • Have a user account on that webMethods Integration Server. • Belong to a group that is a member of the “Developers” ACL (access control list) on that webMethods Integration Server.

Developer Window

Properties panel displays the properties for an item Navigation Panel displays the contents of Servers, packages and folders

Editor displays the controls you use to examine and edit an element you have opened from the navigation or Recent Element panels Results panel displays the results of a service execution Recent elements panel displays the elements you viewed recently

Developer Features
• Managing Elements in Navigation Panel • Working with Packages • Locking and Unlocking of Elements • Assigning and Managing Permissions • Building Flow Services • Inserting Flow Services • Using Flow Diagram View

Developer Navigation & Panel Icons
You can have multiple server contexts displayed in Developer. The active server context is the one that is highlighted in the Navigation panel. To display the contents of the server, click the symbol (+) next to its name A package contains a set of services and related files, such as specifications, IS document types, and output templates. To display the contents of a package, click (+) next to its name. A folder contains related services and optional folders (called subfolders). To display the contents of a folder, click (+) next to its name. A flow service is a service written in the webMethods flow language

A specification is a formal description of a service’s inputs and outputs

Developer Navigation & Panel Icons
A Java service is a service written in Java. A trigger associates one or more publishable document types with one or more services. At run time, when the Integration Server receives a document that satisfies the conditions of the trigger, the Integration Server executes/invokes the associated services. An adapter service connects to an adapter’s resource and initiates an operation on the resource. Adapter services are created using service templates included with the adapter. An adapter notification enables an adapter to receive event data from the adapter’s resource. An adapter notification can have an associated publishable document type that the adapter uses to send the notification data to an Integration Server or a Broker A publishable document type is an IS document type with specific publishing properties. Instances of publishable document types can be published and subscribed to.

Building Flow Services
• A flow service is a service that is written in wM flow
language. • This simple yet powerful language lets you encapsulate a sequence of services within a single service and manage the flow of data among them. • Any service can be invoked within a flow (including other flow services).

Building Flow Services
• A flow service contains flow steps. A flow step is a basic unit of work (expressed in webMethods flow language) that webMethods Integration Server interprets and executes at run time. • Different Control Steps are used to direct the execution of the flow •Branch •Repeat •Loop •Sequence •Exit • Data handling steps like the Map Step. • Invocation steps like the Invoke Step.

Building Flow Services
• The pipeline is the general term used to refer to the data structure in which input and output values are maintained for a flow service. • The pipeline starts with the input to the flow service and collects inputs and outputs from subsequent services in the flow. When a service in the flow executes, it has access to all data in pipeline at that point.

Flow Steps (Control Steps)
The BRANCH step allows you to conditionally execute a step based on the value of a variable at run time.
When you build a BRANCH step, you can: Branch on a switch value. Use a variable to determine which child step executes. At run time, the BRANCH step matches the value of the switch variable to the Label property of each of its targets. It executes the child step whose label matches the value of the switch. Branch on an expression. Use an expression to determine which child step executes. At run time, the BRANCH step evaluates the expression in the Label property of each child step. It executes the first child step whose expression evaluates to “true.”

Flow Steps (Control Steps)
The LOOP step repeats a sequence of child steps once for each element in an array that you specify. You use the SEQUENCE step to build a set of steps that you want to treat as a group. Steps in a group are executed in order, one after another.
By default, all steps in a flow service, except for children of a BRANCH step are executed as though they were members of an implicit SEQUENCE step (that is, they execute in order, one after another).

The EXIT flow step allows you to exit the entire flow service or a single flow step.

Flow Steps (Data Handling Step)
The MAP step lets you adjust the contents of the pipeline at any point in a flow service.
When you build a MAP step, you can: •Prepare the pipeline for use by a subsequent step in the flow service by linking, •adding, and dropping variables in the pipeline. •Clean up the pipeline after a preceding step by removing fields that the step added but are not needed by subsequent steps. •Move variables or assign values to variables in the pipeline. •Initialize the input values for a flow service. •Invoke several services (transformers) in a single step. •Map documents form one format to another. For example, you can map a document in an XML format to an ebXML format or a proprietary format.executes the first child step whose expression evaluates to “true.”

Testing and Debugging Flow services
•Developing a Flow Service is an iterative process of building, testing and correcting (debugging) the flow. •Developer provides a range of Tools for the above. •Test Services, specify the input and inspect the results. •Examine the call stack and the pipeline when error occurs. •Execute services in Debug mode. •Temporarily disable steps or specify points where you want the flow to halt

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer: Get 4 months of Scribd and The New York Times for just $1.87 per week!

Master Your Semester with a Special Offer from Scribd & The New York Times