Have access to or have installed Oracle JDeveloper Studio Edition (10.1.3.3).

This release includes all the functionality you need to build WebCenter applications. You can download JDeveloper Studio Edition from the Oracle Technology Network at http://www.oracle.com/technology/software/products/jdev/htdocs/soft10133.html.

Have access to or have installed Oracle's Siebel eBusiness Applications. In this OBE, we use Siebel eBusiness Applications 7.8 with Call Center.

Have downloaded sweOBE.zip and unzipped the contents into the c:\mywork directory, which you need to create on your local machine, as shown below.

Note: If you use a different top-level directory, you will need to make a simple modification to the application code.

Have access to Windows Internet Explorer (IE) 7.0 or higher. It is essential that your browser is compatible with Siebel Call Center.

1.

Open Internet Explorer and enter the URL for Siebel Call Center.

The format of the URL is http:// < hostname>/callcenter_<language>/start.swe. For example, http://myhost.oracle.com/callcenter_enu/start.swe.

Be sure you are using a browser that is certified for use with Siebel, such as IE 7.

2.

Enter a valid user ID and password. We used SADMIN for both the user ID and password. Click the arrow to log in.

On the home page, click the Accounts tab.

To find the view that we want to use for the application, follow these steps:

Look at the XML for this view. To access the XML, append the following to the URL in your browser: &SWECmd=GotoView&SWEView=Account+Detail+Orders+View&SWESetMarkup=XML&SWEDataOnly=TRUE&SWERowId0=6SIA-2ZIAL&SWEApplet0=SIS+Account+Entry+Applet

Notice that we have set the SWESetMarkup=XML. We are also setting SWEDataOnly=True to indicate that SWE should return data only and no user interface information such as non-data controls (such as anchors and navigation controls).

Note: In the screenshot, we've selectively collapsed some nodes for readability.

Scroll down to the <RS_DATA> element of the second <APPLET> element to look at the fields that are exposed in the data. Notice the field names (Priority Status, Order Number, and so on) that will be used from the returned XML.

Also notice that some fields (Order Type, for example) have a set of pick list values. These pick lists make the XML more challenging to parse.

Now return to the Siebel Call Center (you can click the Back button in your browser). Select Help > About View from the main menu.

The About View window shows the details of this screen. Notice the name of the view (Account Detail - Orders View) and the applet names.

The applet designated [1] (in this example, SIS Account Entry Applet) always controls the master section of the view. You are going to use the view name and the applet name in the next section.

Click OK to close the About View window.

In the navigator, expand Application Sources and then expand model.swetoadf.

Note: The application uses two projects: The Model project is used to construct the data control on which the Order Detail table is based, whereas the ViewController project defines the user interface. It is always good practice to separate data controls from the user interface. The Portlets project is unused.

Double-click sweData.java to open it in the Visual Editor and see what the code does.

The method public static List<viewRecord> getView(String pZoneName,String pRecordID)
will be called to collect rows from the given record. pZoneName is hard-coded to "orders" to select the
orders.properties file, where the record's attributes are defined.

From the SWEgeneral.properties file, we get the Siebel Call Center's access parameters: host name and account name (which is also used for the password in our example).

From the orders.properties file, we get the record's attributes. These include the names of the module and applet, the default record, the field names of interest, and the field type (pick list or scalar value).

The request URL object is constructed from these parameters. If no record is specified in the method call, the default record is used.

The URL first executes a login ( SWECmd=ExecuteLogin ...) and then requests the data from the appropriate view, applet, and record in XML forma ( SWECmd=GotoView ... ).

Next, a DOM (Document Object Model) parser is created; it parses the newly constructed URL (that is, the reply coming from Siebel when the constructed URL is requested).

Because the code uses Oracle's DOM Parser, the resulting document can be typecast to oracle.xml.parser.v2.XMLDocument. The advantage of this document class is that it implements the non-standard method selectNodes(<XPATH String>), which will return a list of all the records matching the XPATH expression.

The XPATH expression that is constructed selects all the rows from the RSS_DATA element from the specified APPLET tag (in this case, APPLET[2]): APPLICATION/SCREEN/VIEW/APPLET[2]/LIST/RS_DATA/ROW. The matching nodes ("ROWs") are fetched.

Than all of the rows are processed by getting the values of the fields that were specified in the orders.properties file (col1 .. col5).

Finally, all the values are packed into a new viewRecord object and added to the resulting list.

The valueOfField method fetches the requested field's value from the current row.

Some fields get their value from a pick list. Pick lists are given only on the first row.

The method constructs an XPATH expression, starting from the current ROW node. If the first row is being processed and the field is a pick list, then the VALUE attribute of the PICK_LIST of the named field is used:

. ./FIELD[@NAME='" + fieldName + "']/PICK_LIST / @VALUE)

If the field is not a pick list, then the value is simply the value of the field:

./FIELD[@NAME='" + fieldName + "']

The method returns the value of the node selected by the XPATH expression.

Double-click viewRecord.java in the navigator to open the file.

This is a simple Java class, which holds a record of five strings as the values of five fields.

Expand model.siebel and double-click orders.java to open it in the Visual Editor.

orders.java calls the getView method of the sweData class.

When we were building the application, we used this Java class to create a data control by right-clicking the file and selecting Create Data Control from the context menu, as shown below.

The resulting XML files describe the data control:

	DataControls.dcx describes the generated data control.
	orders.xml describes the data control's method and parameter.
	viewrecord.xml describes the method's return type.

Now that we've looked at the application model, click ViewPage1.jspx to revisit the user interface. Notice ordersDataControl in the Data Control Palette.

We used this data control twice when building ViewPage1.jspx.

	The findAllOrders(String) node was dropped on to the page as a parameter form, creating the input field and the button.
	The findAllOrders(String) > viewRecord node was dropped on to the page as an ADF read-only table.

The completed ViewPage1.jspx is shown below.