WEB METHODS

WEBMETHODS is a software company founded in 1996, which

provides integration tools, focused on application integration, business
process integration and business to business partner integration. Later
in 2007 it was acquired by SOFTWARE AG.

WEB METHOD MODULES

EAI(Enterprise application integration)
B2B(Business to Business)

EAI (Enterprise application integration)

The process of integrating disperate or various applications
regardless of the platform, allowing the sharing of business amongst
multiple organizations. one large challenge of EAI is that various
systems need to be linked together to share data or some business
rules, often that systems reside on different operating systems use
different database solution and different computer language and in
some cases are legacy systems that are no longer supported by the
vendor who originally created them.

It is the process of linking such (supply chain management,

customer relationship management, human resource etc) applications
within a single organization together in order to simplify and automate
business process to the greater extent possible.
B2B (Business To Business)
It can be defined as nature and selling process of goods and services
from one company to another company, as manipulating business with
external organizations. Take an example, manufacturing of laptops, it
needs some requirements to manufacture the laptop, so the
manufacturing company has to connect with external parties to meet
the requirements like chips, hard disk etc. so it tie up with the related
requirement partners (i.e., the organization manufacturing the
requirements related to the product) to expose the product i.e., the
company is doing business with external organizations for the release
of the product in the market. This process comes under B2B.

MESSAGE STANDARS
XML (Extended Markup Language)
EDI (Electronic Data Interchange)
IDOC (Intermediate Document)
FLAT FILE
(XML (Extended Markup Language))

It is a default standard message type format and it is used to

transport and share data.XML document is a string of characters. The
design goals of XML emphasize simplicity, generality, usability over the
internet. Although the XML design focuses on the documents. It is
widely used for arbitrary data structures, for example in web services.
 As of 2009, hundreds of XML-based languages have been
developed, including RSS, Atom, SOAP, and XHTML. XML-based formats
have become the default for many office-productivity tools, including
Microsoft Office (Office Open XML), OpenOffice.org and LibreOffice
(OpenDocument), and Apple's iWork. XML has also been employed as
the base language for communication protocols, such as XMPP.

EDI (Electronic Data Interchange)

This message standard will be in number format only,it is used to
transfer data between any two organizations electronically by means of
electronic documents or business documents sent from one system to
another.For the security purpose, in order to place any orders or any
service requirements they used to send in EDI format, so that the
other’s can‘t understand this document rather than the crew who
knows this format.

It has two types of formats:

ANSI X12
EDIFACT
ANSI X12
This format is mostly used in NORTH AMERICA. In this format the
elements will be separated by delimeter and it is mentioned with codes
for every transaction. Some of the transaction codes that are mostly
used are

810 – INVOICE
850 – PURCHASE ORDER
 855 – PURCHASE ORDER ACKNOWLEDGMENT (POA)
997 – FUNCTIONAL ACKNOWLEDGMENT
820 – BANKING TRANSACTIONS
860 – CHANGED PURCHASE ORDER
865 – CHANGED POA
856 – ADVANCED SHIPMENT NOTIFICATION

The EDI format will be as follows:

ISA **Send id * Rec id *Date and Time *
GS
ST
SE
GE
IEA
ISA (INTERCHANGE HEADER) in which 16 elements will be there ,in
which each element will be separated by delimeter and in GS (GROUP
HEADER) there are 8 elements and in ST (TRANSACTION SET) there
are 2 elements ,in transaction set we can find the document type which
it is and SE (TRANSACTION END) there will be 2 elements and GE
(GROUP END) in which there are 2 elements and in IEA
(INTERCHANGE TRAILER) there are 2 elements .In between ISA and
IEA there can be multiple GS and GE and in GS there can be multiple ST
and SE.

(EDIFACT)
EDIFACT, Electronic Data Interchange for administration, commerce
and transport. Which is mostly used in European countries, it provides a
set of syntax rules to structure data, an interactive exchange protocol,
standard messages which allow multi country and multi industry
exchange.

Structure of EDIFACT

UNA (service string advice) OPTIONAL

UNB (Interchange Header)

UNG (Functional Group Header)

UNH (Message Header)

USER DATA SEGMENTS THAT AS REQUIRED

 UNT (Message Trailer)

UNE (Functional Group Trailer)

UNZ (Interchange Trailer)

IDOC (INTERMEDIATE DOCUMENT)

IDOC is an intermediate document format for business transaction
data transfers. IDOC is similar to XML in purpose, but differs in syntax.
Both serve the purpose of data exchange and automation in computer
systems, but the IDOC Technology takes a different approach.

An IDOC consists of

 Control record (it contains the type of IDOC, port of the partner,
release of SAP R/3 which produced the IDOC etc.)
 Data records of different types. The number and type of segments is
mostly fixed for each IDOC type, but there is some flexibility (for
example an SD order can have any number of items).
 Status records containing messages like 'ID created', 'The recipient
exists', 'IDOC was successfully passed to the port'.

Because of the flexibility and transparency of IDOC format. some

NON-SAP users also use them as well.
FLAT FILE
A flat file can be a plain text file, usually containing one record
per line, or it can be a binary file. A list of names, addresses, and phone
numbers written by hand on a sheet of paper is a flat file database. This
can also be done with any type writer or word processor. A
spreadsheet or text editor program may be used to implement a flat file
database, which may then be printed or used online for improved
search capabilities.

WEBMETHOD COMPONENTS

WEBMETHOD INTEGRATED SERVER

WEBMETHOD DEVELOPER
WEBMETHOD BROKER
TRADING NETWORKS
BPM

WEBMETHOD INTEGRATED SERVER is the heart of webmethod,

without this there is no webmethods. WEBMETHOD DEVELOPER in
which we build our business logic using flow steps we implement the
coding part at developer stage. WEBMETHOD BROKER, it is referred as
message backbone or message facility, it is the mediator to route data
or messages. TRADING NETWORKS (TN), this is mostly implemented for
B2B .In this we can define partner profiles and enterprise profiles. For
some B2B customers if there are limited customers they won’t use TN,
as they have to buy the license of TN instead they use WEB SERVICE.
Trading networks and Broker are now integrated with MY
WEBMETHOD SERVER application.

DATATYPES IN WEBMETHODS

DOCUMENT
DOCUMENT LIST
OBJECT
OBJECT LIST
STRING

PUB-SUB MODEL

PUBLISHER-SUBSCRIBER MODEL (PUB-SUB MODEL),it is a message

based solution exchanging the data between publisher and subscriber
i.e., routing the data between publisher and subscriber by using broker.
For example if the data exchanges between SAP system to any
DATABASE.SAP sends the data i.e., IDOC to middleware then it
generates a PUBLISHER DOCUMENT TYPE and it publishes to broker ,for
every publisher document type there will be a associate trigger. when
the publisher document type is sent to the broker then the associated
trigger will be fired and it will be inserted into the database i.e., the
subscriber. Here SAP is publisher or information producer and the
DATABASE is subscriber or information consumer.
 Development process
To develop the software, every company follows these steps:
 Functional Requirements
 Technical design
 Development and Unit testing
 Integration Testing
 production
Functional Requirement is nothing but the concern
requirement needful for an entire project. The business analysts
from the users side and the project side will sit together to discuss
and decide about the requirements which were needed and creates
a particular document.
After getting the functional requirements from the user, the
project manager reviews the project and assigns to concerned team lead
,the team lead will give the technical design to the developers team
which was helpful in developing the code. This Design helps in
specifying hardware and system requirements and also helps in
defining overall system architecture.
Receiving the technical design document from team lead, the
document will be divided into modules and then actual coding starts
which was developed in small programs called units and later it
integrates into next step. Each and every module will be tested which is
known as unit testing. In unit testing, every module is tested whether it
meets the requirements. Unit testing is done by the developer only. In
the code review, it tests the code and if any error occurs it send the code
review comments to the developer and the developer resolves the errors
and sends to the testing team.
 In the testing or quality assurance environment, it gets the
functional design document from the team lead and they manipulate on
the document to meet the functional requirements that are needed for the
project, the integration testing or system testing is done over here and if
it requires it sends to the user acceptance test(UAT) and test code
review will be done and it goes to the production phase.
In the production stage, the developed software is tested in the
presence of the user. Here all the test cases are run infront of the user, if
he gets the satisfactory results the user formally accepts the release of
the software.

SUPPORT PROCESS

After the production phase, if the user gets any problem over the
product the support team will rectifies the issue. There are different
levels of support process. They are:
 L1 support
 L2 support
 L3 support
L1 support is to receives the problem from the user. The
problem will be treated as “TICKET” or “SERVICE REQUEST”
or “DEFECT”. L2 support is to sends the ticket number to the
technical support team. L3 support is to resolve the TICKET and
releases the product.
Usually support team members are less than the development
team. For some potential users, they have the levels based upon
 the TICKET severity and resolves the problem based on the
severity levels. If the severity level is 1, it resolves first and so
on….

ERP (ENTERPRISE RESOURCE PLANNING)

ERP is a system that integrates internal and external management

information across an entire organization embracing material
management(MM), financial accounting(FICO),production
management(PP), quality management(QM) etc. The purpose of ERP is
to facilitate the flow of information between all business functions
inside the boundaries of the organization and manage the connections
to outside stalkholders.ERP systems automate this activity by an
integrated software application. All the business modules in an
organization like HR,MM,QM,PP etc are integrated in a single packaging
tool in SAP, as SAP system is a ERP based tool.

Some of ERP’S are ORACLE, JD EDWARDS, OPEN BRAVO etc.

HIERACHIES
For any organization it will be as follows

COMPANY

COMPANY CODE

PLANT

PURCHASING ORG SALES ORG STORAGE LOCATION

INHOUSE DCS

DCS-DISTRIBUTION CHANNEL.

DBMS (DATABASE MANAGEMENT SYSTEM)

DBMS is a software that controls the organization, retrieval,

storage, security and integrity of data from a database, it is a set of
programs that enables to you to store, modify and extract information
from a database .It ensures that no more than one user can update the
same record at a time. The major DBMS vendors are ORACLE, MY
SQL(popular open source product) ,DB2 etc.

RDBMS (RELATIONAL DATABASE MANEGEMENT

SYSTEM)
RDBMS is a type of DBMS that stores data in the form of related
tables. It acquires few assumptions that how data is related and how it
will be extracted from the database. As a result, the same database can
be viewed in different ways.

Most every Business DBMS including ORACLE, MY SQL etc is a

RDBMS.

SQL COMMANDS

SQL is a structured query language used to access databases.It is

instruction used to communicate with the database to perform specific
task.SQL commands are not only used for searching data from database
but also to perform various operations create,select,modify,drop etc.,

SQL commands grouped into 4 major categories depending upon their

functionality, they are

DATA DEFINITION LANGUAGE

DATA MANIPULATION LANGUAGE
TRANSACTION CONTROL LANGUAGE
DATA CONTROL LANGUAGE

Data types used in SQL are:

Int Integer
Char CHARACTER

Float float is used when we want to indicate decimal values

Varchar (20) varchar is used to specify alphanumeric values.(20)

specifies the length of the input string

DATE date

DATA DEFINITION LANGUAGE

It is used to define the database objects,the SQL commands are
used for creating, modifying and dropping the structure of database
objects.

The commands are CREATE, ALTER, DROP, RENAME and

TRUNCATE.

COMMAND SYNTAX
a. CREATE CREATE table table-name
(column1 datatype,column2
datatype,...);

b. ALTER ALTER table table_name

ADD column_name datatype;
c. DROP DROP TABLE table_name;
DATA MANIPULATION LANGUAGE
It is used for manipulate the data from the database i.e., to
retrieve, modify, remove and add data.

COMMAND SYNTAX
a. SELECT SELECT column_name(s)
FROM table_name;
b. INSERT INSERT INTO table_name
(col1,col2….coln)
Values(value1,value2,……);
c. UPDATE UPDATE table_name
SET (column_name1=value,….)
WHERE condition;
d. DELETE DELETE from table_name
WHERE condition;

What is connection pool

A connection pool is a collection of connections with the
same set of attributes. The Integration Server maintains
connection pools in memory. Connection pools improve
performance by enabling adapter services to reuse open
connections instead of opening new connections. All adapter
services use connection pooling.

Explain about pub-sub model

 It is a specific type of message based solution in which it
routes the data between publisher and subscriber through a
third entity called broker. The broker entity temporarily stores
the document that it receives from publisher in a message
queue. Subscribers connect to the broker entity and fetch
documents from the queue.

What is pipeline

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. It allows services in the flow to share data. The
pipeline starts with the input to the flow service and collects
inputs and outputs from subsequent services in the flow.

What is Integration server

Web methods integration server is one of core application

servers in the web method platform. It is the system’s central
run-time component . It serves as the entry point for the
systems and applications that you want to integrate and is the
system’s primary engine for the execution of integration logic.
It publishes documents to receives from the broker.

Which version of the developer are you using

Developer 7.1.1
Which version of soap does it support

Soap 1.1 and 1.2

Explain broker monitor

Broker Monitor is a program that executes along side Broker

Server on the host machine in a web Methods Broker
environment. The Broker Monitor is automatically installed
when you install web Methods Broker server. Broker Monitor
continually checks the state of the Broker Server and
automatically attempts to re‐start it if it stops running.
Broker Monitor is also the program that starts a Broker Server.
You usually do not start a Broker Server directly. Instead, you
ask the Broker Monitor to start it for you.
Any machine that hosts a broker server will host a
broker monitor. In broker environment has only one broker
monitor even if it hosts multiple broker servers.
Trigger properties

Disabling and enabling a trigger

You can use the Enabled property to disable or enable

a trigger. When you disable a trigger, the Integration Server
disconnects the trigger client on the Broker. When you enable a
disabled trigger, the Integration Server connects the trigger
client to the Broker.

Setting a join time-out

 When you create a join condition you need to specify a
join time‐out. A join time‐out specifies how long Integration
Server waits for the other documents in the join condition.
Integration Server uses the join time‐out period to avoid
deadlock situations and to avoid duplicate service invocation.
In the properties panel when we set the join expires to
True - Indicate that the Integration Server stops waiting for the
other documents in the join condition once the time‐out period
elapses.
In the Expire after property, specify the length of the join
time‐out period. The default time period is 1 day.
False - Indicate that the join condition does not expire. Set the
Join expires property to False only if you are confident that all
of the documents will be received.

Specifying trigger queue capacity and refill level

The capacity indicates the maximum number of documents

that the Integration Server can store for that trigger. You can
also specify a refill level to indicate when the Integration Server
should retrieve more documents for the trigger.
In the properties panel in the Capacity property, type the
maximum number of documents that the trigger queue can
contain. The default is 10.
In the Refill level property, type the number of
unprocessed documents that must remain in this trigger queue
before the Integration Server retrieves more documents
for the queue from the Broker. The default is 4.
 The Refill level value must be less than or equal to the
Capacity value.

Controlling document acknowledgments for a trigger

When a trigger service finishes processing a guaranteed

document, the Integration Server returns an acknowledgement
to the Broker. You can increase the number of document
acknowledgements returned at one time by changing the value
of the Acknowledgement Queue Size property.The
acknowledgement queue is a queue that contains pending
acknowledgements for guaranteed documents processed by
the trigger
In the properties panel, in the Acknowledgement
Queue Size property, type the maximum number of pending
document acknowledgements for the trigger. The value must
be greater than zero. The default is 1.

Selecting messaging processing

Message processing determines how the Integration Server

processes the documents in the trigger queue. You can specify
serial processing or concurrent processing. In serial processing,
the Integration Server processes the documents in the trigger
queue one after the other. In concurrent processing,Integration
Server processes the documents in the trigger queue in parallel.
In the properties panel set the processing mode property to
serial or concurrent.
Serial – documents process one after the other
Concurrent - parallel

Configuring fatal error handling

If a trigger processes documents serially, you can

configure fatal error handling for the trigger. A fatal error
occurs when the trigger service ends because of an exception.
In the Properties panel, under, set the Suspend on error
property to True if you want Integration Server to suspend
document processing and document retrieval automatically
when a trigger service ends with an error. Otherwise, select
False. The default is False.

Configuring transient error handling

When building a trigger, you can specify what action

Integration Server takes when the trigger service fails because
of a transient error caused by a run‐time exception. That is,
you can specify whether or not Integration Server should retry
the trigger.
In the properties panel, in the retry until property set to
Maximum attempts reached – enter the max num of times the
integration server should attempt to re-execute the trigger
service. The default is 0 retries.
Successful- the Integration Server retries the trigger service
until the service executes to completion.
In the Retry interval property, specify the time period the
Integration Server waits between retry attempts. The default is
10 seconds.
 Set the on retry failure to
Throw exception -Indicate that Integration Server throws a
service exception when the last allowed retry attempt ends
because of an ISRuntime Exception.
Suspend and retry later -Indicate that Integration Server
suspends the trigger when the last allowed retry attempt ends
because of an ISRuntime Exception

Trigger service retries and shutdown requests

While Integration Server retries a trigger service,

Integration Server ignores requests to shut down the server
until the trigger service executes successfully or all retry
attempts are made. This allows Integration Server to process a
document to completion before shutting down.
In the property panel when we set to
False -The Integration Server shuts down only after it makes all
the retry attempts or the trigger service executes successfully.
This is the default value.
True -The Integration Server should interrupt the trigger
service retry process if a shutdown request occurs.