Software AG Products 10.7 | Integrating On-Premises and Cloud Applications | Service Development | Working with Publishable Document Types | About Testing Publishable Document Types | Testing a Publishable Document Type
 
Testing a Publishable Document Type
Keep the following points in mind when testing a publishable document type:
*If your publishable document type expects Object variables that do not have constraints assigned or an Object defined as a byte[ ], you will not be able to enter those values in the Input dialog box. To test these values, you must write a Java service that generates input values for your service and a flow service that publishes the document. Then, create a flow service that first invokes the Java service and then the publishing flow service.
*If you selected a publication action in which you wait for a reply, and Designer receives a reply document, Designer displays the reply document as the value of the receiveDocumentTypeName field in the Results view.
*If Designer does not receive the reply document before the time specified for next Wait for elapses, Designer displays an error message stating that the publish and wait (or deliver and wait) has timed out. The Results view displays null next to the receiveDocumentTypeName field to indicate that the Integration Server did not receive a reply document.
*To test a publishable document type
1. In the Package Navigator view of the Service Development perspective, select the publishable document type that you want to test.
2. Select Run > Run As > Publishable Document.
3. Do one of the following:
*If more than one launch configuration exists, select the one you want to run from the Launch Configurations dialog box, and then click Run.
*If a launch configuration does not exist, Designer uses the default launch configuration. When the Input dialog box appears, enter launch configuration data for the test in the Input dialog box and then click Run.
Note:
The input data is not saved after the default launch configuration runs. If you want to save the input data in a launch configuration, see Creating a Launch Configuration for a Publishable Document Type for instructions about creating and saving a launch configuration.
Notes:
*Designer displays the instance document and publishing information in the Results view.
*If you selected a publication action in which you wait for a reply, and Designer receives a reply document, Designer displays the reply document as the value of the receiveDocumentTypeName field in the Results view.
*If Designer does not receive the reply document before the time specified next Wait for elapses, Designer displays an error messages stating that the publish and wait (or deliver and wait) has timed out. The Results view displays null next to the receiveDocumentTypeName field to indicate that the Integration Server did not receive a reply document.