Explore topic-wise InterviewSolutions in .

$LOOP will be ASSUMED, and a com.wm.lang.flow.FlowException will be THROWN if the EXIT is not in a LOOP

$loop will be assumed, and a com.wm.lang.flow.FlowException will be thrown if the EXIT is not in a LOOP

SET the "$MERGE" variable in restorePipeline or "merge" in restorePipelineFromFile to be true. This will ensure that EVERYTHING in the PIPELINE before a restorePipeline step is preserved.

Set the "$merge" variable in restorePipeline or "merge" in restorePipelineFromFile to be true. This will ensure that everything in the pipeline before a restorePipeline step is preserved.

If you have adapter notifications and adapter services then you will need to have two separate connections. Otherwise you may get strange ERRORS about transactions and the like. You should also AVOID having connection pools shared across different functional areas, even if they are pointing to the same database. The reason for this is that tuning the size of the pool becomes quite difficult if you have multiple TYPES of usage of a pool. You are also unable to easily CHANGE the database settings for one without impacting on the other.

One approach that seems to work quite WELL is to have separate pools for each package (generally.. not a hard and fast rule though), as your packages should generally be divided up according to functional area too.

If you have adapter notifications and adapter services then you will need to have two separate connections. Otherwise you may get strange errors about transactions and the like. You should also avoid having connection pools shared across different functional areas, even if they are pointing to the same database. The reason for this is that tuning the size of the pool becomes quite difficult if you have multiple types of usage of a pool. You are also unable to easily change the database settings for one without impacting on the other.

One approach that seems to work quite well is to have separate pools for each package (generally.. not a hard and fast rule though), as your packages should generally be divided up according to functional area too.

ALTHOUGH there is no tab to specify "order by" the same functionality is able to be specified in the "SELECT" tab. ONE of the columns in the is labelled "Sort Order" which will ALLOW you to specify the column(s) you WISH to sort by. To alter the order: simply alter the order of the columns SELECTED.

Although there is no tab to specify "order by" the same functionality is able to be specified in the "SELECT" tab. One of the columns in the is labelled "Sort Order" which will allow you to specify the column(s) you wish to sort by. To alter the order: simply alter the order of the columns selected.

•Create a JAVA service
•Create a private static object on the shared source (private static Object LOCK_OBJ = new Object(); )
•Have the code below on the java service source:
IDataCursor IDC = pipeline.getCursor();
IDataCursor idcResult = null;
try {
// put this section into a critical section to ENSURE single-threaded execution
synchronized(LOCK_OBJ)
{
Execute a flow service using Service.doInvoke
}
idc.destroy();
idcResult.destroy();
} catch (Exception EXC){ 
ServerAPI.logError(exc); 
idc.destroy();
throw new ServiceException(exc.toString()); }\

•Create a java service
•Create a private static object on the shared source (private static Object LOCK_OBJ = new Object(); )
•Have the code below on the java service source:
IDataCursor idc = pipeline.getCursor();
IDataCursor idcResult = null;
try {
// put this section into a critical section to ensure single-threaded execution
synchronized(LOCK_OBJ)
{
Execute a flow service using Service.doInvoke
}
idc.destroy();
idcResult.destroy();
} catch (Exception exc){ 
ServerAPI.logError(exc); 
idc.destroy();
throw new ServiceException(exc.toString()); }\

There is a special VARIABLE on the pipeline called $ITERATION which will be incremented as the loop operator works up through the list.

There is a special variable on the pipeline called $iteration which will be incremented as the loop operator works up through the list.

Set a flag in your catch block or leave a variable holding the error message in the pipeline.
Outside the catch block put a BRANCH on that variable or flag and if it is non-null then exit with FAILURE or CALL the service that GENERATES the exception.

Set a flag in your catch block or leave a variable holding the error message in the pipeline.
Outside the catch block put a branch on that variable or flag and if it is non-null then exit with failure or call the service that generates the exception.

Flow is not turned into JAVA code. It resides on disk as XML REPRESENTING the flow OPERATIONS which is then parsed and turned into an in-memory java tree of the operations. Although the UNDERLYING code that IMPLEMENTS the flow operations is java, it is stored on disk as XML.

Flow is not turned into java code. It resides on disk as XML representing the flow operations which is then parsed and turned into an in-memory java tree of the operations. Although the underlying code that implements the flow operations is java, it is stored on disk as XML.

Drop pipeline is an explicit cleanup. It is a REQUEST for the pipeline to remove a variable from the available list of variables and make the object it refers to available for garbage collection by the JAVA Virtual Machine.
Delete is purely a design TIME operation to remove the variable from the current VIEW. It is only of use if you have created a variable that you didn't mean to create. If you delete a variable that was there because it was previously in the pipeline when you change the view in developer you will SEE the variable appear again.

Drop pipeline is an explicit cleanup. It is a request for the pipeline to remove a variable from the available list of variables and make the object it refers to available for garbage collection by the Java Virtual Machine.
Delete is purely a design time operation to remove the variable from the current view. It is only of use if you have created a variable that you didn't mean to create. If you delete a variable that was there because it was previously in the pipeline when you change the view in developer you will see the variable appear again.

START the developer up in DEBUG mode, SIMILAR to the Integration server:
CD pathToWMInstall/Developer/bin
developer.bat -debug 10

Start the developer up in debug mode, similar to the Integration server:
cd pathToWMInstall/Developer/bin
developer.bat -debug 10

To change to the JDK USED by webMethods you will need to EDIT the IntegrationServerbinserver.bat or IntegrationServer/bin/server.sh file used to START up Integration Server.
Edit the file and change the following line to point to the JDK path 
SET JAVA_DIR=C:optj2sdk1.4.2

To change to the JDK used by webMethods you will need to edit the IntegrationServerbinserver.bat or IntegrationServer/bin/server.sh file used to start up Integration Server.
Edit the file and change the following line to point to the JDK path 
SET JAVA_DIR=C:optj2sdk1.4.2

RIGHT click on the ELEMENT for which you have to find the DEPENDENTS in the NAVIGATIONAL pannel.and click on the option find dependents.

Right click on the element for which you have to find the dependents in the navigational pannel.and click on the option find dependents.

Just right click on the ELEMENT ehich u want to see then u click LOCATE in NAVIGATION option then u can see that element in the navigation PANEL

Just right click on the element ehich u want to see then u click Locate in navigation option then u can see that element in the navigation panel

System LOCKS can be REMOVED by making the server side files of the element as redable.right Click on the elemet in developer which is system locked.and choose the lock properties. It will DISPLAY the server side files for the element.Make the files as readable and click the referesh BUTTON in the developer.You will find that the element is no more locked.

System locks can be removed by making the server side files of the element as redable.right Click on the elemet in developer which is system locked.and choose the lock properties. It will display the server side files for the element.Make the files as readable and click the referesh button in the developer.You will find that the element is no more locked.

Open the webMethods developer in EditPrespective.Select the flow step u wanna move just DRAG it to the place u WANT to move.Otherwise use the ARROW BUTTONS on the editor PANNEL to move the selected flow steps.

Open the webMethods developer in EditPrespective.Select the flow step u wanna move just drag it to the place u want to move.Otherwise use the arrow buttons on the editor pannel to move the selected flow steps.

Splitting one FIELD into several or merging fields, reordering PORTIONS of a MESSAGE or RENAMING fields are know as STRUCTURAL transformations

Splitting one field into several or merging fields, reordering portions of a message or renaming fields are know as structural transformations

Mapping is the PROCESS of PERFORMING transformations to resolve data representation differences between services or document formats. By linking variables to each other on the Pipeline tab, you can accomplish name transformations and STRUCTURAL transformations. However, to perform value transformations you must execute some CODE or logic. 
Developer provides two ways for you to invoke services: You can insert INVOKE steps or you can insert transformers onto the Pipeline tab. Transformers are the services you use to accomplish value transformations on the Pipeline tab.

Mapping is the process of performing transformations to resolve data representation differences between services or document formats. By linking variables to each other on the Pipeline tab, you can accomplish name transformations and structural transformations. However, to perform value transformations you must execute some code or logic. 
Developer provides two ways for you to invoke services: You can insert INVOKE steps or you can insert transformers onto the Pipeline tab. Transformers are the services you use to accomplish value transformations on the Pipeline tab.

We can change the Order of STEPS in a Flow Service of Various other services which are called in sequence within Flow service using "Shift Up and Shift Down" buttons exists at top of EDITOR Panel.
As well we can move any service or Map inside a SEQUENCE or BRANCH using "Shift LEFT and Shift Right" buttons

We can change the Order of steps in a Flow Service of Various other services which are called in sequence within Flow service using "Shift Up and Shift Down" buttons exists at top of Editor Panel.
As well we can move any service or Map inside a SEQUENCE or BRANCH using "Shift Left and Shift Right" buttons

ACLS are USED to give the authorization to the particular user groups.If u give ACL to administrator then the ADMIN group users who are there in that group they can have the acess to that particular service.Otherwise we can not use it.This is called ACL LOCKING.

ACLS are used to give the authorization to the particular user groups.If u give ACL to administrator then the admin group users who are there in that group they can have the acess to that particular service.Otherwise we can not use it.This is called ACL locking.

Select "session" from the menu in toolbar and click OPEN. key in the server IP and PORT on which you have to open the connection.The user NAME and password on that server.

Select "session" from the menu in toolbar and click open. key in the server IP and port on which you have to open the connection.The user name and password on that server.

Developer GETS disconnected from the server if the server goes down or if there is a problem in the network. DONOT close the developer.If you close the developer you wont be able to save the changes.Once the server come up or the network problem is RESOLVED. you will be automatically CONNECTED to the server and then you can retsore your SESSION.

Developer gets disconnected from the server if the server goes down or if there is a problem in the network. Donot close the developer.If you close the developer you wont be able to save the changes.Once the server come up or the network problem is resolved. you will be automatically connected to the server and then you can retsore your session.

SET evaluate LABEL property of branch step to true. Then set the label property of sequence with the VALUE on which it NEEDS to be processed.

Set evaluate label property of branch step to true. Then set the label property of sequence with the value on which it needs to be processed.

pub.file:GETFILE does not REQUIRE any MODIFICATIONS to the INTEGRATION SERVER.

pub.file:getFile does not require any modifications to the Integration Server.

The EXIT will THROW an java.lang.NullPointerException.

The EXIT will throw an java.lang.NullPointerException.

Start in level 9 DEBUG mode and write all server log INFORMATION to the screen.

Start in level 9 debug mode and write all server log information to the screen.

The purpose of Sequence operation is to group a subset of FLOW OPERATIONS so that they are TREATED as a unit.

The purpose of Sequence operation is to group a subset of Flow operations so that they are treated as a unit.

VARIABLE of TYPE DOCUMENT Type be REPRESENTED as "IData "

Variable of type Document Type be represented as "IData "

By EDITING the watt.server.dateStampFmt PARAMETER in the server.cnf FILE

By editing the watt.server.dateStampFmt parameter in the server.cnf file

The PORT is 5555

The Port is 5555

WHENEVER the PACKAGE is LOADED or re-loaded

Whenever the package is loaded or re-loaded

$LOOP will be ASSUMED, and a com.wm.lang.flow.FlowException will be THROWN if the EXIT is not in a LOOP

$loop will be assumed, and a com.wm.lang.flow.FlowException will be thrown if the EXIT is not in a LOOP

BRANCH operation conditionally EXECUTES an operation BASED on the value of a VARIABLE at run time

Branch operation conditionally executes an operation based on the value of a variable at run time

In the "MyPacknsmypackmyFlowflow.xml" FILE

In the "MyPacknsmypackmyFlowflow.xml" file

Save the current PIPELINE to a NAMED MEMORY location on the Integration SERVER

Save the current pipeline to a named memory location on the Integration Server

To RESTRICT PIPELINE ACCESS to only the DATA in this DOCUMENT

To restrict pipeline access to only the data in this document

The INTEGRATION Server LOGS the name-value pairs in the PIPELINE at that time

The Integration Server logs the name-value pairs in the pipeline at that time

USE a URL in the form:
http://servername:port/invoke/folder.subFolder.subsubFolder/serviceName 
(the PACKAGE NAME is not part of the URL in any way)

Use a URL in the form:
http://servername:port/invoke/folder.subFolder.subsubFolder/serviceName 
(the package name is not part of the URL in any way)

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. When a service in the flow executes, it has access to all data in the pipeline at that POINT.

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. When a service in the flow executes, it has access to all data in the pipeline at that point.

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.

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.

A STARTUP service is one that INTEGRATION Server automatically EXECUTES when it LOADS a PACKAGE into memory.

A startup service is one that Integration Server automatically executes when it loads a package into memory.

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.

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.

•webMethods Adapters
•webMethods Developer
•webMethods INTEGRATION Server
•webMethods Integration Platform
•webMethods Broker
•webMethods Monitor
•webMethods OPTIMIZE for Infrastructure
•webMethods TRADING Networks
•webMethods EDI Module
•webMethods EDIINT
•webMethods eStandards Modules
•webMethods PIM

•webMethods Adapters
•webMethods Developer
•webMethods Integration Server
•webMethods Integration Platform
•webMethods Broker
•webMethods Monitor
•webMethods Optimize for Infrastructure
•webMethods Trading Networks
•webMethods EDI Module
•webMethods EDIINT
•webMethods eStandards Modules
•webMethods PIM

•Integration and B2B
•Service ORIENTED Architecture
•Business PROCESS Management
•Business ACTIVITY MONITORING

•Integration and B2B
•Service Oriented Architecture
•Business Process Management
•Business Activity Monitoring

A company that provides integration tools. The key PRODUCTS INCLUDE Integration Server, Enterprise Server, Business Integrator, WORKFLOW and MAINFRAME Integration Server. webMethods is a company, not a PRODUCT.

A company that provides integration tools. The key products include Integration Server, Enterprise Server, Business Integrator, Workflow and Mainframe Integration Server. webMethods is a company, not a product.

•TIBCO
•webMethods
•Vitria
•iPlanet
•MQSeries (IBM)
•iPlanet
•BizTalk (MICROSOFT)
•WebLogic (BEA)

•TIBCO
•webMethods
•Vitria
•iPlanet
•MQSeries (IBM)
•iPlanet
•BizTalk (Microsoft)
•WebLogic (BEA)

The main disadvatages of using EAI systems:
•Constant change: The very nature of EAI is dynamic and requires dynamic project managers to manage their implementation.
•Lack of EAI experts : EAI requires knowledge of MANY issues and technical aspects.
•EAI is a tool paradigm: EAI is not a tool, but rather a SYSTEM and should be implemented as such.
•Building interfaces is an art : Engineering the solution is not sufficient. Solutions need to be negotiated with USER departments to reach a common consensus on the final outcome. A lack of consensus on interface DESIGNS leads to excessive effort to map between various systems data requirements.
•Loss of detail : Information that seemed unimportant at an earlier STAGE may become crucial later.
•Accountability : Since so many departments have many conflicting requirements, there should be clear accountability for the system's final structure.

The main disadvatages of using EAI systems:
•Constant change: The very nature of EAI is dynamic and requires dynamic project managers to manage their implementation.
•Lack of EAI experts : EAI requires knowledge of many issues and technical aspects.
•EAI is a tool paradigm: EAI is not a tool, but rather a system and should be implemented as such.
•Building interfaces is an art : Engineering the solution is not sufficient. Solutions need to be negotiated with user departments to reach a common consensus on the final outcome. A lack of consensus on interface designs leads to excessive effort to map between various systems data requirements.
•Loss of detail : Information that seemed unimportant at an earlier stage may become crucial later.
•Accountability : Since so many departments have many conflicting requirements, there should be clear accountability for the system's final structure.

Advantages of EAI solutions are:
•Streamlines business processes and helps raise organizational efficiency.
•Real time information access among systems.
•Maintains information integrity ACROSS multiple systems.
•Speedier TRANSACTIONS at reduced costs.
•If ONE of the applications misbehaves and requires to be shut down for maintenance, then with EAI, we can easily “decouple” it from REST of the systems. Which avoids having to bring down other systems.

Advantages of EAI solutions are:
•Streamlines business processes and helps raise organizational efficiency.
•Real time information access among systems.
•Maintains information integrity across multiple systems.
•Speedier transactions at reduced costs.
•If one of the applications misbehaves and requires to be shut down for maintenance, then with EAI, we can easily “decouple” it from rest of the systems. Which avoids having to bring down other systems.

Integration can be at different application layers:
•Data Level Integration:

1. BATCH data transfer, OR
2. On-line propagation of data updates

•API Level Integration:

1. Data is accessed through published API services

•Service Method Level Integration:

1. Common services shared by different applications

•User Interface Level Integration:The controller REACTS to the user input. It CREATES and sets the model.

1. Common user interface (e.g. web based) for unified access to multiple applications.

Integration can be at different application layers:
•Data Level Integration:

•API Level Integration:

•Service Method Level Integration:

•User Interface Level Integration:The controller reacts to the user input. It creates and sets the model.