...
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. findUserLandingReports (Userid, password, schemaVersionNumber, fishTicketNumber, processorCode, federalProcessorCode, registeredBuyerNumber, registeredCrabRecieverNumber, adfgVesselNumber, reportType, portOfLanding, cfecFishery, cfecPermit, gearCode, nmfsPersonId, ifqNumber, reportStatus, fromDate, toDate, tenderVesselNumber, includeItemizedCatchSummaries, tenderBatch, tenderInvoice);
For example:
If we wanted to search for an individual landing report with fish ticket ¿E06 000511¿ "E06 000511" we would pass in the following parameters:
String xml = ws. findUserLandingReports ("amarx", "A_marx", "2.1", "E06 000511", "", "", "", "", "", "", "", "", "", "", "", "", "", null, null, "", "", "", "");
If we wanted to search for all landing reports with a date of landing between 01/10/2010 and 01/20/2010, we would run something similar to:
DatatypeFactory datatypeFactory = DatatypeFactory.newInstance();
SimpleDateFormat slashFmt = new SimpleDateFormat("MM/dd/yyyy");
Date calendarStartDate = slashFmt.parse("01/10/2010")
Calendar startDate = new GregorianCalendar();
startDate.setTimeInMillis(calendarStartDate.getTime());
Date calendarEndDate = slashFmt.parse("01/20/2010")
Calendar endDate = new GregorianCalendar();
endDate.setTimeInMillis(calendarEndDate.getTime());
XMLGregorianCalendar startDateArg = (null == startDate) ? null : datatypeFactory.newXMLGregorianCalendar((GregorianCalendar) startDate);
XMLGregorianCalendar endDateArg = (null == endDate) ? null : datatypeFactory.newXMLGregorianCalendar((GregorianCalendar) endDate);
String xml = ws. findUserLandingReports ("amarx", "A_marx", "2.1", "", "", "", "", "", "", "", "", "", "", "", "", "", "",startDatestartDateArg, endDateendDateArg, "", "", "", "");
Please note that this web page also calls the findUserProductionReports() web service as well. See the documentation in this document to see the structures that are returned from it.
If the web service call was successful the resulting string will contain a landing_report_info structure containing one or more landing_report_summary objects
...
In eLandings this error would be displayed in red.
For the list of potential elandings messages see the elandings codes page and click on Message Codes
Note: the search button calls two web services ¿ : findUserLandingReports() and findUserProductionReports(). You may see errors reported from both webservice method calls displayed in eLandings.