Possible header elements are listed in this table.

Possible body elements are listed in this table.

All the necessary files are sent with SOAP message as MIME attachments. The attachments are sent as byte arrays. The following attachments can be sent:

Here you can see an example of the request message. This message will generate a report from the template located at c:/ERES/ReportFiles/report.rpt. It then exports it to DHTML to the default ERES repository and returns a link, which allows accessing the exported report.

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">

      <s:Header>
            <UserName>admin</UserName>
            <Password>admin</Password>
            <URLType>FORREPORT</URLType>
            <ReturnOption>LINK</ReturnOption> </s:Header>
      <s:Body>
            <lookup xmlns:er="LookupService">
                  <TemplatePath>c:/ERES/ReportFiles/report.rpt</TemplatePath>
                  <ExportFormat>DHTML</ExportFormat> </lookup> </s:Body> 

</s:Envelope>
        

If your report/chart is parameterized you may want to enter parameter values. This can be done in a similar way as in the Report/Image URL. The QueryParamName, QueryParamSize and QueryParamValue elements are used to specify parameters. All three elements must be used for each parameter in this exact order: QueryParamName followed by QueryParamSize followed by one or more QueryParamValue. This can be followed by other parameter specification. If some parameter value is specified, the default parameter value is used.

The example below shows how to set parameters for a report with a single value parameter (Category) and a multi-value parameter (Products).

<QueryParamName>Category</QueryParamName>
<QueryParamSize>1</QueryParamSize>
<QueryParamValue>Arm Chairs</QueryParamValue>

<QueryParamName>Products</QueryParamName>
<QueryParamSize>3</QueryParamSize>
<QueryParamValue>Cula Chair</QueryParamValue>
<QueryParamValue>Marduk Chair</QueryParamValue>
<QueryParamValue>Nisaba Chair</QueryParamValue>
        

You can get one of the following responses from the LookupService:

The response message can contain only one attachment- the exported report or chart. This is in case you have used the CONTENT ReturnOption and you have gotten the CONTENT response message. Then you can find the attachment, which is containing the file as byte array.

Only single file is supported as attachment. Therefore, it is not possible to export to multi-page (D)HTML using the CONTENT ReturnOption.

Here is an example of using the SimpleSOAPMessenger class.

public class TestLookupService{

      public static void main(java.lang.String[] args) {
            SimpleSOAPMessenger ssm = new SimpleSOAPMessenger();
            ssm.setURL("http://localhost:8080/ERES/services/LookupService");
            ssm.setUsername("admin");
            ssm.setPassword("admin");
            ssm.setURLType("FORREPORT");
            ssm.setTemplatePath("help/quickstart/templates/QuickStart51.rpt");
            ssm.setExportFormat("DHTML");
            ssm.setReturnOption("LINK");
            try {
                  byte[] byteArray = ssm.SendAndRecieve();
                  String link = new String(byteArray);
                  System.out.println("Generated report is at : "+link);
            }catch (Exception ex) {
                  ex.printStackTrace();
            }
      }

}