Page Comparison

...

1. String Userid – i.e "amarx"
2. String password – i.e. "A_marx"
3. String schemaVersionNumber – i.e. "2.1"
4. String numberOfNumbersRequested - i.e. "10"
5. String reportType – i.e. "C" or "" – THIS FIELD'S DATA HAS NO EFFECT

If we pass in a numberOfNumbersRequested=10, we are asking for 10 new landing_report_id's from the database that have never been used and will be reserved for our use.

There are several reportTypes available for use:

1. "C" = Crab
2. "G" = Groundfish
3. "B" = Salmon

Note: Currently, elandings web service logic does not use the reportType. Any String value passed in will be accepted and discarded. It will have no effect on how the numbers are retrieved or reserved in the database.
In the web service client we might auto generate a data structure by providing the web service URL. In eLandings we use Java – JAX-WS and generated a structure called ReportManager.
ReportManagement ws;
...
...
String xml = ws. getLandingReportNumbers (userid, password, schemaVersionNumber, numberOfNumbersRequested, reportType);
Or
String xml = ws. getLandingReportNumbers getReportNumbers ("amarx", "A_marx", "2.1", "10", "C");
If the web service call was successful you will receive a string containing something like:

...

eLandings would call the webservice method and ask for a new Landing Report number to attach to the new landing report. In so doing, eLandings is telling the database not to give this landing report number to anyone else. This preserves the landing report id's uniqueness.
The web page runs the following web service call:
String xml = ws. getLandingReportNumbers getReportNumbers ("amarx", "A_marx", "2.1", "1", "B");
The returned XML

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<number_info>
    <schema_version>2.1</schema_version>
    <landing_report_id>15404133</landing_report_id>
</number_info>

...