Oracle Application Server Wireless Developer's Guide 10g (9.0.4) Part Number B10948-01 |
|
Each section of this document presents a different topic. These sections include:
This chapter introduces OracleAS Wireless Mobile Studio. Mobile Studio is a completely online, hosted environment for developing, testing and deploying mobile applications for the OracleAS Wireless platform. It also serves as a Web portal, supporting the wireless developer community in the enterprise and on the Internet.
Mobile Studio offers developers a simple, intuitive and easy-to-use Web-based user interface to facilitate rapid configuration, testing and deployment of wireless applications. Developers do not need to download or install anything on their workstations; all they need is a Web browser and access to Mobile Studio. Once an application is registered with Mobile Studio, developers can test it using any mobile device or simulator (including voice). They can instantly access real-time logs to troubleshoot any issues. Once the application is tested, developers can deploy it to a production server with the click of a button.
Service providers can easily brand Mobile Studio (customizing its look-and-feel and content), and integrate it with their existing website. Mobile Studio can serve as an interactive development tool, a one-stop shop for up-to-date information and collateral on the OracleAS Wireless server platform, and service deployment portal for third-party content providers. This makes it easy for service providers to support their developer community and attract new developers.
Mobile Studio includes the following major features:
For application providers:
Visit Mobile Studio hosted on the Oracle Technology Network (http://www.otn.oracle.com) for an example of how Mobile Studio can be branded and integrated into an existing website. Any developer, systems integrator or independent software vendor with access to the Internet can use this instance to quickly build and test mobile applications that are immediately accessible from any device. This unique environment allows companies to benefit from faster time to market, increased productivity and a dramatically simplified testing cycles.
Access the Mobile Studio main page at the following URL:
http://<studio_server>:<studio_port>/studio
where <studio_server> and <studio_port> are the name of the host and port number running the Mobile Studio instance. These are configured in the Oracle Installer during the installation process.
Note: Mobile Studio has been optimized for the latest versions of the popular Netscape and Internet Explorer browsers. Mobile Studio is not certified for Netscape 4.x or Internet Explorer 4.x. |
Mobile Studio is deployed configured for Single Sign-on (SSO). The user profile information (including user ID and password) is stored in an Oracle Internet Directory (OID) repository and is shared by all SSO-enabled applications.
All user accounts are created and managed in a central repository backed by the Oracle Internet Directory (OID) server. Once Mobile Studio has been configured for SSO; any user in the shared repository can log in with their single sign-on user ID and password and use Mobile Studio. New users must have their accounts created before they can enter Mobile Studio.
The first step in building an application for the OracleAS Wireless platform is to develop an application using your own tools in your own environment. The mechanism used to generate the presentation layer of your application is transparent to Mobile Studio; all of the dynamic page generation technologies (such as CGI, JSP, and ASP) are supported. The only requirements are:
Below is a simple "Hello World" application written in XHTML:
Once you have registered your application with Mobile Studio, you can test it using either an actual mobile device or device emulation software. Not only can Mobile Studio applications be accessed from any mobile device, but they can be accessed through multiple channels such as HTTP, Voice, and Messaging. Contact your Mobile Studio administrator for a list of valid access points (for example: URL for HTTP access, or a phone number for Voice access).
If you encounter errors (or if you are just curious), you can click the Log icon next to your application to see the real-time debug logs.
When you click the Log icon, log information appears in a new window.
After testing your application, you can deploy it on a production instance of OracleAS Wireless. In the My Studio home page, select the application you want to deploy and click Deploy. If the Deploy button is not available, contact your Mobile Studio administrator for details.
Mobile Studio can be customized in a variety of ways, allowing powerful integration with existing customer Web sites.
Mobile Studio ships with four sample services. Registered users of Mobile Studio may access these services and view their source code. These services were created to demonstrate how to develop mobile applications using various OracleAS Wireless features. To delete or edit existing sample services, see OracleAS Wireless Administrator's Guide. This following section details how to create a new sample service.
To create a sample service, you must first develop the application using XHTML or OracleAS Wireless XML. Be sure to host the sample service at a location that is accessible by Mobile Studio. You must also host a document that contains the source code of your application. The contents of this file are retrieved and embedded inside the body tag of an HTML document when users' choose to view the source code (that is, you may use HTML syntax to format this document).
Note: You must use the Mobile Studio Administrator's Tool to register the sample service you have created before it will be displayed in Mobile Studio. See OracleAS Wireless Administrator's Guide for instructions. |
In Mobile Studio, branding refers to the particular look and feel of a site. For example, the images (logos, borders, icons) used, and the textual content (font size, colors) of a page constitute the look and feel of a site. This section details how to perform such look-and-feel customizations by creating new brandings. If you require more advanced customizations (such as modifying the layout and flow of pages) see Section 6.3.4, "JSP Pages" and Appendix G, "JSP Tag Library".
Creating a new branding does not require coding in Java; brandings are defined using a declarative approach. Only knowledge of HTML is required to create a new branding.
To create a new branding:
Each branding must contain a file called site.properties. This file contains declarations for the textual and image resources used. For example, common.css.filename is a key inside this file that controls which the cascading style sheet (CSS) file used by Mobile Studio. The branding which ships with Mobile Studio includes property files for each supported locale. For example, the properties file site_fr.properties is used for the French (fr) locale.
The valid keys that may be declared in the site.properties file is controlled by the master file SiteResources.properties. If you require additional keys (usually for more advanced customizations), you can locate this file at $IASW_ROOT/wireless/server/classes/messages/oracle/panama/studio. You must restart the OracleAS Wireless Server for changes in this file to take effect.
Note: You must use the Mobile Studio Administrator's Tool to declare the branding that Mobile Studio should display (by default, Mobile Studio will display the branding included with Mobile Studio). See OracleAS Wireless Administrator's Guide for more information. |
The default branding included with Mobile Studio has bundled support for 28 locales. However, only the English locale (en) is enabled upon a fresh installation. To enable support for other locales, see OracleAS Wireless Administrator's Guide for detailed instructions.
If you want to support locales in a branding that you have created or want to support additional locales in the default branding, you must create resource files containing the relevant translations (see Section 6.3.2, "Branding" for information about branding directories).
For example, to create the locale for Hindi (hi):
Note: You must use the Mobile Studio Administrator's Tool to enable the locales that you want supported. See OracleAS Wireless Administrator's Guide for instructions. |
Mobile Studio determines which locale to display by examining the list of preferred locales originating from a request. The algorithm is similar to how Java loads Resource Bundles. English (en) is the default locale in a fresh installation.
This section lists the customization details of the major JSPs used in Mobile Studio:
Users trying to access other pages without logging in are redirected to this page, with an appropriate error message.
Note: In integrated mode, users log in (or self-register) with their OID username and password on a separate page. login.jsp is used only when Mobile Studio is running in standalone mode. |
A User performs the following actions from this page:
Text description of the illustration ms1.gif
User can register to Mobile Studio by filling in the registration form.
Note: In integrated mode, users log in (or self-register) with their OID username and password on a separate page. login.jsp is used only when Mobile Studio is running in standalone mode. |
This page is included to provide a form for the user to login.
Note: In integrated mode, users log in (or self-register) with their OID username and password on a separate page. login.jsp is used only when Mobile Studio is running in standalone mode. |
This page is included as a header for all the customer-facing JSPs.
This page is included as a footer for all customer-facing JSPs.
This page is included inside most pages to provide a common side bar for the user to browse.
This page is included in most of the JSPs. The default branding displays the following page portlets:
Name | Description | Example |
---|---|---|
page.portlets |
HTML included for page portlets |
Sites/default/samplepageportlets.html |
Users can view and edit their profile in this page.
This is the main page for users; it is the first page that users see after logging in.
Users can perform the following actions from this page:
This page is included where there are instructions for testing user applications. It is included in the home.jsp and samples.jsp pages.
|
![]() Copyright © 2003 Oracle Corporation. All Rights Reserved. |
|