|
Oracle® Application Server 10g Best Practices
10g (9.0.4) Part No. B12223-01 |
|
|
|
|
Oracle® Application Server 10g Best Practices
10g (9.0.4) Part No. B12223-01 |
|
|
|
|
This chapter describes best practices for Oracle Application Server Wireless (OracleAS Wireless). It includes the following topics:
It is often necessary to deploy Wireless and Voice applications in a high-volume environment where the number of transactions may exceed the capacity of a single Oracle Application Server 10g middle-tier that is associated with an OracleAS Infrastructure 10g. To determine if you need additional middle-tiers for your enterprise, consult sizing information that is available under the Mobile section of OTN (http://otn.oracle.com).
Since the Device Portal requests usually by far exceed the Customization and Webtool requests, you may want to shut down some OC4J_Portal instances on some of your Oracle Application Server middle tiers. Shut down the instances in proportion to the request ratio. This will free up resources for OC4J_Wireless instances on the middle tiers. However, consider if you will need any Oracle Application Server applications deployed in OC4J_Portal to be available on all middle tiers.
Refer to the Oracle Application Server 10g Administrator's Guide for more information on deploying multiple tiers.
A typical OracleAS Wireless request starts from a device to a WAP gateway. The gateway issues an HTTP request for the content to Oracle HTTP Server, which in turn issues an AJP request to the OC4J container. The Wireless application in the container then issues a corresponding HTTP request to a content source. Since these entities may be deployed on separate computers, it is necessary to ensure that the Firewall settings in a DMZ permit these protocols to pass through.
Content sources, that is, applications or pages that output XHTML or mobile XML, should be deployed in a JVM other than OC4J_Portal or OC4J_Wireless. You may also consider dedicating a separate instance of the application server if your content source is implemented using Oracle Application Server.
Applications written in Oracle Application Server presentation independent XML can be delivered:
to any telephone, either local or wireless
by audio playback of information
by a voice-enabled user interface
In the same way that SMS or WAP applications running on OracleAS Wireless can utilize gateways from multiple vendors, Oracle Application Server voice applications can also run on any Oracle-accepted VoiceXML gateway.
The voice gateways include:
a VoiceXML interpreter
speech recognition (ASR) or text-to-speech (TTS or synthetic speech) software
telephony interface cards such as Dialogic, NMS, or AudioCodes
For a list of Oracle-accepted Voice Gateways, refer to the Partner Solutions section under the Mobile section of OTN (http://otn.oracle.com).
