TRICK : Cannot start Integration Server
Copped a referrer link from a google search ("Flow Services are physically stored on the webMethods Integration Server), thought I'd provide some information to answer it as someone's trying to figure out how it all works.
WebMethods Flow Language
WebMethods Flow is a graphical language for performing common types of integration operations such as mapping, invoking, looping, branching.
The operations supported by the language:
Invoke - for kicking off other services
Map - for manipulating the pipeline (e.g. put a value into, drop a value or map from one to another)
Branch - for executing different paths depending on some condition (like if-else structures or like a switch statement depending on how you use it)
Loop - for iterating over the elements in a list structure in the pipeline
Repeat - I prefer to call it "retry", as it will retry the child operations while those child operations either fail or succeed (depending on how you want it to operate)
Sequence - for grouping together operations and alterning how exceptions will be treated (e.g. you might want to exit on failure, or exit on success, or ignore any errors/successes and just keep processing)
Exit - for jumping out of the flow, the parent, the loop, or back to a label on one of the parents etc
When you're developing, you're working off code on the Integration Server, which is generally a shared development box. So there is nothing really stored on your machine except any unsaved changes. It is stored on the Integration Server in an xml file (in a file called flow.xml inside the directory structure of the package it lives in) and converted into an in-memory representation of the tree of operations which can be executed (all under the covers.. you just write the flow code and it does the rest).
When flow doesn't cut it
Flow is not meant to be able to do everything, that's why you write java services to wrap up any extra code that flow becomes too messy, or you just can't do it.. and then invoke that java service from your flow. After a while you end up with enough "building block" services that you can reuse that functionality by simple invoke.
A little advice: Some people get tempted to do too much in java services, things like maps for instance: general rule I would say is to always use flow for mapping. Java just isn't as maintainable for mapping of nested structures as a few map steps that you've defined by click and drag.
Since this won't teach you anywhere enough to get on with development:
Still can't go past webMethods training for a great way to learn how to get going on webMethods
To get up and running and to get an idea of webmethods terminology, see my earlier post on Crash course on webmethods integration server
testing for webmethods, you'd be wanting WmUnit - the webmethods testing framework (shameless plug warning)
Refer to the ISDevelopersGuide.pdf that comes with the installation of the Developer tool
X)References are as follows:
webMethods Diagnostics Data.
webService-WSDL tab Data getting disappeared.
Universal Messaging integration with JNDI
Setup Universal Messaging
Setup Integration Server
How to import SSL certificates into webMethods Integration Server
Prepare the certificate
Import the certificate into Integration Server
How to create a new webMethods Integration Server instance
ItemReviewed: ALL ABOUT TUTORIAL WEBMETHOD SOFTWAREAG