Oracle Portal-to-Go Implementation Guide Release 1.0.2.2 A86635-02 |
|
This document discusses the Portal-to-Go architecture. It introduces the components of Portal-to-Go, and how you can configure them. Topics include:
Portal-to-Go consists of server and client components. The client components include tools for developing, managing, and monitoring the Portal-to-Go server. The Portal-to-Go Service Designer, for example, is a visual interface for developing and maintaining Portal-to-Go objects. The Portal-to-Go objects include users, services, adapters, and transformers.
The Portal-to-Go server performs the primary tasks associated with acquiring and delivering mobile services; it receives user requests, and adapts and transforms content.
The Portal-to-Go server has the following architecture for acquiring and delivering content:
Portal-to-Go runs on the Oracle9i Application Server. It uses Oracle8i for its persistent object storage. When you implement Portal-to-Go, you primarily create and manage the repository objects, and establish relationships between them.
The Portal-to-Go repository contains the following types of objects:
Portal-to-Go supports system-wide extensibility using property files. Each property file stores runtime parameters and processing information for a Portal-to-Go component. Portal-to-Go property files are named with the extension .properties.
Property files enable you to plug in new components easily, or extend and configure existing ones. For example, the stripper adapter, which acquires and converts arbitrary Web content, reads configuration settings from the Strip.properties file. It uses the settings in the file to locate classes that process the markup tags in content. Each processing class implements a strip level for the adapter. To add a strip level, you create the class that implements the strip level and reference it in Strip.properties. This makes the strip level available to the adapter, without requiring you to make changes to the stripper adapter class.
Portal-to-Go includes many property files. The System.properties file contains configuration settings for the entire Portal-to-Go system. The following table lists several other property files you can use to configure Portal-to-Go.
These files are located in subdirectories of the following directory:
PortaltoGo_Home/server/classes/oracle/panama/core
The Portal-to-Go system configuration file, System.properties, contains parameters and component locators for the entire Portal-to-Go system. To start Portal-to-Go, you must have this file in the class package oracle.panama.core.admin
. This package must be in the environment CLASSPATH.
The System.properties file contains the following parameters:
Portal-to-Go generates logging information for both the server and development client components.
By default, the Service Designer writes error information to the log directory of your Service Designer home directory. You can modify this setting, and the log naming pattern, in the preferences.xml file, which is located in the ServiceDesigner/resources directory.
Portal-to-Go writes server error information to the files and directory specified in the System.properties file. You can open the log files directly, or view them from the Portal-to-Go Runtime Information and Management interface (the Probe interface) at port 8090. Click the "Files" link.
Portal-to-Go specifies these types of errors:
Error | Value |
---|---|
ERR_SERVICE_UNAVAILABLE |
PTG-001 |
ERR_SERVICE_ERROR |
PTG-002 |
ERR_SERVICE_NOT_FOUND |
PTG-003 |
ERR_CONFIGURATION_ERROR |
PTG-004 |
ERR_INTERNAL_ERROR |
PTG-005 |
ERR_DATABASE_ERROR |
PTG-006 |
In addition to error messages, Portal-to-Go provides extensive runtime exception logging. When fatal exceptions occur, Portal-to-Go logs the exceptions and stack traces in the global log file. If you need to contact Oracle Support Services, you should have the log information available.
The transaction log is a log file on the Portal-to-Go server that provides information regarding user access. To enable transaction logging, you must include transaction logging as a log level in the System.properties file. For example:
log.level=Warning, Error, Notify, Transaction
You can also use the System.properties file to set the directory to which Portal-to-Go writes transaction logs, and to specify a file name pattern for the log files. You can also configure the transaction record pattern.
If you enable transaction logging, when a user accesses a service that has a cost value set, the transaction log generates data. You can set a cost for a master service using the Portal-to-Go Service Designer. You can access the transaction log data programmatically, to generate billing information or to integrate Portal-to-Go transaction information with an external billing management system.
The following sample shows the log results of four stock quote queries by a single user. The sample uses the default logging pattern, which you can modify in the System.properties file. It lists the time of access, the user name (Sample), the service, and the price per access (25):
[11/14/99 4:03:26 PM] Sample /master/OnlineQuoteYahoo 25 [11/14/99 4:03:29 PM] Sample /master/OnlineQuoteYahoo 25 [11/14/99 4:03:35 PM] Sample /master/OnlineQuoteYahoo 25 [11/14/99 4:04:43 PM] Sample /master/OnlineQuoteYahoo 25
|
Copyright © 2000 Oracle Corporation. All Rights Reserved. |
|