5-10 Oracle Fusion Middleware Upgrade Guide for Java EE
5.3.5 Configuring Startup and Shutdown Classes
Any startup or shutdown class configured within the source OC4J environment should be converted to a set of Oracle WebLogic Server startup or shutdown classes.
Each class must then be configured within the target Oracle WebLogic Server domain and targeted to the Oracle WebLogic Server instances corresponding to the associated
OC4J instances in the source environment.
Unlike OC4J startup and shutdown classes, an Oracle WebLogic Server startup or shutdown class does not require any specific interface or provide pre-deployment or
post-deployment methods. Instead, you implement the custom logic within the standard main method of the class.
WebLogic Server allows for pre-deployment and post-deployment execution of this logic by providing configuration parameters, which must be set accordingly when
configuring a domain with the startup or shutdown class.
To convert an OC4J startup or shutdown class, it might therefore be necessary to create two WebLogic Server startup and shutdown classes:
■
One that contains the code from the original class preUndeploy method
■
One that contains the code from the postUndeploy method. Although pre-configured parameters can be passed to the main method of a
WebLogic Server startup or shutdown class, Oracle WebLogic Server startup classes have no access to arguments in the way that JNDI context and configuration hash table
parameters are passed to an OC4J startup class.
If the custom logic within the startup class makes use of these parameters, then this logic should be modified to obtain the JNDI context from scratch and access the server
configuration through the Oracle WebLogic Server JMX interfaces.
For more information, see the following:
■
Programming Application Life Cycle Events in Oracle Fusion Middleware Developing Applications for Oracle WebLogic Server
■
Configure startup classes and Configure shutdown classes in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help
5.3.6 Configuring Security on Oracle WebLogic Server
To support the security requirements of your application, you must map the security features of OC4J to the equivalent security features in Oracle WebLogic Server.
Table 5–2 describes how specific OC4J security configurations can be mapped to a
WebLogic Server environment.
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
Kategori