Google News
logo
WebMethods Interview Questions
The publish-and-subscribe model is a specific type of message-based solution in which messages are exchanged anonymously through a message broker. Applications that produce information that needs to be shared will make this information available in specific types of recognizable documents that they publish to the message broker. Applications that require information subscribe to the document types they need.

At run time, the message broker receives documents from publishers and then distributes the documents to subscribers. The subscribing application processes or performs work using the document and may or may not send a response to the publishing application.

In a webMethods system, webMethods Integration Server or applications running on Integration Server publish documents to a messaging provider. You can use Universal Messagingand/or Broker as messaging providers. The messaging provider then routes the documents to subscribers (webMethods messaging trigger) located on other Integration Servers. The following sections provide more detail about these components.
The webMethods Integration platform is made up of several diversified components that you use to design, execute and manage Integration solutions.
 
These components fall into three basic categories and I am trying to give a brief as per my knowledge.
 
1) Runtime components
2) Design-time components
3) Administrative components
 
1) Runtime components : Execute the Integration solution that you develop.
 
a) WebMethods Integration server: Is the platform runtime component and serves as an entry point for systems and applications that you want to integrate.

b) WebMethods Broker: This is a high-speed message router. It is an asynchronous message-based solution that are built a publish-subscribe model..

c) WebMethods trading networks and e standard: In a document-oriented exchange scenario.

d) Webmethods Adapters: Adapters run on the Integration Server. They connect backend resources in the enterprise to the integration platform.

e) webmethods workflow: A series of tasks performed by one or more people.

f) MywebMethods Server: As a major component of the webMethods Suite, it plays a critical role in providing the UI (User Interface) framework so that customers can develop Web, portlet, and BPM (Business process management) applications. 


2) Design Time Components : Provide a tool for developing and testing an Integration solutions.
 
a) WebMethods workflow Designer : Develop and deploy Integration logic and related workflow.

b) WebMethods Developer : This is the IDE (Integrated development environment) that allows you to open sessions on IS (Integration server) and develop your services.

c) WebMethods Modeler : It is a graphical tool used for designing and implementing business processes.


3) Administritive Components : Configures the runtime environment and monitor the execution of Integration solution running on the Platform.
 
a) webMethods Administrator : The administrator installs, configures, and maintains the WebMethods IS (Integration Server).

b) WebMethods Monitor : This tool allows you to view information logged by webMethods IS and webMethods Optimize.

c) WebMethods manager.
1. Integration server(IS) : webMethods Integration Server is one of the core application servers in the webMethods platform. It is a Java-based, multiplatform enterprise integration server. It supports the integration of diverse services, such as mapping data between formats and communication between systems. An integration server may also be known as the core of webMethods Enterprise Service Bus.
 
2. webMethods Broker : webMethods Broker is the core of the webMethods ESB, it is the hub of the ESB. It is the backbone of the webMethods ESB and supports synchronous and asynchronous message based integrations using Publish-Subscribe Model.
 
A webMethods Broker can be connected to multiple clients (Here client is an Integration Server), but an Integration Server can be connected to only one Broker.
 
3. Developer : webMethods Developer is the IDE through which you can open your session on IS and you can develop your services. You can open more than one session on webMethods developer, from webMethods version 8.2 Developer has been deprecated and Software AG focuses on using the Designer tool instead.
 
4. Designer : webMethods Designer is a customized eclipse based tools which can be used for multiple purposes from service development to CAF page design and coding as well as deploying it to My webMethods server. It is used for a variety of purposes let us list it all down.
 
a) Service Development (flow service, java service, web service, etc.)
b) BPM Development (BPM process design, deploying)
c) CAF page development
d) DSP page development
e) working with centrasite
 
For every specific work you do on Designer you have to select the corresponding perspective in Designer. For example, if you want to develop some flow service then you have to use the Service Development perspective in the designer.
 
5. MyWebMethods Server : It is basically a portal based server hosted on jetty. It is used for the administration and monitoring of Integration Server, Broker, Trading Network and other portal and portlet applications.
 
6. Trading Networks(TN) : Trading Networks is the component of the webMethods product suite which is used for B2B transactions. It is a component that runs on the webMethods Integration server(IS) and enables your enterprise to connect with external enterprises preferably call them as partners to your enterprise and marketplaces and etc. Trading Networks supports almost all standards of e-Business standards for communication such as EDI , RosettaNet , SWIFT , FIX , ebXML , aseXML etc .
webMethods Broker : The role of the Broker is to route documents between information producers(publishers) and information consumers (subscribers).
 
The Broker receives, queues, and delivers documents. It is a pub-sub model. Only one broker server can have multiple instances which can be connected to IS.
 
Broker uses – Messaging Protocols
 
* webMethods proprietary messaging protocol
 
* Java Message Service (JMS) protocol.
The arrows connecting the flow steps in the Layout tab show how (sequence) the steps are executed. It is possible to change the order that steps are executed in a flow service by moving or relocating steps. Also, a step can be relocated as a child of another step in the flow service.
 
Changing the sequence of steps in a flow service on the Layout tab
 
* Click the Layout tab, then select the step whose execution order you wish to change.
* You can change the location of flow steps using the buttons, i.e., Cut, Copy, and Paste on the toolbar or in the context menu.

Changing the sequence of steps in a flow service on the editor panel
 
* You can change the steps by pressing the 'Shift Up' or 'Shift Down' buttons.
* By pressing the 'Shift Left' and 'Shift Right' buttons, you can move a service or branch in a sequence.
Triggers, specifically webMethods messaging triggers, establish subscriptions to publishable document types. Triggers also specify the services that will process documents received by the subscription. Within a trigger, a condition associates one or more publishable document types with a service.

Prior to Integration Server 9.5 SP1, a webMethods messaging trigger was called a Broker/local trigger.
When Integration Server creates consumer web service descriptors, it creates web service connectors which is a flow service. The web service connector usually contains logic and information/data required to invoke an operation specified in a WSDL (Web Service Description Language) document used to create the consumer web service descriptor.
 
As Integration Server creates consumer web service descriptors based on WSDL documents, it creates web service connectors for each operation the portType contains in the WSDL document. If, for example, a WSDL document contains 2 portType declarations, each of which contains 3 operations, then Integration Server creates a total of 6 web service connectors.
There are two types of Loops. They are as follows:
 
Times Loop : It allows us to perform a certain action n number of times. Times Loop specifies the number of times the Loop block to be executed.  

Each item : Each item is used to iterate each key in the given array. It allows us to perform certain actions for all the elements of a collection.
The following are the list of some companies that provide EAI tools:
 
* webMethods
* TIBCO
* Vitia
* iPlanet
* WebLogic (BEA)
* MQSeries (IBM)
* BizTalk (Microsoft) etc.
The following are the major categories of the EAI tool :
 
1. API Level Integration:
   * Published API services can access data.

2. Data Level Integration:
  * Batch data transfer
  * On-line propagation of data updates.
 
3. Service Method Level Integration:
  * Various applications share standard services.
 
4. User Interface Level Integration:
  * Common user Interface for unifies access to various applications.