Oracle9iAS Wireless Getting Started and System Guide Release 2 (9.0.2) Part Number A90486-02 |
|
This chapter describes how Content Developers use the Service Designer to create and manage objects of the Oracle9iAS Wireless repository. Each section of this document presents a different topic. These sections include:
The Service Designer is a Web-based interface that enables Content Developers to create the following objects:
Master services provide the actual implementation of the service. They specify the adapter used for the service and any service-specific parameters. By mapping an adapter to device transformers, master services link Wireless content sources to delivery platforms. Each master service is based on one adapter. A master service creates its own instance of the adapter it uses. Therefore, several services can use the same type of adapter, and each can pass its own service-specific argument values.
Content Managers create services based on master services and assign them to user groups.
The Service Designer enables you to augment master services by making them accessible by protocols other than HTTP. For example, you could assign an async agent service for services accessed by users whose devices do not have a Web browser, but support two-way messaging or email.
With async agent-enables services, users can access Web content. For example, async agent services enable end users who subscribe to OracleMobile to retrieve such Web content as stock quotes, traffic reports, or horoscopes by sending a message to Ask@OracleMobile.com. The Ask listener running on the iAS Wireless Server intercepts this message, which can be either an email or a short message, routes the request to the correct service or application, and then sends the requested information back to the user.
A master alert is a template for an alert, a notification service delivered to users based on the trigger conditions they set when subscribing to an alert service. Master alerts designate the data feeders used for an alert service as well as the trigger parameter definition, trigger condition definition and optionally input parameter definition for an alert service. In addition, the master alert presents a simple result XML message template.
An alert service can deliver alert messages which are drawn from data feeds on a determined value, or at a scheduled time.
The default delivery mechanism of the alert message is through the transport module. The alert engine may provide hooks to invoke a customized message delivery mechanism to handle the alert delivery event.
A data feeder is a repository object that retrieves content from both internal and external content sources and then converts that content into a standard XML format. The data feeder mechanism then publishes the content to the alert engine, which formats and sends alert messages that use the content that the data feeder retrieved and rendered from the content source.
A logical device is a repository object that represents either a physical device, such as an Ericsson mobile phone, or an abstract device, such as an email server. Logical devices represent the interface between transformers and the target devices or applications
Presets enable users to personalize services by defining their own input parameters for an application. When a user requests a service, an adapter loads the user-defined input parameters, or presets. The service presents these presets as a list for the user, who must then select an item to execute the application. Wireless saves users presets on a table specific to each service.
Transformers are Java programs or XSLT stylesheets that convert a document into either the target format or to another Wireless format. Transformers not only map source tags to target format tags, but they can also manipulate content. Because transformers can rearrange, filter, and add text, you can present content in the format, as well as the form factor that is best suited for the target device.
The Wireless initial repository includes transformers for several target formats, such as CHTML, HDML, HTML, MML, VoiceXML, VoxML, and WAP (WML). By modifying the provided transformers, or by creating new ones, you can target new device platforms and optimize content presentation for specific devices. Wireless publishes device transformation rule files so that anyone can create support for any type of device and markup language.
The transformer associated with a logical device is that device's default transformer. Default transformers are typically generalized for a markup format, but they can also be specific to a target device. Wireless uses the device's default transformer to convert any service targeted for that type of device, unless a custom device transformer overrides the default transformer. A custom device transformer enables you to control how a service appears on a specific device. While several devices can use a single default transformer, a custom transformer can be associated with only one master service and one device. The custom transformer optimizes the presentation of that service for a particular device and can only be used for that device.
When you create a transformer, you map the elements in the source content to the result format.
An adapter is a Java application that retrieves data from an external source and renders it in Wireless XML. In the Oracle9iAS Wireless architecture, adapters constitute the interface between the Wireless server and the content source. When invoked by a master service, an adapter returns an XML object that contains the service content. This XML object is processed by the core of the Wireless and then delivered to the user's device as a the response to the user's service request.
Wireless uses regions to enable developers to assign a location to a service, making the service location-based, unique to a specified area.
Before using the Service Designer, you must first log into the Webtool as follows:
After you successfully login, the Service screen of the Service Designer appears with the Service Designer Tab selected. The Service Designer Tab contains the following subtabs:
The Service Designer provides a tab for each of these repository objects. Each tab has a browsing screen, which enables you to search for an object, as well as access to functions for creating, editing and deleting, and testing objects.
Selecting the Master Services tab displays the Browse Folder screen, which enables you to create, edit, delete, debug, and move master services and folders. The screen also enables you to test master service and view it on a phone simulator.
The Browse Folder screen enables you to view the top-level folders in the hierarchy, which the Service Designer displays as hyperlinks. These hyperlinks allow you to "drill down" or traverse deeper into the hierarchy with each successive click. Wireless displays the structure of the hierarchy, enabling you to see level you currently access.
The Browse Folder screen displays Wireless objects as follows:
Table 10-1 Elements of the Browse Folder Screen of the Service Designer
The Browse Folder screen of the Service Designer enables you to search for a master service using a search field in conjunction with drop-down lists of search options, which you can use to either narrow or broaden your searches. The search results display as a list on the Search Result screen.
To find an object, perform one or more of the following and then click Go.
Table 10-2 Elements of the Search Results Screen of the Service Designer
You can organize your repository objects by creating subfolders. These subfolders, which can represent topic areas, can be nested into other subfolders. When you create a subfolder, the Service Designer displays it as a hyperlink in the Browse screen. Clicking this hyperlink enables you to see the folder's contents.
To create a folder:
Table 10-3 Parameters of the Create Folder Screen
The Service Designer enables you to create a master service using the Master Service Creation Wizard. This tool provides you with a separate screen for each step of the creation process.
Note: You must follow the sequence to its end to create a master service; if you exit the wizard at any point by selecting Cancel, you lose all the values you have entered. |
From the Browse Folder Screen, click Create Master Service. The Basic Information screen of the Master Service Creation Wizard appears. You use this screen to enter the configuration properties for the master service. The Screen contains the following fields:
Table 10-4 Basic Configuration Parameters for the Master Service
Enter the following in the Basic Information screen:
Note: The SQL adapter and the Web Integration adapter are deprecated in this release. See the Oracle9iAS Developer's Guide for more information on adapters. |
You select the Cacheable check box for a service with changing content. Selecting the Cacheable option saves the adapter invocation and transformation. If you create a caching master service, then you must specify the frequency at which the Wireless server notifies the cache when a Web page has changed by issuing an invalidation report. If you do not wish to create a services that can be cached, leave the Cacheable check box clear, and click Next.
To create a service that can be stored in cache:
The Init Parameters screen contains the init parameters for the adapter you chose in Step 2. Not all adapters have init parameters. Enter the values for the init parameters and click Next. If the selected adapter does not contain init adapters, click Next.
Note: The SQL adapter and the Web Integration adapter are deprecated in this release. See Section 10.10 for more information on setting the parameters for the AppsFramework adapter, the Mobile Applications Framework adapter, the SQL Adapter and the Web Integration adapter. |
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:
Note: You must specify the classpath in the OC4J config/application .XML file or you must copy the .jar file to wirless/lib. |
The Input Parameters Screen displays the input parameters for the adapter you selected in Step 1. The Master Service Creation Wizard queries the adapter definition to determine the parameters that appear in this screen. The input parameters for master services using the HTTP Adapter and the OC4J Adapter include the following:
Table 10-5 Input Parameters for 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 master service.
To select an input parameter for the master service, Click on the Select radio button next to the input parameter you want to use and then click Next.
To add a new parameter to the adapter you selected in Step 1:
See Section 10.10 for information on the parameters for the SQL Adapter and WebIntegration Adapter.
To delete an input parameter,
The HTTP adapter retrieves remote content and delivers it as mobile XML.The input paramters for the HTTP adapter include:
Table 10-6 The Input Parameters for the HTTP Adapter
The Output Parameters screen enables you to select the output parameters for the adapter selected in Step 1, or optionally add output adapters for that adapter. The Master Service Creation Wizard queries the adapter definition to determine the parameters that appear in this screen.
Note: You do not need to define output parameters for master services using the HTTP adapter and the OC4J adapter. |
The output parameters have the following attributes:
Table 10-7 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.
Perform the following to add a new output parameter to the adapter selected in Step 1:
After you have finished adding or deleting the output parameters for the adapter, click Next. The Confirmation screen appears if Wireless has not found a PASection
in the master service you have created. Review the values listed on the Confirmation screen. If they are correct, click the Finish button. You have completed creating a master service.
If your master service contains a PASection
, the Create Result Transformer screen appears.
By assigning Async Agent to a master service, you create a master service that can be accessed by protocols other than HTTP.
To set the values for an Async Agent service:
After you have set the output parameters for the adapter, 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 Master Service 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 stylesheet 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.
PASection
you wish 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.
To add a new result transformer:
You have created a master service. This master service is not visible to users until the Content Manager publishes a service based based upon it to user groups.
The Edit button in the Browse Folder screen enables you to edit the basic configuration, init parameters, input parameters, output parameters, Async Agent functions, and result transformer of a master alert.
To edit a the basic configuration parameters of a master service:
To edit the caching information for a the selected master service:
To edit the init parameters of a master service:
To edit the input parameters of a master service:
To edit the output parameters of a master service:
To edit an Async Agent service:
To edit the result transformer:
To delete a master service:
The Service Designer enables you to simultaneously view a master service on a phone simulator and in Wireless XML or device markup languages.
Transformers, in the form of XSLT stylesheets or Java classes, convert the content returned by Wireless adapters into the format best suited to a particular platform.
To test a service:
Selecting this result type enables you to see Wireless source content in the AdapterResult format, the intermediary format between the source and the target output device. Source content in the AdapterResult format must be converted into SimpleResult format before it can be delivered to a target device. If no text displays in the The Result panel, then no AdapterResult has been produced.
Selecting Wireless XML Result displays the source content in Wireless' SimpleResult format of the output that is returned by an adapter.
The DeviceTransformer drop-down menu lists the logical devices in the repository. Selecting a logical device enables you to see the final markup language for that device.
The System Log section enables you to set the number of lines from the end of the server's system log file that you want to see.
To set the number of lines from the server: displays from the end of the system log.
The Service Designers Move function enables you to organize your master services and folders.
To move a master service:
The Alerts tab of the Service Designer enables you to create, edit and delete master alerts. When you select the Alerts tab, the Browse Alerts screen appears, displaying a list of the current master alerts. The Browse screen organizes the master alerts as follows:
Table 10-8 Element of the Browse Master Alerts Screen
The Master Alert Creation Wizard steps you through the creation of a master alert. This wizard, invoked by clicking the Create Master Alert button in the Browse Master Alerts screen, provides a separate screen for each step of the process.
Once you have created a master alert, a user with the System role this master alert to an alert engine process. The master alert becomes active once the Sytstem manager starts the both alert engine process and the data feeder engine process.
You enter the basic configuration parameters for the master alert in the Basic Info. screen, the first in the master alert creation sequence.
The Basic Info. screen includes the following parameters:
Table 10-9 Basic Configuration Parameters for a Master Alert
To enter the basic configuration parameters for the master alert:
You use the Trigger Condition screen to enable end users to set the conditions that invoke an alert on end users' devices. For example, if you create an alert notifying users of a stock price, you can to set the alert conditions that allow an end user to request a notification when the stock has risen above, or fallen below, a certain price.
The Trigger Condition screen includes the following parameters:
Table 10-10 Trigger Conditions for Master Alerts
Parameter | Value |
---|---|
Condition Name |
The name of the alert trigger for the master alert. The Trigger name must contain only alphanumeric characters and underscore and must be within 30 characters. In addition, the trigger name cannot start with a numeric character and cannot use SQL reserved words. End users seel this label when they subscribe to an alert service. |
Trigger Parameter |
The trigger parameter is an element in a data feeder that you define a trigger condition against. For example, if a data feeder for a stock alert service inlcudes an output parameter of stock price, you could select stock price as the trigger parameters for a condition name. For information on setting the output parameters of a data feeder, see Section 10.5.2.4. |
Condition Type |
The condition, in relation to the value set by the end user, which triggers the alert. |
Default Value |
The default value for the parameter. If you specify a default value, Wireless does not prompt the user for a value. Default values can be overridden by a value specified by a service created by the Content Manager or, if the parameter is visible to the user, by the user through Wireless Customization. |
To select a trigger condition:
To add a new Trigger Condition
If the data type is a number, then the conditions include:
If the data type is text, then the condition types include:
The Message Template screen allows you to either import a message template or provide a hook.
The data feeder output values are the dynamic values in the SimpleText stylesheet. The following stylesheet represents these values as &price
and &change
.
<SimpleText> Stock Alert for [&sym;]: Price: &price; Change: &change;</SimpleText>
To import a message template:
Note: Wireless will not commit any of the values you have entered until you have completed the entire wizard. |
To create a message template by providing a programming hook:
The Edit button in the Browse Master Alerts screen enables you to edit the basic configuration parameters, trigger conditions, and message template for a master alert.
To edit the basic configuration parameters of a master alert:
To edit the trigger conditions of a master alert:
To edit the message template of a master alert:
See Section 10.4.1.3 for information on the message template for a master alert.
The Service Designer's Data Feeder tab enables you to create, edit, and delete data feeders, Wireless object that download data from an internal or external content source and converts that data into a common format for Wireless mobile alerts.
Clicking the Data Feeders tab displays the browse data feeders screen, which lists the current data feeders. The Browse Data Feeders screen displays the data feeders as follows:
Table 10-11 Elements of the Browse Data Feeders Screen
You create data feeders with the Data Feeder Creation Wizard. This wizard, invoked by clicking the Create Data Feeder button in the Browse Data Feeders screen, steps you through the creation of a data feeder by providing a separate screen for each phase of the process.
Once you create a data feeder, you can assign it to a master alert. A data feeder (and consequently the alert that derives its content using the data feeder) cannot become active until a user with the System role assigns it to a configured data feeder process and then starts the process.
The Basic Info screen of the Data Feeder Creation Wizard enables you enter the basic properties for the data feeder.
The Basic Info. screen of the Data Feeder Creation Wizard includes the following parameters.
Table 10-12 Parameters of the Basic Info. Screen of the Data Feeder Creation Wizard
Complete the Basic Info. screen as follows:
The Init Parameters screen displays the init parameters specific to the protocol and format type you selected in Section 10.5.1.1.
Table 10-13 Init Parameters for Data Feeder Protocols
To enter the init parameters for a data feeder using the HTTP protocol and the XML format type:
To Enter Init Parameters for a data feeder using the HTTP Protocol and the delimited format:
To Enter the Init Parameters for a data feeder using the HTTP protocol and the fixed column format:
To enter the init parameters for a data feeder using the file protocol and the XML format:
To enter the init parameters for a data feeder using the file protocol with the delimited format:
To enter the init parameters for a data feeder using the file protocol and the fixed column format:
To enter the init parameters for a data feeder using the FTP protocol and the XML format:
To enter the init parameters for a data feeder using the FTP protocol and the delimited format:
To enter init parameters for a data feeder using the FTP protocol and the fixed column format:
To enter the init parameters for a data feeder using the SQL protocol and the XML format:
To enter the init parameters for a data feeder using the SQL protocol and the delimited format:
To enter the init parameters for a data feeder using the SQL protocol and the fixed column format:
To enter the init parameters for a data feeder using the application protocol and the XML format:
To enter the init parameters for a data feeder using the application protocol and the delimited format:
To enter init parameters for a data feeder using the application protocol with the fixed column format:
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 10.5.1.1.
The data feeder input parameters include the following:
Table 10-14 Data Feeder Input Parameters
To enter the input parameters:
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 10.5.1.1.
The output parameters are the retrieved data from the content provider; you set alerts on the output parameters of a data feeder.
The data feeder output parameters include the following:
Table 10-15 Data Feeder Output Parameters
To enter the input parameters:
The Edit button in the Browse Data Feeder screen enables you to edit the basic configuration, init parameters, input parameters, and output parameters of a data feeder.
To edit the basic configuration of a data feeder:
To edit the init parameters of a data feeder:
To edit the output parameters of a data feeder:
To edit the output parameters of a data feeder:
A logical device is an object in the Wireless repository that represents either a physical device, such as a Nokia mobile phone, or an abstract device, such as email. Logical devices represent the interface between Wireless transformers and the target devices or applications.
Wireless determines the type of device that is requesting a service from the HTTP header. A device agent identifies the user's device address, such as an email address or telephone number and device type. This information enables Wireless to deliver notifications to the user.
You use the Logical Devices tab to create a logical device in the repository. When you click the Logical Device tab, the Browse Logical Devices screen appears, displaying a list of logical devices in the repository. Using the Browse Logical Device screen, you can search for, create, delete, and edit the user agents of a logical device.
From the Browse screen, you can search for logical devices using the Keyword field. You can sort your search results by name, user agents, or transformers. .
To search for a logical device:
You create a logical device using the logical device creation wizard. The logical device creation wizard guides you through each step of creating a logical device. When you complete a screen, you move to the next screen in the sequence by clicking the Next button. Clicking the Back button takes you to the preceding screen in the sequence, allowing you to perform edits.
Table 10-16 Parameters of the Logical Device Creation Wizard Basic Information Screen
The User Agent screen enables you to assign a user agent to the logical device by selecting from a list of user agents, mechanisms that identify device type and address.
To add a user agent.
Complete the Device Attributes screen as follows:
The Login Page screen enables you to create the XSLT stylesheet that generates the login page on the device.
The Error Page screen enables you to create an XSLT stylesheet that generates the error page for the device.
The Wireless Service Designer enables you to modify a logical device in the repository. To modify a logical device:
To delete a logical device from the repository:
Preset definitions enable users to personalize services by entering their own input parameters to an application. When a user requests a service, a service loads the user-defined input parameters, (or presets). Typically, the service may list these presets for the user, who must select an item to execute the application.
.
When selected, the Preset Definitions tab defaults to the Browse Preset Definitions Screen, which displays a list of the current preset definitions. From this screen, you can create, edit, and delete a preset definition.
The Browse Preset Definitions screen includes the following parameters.
Table 10-18 Parameters of the Browse Preset Definitions Screen
Parameter | Description |
---|---|
Preset Definition Name |
The name of the Preset Definition. |
Object ID |
The Object ID stored in the database. |
The Service Designer enables you to create a preset definition, a template which enables users to add values to each pre-defined preset definition. When users invoke a service, they select a value from any of the preset definitions as an input parameter.
To create a new preset definition:
Preset attributes enable you to define the relation of input parameters that an end user can enter and save on the Wireless server.
To add Preset Attributes to your preset definition:
Table 10-19 Preset Description Parameters
You can add several rows of preset attributes to define relationships, such as Name, Street Address, Phone Number.
To edit a preset definition:
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:
To delete a preset definition:
You use the Browse Transformer screen of the Transformer tab to create, edit, and delete transformers in the repository.
To create a new transformer:
Table 10-20 Transformer Parameters
Click Browse to find the XSL file that you want to use. Import the file by clicking Import. In the Import screen, enter the name of the file in the Import File field and then click Import, or retrieve the file using the Browse function and the Upload window. After you select the file, Click Open. From the Import Screen, click Import.
To edit a transformer:
To delete a transformer:
Selecting the Adapters tab invokes the Browse Adapters screen. You use this screen to create, edit, delete adapters.
To create an adapter:
Table 10-21 Adapter Parameters
To edit an adapter:
To delete an adapter:
The following sections describe the uses and parameters of the Wireless adapters.
The Init Parameters screen of the Master Service Creation Wizard shows the initialization parameters for the selected adapter. These parameters vary depending on the adapter implementation. When Wireless first invokes the adapter, it passes the values you set in the Init Parameters screen to the adapter.
The SQL adapter retrieves and adapts content from any JDBC-enabled data source for a master service based on the SQL adapter, the Init Parameters panel includes the following parameters:
Table 10-22 Init Parameters for the SQL Adapter
The Web Integration adapter retrieves and adapts Web content. The Web Integration adapter works with Web Interface Definition Language (WIDL) files to map source content to Wireless XML. Typically, the source format for the Web Integration adapter is HTML, but developers can also use the adapter to retrieve content in other formats, such as XML.
For a master service based on the Web Integration adapter, the Init Parameters panel appears as follows:
Table 10-23 Init Parameters of the Web Integration Adapter
The master service determines the parameters to display in the panel by querying the adapter. Every input parameter defined in the WIDL interface appears in the Inputs panel, including parameters for other WIDL services within the WIDL interface.
In addition to the custom input parameters that you create, Web Integration services provide these parameters:
The OutputType
specifies the type of XML output that the adapter should return. You can specify RawResult
, to return content in Adapter Result format, or SimpleResult
, to return content in Simple Result format. If returning raw result format, you must create a result transformer that converts the result into Simple Result for the device transformer. The result transformer should have the same name as the value you use for the PAsection
parameter; that is, it should have the same name as the WIDL service. You use RawResult
for chained services.
PAsection
is the name of the WIDL service that you want the master service to invoke. A WIDL interface can include more than one WIDL service. Wireless lists the WIDL service names in a selection list in the value field.
InputEncoding
specifies the encoding used to encode the source document. The source document is the URL that was used to create the WIDL file for this service. The default value of this parameter is UTF-8. If the language of the source document is an Asian language, you can change the default encoding to the appropriate multi-byte encoding according to the IANA standards for the particular Asian language that is used in the source document. The InputEncoding
parameter enables you to specify or change the encoding. It is part of the multi-byte character support. The Oracle9iAS Developer's Guide provides more information about multi-byte character support.
The Input Parameters screen displays the input parameters for the adapter. The Content Developer Tool queries the adapter definition to determine the parameters that appear in this panel. The master service passes the input parameter values to the adapter's invoke method every time the adapter executes.
Some parameters rely on user input for values. The values for other parameters, such as name of the WIDL service in the WIDL interface (PAsection
), are set by the master service or service. PAsection
is an internal parameter, not exposed to the end user. In addition to PAsection
, Wireless provides these input parameters:
Wireless input parameters includes the following:
Table 10-25 Input Parameters Attributes
To add a new input parameter to the adapter.
The AppsFramework adapter allows for the development of enterprise applications on top of Wireless. It provides system-wide standard application look and feel, enhanced application widgets support and data binding to enterprise data.
The AppsFramework adapter includes the input parameter classname which must be the package and class of the implementation of the MobileApplicationHandler interface. Refer to the Oracle9iAS Developer's Guide , Section 12.5.6 MobileApplicationHandler Interface, for more information.
The Mobile Application Framework adapter uses style and color mappings to provide a uniform look and feel that can be customized across all applications running on the server. In addition, carrier specific information can be specified to the Mobile Application Framework adapter to optimize the content delivered by the adapter. The StyleColorLoader command-line utility is used to modify the style, color, and SDU size information used by the Mobile Applications Framework adapter.
The <StyleSet> elements help the renderers for a given logical device render application styles into markup language, as described above. For example when a developer wants to create a prompt style "Prompt" and bind the style to the text of the prompt, he/she will create a "Prompt" style in the style repository.
Each <StyleSet> element contains a number of <Style> elements. Each <Style> element contains a name, a font face, font size, font style and font color. The property names are described below.
In addition to the <Style> element, the StyleSet contains the following elements.
By modifying application style definitions in a given <StyleSet>, the system administrator can control how the given application style is rendered on the logical device to which the style set is bound, across the whole system. For example, if the logical device PDA is bound to the StyleSet "Default", then if the system administrator changes the prompt style in the default StyleSet so that it is bold rather than simply plain, all prompts will appear bold rather than plain when rendered on client devices in the PDA Logical Device grouping.
The <ColorSet> element helps the renderers for a given logical device render application colors into markup language. For a given logical device this application color is mapped to a color code, which can be modified by the system administrator to produce the optimal rendering. For example, if the logical device PDA is bound to the ColorSet "Default", then if the system administrator changes the background color in the default ColorSet so that it is grey rather than simply white, the background color for all applications on client devices in the PDA Logical Device grouping will be grey instead of white.
A <ColorSet> element consists of multiple <Color> elements. Each <ColorSet> has the following properties:
A <ColorSet> element consists of multiple <Color> elements, each <Color> element has the following properties
PropertyName | Required | Multiple | Description |
---|---|---|---|
Name |
Y |
N |
The name of the Style. |
ColorDesc |
Y |
N |
The 24 bit color code of the given color, for example White = #FFFFFF. |
The <SDUSize> element helps the renderers for a given logical device render an optimized amount of information on pages. For a given logical device, the SDUSize is the upper limit on the amount of information (in bytes) that the network can carry to this device.
A <SDUSize> element consists of two child elements. They have the following properties:
You can configure SQL input parameters just as you can Web service parameters. You specify input parameters in the SQL statement you use to implement the service.
When you click the Regions tab in the Service Designer, the main displayof the region modeling tool appears.
The region modeling tool lets administrators of a wireless portal service create custom regions that can be associated with location-based services. When you create a service, if you specify that it is location dependent, you specify a region: either an Oracle-supplied system-defined region or a custom region previously created with the region modeling tool.
A region is simply a geographic entity, or location. A region can be small (such as a street address) or large (such as a country). A region can be represented by a point, as is often done for addresses and locations of interest (such as airports and museums), or by a polygon, as is usually done for states and countries. For detailed information about using the region modeling tool, click the Help button on modeling tool in the chapter on Location Services in the Oracle9iAS Developer's Guide.
|
Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|