In the Application Attributes section, for Application Name, enter the application

E Oracle Portal Provider Test Suite E-1 E Oracle Portal Provider Test Suite The Oracle Portal Provider Test Suite performs sanity, performance, and unit tests on a Web provider without an installation of Oracle Portal or Internet access from the provider machine. The following two types of utilities are available to the user in the test suite: ■ Section E.1, Provider Test Page ■ Section E.2, Test Harness You can download the Oracle Portal Provider Test Suite from the Oracle Portal Developer Kit PDK page on Oracle Technology Network OTN: http:www.oracle.comtechnologyproductsiasportalpdk.html From the Oracle Portlet Developer Kit PDK home page, select Download the PDK-Java TestSuite . E.1 Provider Test Page The provider test page provides a basic sanity test for the provider. It contains a list of portlets, servlet initialization arguments, and the version numbers of the ptlshare and pdkjava libraries. The provider test page is the simplest utility available for testing any Web provider. You access the test page by a URL after deploying the enterprise application or Web application on Oracle WebLogic Server. You test the Web provider by accessing this URL from a browser: http:server:portapplication_nameprovidersprovider_name For example, the PDK-Java comes with a sample application and portlets. The application is encapsulated in a WAR file, which in turn is encapsulated in an EAR file. When you deploy it, Oracle WebLogic Server extracts the files and creates a directory structure with the sample portlets under: MW_HOME\user_projects\domains\DomainName\servers\WLS_PORTAL\tmp\_WL_user\jpdk To view the test page for this provider, you would use this URL: http:server:portjpdkproviderssample When you access the test page, the SOAP servlet validates the XML provider definition, provider.xml, ensuring that the corresponding provider is well formed. This validation is useful for debugging deployment issues with your provider before attempting to register it with a Oracle Portal. If you successfully deploy your Web application on WLS, you receive a success message on the test page. E-2 Oracle Fusion Middleware Developers Guide for Oracle Portal You can turn the test page on and off by using the JNDI variable oracleportalproviderprovider_nameshowTestPage to true or false. Once a provider is tested and in service you might want to restrict access to the test page. For more information about retrieving and setting JNDI variables, refer to Section 7.2.4, Using JNDI Variables . E.2 Test Harness The test harness is a command line utility for unit- and performance-testing your providers without accessing an Oracle Portal instance. The test harness sends HTTP requests to the target Web provider and records the responses for further analysis. The responses are logged into an XML file. Performance statistics are logged into another file for analysis. The test harness provides considerable flexibility in the following ways: ■ You create your own test definition. Based on the information in the test definition, the harness sends requests to the provider. The test definition file is in XML format and lists request instances to send to the target Web provider. ■ The information returned by the provider is stored in a standard XML file, which makes it easier to understand and analyze. ■ You can perform load testing of the Web provider. E.2.1 Test Definition File The test definition file is an XML file that lists the request instances for a particular test. You can optionally subdivide the request instances into request groups within the test definition file. You can include the details of the request instances in the test definition file or refer to a request library XML file that defines the instance details. In addition to the request instances, the test definition file also includes information about the host and port of the target Web provider and any pre-processors to which it needs to be sent. A pre-processor enables you to include application-specific logic in the request instances at runtime in the test harness. For example, a pre-processor might check the validity of XML in the SOAP messages being sent to the target Web provider. The test harness provides the following three built-in pre-processors: ■ Oracle Portal pre-processor ■ Validation-based caching pre-processor ■ HMAC Hashed Message Authentication Checksum pre-processor The following sample test definition file illustrates the format and content of the file: ?xml version=1.0 encoding=ISO-8859-1? ?testDefinition version=0.1? testDefinition defaultHostmachine.name.comdefaultHost defaultPort80defaultPort defaultPathjpdkproviderssampledefaultPath property name=portletId value=1 preProcessorDefinitions preProcessor class=oracle.webdb.testharness.preprocessor.PortalPreProcessor nameportalname preProcessor preProcessor class=oracle.webdb.testharness.preprocessor.HMACPreProcessor namehmacname