...
- String Userid – i.e "amarx"
- String password – i.e. "A_marx"
- String schemaVersionNumber – i.e. "2.1"
- String numberOfNumbersRequested operationId - i.e. "101"
- String reportType – numberOfNumbersRequested - i.e. "C" or "" – THIS FIELD'S DATA HAS NO EFFECT10"
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. There are several reportTypes available for use:
- "C" = Crab
- "G" = Groundfish
- "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.getFishTicketNumbers(userid, password, schemaVersionNumber, numberOfNumbersRequested, reportType);
Or
String xml = ws.getFishTicketNumbers("amarx", "A_marx", "2.1", "101", "C10");
If the web service call was successful you might see a string containing something like:
...