Description Syntax Example configurePortalPageEngine

12-6 Oracle Fusion Middleware WebLogic Scripting Tool Command Reference

12.2.2.1 Description

The Oracle Fusion Middleware Portal architecture is designed around a three-tier architecture that allows any browser to connect to it. This flexible architecture allows each component browser, Oracle HTTP Server listener, Oracle Database 11g, and Oracle Portal to be upgraded individually as required. A part of the Oracle Portal middle tier, the Parallel Page Engine PPE is a servlet that runs under Oracle Containers for J2EE and services page requests. The PPE reads page metadata, calls providers for portlet content, accepts provider responses, and assembles the requested page in the specified page layout. This command updates the properties in the appConfig.xml file, the configuration file that is used by the Portal mid-tier repository servlet. This configuration file is located in the MWHOMEuser_projectsdomainsAllClassicDomainserversWLS_ PORTALstageportalportalconfiguration directory.

12.2.2.2 Syntax

configurePortalPageEngine[encrypt_key], [resource_url_key], [use_port], [use_ scheme], [x509certfile]

12.2.2.3 Example

The following example updates the Portal page engine based on the specified arguments. configurePortalPageEngineencrypt_key=encryption key,resource_url_ key=foo.oracle.com,use_port=9999,use_scheme=page_engine_1, x509certfile=file Argument Definition encrypt_key Optional. Specifies the HMCA key to obscure the headers used for caching using WebCache. This allows for a more secure cache key, and makes retrieving a cached object by unwanted requests more difficult. resource_url_key Optional. This key, used by the PPE servlet, calculates checksums for URLs that are requested by WSRP and JPDK resource proxying. For WSRP resource proxying to work, the key must be set to an alpha-numeric value of 10 characters or more. In addition, for JPDK proxying, a JNDI environment variable, also called resourceUrlKey, must be set for the provider. use_port Optional. Overrides the port used when the PPE makes requests to the portal. The default, if not specified, is to always use the page request port. Note that if you set useScheme, you must also set the usePort argument. This may be used for other reasons, but mostly it is used when SSL is running between the browser and the PPE but not between the PPE and Portal. In this case, the non-SSL port for loop back requests will be different from the SSL port used by the browser. use_scheme Optional. Overrides the scheme HTTP or HTTPS used when the PPE makes requests to the Portal. The default, if not specified, is to always use the page request scheme. Note that if you set useScheme, you must also set the usePort argument. x509certfile Optional. Specifies a file containing a list of certificates to be implicitly trusted by HTTPClient. These certificates are added as trust points to all connections made by HTTPClient using SSL. Portal Custom WLST Commands 12-7

12.2.3 listPortalWebcacheConfigAttributes