4 Developing Services

4.3.5.1 Entering the Basic Information for the Application

Enter a unique name of the application (no two applications residing in the same folder can have the same name) and optionally, enter the URL pointing to the remote application which generates OracleAS Wireless XML or XHTML. You do not have to define the URL if this application is a message template used by a notification application.

You can complete the application at this point and exit the wizard by clicking Finish, or you can click Next to further define the application. Clicking Cancel at any point in an OracleAS Wireless wizard clears any of the values that you have entered.

4.3.5.2 Entering the Notification-Related Information

Complete the second step of the wizard if this application is based on a notification (an alert).

Select the Notification Enabled option if this application can be invoked by the notification engine to generate content for the notification message.

After you select the Notification Enabled option:

• Select a notification from the Notification drop-down list (Figure 4-3). If none of the listed notifications suit your needs, then click Create to construct a notification application using the notification creation wizard. For more information on notifications, see Section 4.4, "Managing Notifications".

• Select Use the default messaging URL for the notifications with message template to use the default messaging generation mechanism. OracleAS Wireless provides a default application JSP to generate the notification message based on the notification template. If you select this option along with a notification that includes a message template, then the default JSP handles the message generation. You do not need to provide the URL to the application. For more information, see Section 4.4.1.3, "Step 3: Creating the Message Template".

• Select Generate Non-Personalized Shared Content so that the application is invoked only once for each incoming event. In this case, the user information passed to the application is the system user, and generated content is shared by the users who are qualified for this event The application can not perform any special processing for each user and can not generate personalized message for each user. However, selecting this option improves performance, since the application is invoked only once for multiple notifications. For more information on notifications, see Chapter 11, "Notification Engine".

• Click Next or Finish.

Figure 4-3 Entering the Notification Information for an Application

Description of "Figure 4-3 Entering the Notification Information for an Application"

4.3.5.3 Entering the Input Parameters for the Application

The Input Parameters screen (Figure 4-4) displays parameters which are passed to the application (JSP, XHTML, MXML). The parameters for this application can either be defined in this screen, or by the Content Manager when publishing this application as an application link. For more information on publishing content, refer to the OracleAS Wireless Administrator's Guide.

Figure 4-4 The Input Parameters Screen

Description of "Figure 4-4 The Input Parameters Screen"

Creating Parameters that Require Input from the End Users

If you create a parameter that requires a value by leaving the Empty OK check box clear, and then do not enter a value for this parameter, then OracleAS Wireless prompts the user for this value at runtime.

Creating Parameters that Can be Modified by the Content Manager

If you select the Modifiable option, then the Content Manager can change this parameter when creating an application link from this application. If you do not select this option, then the Content Manager cannot change this parameter.

4.3.5.3.1 Adding a New Input Parameter to the Application

To add a new parameter to the application, you first click Add Another Row. You then define the parameters listed in Table 4-4 and then click Next or Finish.

Table 4-4 Adding an Input Parameter

Parameter	Description
Name	The name for the input parameter.
Caption	The display label describing the input parameter, which prompts an action or input from the user.
Type	Select an input parameter type, which can be SingleLine, MultiLine, Enum, Password.
Comment	A description for the input parameter.
Modifiable	Select this option to enable the Content Manager to change the parameter.
Empty OK	Select this option if the input parameter does not require a value.
Value	Enter, if needed, a default value for the parameter. If you do not enter a default value, then Wireless prompts the user for a value (That is, if the parameter is not also flagged as Empty-OK.)
Mapped Notification Parameter	Select a parameter from the drop-down list. These parameters are specific to the master notification you selected in the Notification-Related Information screen.

Figure 4-5 depicts the Input Parameters screen, where you enter the values for the new input parameter.

Figure 4-5 Adding an Input Parameter

Description of "Figure 4-5 Adding an Input Parameter"

4.3.5.4 Entering the Async Information

If you select the Async Enabled option, then this application, when published, can be accessed through messaging on asynchronous devices. Users invoke the application by sending a request message to the OracleAS Wireless Server. The Async Listener then retrieves the message, routes it to the appropriate Async application and then replies, sending the user a message with the results of the executed request the user as a message. A complicated Async application can require several round trips for the message. OracleAS Wireless preserves the session for messages sent from the same device.

You set the Async information by selecting the Async Enabled check box and then by defining the values described in Table 4-5. Figure 4-6 depicts the Async Info. screen, where you defined the Async information.

Figure 4-6 The Async Information Screen

Description of "Figure 4-6 The Async Information Screen"

4.3.5.5 Setting the Built-In Parameters

The built-in parameters are the predefined HTTP adapter parameters. Because these parameters default to the correct values, you do not have to configure them. Figure 4-7 depicts the wizard's Built-In Parameters screen.

If, however, you need to overwrite these default values:

• Enter the URI to the CatSpeech Server, where the grammars are defined.

• Enter the base URI to the Audio Library, where the audio library classes are defined.

• Enter the full classname for Adapter Invocation Listener, which can be invoked at the runtime to examine aspects of the runtime status, such as the HTTP request parameters, before the application is executed.

• Select true for Do XML Validate, if you want the HTTP adapter to validate the XML generated by the application. Validation can slow down the runtime performance.

• Select true for Send HTTP headers if you would like the HTTP adapter send information through HTTP headers to the application.

• Select true for Rewrite Relative URLs if you want the HTTP adapter to rewrite the URL occurrences in the application JSP, XHTML or MXML files. The URLs are rewritten to refer to the multi-channel server URL rather than to the application server itself.

• Select the HTTP method, (POST or GET). This is the method used by the HTTP adapter to make the HTTP connection to the application pages.

• Set the input encoding for the application server. This encoding is used when HTTP adapter makes the HTTP connection with the application server. Use IANA character set names.

• Click Next or Finish.

Figure 4-7 The Built-In Parameters Screen

Description of "Figure 4-7 The Built-In Parameters Screen"

4.3.5.6 Setting the Caching Information

The Cacheable option enables you to create a cacheable application. For these applications, the HTTP adapter only retrieves the content from the application for first time that the application is invoked. For subsequent invocations, the HTTP adapter retrieves the content from Web Cache, not from the application. As a result, cacheable applications reduce the application invocation time.

Specify the invalidation frequency (refresh frequency) for application content that is time-sensitive and becomes obsolete after a certain period of time. For example, if you specify the invalidation frequency for the Monday of each week at 6:00 am, then the cached content is invalidated at the time every week. The fresh content is stored in Web Cache the next time that the HTTP adapter retrieves the content from the application. If you do not wish to store the application content in Web Cache, then do not select the Cacheable option and click Next.

To create an application of which the content can be stored in Web Cache, select the Cacheable check box (depicted in Figure 4-8) and then enter the frequency of the caching as a number value, of the unit selected from the Unit drop-down list.

Using the Unit drop-down list, select from among the following time units:

• Second

• Minute

• Hour

• Day

• Week

• Month

Using the drop-down lists, select the day and time (if applicable) for the invalidation frequency.

Click Next or Finish.

Figure 4-8 Setting the Caching Information

Description of "Figure 4-8 Setting the Caching Information"

4.3.5.7 Setting Additional Information

The final screen of the wizard (Figure 4-9) enables you to set the display module configuration attributes for the application. Table 4-6 describes the additional parameters. After you have defined the values, select Finish to complete the master application.

Figure 4-9 The Additional Info. Page of the Application Creation Wizard

Description of "Figure 4-9 The Additional Info. Page of the Application Creation Wizard"

4.3.6.1 Entering the Basic Information for the MIDlet

In this first step of the wizard (depicted in Figure 4-10), you define two required parameters: the a name for the J2ME application, and the URL to the application which generates the J2ME application download page. By default, the OracleAS Wireless server provides a default J2ME download page.

Click Next.

Figure 4-10 Entering the Basic Information for a J2ME MIDlet

Description of "Figure 4-10 Entering the Basic Information for a J2ME MIDlet"

4.3.6.2 Specifying the Deliverable Content

For a OracleAS Wireless J2ME MIDlet application, the delivery content is the J2ME MIDlet binary, the core of the application. The delivery content includes a JAD (Java Archive Descriptor) and a JAR (Java Archive file). Each version of the content is specific to different device requirements.

Entering the Version of the Content

In Step 2 (depicted in Figure 4-11), you enter the version of the content. After you complete this application, you can create another version of the content for another device. The application's name and the version uniquely identify a J2ME MIDlet

You can also optionally enter a display name and description for this version of the contents.

Importing the JAD and JAR Files

The Import buttons enable you to browse for and select a JAD and JAR file for this application. To import these files, click the Import button. The Import File window appears. Click the Browse button, select the file and then click Import.

You can complete the application at this point by clicking Finish. Clicking Next takes invokes the Device Requirement screen (Figure 4-12).

Figure 4-11 Specifying the Deliverable Contents

Description of "Figure 4-11 Specifying the Deliverable Contents"

4.3.6.3 Setting the Device Requirements

The device requirement criteria are evaluated when the J2ME is downloaded to a device at runtime. Each version of the deliverable content has a different device requirement.When a device requests the download, the J2ME Provisioning Server selects the version number with the requirements that match the profile of the device requesting the application.

The Devices Excluded section enables you to prevent the download of the MIDlet to a selected device. To exclude devices, use the right arrow buttons (> and >>) to move devices from the Available Devices pane to the Devices Excluded pane. The devices listed in Devices Excluded display an error message if users try to download this MIDlet to these devices. Use the left arrow keys (< and <<) to move devices from the Devices Excluded pane to the Available Devices pane. Similarly, use the arrow keys in the Supported Physical Devices section to select the devices or devices that support downloading this version of content.

Specify heap size requirement for JVM (Java Virtual Machine) running this J2ME application.

Click Next or Finish.

Figure 4-12 Selecting Devices for the Deliverable Contents

Description of "Figure 4-12 Selecting Devices for the Deliverable Contents"

4.3.6.4 Setting Additional Information

Defining the parameters of the Additional Information screen (Figure 4-13) enables you to set the display information for the MIDlet application. Click Finish to complete the J2ME MIDlet application. Table 4-7 describes these parameters.

Figure 4-13 Entering Additional Information for the MIDlet Application

Description of "Figure 4-13 Entering Additional Information for the MIDlet Application"

For more information on creating J2ME MIDlet applications, see Chapter 12, "J2ME Development and Provisioning"

4.3.7.1 Step 1: Entering the Basic Information for the Application

From the Browse Folder Screen, click Create Application. The Basic Information screen of the Application Creation Wizard appears (Figure 4-14). You use this screen to define the configuration parameters for the application, which are described in Table 4-8.

Figure 4-14 The Basic Info. Screen of the Application Creation Wizard

Description of "Figure 4-14 The Basic Info. Screen of the Application Creation Wizard"

4.3.7.2 Step 2: Entering Caching Information

Select the Cacheable check box (depicted in Figure 4-15) for an application with changing content. When selected, this option saves the adapter invocation and transformation. If you create a cacheable application, then you must also specify the frequency at which the OracleAS Wireless server notifies the cache that a Web page has changed by issuing an invalidation report. To define the invalidation frequency, enter an integer value in the Cardinal field and use the screen's drop-down lists to further define the time interval. If you do not wish to create applications that can be cached, then leave the Cacheable check box clear, and click Next.

Click Next. The Initialization (Init) Parameters screen appears.

Figure 4-15 The Caching Information Screen of the Application Creation Wizard

Description of "Figure 4-15 The Caching Information Screen of the Application Creation Wizard"

4.3.7.3 Step 3: Entering the Initialization Parameters of the Application

The Init Parameters screen contains the initialization (init) parameters for the adapter that you selected in Step 2. Not all adapters have init parameters. Enter the values for the init parameters and then click Next. If the selected adapter does not contain init adapters, click Next.

If you want to plug in a listener for such purposes as debugging, specify the listener class in the HttpAdapterInvokerListener field. These listener methods are called at the following times:

• When the HTTP adapter invocation starts.

• Before the connection to a remote JSP.

• After the connection to the remote JSP.

• At the end of the HttpAdapter invocation.

• When errors occur.

  
  

  Note: You must specify the classpath in the OC4J config/application XML file or you must copy the JAR file to wireless/lib.

  
  

4.3.7.4 Step 4: Selecting the Input Parameters for the Application

The Input Parameters screen (Figure 4-16) displays the input parameters for the adapter that you selected in Step 1. The Application Creation Wizard queries the adapter definition to determine the parameters that appear in this screen. Table 4-9 describes the input parameters for applications using the HTTP Adapter and the OC4J Adapter.

The Input Parameters screen enables you to select an input parameter as well as add and delete input parameters to the adapter implementation for this application.

Selecting an Input Parameter

To select an input parameter for the application, click the Select radio button next to the input parameter you want to use and then click Next.

Adding a New Input Parameter to the Adapter

To add a new parameter to the adapter you selected in Step 1, click Add Another Row. Enter the values for the parameters described in Table 4-9, "Input Parameters for the HTTP Adapter and the OC4J Adapter" and then click Next.

See OracleAS Wireless Administrator's Guide for information on the parameters for the SQL Adapter and Web Integration Adapter.

Deleting an Input Parameter

To delete an input parameter, select the parameter you want to remove from the adapter implementation of this application and then click Delete. Click Next.

Figure 4-16 The Input Parameters Screen of the Application Creation Wizard

Description of "Figure 4-16 The Input Parameters Screen of the Application Creation Wizard"

Setting the Input Parameters for the HTTP Adapter

The HTTP adapter retrieves remote content and delivers it as mobile XML.Table 4-10 describes the input parameters for the HTTP adapter.

4.3.7.5 Step 5: Selecting the Output Parameters for the Application

The Output Parameters screen enables you to select the output parameters for the adapter that you selected in Step 1, or to add output parameters to the application. The Application Creation Wizard queries the adapter definition to determine the parameters that appear in this screen.

Table 4-11 describes the output parameters for adapters.

To select an output parameter, use the radio buttons to select the appropriate output parameter and then click Apply. To delete an output parameter, select the output parameter and click the Delete button.

Adding a New Output Parameter to the Adapter

After you have finished adding or deleting the output parameters for the adapter, click Next. The Confirmation screen appears if OracleAS Wireless has not found a PASection in the application you have created. Review the values listed on the Confirmation screen. If they are correct, click the Finish button to complete the master application.

If the master application contains a PASection, the Create Result Transformer screen appears.

4.3.7.6 Step 6: Creating an Async Agent Service—Optional

By assigning Async Agent to an application, you create an application that can be accessed by protocols other than HTTP.

To set the values for an Async Agent application, you first select the Async Agent check box. In the Async Command Line Syntax field, enter the text that is returned when a user issues an application help command to the Async Server. In the Delimiter field, enter the delimiter parameters for the Async Agent service.

Complete the Async Application Argument List section as follows:

1. Click Add Another Row.

2. In the Name field, enter a name for the argument.

3. Enter a number to represent the sequence in which the argument appears on the command line.

4. Enter a default value for the argument. Leaving this field blank creates an application that requests a value from the user.

5. Click Next.

4.3.7.7 Step 7: Selecting the Result Transformer—Optional

After you have set the output parameters for the adapter, OracleAS Wireless checks if the input parameters include PASection, the value used by the WIDL adapter to identify the service that is the entry point in the chained service sequence. If the Application Creation Wizard finds a PASection input adapter, it invokes the Result Transformer screen.

The transformer screen enables you to select a transformer for the adapter or add a new one by importing the XSLT style sheet from your local file system.

To select a transformer for the adapter you selected in Step 1, use the radio buttons and then click Apply. To delete a transformer from the adapter, select the transformer using the Select radio button and click Delete.

Importing an XSLT Style Sheet

1. Click the tab that represents the PASection that you want to edit. Each panel contains a text editor for entering the XSLT style sheet. You can also import an XSLT style sheet by clicking the import button.

2. Click Next after you have completed editing the XSLT style sheet. The Device Transformer Screen appears. Leave this screen blank if you do not wish to create a result transformer and click Next until you reach the Confirmation screen.

3. If the values appear correct, click Finish to complete the creation of the application.

Adding a New Result Transformer

To add a new result transformer:

1. Enter a name for the transformer in the Name field.

2. Click the Import button to retrieve the XSLT stye sheet from your local file system. The style sheet then appears in the Content window.

3. Make any needed changes to the style sheet.

4. Click Add.

5. Click Finish to complete the creation of the master service.

You have created an application. This master service is not visible to users until the Content Manager publishes an application based upon it to user groups.

4.4.1.1 Step 1: Entering the Basic Configuration Parameters for the Notification

You define the following configuration parameters for the notification in the Basic Info. screen, the first screen in the notification creation wizard. Table 4-13 describes the parameters of the Basic Info. screen.

Figure 4-20 The Basic Information Screen of the Master Notification Creation Wizard

Description of "Figure 4-20 The Basic Information Screen of the Master Notification Creation Wizard"

Click Next. The Trigger Conditions screen appears (Figure 4-21).

4.4.1.2 Step 2: Setting the Trigger Conditions for the Notification

The Trigger Condition screen enables you to set the conditions that invoke a notification on end users' devices. For example, if you create a notification that alerts users of a stock price, you set the conditions that allow an end user to request a notification when the stock has risen above, or fallen below, a certain price.

Table 4-14 describes the parameters of the Trigger Conditions screen.

Setting the Relationship Between Trigger Conditions

Select an AND relationship (both conditions must be met) or an OR relationship (any of the conditions must be met).

Selecting a Trigger Condition

To select a trigger condition:

1. From the list of trigger conditions, select the trigger condition.

2. Edit the Condition Type, Trigger Parameter, or Default Value fields as needed.

3. Click Apply.

Adding a New Trigger Condition

To add a new Trigger Condition (Figure 4-21):

1. Enter the name for the trigger condition in the Condition field.

2. Enter text used for prompting input from end users in the Caption field.

3. Select a trigger parameter from the drop-down list in the Trigger Parameter field.

4. Select a Condition Type from the drop-down list in the Condition Type field. Condition types depend on the data type of the trigger parameter.

If the data type is a number, then the conditions include:

• Less Than

• Greater Than

• Equal

• Less Than and Equal

• Greater Than and Equal

• Less Than Absolute Value

• Greater Than Absolute Value

• Equal Absolute Value

• Less Than and Equal Absolute Value

• Greater Than and Equal Absolute Value

• Value Change (The condition value for this type can only be 0 or 1, where 0 means no trigger and 1 means trigger when value changes. The default value is 0.)

If the data type is text, then the condition types include:

• Exact Match

• Not Match

• Contain

• Not Contain

• Begin With

• End With

• Value Change (The condition value for this type can only be 0 or 1, where 0 means no trigger and 1 means trigger when value changes. The default value is 0.)

1. Enter a default value for the trigger condition in the Default Value field.

2. Click Add.

3. Click Next. The Message Template screen appears.

Figure 4-21 Setting the Trigger Conditions

Description of "Figure 4-21 Setting the Trigger Conditions"

4.4.1.3 Step 3: Creating the Message Template

The Message Template screen (Figure 4-22) enables you to create a message template by entering fully-qualified mobile XML (or XHTML) with variables. The following example includes the values sym, price and change.

<SimpleResult>
   <SimpleContainer>
      <SimpleText>
      <SimpleTitle>OracleAS Wireless</SimpleTitle>
      <SimpleTextItem>Notification with price: $price; and change: $change: for stock: &sym;</SimpleTextItem>
      </SimpleText>
    </SimpleContainer>
</SimpleResult> 

Figure 4-22 The Message Template Screen

Description of "Figure 4-22 The Message Template Screen"

4.5.1.1 Step 1: Entering the Basic Information for the Data Feeder

The Basic Info screen of the Data Feeder Creation Wizard (Figure 4-25) enables you enter the basic properties for the data feeder.

Figure 4-25 The Basic Info. Screen of the Data Feeder Creation Wizard

Description of "Figure 4-25 The Basic Info. Screen of the Data Feeder Creation Wizard"

Table 4-16 describes the parameters of the The Basic Info. screen of the Data Feeder Creation Wizard.

Click Next. The Init Parameters screen appears, displaying init parameters for the protocol type you selected.

4.5.1.2 Step 2: Entering the Initialization Parameters for the Data Feeder

The Initialization (Init) Parameters screen displays the initialization parameters specific to the protocol and format type you selected in Section 4.5.1.1. Table 4-17 describes these init parameters.

4.5.1.3 Entering the Init Parameters for the HTTP Protocol

To enter the init parameters for a data feeder using the HTTP protocol and the XML format type:

1. Enter the HTTP URI of the content source.

2. Enter a user name.

3. Enter a password.

4. Select either the GET or POST HTTP methods.

5. If the feed ingests XML, then you must import an XSL style sheet that converts the XML to standard feed XML format.

6. Click Next. The Input Parameters screen appears.

To enter init parameters for a data feeder using the HTTP Protocol and the delimited format:

1. Enter the HTTP URI of the content source.

2. Enter a user name.

3. Enter a password.

4. Enter the delimiter for the format type. For example, enter a comma (,).

5. Enter a quote character for the format type you selected. For example, enter quotation marks (").

6. Click Next. The Input Parameters screen appears.

To enter the init parameters for a data feeder using the HTTP protocol and the fixed column format:

1. Enter the HTTP URI of the content source.

2. Enter a user name.

3. Enter a password.

4. Select either the GET or POST HTTP methods.

5. Click Next. The Input Parameters screen appears.

4.5.1.4 Entering the Init Parameters for the File Protocol

To enter the init parameters for a data feeder using the file protocol and the XML format:

1. Enter the file path. For example, enter c:\temp\file.txt.

2. If the feed ingests XML, then you must import an XSL style sheet that converts the XML to standard XML.

3. Click Next. The Input Parameters screen appears.

To enter the init parameters for a data feeder using the file protocol with the delimited format:

1. Enter the file path.

2. Enter the delimiter for the format type. For example, enter a comma (,).

3. Enter a quote character for the format type you selected. For example, enter quotation marks (").

4. Click Next. The Input Parameters screen appears.

To enter the init parameters for a data feeder using the file protocol and the fixed column format:

1. Enter the file path.

2. Click Next. The Input Parameters screen appears.

4.5.1.5 Entering the Init Parameters for the FTP Protocol

To enter the init parameters for a data feeder using the FTP protocol and the XML format:

1. Enter the FTP URI.

2. Enter the user name.

3. Enter the password.

4. Select either the Text or Binary FTP mode.

5. If the feed ingests XML, then you must import an XSL style sheet that converts the XML to standard XML.

6. Click Next. The Input Parameters screen appears.

To enter the init parameters for a data feeder using the FTP protocol and the delimited format:

1. Enter the FTP URI.

2. Enter the user name.

3. Enter the password.

4. Select either the Text or Binary mode.

5. Enter the delimiter for the format type. For example, enter a comma (,).

6. Enter a quote character for the format type you selected. For example, enter quotation marks (").

7. Click Next. The Input Parameters screen appears.

To enter init parameters for a data feeder using the FTP protocol and the fixed column format:

1. Enter the FTP URI.

2. Enter the user name.

3. Enter the password.

4. Select either the Text or Binary FTP mode.

5. Click Next. The Input Parameters screen appears.

4.5.1.6 Entering the Init Parameters for the SQL Protocol

To enter the init parameters for a data feeder using the SQL protocol and the XML format:

1. Enter the connect string.

2. Enter a SQL query.

3. Click Next. The Input Parameters screen appears.

To enter the init parameters for a data feeder using the SQL protocol and the delimited format:

1. Enter the connect string.

2. Enter a query.

3. Enter the delimiter for the format type. For example, enter a comma (,).

4. Enter a quote character for the format type you selected. For example, enter quotation marks (").

5. Click Next. The Input Parameters screen appears.

To enter the init parameters for a data feeder using the SQL protocol and the fixed column format:

1. Enter the connect string.

2. Enter a query.

3. Click Next. The Input Parameters screen appears.

4.5.1.7 Entering the Init Parameters for the Application Protocol

To enter the init parameters for a data feeder using the application protocol and the XML format:

1. Enter the command line.

2. If the feed ingests XML, then you must import an XSL style sheet that converts the XML to standard XML.

3. Click Next. The Input Parameters screen appears.

To enter the init parameters for a data feeder using the application protocol and the delimited format:

1. Enter the command line.

2. Enter the delimiter for the format type. For example, enter a comma (,).

3. Enter a quote character for the format type you selected. For example, enter quotation marks (").

4. Click Next. The Input Parameters screen appears.

To enter init parameters for a data feeder using the application protocol with the fixed column format:

1. Enter the command line.

2. Click Next. The Input Parameters screen appears.

4.5.1.8 Step 3: Entering the Input Parameters for the Data Feeder

The Input Parameters enables you to enter the input parameters for the data feeder. The input parameters screen displays the input parameters specific to the format type you selected in Section 4.5.1.1. Table 4-18 describes the input parameters of the data feeder.

To enter the input parameters:

1. Click Add Another Row. A row appears.

2. Complete the row as follows:

   1. Enter the internal name.

   2. Enter the data type.

   3. Enter the external name.

   4. Enter the column number. This parameter is specific to the delimited format.

   5. Enter the starting position. This parameter is specific to the fixed-column format.

   6. Enter the ending position. This parameter is specific to the fixed-column format.

   7. Enter a caption.

   8. Enter a default value.

3. Click Next. The Output Parameters screen appears.

4.5.1.9 Step 4: Entering the Output Parameters for the Data Feeder

The Output Parameters screen enables you to enter the output parameters for the data feeder. The output parameters screen displays parameters specific to the format type you selected in Section 4.5.1.1. The output parameters (described in Table 4-19) are the retrieved data from the content provider; you set alerts on the output parameters of a data feeder.

To enter the input parameters:

1. Click Add Another Row. A row appears.

2. Complete the row as follows:

   1. Enter the internal name.

   2. Select the data type.

   3. Enter the external name.

   4. Enter the column number. This parameter is specific to the delimited format.

   5. Enter the starting position. This parameter is specific to the fixed-column format.

   6. Enter the ending position. This parameter is specific to the fixed-column format.

   7. Enter a caption.

3. Click Finish to complete the data feeder. The Browse Data Feeder screen reappears, displaying the new data feeder.

4.5.2.1 Editing the Basic Configuration of a Data Feeder

To edit the basic configuration of a data feeder:

1. From the Browse Data Feeders screen, select the data feeder that you wish to edit.

2. Click Edit.

3. The screen for editing the basic configuration of the data feeder appears, with its fields populated by the values set for the selected data feeder.

4. Edit the values as needed. See Section 4.5.1.1, "Step 1: Entering the Basic Information for the Data Feeder".for more information on the basic configuration parameters of a data feeder.

5. Click OK to save your changes. Clicking Cancel resets the basic configuration values back to their original state and returns you to the Browse Data Feeders screen.

4.5.2.2 Editing the Init Parameters of a Data Feeder

To edit the init parameters of a data feeder:

1. From the menu, select Init Parameters. The screen for editing init parameters appears, populated with the init parameters set for the selected data feeder.

2. Edit the init parameters as needed. See Section 4.5.1.2, "Step 2: Entering the Initialization Parameters for the Data Feeder" for more information on the init parameters of a data feeder.

3. Click OK to save your changes. Clicking Cancel resets the values for the init parameters back to their original state and returns you to the Browse Data Feeders screen

4.5.2.3 Editing the Input Parameters of a Data Feeder

To edit the output parameters of a data feeder:

1. From the menu, select Input Parameters. The screen for editing the input parameters appears, populated with the values set for the selected data feeder.

2. Edit the values as needed. See Section 4.5.1.8, "Step 3: Entering the Input Parameters for the Data Feeder" for more information on the input parameters of a data feeder.

3. Click OK to save your changes. Clicking Cancel sets the input parameters to their original state and returns you to the Browse Data Feeders screen.

4.5.2.4 Editing the Output Parameters of a Data Feeder

To edit the output parameters of a data feeder:

1. From the menu, select Output parameters. The screen for editing the output parameters appears, populated with the values set for the selected data feeder.

2. Edit the values as needed. See Section 4.5.1.9, "Step 4: Entering the Output Parameters for the Data Feeder" for more information on the output parameters of a data feeder.

3. Click OK to save your changes. Clicking Cancel sets the output parameters back to their original state and returns you to the Browse Data Feeder screen.

4.6.1.1 Adding Preset Attributes

Preset attributes enable you to define the relation of input parameters that an end user can enter and save on the OracleAS Wireless server. You click the ADD button in the Create Preset Screen to add an attribute to the table. In the blank row that appears, you define the following parameters, described in Table 4-21.

Click Finish after you have added the preset. Clicking Cancel clears all values and returns you to the Browse Preset Definitions screen.

You can add several rows of preset attributes (Figure 4-27) to define relationships, such as Name, Street Address, Phone Number.

Figure 4-27 The Create Preset Definition Screen

Description of "Figure 4-27 The Create Preset Definition Screen"

4.6.2.1 Adding, Editing, and Deleting Preset Attribute Enumeration Options

You can edit, add, or delete a preset attribute enumeration option by using the Edit Preset Descriptor Enumeration Options screen.

To edit a preset descriptor enumeration option:

1. In the Preset Descriptors section of either the Create Preset Definitions screen or the Edit Preset Definitions screen, select Enum.

2. Click Edit. The Edit Preset Descriptor Enumeration Options screen appears.

3. In the Description Enumeration Options screen, perform the following operations as needed:

   • From the drop-down list, select the option you wish to edit or delete.

   • Click Add to add a new enumeration option.

4. Click Done. The Create Preset Definition screen or the Edit Preset Definition screen reappears.

4.7.2.1 Viewing the Class Method Details

You can view the Web service method details of a Web service after you register the J2ME Web Service with the J2ME proxy server. To view the method details, select a J2ME web service from the browsing page and then click the Method Details button. The J2ME Web Service Details screen appears (Figure 4-31), displaying method details by name, return type and parameter types.

Figure 4-31 Viewing the Method Details of the J2ME Web Service

Description of "Figure 4-31 Viewing the Method Details of the J2ME Web Service "

See Section 12.2, "Digital Rights Management Support" for information on coding a J2ME Web service.