When your sequence document is ready to test, you can run it through the Studio's debugger. The debugger moves easily between the text and graphical representations of the application. You can set break points, single-step, view component properties, examine the effects on the document at each step, and so on.

After you've decided your new service passes muster, another few clicks in the Orchestrator Studio will deploy your new service to the crossvision installation, and it's ready to be used.

At your service

Software AG's crossvision is, if anything, extensive. This is simultaneously a strength and a weakness. On one hand, the odds are very good that whatever your specific SOA-related needs are, some constituent of crossvision will meet them. Aside from its impressive integration, crossvision's graphical UI and pre-built components combine to make the construction of an SOA site something even less-experienced programmers can do.

On the other hand, it is easy to get lost inside crossvision. That problem is exacerbated by the fact that the names of the component products recently changed, but the documentation -and even some file names haven't caught up. For example, if you come across the name