Blackboard Web Services: Lance Neumann, Senior Software Architect, Blackboard Inc
Blackboard Web Services: Lance Neumann, Senior Software Architect, Blackboard Inc
Run in the dotnetclient directory with the base url of your Academic Suite server as a parameter:
sampleGenClient.cmd http://my.server.url
Two parts:
Code generation Code adjusting
Code Generation is merely running wsdl.exe for each of the Web Services placing the files in dotnetclient\BbWsClient\gen Note that you must have set all your Web Services as discoverable prior to generating code or this step will fail.
A simple sed-like program is included in the .zip (bsed.exe) this is _not_ sed, but merely has enough capability to do the replacements required. If you wish to use your own sed then set SED_PATH prior to running sampleGenClient.cmd
Building: .NET
Follow the readme.txt to make sure you have the prerequisites installed (VS 2008 or 2003 and WSE 2.0) Run sampleGenClient in the dotnetclient directory to generate the client stubs Open the wsagent solution file from the qa\dotnet\wsagent directory for your VS version (.net 2003: wsagent.sln, VS 2008: wsagent2008.sln) Build and Run as normal (i.e. F5) This client application is a GUI interface to demonstrate all of the Web Service operations. It is not meant to be pretty merely functional.
Code Generation is merely running wsdlToJava for each of the Web Services placing the files in client\generated Note that you must have set all your Web Services as discoverable prior to generating code or this step will fail.
Building: Java
Follow the readme.txt to make sure you have all the prerequisites installed (ant, jdk, sed, axis2, rampart, eclipse) In the client directory:
Run sampleGenClient to generate the client stubs Copy project.properties to build_personal.properties and edit it to set AXIS2_HOME for your system Run ant
Tool ContextWS.loginTool
Need to register the tool first, via ContextWS.registerTool Uses shared password for the tool set on the properties page for the proxy tool in AS Session only gets the entitlements for the methods requested in the earlier call to registerTool
Ticket ContextWS.loginTicket
Need to register the tool first, via ContextWS.registerTool Uses a ticket representing the currently logged in user, provided to the tool by AS during an outbound POST in response to a proxy tool action Session gets the intersection of the entitlements the user has in AS and those requested during the registerTool call
In all cases, once a session id is obtained, it must be set in the WS-Security headers for all subsequent method calls.
Resources
http://www.edugarage.com/display/BBDN/How+to+Write+Basic+We b+Service+Clients Javadocs downloadable from UI for each Web Service
Questions?