Objective
Discontinue the use of SOAsoft 5 & 6 and begin consuming APIs from the new API Manager.
Reason
By switching to the new API Manager, BYU takes advantage of new features (which did not exist in SOASoft), including better monitoring, improved performance, improved mediation, and advanced authentication mechanisms.
SOASoft Retirement Date
April 30, 2017
Training Meetings
-
3 Web Client Trainings (For those who consume APIs)
-
Tuesday, March 21st (12pm-2pm): Migrating the Timekeeper Web UI (NodeJS) (Video Coming)
-
Monday, March 27th (1pm-3pm): Migrating Event Hub Web Service Clients (Python) (Video)
-
Thursday, March 30th (3pm-5pm): Migrating the Traffic Web UI (PHP) (Video)
-
-
3 Web Service Trainings (For those who provide APIs)
-
Thursday, March 16th (9am-11am): Migrating the Timekeeper Web Service (NodeJS) (Video Coming)
-
Wednesday, March 24th (2pm-4pm): Migrating the Traffic Web Service (Java) (Video)
-
Tuesday, March 28th (12pm-2pm): Migrating the AWS Voting Web Service (Java) (Video)
-
Steps to be Taken
1. Replace your SOASoft endpoints with new API Manager endpoints (see lookup tool)
2. Create an app in the API Store (full instructions)
3. Subscribe to API in the API Store (full instructions)
4. Replace API key or Basic Auth authentication methods with OAauth 2.0 method
5.Contact Valinda Rose with the old API key and the new WSO2 consumer key to transfer data permissions from SOAsoft to the API Manager (full instructions)
Note, if you currently publish Events in the BYU EventHub that have callback URLs that go to SoaSoft fronted web services or other web services that use API Key AuthN then you will need to migrate those events to use endpoints in the new API Manager. We recommend you publish both endpoints for a time before turning off the old endpoint.
