Explore topic-wise InterviewSolutions in .

Software AG’s webMethods Integration Platform is an enterprise service BUS solution that quickly connects all SYSTEMS and applications no matter where they reside. This POWERFUL solution offers a proven and pre-integrated software suite that MAKES it easy to quickly integrate systems, servers, processes, devices, partners and data.

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.

UDDI stands for Universal, Description, Discovery, and Integration. UDDI is a platform-independent standard that describes SOA (Service Oriented Architecture) registry and its INTERFACE. By using UDDI, clients can discover registered businesses (organizations or service providers) and their web services. Furthermore, UDDI provides APIS for creating and updating registry information. UDDI defines a set of APIs that can be used to access and modify DATA stored in the registry. Some of these APIs are as follows:

• UDDI Inquiry: Through this API, you can find registry entries and retrieve their information. 
• UDDI Publication: You can ADD NEW entries to the registry with this API or edit existing ones.
• UDDI Security: It determines which security settings are applied to registry entities.

Open the INTEGRATION Server and CLICK the 'session' menu on the toolbar. Please enter the IP address and PORT DETAILS for the server you wish to CONNECT to. Enter the username and password and simply click 'Connect'.

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.

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.

To SWITCH or change the JDK USED by webMethods, you must edit IntegrationServer/bin/SERVER.sh or IntegrationServer/bin/server.bat used to start Integration Server. SAVE the file after changing the JDK path as follows.

The 'Run in Browser' command ENABLES you to run a service from a browser. Using this command, Designer prompts you for input values of service, creates the URL (Uniform Resource Locator) that is needed to invoke the service based on the input values you provide and passes the URL to your browser. If you use the 'Run in Browser' command to run a service, the browser (not Designer) triggers or invokes the service and receives the results. Open your browser and enter the following URL to invoke a service:

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.

When you INVOKE the pub.flow:tracePipeline service, the names, and values of all pipeline fields are WRITTEN to the SERVER log. When you invoke pub.flow:clearPipeline, all pipeline fields are REMOVED or cleared. You can SPECIFY fields that shouldn't be removed/cleared using this service.

The pub.flow:savePipeline service is used to save the current pipeline to a SPECIFIC location in memory on the Integration Server. Pipelines are stored in memory and can be RETRIEVED later with the pub.flow:restorePipeline service. Pub.flow:restorePipeline service restores a pipeline that has previously been saved by pub.flow:savePipeline.

If that savePipeline is successfully invoked, a SNAPSHOT of pipeline fields will be saved under the key specified by $name. A pipeline is identified in memory by the string name "$name". If this VALUE is not provided, an exception will be thrown.

As part of the startup and shutdown services SECTION of the Properties dialog box, you can specify what services webMethods Integration Server should AUTOMATICALLY execute when packages are loaded into memory or unloaded from memory.

• Startup Service: This displays the list of startup services a package can use, as well as the list of startup services assigned to a package. When a webMethods Integration Server loads a package into memory, it automatically executes a startup service. A startup service is useful to generate initialization files and prepare the environment (like SETTING up or cleaning up) before a package is loaded.
• Shutdown Service: This displays the list of shutdown services a package can use, as well as the list of shutdown services assigned to a package. When a webMethods Integration Server unloads a package from memory, it automatically executes a shutdown service. Shutdown services are useful for PERFORMING cleanup tasks like closing files and cleaning TEMPORARY data. In addition, they can be used to capture state information or work-in-progress before a package is unloaded.

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.

Flow services are services written in the webMethods flow LANGUAGE. With a flow service, you can encapsulate a sequence of services into a SINGLE service and manage the data flow between them.

Example: Suppose, for example, you created a flow service that ACCEPTS PURCHASE orders from buyers and executes the following SERIES of services before submitting them to your internal ordering system:

• Receives a purchase order submitted by the buyer.
• Record the order in an audit trail.
• Performs credit checks.
• Posts the order in the ordering system.

This is the Java-based IDE (Integrated development environment) that allows you to open sessions on WebMethods IS (Integration server) and develop your services. It is used to develop code on WebMethods IS. In addition, it also supports the development of integration applications in WebMethods Flow. Webmethod flow is a GRAPHICAL PROGRAMMING language specially used to simplify and speed up the development of integration applications.

Since version 7 of webMethods, webMethods Developer has been replaced by a new Eclipse-based IDE called webMethods Designer. As of yet, this transition has not been completed, and both products exist SIDE by side.

The webMethods Product Suite comprises FOUR modules, as follows:

• Service-Oriented Architecture.
• Integration and B2B (BUSINESS to Business).
• Business Activity Monitoring.
• Business Process MANAGEMENT.

WebMethods Integration platform provides components for designing, executing, and managing integration solutions. You can categorize these components as follows:

• Runtime components: Run the Integration solution you developed.
  • WebMethods Integration server: In webMethods, it is one of the core application servers. It's a multiplatform and Java-based enterprise integration server. Integration of diverse services, such as the conversion of data between formats and communication between systems, is supported by this component.
  • WebMethods Broker: It is a high-performance message router. The Publish-Subscribe Model supports both synchronous and asynchronous message-based integrations. 
  • WebMethods Trading networks (TN): Trading networks are an essential part of the webMethods PRODUCT suite that facilitates B2B transactions. This component RUNS on the webMethods IS (Integration server) and allows your firm to interact with external companies, generally referring to them as partners and marketplaces, etc. 
  • WebMethods Adapters: Adapters run on webMethods IS (Integration server). These adapters connect back-end resources in the enterprise to the integration platform. 
  • Webmethods workflow: A set of activities performed by several individuals.
  • 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. Moreover, my webMethods Server provides a central administration and monitoring platform for most of the webMethods Suite's products.
• Design-time components: These components provide tools for designing and integrating solutions.
  • WebMethods Developer: This is the IDE (Integrated development environment) that allows you to OPEN sessions on IS (Integration server) and develop your services.
  • WebMethods workflow Designer: It is used to develop and deploy workflows. A customized Eclipse-based tool, WebMethods Designer can be used for a wide variety of purposes, including service development, CAF (Composite Application Framework) page design and coding, and deployment to the My WebMethods Server. 
  • WebMethods MODELER: It is a graphical tool used for designing and implementing business processes.
• Administrative components: They configure the runtime environment and monitor how Integration solutions are executing on the Platform.
  • WebMethods Administrator: The administrator installs, configures, and maintains the WebMethods IS (Integration Server).
  • WebMethods Monitor: This tool allows you to view information logged by webMethods IS and webMethods Optimize.