Usages of Designer in webMethods 8.2
Version 8.2 of Designer can be used for everything that was done in Developer. Developer is replaced by Designer.
Below are some notes on how to use Designer as a Developer and New features of Designer (webMethods Version 8.2)
Step by step usage of Designer:
v Connect to Integration Server
We have to connect first to an Integration Server.
From Designer, select Window > Preferences > +Software AG > Integration Server >Default > Edit
Set the server Host, Port, User, and Password. You can use the defaults for the check-boxes "Connect immediately" and "Connect at start up". Leave your development is name as Default or else you can edit name .you can add more than one IS but as a default server only one we can set.
If we want to connect another server we have to select that particular server name to check that server details. By default its using default server.
Checking IS is connected.
By default we are in Business Analyst mode. To get to advanced options and settings you have to select an icon in the toolbar i.e. Process Developer This is different than the Process Development perspective. We are using Process developer mode for implementing process model or else creating the flow service using developer.
v Select a Perspective
Perspectives are collections of views, each of which includes specific information about a process. Each perspective has a default set of views. You can add views to or remove them from a perspective, and move views to different locations in Designer. If you can reset a perspective and restore its default setting sand undo changes. If you want to save changes, you can customize a perspective.
Ã Proccess development Perspective:
By default, the Process Development perspective includes basic process design functionality and property information. We can enabled the Advanced Process Development capability preference in Window > Preferences > General > Capabilities adds Process Development advanced configuration and property for allows uploading processes for analysis as well as building and uploading processes for execution. Basically Process development perspective we are using for implementing Process Modal.
We can select Service Development, Process Development, UI Developmentâ¦.etc. Perspective. we can use service development perspective in designer Instead of using developer for creating flow service.
Ã Service Development Perspective
webMethods Service Development provides tools and features that developers can use to build and test services. webMethods Service Development also provides tool to connect to Integration Server, manage packages, and create the elements needed to support services such as document types, triggers, and Web service descriptors.
Before You Use Designer for Service Development
Designer builds and edits services and other elements directly on a webMethods Integration Server. To use Designer for service development, We must have:
· Access to an Integration Server on which you can build and debug services.
· A user account on that webMethods Integration Server.
· âDevelopersâ ACL (access control list) on that Integration Server.
· Create a server definition that defines the connection between Designer and Integration Server
Opening the Service Development Perspective
Designer provides a Service Development perspective that contains the views, editors, and tabs needed to build services and other supporting elements. To open the Service Development perspective.
· In Designer, select Window > Open Perspective > Other.
· In the Open Perspective dialog box, select Service Development. Click OK. Designer switches to the Service Development perspective.
For services implementation we can use show views:
In Designer select Window > Show View > Other
Using palette view we can implement flow service by flow steps and build in services.
In Designer we can implement our flow service logic using Flow steps like MAP,BRANCH,LOOP,REPEAT,SEQUENSE,EXIT and we can also insert build in service .
In Designer, clicking the button next to or opening the Palette view displays a list of commonly used services. You can edit the Windows > Preferences SoftwareAG > Service Development > Flow Service Editor - add/remove favorite services to customize your palette view.
We have Properties, pipeline, service result tabâ¦etc to set properties and check data flow.
Creating New document type in designer using service development perspective.
Ã Creating a Document Type
We can create an IS document type in the following ways:
· Create an empty IS document type and define the structure of the document type by inserting fields. In Designer: File > New > Document Type
Drag the document type field that you want to define from the Palette to the document type tab in the editor.Type the name of the field and then press ENTER. With the field selected, set field properties and apply constraints in the Properties view.
· Create an IS document type from a source file, such as an XML Schema, DTD, XML document.
· Create an IS document type from a Broker document type.
Using designer we can see a service in 3 view:Tree,Layout,Input/Output
v Building Services Using the Tree Tab or Layout Tab
In the flow service editor, we can view and build flow services using the Tree tab or Layout tab.
Ã Building Services Using the Tree Tab
Designer uses the Tree tab as the default tab for building and viewing flow services.
On the Tree tab, Designer lists flow steps sequentially from top to bottom, and executes steps in that order. The Tree tab provides a more condensed view of a flow service.
Ã Tree view of the service:
Ã Layout view of a service:
Layout tab provides a more graphical view in which to create flow services. In the Layout tab, a flow service looks similar to a flow chart. Designer displays shapes for flow steps as well as for the start and end of the flow service. Lines connect the flow steps and show the order in which the flow steps execute.
The Tree tab and Layout tab provide the same capabilities for building a flow service, work in whichever tab you find easier to use. You can easily switch between the tabs when building a flow service.
Ã Input/Output view of the service:
In Input/output tab we specify the variables that we want the service to return to the calling program or client. We can declare the input and output parameters for a service using the Input/Output tab. On the left side of this tab, we define the variables that the service requires as input. On the right side, we define the variables the service returns to the client or calling program.
For a flow service, the input side describes the initial contents of the pipeline. The output side identifies the variables produced by the flow service and returned to the pipeline.
v We can work on only selected Working Set
A working set is a subset of elements on one or more Integration Servers. You can then select only the packages you want to see and filter out the rest packages. To create a working set
· On the Package Navigator toolbar, click and select Select working set > New > Integration Server Elements > Next > name for the working set > select the elements to add to the working set > Finish .
The Pipeline view offers a graphical representation of all of your data through which we can map data and inspect the contents of the pipeline. we use the tools on this view to route variables between services. The Pipeline view displays the pipeline for invoked services or MAP steps in a flow service.On the pipeline view, right click and
· You can lock service for edit. (Ctrl-L)
· You can unlock the service.( Ctrl-U)
· You can see Lock properties, Find dependents, find references, Inspect pipeline references of the service.
· Select "View as HTML" if you want to save the view of the pipeline and/or print it.
v For running or debugging we can Launch Configurations:In Run > Run Configurations you can set up different inputs for a service for different uses. They all inputs get saved as files in your workspace.
In Designer, you create launch configurations to run services. A launch configuration contains the information Designer needs to execute a service. You can create one or more launch configurations for each service. When running the service, Designer invokes the service and receives its results. The service executes once, from beginning to end on the IS.
v Debug Perspective
Using the Debug perspective for debug a service. The Debug perspective contains various views for helping you debug your service. When you debug a flow service, Designer provides tools that you can use to monitor the execution path of the flow service and examine the service pipeline at various points during service execution. While debugging, you can also use Designer to save or modify the current pipeline.
v Saving and restoring the flow service pipeline while debugging
We can now save the pipeline while we are debugging a service either to your local drive or to the Integration Server's pipeline directory, instead of using build in service like pub. flow: restore Pipeline and pub. flow: save Pipeline service in your main service. You can restore pipeline data from that saved file for debugging.
Ã Saving the Flow Service Pipeline while Debugging
You can save the pipeline to a file, which you can use to restore the pipeline to its current state at a later point in time. This is useful when you want to debug another service against the current set of pipeline values or if you want to restore the pipeline to this exact state later in the debugging process. We can save pipeline as locally or save in integration server.
Ã Restoring the Flow Service Pipeline while Debugging
Restoring a pipeline is useful when you simply want to inspect the values in a particular pipeline file, For example, you can use it to replace the existing pipeline with a different set of values when stepping though a flow service with the debugging tools. We can restore pipeline as locally or restore pipeline from integration server.
Ã Automatically Saving or Restoring the Pipeline at Run Time
Use the Pipeline debug property to save or restore the pipeline for a flow service at run time. The ability to save and restore the pipeline is especially useful when you are testing and debugging the service. If you set Pipeline debug to Save, Integration Server saves the entire contents of the pipeline to a file just before the service executes. You can use the data in the saved pipeline file to debug and troubleshoot the service or to restore the pipeline.
I hope this helps anybody looking to start working on designer for service development.
Please feel free to point out any corrections.