Public Facing Web Services
eLandings public  web services are isolated from the rest of the eLandings web services to keep their definitions as stable as possible while active development is happening on the eLandings system. We provide test, training and production versions.  Code is actively developed in TEST. Typically, once a month, code is moved into TRAINING for acceptance testing for ~3 days. After the acceptance testing, code is release to PRODUCTION. TRAINING is left active to allow users to practice using eLandings in a safe environment.
This means that the TEST environment is undergoing constant change. It may be unstable and the TEST web services may not always be available due to server cycling during builds, bugs, or other development activity. The TRAINING web services will be much more stable. Third party developers can test against either system. The advantage of using the TEST system is that developers can work with the most current version of the schema, the one which will be moved to production in the next release. The advantage of using the TRAINING system is that it will be more stable, and when the testing is complete the third party system can be used in production without waiting for an eLandings release.
Test:
http://elandingstest.alaska.gov/elandings/ReportManagementService?wsdl
Training:
http://elandingst.alaska.gov/elandings/ReportManagementService?wsdl
Production:
https://elandings.alaska.gov/elandings/ReportManagementService?wsdl
While the WSDL definitions on Test, Training, and Production may be different at any given point in time, the differences are due to ongoing development and release schedules. Therefore, the version on Production will always match what was previously on Test, the Production definition is never changed independently. As a result, third party developers who develop their software with the Test definition can move to Training and Production with the eLandings release without having to rebuild their software with the definitions on Training and Production. The version of the Test definition used must be the last one edited on test before the release, so third party developers should download it frequently during their development and release cycle.
Quick Reference Guide
The quick reference guide is available for download at: eLandings_Public_Web_Services_Quick_Reference_Guide.docx
Available Web Service Methods
- getUserInfo()
- findUserLandingReports()
- findUserLandingReports_001()
- findUserProductionReports()
- findUserProductionReports_001()
- getLandingReport()
- getProductionReport()
- getReportNumbers()
- getFishTicketNumbers()
- saveLandingReport()
- saveProductionReport()
- submitInitialLandingReport()
- submitFinalLandingReport()
- submitProductionReport()
- getFishTicketNumbers001()
- getFishTicketNumbers002()