Using Shared Libraries and Class Loading on Oracle WebLogic Server

Upgrading Your Java EE Environment 5-11

5.3.7 Configuring Logging on Oracle WebLogic Server

WebLogic Logging Services provides a comprehensive set of logging features that provide capabilities similar to OC4J. As with OC4J, the Oracle Diagnostics Logging ODL framework can be integrated into Oracle WebLogic Server through the Oracle Java Required Files JRF domain template. For more information, see Section 5.1.4, Using the Java Required Files JRF Domain Template . Table 5–2 Comparison of OC4J and Oracle WebLogic Server Security Features For this OC4J Security Feature... Perform the following task in Oracle WebLogic Server... More Information Users and groups are stored in the system-jazn-data.xml file. Move the user and group information contained in the system-jazn-data.xml file should be moved to the embedded LDAP server. Managing the Embedded LDAP Server in Oracle Fusion Middleware Securing Oracle WebLogic Server OC4J is configured to use an external LDAP provider. Configure the Oracle WebLogic Server domain with the same LDAP server as you were using for OC4J. Configuring LDAP Authentication Providers in Oracle Fusion Middleware Securing Oracle WebLogic Server Users are authenticated against a database. Configure an RDBMS authentication provider, which can be one of three types: ■ SQL Authenticator ■ Read-only SQL Authenticator ■ Custom RDBMS Authenticator Configuring RDBMS Authentication Providers in Oracle Fusion Middleware Securing Oracle WebLogic Server OC4J environment is configured with Java single sign-on or subject propagation between multiple OC4J server instances. WebLogic Server single sign-on and subject propagation are automatic across the server and clusters within a domain and therefore no special configuration is required. Not applicable. OC4J environment is configured with custom JAAS login modules. Create an Oracle WebLogic Server authentication provider within the target domain, either out-of-the-box or a custom provider which wraps the JAAS login module functionality. Supported Login Modules for JavaSE Applications in the Oracle Fusion Middleware Application Security Guide Configuring Authentication Providers in the Oracle Fusion Middleware Securing Oracle WebLogic Server OC4J environment is configured with Oracle Access Manager. Configure the Oracle WebLogic Server domain to use Oracle Access Manager. Integrating the Security Provider for WebLogic SSPI in the Oracle Access Manager Integration Guide in the Oracle Identity Management 10g 10.1.4 Identity Management instancedocumentation library on the Oracle Technology Network OTN. OC4J server instances are configured with SSL encryption. Configure the Oracle WebLogic Server domain to use SSL. Configuring SSL in Oracle Fusion Middleware Securing Oracle WebLogic Server OC4J environment uses Oracle Wallet to store security keys. Store your security keys in a JKS key store in the WebLogic Server domain. Configuring Identity and Trust in Oracle Fusion Middleware Securing Oracle WebLogic Server 5-12 Oracle Fusion Middleware Upgrade Guide for Java EE As a result, if an application is using the ODL framework for logging, it requires no modification when deployed to Oracle WebLogic Server. The JRF ODL integration into Oracle WebLogic Server is as follows: ■ ODL log messages are sent to a separate log file that is kept in a well-known location on the file system: domain_directoryserversserver_namelogsserver_name-diagnostic.log ■ Critical messages errors are double-logged both in the ODL and WebLogic domain log file. ■ ODL log queries and configuration JMX MBeans are available in the domain’s WebLogic administration server. For more information, see Oracle Fusion Middleware Configuring Log Files and Filtering Log Messages for Oracle WebLogic Server.

5.4 Task 4: Redeploy the Application on Oracle WebLogic Server

After you have compiled your application successfully, you can then deploy the application on the Oracle WebLogic Server environment you installed and configured earlier. You can redeploy your Java EE applications using any of the following typical tools: ■ Apache Ant ■ WLST, the Oracle WebLogic Server scripting tool ■ The Oracle WebLogic Administration Console For more information, see Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server.

5.5 Task 5: Verify the Redeployed Applications

After you have deployed your Java EE applications on Oracle WebLogic Server, you can verify the applications by doing the following: ■ Log in to the Oracle WebLogic Administration Console and review the deployments on the domain. You can also perform various monitoring tasks and post-deployment tasks from the console. ■ Navigate in your browser to the application URL and verify that the features of the application are working as they did when you verified them on OC4J earlier in this procedure. If find any problems with the application, review the domain log files to diagnose the problem. For more information, see Configuring Log Files and Filtering Log Messages in the Oracle WebLogic Server documentation library.