Development and Test servers:

CurrentStatus 3.0 API

Official Servers available to the public:

• Production :  http://services.ifd-library.org/api/2.0?wsdl
  • Version 2.0.4 of the API
• Official Test:  http://services.ifd-library.org/test/api/2.0?wsdl
  • Version 2.0.4 of the API, exact same as production, but different content (test content)

3.0 API beta:

•  http://test.services.ifd-library.org/api/3.0/wsdl/soap. wsdl

2.0_5 API beta:

•  http://test.services.ifd-library.org/api/2.0?wsdl

Development and Test servers available to the 3.0 Upgrade team:

• Test 2.0.x/2.0.5 :  http://195.139.163.4:9584/ifd20/services/ifdRPC-2.0?wsdl
  • Version 2.0.5 of the API, test content, new backend, same signature as 2.0.4 (no need to change apps consuming 2.0.4 to use this)
• Test 3.0 soap encoding:  http://test.services.ifd-library.org/api/3.0/wsdl/soap.wsdl
• Test 3.0 literal encoding:  http://test.services.ifd-library.org/api/3.0/wsdl/literal.wsdl
  • Service endpoint need to be specifid to:  http://test.services.ifd-library.org/api/3.0/

Documentation relevant to upgrade

All these documents are attached to this page (see bottom of page).

• EDMWebServices User Guide
  • Describes how EXPRESS is mapped to SOAP, and how the web service layer on EDM is implemented, design decisions, etc. Important for TG to understand all implications of this
• IFD_3.0_API_Description.pdf
  • To be converted to Wiki, according to ticket #62
• Further_Specification_of_Testsuite_IFD_API.pdf
  • Further description of how test suites will be developed for the IFD Library API
• Old query schema might be in revision 3825

Changes from 2.x to 3.x:

• SessionID has moved to front of the method call, instead of last, as it is now with 2.x

Plan to upgrade to 3.x

Tasks

Please not that this task list is no longer maintained. All tasks are now listed as "tickets". Easiest way to see them is to go to the Roadmap.

1. Resolve with TG (FAST) if 2 WSDLs are OK instead of 1 (See #59)
2. Resolve with EPM if we can remove "group" as a parameter in the login call (in such a way so that the login call do not change from 2.x to 3.x) (See #60)
3. Resolve with TG (or some IFD resolution) if we need to support 2.x after release of 3.x (DONE)
4. Verify that method calls on current production, yield same results with same input data on same content for 3.x
   1. Using proposed testing procedures
   2. Resolve with LBJ what this means (DONE)
   3. Resolve who does what and when (ongoing)
5. Convert new API documentation from EPM to Wiki on dev.ifd-library.org (See #62)
   1. Keep old API documentation, add new one
6. Have TG understand the architectural changes from Java based WSDL generation to fully EDM based (See #63)
   1. Read documentation
   2. Resolve if this is acceptable to IFD
   3. Attach documentation of this to dev.ifd-library.org (See #64)