Testing The Composite Application For LDAP - OpenESB: the Open Source ESB for SOA & Integration

Index Changes

This is version 1. It is not the current version, and thus it cannot be edited.
[Back to current version] [Restore this version]

Testing the Composite Application

This section lists the procedure to test the deployed application.

To Test the Composite Application

1    Expand the Composite Application project. Click Test.
       For example, AddCompApp
2    Right-click to select New Test Case.
3    Enter the Test Case Name.
       For example, AddTest
4    Click Next.
5    Select the WSDL Document.
       a    Select one WSDL Document from the BPEL Module.
           In the current example the WSDL Document is TriggerWSDL.wsdl and the BPEL Module is LDAPBpelModule — Process Files.

Note - Select one WSDL Document.

Select WSDL Document

       b    Click Next.
       c    Select one Operation to text file from the Process Files.
           In the current example the Operation to Text file is TriggerWSDLOperation and the Process File is TriggerWSDLPort (Binding=”TriggerWSDLBinding”).

Note - Select one Operation to Text file.

Select Trigger WSDL

6 Click Finish.
This displays the Source code.

Test Case Source Code

7 Enter the string value.
string = Jane

Enter Value

       The Output console displays Retrieve.xml when you enter a string value in the input.xml window.
8    Right-click the Test Case and click Run.
      For example, AddTest
      A confirmation dialog box prompts to overwrite an existing Output.
9    Click Yes.
      The Output is as shown in the illustration.

Final Composite Output

Source View

Right-click a node and choose Go To —> Source.

The Source view appears with the cursor positioned at the beginning or end of the component's block.

In the Source view, the underlying XML source code appears. You can directly edit the XML.

The top of the Source Editor has a tab for each open document. Each tab shows the name of the document.

Note - If the document has been modified and has not been saved, then an asterisk (*) appears after the name. You can right-click a tab to access various commands.

A toolbar is located at the top of the Source Editor window.
Source code displayed in the Source Editor is syntactically colored.
The Source Editor status line is located beneath the horizontal scroll bar. To toggle between insert mode and overwrite mode, use the Insert key.

Design View: Notification

The Design view displays the results of both real-time and explicit validation in callout windows on the diagram and the error stripe.

In the illustration,

Note - A red cross next to an element on the diagram means that the element has not passed validation and the output contains errors.
A yellow triangle with an exclamation mark means that the element has not passed validation and the output contains warnings.
A red cross in the Design view means there are both errors and warnings.

If you click the cross or the triangle, a callout window lists errors and warnings.

Assign Error

The callout window displays messages related to validation in accordance with the criteria listed above. Messages related to real-time validation are constantly updated.

In the Design view, the error stripe displays the validation results. The error stripe is a strip to the right of the scroll bar that contains red marks if some elements have not passed validation. The error stripe represents the entire diagram, not just the portion that is currently displayed. This stripe helps users to immediately detect any errors in the BPEL process without having to scroll through the entire diagram. Click a red mark to jump to the element that causes problems. If no errors are detected, the small square in the error stripe is green.

Assign1 Error