SoftwareAG webMethods Designer Introduction | Integration | API | SoftwareAG | webMethods

1. Agenda
 Designer Overview
 Flow Services
 Document types
 Mapping
 Java Services
 Invoking Services (Run, Trace, Step)
 Messaging, Triggers
 Specification
 Schema
 JDBC Adapter (Adapter Service, Adapter Notification)
 Flat File Handling
- 1 -
1

2. Designer Overview
2

3. 3
Designer Overview
• WebMethods Designer is a eclipse based IDE development tool that you use to build, edit, and
test integration logic.
• Construct integration logic with an easy‐to‐use implementation language called the
webMethods flow language
• Designer also has extensive data transformation and mapping capabilities that allow you to
quickly drag‐and‐drop data fields from one step to the next.

4. 4
Login to Designer

5. 5
Designer Main Window
Navigation Elements
Editor Window
Properties window

6. 6
Navigation Elements

7. 7
Navigation Elements Contd.

8. 8
Navigation Elements Contd.

9. 9
Switching perspectives
 Service Development Perspective - that contains the views, editors, and tabs needed to build services
and other supporting elements
 Debug Perspective -When you debug a service, use the Debug perspective. The Debug perspective
contains various views for helping you debug your service
 Process Development Perspective

10. 10
Elements
An element is an item that exists in the Navigation panel in webMethods Designer.
Elements include folders, services, specifications, IS document types, triggers, and IS schemas.

11. Flow Services
11

12. 12
Flow Services
•A flow service is a service that is written in the webMethods 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.
•Locking and Unlocking:
•A lock on an element prevents another user from editing that element. When an element is locked by you, you have a
user lock. The element is read‐only to all other users on the Integration Server. Another user cannot edit the element until
you unlock it.

13. 13
Flow Steps

14. The INVOKE flow step invokes another service. You can use it to invoke any type of service, including another flow service.
Invoke Step
14

15. Map STEP
15

16. LOOP STEP
The LOOP step takes as input an array variable that is in the pipeline. It loops over the
members of an input array, executing its child steps each time through the loop
16

17. 17
Repeat STEP
•The REPEAT step repeatedly executes its child steps up to a maximum number of times
that you specify. It determines whether to re‐execute the child steps based on a Repeat on
condition. You can set the repeat condition to one of the following:
•Repeat if any one of the child steps fails.
•Repeat if all of the elements succeed.

18. 18
SEQUENCE

19. 19
BRANCH
•The BRANCH step selects and executes a child step based on the value of one or more variables in the
pipeline. You indicate the variables you want to branch on by specifying a switch value or by writing an
expression that includes the variables.
Branching on a Switch Value
When you branch on a switch value, you specify the switch variable in the Switch property of the BRANCH
step. In the Label property for each child step, you specify the value of the switch variable that will cause that
child step to execute. At run time, the BRANCH flow step executes the child step that has the same label as
the value of the Switch property.
Branching on Expressions
When you branch on expressions, you set the Evaluate labels property of the BRANCH step to true. In the
Label property for each child step, you write an expression that includes one or more variables. At run time,
the BRANCH step executes the first child step with an expression that evaluates to true.

20. 20
Exit Step
The EXIT step exits the entire flow service or a single flow step. Specifically, it may exit
from the nearest ancestor loop step, or the entire
flow service.
The EXIT step can throw an exception if the exit is considered a failure. When an
exception is thrown, user‐specified error message text is displayed by typing it directly or by assigning it to a variable in the
pipeline.

21. 21
Data Types

22. 22
Document Type
•An IS document type contains a set of fields used to define the structure and type of data
in a document (IData object). You can use an IS document type to specify input or output
parameters for a service
You can create an IS document type in the following ways:
• Create an empty IS document type and define the structure of the document type
yourself by inserting fields.
•Create an IS document type from a source file, such as an XML Schema, DTD, or XML
document. The structure and content of the IS document type will match that of the
source file.
• Create an IS document type from a Broker document type.

23. 23
Modifiers (Mapping)
Link a pipeline variable to a service variable. The Link modifier lets you
resolve variable‐name and data‐structure differences by “linking”
(copying) the value of one variable to another at run time.
Drop a variable from the pipeline. The Drop modifier removes
extraneous variables from the pipeline
Assign a value to a variable. The Set Value modifier “hard codes” a
value for a variable

24. 24
Java Services
When you build a Java service, you type (or paste) your code in the text box in the Java
service editor and run the java service to see the outputs.

25. 25
Running Services
•You can use Designer to test services in two ways:
•From Designer. With this technique, Designer is the client. That is, Designer invokes the service and receives the results.
•From a browser. With this technique, Designer formulates the URL necessary to
invoke the service and passes that URL to your browser. Your browser actually
invokes the service and receives the results.
•Trace Executes flow steps one after another to the end of the service and visually marks steps as they execute.
•Trace to Here Executes flow steps one after another up to a specified point and visually marks steps as they execute Step
Executes the next flow step and then halts
•Step Into Opens a child flow or a MAP step so that you can debug the
•individual flow steps within it

26. 26
Messaging/Trigger
In an integration solution that uses the publish‐and‐subscribe model, services publish
instances of publishable document types, and triggers subscribe to publishable document types.
When you build an integration solution that uses publication and subscription, you need
to create the publishable document types before you create triggers, services that process documents, and services that
publish documents
What is Broker / Universal Messaging :
The Broker/Universal Messaging is a high-speed message router. It enables asynchronous, message-based solutions that are
built on the publish-and-subscribe model.
The role of the Broker/universal messaging is to route documents between information producers (publishers) and information
consumers (subscribers
The Broker/Universal Messaging maintains list of subscribers that are interested in receiving certain types of documents. When
the Broker/Universal messaging receives a published document, it queues the document for the subscribers of that document
type. Subscribers receive the documents from their queues, which usually triggers an action on the subscriber’s system that
processes the document.

27. 27
Specification
A specification is a IS element that defines a set of service inputs and outputs. If you have multiple services with the same input
and output requirements, you can point each service to a single specification rather than manually specify individual input and
output fields in each service.
Any change that you make to the specification is automatically propagated to all
services that reference that specification.

28. 28
IS Schema
An IS schema is a element in the Navigation panel that acts as the blueprint or model against which you validate an XML
document

29. 29
JDBC Adapter Services
Adapter services allow you to connect to the adapter’s resource and initiate an operation on the resource from the Integration
Server.
You call adapter services from flow or Java services to interact with database tables. The adapter services perform database
operations by calling JDBC APIs
Adapter services are based on templates provided with the JDBC Adapter. Each template represents a specific technique for
doing work on a resource, such as using the SelectSQL template to retrieve specified information from a database
JDBC Templates:
Select SQL
Insert SQL
Update SQL
Batch Insert SQL
Batch Update SQL
Delete SQL
Dynamic SQL

30. 30
JDBC Adapter Notification
An adapter notification monitors a specified database table for changes, such as an insert, update, or delete operation, so that
the appropriate Java or flow services can make use of the data, such as sending an invoice or publishing it to the Integration
Server.

31. 31
Flat file Handling
A flat file schema is the blueprint that contains the instructions for parsing or creating a
flat file and is created as a namespace element in the webMethods Integration Server. This blueprint details the structure of the
document, including delimiters, records, and
repeated record structures. A flat file schema also acts as the model against which you can validate an inbound flat file.
A flat file schema consists of hierarchical elements that represent each record, field, and
subfield in a flat file. Each element is a record, composite, or field, and either a definition or reference. You then configure each
element with the necessary constraints

32. 32
https://www.youtube.com/c/TechLightning/