|Bookshelf Home | Contents | Index | PDF|
The company's Siebel developer reviews the high-level requirements and determines that the All Account List View is the best view to expose to partners in the custom-built Web application. The Siebel developer opens the Web UI DDK Wizard and selects the appropriate integration object and Web service to use to expose the view. The Siebel developer completes the wizard, generating a developer kit that includes sample JavaServer pages for the view and all the supporting Java EE artifacts required to deploy the view in a Java EE application. The Siebel developer archives the files and directs the Java developer to the file location.
The Java developer uses the readme.txt file in the DDK output folder to deploy the JavaServer pages. The Java developer imports the Java EE artifacts and libraries into the Java development environment and then uses Apache Ant (Java-based build tool) to generate Java proxy objects from the generated WSDL files.
As a proof-of-concept, the Java developer shows the sample JavaServer pages to the business owners and demonstrates how to use the pages to manage accounts. The Java developer uses the sample JavaServer pages as working examples and the Data Schema report to understand the object hierarchy and object metadata. Using the sample JSP pages as a starting point, the Java developer develops custom code to expose the All Account List view in the Web application.
|Siebel Web UI Dynamic Developer Kit Guide||Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices.|