Inc. Server User Manual

Additional Porting and Deployment Considerations
BEA WebLogic Server 7.0 Upgrade Guide 2-31
Use JNDI instead of *.rmi.Naming.
Use weblogic.rmic to generate dynamic proxies and bytecode; with the
exception of RMI IIOP, stubs and skeletons classes are no longer generated.
Note: For more information, see WebLogic RMI Fea tures and Guidelines in
Programming WebLogic RMI.
Use weblogic.rmi.server.UnicastRemoteObject.exportObject() to get
a stub instance.
The RMI examples have not currently been updated to use java.rmi.* and JNDI.
The examples will be revised to reflect
java.rmi.* and JNDI in a future
release.
Security
Upgrading to the New Security Architecture
WebLogic Server 7.0 has a new security architecture. Upgrading WebLogic Server 4.5
or 5.1 to the security functionality in WebLogic Server 7.0 is a two-step process.
1. Upgrade your security configuration to WebLogic Server 6.x.
For instructions on how to upgrade security configurations from WebLogic
Server 4.5 or 5.1 to WebLogic Server 6.x see the Security section under
Additional Migration and Deployment Considerations in Migrating WebLogic
Server 4.5 and 5.1 Applications to 6.x.
2. Upgrade your 6.x security configuration to WebLogic Server 7.0.
See Upgrading Security in Upgrading WebLogic Server 6.x to Version 7.0 for
details.
For specific information about the new security architecture in WebLogic Server 7.0,
see the Security section of the WebLogic Server 7.0 documentation.