Google News
logo
WebMethods Interview Questions
The following are the advantages of EAI :
 
* EAI maintains information integrity over multiple systems.
* It can streamline processes that include data from various software applications.
* It enables the flow of information between separate software programs within the company also from outside the organizational systems.
* The best EAI advantage is that it allows organizations to recognize and respond to opportunities more quickly.
The disadvantages of EAI are as follows:
 
* The nature of EAI requires dynamic project managers to manage their implementation
* EAI has many departments to conflict requirements; there should be clear accountability for the systems.
* Lack of EAI experts to resolve any technical issues.
* The lack of agreement on interface designs leads to more effort to map between various systems data needs.
Workflows and FlowServices enable you to automate and optimize monotonous tasks based on a set of predefined rules and business logic. These features give you the power to connect apps, devices, and on-premises systems with only clicks and zero code. Although Workflows and FlowServices help you to accomplish the same goal, there are significant differences between both the features.

Workflows FlowServices
Designed for Citizen developers. Designed for Integration specialists.
Offers a visual, drag and drop interface to create business use cases. Offers steps and constructs from within the steps to create business use cases.
Offers in-built triggers to automatically trigger workflows when relevant events occur and actions to perform specific tasks. Offers in-built applications and services to perform specific tasks.
Supports executing other FlowServices and workflows from within a workflow. Supports executing other FlowServices from within a FlowService.
Ideal for scenarios where basic data transformation on application data is required. This means you can execute simple business use cases with Workflows. Ideal for scenarios where complex integrations and advanced data transformation are required. This means you can execute simple as well as complex business use cases with FlowServices.
Dropping a variable from Pipeline In or Pipeline Out will remove it from the pipeline. If pipeline variables aren't being used by subsequent services, they can be dropped. By removing unneeded variables, you reduce the size of the pipeline at run time, as well as the complexity of the Pipeline In and Pipeline Out displays. This can make the Pipeline view much more usable when you are working with a complicated flow. The term "drop pipeline" implies an explicit cleanup.
 
Delete is a design-time operation that removes a variable from the current view. It is only useful if you create a variable by mistake. When you change the view in developer after you delete a variable that was previously in the pipeline, the variable will appear again.
Here are two methods to check memory usage:
 
Top command : It provides a dynamic, real-time view of the current state of the system. You can view system information and process information, including up-time, average load, running tasks, number of logged-in users, and RAM usage. Also, you can view the processes that your users are running/using on your server.

Free command : Top command, however, can sometimes be too much for your purposes. If all you need is to see how much memory is free and used on your system, you can use the free command.
Sequence operation is used to group the processing variations to support error handling. It helps to build a set of steps to treat as a group to execute one after another in order. By default, all the steps in aflow service, except the child branch are executed as the members of an implicit sequence step.
In most cases, systems do not produce data in the exact format that other systems require, so you often need to build flow services that transform the data. When applications and systems exchange documents, data transformation resolves differences in data representations. In Designer, data transformations are accomplished through mapping. Among the types of transformation you can achieve via mapping are:
 
Name transformations : The purpose of this transformation is to correct naming differences. By performing name transformations, the value and position of a variable remain the same in the document structure, but the variable's name is altered.

Structural transformations : These types of transformations resolve differences in the data types or structures that represent an item. The value of the variable does not change when you perform structural transformations; only its data type or position in the Document structure changes.

Value transformations : These types of transformations resolve differences in how values are expressed. A value transformation changes the data contained in the variable, but the variable's name and position remain the same.
The lock feature lets you control access at the user (individual) level, whereas ACLs let you control access by groups of users. ACLs provide authorization to specific user groups. By giving ACL access to the administrator, all admin group members included in the group will have access to the specific service. 
Flow service is not curved or turned into Java code. It resides as XML on the disk on behalf of the flow operations. Afterwards, it parsed and transformed into a Java tree of operations. Although the flow operation is coded in Java, it is stored on a disk as XML.
The date format to be used in log files is specified by the watt.server.dateStampFmt parameter. It is best to edit the watt.server.dateStampFmt in the server.cnf file to change the logging date format for WebMethods Integration Server. This parameter specifies the date format to be used in the server log file as well as in the Integration Server Administrator.