A
Advanced Walkthrough

A.1 Creating Oracle9iAS Wireless Applications

These walkthroughs acquaint you with the Wireless Server by showing you how to build a Wireless service, and make it async-enabled. Also, this walkthrough guides you through creating and receiving an alert. You can apply these walkthroughs to your own projects which deploy mobile applications and alert services using Oracle9iAS Wireless services.

A.1.1 Creating the HttpAdapter Master Service, HelloMS

This walkthrough gives you an overview of theWireless Webtool, Wireless Customization, and the Wireless Web Server by creating a wireless application, HelloMS. In creating this application, you create a master service using the HttpAdapter, set the the HttpAdapter URL prefix and then test HelloMS. In addition, you use the User Manager to create a group and a user and then publish HelloMS to a user group as a service (Hello Service).

This walkthrough also guides you through configuring and starting a Wireless Web Server process, emulating the user experience by invoking the service from a device and view the both the system log and the service performance data.

A.1.1.1 Before You Begin

Before you access the Webtool, you must create the HelloMS and the HelloReplyMS JavaServer Pages.

A.1.1.2 Creating the HelloMS JavaServer Page Application

Using any editor, enter HelloMS.jsp as follows:

<?xml version = "1.0" encoding = "ISO-8859-1"?>
<%@ page contentType="text/vnd.oracle.mobilexml; charset=ISO-8859-1" %>
<SimpleResult>
   <SimpleContainer>
      <SimpleForm title="NameForm" target="reply/HelloReplyMS.jsp" 
method="POST">
	   <SimpleFormItem name="UserName" title="Name:" />
      </SimpleForm>
   </SimpleContainer>
</SimpleResult>

A.1.1.3 Creating the HelloReplyMS JavaServer Page

Enter the HelloReplyMS.jsp as follows:

<?xml version = "1.0" encoding = "ISO-8859-1"?>
<%@ page contentType="text/vnd.oracle.mobilexml; charset=ISO-8859-1" %>
<%
   String name = request.getParameter("UserName");
%>
<SimpleResult>
   <SimpleContainer>
      <SimpleText>
         <SimpleTextItem>Oracle9iAS Wireless says hello 
<%=name%></SimpleTextItem>
      </SimpleText>
   </SimpleContainer>
</SimpleResult>

A.1.1.4 Folders for HelloMS and HelloReplyMS

After you create the .jsps, you then place them in folders. Under a running Web servlet container file, create a files for the .jsps as follows:

1. Create a subfolder entitled app under $ORACLE_HOME/j2ee/OC4J_wireless/applications/examples/examples_web.

2. Copy HelloMS.jsp to the app folder.

3. Create a subfolder under the app folder entitled reply.

4. Copy HelloReplyMS.jsp to the reply folder.

Note: These .jsps must be accessed from a Web browser. For example, the app folder is created under an OC4J application, examples, which runs at localhost port 7777 and in a browser. You access the .jsps by entering the following URLs: http://localhost:7777/examples/app/HelloMS.jsp http://localhost:7777/examples/app/reply/HelloReplyMS.jsp

Each section of this walkthrough describes a step. These sections include:

• Section A.1.2, "Step 1: Creating the Master Service with the Service Designer"

• Section A.1.3, "Step 2: Using OEM to Set the HttpAdapter URL Prefix"

• Section A.1.4, "Step 3: Using the Webtool Simulator to Test and Debug HelloMS"

• Section A.1.5, "Step 4: Creating a User and User Group"

• Section A.1.6, "Step 5: Publishing HelloMS to TestGroup as a Service"

• Section A.1.7, "Step 6: Configuring and Starting the Wireless Web ServerProcess"

• Section A.1.8, "Step 7: Configuring and Starting the Performance Monitor"

• Section A.1.9, "Step 8: Customizing Hello Service Using Wireless Customization"

• Section A.1.10, "Step 9: Running HelloService in the Wireless Web Server"

• Section A.1.11, "Step 10: Viewing sys_panama.log and Service Performance Data"

• Section A.1.12, "Step 11: Viewing the User Service Log"

A.1.2 Step 1: Creating the Master Service with the Service Designer

This step leads you through creating an HttpAdapter service and its attribute settings. To create this service, you must access Wireless Webtool as follows:

1. Log into the Wireless Webtool using orcladmin as your user name and then enter your password.

2. From the Wireless Webtool, select the Service Designer tab. The Browse Folders screen of the Service Designer appears.

A.1.2.1 Creating a Folder for the Master Service

You can use folders to organize your master services.

To create a folder:

1. Click Add Subfolder. The Create Folder screen appears.

2. Complete the Create Folder screen as follows:
   1. Enter TestMSFolder in the Folder Name field. This is a required field.

   2. Select Valid so that this folder can be published to user groups by the Content Manager.

3. Click Create. The folder, TestMSFolder appears in the Browse Folder screen.

A.1.2.2 Creating a Master Service

Next, you add a master service to TestMSFolder.

To create a master service:

1. From the Browse Folders screen, click TestMsFolder.

2. Click Create Master Service. The Master Service Creation Wizard appears, displaying the Basic Info. screen, the first screen of the master service creation sequence.

3. Complete the Basic Info. screen as follows:
   1. Enter HelloMS in the Name field. This is a required field.

   2. In the Description field, enter Testing Master Service.

   3. From the drop-down list of adapters, select HttpAdapter. This is a required field.

   4. Select Valid so that the Content Manager can publish this master service to user groups (and edit its values, if needed).

Note: Leave the Modulable and Location-Dependent check boxes clear. Also, you do not have to enter any values for the Menu Icon URI, Title Icon URI, Menu Audio URI, or Title Audio URI fields for this walkthrough.

4. Click Next. The Caching screen appears.

A.1.2.3 Setting the Caching for the Master Service

The Caching screen enables you to cache the master service pages in the Web Cache Server.

To set the caching options:

1. Select the Cacheable check box if you would like to cache the master service with the Web Cache Server. Leave the check box clear if you do not want to cache this master service.

2. If you want to cache the master service, set the frequency of the invalidation.

3. Click Next. The Init Parameters screen appears.

Note: Cacheable is an optional field, one that can be left unselected.

A.1.2.4 Setting the Init Parameters

Do not enter any values into the HttpAdapterInvokerListener field.

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

• When the HttpAdapter 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: The HttpAdapterInvokeListener field is optional. You can leave it clear. If you specify a listener, you must specify the classpath in the @ORACLE_HOME/j2ee/OC4J_wireless/config/application.xml file or you must copy the .jar file to $ORACLE_HOME/j2ee/OC4J_wireless/lib.

A.1.2.5 Entering the Input Parameters

Click Next. The Input Parameters screen appears.

1. Complete the input parameters screen as follows:
   1. In the URL field, enter examples/app/HelloMS.jsp.

   2. In the REPACE_URL field, set True to enable the server to replace the relative URL in the .jsp with the entire URL. For example, the server replaces reply/HelloReplyMS.jsp as http://hostname:7777/examples/app/reply/HelloReplyMS.jsp. See Section A.1.3 for information on setting the HttpAdapter URL prefix.If you set the REPLACE_URL field to False as the the default setting, then Wireless does not replace the relative URLs. The default value is True.

   3. In the FORM_METHOD field, enter POST as the form method used between the Wireless Web server and the remote .jsp.

   4. Leave the INPUT_ENCODING field clear. If you specify an encoding, then the encoding you choose is used between the Wireless server and the .jsp.

2. Click Next. The Async Agent screen appears. Do not select the Async-Enabled check box.

3. Click Next. The Result Transformer screen appears. For this walkthrough, you do not have to specify a result transformer.

To complete the master service, click Finish. The master service, HelloMS appears in the Browse Folders screen under TestMSFolder.

Note: See for more information on using the Service Designer. See the Oracle9iAS Developer's Guide for more information on master service attribute definitions and the HTTPAdapter.

A.1.3 Step 2: Using OEM to Set the HttpAdapter URL Prefix

This step shows you how to specify the HttpAdapter URL prefix. This HttpAdapter uses this prefix to concatenate with the relative URL value defined for the URL input parameter of each HttpAdapter service.

To set the HttpAdapter URL prefix:

1. Login to the Oracle Enterprise Manager (OEM) using orcladmin as your user name and welcome as your password.

2. From the OEM console, drill down to Wireless . The Wireless Server tab appears.

3. Click the Site tab. The Site overview screen appears.

4. In the Administration section, select URL Configuration. The URL configuration screen appears.

5. For HttpAdapter URL Prefix, enter http://hostname:7777/.

6. Click OK. The Site Overview screen reappears.

Note: Ensure the the OC4J example application is running.

A.1.4 Step 3: Using the Webtool Simulator to Test and Debug HelloMS

The Webtool simulator enables you to simultaneously view a master service on a phone simulator and its immediate XML results. In this step, you use the Webtool's Service Designer to search for HelloMS, view and debug HelloMS.

A.1.4.1 Logging into the Webtool

To test HelloMS on the Webtool simulator:

1. Log into the Webtool using orcladmin as your user name and welcome as your password. The Webtool appears.

2. Select the Service Designer tab. The Browse Folder screen appears.

A.1.4.2 Searching for HelloMS

To find HelloMS:

1. Enter Hel* in the Name field.

2. From the drop-down menu, select Any Master Service.

3. Click Go.

4. The Search Results screen appears, displaying HelloMS. In the Full Path column, select the link TestMSFolder, which represents the folder containing HelloMS. The Browse Folder screen displays TestMSFolder as the current folder.

A.1.4.3 Viewing HelloMS on a Phone Simulator

To view HelloMS on a phone simulator:

1. Click the PhoneTest icon in the Test column. The phone simulator appears, displaying the page generated by HelloMS.jsp.

2. Enter your name (for example, Scott) in the Name field.

3. Click Submit. The next page, generated by HelloReplyMS.jsp, appears, displaying "Oracle9iAS Wireless says hello Scott."

A.1.4.4 Debugging HelloMS

In this step, you use the debugging tool to view the Wireless XML result of HelloMS.

To view the Wireless XML result of HelloMS:

1. Select HelloMS in the Browse Folder screen.

2. Click Debug.

3. In the Debug screen, do the following:
   1. Select View Wireless XML Result.

   2. Click Set Parameters

   3. Click Run Service. The phone simulator appears, displaying the first page of HelloMS, which is generated by HelloMS.jsp. The Service Result section of the screen displays the intermediate result in Wireless XML, enabling you to see if this is the result that you want to generate.

   4. On the phone simulator, enter your name and then click Submit. The Service Result section of the screen displays the Wireless XML for the second page, which is generated by HelloReplyMS.jsp.

A.1.4.5 Viewing Another Device Result of HelloMS

If you want to see a device result other than Wireless XML for HelloMS:

1. In the Debug Parameter section, select View Device Result.

2. From the drop-down list, select a device result type, such as WML11. Click Set Parameters.

3. To view the device results for HelloMS, follow the steps 3c and 3d in Section A.1.4.4.

A.1.4.6 Viewing the System Log File

The System Log section enables you to view the number of lines from the end of the system log file (sys_panama.log)

To view a selected number of lines from the logging file:

1. Enter the number of lines you want to display in the System Log section. For example, enter 100.

2. Click Refresh Log. The designated number of lines of the logging file display.

Note: See Chapter 10, "Developing Services" for more information on testing and debugging a master service.

A.1.5 Step 4: Creating a User and User Group

In this section, you create a user account and then assign the user to a user group. Log into the Webtool using orcladmin as your user name and welcome as your password. The Webtool appears.

A.1.5.1 Creating a User Group

You first create a user group:

1. Select the User Manager tab.

2. Select the Groups tab. The Groups screen appears, displaying the current user groups.

3. In the Create New Group section, enter TestGroup in the Group Name field.

4. Click Create. TestGroup appears in the Group Name section.

A.1.5.2 Creating a User

Next, you create a user for TestGroup.

To create a user:

1. Click the User tab. The User screen appears, displaying the current users.

2. In the Users screen, click Create. The Create a New User screen appears.

3. Complete the basic information for the new user by entering the following values:
   1. In the User Name field, enter TestUser

   2. Enter Test User in the Display Name field.

   3. In the Password field, enter 1234.

   4. Enter 1234 once more in the Password Confirmation field.

   5. Enter My Birthday in the Password Hint field.

   6. Enter 01/01/1960 in the Password Answer field.

   7. Enter 12345 in the Account Number field. Having an account number enables Test User to access services from a hand-held device more easily than by entering an name.

   8. Enter 1234 as the PIN for the account number.

   9. Enter 1234 again in the PIN Confirmation field.

   10. Select male as the gender of the user.

   11. From the drop-down list, select Registered User.

   12. In the Date of Birth field, enter 01/01/1960.

   13. Select Enabled so that Test User can log in.

4. Complete the User Preference section as follows:
   1. From the Language drop-down list, select English.

   2. Select Pacific Standard Time from the Time Zone drop-down list.

   3. Select User Home from the User Home Root drop-down list.

   4. Select Disclose Identity to External Application to disclose your identity to a third-party application.

   5. Select Disclose Location to an external application to disclose your current location to third-party application.

5. Complete the Group and Role sections as follows:
   1. From the Group list, select Test Group and then use the Select arrow (>).

   2. Do not assign any roles.

6. Click Finish. The User screen reappears, displaying Test User.

A.1.6 Step 5: Publishing HelloMS to TestGroup as a Service

You publish a master service to a user group by creating a service. A service is based on a master service and inherits its values. Services enable you to specialize a master service by modifying its values.

In this section, you use the Content Manager to create a folder and then a service. You then publish the folder and the service to the user group, TestGroup.

To access the Content Manager, you must log into the Webtool using orcladmin as your user name and welcome as your password. The Webtool appears.

A.1.6.1 Creating a Folder

1. Select the Content Manager tab. The service browse screen appears.

2. Click Add Folder. The General page of the New Folder screen appears.

3. Complete the general parameters of the folder as follows:
   1. Enter TestFolder in the Name field.

   2. In the Description field, enter TestFolder.

   3. Enter zero (0) in the Sequence field.

   4. Select System from the Renderer Type drop-down list. The System option sorts folders by sequence number, then by name.

   5. Select Personalizable so that you can reorder, hide, or show this folder.

4. Click Continue. The Rendering screen appears. From the drop-down list, select Name Ascend.

5. Click Finish the Service Browse screen reappears, displaying TestFolder. click Test Folder. Service Browse screen for Test Folder appears. Because Test Folder is new, the Browse Service screen for Test Folder displays no services.

A.1.6.2 Creating a Service

In this step, you use the Content Manager's Service Creation Wizard to create a service based on the master service, HelloMS. Because you create this service in the browse service screen of Test Folder, this service will reside in Test Folder.

A.1.6.3 Entering the General Information for a Service

To create a service:

1. From the Browse Service screen of Test Folder, click Add Service. The General screen of the Service Creation Wizard appears.

2. Complete the General screen as follows. You need only to complete the fields noted here.
   1. Enter HelloService in the Service Name field.

   2. Enter Test Hello Service in the Description field.

   3. Enter zero (0) in the Sequence field.

   4. Enter zero (0) in the Cost field.

   5. Select the Visible check box to make this service visible to Test User.

   6. Select the Personalizable check box to enable you to reorder, or hide or show this service.

   7. Select Normal Service.

3. Select Next. The Master Service screen appears.

A.1.6.4 Basing Hello Service on a Master Service (HelloMS)

1. Click TestMSFolder.

2. Select HelloMS using the radio button.

3. Click Next. The Input Parameters screen appears.

A.1.6.5 Setting the Input Parameters for HelloService

The Input parameters screen displays the input parameters that you set for Hello MS using the Service Designer. You do not have to change the input parameters. Click Next. The Async Services screen screen appears.

A.1.6.6 Setting the Async Services Parameters

The Async Services screen enables you to set the parameters for an async service. Since the master services, HelloMS is not async-enabled, you do not have to enter any values in this screen. Click Submit to complete Hello Service.

The Browse Service screen for TestFolder reappears, displaying HelloService.

A.1.6.7 Assigning Hello Service to a Group

In this section, you use the Content Manager to assign HelloService to a user group, TestGroup, which you created with the User Manager.

1. Click the Groups Tab. The Groups List screen appears.

2. Use the radio box to select TestGroup.

3. Click Assign Services. The Service Content screen for TestFolder appears. The screen includes two tables: services accessible to the Test Group and the Available Services table, which lists services that currently exist in the repository.

4. Using the Select check box, select TestFolder from the Available Services table.

5. Click Add to Group. Test Folder appears in the available services for Test Group.

6. Click Finish. The Group List screen reappears.

A.1.7 Step 6: Configuring and Starting the Wireless Web ServerProcess

In this section, you use the Wireless system management functions (accessed through the OEM console) to configure the connection pool, log directory, URL prefix, and HttpAdapter, and then start the Wireless Web server.

A.1.7.1 Configuring the Connection Pool

To configure the connection pool.

1. After you log into OEM and drill down from the Wireless system component, click the Site tab. The Site screen appears.

2. From the Administration section of the screen, select Connection Pool. The JDBC Connection Pool screen appears.

3. Complete the JDBC Connection Pool screen as follows:
   1. Enter the minimum number of connections for the connection pool. The default is 4.

   2. Enter the maximum number of connections for the connection pool. The default is 100.

   3. Enter the incremental allocation of new connections to the connection pool. The default is 1.

4. Click OK. The Site screen reappears.

Note: The values you enter in the JDBC Connection Pool screen in the Site tab are used as the default connection values for the Wireless Web Server and Async Server applications, as well as the Wireless Webtool and the Wireless Customization.

A.1.7.2 Configuring the System Logging

Next, you configure the system logging.

1. From the Administration section of the Site screen, select Logging. The System Logging screen appears.

2. Complete the System Logging screen as follows:
   1. Enter the name of a log file. The default is sys_panama.log.

   2. Enter the maximum number of bytes in the Maximum Log File Size field. The default value is 10000.

   3. Select the logging level from the log level list. The default is Warning and Error.

3. Click Finish. The Site screen reappears.

Note: The values you enter in the System Logging screen of the Site tab are used as the default values for the Wireless Web Server and Async Server applications, as well as the Wireless Webtool and the Wireless Customization. Unless these values are overridden, the server processes of the Alert Engine, Data Feeder, Messaging Server, and Performance Monitor also use them as the default system logging configuration.

A.1.7.3 Configuring the Site URLs for the Wireless Web Server

To configure the Site URLs:

1. From the Administration section of the Site tab, select URL Configuration. The URL Configuration screen appears.

2. Complete the screen as follows:
   1. Enter the Wireless Web Server HTTP URL. The default setting is http://hostname:7777/ptg/rm.

   2. Enter the Wireless Server HTTPS URL. The default setting is http://hostname:7777/ptg/rm.

3. Click OK. The Site screen reappears.

A.1.7.4 Configuring the Logging Directory for the Wireless Web Server

To configure the logging directory:

1. Select the Server tab. The Server screen appears.

2. From the Configuration section, select Logging Directory.

3. In the System Logging screen, specify the logging directory. For example, enter /tmp. All of the servlet container processes and standalone processes log error, warning and notification to this directory. The runtime data, such as service invocation and user session are also logged to this directory.

A.1.7.5 Starting the Wireless Server

After you have logged into the OEM console, you can start the

To start the Wireless Server as follows:

1. Click the Enterprise Manager link. The home page of the Enterprise Manager appears.

2. Drill down to the OC4J Component screen.

3. Start the Wireless Server product group. Starting this product group also starts the Wireless Web Server and the Async Server.

A.1.8 Step 7: Configuring and Starting the Performance Monitor

To complete this section, you must first access Wireless from the Oracle Enterprise Manager.

A.1.8.1 Configuring the Performance Monitor Schema

1. Drill down to the Wireless Server and then click the Site tab.

2. Select Performance Monitor from the Processes table. The Performance Monitor Configuration screen appears.

3. Accept the settings in the Basic Configuration section. The default settings are as follows:
   • The delimiter for the logged name/value pairs is #%=%#.

   • The delimiter for logged records is ~#$.

   • The default wakeup frequency is one (1) minute.

   • The default close frequency is 300 seconds.

   • The batch size for the database logging is 15.

4. If needed, modify the wakeup and frequency values.

5. Click OK.

Note: You do not need to specify the values for the JDBC Driver section. If you do not enter a username, password, host name, or SID, then Wireless logs the runtime data to the same schema as the Wireless schema. You can also specify the JDBC driver values to log the runtime data to a separate schema. See Chapter 7, "Server Performance Monitoring" for viewing runtime data. The default port number for the JDBC driver is 1521.

A.1.8.2 Configuring the Performance MonitorThread Pool

To configure the thread pool:

1. Click the Wireless Server tab.

2. From the Processes table, select Performance Monitor. The Performance Monitor Processes screen appears.

3. Click a performance monitoring process. The detail screen for that process appears.

4. From the Configuration screen, select Thread Pool Configuration. The Thread Pool Configuration screen appears.

5. If needed, increase the number of threads to increase the speed of the logging processes.

6. Click OK. The detail screen for the performance monitor process reappears.

7. If the performance monitor process is stopped, then start it by clicking the Start button. This process moves the runtime data logged in the logging directory file to the specified logging database schema. The data in the database schema is retrieved and displayed as performance data table or chart.

A.1.9 Step 8: Customizing Hello Service Using Wireless Customization

In this step, you use Wireless Customization to tailor HelloService to different user view profiles.

A.1.9.1 Logging into Wireless Customization

To access the Wireless Customization tool from a Web browser, enter a URL. For example:

http://hostname:7777/customization/Login.jsp

In the login page, enter TestUser as the username and 1234 as the password. The Service subscription screen appears, displaying the service tree. The user profile displays the system generated default profile.

A.1.9.2 Managing the View Profile

To manage the view profile.

1. Click View Profiles. The View Profiles screen appears.

2. In the View Profile Name field, enter Work.

3. Click Create. The new view profile, Work, appears in the View Profile List.

4. Create another view profile, Home, using these steps.

A.1.9.3 Customizing a Hello Service for the Work View Profile

In this step, you make Hello Service visible in the Work view profile.

To select Work as the view profile:

1. Click the Services tab. The Service Subscription screen appears.

2. From the Select a View Profile drop-down, select Work.

3. Click Go.

4. Click HelloService. (You may have to expand the folders of the service tree to access Hello Service). The Edit service page appears.

5. In the Edit Service screen, select the Visible check box to make Hello Service visible in the work view profile. The Visible check box is clear in the default setting.

6. Click Apply. The Service Subscription screen reappears.

A.1.9.4 Hiding Hello Service in the Home View Profile

In this step, you differentiate the Home view profile from the Work view profile by hiding Hello Service in the Home view profile.

To hide HelloService in the Home view profile:

1. Click the Services tab. The Service Subscription screen appears.

2. From the Select a View Profile drop-down, select Home.

3. Click Go.

4. Click HelloService. The Edit Service screen appears.

5. Clear the Visible check box.

6. Click Apply. The Service Subscription screen reappears.

7. Click the View Profiles tab.

8. From the View Profile list, select Work.

9. Click the SetDefault button.

For more information on user profiles see Chapter 13, "Customizing Services".

A.1.10 Step 9: Running HelloService in the Wireless Web Server

Running Hello Service from Wireless Web Server enables you to see the device-level view of the service.

1. In the login page for Wireless Web server, enter TestUser and then 1234 as your password. Your home page appears, displaying the settings for the Work user profile (both TestFolder and HelloService are visible).

2. Click Test Folder. Hello Service appears.

3. Click Hello Service.

4. Enter your name and then click Submit. The phone simulator displays "Oracle9iAS Wireless says hello (your name )".

A.1.10.1 Changing Your Default User View Profile

To change your user profile from Work to Home.

1. Return to your home page.

2. Select the User Profile from the set up menu.

3. Click Go. The User Profile page appears, displaying the current user view profiles, Work, Home, and System Generated Profile. Wireless places an asterisk (*) in front of the default profile, Work.

4. Select Home.

5. Click Set Default. An asterisk (*) appears before Home, designating it as the current default view profile.

6. Return to your home page.

7. Click TestFolder. This time, HelloService does not appear, since you hid this service from the Home profile inWireless Customization in Section A.1.9.4.

A.1.11 Step 10: Viewing sys_panama.log and Service Performance Data

For this walkthrough, you access Wireless through the OEM to view the system log file and also view the service performance on a per-user basis.

1. From the Wireless Server tab, click the Wireless Web Server. The Wireless Server screen appears.

2. From the Runtime section, click System Log Files. The System Log Files screen appears, displaying all of the files in the log directory.

3. Find sys_panama.log.

4. Click the eyeglass icon in the same row. A viewing screen appears for sys-panama.log. The log file appears in the text pane.

5. Click Printable Page. The log file appears in full-screen view, which enables you to easily print the log file.

6. To exit the Printable Page, click your browser's back button.

7. Click the Wireless Server tab. The Wireless Server screen appears.

8. Click the process name in the table.

9. In the Process table, click the Wireless Web Server process. The Wireless Web Server processes screen appears.

10. In the Performance Section, select User Service. The User Service screen appears. This screen displays the number of invoked services on a per-user basis.

11. From the Performance Data Sample Time Period drop-down list, select Last 1 day.

12. Click Go. The table displays the number of invoked services for each user in the last day. If needed, view other types of performance data in the Performance Section, such as Session Service or Session Duration.

A.1.12 Step 11: Viewing the User Service Log

The User Manager enables you to view the service activity log for a given user. To view an activity log:

1. From the Webtool, select the User Manager tab. The User screen appears, displaying a list of current users.

2. From the list of users, select TestUser.

Click the View Service Log button. The User Manager displays the user service data screen, which lists all of the services invoked by TestUser over the previous day as follows:

Table A-1 Service Log Statistics

Element	Description
Service Name	The name of the service
Service ID	The OID of the service in the database.
Service Type	The type of object (folder, bookmark, link, or local module) accessed by the user..
Invocation Time	The time the user accessed the service.
Invocation Status	Whether Wireless successfully executed the service. 0 indicates that Wireless successfully launched the service; 1 indicates that Wireless failed to launch the service.

You can view the activity log for a specific period using the From Date and To Date fields. You can set starting and ending dates either by entering them in the fields in the yyyy-mm-dd format, or by picking them from the calendars. Click Go after you have completed entering the date range.

A.2 Creating an Async-Enabled Service

In this walkthrough, you make HelloMS an async-enabled master service. You will also configure and start the messaging server and async server processes so that you can invoke an async-enabled service through email.

To create this service, you must access Wireless Webtool as follows:

1. Log into the Wireless Webtool using orcladmin as your user name and then enter your password.

2. From the Wireless Webtool, select the Service Designer tab. The Browse Folders screen of the Service Designer appears.

Each section in this walkthrough describes a step for creating an async-enabled services. These steps include:

• Section A.2.1, "Step 1: Enabling HelloMS as an Async Service"

• Section A.2.2, "Step 2: Setting the Async Parameters for HelloService"

• Section A.2.3, "Step 3: Configuring the Messaging Server with the Email Driver"

• Section A.2.4, "Step 4: Configuring the Driver Instance Configuration"

• Section A.2.5, "Step 5: Starting the Messaging Server"Chapter A.2.6, "Step 6: Configuring the Async Server"

• Section A.2.7, "Step 7: Starting the Async Server"

• Section A.2.8, "Step 8: Invoking an Async-Enabled Service"

• Section A.2.9, "Step 9: Viewing sys_panama.log and Performance Data from the Enterprise Manager"

• Section A.2.10, "Step 10: Viewing the User Async Log"

A.2.1 Step 1: Enabling HelloMS as an Async Service

To make HelloMS into an async service:

1. From the Browse Folder screen, click TestMSFolder to drill down to the browse screen for TestMSFolder.

2. Using the radio buttons, select HelloMS.

3. Click Edit. The Basic Info. screen of the Edit Master Service tool appears.

4. From the left menu, select Async Agent. The Async Agent screen appears.

5. Select Async-Agent Enabled.

6. In the Async Command Line Syntax field, enter Please invoke Hello Service by sending a message saying 'Hello <your name>.' This help text is sent to the user if the user issues an application help message (a 'help' command) to the Async Server.

7. Enter a semi-colon (;) as in the Delimiter field. Users use this delimiter to separate the input parameters in the messages they send.

8. Click Apply. The Browse screen for HelloMS reappears.

Note: See Section 10.3.3.6 in Chapter 10, "Developing Services" for information on creating async services.

A.2.2 Step 2: Setting the Async Parameters for HelloService

After you make an master async service with the Service Designer, you then use the Content Manager to set async parameters for the service based on the master async-enabled service.

To set the async parameters for a service:

1. Log into the Content Manager. The browse service screen appears for the services and folders at the root level.

2. Click TestFolder to drill-down to the service-browsing page for TestFolder.

3. From the service-browsing page for TestFolder, use the radio buttons to select HelloService.

4. Click Edit. The Edit service tool appears and defaults to the General screen.

5. From the left menu, click Async Service. The Async Service screen appears. The Delimiter, Async Command Line Syntax, and input fields are populated with the values set for HelloMS in the Service Designer. You do not have to edit these fields for this walkthrough.

6. Complete the Async Service screen as follows.
   1. Enter Hello in in the Short Name field. This is short command for invoking the service from the message sent by users.

   2. You do not have to enter a service-specific address. If you enter a service-specific address for each device, then the user does not need to enter the short name when invoking this async service from the device. For example, if you specify [e-mail] as the email address for HelloService, then the user can invoke this service by sending an email to [e-mail] without entering Hello as the short name in this query email. If the service-specific address is not specified, then the site-wide address is used instead. For the site-wide address, the user invokes HelloService by sending an email to the site-wide address (for example, [e-mail]) with Hello in the subject or body.

A.2.3 Step 3: Configuring the Messaging Server with the Email Driver

You use the Wireless part of the Oracle Enterprise Manger (OEM) to configure the messaging server with the email driver.

To configure the messaging server:

1. Click the Site tab.

2. Click messaging server in the process table. The Messaging server screen appears.

3. In the Configuration section, click Messaging Server Drivers. The Messaging Server Drivers screen appears.

4. Click Add Driver. The Add Driver screen appears. Enter only the values noted here; you do not have to enter values for fields not noted in these instructions.

5. Complete the Add Driver screen as follows:
   1. In the Driver Name field, enter TestEmailDriver.

   2. Select Email from Delivery Category.

   3. From the Speed Level drop-down list, select 3.

   4. From the Cost Level drop-down list, select 1.

   5. From the Capability drop-down list, select BOTH.

   6. Enter 1 in the Number of Message Queues field.

6. In the Driver Class Name field, enter oracle.panama.messaging. transport.driver.email.EmailDriver.

7. Click Add Another Row to add a row for each of the following parameters:
   • server.incoming.protocol

   • server.incoming.host

   • server.incoming.receiverfolder

   • server.incoming.usernames

   • server.incoming.passwords

   • server.incoming.emails

   • server.incoming.checkmailfreq

   • server.incoming.autodelete

   • server.incoming.deletefreq

   • server.outgoing.host

   • default.outgoing.from.address

8. Click Create.

A.2.4 Step 4: Configuring the Driver Instance Configuration

To configure the Messaging Server:

1. Click the Wireless Server Tab. The Server screen appears.

2. Click Messaging Server in the process table.

3. The Messaging Server Processes screen appears.

4. Enter TestEmailServer.

5. Click the Add button. TestEmailServer is added into the Messaging Server process table.

6. Click TestEmailServer (or select it and click View Details). The overview screen for the process appears.

7. In the Configuration section, click Driver Instance Configuration. The Driver Instance Configuration screen appears.

8. Click Add Driver Instance. The Add Driver Instance screen appears.

9. Complete the Add Driver Instance screen as follows:
   1. Enter TestEmailDriverInstance in the Driver Instance Name field.

   2. From the Driver Name drop-down list, select TestEmailDriver.

   3. Click Go.

   4. In the Number of Sending Threads field, enter 2.

   5. In the Number of Receiving Threads field, enter 2.

   6. In the Driver Specific Parameter fields, enter the following values:

      Table A-2 Values for Driver Specific Parameters

      For This Parameter Name...	Enter this Value
      server.incoming.protocol	IMAP
      server.incoming.host	gmmailt.oraclecorp.com (Replace this with your incoming mail server.)
      server. incoming.receivefolder	INBOX
      server.incoming.usernames	demo This is a list of all the email accounts you use for Site-Wide Addresses and Service-Specific Server Addresses. Use a comma (,) to separate the email accounts in this list. For this example, you specify [e-mail] as the Site-Wide Address.
      server.incoming.passwords	demopass, (A list of the passwords for each email account listed in the server.incoming.usernames field with the same sequence.)
      server.incoming.emails	[e-mail], [e-mail] (list all of the site-level server address and server-level server addresses.)
      server.incoming.checkmailfreq	5
      server.incoming.autodelete	true (This enables the email driver to delete all of the processed messages in the inbox.)
      server.incoming.delete.freq	600
      server.outgoing.host	gmsmtp01.oracelcorp.com (Replace this with your outgoing mail server).
      default.outgoing.from.address	[e-mail]. (This is the email account that the driver uses as the default from address.)

10. Click Create.

Note: You must re-start the messaging server each time you change the driver-specific attributes.

A.2.5 Step 5: Starting the Messaging Server

To start the messaging server:

1. Log into the Wireless part of the Oracle Enterprise Manager as orcladmin.

2. Select the Wireless Server tab.

3. Select Messaging Server from the process table. The Messaging Server Processes screen appears.

4. Using the radio buttons, select TestEmail Server.

5. Click Start.

A.2.6 Step 6: Configuring the Async Server

To configure the async server:

1. Log into the Wireless part of the Oracle Enterprise Manager as orcladmin.

2. Select the Site tab.

3. In the Process table, click Async Server. The Async Server screen appears.

4. In the Configuration section, click Async Server Configuration. The Async Server Configuration screen appears.

5. Use the default values fo the Async commands in the Command Format Section of the Async Configuration screen. The default values are as follows:
   • Help Command: The command in a message from the user that invokes a general help menu.

   • Application Help Command: If a user sends in a message as 'help hello', then the Async Server returns the help line for HelloServer, which is Please invoke Hello Service by sending a message saying,'Hello <your name>'.

   • Escape Command: Enables users to abort the current service and start a new one by entering the short name of the new service and parameter after the escape command.

   • Stop Command: Indicates the end of the current command input. The async server ignores all text after the stop command. (A blank line also indicates the end of the current command input).

   • Login Command: Enables users to login to their accounts.

   • Logoff Command: Enables users to logoff of their accounts.

   • Command Line Delimiter: Separates commands when multiple commands are entered onto one line.

6. In the Site-Wide Address section, enter [e-mail] (replace this with a valid email account on your email server). This address is included in the server.incoming.emails list of the EmailDriverInstance. See Section A.2.4 for more information. You do not need to enter a value in the SMS Address field.

   For this walkthrough, you do not have to enter a value in the Default Service field. If needed, you can enter the name of the default service invoked if the message sent by the user does not specify a short name for a service.

7. Click OK.

A.2.7 Step 7: Starting the Async Server

To start the async server:

1. Log into the Wireless part of the Oracle Enterprise Manager as orcladmin.

2. Drill down to OC4J page.

3. Start the Wireless Server product group.

A.2.8 Step 8: Invoking an Async-Enabled Service

To invoke an async-enabled service:

• Send an email to [e-mail] (or to the value you entered as the site-wide server address). In the Subject line, enter Hello. After you send this message, you receive a message asking you to enter a user name. Reply to this email and enter your name in the body of the email. You then receive another email saying, "Oracle9iAS Wireless says hello <your name>."

A.2.9 Step 9: Viewing sys_panama.log and Performance Data from the Enterprise Manager

To view the sys_panama.log:

1. From the Wireless part of the Oracle Enterprise Manager, click the Wireless Server tab. The Wireless Server screen appears.

2. From the Runtime section, click System Log Files. The System Log Files screen appears, displaying all of the files in the log directory.

3. Find sys_panama.log.

4. Click the eyeglass icon in the same row. A viewing screen appears for sys-panama.log. The log file appears in the text pane.

5. Click Printable Page. The log file appears in full-screen view, which enables you to easily print the log file.

6. To exit the Printable Page screen, click your browser's back button.

7. Click the Wireless Server tab. The Wireless Server screen appears.

8. In the Process table, click the Async Server process. The Async Server processes screen appears.

9. Click the Async Server process. The overview screen for that process appears.

10. In the Performance section, click Service Access Count Today. The Service Access Count Today screen appears. The table displays the number of async-enabled services for the day. Clicking other links, such as Average Message Queue Time Today, enables you to view other performance metrics for the async server.

A.2.10 Step 10: Viewing the User Async Log

The User Manager enables you to view the async service activity log for a given user. To view an activity log:

1. From the Webtool, select the User Manager tab. The User screen appears, displaying a list of current users.

2. From the list of users, select TestUser.

3. Click the View Async Log button. The User Manager displays the user async service data screen, which lists all of the async services accessed by TestUser over the previous day as follows:

   Table A-3 The Async Log

   Element	Description
   Short Name	The name of the async service (for example, ST for a stock quote service).
   ID	The OID of the async agent service in the database.
   Device Address	The address of the user's device receiving the alert.
   Server Address	The address of the async service.
   Delivery Type	The delivery type for the async service (for example, SMS).
   Receiving Time	The time the async agent engine received the request.
   Error Description	A message describing how Wireless failed to respond to the async service.

You can view the activity log for a specific period using the From Date and To Date fields. You can set the starting and ending dates, either by entering them in the yyyy-mm-dd format, or by selecting the appropriate days from the calendars. Click Go after you enter the date range.

A.3 Creating and Receiving an Alert

This walkthrough illustrates the creation of an alert service that sends stock quotes. Using this walkthrough, you will learn how to configure and start a data feeder process and the alert engine. This walkthrough also guides you through the user experience of registering a device and subscribing to an alert.

Each section of this walkthrough describes a step for creating or receiving an alert. These sections include:

• Section A.3.1, "Step 1: Creating a Data Feeder from a Static File"

• Section A.3.2, "Step 2: Creating a Master Alert"

• Section A.3.3, "Step 3: Publishing the Master Alert as an Alert"

• Section A.3.4, "Step 4: Configuring the Messaging Server with the Email Driver"

• Section A.3.5, "Step 5: Configuring the Driver Instance Configuration."

• Section A.3.6, "Step 6: Starting the Messaging Server"

• Section A.3.7, "Step 7: Configuring and Starting the Data Feeder Process"

• Section A.3.8, "Step 8: Configuring and Starting an Alert Engine Process"

• Section A.3.9, "Step 9: Registering a Device and Subscribing to StockAlert"

• Section A.3.10, "Step 10: Viewing sys_panama.log and Performance Data from the Enterprise Manager"

• Section A.3.11, "Step 11: Viewing the User Alert Log from the User Manager"

A.3.1 Step 1: Creating a Data Feeder from a Static File

Copy $ORACLE_HOME/wireless/sample/stock.csv to /tmp/stock.csv. This file has a table of stock quotes as follows:

Table A-4 $ORACLE_HOME/wireless/sample/stock.csv

Stock Symbol	Current Price	% Change	Closing Price	High Price	Low Price	Volume
MOT	14.26	-0.02	14.51	14.6	14.1	4605100
CSCO	19.73	0.88	19.08	19.81	19.01	52400100
IFMX	5.13	0.09	5.1	5.18	4.92	2644600
SEBL	46.8	0.92	47.51	47.51	45.11	8816800
A	33.5	-0.47	34	34.19	33.3	1579000
B	21.93	0.68	21.24	21.93	21.24	14700
C	52.28	0.48	52.15	52.3	51.2	10872700
ETYS	0	0	0	0	0	0
ARBA	5.85	-0.02	6.05	6.1	5.76	3005600
TIBX	13.93	0.35	13.675	14.59	13.64	2351400
IBM	9.21	0.05	9.26	9.43	9.13	470900
METG	2.65	-0.07	2.7	2.75	2.65	249400
ERICY	6.22	0.02	6.235	6.36	6.19	6081900
EXDS	7.9	-0.09	8.16	8.17	7.81	3263700
LBRT	7.92	-0.55	8.565	8.6	7.92	398800
NUAN	15.65	-0.85	16.455	16.96	15.57	675000
YHOO	20.78	0.32	20.46	20.5	19.53	12081700
T	21.26	-0.23	21.6	21.75	21.08	7660000
SQST	1.54	-0.07	1.61	1.62	1.5	76300
ASFD	0.3	0.02	0.305	0.31	0.29	50200
TTWO	20.55	-0.35	20.955	21.12	20.1	795900
LUMT	0.58	-0.07	0.61	0.62	0.58	170400
ILUM	32.34	-0.22	32.5	32.66	32.01	325500
BBSW	1.93	-0.13	2.06	2.09	1.92	368300
CMRC	6.64	-0.06	6.83	6.9	6.55	2092300
NEOF	0.86	-0.01	0.875	0.93	0.86	653200
SUNW	16.08	-0.55	16.781	17	16.04	24525600
PALM	6.25	0.06	6.34	6.49	6.2	14666500
KANA	1.98	-0.08	2.05	2.09	1.93	849500
USIT	0	0	0	0	0	0
BVSN	6.5	0.09	6.67	6.74	6.45	3327800
LU	8	0.01	8.06	8.07	7.76	11512000
FLPSX	26.72	0.24	0	0	0	0
RHAT	5.26	-0.08	5.48	5.5	5.21	671700
SDLI	0	0	0	0	0	0
DJIND	0	0	0	0	0	0
WBVN	0.17	0.02	0.18	0.19	0.16	6160900
TRRA	0	0	0	0	0	0
ORCL	28.06	0.2	16.53	16.54	15.93	34347900
MSFT	70.78	0.44	70.55	71.028	69.8	21534300
NVGP	0	0	0	0	0	0
RIMM	35.4	-0.29	36.21	36.78	34.85	1881400
CORL	2.51	-0.01	2.555	2.59	2.45	528800
WB	68	-0.26	68.36	68.47	67.61	1196700
FQYXD	0	0	0	0	0	0
FNSR	15.93	-0.88	17.05	17.14	15.85	1988900
MSQJJ	0	0	0	0	0	0
DL	14.35	0.31	13.95	14.5	13.95	136800
PCS	22.61	0.9	21.72	22.8	21.5	4583200
COMS	5.55	-0.18	5.71	5.88	5.53	1852100
CLGY	6.48	-0.02	6.1	6.48	6	15300

A.3.1.1 Creating the Data Feeder

In this step, you use the Data Feeder Creation Wizard in the Service Designer to create a data feeder that retrieves the stock information from the stock.csv file and feeds it to a master alert.

Entering the Basic Information for the Data Feeder

To create the data feeder:

1. Log into the Webtool as orcladmin.

2. Select the Service Designer tab.

3. Select the Data Feeder subtab. The data feeder browsing screen appears.

4. Click Create Data Feeder. The Basic Info. screen, the first screen of the Data Feeder Creation Wizard appears.

5. Complete the Basic Info. screen as follows:
   1. Enter StockDF in the Name field.

   2. Select Regular. (You select the Regular option since this data feeder uses the built-in data retrieval frame work to collect data and push it to an alert engine. You select Pass-Through if you specify an external application that pushes data to an alert engine.)

   3. From the Protocol Type drop-down list, select File since this data feeder retrieves its content for the alert from stock.csv file.

   4. From the Format Type drop-down list, select Delimited since stock.csv is a comma-separated file.

   5. You do not have to enter a value into the Data Filter Hook field. You use this field to specify a filter hook for additional customization of the data filter, such as filtering out content data before feeding the data to the content cache table.

   6. You do not have to enter a value into the Download Hook field. You use this field to customize the data feeder to download data from a special URL.

   7. You do not have to enter a value into the Null Value field. You use this field to mark inapplicable data using such conventions as N/A.

   8. Select 6:00 am as the start time.

   9. Select 1:00 pm (1300) as the end time.

   10. Select 60 seconds as the update interval. This is the interval in which the data feeder fetches data from the data source, stock.csv.

   11. In the Batch Size field, enter 30. This instructs StockDF to download 30 rows of data from stock.csv during each interval.

   12. Select Workdays as the days designated for updating the data.

6. Click Next. The Init Parameters screen appears.

Entering the Init Parameters for the Data Feeder

Enter the init parameters for StockDF as follows:

1. In the File Path field, enter /tmp/stock.csv

2. Enter a comma (,) in the Delimiter field.

3. You do not have to enter a value into the Quote Char field. You use this field to specify a special character that represents a quote in the data source.

4. Click Next. The Input Parameters screen appears.

Entering the Input Parameters for the Data Feeder

Enter the input parameters for the data feeder as follows:

1. Click Add Another Row.

2. Complete the fields as follows:
   1. Enter symbol in the Internal Name field. This name is used within the Wireless server both by the master alert and the alert.

   2. From the Data Type drop-down list, select TEXT_80. This is the data type for the table column when creating a subscription table.

   3. You do not have to enter a value in the External Name because this parameter does not apply to a data feeder using the File protocol.

   4. Enter 1 in the Return Content Column Number field. (The stock ticker symbol is in the first column of the stock.csv file.)

   5. Enter Ticker in the Caption field. End users see this caption when they subscribe to the alert.

   6. You do not have to enter a value into the Default Value field. Values entered into this field are the default value if an end user does not supply a value.

3. Click Next. The Output screen appears.

Entering the Output Values for the Data Feeder

To enter the output values for the data feeder:

1. Click Add Another Row.

2. Complete the fields as follows:
   1. Enter Price in the Internal Name field. This name is used within the Wireless Server by both the master alert and the alert.

   2. From the Data Type drop-down list. select NUMBER. This is the data type for the table column when creating the subscription table.

   3. Enter 2 in the Column Number field. (The stock prices are in the second column of the stock.csv file.)

   4. Enter Price in the Caption field. End users see this label when they subscribe to the alert service.

3. Click Add Another Row and complete the fields as follows:
   1. Enter Change in the Internal Name field.

   2. From the Data Type drop-down list, select NUMBER.

   3. Enter 3 in the Column Number field. (The change in stock prices is in the third column of the stock.csv file).

   4. Enter Change in the Caption field.

4. Click Finish. The data feeder browsing screen reappears, displaying StockDF in the table.

Note: See Section 10.5 in Chapter 10, "Developing Services" for information on data feeders. For information on data feeder semantics, see Oracle9iAS Developer's Guide.

A.3.2 Step 2: Creating a Master Alert

After creating the StockDF data feeder, you can create a master alert.

1. Log into the Webtool as orcladmin.

2. Select the Service Designer tab.

3. Select the Master Alert subtab. The browsing screen for master alerts appears.

4. Click Create Master Alert. The Basic Info screen of the Master Alert Creation Wizard appears.

Entering the Basic Information for a Master Alert

To enter the basic information of the master alert:

1. Enter StockMA in the Name field.

2. In the Description Field, enter Stock Master Alert.

3. From the Data Feeder drop-down list, select StockDF (the data feeder you created in Step 1).

4. You do not have to enter a value into the Subscriber Filtering Hook. This hook enables you to filter out some subscribers for the qualified alerts before these alerts are sent to the messaging server.

5. Select the Time-Based Enabled check box. This option enables the end user to specify the time for the alert to be sent.

6. Click Next. The Trigger Conditions screen appears.

Setting the Trigger Conditions for the Master Alert

To enter the trigger conditions for the master alert:

1. Click Add Another Row.

2. Complete the fields as follows:
   1. Enter PriceMax in the Condition Name field. End users see this label when the subscribe to an alert service.

   2. Select price in the Trigger Parameter field. This condition is set for the output parameter price.

   3. From the Condition Type drop-down list, select Greater Than. By selecting this condition type, you create a master alert that is triggered when the stock price rises above the subscription value entered by users.

   4. You do not need to enter a value in the Default Value field. This field specifies the default value of PriceMax if users do not enter a value.

3. Click Add Another Row and complete the fields as follows:
   1. Enter PriceMin the in the Condition Name field.

   2. Select price in the Trigger Parameter field.

   3. From the Condition Type drop-down list, select Less Than. Selecting this option creates a master alert that is triggered when the stock price falls below the subscription value entered by users.

4. Click Add Another Row and complete the fields as follows:
   1. Enter Change in the Condition Name field.

   2. Select change in the Trigger Parameter field.

   3. Select Greater than Absolute Value from the Condition Type drop-down list. By selecting this condition type, you create a master alert that is triggered when the absolute value of the percentage of the change in the stock price is greater than the subscription value entered by users.

   4. You do not have to enter a value in the Default Value field.

5. Click Next. The Message Template screen appears.

Creating the Message Template for the Master Alert

Complete the Message Template screen as follows:

1. Select XML Template.

2. Enter the following template for formatting the alert message that Wireless sends the end user:

   <SimpleText>
    Stock Alert for &symbol;
    Price: &price;
    Change: &change;
   </SimpleText>
   
   

3. Click Submit. The browsing screen for master alerts reappears, displaying StockMA in the master alert table.

Note: See Section 10.4 in Chapter 10, "Developing Services" for information on creating master alerts.

A.3.3 Step 3: Publishing the Master Alert as an Alert

In this step you use the Content Manager to publish the master alert, Stock MA, to user groups as an alert.

1. Log into the Webtool as orcladmin.

2. Select the Content Manager tab.

3. Select the Alert subtab. The browsing screen for topics and alerts appears.

4. Click Add SubTopic. The New Topic screen appears.

5. In the Topic Name field, enter TestTopic. Click Finish. The browsing screen reappears, displaying TestTopic.

6. Click TestTopic. The browsing screen for TestTopic appears.

7. Click Add Alert. The General screen of the Alert Creation Wizard Appears.

Entering the General Information of an Alert

To enter the general parameters of an alert:

1. Enter StockAlert in the Alert Name field.

2. In the Description field, enter Alert for Stock Price.

3. Click Next. The Master Alert screen appears.

Selecting a Master Alert

To select a master alert:

1. Using the radio buttons, select StockMA.

2. Click Next. The Input Parameters screen appears.

Setting the Input Parameter for the Alert

There is a one input parameter defined by the data feeder, symbol. To set this input parameter:

1. In the Caption field, enter StockTicker.

2. You do not have to enter a value in the Value field. Leaving this field blank instructs the user to enter a value.

3. Click Next. The Trigger Condition Screen appears.

Setting the Trigger Conditions for the Alert

To set the trigger conditions for the alert, enter the following captions for the three trigger conditions, Change, PriceMax, and PriceMin. You do not have to enter any values in the Value fields for these trigger conditions.

1. Enter Change in the Caption field for Change.

2. Enter PriceMax in the Caption field for PriceMax.

3. Enter PriceMin in the Change field for PriceMin.

4. Click Submit to complete the alert. The browsing screen for TestTopic reappears, displaying StockAlert.

Publishing the Alert to a User Group

To publish StockAlert to a user group:

1. Click the Groups tab. The Groups screen appears.

2. Select TestGroup using the Select radio button.

3. Click Assign Alert. The Alert Content of TestGroup appears. The top table lists the topics and alerts that TestGroup can currently access. The bottom table list the all of the existing alerts and topics in the repository.

4. Select TestTopic using the check box in the Select column.

5. Click Add to Group. TestTopic appears in the top table, as it can now be accessed by TestGroup.

6. Click Finish button. The Groups screen reappears.

Note: See Section 11.5 in Chapter 11, "Managing Content" for information on creating alerts.

A.3.4 Step 4: Configuring the Messaging Server with the Email Driver

See Section A.2.3 for information on configuring the messaging server with the email driver.

A.3.5 Step 5: Configuring the Driver Instance Configuration.

See for Section A.2.4 for information on configuring the driver instance.

A.3.6 Step 6: Starting the Messaging Server

See Section A.2.5 for information on starting the messaging server.

A.3.7 Step 7: Configuring and Starting the Data Feeder Process

To configure a data feeder process:

1. Log into the Wireless part of the Oracle Enterprise Manager as orcladmin.

2. Select the Wireless Server tab. The Server screen appears.

3. From the processes table, click the Data Feeder hyperlink. The Data Feeder Processes table appears.

4. In the Process Name field, enter StockDataFeeder.

5. Click Add. StockDataFeeder appears in the process table.

6. Click StockData Feeder. The overview screen for StockDataFeeder appears.

7. From the Data Feeder Name drop-down list, select StockDF.

8. Click Add. StockDF appears in the Data Feeders table.

9. In the General section, click the Start button.

Note: See Section 3.2.2 in Chapter 3, "Server Administration" for information on configuring and starting a data feeder process.

A.3.8 Step 8: Configuring and Starting an Alert Engine Process

To configure and start an alert engine process:

1. Log into Wireless part of the Oracle Enterprise Manager as orcladmin. Select the Wireless Server subtab.

2. From the process table, click the Alert Engine hyperlink. The Alert Engine processes screen appears.

3. Enter StockAlertEngine in the Process Name Field.

4. Click Add. StockAlertEngine appears in the alert processes table.

5. Click StockAlertEngine. The overview page for StockAlertEngine appears.

6. From the Master Alert Name drop-down menu, select StockMA.

7. Click Add. StockMA appears in the Alert Engine table.

8. In the General section, click Start.

Note: See Section 3.2.1 in Chapter 3, "Server Administration" for more information on starting and stopping an alert engine process.

A.3.9 Step 9: Registering a Device and Subscribing to StockAlert

To register a device:

1. Log into the Wireless Customization as TestUser.

2. Enter 1234 as the password.

3. Select the Devices tab. The Device screen appears.

4. Create a new device by completing the screen as follows:
   1. Enter MyEmail in the Device Name field.

   2. Enter [e-mail] in the Address field. (You can replace this value with your email address.)

   3. From the drop-down list in the Device Type field, select Email.

   4. Enter SpintPCS in the Carrier field. (You can replace this value with your email carrier.)

   5. Enter Timeport in the Model field. This is the name of the model. (You can replace this value with your phone model.)

   6. Enter 10 in the Maximum Alerts to Send per Day field. Wireless sends a maximum number of ten alerts per day to this device. You will not receive any alerts from this device if you enter 0 (zero) in this field, or if you leave this field blank.

   7. Select the Default check box to make this the default device.

5. Click Create. MyEmail appears in the device list. This device is not yet validated, so Wireless notes its validation status as false.

   After you complete a device, Wireless Customization sends an eamil with the subject line, Validation Number to the address entered in Step 3b ([e-mail]). The message reads, <number> is the validiation number for MyEmail. To receive alerts, you must validate this device using the validation number that you received in this email message.

Validating MyEmail

To validate MyEmail:

1. From the Device list, select MyEmail.

2. Click Validate. The Validate screen appears.

3. Enter the validation number noted in the email sent from Wireless Customization in the Validation Number field. The Device screen reappears. The Validation column in the device list displays "true" for MyEmail. MyEmail is now validated and can receive alerts.

Subscribing to an Alert Service

To subscribe to an alert service:

1. Select the Alert tab. The Alert Subscription screen appears.

2. Expand AlertTest. StockAlert appears under AlertTest.

3. Click StockAlert. The Alert Subscription screen for StockAlert appears.

4. Complete the New Subscription section for the Alert Subscription screen as follows:
   1. Enter MySubscription in the Alert Subscription Name field.

   2. Enter ORCL inthe StockTicker field.

   3. Enter 1 in the Change field.

   4. Enter 26 in the PriceMax field. This condition should be satisfied, since the price of ORCL is 33.06 in the stock.csv file).

   5. Enter 20 in the PriceMin field.

   6. Enter 03/31/02 in the Expiration Date field. (After March 31, 2002, this alert subscription becomes invalid.)

   7. In the Frequency field, enter Weekday, so that this subscription is processed only on weekdays.

   8. Enter 9 in the Hour field, so that this alert is processed only at 9:00 am in your time zone.

   9. You do not have to enter a value in the Minutes field. Leaving this filed blank enables the alert to be processed at 9:00 am, sharp.

5. Click Create. MySubscription appears in the Trigger Conditions table. With this subscription information completed, Wireless will send an alert to [e-mail] at 9:00 am of the next workday

A.3.10 Step 10: Viewing sys_panama.log and Performance Data from the Enterprise Manager

See Section A.2.9 for more information.

A.3.10.1 Viewing the Performance Metrics for a Data Feeder Process

To view the performance metrics of a data feeder process:

1. Select the Wireless Server tab.

2. In the process table, select Data Feeder. The Data Feeder Processes screen appears.

3. Click StockDataFeeder. The overview screen for that process appears.

4. In the Performance section of the screen, click Data Downloaded Rows. The Data Downloaded Row screen appears, displaying the number of data feeder downloads today for each data feeder for this process.

A.3.10.2 Viewing the Performance Metrics for an Alert Engine Process

To view the performance metrics of an alert engine process.

1. Select the Wireless Server tab.

2. In the process table, select Alert Engine. The Alert Engine Processes screen appears.

3. Click StockAlertEngine. The overview screen for that process appears.

4. In the Performance section of the screen, click Number of Alerts Sent Today. The Alert Performance Today screen appears, displaying the total number of alerts sent per alert service for today. You can also view such other performance statistics as Number of Alerts Sent Last Hour and Number of Subscribers Notified today by clicking the links in the Performance section.

A.3.11 Step 11: Viewing the User Alert Log from the User Manager

The User Manager enables you to view the service activity log for a given user. To view an activity log:

1. From the Webtool, select the User Manger tab. The User screen appears, displaying a list of current users.

2. From the list of users, select Test User.

3. Click the View Alert Log button. The User Manager displays the View User Alert Log screen, which lists all of the alerts sent to TestUser over the previous day as follows:

   Table A-5 Alert Log Statistics

   Element	Description
   Alert Name	The name of the alert.
   Alert ID	The OID of the alert in the database.
   Device Address	The address of the user device receiving the alert.
   Device Type	The type of logical device receiving the alert (for example, WAP-Push, SMS, or Email).
   Dispatch Time	The time Wireless sent the message.
   Message Status	Whether Wireless successfully sent the message. 0 indicates that Wireless successfully sent the message; 1 indicates that Wireless failed to send the message.

You can view the activity log for a specific period using the From Date and To Date fields. You can set starting and ending dates either by entering them in the fields in the yyyy-mm-dd format, or by picking them from the calendars. Click Go after you have completed entering the date range.