6 JSP Tag Configuration

The location of opreapi_rt.jar as shipped is ORACLE_HOME/mp/jlib; this location is unknown to Oracle Application Server Containers for J2EE (OC4J). The jar should be copied to other Oracle Application Server instances that do not have OracleAS Personalization installed but need to access this API either directly or via the JSP tags.

Applications that use REAPI directly or through OracleAS Personalization JSP tags need to make opreapi_rt.jar and dmtutil.jar visible to their application class loader. There are several ways this can be achieved in OC4J. The simplest way to make a supporting JAR visible is to place it in the WEB-INF/lib directory of the application. If you wish to make REAPI visible to all applications in an OC4J instance, you need to place it in the $J2EE_HOME/lib directory. For more information about application deployment, consult OC4J documentation.

In a future release we expect to include the opreapi_rt.jar in the core installation so that these steps are not required.

The OracleAS Personalization tags demo code is maintained by the JSP group. The tags' functionality is coded in the JSP VOB, and is also documented in the Oracle JSP Utilities Guide.