Siebel Web UI Dynamic Developer Kit Guide > Web UI DDK Overview >

About Developer Roles for Using the Web UI DDK

Tasks for generating and deploying the Web UI DDK are divided between Siebel developers and Java developers.

Siebel Developers

Siebel developers typically perform these tasks:

• Analyzing Siebel data models and object models
• Running the DDK Wizard for a given view to generate JavaServer pages and Java EE artifacts
• Verifying Integration Objects and Business Services in Siebel Tools
• Verifying Web service administration data
• Compiling the SRF with repository changes
• Handing off the Java artifacts generated by the Web UI DDK Wizard to Java Web developers

Java Web Developers

Java developers typically perform these tasks:

• Importing Java artifacts into a Java development environment
• Generating Java proxy objects from WSDL
• Deploying sample pages as working examples
• Using the metadata and schema report to understand the Siebel data model
• Writing custom code to invoke Siebel logic and manage data in the Siebel database using proxy objects

Scenario for Using the DDK Wizard

This section gives one example of how you could use the Web UI DDK Wizard. You can use the Web UI DDK Wizard differently, depending on your business model.

A company has a business requirement to enable partners to create and manage Siebel accounts using a custom-built Web application.

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.