Set the definition value in the provider_name.properties file that is

Manually Packaging and Deploying PDK-Java Providers D-7 D.2.4 Setting Deployment Properties In PDK-Java, you can specify a number of deployment properties through JNDI variables. Table D–2 provides a list of these variables with descriptions. Setting the Variables You can set the values of the variables in Table D–2 as you would any other JNDI variables. Refer to Section 7.2.4.2, Setting JNDI Variable Values for information on how to set JNDI variables. D.2.5 Securing Your Provider When using the PDK-Java framework in a production environment, you should secure your providers. For more information on securing providers, refer to Section 7.2.7, Implementing Portlet Security and the Oracle Fusion Middleware Administrators Guide for Oracle Portal. D.2.6 Registering Your Provider Once you have successfully deployed and verified your provider, you can register it as you would any other provider. Refer to Section 6.5.5, Registering and Viewing Your Oracle PDK-Java Portlet for more information about registering your provider. Table D–2 JNDI Variables for Provider Deployment Variable Description oracleportalprovidergloballoglogLevel Is the logging level 0-8 used by PDK-Java and applies to all providers. oracleportalservice_nameshowTestPage Is a Boolean flag that specifies whether a providers test page is accessible. The default value is true. oracleportalservice_namemaxTimeDifference Is the providers HMAC time difference. oracleportalservice_namedefinition Is the location of the providers definition file, provider.xml. oracleportalservice_nameautoReload Is a Boolean auto reload flag. The default value is true. oracleportalservice_namesharedKey Is the HMAC shared key. It has no default value. oracleportalservice_namerootDirectory Is the location for provider customizations. It has no default value. D-8 Oracle Fusion Middleware Developers Guide for Oracle Portal 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.