Page Comparison

...

The getFishTicketNumbers() takes four five arguments:

1. String Userid – i.e "amarx"
2. String password – i.e. "A_marx"
3. String schemaVersionNumber – i.e. "2.1"
4. String operationId - i.e. "1"
5. String numberOfNumbersRequested - i.e. "10" or null

Each user is associated with one or more operation ID's. You can find a legal operation ID for a user by calling the web service getUserInfo() and examining the list of returned operations associated with the user profile.

If we pass in a numberOfNumbersRequested=10, we are asking for 10 new fish_ticket_numbers from the database that have never been used and will be reserved for our use. If null is passed in for numberOfNumbersRequested, the system will return all previously reserved tickets without adding new numbers to the list.

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.getFishTicketNumbers(userid, password, schemaVersionNumber, numberOfNumbersRequested, reportType);
Or
String xml = ws.getFishTicketNumbers("amarx", "A_marx", "2.1", "1", "10");
If the web service call was successful you might see a string containing something like:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<number_info>
    <schema_version>2.1</schema_version>
    <fish_ticket_number>E11 152461</fish_ticket_number>
    <fish_ticket_number>E11 152462</fish_ticket_number>
    <fish_ticket_number>E11 152463</fish_ticket_number>
    <fish_ticket_number>E11 152464</fish_ticket_number>
    <fish_ticket_number>E11 152465</fish_ticket_number>
    <fish_ticket_number>E11 152466</fish_ticket_number>
    <fish_ticket_number>E11 152467</fish_ticket_number>
    <fish_ticket_number>E11 152468</fish_ticket_number>
    <fish_ticket_number>E11 152469</fish_ticket_number>
    <fish_ticket_number>E11 152470</fish_ticket_number>
</number_info>
{CODE}