D2D scenario : Developer Environment

This scenario is typically used in development phase when you are building a Silverlight rich client that connects to new business Logic. It is mandatory that the business logic is new to ensure you have enough control to enforce a configuration where the Site Of Origin and the Services Host reside on the same node. If you face a configuration where you need to interface with Business Logic exposed by existing Web Services from a distinct node or requiring protocol adaptation, turn to the B2E scenario.

As listed in Silverlight scenarios for Rich Internet Applications, the following constraints apply to the Developer Environment scenario :

1. No infrastructure security constraints since this is a dev/test env (No HTTPS, no DMZ)
2. No protocol adaptation is necessary as we develop brand new services here (ie, messages format & exchange protocol correspond to the Silverlight client capabilities, they can be directly consumed)
3. Authentication & authorization may need to be handled if required at production/deployment time : this point is covered in the B2E scenario.
4. A cross domain security file is needed if the Site Of Origin does not host the Web Services, as in interoperability scenarios where the Site of Origin and the Web Services rely on two different technologies.

We plan to experiment the following configurations :

• SOAP/ RPC style (operation oriented)
  1. Mixed configuration : IIS for Site of Origin + Tomcat and JAVA-WS for Web Services
     • with a cross-domain policy
     • or by servicing Web services request from IIS through the Tomcat connector for IIS
  2. Full Java configuration : Tomcat for Site of Origin + JAVA-WS for Web Services
  3. Full Windows configuration : IIS for Site or Origin + WCF services (SOAP style) for Web Services
     • with a cross-domain policy
     • or with the IIS built-in integration of WCF services through SVC resources
• XML/ REST style (resource oriented)
  1. Mixed configuration : IIS for Site of Origin + Tomcat and the Restlet framework for Web Services
     • with a cross-domain policy
     • or by servicing Web services request from IIS through the Tomcat connector for IIS
  2. Full Java configuration : Tomcat for Site of Origin + Restlet for Web Services
  3. Full Windows configuration : IIS for Site of Origin + WCF services (REST style) for Web Services