webMethods Designer Training (1).ppt

webMethods CoE Designer TrainingPuneet Saxena Integration Architect 1 © 2012 WIPRO LTD | WWW.WIPRO.COM Table of Contents Introduction to Designer Document Types Flow Services Mapping Java Services Monitoring Services Flat File Handling Web Services JDBC Adapter Service Error Handling and Debugging 2 © 2012 WIPRO LTD | WWW.WIPRO.COM Introduction to Designer 3 © 2012 WIPRO LTD | WWW.WIPRO.COM Objectives • At the end of this section, you will be able to: – Understand various perspectives in designer – Basic webMethods configurations – Explain various properties 4 © 2012 WIPRO LTD | WWW.WIPRO.COM Designer • Designer is an integrated, Eclipse-based design environment providing powerful and comprehensive features that enables to model, develop and maintain enterprise-wide business processes and applications, build ESB projects, and SOA implementations. Software AG Designer is also fully integrated with many runtime servers like My webMethods Server, ESB, EntireX, ApplinX, Tamino, CentraSite, and Natural to provide visibility, management, and debugging capabilities to the end user in a single tool. 5 © 2012 WIPRO LTD | WWW.WIPRO.COM • Business analysts and developers work in this environment to design and create process models, user interfaces, task applications, and Web applications. • Developers can build both webMethods ESB services as well as standard Web services to provide customized solutions to support business process management, SOA initiatives, and integration projects. • Application developers work in this environment to create and maintain NaturalONE applications and services with Web-based user interfaces, SQL-based access to relational and non-relational data sources. 6 © 2012 WIPRO LTD | WWW.WIPRO.COM • Workbench refers to the desktop development environment. and navigation of workspace resources. The Workbench aims to achieve seamless tool integration and controlled openness by providing a common paradigm for the creation. or working with a specific type of resource.WIPRO.Workspace. 7 © 2012 WIPRO LTD | WWW. It also provides a set of functionality aimed at accomplishing a specific type of task. • A perspective defines the initial set and layout of views in the Workbench window. Perspectives define visible action sets. just select a path and give a name. which can be changed to customize a perspective. Workbench And Perspectives • The workspace is the directory where all the work will be stored. One or more perspectives can exist in a single Workbench window. Each Workbench window contains one or more perspectives. management.COM . It can be stored anywhere in the local system. . (This provides the same function as the Window > Open Perspective menu on the menu bar..WIPRO.• To open a perspective Click the Open Perspective button on the shortcut bar on the left side of the Workbench window. from the dropdown menu 8 © 2012 WIPRO LTD | WWW.).COM . To see a complete list of perspectives. select Other. basic preferences in the Preferences window. • Process Developer mode provides advanced configuration and property access to further define processes. • The Process Debugging perspective includes functionality that allows process debugging. allows uploading processes for analysis only. 9 © 2012 WIPRO LTD | WWW. and basic functions on the main toolbar.Process Development Perspectives • Process Development perspective includes basic process design functionality and property information to allow the non-developer to create processes. and also supports design and property information of the Process Development perspective. allows uploading processes for analysis as well as building and uploading processes for execution. Business Analyst mode displays only basic properties in the Properties view.WIPRO.COM . Process. which becomes a property inherited by all steps in the swimlane.COM . 10 © 2012 WIPRO LTD | WWW. It contains steps and logic.WIPRO. and uploaded to the Process Audit Database for analysis. Each swimlane designates an actor. Swimlane • Process projects serve as the parent structures for Designer processes and their assets. • Pools are constructs that help organize process project. • A process is the top-level asset in a process project. and it is the asset that is ultimately built and executed in the Process Engine. • Swimlanes are subdivisions of pools. A Designer process can have one internal pool and unlimited external pools.Process Projects. Pools. A single process project can contain one or more processes. Where a pool typically represents a single process. swimlanes typically serve to further subdivide a process. Subprocesses • Create steps onto the process and connect them to create a process. Steps are categorized by what they do.Steps.COM .WIPRO. 11 © 2012 WIPRO LTD | WWW. and also by their function in the process. • Types of Steps – Activity Steps – Receive Steps – Reply Steps – Adapter Notification (AN) Steps – Publish Steps – Terminate Steps – Gateway Steps • A subprocess is not a self-contained process. It can exist only inside its parent process. specified in their properties. A subprocess is a group of steps in a container. and is treated as a step in the process. COM . data logging for examination at run time. and output data for that step and into the pipeline – In an activity step. and information flowing out of a step is called output. • Step inputs and outputs are used to define flow signatures. the step can output new process data into the pipeline.WIPRO. branching and looping logic in the process. 12 © 2012 WIPRO LTD | WWW. Information flowing into a step is called input. and KPIs.Step Inputs and Outputs • Each step in a process has information that flows into and out of it. • Process data assigned in Designer to flow in and out of steps needs to be mapped to physical data that the underlying services require in order for the process to execute. • Data can enter the process in two ways – In a receive step. a subscription document can trigger or join the process. Specialized transition types.Step Transition • Transitions indicate the flow of control in the process being passed from one step to another. • Step transition types: – Split – Branch – Join – Join Timeout – If Condition – Else – Error – Timeout – Step Iterations Exceeded – Unsatisfied Join 13 © 2012 WIPRO LTD | WWW. • Transition conditions are based on logical data. rather than physical data.WIPRO. are permitted from each step. as well as splits and branches. and can be specified in the Process Development perspective. These transitions each have a label and a description that are distinct from the condition itself.COM . COM . based on the values of specific fields in the subscription document 14 © 2012 WIPRO LTD | WWW. using each transition’s source Label (step name) as the identifier can also be created. OR.WIPRO. • Join conditions can use AND. Subscription Filters • Join conditions occur when a step has multiple input transitions. • Complex join conditions by using a combination of NOT/AND/OR/ Unsynchronized OR statements. or Unsynchronized OR statements in their logic.Join Conditions. • Subscription filters provide the option to limit which instances of a document are able to trigger or join a process. and multiple transitions to create a join string. parentheses. and establish or match the correlation ID used by a process instance 15 © 2012 WIPRO LTD | WWW. • Correlation services are written in webMethods Developer or in the flow service editor in Designer. At least one receive step in a process must be designated Allow this step to start new process instance (a start step).WIPRO.COM . Each receive step that can start a new process instance has a Correlation Service property.Correlation Services • Correlation Services are used to allow external documents to join running process instances. Without the Process Developer capability (using Business Analyst mode). and it cannot be executed. Designer places the run-time elements associated with a step on the physical server that is mapped to the Integration Server Name for the step.COM .Building and Uploading Processes • Enabling the Process Developer capability (using Process Developer mode) allows to build a process and upload it to the Process Audit database for execution. and conditions. Designer then places these generated runtime elements on the Integration Server and uploads information about the process to the Process Audit Database. the process is not built.WIPRO. a process can be uploaded to the Process Audit Database for analysis only. 16 © 2012 WIPRO LTD | WWW. such as steps. subscription filters. Designer creates the elements that execute at run time based on the information in the process. • Each step in a process model is associated with a specific Integration Server Name. • When a process is build. transitions. and JMS receive protocols. or multiple processes. • A debugging session requires that process starts with a receive step with an IS document input. energy. • The Process Simulation feature provides a mechanism to simulate processes and see details about how they run. Process Debugging supports subscription. and to see how that data behaves as it travels through the pipeline. 17 © 2012 WIPRO LTD | WWW. or even a test environment.Process Debugging and Process Simulation • Debugging a process involves running it with tools that allows to inspect the way it behaves with real data. • Simulation provides the opportunity for testing and tweaking processes in the design phase. By simulating a process. and resources can be saved that might otherwise be misspent on deploying solutions that do not fit business needs. time.COM .WIPRO. simple service (Web service). before they ever reach production. Different Perspectives • • • • • • • • • • • Java development Platform Plug-in JDT (Java Development Tooling) Plug-in Plug-in Development CentraSite Plug-ins Data Tools Platform Plug-in Data Tools Platform Eclipse Modeling Framework (EMF) Web Tools Project webMethods CAF (Composite Architecture Framework) webMethods Task 18 © 2012 WIPRO LTD | WWW.COM .WIPRO. Insert your Screenshots here 19 © 2012 WIPRO LTD | WWW.WIPRO.COM . WIPRO.Document Types 20 © 2012 WIPRO LTD | WWW.COM . COM .Objectives • At the end of this section. you will be able to: – create Document Types – reference Document Types in the Pipeline – discuss options for Document Type Validation – Publish / Subscribe documents to broker 21 © 2012 WIPRO LTD | WWW.WIPRO. COM .WIPRO. 22 © 2012 WIPRO LTD | WWW.IS Document Type • An IS document type contains a set of fields used to define the structure and type of data in a document (IData object). An IS document type can also be used to build a document or document list field and use as the blueprint for pipeline validation and document (IData object) validation. IS document type is used to specify input or output parameters for a service or specification. – IS document types improve accuracy. because it helps to make a change in one place (the IS document type) rather than everywhere 23 © 2012 WIPRO LTD | WWW. – Using an IS document type to build document or document list fields can reduce the effort needed to declare input or output parameters or the effort/time needed to build other document fields. – IS document types make future changes easier to implement.COM .• IS document types can provide the following benefits: – Using an IS document type as the input or output signature for a service can reduce the effort required to build a flow. because there is less opportunity to introduce a typing error typing field names.WIPRO. • Creating an IS Document Type from an XML Document.Creating a Document Type • Create an empty IS document type and define the structure of the document type by inserting fields. • Creating an IS Document Type from an E-form Template stored on the file system or in a content repository 24 © 2012 WIPRO LTD | WWW. or XML Schema. DTD.WIPRO.COM . Referencing fields especially useful for information that is repeated over and over again.COM . 25 © 2012 WIPRO LTD | WWW.Document Reference • An IS document type (including a publishable document type) can be used to build a document reference or document reference list field.WIPRO. By referencing an IS document type instead of creating a new one. such as address information. it reduces the time required to create fields and maintain better consistency for field names. The changes might make pipeline references invalid. or dropped. the changes affect any document reference and document reference list variables defined by that IS document type. 26 © 2012 WIPRO LTD | WWW. • When an IS document type is edited. assigned a value.Pipeline References • A pipeline reference is where a variable in a document reference or document reference list in Pipeline view is linked to another variable.COM .WIPRO. services publish instances of publishable document types. A trigger specifies a service that the Integration Server invokes to process the document. • In a business process.WIPRO.COM . • In a publication environment that includes a Broker. Essentially.Publishable Document Types • A publishable document type is a named schema-like definition that describes the structure and publication properties of a particular kind of document. a published document can start or join a process. a publishable document type is an IS document type with specified publication properties such as storage type and time-to-live. Designer provides tools that can be used to ensure that these two document types remain synchronized. 27 © 2012 WIPRO LTD | WWW. each publishable document type is associated with a Broker document type. • In an integration solution that uses the publish-and-subscribe model. and triggers subscribe to publishable document types. Triggers • Broker/local triggers establish subscriptions to publishable document types and specifies how to process instances of those publishable document types. • The publishable document type acts as the subscription piece of the Broker/local trigger. The service is the processing piece. • A condition associates one or more publishable document types with a single service.COM . • Broker/local triggers can contain multiple conditions. When the Broker/local trigger receives documents to which it subscribes. 28 © 2012 WIPRO LTD | WWW.WIPRO. the Integration Server processes the document by invoking the service specified in the condition. the Integration Server appends “_1” to the Broker document type name.Creating a Publishable Document Type • To create a publishable document type.COM . set publication properties for an IS document type. when an IS document type publishable is created. 29 © 2012 WIPRO LTD | WWW. If a document type with this name already exists on the Broker.WIPRO. • If the Integration Server on which a session is connected to a Broker. Integration Server automatically creates a Broker document type and assigns the Broker document type a name. Properties that can be set include: specifying whether instances of the publishable document type should be saved in memory (volatile storage) or saved on disk (guaranteed storage) during processing. and specifying how long instances of the publishable document type should remain on the Broker once they are published. This name corresponds to the following format: wm::is::folderName::documentTypeName. That is. • Designer creates a publishable document type automatically when using an e-form template as the source for the IS document type. the publishable document types that is created can be used only in local publishes.COM . 30 © 2012 WIPRO LTD | WWW. instances of the publishable document types can only be published and subscribed to with in the same Integration Server.• If the Integration Server on which a session is not connected to a Broker.WIPRO. COM .WIPRO. The pub:publish:envelope document type defines the content and structure of the envelope that accompanies the published document. 31 © 2012 WIPRO LTD | WWW. The envelope records information such as the sender’s address. sequence numbers.About the Envelope Field • All publishable document types contain an envelope (_env) field. The envelope is much like a header in an e-mail message. and other useful information for routing and control. the time the document was sent. This field is a document reference to the pub:publish:envelope document type. • Each adapter notification has an associated publishable document type.Adapter Notifications and Publishable Document Types • Adapter notifications determine whether an event has occurred on the adapter's resource and then sends the notification data to Integration Server in the form of a published document.COM . Integration Server automatically generates a corresponding publishable document type.WIPRO. but appends PublishDocument to the name. 32 © 2012 WIPRO LTD | WWW. When an adapter notification is created in Designer. • Designer assigns the publishable document type the same name as the adapter notification. Document Type Validation • • • • XML schema FlatFile Schema Document Type Defination Publishable Document Type 33 © 2012 WIPRO LTD | WWW.WIPRO.COM . Validation • Input/Output Validation - In input/output validation, the validation engine in webMethods Integration Server validates the inputs and/or outputs of a service against the declared input and output parameters of the service. • Document Validation - Validate an individual document (IData object) in the pipeline instead of the entire pipeline. • Pipeline Validation - Pipeline validation is the process of verifying the contents of the pipeline against an IS document type. • XML Validation - XML validation is the process of verifying the structure and content of an XML document against an IS schema. • Validation within Java Service - 34 © 2012 WIPRO LTD | WWW.WIPRO.COM Insert your Screenshots here 35 © 2012 WIPRO LTD | WWW.WIPRO.COM Flow Services 36 © 2012 WIPRO LTD | WWW.WIPRO.COM COM . you will be able to: – Describe the capabilities of webMethods Flow • • • • • Repeat Loop Branch Exit Sequence – Try /Catch Flow implementation – Run your Flow services – Debug your Flow Service • SavePipeline / TracePipeline 37 © 2012 WIPRO LTD | WWW.WIPRO.Objectives • At the end of this section. • Integration Server is installed with an extensive library of built-in services for performing common integration tasks. interacting with back-end resources and publishing documents to the Broker. Services are build to carry out work such as extracting data from documents.COM . flow. 38 © 2012 WIPRO LTD | WWW. Adapters and other add-on packages provide additional services that ca be used to interact with specific resources or applications. webMethods graphical implementation language. enables to quickly aggregate services into powerful sequences called flow services. They are executed by Integration Server.Services • Services are method-like units of logic that operate on documents.WIPRO. WIPRO. • Flow services created using Designer are saved in XML files on Integration Server. • Although flow services are written as XML files.COM . • Any service can be invoked within a flow (including other flow services). 39 © 2012 WIPRO LTD | WWW.Flow Service • A flow service is a service that is written in the webMethods flow language. This simple yet powerful language encapsulate a sequence of services within a single service and manage the flow of data among them. Flow service cannot be created with a text editor. they are maintained in a format that can only be created and understood by Designer and webMethods Developer. A flow step is a basic unit of work (expressed in the webMethods flow language) that webMethods Integration Server interprets and executes at run time. When a service in the flow executes. it has access to all data in the pipeline at that point.WIPRO. The webMethods flow language provides flow steps that invoke services and flow steps that let allow to edit data in the pipeline.COM . 40 © 2012 WIPRO LTD | WWW. It allows services in the flow to share data. • 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.Flow Step and Pipeline • A flow service contains flow steps. The pipeline starts with the input to the flow service and collects inputs and outputs from subsequent services in the flow. COM . The control steps allows to:  Conditionally execute a specified sequence based on a field value.  Retry a specified sequence until it succeeds. • Various Control Steps are:  Sequence  Loop  Branch  Repeat  Exit 41 © 2012 WIPRO LTD | WWW.WIPRO.Control Steps • Control steps that allow to direct the execution of a flow service at run time.  Repeat a specified sequence (loop) for each element in an array field. 42 © 2012 WIPRO LTD | WWW. at times it is necessary to explicitly group a subset of flow steps using SEQUENCE so that they can be treated as a unit. The SEQUENCE step is implicit in most flow services (that is.COM .Sequence • Groups a set of flow steps into a series.WIPRO. the steps in a flow service are treated as a series). However. Loop • Executes a set of flow steps once for each element in a specified array. • There can be simple and nested loops. 43 © 2012 WIPRO LTD | WWW.WIPRO.COM Branch • Executes a specified flow step based on the value of a specified variable in the pipeline. • Branch can be build in two ways: – Branch on a switch value (switch case) – Branch on an expression (if-else) • Branch on a switch value and an expression for the same BRANCH step is not possible. 44 © 2012 WIPRO LTD | WWW.WIPRO.COM Repeat • Re-executes a set of flow steps up to a specified number of times based on the successful or non-successful completion of the set. • Repeat can be used as: – Re-execute (retry) a set of steps if any step within the set fails. – Re-execute a set of steps until one of the steps within the set fails. 45 © 2012 WIPRO LTD | WWW.WIPRO.COM COM . • Exit step can be specify exit from: – The nearest ancestor (parent) LOOP or REPEAT flow step to the EXIT flow step. or exit a LOOP or REPEAT without throwing an exception).WIPRO. – A specified ancestor flow step to the EXIT flow step. 46 © 2012 WIPRO LTD | WWW. – The parent flow step of the EXIT flow step.Exit • Controls the execution of a flow step (for example. throw an exception without writing a Java service. abort an entire flow service from within a series of deeply nested steps. – The entire flow service. WIPRO.Invoke and Map • Invoke executes a specified service. and dropping variables from the pipeline). it request a service within a flow. It adjust the contents of the pipeline at any point in a flow service. 47 © 2012 WIPRO LTD | WWW.COM . • Map performs specified editing operations on the pipeline (such as mapping variables in the pipeline. adding variables to the pipeline. from beginning to end (or until an error condition forces it to stop).WIPRO. 48 © 2012 WIPRO LTD | WWW.COM . The service executes on the Integration Server on which there is an open session. The service executes once.Run Flow Service • Designer invokes the service (just as an ordinary IS client would) and receives its results. • Results from the service are returned to Designer and displayed in Service Result view. or on the Integration Server specified in the launch configuration. This allows to quickly examine the data that the service produces and optionally change it or save it to a file. – Set breakpoints to specify points in a flow service at which processing should stop. and Conditions.WIPRO. – Disabling Flow Steps. – Modifying the Flow Service Pipeline while Debugging. 49 © 2012 WIPRO LTD | WWW. – Change the values passed to each step in the flow service.COM .Debugging Flow Services • Debugging a service can be done as: – Execute a flow service one flow step at a time and view the results of each step. Transformers. – Use the Step Over (execute the current flow step ). and Step Out (Return to the parent flow from a child) commands during a debug session. Step Into (open a child flow to debug the individual flow steps within it). Save and Restore the Flow Service Pipeline • Because the pipeline contains the data that a service operates against.WIPRO.COM . the ability to save and restore the pipeline while debugging a service is something frequently wanted to do. – Saving the Pipeline at Run Time • The pipeline gets saved automatically to a file at run time by using the Pipeline Debug property 50 © 2012 WIPRO LTD | WWW. • Saving the Flow Service Pipeline while Debugging – Saving the Pipeline to a File • save the pipeline to ocal file system • save the pipeline to the IntegrationServer_directory\pipeline directory on the machine on which Integration Server reside. Additionally. – programmatically load a saved pipeline at run time by invoking pub.• Restoring the Flow Service Pipeline while Debugging Restoring a pipeline is useful to inspect the values in a particular pipeline file (perhaps one that contains the pipeline from a failed service).COM . There are three ways to restore the contents of the pipeline: – manually load the saved pipeline into the Variables view while debugging in Designer.WIPRO. – automatically load the saved pipeline at run time by using the Pipeline Debug property . it is useful in many debugging situations.flow:restorePipelineFromFile at the point where to modify the pipeline 51 © 2012 WIPRO LTD | WWW. Insert your Screenshots here 52 © 2012 WIPRO LTD | WWW.COM .WIPRO. WIPRO.COM .Mapping 53 © 2012 WIPRO LTD | WWW. WIPRO.Objectives • At the end of this section.COM . you will be able to: – perform complex mapping – use transformers – understand Pipeline Variable Substitution 54 © 2012 WIPRO LTD | WWW. • In Designer.Mapping data in Flow service • Since systems rarely produce data in the exact format that other systems need.COM . 55 © 2012 WIPRO LTD | WWW.WIPRO. data transformations can be accomplished by mapping data. flow services needs to be build that perform data transformations. Data transformation resolves differences in the way data is represented within documents that applications and systems exchange. WIPRO.This type of transformation resolves differences in the way data is named.• By mapping following types of transformations can be accomplished – Name transformations .This type of transformation resolves differences in the data type or structure used to represent a data item. – Value transformations . – Structural transformations .This type of transformation resolves differences in the way values are expressed 56 © 2012 WIPRO LTD | WWW.COM . Basic Mapping • Basic mapping are the tasks to manage the pipeline contents and the values of variables in the pipeline.WIPRO.COM . Various tasks are: – Link variables to each other – Assign values to variables – Drop variables from the pipeline – Add variables to the pipeline – Variable substitution 57 © 2012 WIPRO LTD | WWW. structure. By using transformers. • Transformers are well suited for use when mapping data from one document format to another. When mapping data between formats.Transformers • Transformers are the services use to accomplish value transformations in the Pipeline view. In this way. there is a need to perform several name. Only transformer can be inserted into a MAP step.WIPRO. the flow service in which mapping data between formats could potentially consist of a single MAP step where transformers and links between variables handle all of the data transformations. entire document-to-document mapping is done in a single view.COM . and value transformations. 58 © 2012 WIPRO LTD | WWW. WIPRO. 59 © 2012 WIPRO LTD | WWW. • Any service can be used as a transformer. C services. • Transformers in a MAP step are independent of each other and do not execute in a specific order.COM . including flow services. Designer only displays the links between pipeline variables and transformers. Designer does not display any implicit linking for a MAP step. When inserting transformers.Inserting a Transformer • Transformers can only be inserted in a MAP step. • In a MAP step. and Java services. assume that Integration Server executes the transformers concurrently at run time. • The transformers inserted into a MAP step operate on the same set of pipeline data. • The output of one transformer cannot be used as the input of another transformer in the same MAP step. Insert your Screenshots here 60 © 2012 WIPRO LTD | WWW.WIPRO.COM . COM .WIPRO.Java Services 61 © 2012 WIPRO LTD | WWW. you will be able to: – describe the capabilities of webMethods Java Services – write Java Services – understand the role IData plays in writing Java Services – understand how different Integration Server data structures are exposed to Java services – understand various ways of invoking Java services and generating Java code 62 © 2012 WIPRO LTD | WWW.COM .Objectives • At the end of this section.WIPRO. • When Java service is build.” character. All Java services that reside in the same folder are methods of the same class. Java services follow a simple naming scheme: – The service name represents the Java method name.Java Service • A Java service is a public static method in a Java class file on Integration Server. 63 © 2012 WIPRO LTD | WWW. nested folders are implemented in a class that is scoped within a Java package.WIPRO. – The interface name represents the fully-qualified Java class name. services that reside in. the system automatically combines the service into the class file associated with the folder in which it is created in. • Because Java class names cannot contain the “.COM . • An IData object can contain any number of key/values pairs (elements). The keys in an IData object must be Strings.IData Object • The IData object is the universal container that services use to receive input from and deliver output to other programs. 64 © 2012 WIPRO LTD | WWW.WIPRO.COM . • It contains an ordered collection of key/value pairs on which a service operates. The values can be any Java objects (including IData objects). This class also provides methods for inserting new elements. • The class that used to position a cursor in an IData object is IDataCursor. Next.WIPRO. or next element in the object. • The IDataCursor class contains methods for performing basic cursor operations such as placing the cursor at the first. • After positioning the cursor on the element. last. 65 © 2012 WIPRO LTD | WWW. respectively can be used. and deleting elements.Get and Set IData Objects(IData Cursors) • Getting data from and putting data into IData elements takes two steps. position the cursor at the IData element. getting key names. the getValue or setValue methods to read or write the value of that element. get or set the data in that element. First.COM . Insert your Screenshots here 66 © 2012 WIPRO LTD | WWW.COM .WIPRO. Monitoring Services 67 © 2012 WIPRO LTD | WWW.WIPRO.COM . COM . you will be able to: – set up logging for Services and Processes – describe the key features of My webMethods Monitor – monitor services 68 © 2012 WIPRO LTD | WWW.Objectives • At the end of this section.WIPRO. WIPRO.COM . 69 © 2012 WIPRO LTD | WWW. Integration Server maintains most of the audit logging data in the webMethods.Audit Logging • Audit logging for webMethods products provides important data that needs to monitor webMethods system activity and correct problems. • Service Audit Logging . Designer.Error audit logging provides data about exceptions thrown by services running on Integration Server • Session Audit Logging .WIPRO.Service audit logging provides data about flow and coded (for example.Session audit logging provides data about sessions opened on Integration Server by Developer. 70 © 2012 WIPRO LTD | WWW.COM . third‐party clients. and other servers. Administrative events are configuration changes related to Integration Server security activities. Security audit logging provides data about security‐related administrative and operational events that occur on Integration Server.Types of Logging • Error Audit Logging . Administrative events are configuration changes related to Integration Server security activities.Security audit logging provides data about security‐related administrative and operational events that occur on Integration Server. Java) services that run in Integration Server • Security Audit Logging . • Business Process Audit Logging .COM .• Document Audit Logging • Guaranteed Delivery Audit Logging .WIPRO.If configure the guaranteed delivery capability in Integration Server is configured.Tasks are created in Designer and run on My webMethods Server • Integration Process Audit Logging 71 © 2012 WIPRO LTD | WWW. guaranteed delivery audit logging provides data about guaranteed delivery transactions.Business process audit logging provides data for business processes modeled in Designer that run on Integration Servers • Task Audit Logging . guaranteed delivery. session.WIPRO. either directly or by another service.Logging Setup • Integration Server writes error.set up customized logging on a service‐by‐service basis in Developer or Designer. – Verbose . document. – Brief . and Mediator transaction audit logging data to files or database tables collectively called the IS Core Audit Log.COM . • Integration Server writes business process. service. except that the logger also writes the input pipeline in all cases 72 © 2012 WIPRO LTD | WWW. integration process. and task audit logging data to database tables collectively called the Process Audit Log • Levels of Logging – perSvc .The logger writes start and failure or start and success log entries for every service every time the service is called.Same as Brief. security. • Trace .COM . • Debug . except that existing error handling renders the failure unlikely to affect other operations or products.Failures that end operations in such a way that the operations cannot successfully continue without user intervention. Failure is VERY likely to affect other operations or products. • Warn .Code-level statements recording unusual conditions or decisions that might lead to errors.Logging Level • Fatal .Code-level statements recording program flow and state during normal execution. 73 © 2012 WIPRO LTD | WWW.No information for the product or facility is written to the server log. or unexpected or unusual conditions that might signal impending failure • Info . • Error .Problems that do not end operations.Success of an event that you need to know about.Same as Fatal. • Off .WIPRO. Service Audit Logging • Track when services start. • Track whether services completed successfully or failed.COM . • Record the client that called the service. and the Integration Server port on which the client connected. their status. • Resubmit services. 74 © 2012 WIPRO LTD | WWW. and their duration.WIPRO. Business Process Audit Logging • Identify business processes. and ended. changed status. • Record the path that business processes took at run time. 75 © 2012 WIPRO LTD | WWW.COM . • Track when business processes and business process steps started. • Resubmit business processes at specified steps. • Track whether business processes and steps completed successfully or failed.WIPRO. WIPRO.My webMethods and webMethods Monitor • My webMethods is a Web-based. log in to the My webMethods user interface. monitoring and administration user interface for managing webMethods components. this user account is assigned the password manage. Data can be logged about business processes.COM . Logging into My webMethods. • webMethods Monitor displays data that webMethods Integration Server and webMethods Optimize for Process have logged. services. The Administrator user account is defined at installation. 76 © 2012 WIPRO LTD | WWW. • To access Monitor functionality. and documents. means logging into all webMethods components that are incorporated into My webMethods. and resubmit process instances Enable process models and define settings that are used by running process instances of those models • Generate reports about process instances. 77 © 2012 WIPRO LTD | WWW. suspend. Resubmit services and documents Monitor. task users. process models.COM .WIPRO. and task roles • Archive or delete audit data from the IS Core Audit Log and Process Audit Log database components • Monitor functionality is in the Applications section in both the Administration and the Monitoring sections of My webMethods. resume.Monitor and My webMethods User Interface • • • • View data logged by other webMethods products. Archive or delete audit data from the IS Core Audit Log and Process Audit Log database components • System Settings . and roles and configure access to Monitor privileges.Identify the Integration Server with which the My webMethods Server is to interact. groups.Define users.WIPRO.Enable process models for execution and define settings that are used by running process instances of the models • Archive Audit Data . 78 © 2012 WIPRO LTD | WWW.COM . • Business Processes .Administration Section • User Management . Resubmit services. • Documents .COM .View the details about individual process instances. Suspend. including drilling down to view information about the steps within a process. Resubmit documents 79 © 2012 WIPRO LTD | WWW.View documents that have been logged to the IS Core Audit Log database component. • Services .WIPRO.Monitoring Section • Process Instances . resume.View audit data that Integration Server have logged for services. and stop process instances. Insert your Screenshots here 80 © 2012 WIPRO LTD | WWW.COM .WIPRO. Insert your Screenshots here 81 © 2012 WIPRO LTD | WWW.WIPRO.COM . Flat File Handling 82 © 2012 WIPRO LTD | WWW.COM .WIPRO. WIPRO. you will be able to: – describe the webMethods Flat File Architecture – create a Flat File Dictionaries and Schemas using Developer – parse delimited. and complex Flat Files – create custom Format services 83 © 2012 WIPRO LTD | WWW. fixed-length.COM . variable-length.Objectives • At the end of this section. In other words. Therefore. the application receiving the flat file must have knowledge of the structure of the flat file. • A single logical record of application data is externalized as a set of records without any structural information.WIPRO.FlatFile • Flat files present complex hierarchical data in a record–based storage format. the metadata of a flat file is separated from the data and contained in a flat file schema.COM . • Flat files enables to send data to any application in a mutually agreed upon format so that the data in the files can be read and processed 84 © 2012 WIPRO LTD | WWW. which unlike XML does not embed structural information (metadata) within the data. to read the flat file. through the flat file schema. • Composites contain multiple fields.COM . • Records (also known as segments) are sequences of fields and/or composites.WIPRO. 85 © 2012 WIPRO LTD | WWW. including how to identify records and separate those records into fields. users must create a flat file schema that contains a particular flat file’s structural information.Architecture • All flat files consist of a list of records containing fields and composites • Fields are atomic pieces of data. • To communicate using flat files. • webMethods can exchange all types of flat files but can process only certain types of flat files. and repeated record structures.COM . • A flat file dictionary is a repository for elements that refers from flat file schemas.WIPRO. including delimiters. records. This allows to create record definitions in a dictionary that can be used across multiple flat file schemas. 86 © 2012 WIPRO LTD | WWW.Flat File Schema and Dictionaries • A flat file schema is the blueprint that contains the instructions for parsing or creating a flat file and is created as a namespace element in the webMethods Integration Server. A flat file schema also acts as the model against which an inbound flat file can be validated. • The decision to define records in a flat file dictionary or in a flat file schema depends on the type of flat files that needs to be parsed. This blueprint details the structure of the document. Reusing record definitions reduces the amount of memory consumed by a flat file schema. This parser measures the lengths and positions of records in terms of bytes.This parser splits a file into records of the same pre-specified length.This parser expects a specific delimiter to indicate the end of a record.COM .WIPRO. a character or character representation or hex-decimal value or octal value or unicode characters. – Fixed Length Record Parser.Parsing of Records using Flat File Schema • Record Parsers . there are four record parser: – Delimited Record Parser .This parser expects each record to be preceded by two bytes that indicate the length of the record – EDI Document Type Record Parser -This parser is used only for EDI flat files and provides additional functionality needed to properly parse EDI documents 87 © 2012 WIPRO LTD | WWW.A record parser breaks a flat file into individual records • In webMethods. rather than characters – Variable Length Record Parser. record identifiers compare the value that occurs in the record.COM . The name of the record definition must match the value obtained by the record identifier. at the specified offset. 88 © 2012 WIPRO LTD | WWW. – Nth Field record identifiers use the value of the specified field as the record identifier.A record identifier looks at a record and extracts an identifier out of the data. The identifier is then used to connect the record definition in a flat file schema with a particular record in the flat file. to all the record names defined in the flat file schema.• Record Identifiers . • In webMethods there are two methods of record identifications: – Starts at position . These identifiers count from zero (0).WIPRO. COM . 89 © 2012 WIPRO LTD | WWW.WIPRO.Format Services • Service that formats the field String in a flat file schema or dictionary and ensures that the value of the String meets the format restrictions of the format service. WIPRO.COM .Insert your Screenshots here 90 © 2012 WIPRO LTD | WWW. WIPRO.COM .Web Services 91 © 2012 WIPRO LTD | WWW. COM .WIPRO.Objectives • At the end of this section. you will be able to: – create Web Service provider nodes – Use Web Service consumer nodes – work with custom fault documents 92 © 2012 WIPRO LTD | WWW. distributed systems.Web Services • A Web service is a collection of functions that are packaged as a single unit and published to a network for use by other software programs.COM . • Designer uses Web service descriptors to encapsulate information about Web services and uses Web service connectors to invoke Web services 93 © 2012 WIPRO LTD | WWW.WIPRO. Web services are building blocks for creating open. COM . 94 © 2012 WIPRO LTD | WWW. and transport serialization formats that should be used between the consumer (requester) and the provider of the Web service. transport protocols.Web Service Descriptors and Connectors • Web service descriptor (WSD) is an element on Integration Server that defines a Web service in IS terms.WIPRO. The WSD contains the message formats. In essence. the WSD represents an agreement governing the mechanics of interacting with that service. Web service connector contains the information and logic needed to invoke an operation defined in the WSDL document used to create the consumer Web service descriptor. The WSD encapsulates all the information required by the provider or the consumer (requester) of a Web service. data types. It also specifies one or more network locations at which a Web service can be invoked. • Web service connector is a flow service that Integration Server creates at the time it creates the consumer Web service descriptor. when a connector is invoked it calls a specific operation of a Web service. A provider Web service descriptor will expose one or more IS services as operations. External users can access the Web service through the registry and invoke the IS services remotely. • A consumer Web service descriptor defines an external Web service.COM . which can be published to a registry as a single Web service. allowing Integration Server to create a Web service connector (WSC) for each operation in the Web service. The Web service connector(s) can be used in Designer just like any other IS flow service.• A provider Web service descriptor defines a Web service that is hosted on the Integration Server.WIPRO. 95 © 2012 WIPRO LTD | WWW. that is. a service “provided” to external users. The IS service becomes an operation in the provider WSD.WIPRO.COM . and encodes and returns the output to the clients. Integration Server provides an environment for executing services efficiently and securely. use the IS service as an operation in a provider Web service descriptor • A provider Web service descriptor (WSD) is created from one or more IS services or from a single WSDL document. and is designed to allow the IS services to be invoked as Web services over a network. as well as the data needed at run time to process the request and response. Integration Server uses the existing service signature as the input and output messages for the operation. To expose an IS service as a Web service. calls the requested services. • A service first provider WSD refers to provider WSDs created from an existing service on Integration Server. Operations and bindings ca be added to a service first provider WSD. It receives and decodes requests from clients. 96 © 2012 WIPRO LTD | WWW. The provider Web service descriptor contains all the data required to create a WSDL document for the IS Web service.Exposing IS Services as Web Services • Any service in any Integration Server package can be turned into a Web service. In this case. A Web service provider can also distribute WSDL files directly to consumers. • The provider WSD can be published to a UDDI registry (or other publicly accessible server) as a Web service. along with IS document types defining the input and output signature of the generated flow services and then implement any required logic within the placeholder flow service. 97 © 2012 WIPRO LTD | WWW.WIPRO. Designer uses the message and operation definitions from the WSDL to generate a “placeholder” flow service for each operation encountered in the WSDL.• A WSDL first provider WSD refers to a provider WSD created from an existing WSDL document or from a Web service acquired from a UDDI registry.COM . Operations or bindings cannot be added to a WSDL first provider WSD. which can be invoked remotely by an external user. as well as data needed for certain Integration Server run-time properties. • The Web service connector is a flow service that: – Uses an input and output signature that corresponds to the input and output messages of the Web service operation.Invoking Web Services • Create a consumer Web service descriptor in Integration Server to invoke Web services located on remote servers. 98 © 2012 WIPRO LTD | WWW. It contains all the data from the WSDL document that defines the Web service. Integration Server creates a Web service connector for each operation contained in the WSDL document.WIPRO. • When creating a consumer Web service descriptor from a WSDL document. – Contains flow steps that extract data from the output message returned by the Web service. – Contains flow steps that create and send a message to the Web service using the transport.COM . and location information specified in the Web service. protocol. COM .WIPRO.Insert your Screenshots here 99 © 2012 WIPRO LTD | WWW. JDBC Adapter 10 0 © 2012 WIPRO LTD | WWW.WIPRO.COM . COM .Objectives • At the end of this section. you will be able to: – configure an Adapter Connection – create Adapter Services – create Notification Services 10 1 © 2012 WIPRO LTD | WWW.WIPRO. • Using the JDBC Adapter. relational databases. AS/400.COM .WIPRO.JDBC Adapters • The webMethods JDBC Adapter is an add‐on to the webMethods Integration Server that enables to exchange data with relational databases through the use of a JDBC driver. Universal Database (UDB) – 􀂄 IBM Informix – 􀂄 Microsoft SQL Server – 􀂄 Oracle – 􀂄 Sybase – 􀂄 Teradata 10 2 © 2012 WIPRO LTD | WWW. and insert and update data in. The adapter provides seamless and real‐time communication with the database without requiring changes to existing application infrastructure. webMethods Integration Server clients can create and run services that execute transactions to retrieve data from. • The JDBC Adapter supports the following databases: – 􀂄 DB2 for OS/390. Connections are configured using the webMethods Integration Server Administrator tool.Adapter Connection • The JDBC Adapter connects to a database through a JDBC driver at run time.WIPRO. One or more connections can be created at design time to use in integrations. • JDBC Adapter connections contain parameters that the Integration Server uses to manage connections to the database so that they can be used by the JDBC Adapter to provide services. and the types of those connections.COM . 10 3 © 2012 WIPRO LTD | WWW. Must have webMethods administrator privileges to access the JDBC Adapter’s administrative screens. The number of connections created. depend on the types of databases connected to and integration needs. WIPRO. one Java service. • XA_TRANSACTION Allows the connection to support two‐phase transactions executed across multiple databases. • LOCAL_TRANSACTION The operations on the same connection in one transaction boundary will be committed or rolled back together. In one transaction boundary.COM . That is. all of the operations on multiple connections will be committed or rolled back together.. the connection automatically commits (Auto Commit) all operations. or several steps in a flow service 10 4 © 2012 WIPRO LTD | WWW. one flow service. It can be in one adapter service. from the beginning to the end of a transaction.Transaction Types • NO_TRANSACTION The connection provides no transaction control over the operations being performed. A transaction boundary means the scope of the transaction. 10 5 © 2012 WIPRO LTD | WWW. • Adapter services can be called from flow or Java services to interact with database tables.COM . • Adapter services are based on templates provided with the JDBC Adapter.Adapter Services • Adapter services allows to connect to the adapters resource and initiate an operation on the resource from the Integration Server. These specifications needs to be provide to create a new adapter service. Each template represents a specific technique for doing work on a resource. The Integration Server then uses adapter connections defined earlier to execute the adapter services. such as using the SelectSQL template to retrieve specified information from a database. The adapter services perform database operations by calling JDBC APIs. • An adapter service template contains all the code necessary for interacting with the resource but without the data specifications.WIPRO. COM . Updates existing information in table Inserts new information into table when dealing with a large volume of data. Updates information in table when dealing with a large volume of data. Deletes rows from a table Defines and executes custom SQL Defines and executes a SQL statement Calls a stored procedure © 2012 WIPRO LTD | WWW.WIPRO.Adapter service Type and Templates Adapter Service Type Select SQL Adapter Service Template SelectSQL Description Retrieves specified information from a database table. Insert SQL Update SQL Batch Insert SQL Batch Update SQL Delete SQL Custom SQL Dynamic SQL Stored Procedure 10 6 InsertSQL UpdateSQL BatchInsertSQL BatchUpdateSQL DeleteSQL CustomSQL DynamicSQL StoredProcedure Inserts new information into table. update. • JDBC Adapter notifications are polling‐based.Adapter Notifications • An adapter notification monitors a specified database table for changes. 10 7 © 2012 WIPRO LTD | WWW.COM .WIPRO. That is. so that the appropriate Java or flow services can make use of the data. the Integration Server will invoke the notification periodically based on the polling interval. or delete operation. such as an insert. Publishes notification data by calling a stored procedure inside database Publishes notification data for multiple insert. or delete operations on multiple tables for a given database.COM .WIPRO. 10 8 © 2012 WIPRO LTD | WWW. update.Adapter Notification Types and Templates Notification Type Notification Template Insert Notification Update Notification Delete Notification Basic Notification Stored Procedure Notification Ordered Notification InsertNotification UpdateNotification DeleteNotification BasicNotification StoredProcedure Notification OrderedNotification Description Publishes notification of insert operations on table Publishes notification of update Operations on table Publishes notification of delete operations on table Polls a table for data using a SQL Select operation. Insert your Screenshots here 10 9 © 2012 WIPRO LTD | WWW.WIPRO.COM . Service Error Handling and Debugging 11 0 © 2012 WIPRO LTD | WWW.COM .WIPRO. you will be able to: – Describe the Java Exception Handling procedure – Distinguish between checked and unchecked exceptions – Throw exceptions from Java – Catch exceptions in Java and Flow – Use built-in Services to help debug your Services – Debug Services using a debugger 11 1 © 2012 WIPRO LTD | WWW.Objectives • At the end of this section.COM .WIPRO. or a designation assigned by a developer.WIPRO.COM . • Unexpected System Error The unexpected result of a system failure. • Expected System Error The predictable result of a known invalid action. memory.Classifying error types • Application Error The result of business process or application failure. These errors are thrown by the server or its components (adapters) and are manifested as Java exceptions. 11 2 © 2012 WIPRO LTD | WWW. use of incompatible software. or starvation of resources. disk space. or any other event. It is a clean API practice to handle as much exception logic as possible from within the throwing service. discretion should be used. The BRANCH operator is handy for managing logic and application errors. • For Flow development. Only when the failure is beyond the developer's control should the Inetgration Server be notified via a Service Exception.WIPRO. This logic is well-known.• Most webMethods Integration Server development is in one of two languages -. webMethods makes available several exception handling techniques.Flow and Java. When throwing errors inside of webMethods Java services. standard exception handling available is using Try-Catch blocks. 11 3 © 2012 WIPRO LTD | WWW. • For Java development. Using defensive programming will help to avoid unwanted failures. though. The EXIT operator can be used to exit from an entire Flow or just a section of Flow.COM . WIPRO.Handling error notifications • How error notifications are handled once caught is required business logic for any integration and must be addressed during the Requirements Gathering phase of a project. An error should be classified and reported to any relevant applications as well as delivered via email to developers.COM . • The most common error reporting method is email notification. A generic Error Handling service can be written to manage these tasks 11 4 © 2012 WIPRO LTD | WWW. This approach helps to deal with critical issues quickly. COM . call the EXIT operator and provide a detailed message for the failed action 11 5 © 2012 WIPRO LTD | WWW.WIPRO. • Using Flow.Throwing errors • In order to use Exception Handling services. we must write code that throws an error to be caught. Using Flow-based Try-Catch Blocks • Another technique for handling Flow exceptions is to create a TryCatch block • The technique for creating Try-Catch blocks in Flow is as follows: SEQUENCE (EXIT on SUCCESS).WIPRO. Label: CATCH Catch block Flow goes here 11 6 © 2012 WIPRO LTD | WWW. Label: MAIN SEQUENCE (EXIT in FAILURE).COM . Label: TRY Try block Flow goes here SEQUENCE (EXIT on DONE). Insert your Screenshots here 11 7 © 2012 WIPRO LTD | WWW.WIPRO.COM . WIPRO.11 8 © 2012 WIPRO LTD | WWW.COM . WIPRO.COM .11 9 © 2012 WIPRO LTD | WWW. 12 0 © 2012 WIPRO LTD | WWW.WIPRO.COM .